When moving to SAP S/4HANA a choice is made between: converting a current ECC environment to SAP S/4HANA (brownfield implementation), and new implementation of SAP S/4HANA (greenfield implementation). In case of a new implementation of SAP S/4HANA a data migration has to be performed. In this blog, an overview is given of the Finance data migration in SAP S/4HANA. Introduction A distinction is made between: master data, and transactional data. First master data is migrated and afterwards transactional data. 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: General ledger accounts, Business partners, Profit centers, Cost centers, Internal orders, Projects, WBS elements, Networks, Assets. 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. Vendor open items Customer open items General ledger open items General ledger balances Asset balances 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. Vendor open items Following posting is made during migration of vendor open items: 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. Customer open items Following posting is made during migration of customer 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. General ledger open items and balances Following posting is made during migration of general ledger open items and general ledger balances: PK 40/50 – GL Account – Dt/Ct 100 PK 50/40 – Migration Account – Ct/Dt 100 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: Asset APC (BS) – Dt 100 Asset Depreciation (BS) – Ct 10 Migration Account – Ct 90 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 OpenSAP course: Data Migration to SAP S/4HANA Muhammad Muzammil Khan Posted on September 19, 2018 4 minute read SAP FI DATA MIGRATION ACTIVITY FollowRSS feedLike 10 Likes 13,253 Views 4 Comments 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. SAP FI DATA MIGRATION ACTIVITY Broadly, SAP FI Data migration Activity has been divided into two categories, 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: Define cut over phase, during which FINANCE has to, 1. 2. 3. 4. 5. 6. Closed the P&L in Retained earning account. Check Balance sheet balances through equation, Assets – Liabilities= Equities You have to create 6 G/L upload clearing accounts through FS00 G/L Upload clearing Vendors Upload clearing Customers upload clearing Assets upload clearing Material Upload Account Main Upload account Also, configure the Doc Type “UL” with separate No. ranges for Upload. 1- G/L Line Items Transfer Balance sheet account balances through F-02 LSMW program. Pass the following JV entry, Example: PK 40 – G/L uploading clearing account Dr 100 PK 50 – Capital ——————————– Cr 100 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 PK 50 -G/hL upload clearing a/c ——— Cr 100 2- Open Items for Customers Transfer Balance sheet account balances through F-02/ F-22 LSMW program. Pass the following JV entry, Example: PK 01 – Customer 1 —————– Dr 100 PK 01 – Customer 2 —————– Dr 100 PK 01 – Customer 3 —————– Dr 100 PK 50 – Customer Upload clearing — Cr 300 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 – Customer upload clearing — Dr 100 PK 50 – Main Upload Account ————– Cr 100 3- Open Items for Vendors Transfer Balance sheet account balances through F-02/ F-43 LSMW program. Pass the following JV entry, Example: PK 50 – Vendor Upload clearing — Dr 300 PK 31 – Vendor 1 ——————– Cr 100 PK 31 – Vendor 2 ——————– Cr 100 PK 31 – Vendor 3 ——————– Cr 100 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 PK 50 – Vendor upload clearing ———- Cr 100 4- Asset Balances As, you have already created the Asset Master data through AS91, during which you have also enter Asset APV and Depreciation values (Asset takeover values) in Asset accounting module. To post in G/L account, go to t-code: OAMK and change the control of reconciliation account to “BLANK” Transfer Balance sheet account balances through F-02 LSMW program. Pass the following JV entry, Example: PK 70 – Fixed Asset 1————– Dr 100 PK 70 – Fixed Asset 2————– Dr 100 PK 50 – Asset Upload clearing—- Cr 100 PK 50 – Acc. Dep Account——— Cr 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: PK 40 – Main Upload Account ——- Dr 100 PK 50 – Asset Upload clearing ——— Cr 100 5- Material Balances Balances are uploaded via t- code MB1C from MM side. When you upload using 561 movement type, the accounting entry should be, Example: PK 89 – Inventory —————– Dr 100 PK 50 – Material Upload Account — Cr 300 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 PK 50 – Main Upload Account ————– Cr 100 6- Cost Center Planning Make LSMW program for the KP06, extract the template and upload Cost center planning data for previous number of years (Optional) 7- Profit Center Planning Make LSMW program for the 7KE1, extract the template and upload Cost center planning data for previous number of years (Optional) 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.