AFAB — Depreciation Posting Run
AFAB is used to post periodic planned depreciation from Asset Accounting to the general ledger. It is most useful during month-end or year-end close after asset master data and planned depreciation have been validated. 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 AFAB — Depreciation Posting Run — 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· 616 words
Esta página aún no está disponible en español.
Purpose
post periodic planned depreciation from Asset Accounting to the general ledger. 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
AFAB is typically used during month-end or year-end close after asset master data and planned depreciation have been validated. 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
- Run the process according to the closing calendar and approved company-code scope.
- Review test/planned values and prior-period status.
- Execute the posting run in the appropriate mode and monitor logs.
- Investigate assets with errors instead of repeatedly rerunning the whole population.
- Reconcile posted depreciation to asset and G/L reports.
Key data objects
These are the fields and business objects that usually explain the result in AFAB. 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.
- fiscal year/period — verify the exact value, validity/date context and source of derivation.
- posting run mode — verify the exact value, validity/date context and source of derivation.
- depreciation areas — verify the exact value, validity/date context and source of derivation.
- run log and accounting 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
S/4HANA Asset Accounting still requires periodic depreciation posting; the integrated journal improves reconciliation but does not remove closing controls. 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
- Rerunning a completed period without understanding repeat/restart behavior. Reconcile the exact document and period before making a configuration change.
- Ignoring master-data errors for individual assets. Reconcile the exact document and period before making a configuration change.
- Comparing planned depreciation with posted ledger values before the run completes. 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/afabERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.