Skip to Content
Product Information

SAP Finance Data Migration in S/4HANA

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

/
Be the first to leave a comment
You must be Logged on to comment or reply to a post.