AJRW — Asset Accounting Fiscal Year Change
AJRW is used to open the next fiscal year in Asset Accounting so asset transactions and depreciation processing can continue. It is most useful as part of Asset Accounting year-end activities before working in the new fiscal year. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for AJRW — Asset Accounting Fiscal Year Change. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 603 words
Esta página aún no está disponible en español.
Purpose
open the next fiscal year in Asset Accounting so asset transactions and depreciation processing can continue. Treat AJRW as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
AJRW is typically used as part of Asset Accounting year-end activities before working in the new fiscal year. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Confirm closing calendar and prerequisite depreciation/status activities.
- Run the fiscal-year change for the intended company code.
- Review the log for assets or company codes not advanced.
- Resolve errors before allowing new-year processing.
- Verify Asset Accounting year status after completion.
Key data objects
These are the fields and business objects that most often explain the result in AJRW. Record them in support evidence so the next person can reproduce the same outcome.
- company code — verify the exact value, validity/date context and relationship to the source document.
- new fiscal year — verify the exact value, validity/date context and relationship to the source document.
- last closed year — verify the exact value, validity/date context and relationship to the source document.
- asset fiscal-year status — verify the exact value, validity/date context and relationship to the source document.
- run log — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the AJRW document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
SAP lists AJRW as the Asset Accounting Fiscal Year Change transaction; it remains part of classic year-end control in S/4HANA Asset Accounting. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Running AJRW for the wrong company code/year. Reconcile the exact business document and date before applying a workaround.
- Confusing fiscal-year change with year-end close. Reconcile the exact business document and date before applying a workaround.
- Ignoring unresolved prior-year depreciation/posting issues. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the Finance/Controlling team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ajrwERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.