In Asset Accounting, for depreciation we still use the previous AFAB or AFABN transaction

codes but it is now mapped to a new program which is FAA_DEPRECIATION_POST. The

initial programme RAPOST2000 and RAPOST2010 are not being used now. Below are the
screenshots of AFAB transaction in ECC and S4HANA.

AFAB in ECC:

AFAB in S4HANA:
As per the screenshots, you will be able to analyse major changes in the screen itself. I would
like to explain few changes in details between ECC and S/4HANA.

·        S4HANA - The major change which is there in S4HANA is related to table ACDOCA. We
can get complete details of the posting at GL’s also and can get report of the data posted in the
accounting principle and Fiscal Period.

·        ECC – Whenever we used to run the depreciation it used to update ANLP table and then it
used to get updated in the GL tables. First, it would summarize the depreciation values for every
account and then creates its own internal asset document. Then it will create these asset
document into multiple line items in an FI Document. In ECC it will be difficult to find the
actual amount posted per asset and period. ANLP table had the information but not BSEG. Now,
ACDOCA will show us the amounts posted per asset, per period, and per accounting principle.

In the below screenshot the document is posted by FAA_DEPRECIATION_POST. While the

asset field isn’t shown, the description column shows the asset number that is credited in
each line item. This is the big change we can now see the posted depreciation at an asset level
from within the GL.
The underlying source is ACDOCA. For this same FI document, the table is recording the data
per ledger.
·        A major change that SAP has made has to do with errors that hold up the depreciation
run. In ECC, the FI document created by the depreciation run would post the Document only if
there is no error in the assets. Even if a single asset contains any error, then all of the other assets
that were summarized in that particular FI document would also not get posted. You had to then
execute the program in Restart mode after you fixed the underlying error. This is no longer the
case in S/4HANA. The assets without errors are allowed to post and only the assets that errored
out will be held back. We can even complete the month end closing activity and move on to the
next period in this situation. However, at year end, we’ll need to correct all the errors which we
skipped during the Period run in order to close out the fiscal year. In this, the point is a single
error on one asset won’t hold up the posting of depreciation for other assets.

·        You can now execute the depreciation run for multiple company codes. Previously in ECC,
it was only possible to execute depreciation for a range of company codes by directly executing
program RAPOST2010. RAPOST2010 wasn’t mapped to any tcode so few customers were
aware of it. Now in S/4HANA, the main (and only) program allows you to execute it for multiple
company codes.

·        The selection screen has changed in a few noticeable ways. First, there were four options
under “Reason for Posting Run” which are no longer available. In S4HANA new program will
correctly determine what type of depreciation run you are making so the options are no longer
there.