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.

Relevancy criteria:

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 ( Only balance sheets including retained earning account ). It will be posted on the last day of the prior year’s final posting period, followed by a carry-forward. Therefore, The opening balances for January 2027 will be migrated as the closing balances from 2026 after the execution of a balance carry-forward by the business. 

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

  • TB migration scope: 1 years of balances, starting from the Opening Balance as at January 2028 ( Only balance sheets including retained earning account ). It will be posted on the last day of the prior year’s final posting period, followed by a carry-forward. Therefore, The opening balances for January 2028 will be migrated as the closing balances from 2027 after the execution of a balance carry-forward by the business. 

Note:  There will be no carryforward of the prior-year TB balance. Instead, it will be reversed on the first day of the current year and reinstated at the end of the first period (January) as a life-to-date balance, including the retained earnings account.

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 the approximate number of records. Balances from all three systems must be extracted in full.

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	TB PY	N/A	S4HANA	N/A
WP2	TB PY	N/A	S4HANA	N/A
PI2	TB PY	N/A	S4HANA	N/A

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.

Note: Although this document references the trial balance migration across all periods, it specifically focuses on the opening balance migration. The carried-forward balances from the legacy system will form the opening balances, which will be posted using the last day of the preceding fiscal year, followed by a balance carryforward process.

• • Group 1: The carried-forward balances from FY 2027 will form the opening balances and will be posted with a posting date of 31st December 2026.

  • Group 2: The carried-forward balances from FY 2028 will form the opening balances and will be posted with a posting date of 31st December 2027.

1. 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 30th June 2028

     • Group 2 company codes: up to 31st December 2028

     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. Risks will be minimised by selecting individual entities during the reversal process, ensuring that no incorrect company codes or fiscal periods are reversed accidentally.

• 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, 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.
• Upon completion of go-live and the reconciliation process, all take-on accounts must be fully cleared and subsequently blocked for any future postings.

Approach of Migration of Balances of Open-Item Managed GL Accounts:

• For Periodic Movements Including Opening Balance, TB for open item managed accounts will be migrated into their mapped target mapped accounts. Reversal posting for each period will ensure automatic clearing of these lines items ensuring there will be no residual open item lines at the go-live period (posting date = cutover date), 

• During go-live (posting date = cutover date), balances of open item–managed accounts ( Included in CNV-9010 GL Open Items) will be migrated into GL take-on account 5310998 (in place of the actual accounts) as part of the Trial Balance migration process. GL take-on account 5310998 is the same account as Trial Balance offset account

• Subsequently, CNV-9010 GL Open Items will be migrated with offset lines recorded in the trial balance offset account 5310998, ensuring alignment between the trial balance and open item data.

• This ensures data accuracy and prevents duplicate or additional open items requiring clearing.

Note: The migration of GR/IR open item balances will be posted to the designated take-on accounts, while the cutover approach for transferring these balances to the actual GR/IR accounts (most probably into some manual GR/IR account ) is still pending finalization by the S2P stream.

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 )

An very important point to be noted here. 

For non–cut-over periods, multiple take-on accounts—"based on the GL Account Mapping for Migration"—will be used for the various sub-ledger types. However, during the cut-over period, only one designated account will be used for each individual sub-ledger (as listed below). Syniti team will need to apply right logic in the transformation to take care of this.  Refer to Transform section for the field HKONT.

Account	Description	Type	Generic Code ( For Illustration Purpose )
1399999	Fixed Asset Tangibles (PP&E) - Take-on Account	Legacy Data Assets Take on Account	ZZ00000006        Legacy Data Assets Take on Account
2210999	Trade AR External - Take-on	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
2199999	Stock Take-on	Legacy Data Inventory Take on Account	ZZ00000005        Legacy Data Inventory Take on Account
5310998	GL Balance Migration Account	Legacy GL Balance Migration Account	ZZ00000001       GL Balance Take-On Account ( TB Migration Account )

Note: The migration GL account mapping will specify the mapping details for each sub-ledger type during non cut-over periods. A separate GL account mapping will be used to define the mapping details for each sub-ledger type specifically for the cut-over period.

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.

Separate conversion specs describe the migration of balances into local accounts. To maintain simplicity, A Data Construction Sheet  will be created to list all local accounts, enabling their exclusion from the leading ledger migration. The migration of balances for local accounts will be described in the following two conversion specifications: 

• CNV-9016 TB PY (Legal Val - Local GAAP)  - Opening balance
• CNV-9014 TB CY (Legal Val - Local GAAP) mntly mvmt - Periodic movement.

In general, account numbers (Legacy SAKNR from the source tables) that begin with an alphabetic character (A–Z) are considered Local Accounts and should therefore be excluded from the IFRS trial balance migration.

The Trial Balance migration executed through the object ‘CNV-9015 TB PY’ will post values to both the IFRS and Local (LG) ledgers. Subsequently, the Local Ledger (LG) will be migrated again using ‘CNV-9016 TB PY (Legal Val – Local GAAP)’, which will recalculate the legacy local account balances and adjust for the amounts already posted via ‘CNV-9015 TB PY’.

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	4	Mandatory Note: More details described in the Transformation Rules
ACDOCA	LDGRP	LDGRP	Ledger Group	CHAR	2	Optional Note: More details described in the Transformation Rules
BKPF	XBLNR	XBLNR	Reference Document Number	CHAR	16	Mandatory Note: More details described in the Transformation Rules
ACDOCA	DOCLN	DOCLN	Line Item Number	CHAR	6	Mandatory Note: More details described in the Transformation Rules
ACDOCA/BSEG	RACCT/ HKONT	RACCT/ HKONT	G/L Account	CHAR	10	Mandatory Note: More details described in the Transformation Rules
BKPF	BLART	BLART	Document Type	CHAR	2	Mandatory Note: More details described in the Transformation Rules
BKPF	BUDAT	BUDAT	Posting Date	Date		Mandatory Note: More details described in the Transformation Rules
BKPF	BLDAT	BLDAT	Document Date	Date		Mandatory Note: More details described in the Transformation Rules
BKPF	WWERT	WWERT	Translation Date	Date		Optional Note: More details described in the Transformation Rules
BKPF	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
BSEG	WAERS	WAERS	Transaction Currency	CUKY	5	Mandatory Note: More details described in the Transformation Rules
BSEG	WRBTR	WRBTR	Amount	CURR	23	Mandatory Note: More details described in the Transformation Rules
BSEG	H_HWAER	HWAER	Company Code Currency	CUKY	5	Optional Note: More details described in the Transformation Rules
BSEG	DMBTR	DMBTR	Amount	CURR	23	Mandatory Note: More details described in the Transformation Rules
BSEG	H_HWAE2	HWAE2	Group Currency	CUKY	5	Optional Note: More details described in the Transformation Rules
BSEG	DMBE2	DMBE2	Amount	CURR	23	Mandatory Note: More details described in the Transformation Rules
BSEG	H_HWAE3	HWAE3	Freely Defined Currency	CUKY	5	Optional Note: More details described in the Transformation Rules
BSEG	DMBE3	DMBE3	Amount	CURR	23	Optional Note: More details described in the Transformation Rules
ACDOCA	RASSC	RASSC	Company ID of Trading Partner	CHAR	6	Optional Note: More details described in the Transformation Rules
ACDOCA	ZUONR	ZUONR	Assignment Number	CHAR	18	Optional Note: More details described in the Transformation Rules
ACDOCA	RMVCT	RMVCT	Transaction Type	CHAR	3	Optional Note: More details described in the Transformation Rules
ACDOCA	PERNR	PERNR	Personnel Number of Employee	NUMC	8	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	5	Optional Note: More details described in the Transformation Rules
ACDOCA	HKTID	HKTID	ID for Account Details	CHAR	5	Optional Note: More details described in the Transformation Rules
ACDOCA	RMVCT	RMVCT	Transaction Type	CHAR	4	Optional Note: More details described in the Transformation Rules
BSEG	VBUND	VBUND	Trading Partner	CHAR	6	Optional Note: More details described in the Transformation Rules
BSEG/ACDOCA	KOSTL/RCNTR	KOSTL	Cost Center	CHAR	10	Conditional Note: More details described in the Transformation Rules
ACDOCA	PRCTR	PRCTR	Profit Center	CHAR	10	Conditional Note: More details described in the Transformation Rules
BSEG	XREF1	XREF1	Reference key 1 for line item	CHAR	12	Optional Note: More details described in the Transformation Rules
BSEG	XREF1	XREF2	Reference key 2 for line item	CHAR	12	Optional Note: More details described in the Transformation Rules
BSEG	XREF1	XREF3	Reference key 3 for line item	CHAR	20	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.

Note: Although both DCT-based data and extraction-based data approaches are possible, the extraction-based data option applies in this case.

Extraction Run Sheet

Req #	Requirement description	Team responsible
1.	Ensure that the source tables GLT0 (for the company codes within scope for each group and fiscal years covering the last two years or later) are extracted into the tool in accordance with the agreed cut-off date specified in the project plan.	Data team
2.	Ensure that all records from the source tables BSEG and BKPF are extracted into the tool in accordance with the agreed cut-off date defined in the project plan (to be confirmed).	Data team
3.	Perform preliminary completeness check documented in section	Data team
4.	Raise issues as defects if Req # 1 to 2 are not met	Data team
5.	Repeat Req # 1 to 3 if required	Data team
6.	Report extraction result to person in charge of TB 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.

Note: WP2 does not have trial balance maintained in the profit centre level and thus, there is no data in GLPCT.

Since this CS pertains to the opening balance, and the opening balance includes only balance sheet data, only GLT0 is relevant for extraction within the scope of object number 9015.

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 TB-PY ( Opening Balance )::

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.  As this option involves processing a extremely large volume (200 Million)of data, it should be pursued only after thorough evaluation and justification and need agreement with technical team.  

Note: Since this CS pertains to the opening balance, and the opening balance includes only balance sheet data, only GLT0 is relevant for extraction within the scope of object number 9015.

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 ).

However, because the migration is performed periodically, the posting date must be updated for each period, which can be very time-consuming. To streamline the process, it would be advisable to enhance the migration cockpit object to include the posting date directly within the upload template.

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table	Target Field	Target description	Transformation logic
1	ECC	GLT0	BUKRS	Company Code	S/4HANA	ACDOCA	BUKRS	Company Code	Map Company Code from ECC to S4 Mapping File Location:
2	ECC	GLT0	LDGRP	Ledger Group	S/4HANA	ACDOCA	LDGRP	Ledger Group	To be kept blank
3	ECC	GLT0	XBLNR	Reference Document Number	S/4HANA	ACDOCA	XBLNR	Reference Document Number	Default to 'Syway TB Opening'
4	ECC	GLT0	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	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. For non–cut-over periods, multiple take-on accounts—"based on the GL Account Mapping for Migration"—will be used for the various sub-ledger types. However, during the cut-over period, only one designated account will be used for each individual sub-ledger (as listed below). Syniti team will need to apply right logic in the transformation to take care of this.  Therefore, two GL Account Mapping for Migration to be provided and maintained as DCT Pages.
6	ECC	GLT0	GKONT	Offsetting Account	S/4HANA	ACDOCA	GKONT	Offsetting Account	TB Balance Offset Account ( Account Number:  5310998  )
7	ECC	GLT0	BLART	Document Type	S/4HANA	ACDOCA	BLART	Document Type	Default to '9S'
8	ECC	GLT0	BLDAT	Posting Date	S/4HANA	ACDOCA	BUDAT	Posting Date	Group 1:  Posting Date - 31st December 2026 Group 2:  Posting Date - 31st December 2027
9	ECC	GLT0	BLDAT	Document Date	S/4HANA	ACDOCA	BLDAT	Document Date	Group 1:  Posting Date - 31st December 2026 Group 2:  Posting Date - 31st December 2027
10	ECC	GLT0	WWERT	Translation Date	S/4HANA	ACDOCA	WWERT	Translation Date	Keep it blank
11	ECC	GLT0	BKTXT	Header Text	S/4HANA	ACDOCA	BKTXT	Header Text	Set to Concatenation of "DM:", Legacy BUKRS, Period ( Year + Period )
12	ECC	GLT0	SGTXT	Item Text	S/4HANA	ACDOCA	SGTXT	Item Text	Set to ECC Account Number (HKONT), ECC Profit Centre, ECC Transaction Type
13	ECC	GLT0	WAERS	Transaction Currency	S/4HANA	ACDOCA	WAERS	Transaction Currency	Use Currency Key Mapping File Mapping File Location:
14	ECC	GLT0	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	HWAER	Company Code Currency	S/4HANA	ACDOCA	HWAER	Company Code Currency	Automatic, to be kept blank in load template
16	ECC	GLT0	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	HWAE2	Group Currency	S/4HANA	ACDOCA	HWAE2	Group Currency (Legal Valuation)	Automatic, to be kept blank in load template Note: it is controlling area currency ( EUR )
18	ECC	GLT0	DMBE2	Amount	S/4HANA	ACDOCA	DMBE2/KSL	Amount	Group Currency 1 This is for currency type 30 Refer to Note Below this table 'Legal/Group Currency Calculation' 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
19	ECC	GLT0	HWAE3	Freely Defined Currency	S/4HANA	ACDOCA	HWAE3	Freely Defined Currency (Group Currency, Group Valuation	Automatic, to be kept blank in load template Note: it is client currency ( EUR )
20	ECC	GLT0	DMBE3	Amount	S/4HANA	ACDOCA	DMBE3/VSL	Amount	Group Currency 2 This is for currency type 31 ( Freely Defined currency type 2 ) Refer to Note Below this table 'Legal/Group Currency Calculation' 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	RASSC	Company ID of Trading Partner	S/4HANA	ACDOCA	RASSC	Company ID of Trading Partner	to be kept empty
22	ECC	GLT0	ZUONR	Assignment Number	S/4HANA	ACDOCA	ZUONR	Assignment Number	to be kept empty
23	ECC	GLT0	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	VALUT	Value Date	S/4HANA	ACDOCA	VALUT	Value Date	to be kept empty
26	ECC	GLT0		Short Key for House Bank	S/4HANA	ACDOCA	HBKID	Short Key for House Bank	to be mapped from legacy to target Based on the mapping file
27	ECC	GLT0		ID for Account Details	S/4HANA	ACDOCA	HKTID	ID for Account Details	to be mapped from legacy to target Based on the mapping file
28	ECC	GLT0	VBUND	ID for Account Details	S/4HANA	BSEG	VBUND	Company ID of Trading Partner	to be mapped from legacy to target Based on the mapping file
29	ECC	GLT0	KOSTL	Cost Center	S/4HANA	ACDOCA	KOSTL	Cost Center	Not applicable as Opening balance consists of only balance sheet accounts
30	ECC	GLT0	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.
31	ECC	GLT0		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 , 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		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.
33	ECC	GLT0		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.

Legal/Group Currency Calculation

During the migration of GL balances from SAP ECC to S/4HANA, it was identified that group currency balances are missing. To address this, the plan is to derive group currency amounts by reading the relevant exchange rates from the BFC consolidation system for each period within the migration scope.

For each period:

• The local currency trial balance will be extracted from ECC.
• The corresponding period’s exchange rate will be retrieved from BFC.
• The group currency balance will be calculated by converting the local currency amounts using the BFC exchange rates.
• The calculated group currency balances will then be loaded into S/4HANA as part of the migration process.

This approach ensures consistency between the group currency balances in S/4HANA and the consolidation system.

Exchange Rate Table: Local Currency to Group Currency ( A DCT page to be maintained to store this information for each cycle ) 

Target Company Code	Period (YYYYMM)	Local Currency	Legal Currency	Exchange Rate (Local to Legal - Currency Type 30)	Group Currency	Exchange Rate (Local to Group - Currency Type 31)	Source System (e.g., BFC)
1000	202401	EUR	USD	1.10	USD	1.10	BFC
1000	202402	EUR	USD	1.12	USD	1.12	BFC
2000	202401	GBP	USD	1.30	USD	1.30	BFC
2000	202402	GBP	USD	1.28	USD	1.28	BFC
3000	202401	CNY	USD	0.14	USD	0.14	BFC
.	.	.	.	.	.	.	.
3000	202402	CNY	USD	0.15	USD	0.15	BFC

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: 

For each reporting period, balance sheet balances should ideally be allocated to the appropriate profit centres for all the accounts including balance sheet accounts. However, given the complexity involved, a more practical approach is outlined below for the balance sheet accounts.

• Cutover Period:
  During the cutover period, balances related to sub-ledger control accounts will already be correctly assigned to the respective profit centres from the sub-ledger side. therefore, For the cutover period, general ledger migration balances must be distributed by profit centre in accordance with the details outlined below. This ensures that the sub-ledger take-on account balances recorded in the general ledger can be properly offset against the sub-ledger clearing entries.

• Prior Periods ( Including Opening balance):
  For periods preceding the cutover, sub-ledger control account balances will be derived from the general ledger and migrated into the respective sub-ledger take-on accounts. However, these ledger-based balances do not contain profit centre details. As the balances for each period will later be reversed, unless a viable solution and compelling business case exist to justify detailed allocation given the significant complexity involved, the balances for periods prior to the cutover may be migrated using a default profit centre.

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 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: the profit center will be derived from the offset line of the AR open item document.
   3. PI2:  AR open items transferred to PI2 from PF2 will include the business area, and the profit center derivation process for these items will follow the approach outlined in the PF2 section. Similarly, AR open items transferred to PI2 from WP2 will include the business area, and the profit center derivation process will follow the approach detailed in the WP2 section.
4. AP Take-On Account
   1. PF2:
      1. The Business Area will be used to derive the corresponding Profit 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:  the profit center will be derived from the offset line of the AP open item document.
   3. PI2:  AP open items transferred to PI2 from PF2 will include the business area, and the profit center derivation process for these items will follow the approach outlined in the PF2 section. Similarly, AP open items transferred to PI2 from WP2 will include the business area, and the profit center derivation process will follow the approach detailed in the WP2 section.

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

Mapping File DCTs 

Cost Centre: 

Source System	Legacy Cost Centre	Legacy Cost Centre Description	Target Profit Centre	Target Cost Centre Description	Notes
PF2
WP2
PI2

Profit Centre:

Source System	Legacy Profit Centre	Legacy Profit Centre Description	Target Profit Centre	Target  Profit Centre Description	Notes
PF2
WP2
PI2

 House Bank ID and Account ID Mapping

Source System	ECC House Bank	ECC Account ID	ECC G/L	S/4 House Bank	S/4 Account ID
PF2
WP2
PI2

GL Account: 

Source System	Legacy GL Account	Legacy GL Description	Sub-Ledger Type	Target GL (Cut-Over Period)	Target GL (Non–Cut-Over Period)	Target GL Description	Notes
PF2
WP2
PI2

Trading Partner Mapping: 

Source System	ECC Company Code	ECC Company Name	ECC Trading Partner (VBUND)	S4 Company Code	S4 Company Name	S4 Trading Partner (VBUND)
PF2
WP2
PI2

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	Create a complete preload report with all the fields with source and transformed columns side-by-side. Confirm mandatory key fields are populated — Company Code, GL Account, Fiscal Year, Period, Currency, Profit Centre, Cost Centre, etc. Verify debit/credit amounts are numeric and decimal precision aligns with S/4 configuration. Validate that mapping files for GL Account, Company Code, Profit Centre, and Cost Centre are complete. Ensure all GL accounts in the TB exist in the S/4HANA chart of accounts and are correctly mapped (no obsolete or unmapped accounts). Validate all profit and cost centres are active (CSKS, CEPC), not marked for deletion, and valid for the posting date. Check All the Transaction Types are mapped. ( In case Option 2 (Transaction Data as source ) is used for migration)
Reconciliation of total	For Open-Item managed accounts, confirm that balances agree with open-item totals from CNV-9010 GL Open Items. For AR Open Items, confirm that balances agree with AR open-item totals from CNV-9008 AR Open Items For AP Open Items, confirm that balances agree with AR open-item totals from CNV-9006 AP Open Items For Fixed Assets, confirm that balances agree with AR open-item totals from CNV-1070 Fixed Assets (incl. Sub Assets) For AUC Balances, confirm that balances agree with AR open-item totals from CNV-9031 Project-Actual GL Line Items (PNL-WBS for AuC)

Accuracy

Task	Action
Mandatory field mapping and transformation	Verify that local and group currency balances align as per configured exchange rates (TCURR). Ensure for each company code, total debits equal total credits. Check Balances at transaction Type level ( In case Option 2 (Transaction Data as source ) is used for migration)

Business

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

Completeness

Task

Action

Verify record count in Pre-load reports by region

Validate that total TB balances by company code, GL account, and currency match between source and pre-load files. Ensure TB data aligns to the agreed migration period and fiscal year (e.g., Period 12 FY2024). Review and sign off on final mappings (GL, cost/profit centre, company code) for business accuracy. Validate reconciliation accounts (e.g., GR/IR, AR, AP, inventory) match sub ledger balances. Ensure there are no records posted to suspense or unmapped accounts prior to load. All exceptions (if any) are documented and approved with remediation actions.

Accuracy

Task	Action
Conversion accuracy	Compare S/4 pre-load trial balance with legacy ECC TB totals for accuracy. All exceptions (if any) are documented and approved with remediation actions. Check Balances at transaction Type level ( In case Option 2 (Transaction Data as source ) is used for migration)

Load

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
	Reversal Postings ( Using F.80 ) - Mass Processing
10	Retrieve the list of FI documents along with their respective company codes and fiscal years. Simulate the reversal process in F.80 to verify posting accuracy. Execute the reversal in F.80 once the simulation results are validated.	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 Centre
1074	Cost Centre

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

Confirm that all load jobs completed successfully without errors or truncations in Migration Cockpit logs. Generate Post-Load Reports for the following items. Total number of records loaded for TB Balance ( PY )  will be generated in the Post-load reports based on the target table and fields mentioned in the preload file. 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 Complete Report comparing each field side-by-side with a True/ False column checking preload and target Compare record counts between the pre-load staging file and the target S/4HANA tables (e.g., FAGLFLEXT) to ensure completeness. Conduct a summary balance comparison between the pre-load and target data to validate balances in Transaction Currency, Company Code Currency, and Group Currency for the following qualifier fields: GL Account, Company Code, Posting Date, Profit Centre, and Transaction Type.

Accuracy

Task	Action
Check values in key fields for accuracy	Generate Post-Load Reports for the following items.   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
Summary Balance using Tcode	Verify the post-load report generated by project team. Business performs a Trial Balance check using transaction code FAGLB03 to compare the loaded balances against the pre-load data. Open the Transaction: Enter FAGLB03 in the SAP command field and press Enter. This opens the G/L Account Balance Display screen. Enter Selection Criteria: Company Code: Enter the relevant company code(s). Ledger: Select the ledger to check (e.g., 0L – Leading Ledger). Fiscal Year / Period: Enter the fiscal year and period of the TB to review. G/L Account Range: Specify the account range or leave blank to include all accounts. Currency: Choose local currency or group currency as needed. Additional Filters (Optional): Profit Centre, Cost Centre, Business Area, etc. Execute the Report: Click Execute (or press F8) to generate the GL balances. Review the Balances: Check Debit and Credit totals for each G/L account. Compare the results against the pre-load TB extract to ensure that balances match. Spot-check key accounts (control accounts, suspense accounts, major P&L accounts) for accuracy. Check Detail (Optional): Double-click on individual G/L accounts to view line-item details. Verify postings, posting keys, amounts, profit/cost centre allocations, and document references. Export for Reconciliation (Optional): Use List → Export → Spreadsheet to download the report to Excel. Perform a detailed comparison against the pre-load TB file.
Summary Balance using Fiori App	Run GL Balance Report for Post-Load Trial Balance Check (Using Fiori App) Objective: Validate migrated Trial Balance (TB) data after load by running the General Ledger balance report in S/4HANA. Steps: Access the Fiori Launchpad. Log in to the SAP Fiori Launchpad with the appropriate financial reporting role. Open the Fiori App: Navigate to and open “Display G/L Balances” (App ID: F0718) Alternate app names: “G/L Account Balances – Display” or “Display Line Items in General Ledger” (F0708) depending on configuration. Enter Selection Criteria: Company Code: Enter the relevant company code(s). Fiscal Year / Period: Specify the migration fiscal year and period. Ledger: Choose the appropriate ledger (e.g., 0L – Leading Ledger). G/L Account Range: Enter the account range or leave blank for all. Currency: Select local or group currency as required. Execute the Report. Click Go to generate the balance report. Validate Results: Confirm that total debits equal credits for each company code. Compare balances with the pre-load TB or legacy TB extract. Review Profit Centre and Cost Centre-level balances for accuracy. Ensure no postings appear in suspense or unmapped accounts. Download / Export Results: Export the report to Excel for reconciliation and business sign-off documentation.

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. Review financials under group currency and ensure alignment with group consolidation requirements. ( Based on currency exchange rate ) Validate reports such as Trial Balance, GL Line Item Report, and Financial Statements in Fiori / SAP GUI match legacy totals. Review financials under group currency and ensure alignment with group consolidation requirements.
Spot check	Spot check FI documents to ensure the information reflects correctly Open Transaction Code: Enter FB03 in the SAP command field and press Enter. Enter Document Details: Document Number – Enter the specific FI document to review. Company Code – Enter the relevant company code. Fiscal Year – Specify the fiscal year of the document. Display Document: Click Display (or press Enter) to view the accounting document. Review Document Header: Verify Document Type, Posting Date, and Document Date. Confirm that the posting period aligns with the migration period. Review Line Items: Check G/L Account, Amount (Debit/Credit), and Currency. Confirm that Profit Centre, Cost Centre, Transaction Types etc (if applicable) are populated correctly. Validate that posting keys and amounts align with expected migration data. Cross-Check Totals: Ensure the total debit equals total credit within the document. Optionally, compare with source or pre-load record for that document.

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