Purpose

The purpose of this document is to define the conversion approach to migrate TB PY in S/4 HANA. This is the opening balance of FY '26 ( for Group 1 ) or  opening balance of FY '27 ( for group 2 )

Amounts in legacy involve document currency, local currency and group currency. All currencies will be loaded accordingly unless there is a change in company design where local / group currency changes. Rates are as per the historical postings unless specific requirement calls for a fixed rate eg. group currency rate for consolidation purposes. Offsetting gl accounts in legacy documents will not be considered in this migration scope, they will be migrated in other objects scope eg. GL open item or GL balances.

Conversion Scope

The scope of this document covers the approach for converting active TB CY (Current year) from Legacy Source Systems into S/4HANA following the target design requirements.

As per the current plan, there are two go-lives - Group 1 and Group 2. 

1. Group 1 goes live on 1st July 2028 : TB Migration scope for this group is 1.5 Years worth of Balance starting from Opening Balance from January-2027
2. Group 2 goes live on 1st January 2029 : TB Migration scope for this group is 1.5 Years worth of Balance starting from Opening Balance from January-2028

Trial balance of January is the opening balance of the relevant fiscal year and will be migrated as the prior year closing balance. Thereafter, a carry forward of TB will be carried out by business after migration completion. In other words, migration posting date of the opening balance of January-2027 will be 31-12-2026 and migration posting date of the opening balance of January-2028 will be 31-12-2027.

Additional Information

• Balance Sheet migration strategy is different based on the below GL Types -

  • Non-Open item managed Balance Sheet Account

  • Open Item managed Balance Sheet Account

  • Reconciliation (Control) Accounts (including Inventory Account)

• Balance Sheet Account balances will be migrated as a two-step process -

• Opening Balance as on 31st December '26

• Year to date movement - Migrate year to date movement for each month until 31st December '26 for Group 1 company codes and until 31st June for Group 2 countries. 

• Balance of Reconciliation accounts, GL open item accounts and Inventory accounts will not be migrated against actual GL on 31st March/YTD. Instead, below take on account will be posted, and the actual account will be posted only on the cutover month end against subledger postings/open item postings.

  • ZZ00000001 (TBD)      GL Balance Take-On Account ( TB Migration Account )

  • ZZ00000002 (TBD)       Legacy GL Open Item offset Take on Account

  • ZZ00000003 (TBD)       Legacy Data AR Take on Account

  • ZZ00000004 (TBD)       Legacy Data AP Take on Account

  • ZZ00000005 (TBD)       Legacy Data Inventory Take on Account

  • ZZ00000006 (TBD)       Legacy Data Assets Take on Account

Following illustrations show how TB and Sub-Ledger Financial data migration will be carried out. 

AP Open Item migration with Respect to TB

GL Open Item Migration with Respect to TB

Inventory Stock migration with Respect to TB

Fixed Asset Migration with Respect to TB

WBS AUC Balance Migration With Respect to TB 

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

In ECC, parallel accounting was based on account approach.

e.g

Parallel accounting in target S4 is ledger based approach. In ledger-based approach assigns each principle to its own dedicated ledger with a 1:1 ratio between ledgers and principles.  The migration strategy typically involves a conversion from an existing classic G/L (often using the account approach) to the new G/L, then to S/4HANA.

for the same example above, migration to be done into local GAAP and IFRS ledger as below

Therefore, accounts as illustrated above need to be migrated through ledger-specific postings. (e.g FB01L instead of FB01). 

For the transfer of open items and Balance carryforward, the following applies:

• You can only manage open items in common accounts because the transfer of open items always applies to all ledgers and is not specific to individual ledgers.

• You have to transfer balances carried forward for individual ledgers, that is

  • Common accounts to all ledgers

  • Valuation-specific (parallel) accounts to the respective ledgers. 

A list of accounts to be identified for which IFRS GAAP to be posted against directly using IFRS ledger selection like done in tcode FB01L. 

Target Design

The technical design of the target for this conversion approach. 

Data Cleansing

Conversion Process 

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

1. The data exists. connects to the source and loads the data into . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

DCT is not applicable

Suggestion to add:

Decimal validation - Check table TCURX for the document currency key and if Decimals (TCURX-CURRDEC) is ‘0’, validate that no decimal value is populated.

Extraction Dependencies

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team.  This identifies the transformation activity required to allow to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool.  This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Transformation Rules

Note: 

Periodic balances of GL Accounts to be read from GLPCT/GLT0.

Note: for Each GL balance in scope of migration, an offset line to be created with the same GL Account. 

For the Field mapping transformation rules, wherever Rule 1 and Rule 2 denoted in the transformation logic column, please note that Rule 1 applies to main line ( GL Balance line ) and Rule 2 applies to offset line.

How to derive profit centres for various GL balance components: 

1. Inventory Balance Take-on Account:
   1. PF2:
      1. Stock balance data will be derived and structured at the profit centre level to ensure alignment with the target S/4HANA organisational structure.
      2. This dataset will provide stock balances at the material and plant level, which in turn will be mapped to the corresponding profit centres based on the material–plant–company code–profit centre mapping logic.
      3. The same distribution key (comprising Company Code, Profit Centre, and Stock Balance) will be applied to allocate the stock-related take-on GL account balances, derived from the source ECC GL balance data, ensuring accurate and consistent inventory take-on balances at the profit centre level.
   2. WP2:
      1. Stock balance data will be derived and structured at the profit centre level to ensure alignment with the target S/4HANA organisational structure.
      2. This dataset will provide stock balances at the material and plant level, which in turn will be mapped to the corresponding profit centres based on the material–plant–company code–profit centre mapping logic.
      3. The same distribution key (comprising Company Code, Profit Centre, and Stock Balance) will be applied to allocate the stock-related take-on GL account balances, derived from the source ECC GL balance data, ensuring accurate and consistent inventory take-on balances at the profit centre level.

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

oad

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Configuration

 Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load. 
• is in scope based on data design and any exception requested by business.

Change log

Workflow history