Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

There have been several postings on the ERP Financials and Asset Accounting forums in the past year related to the reversal of depreciation in the fixed asset area.  I decided to write up a quick blog to discuss the SAP functionality provided around this topic.  As a reference point you can first look at some of the forum threads Depreciation posting reversal and Re: how to reverse depriciation posted to an asset.


First, the Question

The question that has been asked is whether or not it is possible to reverse a depreciation posting run in SAP ERP. 

To clarify, I'm referring to the reversal of a depreciation posting run, i.e. from the depreciation posting program RAPOST2000 (or RABUCH00 if you are on an older SAP release).  This is different than resetting depreciation or adjusting depreciation...  two other common phrases related to this subject area.


Now, the Answer

There is no standard solution offered by SAP to reverse a depreciation run.  To even attempt a solution would require a significant series of adjustments to the associated FI-AA tables as well as the corresponding FI documents generated by the Depreciation Posting program.  To create a solution for this that would still maintain proper consistency of the sub-ledger to support future depreciation runs and fixed asset reporting, as well as maintain the reconciliation between the General Ledger and the asset Sub-Ledger would be enormously difficult.  For those customers that have a legitimate requirement to reverse a depreciation run, SAP offers a remote consulting service ($$$) to assist in this highly technical area...  but this is not a standard solution and not freely available. 

Resetting depreciation (transaction OAGL) should NEVER be executed in a live system.  The only reason that SAP even  delivers the program in the first place is to assist in the initial configuration and setup of a new ERP instance.  As an example, during the initial implementation it is normal to have to execute the depreciation program multiple times to flush out issues surrounding account assignment, reporting, depreciation calculation, authorization, etc.  During this time of constant change it is often necessary to reset the various asset tables so that depreciation can be run anew for a given company code or fiscal year/period.  It is important to mention that there is no way to reverse the effects of a program like this.  Also keep in mind that your userID is logged in SAP whenever this is run which provides a very easy-to-follow audit trail if it were ever necessary to track down who ran the program.

Adjusting depreciation...  well, that's a topic for about another dozen blogs.  There are numerous ways to adjust depreciation in SAP and even more requirements based on transactional processing and reporting.

Labels in this area