ASKB Error

Hi Friends,
The business try to execute the t. code ASKB manually to post the year 2010 getting an error message Account 'Acc dep, account for ordinary depreciation' could not be found for area10.
As we can see in the Asset Explorer for the asset 10010000009 ordinary depreciation was calculated as 7900.57 EUR. and also find that this asset was retired on 10 2010.
1) I understand that this depreciation came from the legacy transfer. There is no depreciation in any year.
2) This transaction had run since started globe. I understand that the error became when this asset was retired on February 2010.
Request you to let us know how to rectify the error, how can we run the ASKB with out any errors.
Regards
Sree

Hi Sree,
Error AU133, is generally issued from some wrong or missing customizing. The text of the error message indicates in your case that a "dep, account for ordinary depreciation' " and area 10 is concerned.
1) At first, please double check if in in AO90 (or table T095) the account is maintained for area 10.
Further, check in tr. OADB if you have defined "Different Depreciation Area XX". That means area 64 takes the account determination from area xx and perhaps there it is no account defined?
If this is not the reason:
2) Execute report RACKONT1 or transaction OAK4. Account determination should be set following the rules explained in SAP note 7595. Even if some account is not directly used, the account determination has to be completed. If output from RACKONT1 is not error free, it indicates that your customizing is wrong. You might correct it with the help of note 7595.
Furthermore:
3) You have defined the account in Asset Accounting, however, it is not created in the affected company code. Check whether the account is correct and create it for the company code, if necessary.
4) Threats
Error AU133 Account 'Contra account: Acquisition value' could not be found
AFAB- account determination error
Error AU133 received while posting asset transfer
Best regards Bernhard

Similar Messages

ASKB error - Posting period 012 2009 is not open

Hi All,
We are using ECC 6.0 version.
We have posted an asset acquisition on 31st Dec 2008 in a Local Dep area with posting date 31st Dec 2009. Posting was made only in Local ledger and not in leading ledger.
It was a mistake from our side and rectified immediately on the same day by reversing the entry and reposted with posting date 31st Dec 2008
This issue is erroneous as posting period 12 2009 was open at the time of posting and later realized and has been closed.
Now, We are trying to run ASKB for all the assets in that Co.Code. But, System is blocking the entire log for processing. The Error being u201Cposting period 012 2009 is not openu201D
We cannot exclude this particular asset for this run and we cannot even open period 012 2009 for security reasons
Pls advise.
Thanks,
Pavan.

Hi Pawan,
May be you can try posting with period 12/2009 opened. For security reasons, you can block the period for others and keep it opened only for a particular authorisation group and have the auth. group assigned to only one person who runs the transaction.
Regards,
Mike

ASKB posting error, period 7 2010 is closed

Hi All,
Fo for the captioned issue , 2010 year is not closed .
When we are tring to close the same through AJAB, we are gettiing teh error, transactions not completely periodically posted.
I got the error '1000xxxx-xxx Depreciation not posted completely'
Now I tried to run ASKB .
I get teh error `period 7 2010 is not open`. Please let me know, how to handle this scenario.As we can no more open 2010 period.
How to ensure 2010 asset year close will be done.
Regards
Rudra

Hello,
Please check the set-up of transaction OADB.
If you have areas assigned to GL indicator 2, 4, 5 and 6 this causes the error.
You need to temporarily set GL indicator for those Areas to 0. Then run AJAB. You will not encounter any more error regarding "not periodically posted". After you run AJAB, you may set the indicator back.
Thanks!
Jhero

Error AA 738 while periodic asset posting - ASKB

Hello,
could you please advise if anybody have encounterd following error when executing transaction: ASKB (test run) as background processing:
Number range 01 has not been created for document type AA.
Message no. AA738
Diagnosis
No valid number range interval has been created for document type AA.
Procedure
Specify an interval for number range 01 in the year 999 for company code XXXX.
I checked that for the mentioned company code number range 01 is created for the current year.
Additionally users executed production run of ASKB (without a test run) and then got an error: Account determination - Loss made on asset retirement w/o reven. not found for area 20 for account group 1411000 - this was fixed but then additional error AA738 came up.
If you can advise how to get rid of error AA738, I would be more than grateful.
Thank you in advance,
Monika

Hi
Though the error says 999, usually its maintained for 9999 (assuming there is no issue wiht your FYsettings)
In addition to that,
The report evaluates all asset transactions since the last run. Unlike the periodic depreciation posting program, the APC posting run is not tied to a certain accounting period. It generates one document per posting period and depreciation area. That means that asset values are summarized for various account groups in one document. Document number assignment is external. You have to enter the document type in Customizing for Asset Accounting.
What I suggest, pls go thru the blue colour 'i' icon in that T code input screen.
regards
S

Error in transaction ASKB - Balance in transaction currency

Hi
When i am executing transaction ASKB im getting the error:
Balance in transaction currency
Message no. F5702
Diagnosis
A balance has occurred in transaction currency 'EUR' with the following details:
Exchange rate '00', amount '     1,953,936.19' and currency key 'EUR'.
The data in the transaction currency were transferred from the calling application.
System response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.
Can anybody help me in same.
Thanks and Regards
Megha

Hi Chris,
have you checked the last answer from Raja,?
Derived depreciation areas could no handle APC differences unless you activate the indicator "Treat Derived Depreciation Area As Real Area" under the following menu:
SPRO -> Asset Accounting -> Valuation -> Depreciation Areas -> Define Depreciation Areas).
If you set this indicator, then the system posts the real difference. If you would like to apply this indicator you have to complete the account assignment in the configuration, too.
You can switch the derived area from a special reserves area to a "handled as real" area in transaction OADB. There is no other possibility to get the derived area post APC differences, which you definitely have on some assets.
Please also review and apply the following Notes:
759890   Depreciation run ends with error F5 702
1094330 F5 702 with retirement on group asset
1024598 Incorrect values with repeated simulation
Regards Bernhard

Error in ASKB "Asset 1-177 0 not in company code LX01'

Hi Experts,
Until Jan. 2009, only 1 depreciation area is activated for company code LX01 (01). For some assets, we had retirements/write-up postings. Came Feb. 2009, dep.area 10 was activated.
With 2009 year-end closing AJAB, the process found an error ' Transactions not periodically posted'. This error upon analysing was due to those assets posted with retirements/write-ups (Jan. 09) and mentioned that ASKB needs to be executed for these assets for deparea 10. It's logical that there are no postings on these new accounts for January and the system should not ask them. For example there also are no depreciation postings in area 10 for January and this does not generate any problem. Then, why in ERP, the ASKB for deparea 10 is needed for those related assets?
Also, I tried to process ASKB for deparea 10 to complete, but another error prompted: Message AA001 'Asset 1-177 0 not in company code LX01'. With this error message, I changed the 'Deactivation on' field in the masterdata and tried to rerun ASKB, but still this error exists. Would you know why or how this error could be eliminated?
Kindly help.
Thanks in advance.
jandaph

Hi,
According to the error message, it seems like The asset does not exist in your company code.
Please check again.
Thanks,
Srinu

ASKB - Message error F5800 - Inconsistent currency information

Mrs., I am with a problem when a I execute the transaction ASKB. This message appears in the error log:
Inconsistent currency information
Message no. F5800
Diagnosis
The currency information for the financial accounting component must be transferred fully for each currency type.
If, for example, the sending application sends corporate group currency data to Accounting, this currency data must be transferred for every company code line item.
An error has occurred for line item '000' of the financial accounting document (company code '5557') with currency type '10' (currency key 'BRL'). This could be for one of three reasons:
Line item '000' does not have any currency data for currency type '10', although at least one other line item has currency data for currency type '10'.
Line item '000' contains currency data for currency type '10', although at least one other line item contain no currency data for currency type '10'.
Line item '000' has no currency data for currency type '10', although the currency type '10' corresponds to the local currency ( currency type '10').
System response
Data processing within Financial Accounting can only take place with consistent currency information.
Procedure
The calling application probably contains a system error. Contact the calling application to locate the error.
Somebody knows what can I do to solve this problem?
Tks,
Eliana

Hi Eliana,
Have a look to the Wiki from Markus, this should help you:
/people/markus.bredel/blog/2008/11/28/currencies-in-fixed-asset-accounting

Error While running ASKB

Hi,
I had done one acquisition through ABZON ,when i try to process this through ASKB,i am getting the below error message.
this is infor mation:
Company code XXXX, depreciation area 31, fiscal year 2009, account group 1960
Message no. APERB009
Error:
Internal error in item 0000000000: asset row is not complete
Message no. AAPO191
can any one please help me to resolve this error.

Hi
please check the note 859617.
Blaz
Edited by: Nathan Genez on Sep 23, 2009 7:56 AM

Error in ASKB after creating parallel & delta depreciation area

Hi All,
We have APC and depreciation values in Area 1 for an Asset. Now I have created parallel depreciation area 70 and delta depreciation area 90. area 70 posting to parallel ledger. As soon as I created area 90, the following values are showing in AW01N
01 - Dep Area
APC - $45000
Depreciation - 1500
70 - Depr Area
APC - Null
Depreciation - Null
90 - Dep Area
APC - $45000
Depreciation - 1500
So when I run ASKB it gives me an error saying 'Balancing field in Profit center in line item 001 not filled'. The ledger group it is trying to post is the non-leading ledger.
Can you please help.

Hi Murali & Vinod,
Thanks for your replies. The document splitting settings are fine. It was the issue corss-system depreciation are settings. The client had activated area 70 for an Asset in one company code, but did not have it in the transferred Asset in the other company code. It was an intercompany transfer. We fixed this activating area 70 and now it is ok.
Now the problem is after I run ASKB, and check ABST2, the reconciliation report shows a line item with
Account : 1XXXXXX (Accum. Depr A/c)
Ledger : 3G (non leading ledger)
Period : 999
2ndLCGL :example 1000
2ndLC in AA: 0
2ndLC Delta : 1000
3rdLCGL :example 1000
3rdLC in AA: 0
3rdLC Delta : 1000
Leading ledger postings reconcile properly. Non leading ledger APC values in all 3 currencies reconcile properly. Only for Depr A/c in non-leading ledger it is not posting to LC2 and LC3.
Any thoughts?
Regards
Panneer

ASKB Posting Error

Hi,
We are trying to do Periodic Asset psoting in ASKB in ECC 6.0.
On execution we get this error message "Account xyz does not exist in company code C1".
This chart of depreciation is not configured to revalue so the processing of the programs
should not call the account. How is it possible to do so ?
Thanks,
Pankaj

Hello Paul,
Thanks for getting back on this.
Unfortunately, their is nothing to post to these accounts which is the problem.
It doesn't make sense that the programs are requiring the accounts to be created, and there is no posting to be generated. Once the account is created, the error will go away and nothing will post to the account. We wanted to stay away from that since it causes a bunch of unnecessary account creations.
Is it possible to do so?
Regards,
Pankaj Singh.

ASKB - POsting Period not open problem

Hi All,
I saw many threads on this problem but not got suiatable solution thats why i am raising this thread again.
Due to some problem my client not Run ASKB for October period, now when he is trying to run ASKB for November month he is getting error that 'Posting period is not open'.
Now we cannot open 'Posting period' 'October' because of some organizational issues.
Kindly suggest me how i run ASKB for 'Current month.
Regards
Sandeep

Hi Sandeep,
To my regret, is the answer here is definitely NO.
A reconciliation of the system would be not possible (For example, in foreign currency and a parallel currency).
This source of error was stopped by switching from batch input sessions to the Direct booking with RAPERB2000. (With batch input sessions it was possible to manipulate).
Furthermore, the values in the periodically posting areas have to be posted into the correct period.
If the reconciliation is not relevant, you can check via testrun which values have to be posted and post them via FB01. In this case you have to manipulate also the table TABAS and T093D. But take into acount that this is on your own risk and will not be supported by SAP.
My personal opinion: Open the periods and run the RAPERB2000 regular.
Regards Bernhard
Edited by: Bernhard Kirchner on Nov 29, 2010 12:54 AM

ASKBN error: Posting period Jan is not open

Hi,
We are getting the following error : Posting period Jan 2009 is not open when we do ASKBN.
Can it be resolved without opening period Jan 2009? if we dont resolve it we cannot do AJAB.
But if we open Jan and do ASKBN what could be the financial impact?
Please advise.
Regards,
DP

Hi DP,
I think you have to open the period to post ASKB (or ASKBN)
The financial impact is that it will post from the cost depreciation areas to the general ledger, depending on how the account determination is configured in your system.
Thanks,
Tammy

Error while executing AJAB

Hello,
While executing AJAB transaction we are getting the below error message
Message no. AU075
Diagnosis
In company code, which is to be closed, APC values have not been posted to Financial Accounting for all relevant depreciation areas.
Depreciation area 30, at least, is set up for periodic posting of APC values.
The year-end closing checks if documents were posted that have an entry date after the last run of the program for periodic posting of APC values. If such documents are found, the system issues this message.
Procedure
Check which depreciation areas are supposed to post APC values periodically to Financial Accounting according to their Customizing definitions (indicator: "Post assets periodically in General Ledger")
See the Define How Depreciation Areas Post to General Ledger IMG activity.
Start the program for posting APC values. In the Asset Accounting main menu, choose Periodic processing. Start this program in update mode, regardless of whether or not documents are displayed in test mode, or if a message appears stating that there are no documents to be posted.
Start APC Posting Program
According tho the error message it is instruction to execute APC posting program. Transaction-ASKB. But i am not sure for what the tranaction is used and what would be its implication.
Please can someone explain me the same and how to solve the above error.
BR,
Zulfikar

Hello,
Thanks for your explanation. One small question.
Will there be any figures posted when I execute ASKB? since i am not allowed to make posting in 2007.
Also i have executed ASKB in our sandbox it executed successfully and when i check in SM37 it is giving me below message.
Data statistics Number of
Records passed 0
Status Acct.det-No Data.
BR,
Zulfikar

Posting of retirement/transfer not possible(error in asset)

Hi All,
this is regarding intra company asset transfer through transaction code ABUMN. The issue is like below :
Let's say asset code is 764 in 111 asset class & i am transferring this asset to 3615 in 112 asset class through ABUMN.
Actaully in 2004, a part of the asset value has already been retired with scrap.So now the requirement is complete transfer the remaining amount. So while trasfer, the error shows and not allowing to post the transaction.
There are several depreciation areas in the asset. The depreciation has been calculated for all the dep. area except 42(for US)
As this book has pending the dep. since 2004, system doesn't allow to trasfer this asset. For this purpose, i have tried AFAR, ASKB but the issue is not solved.
Kindly revert back with your valuable suggestions.
Thanks,
Raj

Hi Raj,
In most cases AA 465 is due to recalculation errors in the past on the asset in question. From your information I assume this is probaby due to depreciation area 42.
I do not know how you were able to close all following fiscal years if errors existed
on the assets with pending depreciation since 2004.
As you known, the indicator ANLC-XAFAR gives the information about errors in the calculation of depreciation.
0 No error occurred during depreciation calculation
1 Error occurred in depreciation calculation from previous yrs
2 Error occurred in depreciation calculation of current year
At this point it may be necessary to execute the report RACORR52 for the fiscal years
that may be closed now and for which the asset in question seems to have an incorrect entry for ANLC-XAFAR. You have to carefully check the asset beforehand though, to be sure that the values on the asset as such are correct as per your expectation. Only then should you consider using the correction report RACORR52.
Please review the attached note in this regard, and follow the instructions given:
103749     -   RAJABS00: Error message AU069
This report is not in your system until you manually apply this source code.
Also review SAP note 141656 as it might help, too.
I hope this information helps you further.
Kind regards,
Brigitte

Year ending closing ASKB

Hi,
Please suggest to me for below given issue.
As per business requirement, we need open new FY2012 and close the old FY2010 and we trying to close the FY2010 in AJAB but system through the error message as u201CTransactions not complete ly periodically posted u201C( message no : AU075),
As per this error message system show the procedure as
1.Check which depreciation areas are supposed to post APC values periodically to Financial Accounting according to their Customizing definitions (indicator: "Post assets periodically in General Ledger")
See the Define How Depreciation Areas Post to General Ledger IMG activity.
2.Start the program for posting APC values. In the Asset Accounting main menu, choose Periodic processing. Start this program in update mode, regardless of whether or not documents are displayed in test mode, or if a message appears stating that there are no documents to be posted.
Start APC Posting Program
As per second step we run the periodic asset postings in AKSB, while running this postings system through the error message as u201CPosting periods 2010 not openu201D and we suggest to business need to open 2010 periods, they are asking once we reopen that period FY 2010 what about FY 2010 result values.
So please suggest to me on urgent basis.
Many thanks in advance for your valuable suggestions

It seems that if you reopen FY10 and run ASKB in live mode you will get postings - and hopefully the postings will net to zero but probably not. Running the test mode should tell you what the outcome would be, accounting wise.
If you do this, chances are that you would also need to rerun AFAR and AFAB depending on whatever comes through ASKB to completed asset records. Again, analyzing ASKB test mode data will tell you whether a depreciation REPEAT would be needed.
If your FY10 g/l has already been audited, or FY11 has already been audited, then you might consider booking journal entry in FY11 (that will reverse in FY12) moving the accounting impact to a year that has not been audited yet. This type of entry is usually referred to as an adjusting entry that defers accounting recognition. I just call it a deferral which is the opposite of an accrual. Hopefully the magnitude of the accounting is not material in the eyes of your auditor.
1) add ASKB to your end of year routines
2) you forgot to close FY10 until you were reminded when you tried to open FY12, as only two fiscal years can be open at same time
Regards

ASKB Error

Similar Messages

Maybe you are looking for