You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Status

80%

OwnerPILLAY-ext, Lawrence 
Stakeholders

LARU-ext, Soumen GARCIA-ext, Angel Luis 

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 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Statistical key figures
S4HANA
WP2Statistical key figures
S4HANA
  • Data will be sourced via a DCT.

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements


Target Design

The technical design of the target for this conversion approach.

IDTableFieldField DescriptionData TypeLengthDecimalsRequirement
1TKA03KOKRSControlling AreaCHAR4
Required
2TKT03STAGRStatistical Key FigureCHAR6
Required
3TKA03MSEHIUnit for Statistical Key FigureCHAR3
Required
4TKA03GRTYPStatistical Key Figure CategoryCHAR1
Required
5TKT03SPRASLanguageCHAR1
Required
6TKT03BEZEIStatistical key figure descriptionCHAR20
Required


Data Cleansing


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


Extraction

Extract data from source systems. 

Extraction Run Sheet


Req #

Requirement description

Team responsible

  



   




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set











Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Statistical Key Figures.


IDTableFieldField DescriptionRule
1TKA03KOKRSControlling AreaBusiness to enter content as per data type and length permitted
2TKT03STAGRStatistical Key FigureBusiness to enter content as per data type and length permitted
3TKA03MSEHIUnit for Statistical Key FigureBusiness to enter content as per data type and length permitted
4TKA03GRTYPStatistical Key Figure CategoryBusiness to enter content as per data type and length permitted
5TKT03SPRASLanguageBusiness to enter content as per data type and length permitted
6TKT03BEZEIStatistical key figure descriptionBusiness to enter content as per data type and length permitted


Extraction Dependencies


Item #

Step description

Team responsible

1.  





Transformation

The Target fields are mapped to the applicable Legacy/Source fields. This is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow  to make the data Target ready:

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

Transformation Run Sheet

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 FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ECCTKA03KOKRSControlling AreaS/4 HANATKA03KOKRSControlling AreaCopy
2ECCTKT03STAGRStatistical Key FigureS/4 HANATKT03STAGRStatistical Key FigureCopy
3ECCTKA03MSEHIUnit for Statistical Key FigureS/4 HANATKA03MSEHIUnit for Statistical Key FigureCopy, XREF is required to validate the unit of measure
4ECCTKA03GRTYPStatistical Key Figure CategoryS/4 HANATKA03GRTYPStatistical Key Figure CategoryCopy
5ECCTKT03SPRASLanguageS/4 HANATKT03SPRASLanguageCopy
6ECCTKT03BEZEIStatistical key figure descriptionS/4 HANATKT03BEZEIStatistical key figure descriptionCopy


Transformation Mapping

Mapping Table Name

Mapping Table Description





Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible







Pre-Load Validation

Project Team

Completeness


Task

Action

Reconciliation of Record CountConfirm record count of the source to target, they should match. 



Accuracy


Task

Action




Business

Completeness

TaskAction
Record Count Check

Confirm record count of the source to target, they should match. 




Accuracy

TaskAction



Load

  1. Loading will be done through migration cockpit and the templates are attached below:
  2. Templates:

Source data for CO - Statistical key figure.xml


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

Configuration

Item #

Configuration item

    


 


 Conversion Objects

Object #Preceding Object Conversion Approach




Error Handling


Error type

Error description

Action taken








Post-Load Validation

Project Team

Completeness

TaskAction
Reconciliation of Record CountReconciliation of Record Count

Accuracy

TaskAction




Business

Completeness

TaskAction
Reconciliation of Record Count

Reconciliation of Record Count


Accuracy

TaskAction



Key Assumptions

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



Change log

Version Published Changed By Comment
CURRENT (v. 11) Nov 07, 2025 19:58 PILLAY-ext, Lawrence
v. 14 Nov 07, 2025 19:54 PILLAY-ext, Lawrence
v. 13 Sept 29, 2025 09:34 GARCIA-ext, Angel Luis
v. 12 Sept 25, 2025 21:19 PILLAY-ext, Lawrence
v. 11 Sept 16, 2025 23:17 PILLAY-ext, Lawrence
v. 10 Sept 16, 2025 23:15 PILLAY-ext, Lawrence
v. 9 Sept 16, 2025 23:14 PILLAY-ext, Lawrence
v. 8 Sept 16, 2025 23:08 PILLAY-ext, Lawrence
v. 7 Sept 16, 2025 23:06 PILLAY-ext, Lawrence
v. 6 Sept 16, 2025 22:59 PILLAY-ext, Lawrence

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels