7/20/2023

Migration of Historical Balances

to SAP S/4HANA
Generated on: 2023-07-20 08:26:14 GMT+0000

Data Migration with SAP S/4HANA Migration Cockpit | SHIP

CONFIDENTIAL

Original content: https://help.sap.com/docs/DATAMIG_S4HANA/bc683d7705f246f28fdd0e183a4c6c1b?locale=en-

US&state=PRODUCTION&version=SHIP

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 7/20/2023

Purpose
This documentation describes the recommended approach for migrating historical balances to SAP S/4HANA for customers
who use SAP S/4HANA 1809 or earlier.

Migrating historical nancial transactions is supported in SAP S/4HANA Cloud and as of SAP S/4HANA 1909 using the FI -
Historical balance migration object. If you're using SAP S/4HANA Cloud or SAP S/4HANA 1909 or newer, this documentation is
not relevant for you.

Overview

Enter the balance on G/L account level for each period for which you want to run a “previous year/current year comparison”
report. The posting date is equivalent to the last day of that period. Reverse this posting on the rst day of the following period.

Migration Strategy Approach – Finance View

This is custom documentation. For more information, please visit the SAP Help Portal 2
 7/20/2023

Create "Dummy" G/L Accounts

For some account types, it is recommended that you create “dummy” accounts (that is, regular G/L accounts without
reconciliation type, not open item managed, not cash relevant), for example, for reconciliation accounts. Reconciliation
accounts cannot be posted directly, but always need a subledger account such as customer, asset, material etc. It is also
recommended that you create "dummy" accounts for accounts that require speci c elds such as tax accounts, which require
base amount and tax code. When migrating the historical balances, these accounts will be posted instead of the original
accounts. For P&L accounts, no "dummy" accounts are needed if a "dummy" cost object – for example, cost center – is created.
The internal reporting is based on FSV (Financial Statement Version). To see all balances in reporting, assign all "dummy"
accounts to the relevant items in the FSV on the corresponding hierarchy level.

Create "dummy" G/L accounts for:

asset values (acquisitions and accumulate depreciation)

stocks

accounts payables

accounts receivable

any other accounts that need to be migrated as G/L balances with special required elds, for example, tax
accounts, bank accounts etc.

initial offsetting account for migration of historical balances

Add "dummy" accounts to FSV (Financial Statement Version) to the proper nodes.

Create "dummy" cost object – for example, cost center – to de ne a CO account assignment for P&L account that is
relevant to cost accounting.

 Note
The result of the reporting of previous months is only supported on general ledger level. Details on subledgers are not
supported.

Migrate Cumulative Balances

Posting Period
Migrate cumulative balances for these "dummy" accounts only on the last day of each period, for example 31.01.2017. To prevent
errors, it is recommended that you close the current posting period after each migrated period. Only open the subsequent one
that is relevant for migration. However, it is possible that all periods are open during migration.

Offsetting Account
Always use the created "dummy" offsetting account as the offsetting account for migration of historical balances, as mentioned
in the Create "Dummy" G/L Accounts section of this guide.

Document Type
For migration, it is useful to use the document type 'UE', which classi es the documents as data transferred posting. This
assignment can help distinguish the migrated records from those posted manually. Furthermore, the number range assigned to
the associated documents is de ned based on the document type.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 7/20/2023

Reverse Balances
At the beginning of the following period, for example 01.02.2017, perform a mass reverse for the postings of the previously
migrated period. By doing so, the numbers that are shown in the nancial statement equal the balance of the particular period.

The mass reverse can be done via related business transaction. Here, all migrated documents for previous periods can be
ltered, for example by posting date, and reversed at the same time.

Cutover
If the cutover date is planned, for example for 30.09.2017, reverse migrated balances for 31.08.2017 only. Balances that are
migrated with cutover date 30.09.2017 are already part of proper subledgers. The balance sheet migration will be executed on
real G/L accounts – not on "dummy" accounts – and on subledger level.

This is custom documentation. For more information, please visit the SAP Help Portal 4