SAP AFAB Depreciation Run: Fix Errors, Restart and Reverse
SAP AFAB depreciation run errors how to fix and repeat
Also searched as
- AFAB depreciation posting run terminated
- SAP AFAB error assets not posted
- how to reverse depreciation run AFBN
- AFAR restart depreciation run SAP
Short answer
AFAB posts planned depreciation for a fiscal year and period. If it ends with errors, open the log, fix the listed cause (closed period, locked cost center, missing account determination, or missing master data), then restart the run with AFAR. Use AFBN only when a completed run must be reversed.
Applies to: SAP ECC 6.0 and S/4HANA Asset Accounting; in S/4HANA new Asset Accounting depreciation lands in the universal journal, the transactions remain AFAB, AFAR and AFBN
How to handle a failed depreciation run
- 1Run AFAB with company code, fiscal year, posting period and reason for the posting run: Planned posting run for a normal period. Use Test Run first to see errors without posting.
- 2Open the log after the run (Goto, Log, or AFBP). It lists assets with errors and the message, for example posting period closed, cost center blocked or account not defined.
- 3For closed periods check OB52 (posting periods) for the asset accounting account type and period range, with the usual approvals, or post in an open period.
- 4For account determination errors check AO90 (account assignment of depreciation areas) and the chart of depreciation. The depreciation expense account for the asset class and area must exist.
- 5For cost center issues check the asset master (AS03): the cost center must be valid in the period, not locked for posting, and belong to the correct company code.
- 6After fixing causes, restart with AFAR for the same period, which processes only the assets that failed or were not posted.
- 7To undo a completed run, use AFBN to reverse the posting run for the period, after checking dependent postings and period close status.
- 8Reconcile with the depreciation report (S_ALR_87011964 or the standard asset reports) to ensure planned and posted depreciation agree.
What AFAB does
AFAB calculates the planned depreciation for each asset and depreciation area up to the posting period and posts the amounts to the general ledger. Only areas flagged to post depreciation in the chart of depreciation are processed. The program works from the depreciation key assigned to the asset and the dates for capitalisation and period control.
Every run is recorded with its reason: Planned posting run, Repeat run, Restart run or Unplanned posting run. This history controls which options are available next. For example a repeat is possible for assets that failed, while a restart picks up a run that terminated for technical reasons such as a lock or dump.
Common error causes
Posting period problems are the most frequent: either the general ledger period is closed in OB52, or the asset accounting subledger period is closed for the account type A. Another common cause is that the previous fiscal year was not closed with AJAB, so the new year cannot be opened for depreciation postings. Check both before looking at individual assets.
Asset level errors include blocked or expired cost centers, an asset flagged with a deactivation date, missing depreciation terms in an area, or an account determination gap for a new asset class. Mass failures after an asset class change usually point to a missing account assignment, whereas a handful of failing assets point to master data.
AFAB Depreciation posting run AFAR Repeat or restart depreciation run AFBN Reverse depreciation posting run AFBP Display depreciation posting log AO90 Account determination for asset areas OB52 Maintain posting periods AJAB Fiscal year closing AS03 Display asset master
Reversing and reconciling safely
Reversal is a controlled operation. AFBN reverses the posting run for the period, and later periods that depend on it must be handled in order. In practice you reverse the latest run first, correct the cause and rerun AFAB. If subsequent periods have posted depreciation, escalate to finance before reversing.
After correction, reconcile asset subledger to general ledger. Compare depreciation expense accounts with the sum of depreciation in the asset report for the same period, and check that no assets remain with unposted depreciation. A quick check is the Asset Explorer (AW01N) for a sample asset, comparing planned and posted depreciation.
Common pitfalls
- !Skipping the test run and discovering errors only after a partial posting.
- !Forgetting that the previous fiscal year must be closed with AJAB before the new year's depreciation can run.
- !Reversing with AFBN without checking whether later periods have already posted.
- !Fixing one asset's cost center but ignoring a missing account determination that affects the whole asset class.
- !Changing OB52 period settings without finance approval to force a run through.
How an ERP-grounded AI assistant handles this
A grounded assistant like ERPray can read the depreciation log, asset master data and period status to say which assets failed and why, grouped by cause: closed period, blocked cost center or missing account. It shows the underlying queries and does not run AFAB or AFBN. Posting, restart and reversal remain with authorised finance users.
Frequently asked questions
What is the difference between AFAR and AFBN?
AFAR repeats or restarts a depreciation run for assets that failed or were not processed, so you finish an incomplete run. AFBN reverses a completed posting run for the period. Use AFAR after fixing errors, and AFBN only when posted depreciation is wrong and must be undone.
Why does AFAB say the posting period is closed?
Either the general ledger period is closed in OB52 or the asset accounting period for account type A is. Check both with finance, open the period if approved, or post to the current open period. The depreciation log shows which period caused the failure.
Can I run depreciation before closing the prior year?
Generally no. The prior fiscal year needs to be closed in asset accounting (AJAB) before the new year can post depreciation. Complete year-end steps first, including any outstanding year-end depreciation and balance carry forward, then run AFAB for the new year.
How do I check which assets did not get depreciation?
Open the AFAB log (AFBP) and filter for error messages, then compare to the asset depreciation report for the period. Assets with planned depreciation but no posting need attention. Standard reports and Asset Explorer show planned versus posted values.
Related
SAP F5 060: Posting Only Possible in Periods X and Y
Message F5 060 fires when a document date falls in a fiscal period that the posting period variant has not opened for that account type. Either change the document/posting date into an open period, or have Finance open the required period and account type in OB52 for the relevant variant.
Error fixSAP KI 235: G/L Account Requires an Assignment to a CO Object
KI 235 means a primary cost or revenue element exists (or should exist) on a P&L account, but the posting you are entering has no valid Controlling object - cost center, order, WBS element or profitability segment - to receive it. Add the account assignment on the posting, or set a default cost center via OKB9 so future postings resolve automatically.
Error fixSAP F110 Payment Run: No Payments and the Exception List
When F110 selects nothing or lists vendors in the exception list, the cause is one of four things: the parameters or free selection excluded the items, an item or vendor is blocked, no valid payment method or bank was found in FBZP, or the due date check did not consider the item due in this run. Display the proposal log and exception list to find which.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI for SAP S/4HANA Finance Close (FI/CO) That Traces the Universal Journal for You
AI for SAP S/4HANA financial close: query the universal journal, trace allocations and variances, and manage close tasks. On-prem option, read-only by default.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.