# SAP AFAB Depreciation Run: Fix Errors, Restart and Reverse > Source: https://netray.co/erp-help/sap-afab-depreciation-run-errors-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module FI-AA Asset Accounting ## Query SAP AFAB depreciation run errors how to fix and repeat ## Alternate Queries - AFAB depreciation posting run terminated - SAP AFAB error assets not posted - how to reverse depreciation run AFBN - AFAR restart depreciation run SAP ## 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 ## Steps ### How to handle a failed depreciation run **Items:** - Run 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. - Open 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. - For 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. - For 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. - For 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. - After fixing causes, restart with AFAR for the same period, which processes only the assets that failed or were not posted. - To undo a completed run, use AFBN to reverse the posting run for the period, after checking dependent postings and period close status. - Reconcile with the depreciation report (S_ALR_87011964 or the standard asset reports) to ensure planned and posted depreciation agree. ## Sections ### What AFAB does **Body:** 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 **Body:** 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. **Code:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is the difference between AFAR and AFBN? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms SAP AFAB depreciation run, AFAB errors, AFAR restart depreciation, AFBN reverse depreciation run, SAP asset accounting depreciation posting, AJAB fiscal year closing assets, AO90 account determination, SAP depreciation posting log, OB52 asset posting period, SAP FI-AA troubleshooting --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json