Status
Owner	Soumen Laru
Stakeholders	GARCIA-ext, Angel Luis PILLAY-ext, Lawrence

Purpose

The purpose of this document is to outline the conversion approach for migrating Trial Balance – Prior Year (TB PY) data into SAP S/4HANA.
This dataset represents the opening balances for FY2026 (for Group 1 company codes) and FY2027 (for Group 2 company codes).

The legacy trial balance data includes document currency, local currency, and group currency amounts. All currencies will be migrated accordingly, unless there are design changes affecting local or group currency configurations.
Exchange rates will be applied based on historical posting rates for each period end.

Conversion Scope

This document outlines the approach for converting Trial Balance – Current Year (TB CY) data from legacy source systems into SAP S/4HANA, in alignment with the target design and migration strategy.

As per the current implementation plan, there will be two separate go-live waves:

• Group 1: Go-live on 1st July 2028

  • TB migration scope: 1.5 years of balances, starting from the Opening Balance as at January 2027

• Group 2: Go-live on 1st January 2029

  • TB migration scope: 1 years of balances, starting from the Opening Balance as at January 2028

The January Trial Balance represents the opening balance of the respective fiscal year and will be migrated as the prior year closing balance.
Following migration, the carry-forward of balances into the next fiscal period will be performed by the business.

Accordingly, the migration posting dates for opening balances will be as follows:

• For January 2027, posting date: 31st December 2026

• For January 2028, posting date: 31st December 2027

List of source systems and approximate number of records 

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	TB PY		S4HANA
WP2	TB PY		S4HANA

Additional Information

The Balance Sheet migration approach will vary depending on the type of General Ledger (GL) Account, as outlined below:

1. Non–Open Item Managed Balance Sheet Accounts

2. Open Item Managed Balance Sheet Accounts

3. Reconciliation (Control) Accounts, including Inventory Accounts

The migration of Balance Sheet account balances will be executed in two stages:

1. Opening Balances

   • Opening balances will be migrated to establish the financial position at the start of the target fiscal year.
     For Group 1 company codes, the migration will be based on balances as at 31st December 2026, and for Group 2 company codes, as at 31st December 2027, in line with the current go-live schedule.

2. Year-to-Date (YTD) Periodic Movements

   • Monthly balance movements will be migrated progressively up to the following cut-off periods:

     • Group 1 company codes: up to 31st December 2026

     • Group 2 company codes: up to 30th June 2026

     This approach ensures that all interim financial movements are accurately reflected in the target system up to the designated migration period for each group

Migration Approach and handling in each period:

• For each period in scope, TB data will be migrated as life-to-date balances with the posting date set to the last day of the respective period.

• These entries will be reversed using mass reversal (T-code F.80) on the first day of the subsequent period.

• This approach ensures that open item managed lines are automatically reversed and cleared for all periods up to (but not including) the go-live period.

 

Approach of Migration of Balances of Sub-Ledger or Reconciliation Accounts:

• Balances related to Reconciliation Accounts, GL Open Item Accounts, and Inventory Accounts will not be migrated directly to their actual GL accounts as part of Trial balance Migration.
• Instead, these balances will be temporarily posted to designated Take-On Accounts during migration of Trial Balance ( TB).
  The corresponding actual GL accounts will be updated only at cutover month-end, in alignment with the migration of subledger or open item postings.

Note: GR/IR Open Item Account Balance Migration is not in scope of TB Migration and an approach is yet to be confirmed.

Take-On Accounts for Migration of Sub-Ledger Accounts:

Account	Description	Type	Generic Code ( For Illustration Purpose )
1199999	Fixed Asset Take-on Account - Intangibles	Legacy Data Assets Take on Account	ZZ00000006        Legacy Data Assets Take on Account
1299999	Goodwill - Take-on Account	Legacy Data Assets Take on Account	ZZ00000006        Legacy Data Assets Take on Account
1399999	Fixed Asset Tangibles (PP&E) - Take-on Account	Legacy Data Assets Take on Account	ZZ00000006        Legacy Data Assets Take on Account
1499999	RoU Assets - Take-on Account	Legacy Data Assets Take on Account	ZZ00000006        Legacy Data Assets Take on Account
2199999	Stock Take-on	Legacy Data Inventory Take on Account	ZZ00000005        Legacy Data Inventory Take on Account
2210999	Trade AR External - Take-on	Legacy Data AR Take on Account	ZZ00000003        Legacy Data AR Take on Account
2260999	Trade AR Take-on - I/C	Legacy Data AR Take on Account	ZZ00000003        Legacy Data AR Take on Account
2310999	Current Non-Trade AR Take-on - External	Legacy Data AR Take on Account	ZZ00000003        Legacy Data AR Take on Account
2360999	Current Non-Trade AR Take-on - I/C	Legacy Data AR Take on Account	ZZ00000003        Legacy Data AR Take on Account
5210999	Current Trade AP Take-on - External	Legacy Data AP Take on Account	ZZ00000004        Legacy Data AP Take on Account
5260999	Current Trade AP Take-on - I/C	Legacy Data AP Take on Account	ZZ00000004        Legacy Data AP Take on Account
5310999	Current Non-Trade AP Take-on - External	Legacy Data AP Take on Account	ZZ00000004        Legacy Data AP Take on Account
5360999	Current Non-Trade AP Take-on - I/C	Legacy Data AP Take on Account	ZZ00000004        Legacy Data AP Take on Account
5210997	GR/IR Take-on - Freight & Customs	Legacy Data GR/IR Take-On Account	ZZ00000008       Legacy GR/IR Take-On Account
5210998	GR/IR Take-on - Goods/Services	Legacy Data GR/IR Take-On Account	ZZ00000008       Legacy GR/IR Take-On Account
5310998	GL Balance Migration Account	Legacy GL Balance Migration Account	ZZ00000001       GL Balance Take-On Account ( TB Migration Account )

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

• AR Open Item migration with Respect to TB

• 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

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

In the SAP ECC system, parallel accounting was implemented using the account-based approach. But, In the SAP S/4HANA target system, parallel accounting is instead managed through the ledger-based approach using multiple ledgers.

The account-based approach was implemented differently across the source systems, specifically in PF2 and WP2.

In the case of PF2, parallel accounting was handled by performing reversal postings to designated contra accounts, followed by repostings to the corresponding local (main) accounts. This approach allowed the system to maintain multiple accounting perspectives on the same transactions while ensuring that the balances in local accounts accurately reflected the intended financial position.

e.g

In SAP S/4HANA, parallel accounting is implemented using a ledger-based approach. In this approach, each accounting principle is assigned to a dedicated ledger, establishing a 1:1 relationship between ledgers and accounting principles.

TB migration strategy involves converting the existing classic G/L (based on the account approach) to the new G/L. 

For the example provided, the migration will be executed into the Local GAAP and IFRS ledgers, in accordance with the sample data presented in the ECC system illustration.

In the case of WP2, parallel accounting was handled by performing Delta postings to the corresponding local (main) accounts. This approach allowed the system to maintain multiple accounting perspectives on the same transactions while ensuring that the balances in local accounts accurately reflected the intended financial position.

e.g

In SAP S/4HANA, parallel accounting is implemented using a ledger-based approach. In this approach, each accounting principle is assigned to a dedicated ledger, establishing a 1:1 relationship between ledgers and accounting principles.

TB migration strategy involves converting the existing classic G/L (based on the account approach) to the new G/L. 

For the example provided, the migration will be executed into the Local GAAP and IFRS ledgers, in accordance with the sample data presented in the ECC system illustration.

Accordingly, the accounts illustrated above must be migrated using ledger-specific postings (e.g., FB01L instead of FB01).

For the transfer of open items and balance carryforward, the following rules apply:

• Open Items:
  Open items can only be managed in common accounts, as their transfer affects all ledgers and is not specific to individual ledgers.

• Balance Carryforward:
  Balances must be transferred per ledger as follows:

  • Common accounts: carried forward to all ledgers

  • Valuation-specific (parallel) accounts: carried forward to their respective ledgers

A list of accounts must be identified for which IFRS balances will be posted directly to the IFRS ledger, using ledger-specific posting (similar to transaction FB01L).

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach. 

Table	Field	Data Element	Field Description	Data Type	Length (Decimals)	Requirement
ACDOCA	BUKRS	BUKRS	Company Code	CHAR	30	Mandatory Note: More details described in the Transformation Rules
ACDOCA	LDGRP	LDGRP	Ledger Group	CHAR	30	Mandatory Note: More details described in the Transformation Rules
ACDOCA	XBLNR	XBLNR	Reference Document Number	CHAR	16	Optional Note: More details described in the Transformation Rules
ACDOCA	DOCLN	DOCLN	Line Item Number	Number	6	Mandatory Note: More details described in the Transformation Rules
ACDOCA	HKONT	HKONT	G/L Account	CHAR	30	Mandatory Note: More details described in the Transformation Rules
ACDOCA	GKONT	GKONT	Offsetting Account	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	BLART	BLART	Document Type	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	BUDAT	BUDAT	Posting Date	Date		Mandatory Note: More details described in the Transformation Rules
ACDOCA	BLDAT	BLDAT	Document Date	Date		Mandatory Note: More details described in the Transformation Rules
ACDOCA	WWERT	WWERT	Translation Date	Date		Optional Note: More details described in the Transformation Rules
ACDOCA	ACC_PRINCIPLE	ACC_PRINCIPLE	Accounting Principle	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	BKTXT	BKTXT	Header Text	CHAR	25	Mandatory Note: More details described in the Transformation Rules
ACDOCA	SGTXT	SGTXT	Item Text	CHAR	50	Mandatory Note: More details described in the Transformation Rules
ACDOCA	WAERS	WAERS	Transaction Currency	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	WRBTR	WRBTR	Amount	Number	23	Mandatory Note: More details described in the Transformation Rules
ACDOCA	HWAER	HWAER	Company Code Currency	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	DMBTR	DMBTR	Amount	Number	23	Mandatory Note: More details described in the Transformation Rules
ACDOCA	HWAE2	HWAE2	Group Currency	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	DMBE2	DMBE2	Amount	Number	23	Mandatory Note: More details described in the Transformation Rules
ACDOCA	HWAE3	HWAE3	Freely Defined Currency	CHAR	80	Mandatory Note: More details described in the Transformation Rules
ACDOCA	DMBE3	DMBE3	Amount	Number	23	Optional Note: More details described in the Transformation Rules
ACDOCA	RASSC	RASSC	Company ID of Trading Partner	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	ZUONR	ZUONR	Assignment Number	CHAR	18	Mandatory Note: More details described in the Transformation Rules
ACDOCA	RMVCT	RMVCT	Transaction Type	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	PERNR	PERNR	Personnel Number of Employee	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	VALUT	VALUT	Value Date	Date		Optional Note: More details described in the Transformation Rules
ACDOCA	HBKID	HBKID	Short Key for House Bank	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	HKTID	HKTID	ID for Account Details	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	KOSTL	KOSTL	Cost Center	CHAR	80	Conditional Note: More details described in the Transformation Rules
ACDOCA	PRCTR	PRCTR	Profit Center	CHAR	80	Conditional Note: More details described in the Transformation Rules
ACDOCA	XREF1	XREF1	Reference key 1 for line item	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	XREF1	XREF2	Reference key 2 for line item	CHAR	80	Optional Note: More details described in the Transformation Rules
ACDOCA	XREF1	XREF3	Reference key 3 for line item	CHAR	80	Optional Note: More details described in the Transformation Rules

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
N/A

Conversion Process 

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

Extraction Run Sheet

Req #	Requirement description	Team responsible
1.	Ensure source tables GLPCT, GLT0, COEP are extracted in tool according to the agreed cut-off date in the project plan	Data team
2.	Perform preliminary completeness check documented in section 5.2.8.1.1	Data team
3.	Raise issues as defects if Req # 1 to 2 are not met	Data team
4.	Repeat Req # 1 to 3 if required	Data team
5.	Report extraction result to person in charge of APOI conversion	Data team

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

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

<Object> DCT Rules

DCT is not applicable

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step description	Team responsible
1.	Any period / year end close activities have been fully completed	Business
2.	Reconciliation for intercompany payables have been completed, and adjustment made in legacy SAP system	Business
3.	Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items	Business and Data

Transformation

The target fields are mapped to the corresponding legacy source fields through a three-way collaboration involving the Business, Functional, and Data teams. This process establishes the necessary data transformations to make the data target-ready, and typically involves the following steps:

1. Value Mapping and Transformation:

   • Map legacy values to the corresponding to-be values, including the assignment of default values where applicable.

   • Apply transformation rules as defined to ensure consistency and compliance with the target system requirements.

2. Preparation of Target-Ready Data:

   • Structure and format the data according to the requirements in the Syniti ADMM Migrate

   • Generate the load-ready dataset, which can then be used by the business team to perform pre-load data validation.

Transformation Run Sheet

Item #	Step description	Team responsible
1.	Ensure all the fields that require value mapping, as stipulated  Mapping tables, have the latest signed-off mapping files imported into toolMigrate.	Data team
2.	In tool, select the Trial Balance object PY.	Data team
3.	Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY.	Data team
4.	Launch the Objects to execute transformation.	Data team
5.	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
6.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
8.	Log errors as defects, if any and address resolutions. Close defects.	Data team
9.	Re-transform and re-validate the Pre-load reports if necessary.	Data team
10.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11.	Analyse and resolve any pre-load defects logged by business.	Data team
12.	Repeat steps 6 to 11 if necessary	Data team
13.	Proceed to pre-load validations	Data team

Transformation Rules

The extraction of General Ledger (GL) balance data from the source system will be performed using one of the following approaches:

Option 1 – Ledger-Based Extraction:

Periodic balances of General Ledger (GL) accounts will be extracted directly from the GLPCT and GLT0 tables. This approach is recommended when the ledger tables provide a complete and reconciled view of financial balances as of the cut-over date.

In the legacy systems (ECC – PF2, WP2, and PI2), document splitting and profit centre balancing functionalities are not enabled. As a result, only Profit and Loss (P&L) account balances are available at the profit centre level within the ledger tables.

Accordingly:

• Balance Sheet account balances will be extracted from GLT0, as these balances are not maintained in GLPCT.

• P&L account balances will be extracted from GLPCT, where profit centre-level balances are available.

• The combined dataset from GLPCT and GLT0 will provide a complete representation of all account balances required for migration.

It should be noted that records extracted from GLPCT contain profit centre information, whereas records from GLT0 do not. Consequently, a significant number of account lines will not include profit centre details. These lines will need to be managed either by assigning default profit centres or by allocating balances based on subledger-level data to ensure accurate profit centre reporting in the target system.

Option 2 – Transaction-Based Extraction:

All transactional line items will be extracted from the BSEG table and subsequently aggregated at the relevant key field level — Company Code, GL Account, Posting Period, Fiscal Year, Profit Centre, Cost Centre, and Transaction Currency — to derive the General Ledger (GL) balances.

This approach is suitable in scenarios where a detailed reconstruction of balances is required, or where ledger tables are not fully aligned with the underlying transactional data.

Additionally, this method enables the generation of Trial Balances that include both the key financial attributes (such as Company Code, GL Account, Period, Fiscal Year, Profit Centre, Cost Centre, Transaction Currency) and extended analytical dimensions (such as Transaction Type, XREF1, XREF2, etc.), thereby providing enhanced traceability and reconciliation capability.

Recommended Approach for S/4HANA Migration:
For migration to S/4HANA, the ledger-based extraction approach (Option 1) is recommended. This method ensures alignment with the source system’s reconciled balances, simplifies reconciliation during cut-over, and provides a structured foundation for subsequent profit centre enrichment where required. The transaction-based extraction (Option 2) may only be considered in exceptional cases where ledger balances are incomplete or reconciliation discrepancies are identified and balances are needed at the additional attribute level like transaction type. 

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

In Migration cockpit, offset account number field is set in the same line and therefore, it will create offset line on its own. So, transformed data will be one line for each legacy in-scope line but will be automatically created with an offset line. 

Posting Date ( which is generally the cut-over date ) is not part of the template, as posting date will be maintained by the Syensqo data team in the view FINSV_MIG_CTRL_1. This posting date will be used across all the financial transactions migrations ( exception is Trial Balance ).

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table	Target Field	Target description	Transformation logic
1	ECC	(GLT0+GLPCT)/ BKPF+BSEG	BUKRS	Company Code	S/4HANA	ACDOCA	BUKRS	Company Code	Map Company Code from ECC to S4 Mapping File Location:
2	ECC	(GLT0+GLPCT)/ BKPF	LDGRP	Ledger Group	S/4HANA	ACDOCA	LDGRP	Ledger Group	Default to '0L'
3	ECC	(GLT0+GLPCT)/ BKPF+BSEG	XBLNR	Reference Document Number	S/4HANA	ACDOCA	XBLNR	Reference Document Number	To be kept Blank
4	ECC	(GLT0+GLPCT)/ BKPF	DOCLN	Line Item Number	S/4HANA	ACDOCA	DOCLN	Line Item Number	Sequential number ( Part of ADMM tool build) for each summarized balance lines.
5	ECC	(GLT0+GLPCT)/ BKPF+BSEG	HKONT	G/L Account	S/4HANA	ACDOCA	HKONT	G/L Account	Map Old GL Account to new GL Account Note: For each Sub-ledger Accounts ( Fixed Asset, Customer, Vendor, GR/IR Open items, Inventory Accounts), standard mapping to be replaced with Take-on Accounts.  In the GL Account Mapping File, additional target mapping will be given to contain take-on account.
6	ECC	(GLT0+GLPCT)/ BKPF	GKONT	Offsetting Account	S/4HANA	ACDOCA	GKONT	Offsetting Account	TB Balance Offset Account ( Account Number:  5310998  )
7	ECC	(GLT0+GLPCT)/ BKPF+BSEG	BLART	Document Type	S/4HANA	ACDOCA	BLART	Document Type	Default to '9S'
8	ECC	(GLT0+GLPCT)/ BKPF	BLDAT	Document Date	S/4HANA	ACDOCA	BLDAT	Document Date	Same as the posting Date ( Last date of each period including opening balance )
9	ECC	(GLT0+GLPCT)/ BKPF+BSEG	WWERT	Translation Date	S/4HANA	ACDOCA	WWERT	Translation Date	Keep it blank
11	ECC	(GLT0+GLPCT)/ BKPF+BSEG	BKTXT	Header Text	S/4HANA	ACDOCA	BKTXT	Header Text	Set to Concatenation of "DM:", Legacy BUKRS, Period ( Year + Period )
12	ECC	(GLT0+GLPCT)/ BKPF	SGTXT	Item Text	S/4HANA	ACDOCA	SGTXT	Item Text	Set to ECC Account Number (HKONT), ECC Profit Centre, ECC Transaction Type
13	ECC	(GLT0+GLPCT)/ BKPF+BSEG	WAERS	Transaction Currency	S/4HANA	ACDOCA	WAERS	Transaction Currency	Use Currency Key Mapping File Mapping File Location:
14	ECC	(GLT0+GLPCT)/ BKPF	WRBTR	Amount	S/4HANA	ACDOCA	WRBTR/TSL	Amount	This is for currency type 00 Copy as is with Signage as '-' if the posting key is 50 or else '+' Also consider Currency Adjustment During Migration (TCURX Consideration) below this table
15	ECC	(GLT0+GLPCT)/ BKPF+BSEG	HWAER	Company Code Currency	S/4HANA	ACDOCA	HWAER	Company Code Currency	Automatic, to be kept blank in load template
16	ECC	(GLT0+GLPCT)/ BKPF	DMBTR	Amount	S/4HANA	ACDOCA	DMBTR/HSL	Amount	This is for currency type 10 Copy as is with Signage as '-' if the posting key is 50 or else '+' Also consider Currency Adjustment During Migration (TCURX Consideration) below this table
17	ECC	(GLT0+GLPCT)/ BKPF+BSEG	HWAE2	Group Currency	S/4HANA	ACDOCA	HWAE2	Group Currency	Automatic, to be kept blank in load template
18	ECC	(GLT0+GLPCT)/ BKPF	DMBE2	Amount	S/4HANA	ACDOCA	DMBE2/KSL	Amount	Group Currency 2 This is for currency type 30 ( Global currency / Group currency ) Note: Currently, legacy does not have group currency amount, the plan is let exchange rate to populate this.
19	ECC	(GLT0+GLPCT)/ BKPF+BSEG	HWAE3	Freely Defined Currency	S/4HANA	ACDOCA	HWAE3	Freely Defined Currency	Automatic, to be kept blank in load template
20	ECC	(GLT0+GLPCT)/ BKPF	DMBE3	Amount	S/4HANA	ACDOCA	DMBE3/VSL	Amount	Group Currency 2 This is for currency type 31 ( Freely Defined currency type 2 ) Note: Currently, legacy does not have group currency amount, This is yet to be confirmed as to how this will be derived, Copy as is with Signage as '-' if the posting key is 50 or else '+' Also consider Currency Adjustment During Migration (TCURX Consideration) below this table
21	ECC	(GLT0+GLPCT)/ BKPF+BSEG	RASSC	Company ID of Trading Partner	S/4HANA	ACDOCA	RASSC	Company ID of Trading Partner	to be kept empty
22	ECC	(GLT0+GLPCT)/ BKPF	ZUONR	Assignment Number	S/4HANA	ACDOCA	ZUONR	Assignment Number	to be kept empty
23	ECC	(GLT0+GLPCT)/ BKPF+BSEG	BEWAR	Transaction Type	S/4HANA	ACDOCA	RMVCT	Transaction Type	The population of this field will vary depending on the Trial Balance extraction approach: Option 1: If the TB is derived from GLT0 / GLPCT, this field will remain blank. Option 2: If the TB is derived from BSEG, this field will be Mapped Location of Mapping file:
25	ECC	(GLT0+GLPCT)/ BKPF	VALUT	Value Date	S/4HANA	ACDOCA	VALUT	Value Date	to be kept empty
26	ECC	(GLT0+GLPCT)/ BKPF+BSEG	HBKID	Short Key for House Bank	S/4HANA	ACDOCA	HBKID	Short Key for House Bank	to be kept empty
27	ECC	(GLT0+GLPCT)/ BKPF	HKTID	ID for Account Details	S/4HANA	ACDOCA	HKTID	ID for Account Details	to be kept empty
28	ECC	(GLT0+GLPCT)/ BKPF+BSEG	KOSTL	Cost Center	S/4HANA	ACDOCA	KOSTL	Cost Center	Lookup S4HANA target table CSKS by passing mapped new S4 Profit Centre (PRCTR).  However, this mapping applies only to P&L accounts, excluding revenue accounts. Determine Account Type: Identify if the GL Account is a P&L Account based on the Account Type in SKA1 / SKB1 (e.g., not a balance sheet account) by confirming Balance Sheet indicator = ‘P’ or Account Type = ‘X’ in SKA1/SKB1 Exclude Revenue Accounts: Join with CSKSB (Cost Element: Basic Data) using key field KSTAR (Cost Element = GL Account). Exclude records where CSKSB.KATYP = '11' (Revenue Cost Element Category). For remaining (non-revenue) P&L accounts, perform lookup on CSKS using the mapped new S/4 Profit Centre to find a cost centre (KOSTL) to be mapped here.
29	ECC	(GLT0+GLPCT)/ BKPF	PRCTR	Profit Center	S/4HANA	ACDOCA	PRCTR	Profit Center	Map Old Profit Centre to New Profit Centre Note:  For line items missing profit centres, a generic(across all financial transaction objects) enrichment construct page in ADM containing company code, default profit centre will be used to populate a default profit centre. Further discussions will be necessary on this.
30	ECC	(GLT0+GLPCT)/ BKPF	XREF1	Reference key for line item	S/4HANA	BSIS	XREF1	Reference key for line item	The population of this field will vary depending on the Trial Balance extraction approach: Option 1: If the TB is derived from GLT0 / GLPCT, this field will remain blank. Option 2: If the TB is derived from BSEG, this field will be carried forward as-is.
31	ECC	(GLT0+GLPCT)/ BKPF	XREF2	Reference key for line item	S/4HANA	BSIS	XREF2	Reference key for line item	The population of this field will vary depending on the Trial Balance extraction approach: Option 1: If the TB is derived from GLT0 / GLPCT, this field will remain blank. Option 2: If the TB is derived from BSEG, this field will be carried forward as-is.
32	ECC	(GLT0+GLPCT)/ BKPF	XREF3	Reference key for line item	S/4HANA	BSIS	XREF3	Reference key for line item	The population of this field will vary depending on the Trial Balance extraction approach: Option 1: If the TB is derived from GLT0 / GLPCT, this field will remain blank. Option 2: If the TB is derived from BSEG, this field will be carried forward as-is.

Currency Adjustment During Migration (TCURX Consideration)

In SAP, the TCURX table defines the number of decimal places used for each currency.
This impacts how amounts are stored internally in database tables versus how they are displayed externally in user interfaces or reports.

Currencies such as JPY (Japanese Yen), KRW (Korean Won), or VND (Vietnamese Dong) are typically configured with no decimal places (TCURX-CURRDEC = 0).

Understanding and correctly applying the TCURX rules is essential during data migration to ensure financial consistency between ECC and S/4HANA.

Internal vs External Currency Representation example:

External Amount	The amount value as displayed to users in SAP screens and reports.	96015 JPY
Internal Amount	The amount value stored in database tables for computation.	960.15	Multiplied by factor = 10² if target has 2 decimals

 During data migration, these internal (technical) amounts must be converted to external amounts to ensure accuracy and consistency in the target S/4HANA system.

Conversion Formula:

External Amount =  Internal Amount * 10 to the power ( 2 - Number of decimal for the currency in TCURX table )

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.
2. Fixed Assets Take-On Account
   1. PF2:
      1. Fixed Assets are associated with Cost Centres, enabling straightforward derivation of the corresponding Profit Centres through existing master data mappings.
      2. Once Profit Centre mapping is established, the Asset Cost and Accumulated Depreciation balances will be segregated by Profit Centre accordingly.
      3. Subsequently, the Asset take-on GL account balances extracted from the source ECC GL balance data will be distributed across Profit Centres based on the derived split details, ensuring consistency between Asset subledger and General Ledger balances during migration at the profit centre level.
   2. WP2:
      1. Fixed Assets are associated with Cost Centres, enabling straightforward derivation of the corresponding Profit Centres through existing master data mappings.
      2. Once Profit Centre mapping is established, the Asset Cost and Accumulated Depreciation balances will be segregated by Profit Centre accordingly.
      3. Subsequently, the Asset take-on GL account balances extracted from the source ECC GL balance data will be distributed across Profit Centres based on the derived split details, ensuring consistency between Asset subledger and General Ledger balances during migration at the profit centre level.
3. AR Take-On Account
   1. PF2:
      1. The Business Area will be used to derive the corresponding Profit Centre via the Cost Centre to which the Business Area is assigned, for the AR Open Item data.
      2. AR Open Items will be aggregated at the Company Code and Profit Centre levels.
      3. The aggregated data will then be used to allocate the AR Take-on GL Account balances by Profit Centre, ensuring reconciliation and alignment between subledger and general ledger balances at the profit centre level during migration.
   2.  WP2: No process yet to derive PC
   3. PI2:  No Process yet to derive PC
4. AP Take-On Account
   1. PF2:
      1. The Business Area will be used to derive the corresponding Profit Centre via the Cost Centre to which the Business Area is assigned, for the AR Open Item data.
      2. AR Open Items will be aggregated at the Company Code and Profit Centre levels.
      3. The aggregated data will then be used to allocate the AR Take-on GL Account balances by Profit Centre, ensuring reconciliation and alignment between subledger and general ledger balances at the profit centre level during migration.
   2.  WP2: No process yet to derive PC
   3. PI2:  No Process yet to derive PC

Note: A default Profit Center will be maintained for each company code in ADMM and will be applied in cases where Profit Center derivation is not possible due to unavailable data.

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
Company Code	Mapping of legacy company codes to target system value
GL Account	Mapping of legacy GL accounts to target system value
Profit Centre	Mapping of legacy Profit Center to target system value
Cost Centre	Mapping of legacy Cost Centre to target Cost Centre

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.	Data team

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Based on S/4HANA target design fields, account field status groups and tax settings Check if records have all mandatory fields filled and mapped, otherwise they should be flagged as error. Check GL Accounts are extended to required company code Field combination of SAKNR and BUKRS to be checked against SKB1. Cost-Centre Validity Period Check KOSTL against CSKS-DATBI>= Cut-Over Date ( Parameter Based ) Check signage of amount. Sum of total balance of combination fields BUKRS, SAKNR, PRCTR and KOSTL is zero for each currency types ( WRBTR, DMBTR, DMBE2 and DMBE3 )  Total balance of All the accounts for each BUKRS is zero.
Reconciliation of total	Record Summation  Check the sum of record count of the TB Balance ( PY )  in the load file is the same as source. The record count for TB Balance ( PY )  will be done on the group basis. The fields in the group are consist of: Company Code, GL Account, Profit Centre Check Amount in Document Currency and Local Currency Check the sum of the amount in Document Currency and Local Currency in load file is the same as source. If any of the sum is different, flag the record as error.

Accuracy

Task	Action
Mandatory field mapping and transformation	Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.  Review the data report to ensure mapping value is not missing in tool. Capture errors in the Data Error report.

Business

The following pre-load validations will be performed by the business.

Completeness

Task

Action

Verify record count in Pre-load reports by region

In legacy system, execute report AP Line Item Display (t/code: FS10N ) with selection parameters stated in section 7.2.  Group the output of the report by Company Code, GL Account and Profit Centre using subtotal function and compare the count in this report against the TB Balance ( PY )  count in the pre-load file. The record count for TB Balance ( PY )  may also be done on the more granular level. The recommended granular level or the subtotal fields can consist of: Company Code, Vendor, Profit Centre, Document Currency Key, Company ID for Trading Partner. If any of the count is different, raise defect and flag the relevant record as error.

Accuracy

Task	Action
Conversion accuracy	Verify TB Lines are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. In legacy system, execute report Trial Balance Display (t/code: FS10N ) with selection parameters. If any of the sum is different, raise defect and flag the relevant record as error.
Business partner balance on Company code and profit center level	Check the total open item amount on Business partner at Company Code and Profit center level, against the total in legacy by Document, Local and Group currency. Apply currency rules where applicable

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

Item	Step description	Team responsible
1	Ensure the load tools are transported into the correct tool instance.	Data team
2	Ensure DCTs and all required mappings are submitted and complete	Data team
3	Ensure Pre-load sign-offs are obtained.	Data team
4	Execute tool Trial Balance Upload	Data team
5	Generate the post load reports in tool.	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	Data team

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence 

Item #	Configuration item
1.	Company code-related configuration (posting period variant).
2.	Finance posting (document types, document number ranges, special gl indicator)
3.	Currencies (currency keys, decimal places in currencies)

 Conversion Objects

Object #	Preceding Object Conversion Approach
1067	GL Account Operational CoA (incl. secondary CE)
1073	Profit center

Error Handling

The table below depicts some possible system errors for this data object during data load.  All data load error is to be logged as defect and managed within the Defect Management

Error type	Error description	Action taken
Posting Period Error	Posting period is blocked for posting	Review project / cutover plan and ensure posting periods can be opened for postings
Profit Centre does not exist	Profit centre does not exist in company code	Ensure the profit centre mapping is correct and or create the profit centre if it is valid

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task

Action

Reconciliation of Record Count

Total number of records loaded for TB Balance ( PY )  will be generated in the Post-load reports in tool based on the target table and fields mentioned in section 3. The reconciliation needs to be executed on the total number of ‘valid’ records and currency amount per company code in the source compared to total number of records and currency amount in S/4HANA Record Count Check the sum of record count of the open items in the load file is the same as S/4HANA. The record count for TB Balance ( PY )  will be done on the group basis. The fields in the group are consist of: Company Code, Vendor Account Check Amount in Document Currency and Local Currency Check on line item level that the sum of the amount in Document Currency and Local Currency in the load file is the same as posted in S/4HANA. If any of the sum is different, flag the record as error.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code FAGLB03 – or equivalent report in Fiori App to display loaded TB Balance ( PY )  in S/4HANA and compare results against the pre-load reports generated from tool.

Accuracy

Task	Action
Open items totals	Check business partner open item totals by Business partner, Company code, profit centre. Totals should be checked in Document, Local and Group currency.
Spot check	Business should choose some business partners and perform comprehensive check of open items, payment terms etc Such partners should have huge number of open items or be critical for payment runs in S4 or have certain complexity in conversion.

Key Assumptions

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

Any additional key assumptions.

Change log

Workflow history