Status
Owner	PILLAY-ext, Lawrence
Stakeholders	LARU-ext, Soumen GARCIA-ext, Angel Luis KUMAR-ext, Rajib

Purpose

The purpose of this document is to define the conversion approach of Statistical Key Figures into S/4 HANA. 

The statistical key figures is master data in a CO area that represents allocation drivers for different kind of allocations.

The statistical key figures contains a prorata value that can be assigned to a cost center (in case of cost center allocation) or to a G/L account and some CO-PA characteristics in case of CO-PA allocation.
The statistical key figures can contains planned and actual values.

Statistical key figures can be defined as: 
- Fixed value that applies for all periods until there is a change (example headcounts) or 
- Total values which means that you have input each month a value otherwise this is considered as nul (example invoice number)

In SYENSQO context, the preferred approach is to define statistical key for all allocation cases based on fixed percentages or fixed amounts. 

 

Conversion Scope

List of source systems and approximate number of records 

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Statistical key figures		S4HANA
WP2	Statistical key figures		S4HANA

• Data will be sourced via a DCT.

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.

ID	Table	Field	Field Description	Data Type	Length	Decimals	Requirement
1	TKA03	KOKRS	Controlling Area	CHAR	4		Required
2	TKT03	STAGR	Statistical Key Figure	CHAR	6		Required
3	TKA03	MSEHI	Unit for Statistical Key Figure	CHAR	3		Required
4	TKA03	GRTYP	Statistical Key Figure Category	CHAR	1		Required
5	TKT03	SPRAS	Language	CHAR	1		Required
6	TKT03	BEZEI	Statistical key figure description	CHAR	20		Required

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.

Not Applicable

Conversion Process 

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

The high-level process:

1. Extract data from source systems.
2. Apply relevancy rules.
3. Transform data based on field and value mappings.
4. Create load files outputs.
5. Load data in target system.

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from source systems. 

Extraction Run Sheet

Req #	Requirement description	Team responsible
N/A	N/A	N/A

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 Statistical Key Figures.

<Object>

ID	Table	Field	Field Description	Rule
1	TKA03	KOKRS	Controlling Area	Business to enter content as per data type and length permitted
2	TKT03	STAGR	Statistical Key Figure	Business to enter content as per data type and length permitted
3	TKA03	MSEHI	Unit for Statistical Key Figure	Business to enter content as per data type and length permitted
4	TKA03	GRTYP	Statistical Key Figure Category	Business to enter content as per data type and length permitted
5	TKT03	SPRAS	Language	Business to enter content as per data type and length permitted
6	TKT03	BEZEI	Statistical key figure description	Business to enter content as per data type and length permitted

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step description	Team responsible
1.

Transformation

The Target fields are mapped to the applicable DCT field that will be its source.  

Note:  as this object is DCT, the mapping rule for all the fields is 'Copy'  as described in the transform rule section. However, some reports are to be created and executed to ensure integrity in the data collected in DCT as described in 'Pre-load Data Validation' section. 

This step identifies the transformation activity required to allow  to make the data Target ready:

1. Prepare target-ready data in the target structure and format that is required for loading via prescribed Load Tool in the load section.
2. Produce the preload reports as requested in the 'Preload Data Validation' section. 

Transformation Run Sheet

Item #	Step description	Team responsible
1	Define the target load structure	Data team
2	Map the target fields to the source fields as per the transformation rules	Data team
3	Apply transformation rules	Data team
4	Execute ETL job	Data team
5	Generate Error reports	Data team
6	Log and resolve defects	Data team
7	Generate Pre-load reports	Data team
8	Generate load file	Data team
9	Generate post load reports	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	TKA03	KOKRS	Controlling Area	S/4 HANA	TKA03	KOKRS	Controlling Area	Copy
2	ECC	TKT03	STAGR	Statistical Key Figure	S/4 HANA	TKT03	STAGR	Statistical Key Figure	Copy
3	ECC	TKA03	MSEHI	Unit for Statistical Key Figure	S/4 HANA	TKA03	MSEHI	Unit for Statistical Key Figure	Copy, XREF is required to validate the unit of measure
4	ECC	TKA03	GRTYP	Statistical Key Figure Category	S/4 HANA	TKA03	GRTYP	Statistical Key Figure Category	Copy
5	ECC	TKT03	SPRAS	Language	S/4 HANA	TKT03	SPRAS	Language	Copy
6	ECC	TKT03	BEZEI	Statistical key figure description	S/4 HANA	TKT03	BEZEI	Statistical key figure description	Copy

Transformation Mapping

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

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Reconciliation of Record Count	Confirm record count of the source to target, they should match.

Accuracy

Task	Action
XREF Report for Unit for Statistical Key Figure	Check all unit of measure values are configured in the target.

Business

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

Completeness

Task	Action
Record Count Check	Confirm record count of the source to target, they should match.

Accuracy

Task	Action

Load

1. Loading will be done through migration cockpit and the templates are attached below:
2. Prepare the load files in accordance with the Migration Cockpit templates.

Item	Step description	Team responsible
1	Produce the load ready file or transfer data to the S/4 migration tables in LTMC	Data team
2	Run the load program in S/4	Data team
3	Generate the post load reports in tool.	Data team
4	Log errors as defects, if any and address resolutions. Close defects.	Data team
5	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
6	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business

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

 Conversion Objects

Object #	Preceding Object Conversion Approach

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

Post-Load Validation

Project Team

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

Completeness

Task	Action
Reconciliation of Record Count	Reconciliation of Record Count

Accuracy

Task	Action

Business

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

Completeness

Task	Action
Reconciliation of Record Count	Reconciliation of Record Count

Accuracy

Task	Action

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