SAP Note 23760 - Incorrect audit trail for commercial law

Symptom:

Audit trail, Depreciation run
The end of the log shows the planned total, the posting total for the previous months, and the postings for this depreciation run. A summation error then occurs, as the depreciation posting total for the previous months is wrong.
Example: actually posted in January: 2'095'051.58
actually posted in February: 2'102'830.35
results in a total of 4'197'881.93
The audit trail for March reports 'posted so far': 4'178'014.93.

Cause and prerequisites

Problems in understanding the system.

Solution
Only those fixed assets are included in each depreciation posting run which contain depreciation that has still to be posted. Assets without depreciation in the period in question, either because they have been deactivated, or whose depreciation calculation had been closed with the end of their useful life (for example, during the fiscal year, in which case the depreciation for past periods in a lump sum was defined in the depreciation posting rules), are no longer contained in the next posting run. As a result, the depreciation posted so far for these fixed assets is not displayed in the RABUCH list. Therefore, you cannot expect that the depreciation for these fixed assets to be posted in the previous period will be displayed in the next period as 'depreciation posted so far'. From Release 3.0A this procedure has been re-arranged
to agree better with Financial Accounting. In the log for Rabuch00 from
Release 3.0A, those fixed assests are also posted for which depreciation
was to be posted in the previous period, but not, however, in the
present period. (You should compare Note 82541)

Additional key words

RABUCH00