AA 347 — AA 347 — You Cannot Post to Asset in Company Code and Fiscal Year

AA 347 is an Asset Accounting control message that prevents posting to an asset when the fiscal-year state of the company code does not permit it. SAP support describes the message as 'You cannot post to asset in company code ..., fiscal year ...'. Asset Accounting maintains its own fiscal-year processing state in addition to general FI posting periods. A company can therefore have an FI period that appears open while asset posting is still blocked because the asset fiscal-year change or year-end close sequence has not been completed correctly.

The fiscal-year change may not have been executed for Asset Accounting, or it may have been run incompletely. The prior year may not be closed as expected, particularly after system copies, conversions or delayed year-end activity. Fiscal-year status data can become inconsistent if year-change and year-end close jobs are performed out of sequence. Backdated asset acquisitions or retirements can also target a year that Asset Accounting no longer permits. During migration or legacy-data transfer, the target company code may have initialization status that differs from the posting date used by the transaction.

Confirm the company code, asset number and requested posting date/fiscal year. Check Asset Accounting year status and whether fiscal-year change has been completed. Review AJRW execution history and the year-end close process represented by AJAB or the corresponding S/4HANA apps/processes for the release. Compare the target company code with another company code that can post successfully. If the error appeared after a system refresh, migration or conversion, validate the current asset fiscal-year state rather than assuming the copied calendar dates are enough. Also confirm that the posting is genuinely intended for that year and is not using an old document date accidentally.

Complete the supported Asset Accounting fiscal-year change or year-end sequence for the company code, following the release-specific process and prerequisites. If a backdated posting is no longer allowed, determine the correct accounting treatment with Asset Accounting rather than manipulating the fiscal-year status solely to post one document. In migrated systems, correct initialization or year-state issues through supported migration/year-change procedures. After the change, test a standard asset posting and validate depreciation/fiscal-year values; opening the year technically is not sufficient if the year-end sequence remains inconsistent.

Changing the posting date to a current year can make the message disappear but may put the asset acquisition, retirement or transfer in the wrong fiscal period. Another poor workaround is manually changing year-status tables. That risks breaking depreciation carryforward and subsequent year-end processing. Asset Accounting year state is part of financial control and should be advanced through supported transactions or apps, not database edits.

FI-AA owns AA 347. General FI should confirm posting periods but cannot resolve the asset-specific fiscal-year state alone. Basis may schedule jobs, while migration teams may be involved after conversion or system refresh. Business asset accountants should approve any decision involving backdated posting or reopening historical activity. ABAP is generally not required unless custom posting logic is supplying an incorrect posting date.

Do not assume OB52 or open FI periods prove Asset Accounting is ready for the year. Check the asset fiscal-year change separately. Be careful in January when calendar year has changed but AA year-change processing has not. System copies can leave business users seeing a new date while asset status reflects the source system's close cycle. After correction, verify depreciation and year-end reports, not just the ability to save one posting.