AS01 — Create Asset Master Record
AS01 is used to create a fixed-asset master with asset class, organizational assignments, depreciation areas and useful-life information. It is most useful when a new capital asset must exist before acquisition, transfer or capitalization postings can be recorded. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains AS01 — Create Asset Master Record — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 640 words
Esta página ainda não está disponível em português.
Purpose
create a fixed-asset master with asset class, organizational assignments, depreciation areas and useful-life information. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
AS01 is typically used when a new capital asset must exist before acquisition, transfer or capitalization postings can be recorded. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Select the correct company code and asset class first because they drive field status and account determination.
- Enter descriptive and organizational assignments from approved asset-creation evidence.
- Review depreciation-area defaults rather than accepting them blindly.
- Save and capture the asset/subnumber.
- Display the asset again before acquisition posting to confirm master data.
Key data objects
These are the fields and business objects that usually explain the result in AS01. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- company code — verify the exact value, validity/date context and source of derivation.
- asset class — verify the exact value, validity/date context and source of derivation.
- cost center/profit center — verify the exact value, validity/date context and source of derivation.
- depreciation key and useful life — verify the exact value, validity/date context and source of derivation.
- time-dependent assignments — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
S/4HANA keeps asset master functionality, while Business Partner changes do not replace fixed-asset master data. Universal Journal integrates asset postings more tightly with the general ledger. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Choosing the wrong asset class and discovering the account determination problem only at posting. Reconcile the exact document and period before making a configuration change.
- Leaving time-dependent cost-center assignments inconsistent with the capitalization date. Reconcile the exact document and period before making a configuration change.
- Manually overriding depreciation settings without Asset Accounting approval. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/as01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.