SAP Asset Data Migration

Before performing asset data migration, there are some prerequisites regarding the project type and/or Go live date (migration during or at the end of the fiscal year) that should be fulfilled. 7 mandatory steps are to be considered like following:

1- Asset Setting

The first prerequisite is the asset setting on the target system. This step will be different if it is an implementation or a roll out project.

Depending on whether if it is implementation or roll out project, setting to perform will be different like in the figure below:

2- Extraction

Data cleansing and extractions should be done in the source system according to the asset file format.

3- Data migration setting

Before doing data injection, there are some data migration setting to perform.

Depending on whether if it concerns data migration at the end or during fiscal year, setting will be a little different little like in the figure below:

The takeover date should be entered in the system. Below is an example of a migration during fiscal year.

Another setting should be done when the migration is during the fiscal year. The period until which depreciation will be posted should be maintained like below:

4- Asset data file

To be able to perform data transfer, a medium file should be defined. This medium file depends on the chosen program to perform asset data migration. Many possibilities exist. In this example, we choose an LSMW based on the program RAALTD11. The program RAALTD11 contains two structures:

BALTD Structure: For Master data fields and Depreciation areas data

BALTB Structure : For Asset movements occurred if the migration take place during the fiscal year

A- BALTD Structure:

As explained above, the BALTD structure will allow to collect Asset master data and depreciation area data.

Below, some of the fields available for data transfer in BALTD structure. The last part from AFABEXX to AAFAGXX will contains the depreciation area data.

Depending on whether if data migration happens at the end or during fiscal year, field relance will change. for example, fields OLDN1, OLDN2 & BWCNT will be important to do make the link with BALTB structure.

NB: If in your system you have 5 areas you should fill the medium file with data form each area like below:

B- BALTB Structure:

As explained above, the BALTB structure will allow to collect Asset Movements data. it is only relevant if your migration happens during the fiscal year. Below the proposed field in this structure.

NB:If in your system you have 5 areas you should fill the medium file with data form each area like below:

Exemple of a file for end year data migration

5- Injection

A- File format for migration during fiscal year:

This represents two assets; one with capitalization before 2023 and another one with capitalization in 2023.

Asset 1: Asset with capitalization prior current fiscal year

Following fields should be controlled for Asset with capitalization prior current fiscal year:

BALTD-KANSWXX: Acquisition value transfer (capitalization prior 2023)

BALTD-KNAFAXX: Depreciation cumulative amount until 31.12.2023 (prior 2023)

BALTD-NAFAGXX: Depreciation from 01.01.2023 until takeover date (date in data migration setting). in our example 30.09.2023.

Asset 2: Asset with capitalization during fiscal year

Following fields should be controlled for Asset with capitalization during fiscal year:

BALTD-NAFAGXX: Depreciation from 01.01.2023 until takeover date (date in data migration setting). in our example 30.09.2023.

BALTB-ANBTRXX: Transaction amount

B- LSMW Properties

Structure relations

Field mapping

File specification

C- Data injection

After LSMW Successful run, here are the result for each case:

Asset 1: Asset with capitalization prior current fiscal year

Display asset and check asset values

BALTD-KANSWXX: Acquisition value transfer & BALTD-KNAFAXX: Depreciation cumulative amount until 31.12.2023 are like expected (file data)

BALTD-NAFAGXX: Depreciation from 01.01.2023 until takeover date is like expected as per the file.

The asset explorer shows data like expected. Asset data migration is done successfully

Asset 2: Asset with capitalization during fiscal year

Display asset and check asset values

BALTD-KANSWXX: Acquisition value transfer & BALTD-KNAFAXX: Depreciation cumulative amount until 31.12.2023?are not applicable (Capitalisation date is 01012023)

BALTD-NAFAGXX: Depreciation from 01.01.2023 until takeover date is like expected as per the file.

BALTB-ANBTRXX: Transaction amount

The asset explorer shows data like expected. Asset data migration is done successfully

6- Asset accounts balances posting

In order to finish Asset data migration, the last step is to upload the Asset accounts balances. In this step, a mass usually a mass posting is done with an LSMW or else.

To do this, some prerequisites are mandatory. Like below, Asset reconciliation accounts should be changed to allow direct posting and of course accounting periods should be opened.

Below AOMK Screenshot where is it required to change Asset reconciliation setting

Mass Posting can be done based on an LSMW using program below

7- Data check

Once previous step performed, reconciliation between FIAA an G/L Asset account should be controlled. The Tcode ABST2 should be launched for the concerned company code.

Below ABST2 screenshot of slection screen. As visible on the screen a log of data analysed is displayed on the popup.

After the analysis, if the transaction shows a delta between FIAA and G/L Asset accounts like screenshot below, it means that there is a discrepancy in asset data.

This delta should be analyzed, and the gaps must be justified.

Good to know:?If analysis is hard to perform and errors in asset data file are suspected, SAP offers very helpful tools allowing to reset data and restart form beginning.

Conclusion

If the reconciliation between FIAA and G/L Asset Accounts is OK or justified, that means that the Asset Migration is successful, and the system is ready for the very first depreciation run!