SAP Note 26073 - RABUCH00 table T093D is inconsistent

Symptom:

During depreciation posting using RABUCH00, error messages (for example AA726) are issued because a previous period or even a previous fiscal year instead of the actual last posted period is entered in table T093D.

Other terms

TABA, OAE4, AA683, RABUCH00, RAPOST2000, AFAB, AFABN, AA726, AA 726,

Reason and Prerequisites

The date "Posted upto" was presumably changed for old assets data takeover during the fiscal year in Old Assets Data Takeover Customizing after the last depreciation posting. In the process, the fields for the last posted period were also reset in table T093D.

Solution
After depreciation has already been posted, the parameters may no longer be changed for old assets data takeover. If necessary, this should be ensured by the appropriate restricted authorizations.
Table T093D can be rectified with the following ABAP report.

Report ZZT093DU.
Tables T093D.
Update T093D
Set AFBLPE = 'PPP' " <=== correct period
AFBLGJ = 'YYYY' " <=== correct fiscal year
AFBANZ = '00'
STATUS = ' '
Where BUKRS = 'BBBB' and " <=== company code
AFABER = '01' and " <=== depreciation area
AFBLPE = 'ppp' and " <=== wrong period
AFBLGJ = 'yyyy'. " <=== wrong year