How to Reconcile Asset Legacy data with SAP uploaded data

[Former Member]

Dear,

Now we are doing Asset Implementation for our Indian client.

We have uploaded Asset Legacy Data in our SAP system.

We have checked uploaded data compare with ANLC table.

But in user point of view, it is not possible to view in SAP table wise.

We have checked in t.code S_ALR_87011963 - ... by Asset Number, in this t.code Acquisition Value is showing Legacy value. But Accumulated Depreciation Value and Book Value is showing differently.

LSMW file - we have put value for Accumulated Depreciation Posted upto 2012 (for India upto March 2013) as in SAP AS91 field we used ANBTR01_06 and Value for Current Year Depreciation posted upto July 2013 (for India April 2013 to July 2013) in SAP AS91 field we used ANBTR01_16.

This both uploaded values only mismatching in the above Report t.code.

Can any one suggest in which t.code & report we have to check in user point of view for reconcile of Asset Legacy Data and SAP uploaded data?

Regards,

M.Mohan.

[former_member188028 · Accepted solution]

Please check AR01 or AR02

[Former Member · Accepted solution]

Dear Murali and Ajay,

I got one OSS Note which is related for Reconciliation of Legacy Data and SAP Uploaded data. Please find below.

Note No. Note 1566099 - Reporting in Asset Accounting

Symptom

You call a standard report in Asset Accounting. Depending on the selection criteria, you get the planned depreciation and the posted depreciation in the following reports:

1. Standard asset reports with planned or posted depreciation

2. Selection of asset line items (transactions) in reporting

3. Report RABEST_ALV01 ("Asset Balances")

4. Report RAGITT_ALV01 ("Asset History Sheet")

5. Report RAITAR01 ("Asset Register (Italy)")

6. Report RASIMU02 / RASIMU_ALV01 ("Depreciation Simulation" in Asset Accounting)

7. Transaction data reports

• Report RAZUGA_ALV01 (acquisition list)

• Report RAABGA_ALV01 (retirement list)

• Report RABEWG_ALV01 (transaction data report)

8. Query reports

9. Reporting with time-dependent depreciation terms (table ANLBZA)

10. Changed interface for the SAP List Viewer (ALV display)

11. Custom selection and ALV list

12. Reporting with the selection ".... or main numbers only"

13. Translation method

14. Reporting with selection in value fields

15. Authorization concept for Information System

16. Other explanatory notes

Other termsReporting
Solution

1. Standard asset reports with planned or posted depreciation

In a standard asset report (RABEST_ALV01, RAGITT_ALV01, and so on), you can create a report with the asset values from the planned depreciation or from the posted depreciation. The depreciation is recalculated depending on the report date and read directly from the database (table ANLC).

a) Planned depreciation

Report date at fiscal year end

The report date is in the past or in the current fiscal year.

The planned asset values are saved per depreciation area and per fiscal year in the table ANLC. The asset values (acquisition and production costs, planned depreciations, and so on) are read directly from the database. It is not necessary to recalculate the depreciation at this point.

In past reports, the system uses the report date to determine whether it should access the online database or an archive file.

The fiscal year is in the future.

In this case, the fiscal year change is simulated resulting from the current fiscal year until the fiscal year of the report date is reached. The current fiscal year is always the year for which the fiscal year change was last performed.

Mid-year report date

A standard asset report with a mid-year report date (report date at the end of the period) is called in the open fiscal years.

• A reconciliation between Asset Accounting (for example, asset history sheet) and financial accounting is not possible because the depreciation is always recalculated with the current depreciation terms in Asset Accounting.

• In the mid-year asset report (with a report date at the fiscal year end or before it), the depreciation or net book value may have different results in the historical calculation and in the current calculation on the report date.  This is due to the asset-related depreciation terms that may have been changed; for example, the depreciation key, the useful life, and so on.

• Mid-year report date in closed fiscal years
  
  See the special functions from SAP Note 1433686.

• It is not possible to report on archived fiscal years with a mid-year report date.

b) Posted depreciation

Report date at fiscal year end

See the section about a report date at the fiscal year end for planned depreciation. In this case, the posted depreciation is read directly from the database (table ANLC) instead of the planned depreciation.

Mid-year report date

In each case, these reports can be performed only on the last day of the period of the last depreciation posting run (or of a subsequent period) in the current fiscal year. It is not possible to report on the posted depreciation with a report date before the last depreciation run (error message AU 115).

Report for multiple company codes
If you call a report for multiple company codes, the conditions mentioned above (depreciation posted to period) must be met in all company codes.

There is still no posted depreciation for the selected company code.
If there is still no posted depreciation in a company code for the selected fiscal year, the system always takes the last date in the fiscal year as the last posting date. In this case, if you specify a report date before the last date of the fiscal year, the system issues error message AU 115.

Retroactive report with posted depreciation

If you still want to generate a retroactive report with posted depreciation (for reconciliation purposes), you can archive a created asset history sheet with posted depreciation before a posting period closes, where you can always access the archived asset history sheet for the required posting period.

or

If you have integrated BW, you can extract the posted values to BW, where you can then start subsequent reports from BW.

2. Selection of asset line items (transactions) in reporting

SAP Note 46973 ("Document: Posting date instead of asset value date") describes which asset line items (transactions) should be selected in the reports (for example, RABEST_ALV01, RAGITT_ALV01, and so on).

3. Report RABEST_ALV01 ("Asset Balances")

The following asset values are displayed in the report up to the specified report date with or without the "Current book value" indicator set:

Acquisition and production costs
Planned depreciation and posted depreciation
Planned book value and current book value (determined from posted depreciation)

Current book value
If the "Current book value" indicator is set and the report date is during the fiscal year, see the restrictions under the following points:

-> Posted depreciation
-> Mid-year report date

4. Report RAGITT_ALV01 ("Asset History Sheet")

Report RAGITT01 (ALV list) and report RAGITT01 (ABAP list) are for setting up an asset history sheet according to country-specific legal requirements (for example, the German Accounting Directives Act) and for creating other reports (which can be freely defined in Asset Customizing) regarding asset transactions.  The most important parameter when starting the report is the asset history sheet version. The asset history sheet version determines the form and content of the report.

When you call the asset history sheet, the system checks whether the definition of the history sheet version is complete. The history sheet version is complete when all value categories (asset balances, value adjustments, depreciation, and so on) have been assigned to a cell in the history sheet version.  If the history sheet version you are using is not complete, you should check the Customizing definition of the history sheet version and of the transaction types that belong to it.

Note:
The system determines whether the history sheet version is complete based on Customizing definitions (especially the defined transaction types). Therefore it is possible that even standard history sheet versions supplied by SAP can be incomplete by this definition.

Output list: Report RAGITT_ALV01 (List Viewer - ALV list); report RAGITT01 (ABAP list).

You can freely define line and column structure in the asset history sheet (for more information, see the Implementation Guide). SAP delivers country-specific versions of the asset history sheet, which satisfy the legal requirements of the given country (for example, the 4th EC directive).  Additional history sheet versions are also available (for example, for displaying the development of reserves for special depreciation).

Due to the selection criteria in the further settings:

"History sheet version"
to display posted depreciation instead of planned depreciation,

the display in the standard output is formatted according to the asset values and displayed in three display areas in an ABAP list (report RAGITT01) or in an ALV list (report RAGITT_ALV01).

Display area: Fiscal Year Start:
This display area in the list contains the cumulated asset values (acquisition and production costs, depreciation and calculated book value) at the fiscal year start.

Display area: Non-***. Value Changes:
This display area in the list contains all non-***. value changes (acquisitions, retirements, intracompany transfers, proportional depreciations, and so on) for the selected fiscal year. The asset values are distributed here according to the control from the transaction type group of the transactions (tables ANEP and ANEA) and the depreciation for the year is processed.

Display of the depreciation for the year
If the "Posted Depreciation" indicator is set and the report date is during the fiscal year, see the restrictions under the following points:

-> Posted depreciation
-> Mid-year report date

Display area: Fiscal Year End

This display area of the list contains the accumulated asset values at the fiscal year end.

IMPORTANT:
If there was a difference between the query total (resulting from the asset values at the fiscal year start plus balance changes of the current fiscal year) and the fiscal year end, transaction type groups (history sheet group) were not assigned to the asset history sheet version or were assigned incorrectly. You can control the asset history sheet versions using transaction OA79.

5. Report RAITAR01 ("Asset Register (Italy)")

The asset register is a report required by law in Italy. The asset register must display all transactions, such as acquisitions, retirements, transfers, depreciation and revaluation.

The Italian asset register has to be printed according to special sort criteria (location, year, description, license plate number).  You can define the sort sequence in FI-AA Customizing.

Example:
Machines have to be sorted and totaled by year; buildings have to be sorted by location and year; vehicles have to be identified individually and sorted by year and license plate number, and so on. There is a concrete example for this below. If the asset was revalued, the data relating to the revaluation is displayed in a separate section.

You must enter all the relevant depreciation areas (for example,  '01' for book depreciation and '71' for revaluation in 2010).

Note:
Note the following functions for the report:

• The "List assets" function (indicator in the report selection screen) is not available in this report.
  
  According to the settings in Customizing for the Italian asset register, the asset values are totaled according to the grouping, and displayed in the list.
  
  In Customizing for the asset register, you have indicated all fields for grouping:
  
  CoCode        1111
  Acct.det        2222222
  Asset class        3333333
  Location              X
  Asset text          X
  Indicator          X
  Print acquis. year   X
  
  The asset values are totaled according to these sort levels, and displayed in the list.
  
  Example:
  
  The assets 4711 to 4713 have the same evaluation group "Location, Asset text, Indicator" from defined Customizing. The asset values are totaled here and displayed as group totals. In addition, the last asset number of this group is listed as information.
  
  ---------------------------------------------------------
  Asset  Asset text  Location  Indicator  APC  Acquisition
  ---------------------------------------------------------
  4711    Test         -        -            5000  200
  4712    Test        -        -            2000  500
  4713    Test        -        -            3000  300
  ---------------------------------------------------------
                                            10000 1000
  
  List output:

• ----------------------------------------------------------
                APC FY start   Acquis.  APC FY end        ...
  ----------------------------------------------------------
  Year:2010 - Asst.No: 4713-0 Desc.: Test - % O-dep:  ...
  Book depreciation    10000        1000    11000              ...
  ----------------------------------------------------------
  Asset class   3100            Vehicles              ...
  ----------------------------------------------------------
                 10000        1000    11000              ...
  ----------------------------------------------------------

• The only sort versions that are allowed are those that contain the company code and the asset class, and only contain fields, and do not involve a finer sorting than defined in Customizing for the Italian asset register.
  
  We propose the standard sort version 0009.

• For more information about the Italian asset history sheet, see the following SAP Notes:
  
  SAP Note:
  70118  RAITAR01:  options in selection screen
  70212  Asset register (Italy):  sort versions

6. Report RASIMU02 / RASIMU_ALV01 ("Depreciation Simulation" in Asset Accounting)

This is a report for the simulation of future depreciation (fixed assets and/or planned investments). The report date determines the future fiscal year, up to which the simulation should be carried out.

• Simulation in the future
  
  When you specify a report date in the future, a fiscal year change (carry forward the accumulated value and recalculate the depreciation) is simulated until the fiscal year to be evaluated (determined from the report date) is reached.
  
  Evaluation period "Fiscal year"
  
  In the report, the simulated annual values are in the individual columns based on the year.
  
  Evaluation period "Month/Quarter/Half year"
  
  When the simulation is for a time period of less than one fiscal year (evaluation period "Month/Quarter/Half year"), then the report date specifies the fiscal year in which this simulation takes place. The simulation supplies values for all months/quarters/half years up to and including the period in which the report date lies.

• Simulation in the current fiscal year
  
  When you call a depreciation simulation in the current fiscal year, see the description in SAP Note 1243806 for more information. The SAP Note describes which depreciation (posted or simulated) is displayed in the individual reporting period "month/quarter/half year".
  
  A simulation for the depreciation to be posted is determined here for each reporting period "month/quarter/half year" (in the same way as for the report RAPOST2000 - "Depreciation Posting Run").
  
  If you specify a report date before the last posted depreciation run, depreciations that were already posted may be undone (depreciation is positive).

• Simulation versions and substitutions
  
  In addition to the simulation rules in table form, you can also specify a substitution rule for the simulation of the depreciation term here.
  
  The variants contain alternative depreciation terms for the valuation of the assets (depreciation key, useful life, and so on). These can be specified when the asset report is called. In this way, it is possible to determine the depreciation values on the basis of a simulated exchange of the valuation rules.

• New report RASIMU_ALV01
  
  As of Release 605, the new report RASIMU_ALV01 is created. In the new report RASIMU_ALV01, it is possible (in the same way as in the report RABEST_ALV01, and so on) to include additional selection criteria (for example, sort version) in the selection menu.

• SAP Note 815513
  For further information on depreciation simulation and primary cost planning for depreciations or interest, see SAP Note 815513.

7. Transaction data reports

Report RAZUGA_ALV01 (acquisition list)

The report displays all acquisition documents in a fiscal year per asset.  The following asset values are displayed for each document:

The acquired APC
The acquired quantity
The planned ordinary and special depreciation for the acquisition

Report RAABGA_ALV01 (retirement list)

The report displays, per asset, the retirement documents in the fiscal year.  Each document shows the

Retired acquisition and production costs
Retired quantity
Retired proportional depreciation
Earned revenue
Gain/loss
Possible retirement costs

However, the retirement costs have no affect on the gain or loss. Retirement costs are independent of gain or loss in this report, and are displayed for statistical purposes only.

Report RABEWG_ALV01 (transaction data report)

The report displays all transactions in a fiscal year by asset.   For each document, the report shows:

The change to the acquisition and production costs
The change to the value adjustments
The ordinary and special depreciation planned for this transaction

Important:

Write-ups are displayed in the "Value adjustments" column because they reduce the value adjustments for previous years.

In contrast, unplanned depreciation is displayed in the "Acquisition and production costs" column because the "Depreciation" column reserves the depreciation for the accrued transaction (that is, ordinary and special depreciation) and the proportional accumulated depreciation for retirements and intracompany transfers and write-ups that is being retired or acquired is managed under the "Value adjustments" column.

8. Query reports

In addition to the standard SAP reports, there are also query reports created by SAP under the user group "/SAPQUERY/AM". Some of the queries access the logical database "ADA" (for example, physical inventory list, and so on) or access a table directly (for example, ANLP for posted depreciation).

9. Reporting with time-dependent depreciation terms (table ANLBZA)

• SAP Note 1366920 integrated the time-dependent depreciation terms (table ANLBZA) into reporting. To be able to use the function, you must implement the program corrections in SAP Note 1366920.

• Due to the integration of SAP Notes 1519278 and 1564907, it is possible to define a substitution for time-dependent depreciation terms in a simulation version.

• SAP Note 1564004 also ensures that a validation of the time-dependent depreciation term is taken into account.

10. Changed interface for the SAP List Viewer (ALV display)

SAP Note 1496486 revised the "ALV Display" data interface for the reports:

RABEST_ALV01 (asset list)
RAGITT_ALV1 (asset history sheet)
RABEWG_ALV01 (transaction data report)



SAP Note 1496486 describes all recalculations.

11. Custom selection and ALV list

SAP Note 1652972 transfers the fields from the selection "Custom selection" to the SAP List Viewer (ALV list).
This function is described in SAP Note 1652972.

12. Reporting with the selection ".... or main numbers only"

You call the report RABEST_ALV01 (asset list) or RAGITT-ALV01 (asset history sheet) with the option "... or group totals only", for example. In this case, the results between the reports may be inexact:

- Individual list (list for each asset subnumber)
- Main asset number (totaling for each main number)
- Group total according to sort levels



If, for example, a main asset number (with the subnumber 0) is already deactivated, all asset subnumbers belonging to it are ignored even though some of the subnumbers are still active.

When you select a derived depreciation area, the results are sometimes incorrect if there are transactions with restrictions on depreciation areas (see standard preliminary correction (SPC) note 1580650).

Solution:

A good solution is a separate sort version, where the lowest sort level is the asset number (field name ANLN1) and the report is executed with the function to create group totals only.

For this reason, this option is not provided for the reports RABEWG_ALV01 (transaction data report), RAZUGA_ALV01 (acquisition list), RAABGA_ALV01 (retirement list) and RAUMBU_ALV01 (intracompany transfer list).

13. Translation method

In Customizing, you maintained translation methods in Asset Accounting using transaction OAW3 (translation method, currency, exchange rate types, and so on).

Using the translation method, the values can be calculated in a different currency in the standard reports of Asset Accounting (for example, RAGITT_ALV01, RASIMU02, and so on).

For this purpose, the translation method determines:

With which exchange rate type (average rate, bank selling rate, buying rate, and so on)
Into which currency and when the translation should occur

14. Reporting with selection in value fields

You call, for example, the report RABEST_ALV01 (asset list) with the following selection criteria:

- Settings: ... or group totals only.
- Further selections: Acquisition value, Accumulated depreciation or Book value.

SAP Note 62285 ("Different results for individual/totals lists") describes why the results are different in the individual list and the totals list.

Solution proposal

• You call the report with the settings:
  "List assets"
  without the ALV grid control and further selections (for example, selected book value =1)

• To see only the totals list, you must perform the following steps in the display of the ALV list:
  Choose "Settings"
  -> Summation levels
  -> Define breakdown
  -> "Sum Steps: Specify Breakdown" dialog box
  -> Select the required summation level.

• The ALV list displays the totals lines of the required level.

• Save this layout to ensure that you can access these display variants later (even as a background job).

• Large datasets can no longer be executed in the online operation
  In the case of a large dataset, it is advisable to execute the report for a small quantity and save the layout as described. Then call the report with the saved display variants again as a background job. In the spool list, only the totals lines are now displayed.

15. Authorization concept for Information System

              See SAP Notes 141876 and 1491612.

       16. Other explanatory notes

1. 115859    Logical database ADA / group totals option
2. 335065    Include user-defined fields in reports
3. 372724    Maintenance of report variants
4. 377686    Modifying the area menu for Information System FIAA
5. 439407    User field integration in dynamic selections
6. 540785    FAQ note:Reporting of Asset Accounting
7. 917786    Reporting: Account determination

[former_member188028]

Hi Mohan,

Thank you very much for the update.

Rgds

Murali. N

[ajaycwa1981]

Hi

If it is really mismatching, why dont you upload it again and check

Do this for one  single asset and reconcile 1st.. I prefer table ANLC.. You can use the report that you are currently using

Br, Ajay M

[Former Member]

Thanks Ajay.

I have found the difference about Legacy & SAP. The reason is user has given Legacy Data with wrong value for the Depreciation of Current Year. This is the reason we got difference between them.

For example, Accum. Depn for the whole current year 2013 is 650 only. But user has given Acc.Depn. Value for April 2013 to July 2013 as 817 (for 4 months). Like this So system is showing difference.

So, as per my understanding we can use t.code S_ALR_87011963 for reconcile of Legacy data & SAP uploaded data and also we can use AR02 t.code.

Regards,

M.Mohan.