Environment:
It was launched in 2008, and the deactivating system in 2009 only raised depreciation once in January. 2010. 03 newly purchased assets, an error occurred during depreciation in May April. "after the previous year's settlement, you can only keep your account for the New Year." In May 2009, you normally complete the year's settlement, there is no problem with the asset data. It should be a system bug. I found a SAP solution for this bug and successfully solved it.
Cause: When SAP raises depreciation, it first checks the depreciation log (not logs for each asset). If the depreciation log does not exist in the early stage, but it can be calculated out of the plan, but if the amount is not depreciated in the early stage, this bug will occur. No matter which method you use, you cannot make a profit. Depreciation logs are stored in the Taba table. You can manually add a log of the previous period (the last period of the previous year) so that the system determines that the last period of the previous year has been depreciated. Based on the situation, make plans or unplanned provisions.
The reference is as follows:
Handling
Depreciation posting program error for first period depreciation
Posting
Error
Message: "aa687-you can only post in New Year after closing
Previous Year"
Background:
In
Scenario where asset accounting has been implemented first time for
Company Code
With
The following configuration settings:
Fiscal
Year variant: Calendar year based
Current
Fiscal year: January 2009 to December 2009
Depreciation
Posting cycle: monthly
Legacy
Asset Transfer Date: 12/31/2008 (I. e. Last day
Previous fiscal year)
Go
Live Volume l 2009
Following
Activities also have been completed:
• Fiscal
Year changed to Year 2009 using transaction code ajrw
• Fiscal
Year closed for year 2008 using transaction code abaj
• Legacy
Assets created
• New
Assets created
• Transactions
Posted for new assets
Depreciation
Is being posted for period 01 2009
Afab:
System
Is giving error message "You can only post in New Year after
Closing
Previous
Year "even though fiscal year is changed to 2009 and previous
Fiscal year 2008
Is already closed.
The
Detail description of the error is as below:
We
Cannot post any depreciation to previous fiscal year 2008 as no
Planned depreciation
Is
Envisaged for the previous year 2008. The transfer date for legacy
Asset data transfer is
Maintained
As 12/31/2008 and takeover values are uploaded accordingly. Hence,
2009 is
A
First year for asset accounting of the company code.
However,
Depreciation posting program checks for previous period log while
Executing
The
Current period. The logs are stored in "Taba" table. For new
Company Code there will
Not
Be any entries in Taba table.
Due
To missing functionality, system is checking for previous year
Depreciation posting
Logs
Even though the current fiscal year is first year for planned
Depreciation and giving
Error
Message AA 687.
As
Per sap note 144441 this error can be rectified with the help
Correction Program
Zaobao _taba_entry_create.
Steps
To rectify the error
1. Copy
Correction program from SAP note 144441 into SAP system.
2. Execute
The program with transaction code sa38
3. Correction Program
Inserts the dummy entry in the table Taba
Related
Content
SAP
Note: 14444
SAP
Note: 843612
SAP
Note: 156181
For
More information, visit the Enterprise Resource Planning homepage.
SAP community network SDN-sdn.sap.com | BPX-bpx.sap.com | Boc-boc.sap.com
2009 SAP AG