Status
Owner	Soumen Laru
Stakeholders	PILLAY-ext, Lawrence WELENSKY-ext, Dave GARCIA-ext, Angel Luis  GONCHIGARU-ext, Ashok

Purpose

The purpose of this document is to define the conversion approach of Cost Centre Group (Alt, Std Hierarchy)s into S/4 HANA.  

The document details out the field list, extraction criteria, scoping, mapping of  Cost Centre Group (Alt, Std Hierarchy)s.

Note:  Cost centre standard and alternate hierarchies will be constructed newly based on the new organizational design. Therefore, even though extracting and transforming of source hierarchy is an option, that will not be used. Instead, a DCT( Data Construction Template) will be used to collect the new hierarchy details. 

As per the current implementation approach, any alternative hierarchies, if applicable, will be uploaded exclusively through the Manage Global Hierarchies application and not via LSMW. Should there be a requirement to upload any alternative hierarchy using LSMW, this specification is designed to accommodate such a scenario. At this stage, there is no anticipated requirement for the inclusion of alternative hierarchies within the migration scope.

Conversion Scope

Cost Centre Group (Alt, Std Hierarchy)s 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	Cost Centre Group (Alt, Std Hierarchy)	TBD	S4HANA	TBD
WP2	Cost Centre Group (Alt, Std Hierarchy)	TBD	S4HANA	TBD

Additional Information

Multi-language Requirement

In the Syensqo Cost Centre Group (Alt, Std Hierarchy)s, the following four language keys must be maintained:
 - English (EN)
 - French (FR)
 - Italian (IT)
 - Chinese (ZN)
Note: For certain countries it may be required to also maintain account descriptions for certain Cost Centre Group (Alt, Std Hierarchy)s in local language as per regulatory requirement (e.g. Japanese) in the respective country. Such requests must be backed by supporting evidence of the underlying regulatory requirement.
Such data will be collected as part of DCT for the translation texts for Cost Centre Group (Alt, Std Hierarchy)s.

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 Label	Data Type	Length	Syensqo Requirement R = Required : Mandatory field. O = Optional: Not mandatory. If a value is entered it doesn't impact Business Process. C = Conditional: Not mandatory. If a value is entered it impacts Business Process or Reporting. S = System: System generates the value. NU = Not Used
SETHEADER	SETCLASS	SETCLASS	Set Class	CHAR	4	R
SETHEADER	SUBCLASS	SETSUBCLS	Sub class org unit	CHAR	12	R
SETHEADER	SETNAME	SETNAMENEW	Set Name	CHAR	24	R
SETHEADERT	LANGU	SPRAS	Language Key	CHAR	1	R
SETHEADERT	DESCRIPT	SETTEXT	Description	CHAR	40	R
SETNODE	LINEID	SETLINE	Set Line Counter	NUMC	10	R
SETNODE	SETNAME	SETNAMENEW	Parent Group Name	CHAR	24	R
SETNODE	SUBSETNAME	SUBSETNAME	Child Group Name	CHAR	24	C
SETLEAF	SETNAME	SUBSETNAME	Group Node Name	CHAR	24	O
SETLEAF	VALFROM	VALFROM	(Cost Centre) From Value	CHAR	40	O
SETLEAF	VALTO	VALTO	(Cost Centre) To Value	CHAR	40	O

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

Note: When Data Source denotes DCT, no relevancy and extract rules to be applied in Syniti tool. DCT records will be collected by business Data Consultant. 

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extraction Run Sheet

Req #	Requirement description	Team responsible
1.	Ensure DCT is collected for the Cost Centre Group (Alt, Std Hierarchy)s based on the collection template	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.

DCT Rules will be used by the data collectors for collecting data.

Note: Constructed data will be imported into ADM Data Construction page.

There will be two pages -

  1. Main page to contain the hierarchy details with EN Language key Description

  2. Detailed Page will contain descriptions SETHEADERT-LANGU,  ( SETHEADERT-DESCRIPT )  of the SETHEADER-SETNAME in various languages as they are collected.

Table Name	Field Name	Field description	Rule
CSKS	KOKRS	Controlling Aera	Default to 'CO01'
SETHEADER	SETCLASS	Set Class	Set to '0101' for Cost Centre Group
SETHEADER	SUBCLASS	Organizational Unit as Set Subclass	Default to 'CO01'
SETHEADER	SETNAME	Set Name	The standard hierarchy will be organized via the following structure: - GBU / Company Code / Plant The standard hierarchy will only include authorization relevant dimensions for cost centers. All reporting dimension can be covered via alternative (flexible) hierarchies
SETHEADERT	LANGU	Language Key	Language Key of the Text
SETHEADERT	DESCRIPT	Description	Group description
SETNODE	LINEID	Line Number	This will contain the level of the hierarchy nodes ( will do in exact hierarchy form ) - example is given in Load section.
SETNODE	SETNAME_SETNODE	Parent Group Name	The code of the parent group. If node 2, it refers to node 1. If node 1 : no reference.
SETNODE	SUBSETNAME	Child Group Name	The code of the child group. If node 1, it refers to node 2. If node 2 : no reference as it will be directly Cost center values. For the values, refer to the field Set Name.
SETLEAF	SETNAME_SETLEAF	Group Node Name	Changes based on the length of the item/package.
SETLEAF	VALFROM	(Profit Centre) From Value	Cost Centre Value ( Optional in DCT and Cost centres will be assigned to Hierarchy node in Cost Centre DCT part of CNV-1074 Cost Centre )
SETLEAF	VALTO	(Profit Centre) To Value	Cost Centre Value ( Optional in DCT and Cost centres will be assigned to Hierarchy node in Cost Centre DCT part of CNV-1074 Cost Centre )

Descriptions will be collected on multiple languages and therefore a detail page to created and linked to the main page

Table Name	Field Name	Field description	Rule
SETHEADER	SETNAME	Set Name	The standard hierarchy will be organized via the following structure: - GBU / Company Code / Plant The standard hierarchy will only include authorization relevant dimensions for cost centers. All reporting dimension can be covered via alternative (flexible) hierarchies
SETHEADERT	LANGU	Language Key	Language Key of the Text
SETHEADERT	DESCRIPT	Description	Group description

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step description	Team responsible
1.	N/A

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.	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 Cost Centre Group (Alt, Std Hierarchy) Object	Data team
3.	Go to Process Area Launch and Process the Object - Cost Centre Group (Alt, Std Hierarchy) Object - Cost Centre Group (Alt, Std Hierarchy) Object.	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	DCT/ECC	SETHEADER	SETCLASS	Set Class	S/4HANA	SETHEADER	SETCLASS	Set Class	Copy From DCT as-is
2	DCT/ECC	SETHEADER	SETNAME	Set Name	S/4HANA	SETHEADER	SETNAME	Set Name	Copy From DCT as-is
3	DCT/ECC	SETHEADERT	LANGU	Language Key	S/4HANA	SETHEADER	LANGU	Language key	Copy From DCT as-is
4	DCT/ECC	SETHEADERT	DESCRIPT	Description	S/4HANA	SETHEADERT	DESCRIPT	Description	Copy From DCT as-is
5	DCT/ECC	SETNODE	LINEID	Set Line	S/4HANA	SETNODE	LINEID	Set Line	Copy From DCT as-is
6	DCT/ECC	SETNODE	SETNAME	Parent Group Name	S/4HANA	SETNODE	SETNAME	Parent Group Name	Copy From DCT as-is
7	DCT/ECC	SETNODE	SUBSETNAME	Child Group Name	S/4HANA	SETNODE	SUBSETNAME	Child Group Name	Copy From DCT as-is
8	DCT/ECC	SETLEAF	SETNAME	Group Node Name	S/4HANA	SETLEAF	SETNAME	Group Node Name	Copy From DCT as-is
9	DCT/ECC	SETLEAF	VALFROM	Cost Centre ( From Value )	S/4HANA	SETLEAF	VALFROM	Valid-From Date	Copy From DCT as-is
10	DCT/ECC	SETLEAF	VALTO	Cost Centre ( To Value )	S/4HANA	SETLEAF	VALTO	Valid-To Date	Copy From DCT as-is

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
N/A

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields and values are imported into ADM Construction page correctly	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. Language key(LANGU) for description in various languages maintained.
Record Count	Record Count Confirm the record counts in preload summary report Total Records: To be Filled in Summary Report Valid Records: To be Filled in Summary Report Invalid Records: To be Filled in Summary Report

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 the DCT (Data Construction Template)

Accuracy

Task	Action
Conversion accuracy	Verify Cost Centre Group (Alt, Std Hierarchy)s 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 SETHEADER, SETLEAF and SETNODE  ( with SETCLASS = '0101' ) to confirm copied fields are accurately copied. ( If applicable)

Load

Loading of standard hierarchy: Load Template is different from the data collection template. Loading of standard hierarchy will be done using LSMW with Idoc ( COSTCENTERGROUP_CREATE_01) as the technology behind. 

Loading of Alternate hierarchy: Loading of alternate hierarchy will be done using LSMW with Idoc ( COSTCENTERGROUP_CREATE_01) as the technology behind. However, some fiori based app will be explored to check if that could be used for upload alternate hierarchy. In this option,  loading is done using either the "Manage Global Hierarchies" (F2918) or "Manage Flexible Hierarchies" (F2759) app in your Fiori launchpad.

Loading of Descriptions in various Languages: Loading of descriptions in various languages will be done using tcode SE63.

Three exports views will be required to upload this object. 

Export view 1. 

Please generate an export view for the load template as in the table below, details of mapping of fields between DCT to load template.

LNIND = H for the record where DCT field SETNAME is empty

LNIND = L for all the other lines

Parent = DCT Field SETNAME_SETNODE

VALU1 = DCT Field SUBSETNAME

VALU2 = DCT Field LINEID

VALU3 = 0 for standard hierarchy and count of VALFROM for combination of other fields ( LNIND, Parent, VALU1, VALU2 ) 

VALU4 = DCT Field DESCRIPT

LNIND	Parent	VALU1	VALU2	VALU3	VALU4
H		<Controlling area - KOKRS>
L	<SETHEADER-SETNAME>	<SETHEADER-SETNAME>	0	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 1	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 2	0	<SETHEADERT-DESCRIPT>
L	<SSETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 3	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 4	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 4	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 3	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 4	0	<SETHEADERT-DESCRIPT>
L	<SETNODE-SETNAME>	<SETNODE-SUBSETNAME>	<SETNODE-LINEID> E.G 4	0	<SETHEADERT-DESCRIPT>

Export view 2.

Generate 2nd export view containing below columns. This view will contain the profit centres to be assigned to the hierarchy node. 

This view is created for the non-blank entries from SETLEAF.

SETNAME	VALFROM	VALTO
<SETLEAF-SETNAME>	<SETLEAF-VALFROM>	<SETLEAF-VALTO>
<SETLEAF-SETNAME>	<SETLEAF-VALFROM>	<SETLEAF-VALTO>
<SETLEAF-SETNAME>	<SETLEAF-VALFROM>	<SETLEAF-VALTO>

Export view 3.

Generate 3rd view containing the descriptions of the Hierarchy for different languages. 

SETNAME	LANGUAGE	DESCRIPTION
<SETHEADER-SETNAME>	<SETHEADER-LANGU>	<SETHEADER-DESCRIPT>
<SETHEADER-SETNAME>	<SETHEADER-LANGU>	<SETHEADER-DESCRIPT>
<SETHEADER-SETNAME>	<SETHEADER-LANGU>	<SETHEADER-DESCRIPT>

Note:  Description translation data which will be given in the export view 3, will be loaded using tcode SE63.  LSMW will be created based on the tcode SE63 to enable mass upload of this data. However, further checks will be done to check if some Fiori App could be used for uploading. 

Note: 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_DCT, 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 Cost Centre Group (Alt, Std Hierarchy) Object using Migration Cockpit Object for Cost Centre Group (Alt, Std Hierarchy) 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

 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

Post-Load Validation

Project Team

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

Completeness

Task	Action
Reconciliation of Record Count	Check Record count between DCT, Preload file and target extracted data from tables SETHEADER, SETNODE, SETLEAF. A Summary report to be added in the post-load report

Accuracy

Task	Action
Check values in key fields for accuracy	Refer to the post-load file and Manual check of the Loaded data using KSH3 and SE16N

Business

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

Completeness

Task	Action
Record Count Check	Business to check Post-Load File and Summary report in post-load

Accuracy

Task	Action
Spot check	Spot check some sample records from the post-load report to be picked for checking in SAP transaction code KSH3 to verify accuracy of the data.

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