Status
Owner	Soumen Laru
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach of GL Accounts COAs into S/4 HANA.  GL Accounts COAs

The document details out the field list, extraction criteria, scoping, mapping of cost centre object

Cost Centres will be extracted from Source and based on the list of cost centres from the cost centre mapping sheet, target cost centre data file will be 

Conversion Scope

GL Accounts COAs which will be listed as part of scope list with new numbering will be in scope of migration. 

List of source systems and approximate number of records 

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	GL Accounts COA		S4HANA
WP2	GL Accounts COA		S4HANA
PI2	GL Accounts COA		S4HANA

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

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	Requirement
SKA1	KTOPL		Chart of Accounts	CHAR	4	Key that uniquely identifies a chart of account. At Syensqo, the following naming convention applies: 1.) COCA for the operational corporate CoA 2.) LOXX for country CoAs where XX represents the country code of the country CoA. The global Syensqo operational Chart of Accounts will be assigned as operational Chart of Accounts to all Syensqo entities. A maximum of one local CoA per country is permitted.	R
SKA1	SAKNR		G/L Account Number	CHAR	10	The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group.	R
SKA1	GVTYP		P&L Statement Account Type	CHAR	2	With the P&L statement account type, you determine the retained earnings account for each P&L account. The retained earnings account is used during year-end closing to calculate the company's result. If you are creating a P&L account, you must make an entry here.	C
SKA1	KTOKS		G/L Account Group	CHAR	4	The account group is a classifying feature within the G/L account master records. The account group determines the fields for the entry screens if you create or change a master record in the company code. The account group also determines in which number range the account number must be contained.	R
SKA1	XLOEV		Indicator: Account Marked for Deletion?	CHAR	1	Indicator which specifies that master record data is to be deleted. The deletion must be carried out using the program for archiving G/L account master data. This program archives the master records that have been marked for deletion, providing there is no dependent data remaining in the system.	C
SKA1	XSPEA		Indicator: Account Is Blocked for Creation ?	CHAR	1	An entry in this field causes the account to be blocked for creation in the specified company code.	C
SKA1	XSPEB		Indicator: Is Account Blocked for Posting?	CHAR	1	An entry in this field means that the account is blocked for posting at Chart of Account level.	C
SKA1	XSPEP		Indicator: Account Blocked for Planning ?	CHAR	1	An entry in this field causes the account to be blocked for planning.	C
SKA1	FUNC_AREA		Functional Area	CHAR	16	The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria: Manufacturing Administration Sales Research and development	C
SKA1	GLACCOUNT_TYPE		Type of a General Ledger Account	CHAR	1	Specifies the general ledger account type that classifies the general ledger account. The following types are available (Financial Accounting modules where accounts are visible kept in brackets): X - Balance Sheet Account - Asset, liability, or equity B/S account. (FI only) C- Cash Account - Bank G/L Account (FI only) N - Non-operating Expense or Income - Below EBIT P&L Account (FI only) P - Primary Costs or Revenue - Above EBIT P&L Account (FI&CO) S - Secondary Costs - P&L Account (FI&CO)	R
SKA1	GLACCOUNT_SUBTYPE		Subtype of a G/L Account	CHAR	1	Indicates the usage of an account that has the Cash Account G/L account type.	C
SKA1	MAIN_SAKNR		Bank Reconciliation Account			This field indicates the relationship between bank subaccounts and the main reconciliation accounts the bank sub-accounts belong to. This field is only visible for accounts of G/L account subtype ''Bank Subaccount' and is a mandatory input field for those accounts so the system can establish a connection between the sub-accounts and the main bank reconciliation account in the bank ledger.	C
SKAT	TXT20		Short Text	CHAR	20	Short description of the G/L account. This should be used to provide a short text that will explain the use of the general ledger account. (Note: When used in reporting, if there is not enough space on the report, the short text can be displayed)	R
SKAT	TXT50		Long Text	CHAR	50	Long description of the G/L account. This field should be used to provide a more detailed description of the G/L account that intuitely explains the purpose of the account.	R
SKB1	BUKRS		Company Code	CHAR	4	The company code is an organisational unit used in financial accounting representing Syensqo's independent legal entity or other entity as described in the Enterprise Structure Position Paper.	R
SKB1	SAKNR		G/L Account Number	CHAR	10	The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group.	R
SKB1	FDGRV		Planning Group	CHAR	10	In cash management, G/L accounts as well as customer and vendor accounts are allocated to planning groups by means of an entry made in the master record. This is used for liquidity planning and reporting.	C
SKB1	FDLEV		Planning Level	CHAR	2	The planning level is used to control displays in Cash Management. The freely defined field is used to identify specific account groups in cash management.	C
SKB1	FSTAG		Field Status Group	CHAR	4	Field statuses are SAP's method to control which fields are required to have data in postings that are made to the general ledger account line items. It controls these fields by selecting them as suppressed, required or optional. Example of the fields are cost centre, text, material number, asset number, etc. - Suppressed: if this is selected, the field is not available for input. - Optional: if this is selected, the field is available for input but isn't mandatory. - Required: if this is selected, the field is mandatory for input.	R
SKB1	MITKZ		Recon. Account for Acct Type	CHAR	1	An entry in this field characterises the G/L account as a reconciliation account. The reconciliation means that this G/L account represents a subledger account for Accounts Receivable, Accounts Payable, or Fixed Assets. Only these types of reconciliation accounts should be selected.	C
SKB1	MWSKZ		Tax Category	CHAR	2	Determines whether you want to use the account for tax-relevant postings and which types of taxes are allowed for that General Ledger account.	C
SKB1	WAERS		Account currency	CUKY	5	The account currency indicates the currency in which this account is held. If a currency other than the company code currency is specified, then you can only post items in that currency to this account e.g. foreign currency bank account or foreign currency loan. If the company code currency is specified, then you can post items in any currency to this account.	R
SKB1	XGKON		Relevant to Cash Flow	CHAR	1	Indicator that determines that the G/L account is a cash flow-relevant account.	C
SKB1	XINTB		Post Automatically Only	CHAR	1	This is selected for system accounts i.e. only where postings are made via account determination tables. This will ensure that there are only system postings and no manual adjustments to the account, eg GR/IR, inventory accounts, etc.	C
SKB1	XSPEB		Indicator: Is Account Blocked for Posting?	CHAR	1	An entry in this field means that the account is blocked for zum posting.	C
SKB1	XOPVW		Open Item Management	CHAR	1	Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.	C
SKB1	ZUAWA		Sort Key	CHAR	3	This field determines how the system will populate the default assignment field during document entry. This is then used for information to aid with clearing open items by the allocation field in the document line item. Each G/L account type may require a different key specified here to best facilitate sorting / clearing requirements line items posted to it. Note that the Sort Key only populates the assignment field with a default value, and the dassignment field will be overwritten when a new value is entered. This applies to all postings whether manual or interfaced.	C
SKB1	ALTKT		Alternative Account Number	CHAR	10	A freely definable field to be used to enter the account number from a country chart of accounts if a country chart of accounts is required for the company code.	C
SKB1	XMWNO		Indicator: Tax code is not a required field	CHAR	1	Indicates that the account can still be posted to even if a tax code has not been entered.	C
SKB1	XSALH		Balances in Local Crcy Only	CHAR	1	Indicates that balances are updated only in local currency (LC) for all postings to the account. You set this indicator for accounts in which you do not want the system to update transaction figures separately by currency. Setting this indicator for accounts managed on an open item basis affects the clearing procedures. Clearing can only be done in local currency if the indicator is set. Setting this indicator for accounts which are line-item managed only affects the foreign currency revaluation. Accounts which only manage balances in local currency will not be taken into consideration in foreign currency revaluation runs towards local currency.	C
SKB1	TOGRU		Tolerance group	CHAR	4	Tolerance groups define the limits within which differences are accepted when clearing open items. Where this is active, differences are automatically posted to predefined accounts. Syensqo will use the default tolerance group "Blank" which means no tolerance limits will be specified for clearing. For GR/IR clearing accounts a tolerance group shall be assigned with minimal value tolerances to allow for clearing of open items with minor rounding differences.	C
SKB1	XLGCLR		Open Item Management by Ledger Group	CHAR	1	Determines that journal entry line items are managed on an open item basis by ledger group for this G/L account.	C
CSKB	KATYP		Cost Element Category	CHAR	10	The cost element category determines which cost elements can be used for which business transactions. Primary Cost Element Categories 01: Primary costs / cost-reducing revenues - This cost element category is used for all primary expense postings and requires at least one real cost object to be specified in the line item details. 11: Revenues - This cost element category is used for all revenue postings and requires a Margin Analysis characteristics or real billing elements to be specified as cost objects. 12: Sales Deductions - This cost element category is used for all revenue deduction postings and requires a profit center to be specified as a COPA characteristic.. e.g. Sales Rebates Secondary Cost Element Categories 21: Internal Settlement - This cost element category is used to settle project costs to objects in Controlling (CO), such as profitability segments, cost centers, and WBS elements. 22: External Settlement - This cost element category is used to settle project costs to objects outside of Controlling (CO), such as G/L accounts, Fixed Assets or Materials. 31: Order/Project Results Analysis - Enables order or project results analysis data to be saved to the relevant order or project. 41: Overhead - This cost element category is used to allocate overhead costs from cost centers to orders. 42: Assessments - This cost element category is used to allocate costs during assessment from a sender Cost Center to receivers (Cost Centers or WBS Elements). 43: Internal Activity Allocation - This cost element category is used to allocate costs during internal activity allocation and for allocating process costs via an activity type to a receiver object. Statistical Cost Element Category: 90: Statistical Cost Element for Balance Sheet Account - This cost element category is typically used for Fixed Asset Reconciliation Accounts or inventory accouns to update the Controlling module statistically with line items posted to those accounts for getting full visibility over directly capitalized expenditures in Controlling reports.	C
CSKB	MGEFL		Record Quantity	CHAR	10	Indicator defining whether the system issues a message if no quantity or quantity unit is specified for a postings. Note: Once you have specified this and a posting has occurred in the leading ledger fiscal year against the particular G/L account that has quantities recorded, although you can change the flag in the G/L account, the system will always use the original value set until the following leading ledger fiscal year.	C

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
1.	Can load, but business process will fail	Lock any GL Accounts COA not being used for last 5 years	TBD	Report	PF2 / PI2 / WP2

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 CEPC and CEPCT are extracted in tool according to the agreed cut-off date in the project plan Ensure DCT is collected for the GL Accounts COAs based on the collection template	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

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

Field Name	Field description	Rule
CEPC-PRCTR	GL Accounts COA	Business to enter content as per data type and length permitted

Suggestion to add:

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

Extraction Dependencies

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 applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team.  This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:

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

Transformation Run Sheet

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

Rule #	Source system	Source Table	Source Field	Source description	Target system	Target Table	Target Field	Target description	Transformation logic
1	ECC	SKA1	KTOPL	Chart of Accounts	S4HANA	SKA1	KTOPL	Chart of Accounts
2	ECC	SKA1	SAKNR	G/L Account Number	S4HANA	SKA1	SAKNR	G/L Account Number
3	ECC	SKA1	GVTYP	P&L Statement Account Type	S4HANA	SKA1	GVTYP	P&L Statement Account Type
4	ECC	SKA1	KTOKS	G/L Account Group	S4HANA	SKA1	KTOKS	G/L Account Group
5	ECC	SKA1	XLOEV	Indicator: Account Marked for Deletion?	S4HANA	SKA1	XLOEV	Indicator: Account Marked for Deletion?
6	ECC	SKA1	XSPEA	Indicator: Account Is Blocked for Creation ?	S4HANA	SKA1	XSPEA	Indicator: Account Is Blocked for Creation ?
7	ECC	SKA1	XSPEB	Indicator: Is Account Blocked for Posting?	S4HANA	SKA1	XSPEB	Indicator: Is Account Blocked for Posting?
8	ECC	SKA1	XSPEP	Indicator: Account Blocked for Planning ?	S4HANA	SKA1	XSPEP	Indicator: Account Blocked for Planning ?
9	ECC	SKA1	FUNC_AREA	Functional Area	S4HANA	SKA1	FUNC_AREA	Functional Area
10	ECC	SKA1	GLACCOUNT_TYPE	Type of a General Ledger Account	S4HANA	SKA1	GLACCOUNT_TYPE	Type of a General Ledger Account
11	ECC	SKA1	GLACCOUNT_SUBTYPE	Subtype of a G/L Account	S4HANA	SKA1	GLACCOUNT_SUBTYPE	Subtype of a G/L Account
12	ECC	SKA1	MAIN_SAKNR	Bank Reconciliation Account	S4HANA	SKA1	MAIN_SAKNR	Bank Reconciliation Account
13	ECC	SKAT	TXT20	Short Text	S4HANA	SKAT	TXT20	Short Text
14	ECC	SKAT	TXT50	Long Text	S4HANA	SKAT	TXT50	Long Text
15	ECC	SKB1	BUKRS	Company Code	S4HANA	SKB1	BUKRS	Company Code
16	ECC	SKB1	SAKNR	G/L Account Number	S4HANA	SKB1	SAKNR	G/L Account Number
17	ECC	SKB1	FDGRV	Planning Group	S4HANA	SKB1	FDGRV	Planning Group
18	ECC	SKB1	FDLEV	Planning Level	S4HANA	SKB1	FDLEV	Planning Level
19	ECC	SKB1	FSTAG	Field Status Group	S4HANA	SKB1	FSTAG	Field Status Group
20	ECC	SKB1	MITKZ	Recon. Account for Acct Type	S4HANA	SKB1	MITKZ	Recon. Account for Acct Type
21	ECC	SKB1	MWSKZ	Tax Category	S4HANA	SKB1	MWSKZ	Tax Category
22	ECC	SKB1	WAERS	Account currency	S4HANA	SKB1	WAERS	Account currency
23	ECC	SKB1	XGKON	Relevant to Cash Flow	S4HANA	SKB1	XGKON	Relevant to Cash Flow
24	ECC	SKB1	XINTB	Post Automatically Only	S4HANA	SKB1	XINTB	Post Automatically Only
25	ECC	SKB1	XSPEB	Indicator: Is Account Blocked for Posting?	S4HANA	SKB1	XSPEB	Indicator: Is Account Blocked for Posting?
26	ECC	SKB1	XOPVW	Open Item Management	S4HANA	SKB1	XOPVW	Open Item Management
27	ECC	SKB1	ZUAWA	Sort Key	S4HANA	SKB1	ZUAWA	Sort Key
28	ECC	SKB1	ALTKT	Alternative Account Number	S4HANA	SKB1	ALTKT	Alternative Account Number
29	ECC	SKB1	XMWNO	Indicator: Tax code is not a required field	S4HANA	SKB1	XMWNO	Indicator: Tax code is not a required field
30	ECC	SKB1	XSALH	Balances in Local Crcy Only	S4HANA	SKB1	XSALH	Balances in Local Crcy Only
31	ECC	SKB1	TOGRU	Tolerance group	S4HANA	SKB1	TOGRU	Tolerance group
32	ECC	SKB1	XLGCLR	Open Item Management by Ledger Group	S4HANA	SKB1	XLGCLR	Open Item Management by Ledger Group
33	ECC	CSKB	KATYP	Cost Element Category	S4HANA	CSKB	KATYP	Cost Element Category
34	ECC	CSKB	MGEFL	Record Quantity	S4HANA	CSKB	MGEFL	Record Quantity

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
GL Accounts COA	Mapping of legacy Profit Center to target system value
Person Responsible	Mapping of legacy Person Responsible to New Person Responsible
User ID	Mapping of legacy User ID
Hierarchy Group	Mapping of Legacy Hierarchy Group to Hierarchy Group

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
2	Ensure GL Accounts COA hierarchies are loaded into target S/4HANA	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. GL Accounts COAs are mapped to new values GL Accounts COA Hierarchy Mapped to new values Person Responsible / HR positions mapped to new values
	Record Count Confirm the record counts in preload summary report Total Records:  Valid Records: Invalid Records:

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	Confirm the Preload File contains all the records in scope of migration ( Based on list of GL Accounts COAs mapped from old to new )

Accuracy

Task	Action
Conversion accuracy	Verify GL Accounts COAs 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 ECC tcode SE16N to display table CEPC to confirm copied fields are accurately copied.  If any of the sum is different, raise defect and flag the relevant record as error.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of GL Accounts COA. 
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE) 

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 upload of GL Accounts COA Object using Migration Cockpit Object for GL Accounts COA 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.	Controlling Area
2.	Standard Hierarchy is Maintained
3.	Currencies (currency keys, decimal places in currencies)

 Conversion Objects

Object #	Preceding Object Conversion Approach
N/A

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
P	Posting period is blocked for posting	Review project / cutover plan and ensure posting periods can be opened for postings
GL Accounts COA does not exist	GL Accounts COA does not exist in company code	Ensure the GL Accounts COA mapping is correct and or create the GL Accounts COA 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 FS10N – Vendor Line Item Display 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, GL Accounts COA. 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