Anand Raichura

January 16, 2022 8 minute read

SAP S/4HANA Fixed Asset Legacy Data

Migration
8105,106

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.

#Configura Accounting Entries

tion
1Define  Transfer date – This date depends upon whether legacy data
Transfer transfer is at fiscal year-end or during the year
Date and  Transfer status – Select transfer status from In Preparation,
Additional Ongoing, Ongoing (Other Postings Allowed) or Completed.
Paramete  Document type – This document type will be used when
rs posting fixed asset migration documents.
#Configura Accounting Entries
tion

2Specify Mention offsetting account for transferring the asset balances. This
Offsetting GL account will be used for asset data migration.
Account
for
Legacy
Data
Transfer

3Define Define transaction types for the takeover of open items from a
Transacti previous system. If you do not have any assets under construction
on Types with line-item management, you do not need this kind of transaction
for type.
Transfer
of Open
Items
#Configura Accounting Entries
tion

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 Transactions Accounting Entries

Applicable
1Year-end Previous year Dr. Accumulated Acquisition
migration and Mid- accumulated Values
year migration Cr. Accumulated Dep.

Cr. Offsetting/Takeon Account

2Mid-year migration Current year Dep. Dr. Offsetting/Takeon Account

Cr. Accumulated Dep.

3Mid-year migration Current year Acquisition Dr. Accumulated Acquisition

or additions
Cr. Offsetting/Takeon Account

4Mid-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 Tab Comment
.
N
o.
1 Master This worksheet/tab hold important information for creation of the
Details assets. Some of the fields are Asset number, sub-number, asset
(mandat class, description, etc.
ory)

2 Posting Asset Capitalization Date field is provided in this worksheet/tab.

Informat
ion
Sr Tab Comment
.
N
o.

3 Time- Time dependent data like cost center, WBS, plant, etc. are part of
Depende this worksheet/tab.
nt Data

4 Allocatio This worksheet/tab hold information like evaluation group, sort key,
ns etc.

5 Deprecia Details like depreciation (dep.) area, dep. Key, useful life, dep. Start
tion date, etc. can be updated here.
Areas
In case there are multiple dep. area then separate line needs to be
created for each dep. area.

6 Cumulati From this tab transaction data field is started, fields like current
ve fiscal year (Current fiscal year = active fiscal year in system),
Values Cumulated Acquisition Value, Accumulated Ordinary Depreciation,
Currency, etc. Using this details system will post the required
Sr Tab Comment
.
N
o.
transaction.

In case there are multiple dep. area then separate line needs to be
created for each dep. area.

7 Posted This tab needs to be populated for transfers during the year, it holds
Values 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 Transact This tab needs to be populated for transfers during the year, it helps
ions 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.
Sr Tab Comment
.
N
o.

9 Proporti This tab needs to be populated for transfers during the year, it holds
onal important fields like Prop. Accumulated Ordinary Depreciation, Prop.
Values Cumulative Special Depreciation, etc.
on
Transact In case there are multiple dep. area then separate line needs to be
ions 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
o BAPI for creating and optionally transferring values to new legacy assets to be created
o S/4HANA migration cockpit Object Fixed asset (incl. balances and transactions) is using
this BAPI
 BAPI_FIXEDASSET_OVRTAKE_POST
o 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:

Parameter S/4HANA Migration Cockpit LSMW

s
Standard Migration object – Fixed asset SAP has provided and support
(incl. balances and transactions) standard BAPI for fixed asset data
is available out of the box migration. A migration (or
solution. This is having standard conversion) object needs to be
simulation, mapping, validation, created using provided BAPI/IDOC.
and postings.
Performan The normal performance Using parallel processing in LSMW
ce benchmark for with BAPI/IDOC system can use
BAPI_FIXEDASSET_OVRTAKE_CR multiple (i.e., 80%) dialogue
EATE (which is used for Migration processes in parallel for asset data
object – Fixed asset) is approx. 2 migration.
sec per asset. This benchmark is
valid for Validation, Simulation
and for Execute Import. This
means it might take approx. 5 With personal experience on BAPI
hours for migrating 10,000 assets. (BAPI_FIXEDASSET_OVRTAKE_POS
T), I have notice approx. 10
records were created/migrated in a
second. Considering this speed
Parallelization of XML file loads is 10,000 assets will migrate within
possible using attribute (“Max. 15 minutes of time.
Data Transfer Jobs”) in S/4HANA
migration cockpit. This will use
batch-job processes in the
system. Please note actual time depends
on the system resources and
performance. And time for creation
and posting with BAPI
(BAPI_FIXEDASSET_OVRTAKE_CRE
ATE) will also be differ.
Parameter S/4HANA Migration Cockpit LSMW
s
Volume By standard the default size limit LSMW does not have limitation on
for each uploaded XML file is file size but by default LSMW can
100MB, size limit for each only read 2,147,483,647 records.
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”.
Custom Migration object provided can be Standard BAPI has provided
Fields updated to add new fields which extension structure for updating
are not in template using the such fields.
Migration Object Modeler
(transaction LTMOM).

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: –
Descripti Source Link
on
S/4HANA SAP https://help.sap.com/viewer/
Migration Help 29193bf0ebdd4583930b2176cb993268/2020.000/en-US/
Cockpit 8f97f0b407024465a283809f0bbe000c.html
List of SAP https://help.sap.com/viewer/
Migration Help d3a3eb7caa1842858bf0372e17ad3909/2020.000/en-US/
objects 8dd142b479f9481891fa8b3f86648df3.html
with
S/4HANA
cockpit
Migration SAP https://help.sap.com/viewer/
Object Help d3a3eb7caa1842858bf0372e17ad3909/2020.000/en-US/
Fixed 6b5e59864fe846529f841fe5b599b930.html
asset
(incl.
balances
and
transacti
ons)
LTMC for SAP https://blogs.sap.com/2019/04/26/ltmc-for-master-data-step-by-
Master Blogs step-process/
Data Step (by
by Step Ruthvik
Process Chowda
ry)
How to SAP https://blogs.sap.com/2021/01/22/how-to-add-custom-fields-to-
add Blogs sap-s-4hana-data-migration-cockpit-with-data-migration-
custom (by modeller.-example-with-material-master./
fields to Fernand
SAP o
S/4HANA Martin)
data
migration
cockpit..

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
asset upload for dep areas pointing to leading
and non leading ledger
1187 Views

Follow

RSS Feed

Hi all ,

Following is the scenario :

Fiscal year of leading ledger is April 2019 to march 2010 ( book

depreciation points to leading ledger )

Fiscal year of non leading ledger is Jan 2019 to dec 2019 ( local GAAP
depreciation points to non leading ledger )

Asset transfer date is 30.09.2019 ( during the fiscal year )

My query is that what TAKE OVER values ( on which dates ) to be

taken for APC , accumulated dep and posted depreciation while
uploading assets through AS91 in Book depreciation area and local
GAAP depreciation area .

Regards

Manoj

 Add a Comment

 Alert Moderator

Assigned Tags

 FIN Asset Accounting

Similar Questions

 Fixed assets -subledger

 Former MemberNov 23, 2019

 Asset Accounting

Former MemberNov 23, 2019

Join the Conversation

SAP TechEd

Tune in for tech talk. Stay for inspiration. Upskill your future.

SAP BTP Learning Group

SAP Business Technology Platform Learning Journeys.

Coffee Corner

Join the new Coffee Corner Discussion Group.

2 Answers
Sort by:

Votes

Newest

Oldest

Vote up 1 Vote down

Narasimhulu Konnipati
Aug 05, 2019 at 02:19 AM

Hi Manoj,
Takeover values:

Book Depreciation area (Leading Ledger) : April to March

1. APC Values of the assets from the beginning of their capitalization

2. Accumulated depreciation till 31.03.2019 for all the Assets

3. Ordinary Depreciation from 01.04.2019 to 30.09.2019.

Local GAPP Depreciation area (Non-Leading Ledger) : Jan to Dec

1. APC Values of the assets from the beginning of their capitalization

2. Accumulated depreciation till 31.12.2018 for all the Assets

3. Ordinary Depreciation from 01.01.2019 to 30.09.2019.

Migration Approach:

Book Depreciation area (Leading Ledger) : April to March

1. For the Assets Purchased and Capitalized on or before 31.03.2019,

you will have both Accumulated Depreciation and Ordinary
Depreciation.

2. For the Assets Purchased after 01.04.2019, you will only have
ordinary depreciation.

Local GAAP - Depreciation area (Non-Leading Ledger) : Jan to Dec

1. For the Assets Purchased and Capitalized on or before 31.12.2018,

you will have both Accumulated Depreciation and Ordinary
Depreciation.

2. For the Assets Purchased after 01.01.2019, you will only have
ordinary depreciation.

Assets migration is different from ECC to S/4HANA

ECC:
1. Migrate Assets and its values using AS91. For the current year
assets, use Transaction 100 in AS91 for migration

2. Post G/L Values using OASV. Use Initial Upload Account for
offsetting.

S/4HANA:

1. Migrate all Assets using AS91 (no values).

2. Post Values in both Assets and G/L using ABLDT.

3. For the Current year assets, use AB01L for APC Values posting and
ABLDT for Depreciation posting.

Any doubts, please revert.

Thanks,

NSK

 Add a Comment

 Alert Moderator

 Share

1 comment

Manoj Chauhan

Aug 19, 2019 at 09:38 AM

Thanks ,

Manoj

 Like 0

 Share

 Alert Moderator

Vote up 0 Vote down

Narasimhulu Konnipati
Aug 19, 2019 at 10:00 AM

Close the thread if the given answer helped by marking it as Accepted.

Thanks,

NSK

 Add a Comment

 Alert Moderator

Report as offensive (i.e. containing spam, advertising, malicious text,

etc.)

 Share