AO90 — Asset Accounting Account Determination
AO90 is used to maintain G/L account assignments used by Asset Accounting for acquisition, depreciation, retirement and related postings. It is most useful when configuring an asset class/account-determination design or troubleshooting unexpected FI accounts from asset postings. 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 AO90 — Asset Accounting Account Determination. 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· 612 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
maintain G/L account assignments used by Asset Accounting for acquisition, depreciation, retirement and related postings. Treat AO90 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
AO90 is typically used when configuring an asset class/account-determination design or troubleshooting unexpected FI accounts from asset postings. 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
- Start from the asset class and account-determination key used by the failing asset.
- Identify the exact posting type and depreciation-area context.
- Compare configured accounts with the approved chart-of-accounts design.
- Change only with FI-AA/GL governance.
- Test acquisition, depreciation and retirement scenarios as appropriate.
Key data objects
These are the fields and business objects that most often explain the result in AO90. Record them in support evidence so the next person can reproduce the same outcome.
- chart of accounts — verify the exact value, validity/date context and relationship to the source document.
- account determination key — verify the exact value, validity/date context and relationship to the source document.
- depreciation area/posting type — verify the exact value, validity/date context and relationship to the source document.
- G/L accounts — verify the exact value, validity/date context and relationship to the source document.
- asset class linkage — 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 AO90 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 documentation references AO90 as Asset Accounting account determination; it remains a high-impact S/4HANA FI-AA configuration transaction. 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
- Changing AO90 before confirming the asset class/account-determination key. Reconcile the exact business document and date before applying a workaround.
- Using one account to bypass a missing G/L master or field-status issue. Reconcile the exact business document and date before applying a workaround.
- Testing only one asset transaction type after a broad account change. 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/ao90ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.