Posting Depreciation 

Use

Every asset transaction in the Asset Accounting (FI-AA) component immediately causes a change of the forecasted depreciation. However, an asset transaction does not immediately cause an update of the depreciation and value adjustment accounts for the financial statements. The planned depreciation is posted directly to Financial Accounting (FI) when you run the periodic depreciation posting run. This posting run posts the planned depreciation for each posting level for each asset as a lump sum amount.

When the system posts depreciation, it creates collective documents. It does not create separate documents for each asset.

Prerequisites

You can choose both the posting cycle and the additional account assignment levels, such as, cost center or order (see Additional Account Assignment), for the depreciation posting run for each company code and depreciation area. This specification is made in Customizing for Asset Accounting.

In Customizing for Asset Accounting, choose Integration with the General Ledger and then these activities:

●      Post Depreciation to the General Ledger → Specify Intervals and Posting Rules

●      Activities under the Additional Account Assignment Objects node

You can enter the accounts that are to be posted in the account determination in each depreciation area (see Account Determination).

Features

The calculation and scheduling of depreciation, interest and revaluation are automatically controlled by keys in the system, or you can control them manually using a special posting transaction. In both cases, planned depreciation from Asset Accounting has to be periodically posted to the corresponding asset and expense accounts of the general ledger. In addition to the various depreciation types, interest and revaluation, this posting run also posts the allocation and write-off of special reserves.

For more information on the posting run, see Posting Depreciation.

Performance

It is difficult to provide precise information on performance, since it is strongly dependent on your system configuration. However, you can use the figures below for a rough estimate:

●      For the calculation of depreciation, 16000 assets per hour is possible.

●      Since only collective documents are created, the number of documents to be posted per depreciation posting run depends on the number of G/L accounts to be posted, and on the number of combinations of account assignments and account determinations.

 

For more information on improving performance, see System Performance Improvements.

Keep in mind that the update run of the depreciation posting run can only be started in the background.