SAP Finance Data Migration in S4HANA
SAP Finance Data Migration in S4HANA
In this blog, an overview is given of the Finance data migration in SAP S/4HANA.
Introduction
A distinction is made between:
In the past for the data migration to SAP ERP, SAP offered the legacy system migration workbench
(transaction code LSMW). But for the migration of business data to SAP S/4HANA and SAP
S/4HANA Cloud, the SAP S/4HANA migration cockpit is the tool of choice (transaction code LTMC).
Even if the LSMW functionality could theoretically be used in some areas, it might propose incorrect
migration interfaces that cannot be used in SAP S/4HANA anymore. Therefore LSMW is on the
simplification list and will not be supported in the SAP S/4HANA context. For more information on
this, please consult oss note 2287723 (LSMW in SAP S/4HANA on-premise).
Master data
The common master data objects include:
SAP S/4HANA migration cockpit is the tool of choice for the migration of financial master data.
For all of the master data objects mentioned above, a standard migration object is available for SAP
S/4HANA.
Transactional data
A data migration is typically done at year-end or period-end. This means that transactional data is
migrated after closing the last posting period.
The migration of financial figures is split in different parts. Each part can be executed at different
timings according to your cut-over and migration plan.
As the migration is split in different parts, one or multiple migration accounts are created. The
balance of this(these) migration account(s) has to be zero at the end of the migration.
Additionally it’s also common to create a specific document type for migration.
PK 31 – Vendor 1 – Ct 100
PK 40 – Migration Account – Dt 100
SAP S/4HANA migration cockpit is the tool of choice for this migration activity. The migration object
‘FI – Accounts payable open item’ can be used for migration of vendor open items.
PK 01 – Customer 1 – Dt 100
PK 50 – Migration Account – Ct 100
SAP S/4HANA migration cockpit is the tool of choice for this migration activity. The migration object
‘FI – Accounts receivable open item’ can be used for migration of customer open items.
SAP S/4HANA migration cockpit is the tool of choice for this migration activity. The migration object
‘FI – G/L account balance and open/line item’ can be used for migration of general ledger open
items and general ledger balances.
Asset balances
Following posting is made during migration of assets:
The offsetting account for the legacy data transfer (asset balance sheet account) is defined in
customizing for asset accounting under ‘Define Offsetting Account for Legacy Data Transfer’.
SAP S/4HANA migration cockpit is the tool of choice for this migration activity. The migration object
‘Fixed asset (incl. balances and transactions)’ can be used for migration of asset balances.
Conclusion
The migration approach in S/4HANA is not that different from the one for SAP ECC.
A new and improved functionality is available to perform the migration: SAP S/4HANA migration
cockpit.
Useful references
Blog: SAP FI DATA MIGRATION ACTIVITY
Data Migration is one the critical and final phase in the ASAP Methodology road map. During this
phase the cut over period is defined at which the data entry in legacy system is halted, collected and
taken to migrate to SAP system. One of the crucial data to migrate during this activity is the Finance,
based on accuracy of this your whole implementation is analyze because it is the final outcome or
the result seen by the Management. In this blog, I have discussed the data migration steps,
techniques and procedures to migrate Financial data to SAP ERP.
1. Master data (G/L accounts, customers, vendors, assets, cost elements, cost centers, profit
centers etc.)
2. Transnational Data (Open Items for customers and vendors, G/L line items, Asset Balances,
Material balances, Cost Center planning, profit center plan data load etc.)
1- Master Data
1- G/L Accounts
– Make LSMW Upload for t-code FS00. Extract template, Fill data and Upload.
2- Customer Accounts
– Make LSMW Upload for t-code XD01. Extract template, Fill data and Upload.
3- Vendor Accounts
– Make LSMW Upload for t-code XK01. Extract template, Fill data and Upload.
4- Asset Accounts
– Make LSMW Upload for t-code AS91. Extract template, Fill data and Upload.
5- Cost Elements
– Make LSMW Upload for t-code KA01. Extract template, Fill data and Upload.
6- Cost Centers
– Make LSMW Upload for t-code XS01. Extract template, Fill data and Upload.
7- Profit Center
– Make LSMW Upload for t-code KE51. Extract template, Fill data and Upload.
2- Transaction Data
Pre-Requisites
Pre-Requisites required by FINANCE Department:
After uploading the balances you can a pass an adjustment entry for these clearing
accounts. Any way total balance for uploading clearing accounts should be zero.
Example:
After uploading the balances you can a pass an adjustment entry for these clearing
accounts. Any way total balance for uploading clearing accounts should be zero.
Example:
After uploading the balances you can a pass an adjustment entry for these clearing
accounts. Any way total balance for uploading clearing accounts should be zero.
Example:
PK 40 – Main Upload Account ————– Dr 100
Post G/L balances and go to OAMK and restore control of reconciliation account to ”
ASSETS”
2nd Option for G/L posting is through t-code: OASV. In this you don’t have to use t-codes:
OMAK & F-02.
Now, you have to reconcile Asset values in Asset Accounting module with GL balances
using t-code: ABST2
After uploading the balances you can a pass an adjustment entry for these clearing
accounts. Any way total balance for uploading clearing accounts should be zero.
Example:
The system would read the material master price for the plant and multiply the same with
quantity of the material. This will be the value which will be updated as the stock value in the
inventory account G/L as well as stock balance in Materials Management.
After uploading the balances you can a pass an adjustment entry for these clearing
accounts. Any way total balance for uploading clearing accounts should be zero.
Example:
PK 40 – Material Upload account — Dr 100
In the above article the major focus is on the data migration steps and techniques used to migrate
Finance data. If anyone want to acquired more knowledge on the subject matter, then it is requested
to go through the below links in references. I appreciate the time you took to read this blog, hope this
article is helpful and knowledgeable to the readers.