← All SAP articles

SAP depreciation becomes confusing when we begin with transaction codes. Start with the business requirement: an asset provides value over several periods, so its cost must be allocated systematically instead of expensed immediately.

SAP Fixed Asset Depreciation Explained: APC, Keys, Areas and Accounting

Start with acquisition and production cost

Acquisition and production cost, usually called APC, is the value that becomes the basis for depreciation. It can include purchase price and other directly attributable costs, depending on accounting policy.

The depreciation calculation does not begin with a percentage alone. SAP needs the correct APC, capitalization date, useful life, depreciation key and depreciation area.

What a depreciation area represents

A company may need different asset values for different purposes: group accounting, local statutory accounting, tax reporting or management analysis. Depreciation areas represent these parallel valuation views.

One area may post to the leading ledger while another supplies a non-posting statistical view or posts to a different ledger. The design must align with the accounting principles and ledger approach.

What the depreciation key controls

The depreciation key combines calculation methods. It determines how SAP spreads value over time and handles the beginning or end of depreciation.

Key components can control:

Do not select a key because its description sounds familiar. Test it against specific dates and values.

Period control is where dates become amounts

Period control determines how acquisition, retirement, transfer and other transaction dates affect the depreciation start or end period.

For example, two assets with the same cost and useful life can produce different first-year depreciation if one uses exact-day calculation and the other uses a monthly convention.

This is why test cases must include mid-month and year-end transactions.

Planned versus posted depreciation

SAP calculates planned depreciation based on master data and transactions. The periodic depreciation run posts the amount to Financial Accounting.

A simplified posting is:

The asset explorer helps compare APC, planned depreciation, posted depreciation and net book value across years and depreciation areas.

The periodic depreciation run

The run normally selects company code, fiscal year and posting period. It posts depreciation for eligible assets and records errors for assets that cannot be processed.

Before running it, confirm:

Review the log instead of assuming a completed job means every asset posted correctly.

Changes after capitalization

Useful life, depreciation key, capitalization date or value can change. SAP may recalculate planned depreciation and distribute the adjustment over remaining periods or create catch-up effects, depending on configuration.

Every change should have an accounting reason and an effective date. Test current-year and prior-year changes separately.

Common troubleshooting checks

If depreciation is missing or wrong, inspect:

This sequence moves from asset facts to posting controls.

The takeaway

Depreciation is a chain: APC provides the value, depreciation areas provide valuation views, the depreciation key provides calculation logic, period control interprets dates, and the periodic run creates the FI posting.

Do not memorize AFAB in isolation. Explain the expected annual and periodic amount first, then prove how SAP derived and posted it.

Follow the complete Fixed Assets learning path