Please check the below for error resolution:
1. Error in RAEWUS1A
For this error category, only refer to the error note from the long text and carry out the procedure detailed there.Use the documentation in case of doubt.
If the affected company code is a test company code, you may either reset the data of the company code and delete the assignment to the chart of depreciation or change the currency of the company code and the depreciation areas to a table that is not affected by local currency changeover.
Note also that you can only exit the program without errors if the current fiscal year in Asset Accounting corresponds to the year of changeover.That is, it is checked whether the year T093C-LGJAHR (corresponding to the current fiscal year) equals the fiscal year determined via the system date and the fiscal year variant.
If you want to test the local currency changeover to be dealt with in the next year and you are in the last month of your fiscal year, you have two possibilities to test the changeover:
Test in the current fiscal year
Set up your test system from productive data before you carry out the fiscal year change in production system.In the test system, you must in no case carry out the fiscal year change afterwards.Generate your own changeover package for the current fiscal year.
Test in the next fiscal year
You can only carry out the analysis in the next fiscal year, that is, if the system date is in the next fiscal year!
2. Error in RAEWUAFA (MQ563)
You can use Transaction AIAB to display the total of the open items on an asset.It should be possible to reconcile this total with the accumulated values on the asset.An incorrect reconciliation can have the following reasons (see also the long text of the error message).
a) During R/2 - R/3 migration, not all open or cleared items of the current year were migrated (see also R/2 Note 72848).
b) Incorrect legacy data transfer:items already existed before legacy data transfer.
c) For reversal transactions, it is not noted in all items that they are cleared.
d) Incorrect cumulative values, because the items were not added correctly to the cumulative values.
In cases a) and b) set the clearing information (ANEP-AUGLN) or set up a new item or delete an item with the support of your consultant and in case c) ask the support team. In the case of d), use the correction programs from Note 322988.
3. Error in RAEWUC1B (MQ555)
Analyzing the error with report RFEWSBAL and source modification AS.(Branching from the error message is possible).
The accounts in the list must now be examined.The following procedure is recommended by SAP:(you can change the sequence).
a) Compare the last two fiscal years for the affected account with the balances display (FS10) in G/L accounting.If the closing balance and the opening balance are different, the balance carry forward program (SAPF011) must be started again for the current year.
b) Create two asset history sheets for the accounts affected.For performance reasons, you are recommended to restrict by account assignment or by asset classes.Enter 0020 as the sort version, the year-end of the previous year and the year-end of the current year as the report date and activate 'Posted depreciation'.If the opening and closing values of the asset history sheet are different, the fiscal year change should be repeated.If the opening and closing value differ after the fiscal year change, you should examine whether a fixed asset with capitalization date exists for which acquisition dates are missing.
Note that down payments and acquisition values are shown together in the asset history sheet while there are normally different reconciliation accounts for it.
An incremental takeover may be present and the accounts are not reconciled correctly.
c) The asset history sheet for the previous year does not agree if you cross-check the values.In this case, RAABST01 should be started for the account affected.If the balance carried forward is affected, the year-end closing must now be cancelled, a depreciation recalculation must be carried out, a depreciation posting may need to be carried out and the year-end must be closed again.
d) The opening balance values of the current year do not match the value of the balance display. There may be a variety of reasons for this.
The error occurs only on the business area level.In Financial Accounting in the previous year, you must post a transfer between the business areas directly to the account using ABF1/FB01.For the differences refer to RFEWSBAL.There is only a problem if there are values on the account for business areas for which there are no longer any assets.You can use these business areas as an offsetting account assignment for the differences. You can make the postings in same way as for Note 69225. As an alternative, you can deactivate the business area balance sheets. You can choose this solution if you activated the balance sheets by mistake.Upto now you did not reconcile FI-AA and FI-GL at business area level either.
Incorrect legacy data transfer:if there already exist differences in the year of the legacy data transfer, the differences must also be written off on the G/L account in the previous year. Refer also to Note 69225. This error occurs especially when a local currency changeover is performed directly in the year of a mid-year legacy data transfer and the balance values of Asset Accounting were not posted at the beginning of the year, that is, on December 31 but on the key date of legacy data transfer to the general ledger.You encounter this error when the system displays pairs of entries in the list for the balance carried forward (period is blank) and for the key date (period 999).
The problem also occurs if you manage reserves for special depreciation and have not reconciled the reserve for special depreciation balance sheet account during transfer or migration.
RAABST01 finds missing line items - these must be regenerated using RACORR05.
The account was posted manually.You can see this using the line item display of the account.These manual postings must be reversed.If necessary, a separate account that is not posted to by FI-AA must be created.(Also refer to Note 69225 - however, the adjustment posting has to be entered in the previous year.)
Account is an accumulated depreciation account:depreciation was reset by program during the fiscal year or fixed assets were deleted but depreciation had already been posted.Correct the values in the general ledger in the previous year (see Note 69225).
Account is not a reconciliation account of Asset Accounting:contact an SAP consultant. A serious Customizing error exists.However, this only applies to depreciation areas posting online.Customizing can be checked with the report RACKONT1 or via the IMG:'Preparations for productive operation --> Check consistency --> Assets: Report for G/L accounts'.
Start RAHAFA01 for the account with indicator 'Display special dep.If accumulated depreciations exist for different depreciation types (for example, normal or special depreciation, transfers of reserves), check whether accounts for these depreciation types are entered in the corresponding account assignment. If not, maintain the accounts.
4. Error in RAEWUC1B (MQ557).
a) Create an asset history sheet for the affected accounts.For performance reasons, you are recommended to restrict by account assignment or by asset classes.Enter 0020 as the sort version, the year-end of the current year as the report date and activate 'Posted depreciation'.
History sheet for the current year does not agree if you cross-check the values.In this case, RAABST01 should be started for the account affected.For incorrect fixed assets a depreciation recalculation should be executed.
History sheet for single values and total values does not fit.In most cases the reason is a fixed asset without acquisition date.
b) The key date values do not match the value of the balance display.There may be a variety of reasons for this.
The error occurs only on the business area level.In Financial Accounting you must post a transfer between the business areas directly to the account using ABF1/FB01 or reverse the original document.
RAABST01 finds missing line items - these must be regenerated using RACORR05.
The account was posted manually.You can see this using the line item display of the account.These manual postings must be reversed.It may be necessary for you to create a separate account which is not posted to by FI-AA and post the difference amount to this account.
Please don't forget to award me points.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.