Sunteți pe pagina 1din 1

SAP Knowledge Base Article

1581671 - Error message AU133 during execution of RAPOST2000


Version 2 Validity: 04.05.2011 - active

Language English (Master)

Symptom
l

ErrorAU133keepsoccuringwhenexecutingtherestartoptioninprogramRAPOST2000(transactionAFAB)evenafterupdating
depreciation key 0000 on the asset.

Environment
l

SAPERPallreleases

Reproducing the Issue


1.
2.
3.
4.
5.

Execute program RAPOST2000 (transaction AFAB) in real mode.


Error AU133 is prompted (account is missing in the account determination).
Depreciationkeyoftheassetsinvolvedischangedafterwardsto0000.
RunRAPOST2000inrestartmode.
ErrorAU133persists.

Cause
l

ThedepreciationrunusesstatustableTABAduringtheruntimetosaveastatusofprocessing,justincasethedepreciationrunfailssothe
RESTART option of program RAPOST2000 can determine which actions have to be continued with.
Below phases are processed during the depreciation posting:
Phase 1
After creating the application specific data in Asset Accounting (this is phase 1), the depreciation run updates protocol table TABA with
status "1". At this point of time, the period depreciation is calculated and stored in the Asset Accounting tables (ANLP).
Phase 2
Afterwards the program collects the data and creates the G/L documents to be posted. After all documents are posted successfully, one of
the last actions of the depreciation run is to update the protocol table with value "X", what represents that the depreciation run execution
was successful.

If an error has occurred after phase 1 has been completed, it means that an accounting error has occured (protocol table TABA remains with
status "1").
Changingthedepreciationparametersatthisstatewillnotimpactthecurrentdepreciationcalculationwhichhasalreadyconcludedphase1
andhasstoreddepreciationvaluesintableANLP.

Resolution
1. Finish RAPOST2000 restart execution by completing the account determination and posting the accounting document (you can use dummy
accounts).
2. Subsequent execution will consider new depreciation parameters (depreciation key 0000 in the example) and reverse the already posted
amountsusingsameaccounts.

Header Data
Released On 04.05.2011 09:21:15
Release Status Released to Customer
Component
FI-AA-AA-E Periodic Posting
Priority
Normal
Category
How To

Product
This document is not restricted to a product or product version

S-ar putea să vă placă și