Technical Articles
SAP S/4HANA Fixed Asset Legacy Data Migration
Introduction
As an introduction, I would like to highlight this blog is for fixed asset legacy data migration in S/4HANA (and not for conversion). There are many contents available online for SAP Fixed Asset Legacy Data migration, and this could be one of it. But in this blog, I would like to touch upon multiple points which I was looking before starting fixed asset legacy data migration in S/4HANA. Instead of duplicating details, I have provided link to the content wherever applicable. Please note details provided here are relevant for S/4HANA 2020 version and may or may not be valid for other versions.
Important configuration for Fixed Asset Legacy Data Migration
Configuration related to Fixed Asset Legacy Data migration in S/4HANA can be set using path ‘SAP Customizing Implementation Guide –> Financial Accounting –> Asset Accounting –> Asset Data Transfer –> Parameters for Data Transfer’, predominately company code status, transfer date, transfer status, document type, offsetting account and transaction types.
| # | Configuration | Accounting Entries |
| 1 | Define Transfer Date and Additional Parameters |
|
| 2 | Specify Offsetting Account for Legacy Data Transfer | Mention offsetting account for transferring the asset balances. This GL account will be used for asset data migration. |
| 3 | Define Transaction Types for Transfer of Open Items | Define transaction types for the takeover of open items from a previous system. If you do not have any assets under construction with line-item management, you do not need this kind of transaction type. |
Alternatively, configuration can also be set using procedure described in the BH5 test script (Link) on SAP Best Practices Explorer.
Key Accounting Entries
Below example accounting entries are posted at time of fixed asset legacy data migration: –
| # | Scenario Applicable | Transactions | Accounting Entries |
| 1 | Year-end migration and Mid-year migration | Previous year accumulated Values |
Dr. Accumulated Acquisition Cr. Accumulated Dep. Cr. Offsetting/Takeon Account
|
| 2 | Mid-year migration | Current year Dep. |
Dr. Offsetting/Takeon Account Cr. Accumulated Dep.
|
| 3 | Mid-year migration | Current year Acquisition or additions |
Dr. Accumulated Acquisition Cr. Offsetting/Takeon Account
|
| 4 | Mid-year migration | Current year Retirements |
Dr. Offsetting/Takeon Account Dr. Accumulated Dep. Cr. Accumulated Acquisition
|
Fixed Asset Legacy Data Migration options
With S/4HANA, SAP has improved data migration by providing S/4HANA migration cockpit tool. However, Legacy System Migration Workbench (LSMW) and transaction code AS100 is also available in S/4HANA. Please find below further details for S/4HANA migration cockpit and LSMW: –
S/4HANA migration cockpit
S/4HANA migration cockpit has provided multiple Migration Objects (click link to access latest/full list). Migration Object Fixed asset (incl. balances and transactions) is used for migrating fixed asset master data and transactional data. SAP has provided standard template for uploading master data and balance. Below is detail of some of the important tabs and fields in upload format: –
| Sr. No. | Tab | Comment |
| 1 | Master Details (mandatory) |
This worksheet/tab hold important information for creation of the assets. Some of the fields are Asset number, sub-number, asset class, description, etc.
|
| 2 | Posting Information | Asset Capitalization Date field is provided in this worksheet/tab. |
| 3 | Time-Dependent Data | Time dependent data like cost center, WBS, plant, etc. are part of this worksheet/tab. |
| 4 | Allocations | This worksheet/tab hold information like evaluation group, sort key, etc. |
| 5 | Depreciation Areas |
Details like depreciation (dep.) area, dep. Key, useful life, dep. Start date, etc. can be updated here. In case there are multiple dep. area then separate line needs to be created for each dep. area. |
| 6 | Cumulative Values |
From this tab transaction data field is started, fields like current fiscal year (Current fiscal year = active fiscal year in system), Cumulated Acquisition Value, Accumulated Ordinary Depreciation, Currency, etc. Using this details system will post the required transaction. In case there are multiple dep. area then separate line needs to be created for each dep. area. |
| 7 | Posted Values |
This tab needs to be populated for transfers during the year, it holds the Posted Ordinary Deprec. for the Year (Depreciation values must be negative), Depr. posted until (including period). In case there are multiple dep. area then separate line needs to be created for each dep. area. |
| 8 | Transactions |
This tab needs to be populated for transfers during the year, it helps to transfer the transactions starting from the beginning of the fiscal year up to the time of the transfer date. E.g., transactions are, additional acquisitions, retirements, etc.
In case there are multiple dep. area then separate line needs to be created for each dep. area. |
| 9 | Proportional Values on Transactions |
This tab needs to be populated for transfers during the year, it holds important fields like Prop. Accumulated Ordinary Depreciation, Prop. Cumulative Special Depreciation, etc. In case there are multiple dep. area then separate line needs to be created for each dep. area. |
Below table from SAP help portal provides full details on the available tab: –
Source: SAP Help Portal: Link
Legacy System Migration Workbench – LSMW
Fixed Asset Data migration can also be performed using LSMW. This traditional tool has 4 import method, but I tend to use more of BAPI and IDOC mainly because of its speed (parallel processing), error handling and standard. For Fixed Asset Data migration, below BAPI can be used: –
- BAPI_FIXEDASSET_OVRTAKE_CREATE
- BAPI for creating and optionally transferring values to new legacy assets to be created
- S/4HANA migration cockpit Object Fixed asset (incl. balances and transactions) is using this BAPI
- BAPI_FIXEDASSET_OVRTAKE_POST
- BAPI for transferring values to existing legacy assets, using this BAPI asset transactions/values can be updated
Parallel processing of IDocs in the background (report RBDAPP01) with package size 50 has proven successful. Ensure that your package contents are as homogenous as possible (for example, fixed assets from the same asset class).
Selection of S/4HANA migration cockpit or LSMW
Below comparison is based on personal experience, kindly note every project is different, and you should evaluate beforehand:
| Parameters | S/4HANA Migration Cockpit | LSMW |
| Standard | Migration object – Fixed asset (incl. balances and transactions) is available out of the box solution. This is having standard simulation, mapping, validation, and postings. | SAP has provided and support standard BAPI for fixed asset data migration. A migration (or conversion) object needs to be created using provided BAPI/IDOC. |
| Performance |
The normal performance benchmark for BAPI_FIXEDASSET_OVRTAKE_CREATE (which is used for Migration object – Fixed asset) is approx. 2 sec per asset. This benchmark is valid for Validation, Simulation and for Execute Import. This means it might take approx. 5 hours for migrating 10,000 assets.
Parallelization of XML file loads is possible using attribute (“Max. Data Transfer Jobs”) in S/4HANA migration cockpit. This will use batch-job processes in the system.
|
Using parallel processing in LSMW with BAPI/IDOC system can use multiple (i.e., 80%) dialogue processes in parallel for asset data migration.
With personal experience on BAPI (BAPI_FIXEDASSET_OVRTAKE_POST), I have notice approx. 10 records were created/migrated in a second. Considering this speed 10,000 assets will migrate within 15 minutes of time.
Please note actual time depends on the system resources and performance. And time for creation and posting with BAPI (BAPI_FIXEDASSET_OVRTAKE_CREATE) will also be differ. |
| Volume |
By standard the default size limit for each uploaded XML file is 100MB, size limit for each uploaded XML file can be set to 160MB by changing the system parameter (icm/HTTP/max_request_size_KB).
Although here is no limit in case you are migrating using “Staging tables”. |
LSMW does not have limitation on file size but by default LSMW can only read 2,147,483,647 records. |
| Custom Fields | Migration object provided can be updated to add new fields which are not in template using the Migration Object Modeler (transaction LTMOM). | Standard BAPI has provided extension structure for updating such fields. |
Subsequent corrections to the transferred values
It is advisable to perform mock migration or migration rehearsal before actual migration. It is also recommended that you use a variety of tests to ensure that the transfer of production legacy data can be carried out and reconciled without errors, without requiring subsequent corrections to the transferred values. If incorrect migration is performed and data need to be corrected (and you don’t want to Reset Company Code). Below steps are suggested, however every project is different, and you should evaluate/check the steps beforehand: –
- Reverse the transfer documents using BAPI (BAPI_ASSET_REVERSAL_POST) with LSMW, reversal will be posted to transfer documents. Legacy Fixed Assets which were already created are retained. If require, you can deactivate the legacy assets using change function
- Re-post the corrections of the transfer values using transaction code ABLDT (SAP Customizing Implementation Guide –> Financial Accounting –> Asset Accounting –> Asset Data Transfer –> Manual Data Transfer –> Legacy Fixed Asset –> Post Transfer Values) or using BAPI (BAPI_FIXEDASSET_OVRTAKE_POST). It is recommended to use BAPI with LSMW for mass upload because transaction code ABLDT uses an input enabled ALV grid control and does not support batch input.
Link to important information/source
Below are some useful links for further study: –
| Description | Source | Link |
| S/4HANA Migration Cockpit | SAP Help | https://help.sap.com/viewer/29193bf0ebdd4583930b2176cb993268/2020.000/en-US/8f97f0b407024465a283809f0bbe000c.html |
| List of Migration objects with S/4HANA cockpit | SAP Help |
|
| Migration Object Fixed asset (incl. balances and transactions) | SAP Help | https://help.sap.com/viewer/d3a3eb7caa1842858bf0372e17ad3909/2020.000/en-US/6b5e59864fe846529f841fe5b599b930.html |
| LTMC for Master Data Step by Step Process | SAP Blogs (by Ruthvik Chowdary) | https://blogs.sap.com/2019/04/26/ltmc-for-master-data-step-by-step-process/ |
| How to add custom fields to SAP S/4HANA data migration cockpit.. | SAP Blogs (by Fernando Martin) | https://blogs.sap.com/2021/01/22/how-to-add-custom-fields-to-sap-s-4hana-data-migration-cockpit-with-data-migration-modeller.-example-with-material-master./ |
Below are some useful SAP’s notes for reference: –
- 2208321 – FAQ for legacy data transfer in SAP_FIN 720 and subsequent releases
- 2331123 – Prerequisite customizing required for legacy asset takeover in Simple Finance (sFIN)
- 2631104 – Performance of migration the fixed assets
- 2719524 – SAP S/4HANA Migration Cockpit: XML template size limits
- 2878945 – Migration Cockpit: Parallelization of XML file loads
- 2554160 – SAP S/4HANA Migration Cockpit: Fixed Asset: Less performance during simulation run
- 2576565 – SAP S/4HANA Migration Cockpit and Migration Object Modeler (LTMOM): Learning materials and knowledge points, Data Migration On-Premises
Conclusion
Hope after reading this blog, you got information on important configuration, accounting entries, migration options, parameter on selection of migration options, idea on subsequent correction of transfer values and some links to other important information/source.
Disclaimer
This blog post is my opinion and not linked to any organization. All screen shots are from test systems and any similarity is coincidence.
Thank you for your valuable blog, it's really very useful.
Thanks Gunjan for feedback!! Glad to know content was useful.
This is quite useful information. Thanks a lot for sharing.
Thanks Surbhi for feedback.
Very informative and to the point, Excellent contribution
Thanks Anchal!!
Thank you for this Blog, its very useful.
Can you please clarify, how Transaction type will update what we have created in 'Define Transaction Types for Transfer of Open Items'.
In my project system is automatically updating 970 instead of 980.
Please reply.
Thank you in advance.
Kishan
Hi Kishan,
I am glad that you found this blog useful.
Configuration 'Define Transaction Types for Transfer of Open Items' is for migration of assets under construction (AuC) with line item management. Kindly go through below link for better understanding (specially constrain) and also go through the example provided by SAP:
https://help.sap.com/viewer/67e323b7117e4c91869c258933f47182/latest/en-US/bfd8d153c9684608e10000000a174cb4.html
Regards,
Anand Raichura
Hi Anand,
Really happy to see structured approach to follow for assets migration.
Can you please also share - how to migrate the zero balances assets as getting errors from the migration cockpit simulation stage?
For audit compliances, we need to have in use but fully depreciated assets in the asset history sheet report for the new ERP - SAP S4 HANA Cloud.
Regards
Govind Sharma
Hi Govind,
Thanks for feedback on the blog. Please note you can migrate the zero balance assets (i.e. fully depreciated asset) by updating relevant values (i.e. actual values) Cumulated Acquisition Value and Accumulated Ordinary Depreciation.
Please find below screen shot as an example and kindly perform testing in non-production system:
Cumulative Values
For above example, system should post below accounting entry with ultimate zero balance on asset:-
Dr. Accumulated Acquisition 17,520
Cr. Accumulated Dep. -17,520
Hope you are able to get required information.
Thanks a lot.
Regards,
Anand Raichura
Great post, Anand.
Ford the 0 value assets, I followed your advice and added APC and 100% depreciation amount into tab cumulative value in the xml.
Current FY is 2023 for mid-year migration (04/2023 in test).
The file is loaded and it created an asset. The value date however is 1.1.2023 with a transaction type 970 - mid-year transfer
Beginning and year end APC in 2023 is my APC amount,
but same with depreciation
A deactivation is not possible, with message that dep area still has acquisition values.
Is there somehere a place where I can set a "previous year" APC and depreciation amount?
Cheers
Thanks for the feedback on blog.
Please note to update current year transactions if applicable for this zero value asset. As suggested in earlier response and blog kindly test it for getting exact results. I will first check manually using SPRO path to unit test before testing using LTMC. Please give it a try and respond on blog so it will be useful for other members in need.
Thanks a lot.
Regards,
Anand
Thanks.
The situation is that the assets have been fully depreciated in previous years but are still in use (value = 0).
I would need hoever to show the original APC and the (fully) depreciated amount.
So, for this case where would I need to capture the APC and the depreciation amount?
Cheers
Hello Anand,
I am working on Asset migration and we are using migration BAPI to migrate assets. I have a question on migration retired assets of current year having revenue (210 Trans type). Can you help with 2 questions -
Dear Abhinav,
Please note below:-
From where we can find the revenue amount of each transaction.
Thanks a lot.
Regards,
Anand Raichura
PS: Please update the approach you have taken for future reference, this will help others.
Thanks Anand for your quick response.
Legacy is also SAP and when i am migrating the scenario for ex -
ANLC - KANSW - APC -> 1000 (passing in migration)
ANLC - KNAFA - ACC dep -> -200 (passing in migration)
ANLC - NAFAG - Dep CY -> -50 (passing in migration)
Retirement Trans -
ANEP - ANBTR -> -1000 (passing in migration)
ANEA - NAFAL -> 50 ((passing in migration)
ANEA - NAFAV -> 200 (passing in migration)
If in legacy entry was posted with revenue (210 type) during retirement so where this revenue amount is stored to fetch in SAP ECC? I can see trans type 210 is used so there is some revenue posted during retirement but i am unable to find it at table level to fetch for migration and map that field into BAPI. The impact is after posting above set of values - it is treating as loss.
I will check with the developer about the revenue field available in BAPI and how entry will reflect after using it.
Regards,
Abhinav.
Hi Anand,
This is a very helpful post. Can you further elaborate about the Posted value sheet as what values should be input in the file in the respective sheets in case of a current year depreciation posting.
Should be input the gross value of the Assets again in the 'Posted value' sheet along with the 'Depreciation amount' or it should be only depreciation amount with a prefix '-'?
Please guide as what values should we input in all the sheets in the Asset posting file, in case of a current year depreciation posting.
Appreciate a timely response.
Regards
Partha Sarathi Samantaray
Hi Partha,
Thanks for your feedback. Please note details in the posted value depends upon the legacy details asset you are transferring. You should not post gross value of asset in 'Posted Value'. In general follow the content at section 'S/4HANA migration cockpit' on above blog and kindly pretest as suggested at below SAP help portal link.
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/d3a3eb7caa1842858bf0372e17ad3909/6b5e59864fe846529f841fe5b599b930.html?version=2020.000
SAP Help Portal
Regards,
Anand Raichura
Hi Anand,
Thanks for the note. Please be informed that this migration is happening in SAP S4 HANA Cloud. Please refer the scenario details below and advise.
Fiscal year - Calendar year
Asset transfer date - 01.03.2022 (Ideally should be the last date of the month). This is in Q currently. However, We will have the transfer date as the last date of the month in P.
Legacy Assets received - Till 28th Feb.
Creating the Asset master using the Migration cockpit - We have created the legacy assets till date including the current year assets as well.
However, we are facing issue at the time of Assets postings.
i) We are not able to take over the current year assets APC values and depreciation using the Cumulative sheet. It says, the Asset value date falls in current year. Can you guide here as which is the relevant sheet for Current year assets posting, both APC values and depreciation. If it is 'Posted value' sheet, then how to fill up the data exactly?
ii) Are we able to take over the legacy data, both Gross value and depreciation till 31st March,2022, if we set the Asset transfer date as 31st March,2022, considering the Company code Fiscal year as both Calendar and Year dependent.
Appreciate your time.
Regards
Partha Sarathi Samantaray
Hi Partha,
Please find below comments:-
i) We are not able to take over the current year assets APC values and depreciation using the Cumulative sheet. It says, the Asset value date falls in current year. Can you guide here as which is the relevant sheet for Current year assets posting, both APC values and depreciation. If it is 'Posted value' sheet, then how to fill up the data exactly?
Answer: For current year asset, you need to use tab 'Transactions (Transf. dur. FY)' for APC value and depreciation should be part of 'Posted Values'.
ii) Are we able to take over the legacy data, both Gross value and depreciation till 31st March,2022, if we set the Asset transfer date as 31st March,2022, considering the Company code Fiscal year as both Calendar and Year dependent
Answer: Yes, please test the same in case of any doubts.
Thanks a lot.
Regards,
Anand Raichura
Below are some of the screen shots for your reference, please try to go through blog, link to help and suggested SAP notes
Blog screen shot
SAP Note: 2208321 - FAQ for legacy data transfer in SAP_FIN 720 and subsequent releases
Hi Anand,
Several permutations and combinations did the trick and off course your valuable inputs here. We can upload the Asset values for both previous and current year.
There is another issue with the Asset Masters. .User had given Expired Useful life in the template instead of planned useful life. Now all the FA masters of a particular entity are updated with Exp. useful life value not the planned useful life. Can we do a mass change for this specific field in S4 HANA Cloud? Please advise.
Appreciate a timely response.
Regards
Partha Sarathi Samantaray
Hi Anand Raichura
Could you please help me to know what tabs and fields do I need to fill in order to load some Asset Retirement by Scrapping using LTMC templates?
Grace
Hi Grace,
Kindly note you can use 'Transaction..' tab for migrating current year transactions (including asset retirement by scrapping). In general follow the content at section 'S/4HANA migration cockpit' on above blog and kindly pretest as suggested at below SAP help portal link. With pre-test you will be able to understand required fields when performing migration.
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/d3a3eb7caa1842858bf0372e17ad3909/6b5e59864fe846529f841fe5b599b930.html?version=2020.000
SAP Help Portal
Below are mandatory field in LTMC for 'Transaction..' tab:-
Mandatory Fields for Transaction Tab
Below is screen shot of 'Transaction..' tab:-
Transaction Tab
Regards,
Anand Raichura
Hi Anand,
Hope you are doing well!
I am doing the Fixed Asset migration in SAP S4 On premise this time around but encountering an issue related to the FI period. I tried uploading the Assets template using the migration cockpit, but at the simulation stage, system throws an error saying 'Posting period xxx xxxx is not open'. It is indicating towards OB52 and when checked, everything is fine and I am also able to post a manual document using F-90 in that particular period as well. The period is picked from the Asset Transfer Date maintained in the system. Do we need to look upon any other period related settings for Asset migration?
Regards
Partha
Hi Anand,
Can you explain the steps for configuring the Indian Tax depreciation set up in SAP S4 HANA with Block key concept?
\Regards
Partha
Hi Partha,
Please referre rapid deployment (best practice ) for India, you should be able to get relevant answer. Alternatively, I will suggest try asking question on SAP Q&A, you might get faster responses.
https://answers.sap.com/questions/ask.html
Regards,
Anand Raichura
Hi Anand,
Hope you are doing well!
This blog is very useful for us during the research. I have one concern about the tab "proportional value on transaction"
Could you let us know when we can use this tab and how can to check after migration in S4?
thanks and look for your feedback soon.
Hi Giribabu,
As per my understanding, you can use tab "proportional value on transaction" for migrating details in table ANEA (Asset Line Items for Proportional Values). I came across a certain SAP note (#2530739 - BAPI_FIXEDASSET_OVRTAKE_CREATE: Example of accumulated depreciations for transfer during the fiscal year) which has example of value in concern tab.
Please check SAP note and try to test in system for better understanding.
Regards,
Anand Raichura
Hello Anand,
thanks a lot for the great blog. A short question: we are using the Direct Transfer Method to transfer fixed assets (including balances) object, and I managed to migrate the assets through Migration Cockpit, however only the master data, not the transactional data of it (CUMULATIVEVALUES, POSTEDVALUTION, TRANSACTIONS). Do you perhaps have an Idea why these are not being migrated?
I see the values already in the source system ANLC table, however in the target system, in the ANLC table are only the new assets created without Values basically 0,00 for the KFs of the table (Column KANSW, KAUFW etc.)
Thank you in advance!
Regys
Hi Regys,
I haven't worked on direct transfer method but SAP help has mentioned few prerequisites and details which can help you to troubleshoot issue. If you have followed all the steps mentioned in provided link try raising SAP incident for standard issues.
Please find below SAP help portal link for content on direct transfer method:
https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/d3a3eb7caa1842858bf0372e17ad3909/75f49eeacd204bb38a76492e95345065.html?locale=en-US
Regards,
Anand Raichura