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

Compare with Current View Page History

« Previous Version 6 Next »

Status

30%

OwnerPILLAY-ext, Lawrence 
Stakeholders

LARU-ext, Soumen 

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

Profit Centres 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 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2Statistical key figures
S4HANA
WP2Statistical key figures
S4HANA

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

1.      



2.      



3.      



4.      




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


M







Transformation Dependencies

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





Pre-Load Validation

Project Team

Completeness


Task

Action

Generation of
Pre-load reports

Mandatory field check.
Profit Centres are mapped to new values

Profit Centre 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

Completeness

TaskAction
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 profit centres mapped from old to new ) 


Accuracy

TaskAction
Conversion accuracy

Verify Profit Centres 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 Profit Centre. 
  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 Profit Centre Object using Migration Cockpit Object for Profit Centre 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

Configuration

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


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

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

Completeness

TaskAction
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

TaskAction
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

Completeness

TaskAction
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

TaskAction
Open items totalsCheck business partner open item totals by Business partner, Company code, profit centre. Totals should be checked in Document, Local and Group currency.
Spot checkBusiness 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. 
  • is in scope based on data design and any exception requested by business.



Change log

Version Published Changed By Comment
CURRENT (v. 6) 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