When book depreciation is run as a part of periodic processing, table T093D and TABA are updated accordingly with period and fiscal year information. T093 hold values of recent depreciation period and fiscal year, whereas TABA hold entries for each depreciation run and indicates if a document in FI has been posted or not. With few customizing transactions relevant to depreciation area, table T093D is also transported though this table is not relevent to customizing and is a system dependent. This causes inconsistent values in T093D and possibly could cause error messages when trying to post depreciation or perform year end closing.
To validate, table entries of TABA and T093D should be reconciled and have same last period for which depreciation was posted. If not in such cases, write a code to correct the T093D table entries. Check Note 26073.
Table T093D will get it’s first entry when chart of depreciation is assigned to company code. So do not delete the entry from the table as system would issue error message at the depreciation run.
Above picture shows the initial entry that is created when chart of depreciation is assigned to the co code. Later when assets are loaded and depreciation was run as part of periodic processing, then fiscal year, posted up to, no of posting runs fields are updated accordingly.
Technically this system dependent table shouldn’t be attached to the customizing transport. Hopefully SAP fixes it soon 🙂
FICO bites 