ABZON — Asset Acquisition with Automatic Offsetting Entry
ABZON is used to post an asset acquisition directly with an automatically determined offsetting entry. It is most useful when an asset acquisition is entered without a vendor invoice and the offsetting account is determined by configuration. 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 ABZON — Asset Acquisition with Automatic Offsetting Entry. 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· 594 words
Esta página ainda não está disponível em português.
Purpose
post an asset acquisition directly with an automatically determined offsetting entry. Treat ABZON 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
ABZON is typically used when an asset acquisition is entered without a vendor invoice and the offsetting account is determined by configuration. 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 the asset master and capitalization context.
- Enter dates and acquisition amount.
- Check transaction type and any required account assignment.
- Simulate the generated accounting lines.
- Post and verify acquisition value and FI document.
Key data objects
These are the fields and business objects that most often explain the result in ABZON. Record them in support evidence so the next person can reproduce the same outcome.
- asset — verify the exact value, validity/date context and relationship to the source document.
- document/posting/asset value date — verify the exact value, validity/date context and relationship to the source document.
- amount — verify the exact value, validity/date context and relationship to the source document.
- transaction type — verify the exact value, validity/date context and relationship to the source document.
- offsetting account determination — 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 ABZON 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 Help explicitly documents ABZON for acquisition with automatic offsetting entry. 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
- Using ABZON when a vendor invoice or MM acquisition should provide the source document. Reconcile the exact business document and date before applying a workaround.
- Posting with the wrong asset value date. Reconcile the exact business document and date before applying a workaround.
- Accepting the generated offsetting account without validating account determination. 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/abzonERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.