ABUMN — Asset Transfer Within Company Code
ABUMN is used to transfer asset values from one asset to another within the same company code. It is most useful when responsibility, asset class or organizational ownership changes and accounting requires a formal asset transfer. 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 ABUMN — Asset Transfer Within Company Code. 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· 609 words
Esta página ainda não está disponível em português.
Purpose
transfer asset values from one asset to another within the same company code. Treat ABUMN 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
ABUMN is typically used when responsibility, asset class or organizational ownership changes and accounting requires a formal asset transfer. 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
- Display the sending asset and current values first.
- Enter transfer dates and the receiving asset or new asset data.
- Use the transfer variant required by accounting policy.
- Simulate and review line items by depreciation area.
- Post and verify both assets in Asset Explorer.
Key data objects
These are the fields and business objects that most often explain the result in ABUMN. Record them in support evidence so the next person can reproduce the same outcome.
- sending asset — verify the exact value, validity/date context and relationship to the source document.
- receiving/new 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.
- transfer variant — verify the exact value, validity/date context and relationship to the source document.
- amount/percentage — 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 ABUMN 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 documents ABUMN as the transaction for transfer within company code; it remains relevant 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
- Using an asset transfer to correct an acquisition that should be reversed. Reconcile the exact business document and date before applying a workaround.
- Choosing an asset value date that conflicts with capitalization history. Reconcile the exact business document and date before applying a workaround.
- Ignoring depreciation-area differences between sending and receiving assets. 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/abumnERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.