AS02 — Change Asset Master Record
AS02 is used to change permitted fixed-asset master attributes such as descriptions, assignments and depreciation-related settings. It is most useful when an asset's responsible cost object, location or master-data attributes change and accounting policy permits the update. 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 AS02 — Change 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· 620 words
Esta página aún no está disponible en español.
Purpose
change permitted fixed-asset master attributes such as descriptions, assignments and depreciation-related settings. 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
AS02 is typically used when an asset's responsible cost object, location or master-data attributes change and accounting policy permits the update. 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
- Display the current master and identify which fields are time-dependent.
- Use the correct effective date for organizational changes.
- Change only attributes supported by the business event and policy.
- Review depreciation consequences before changing valuation-related data.
- Save and verify change documents.
Key data objects
These are the fields and business objects that usually explain the result in AS02. 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.
- asset and subnumber — verify the exact value, validity/date context and source of derivation.
- valid-from date — verify the exact value, validity/date context and source of derivation.
- cost center/location — verify the exact value, validity/date context and source of derivation.
- depreciation areas — verify the exact value, validity/date context and source of derivation.
- change documents — 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
AS02 remains relevant on S/4HANA. Because Asset Accounting is tightly integrated with the Universal Journal, valuation changes require careful accounting impact analysis. 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
- Changing historical master data without considering already-posted depreciation. Reconcile the exact document and period before making a configuration change.
- Using a current-date assignment to explain a historical posting. Reconcile the exact document and period before making a configuration change.
- Changing valuation fields to make a posting work instead of fixing the transaction. 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/as02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.