Status
Owner	PUN-ext, Eddy
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 to create Catalog Code Groups & Codes in S/4 HANA.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

Conversion Scope

The scope of this document covers the approach for migrating active Catalog Code Groups & Codes into S/4 HANA following the Catalog Code Groups & Codes Master Data Design Standard.

The conversion of Catalog Code Groups & Codes follows the endorsed EAM Core Data Design describing the Asset Identification Methodology.

Catalog Code Groups & Codes Data from legacy will consolidated based on the S/4 HANA design and will be constructed via a common DCT which is target ready. This also means multiple GBU could be using the same Catalog Code Groups & Codes based on the Asset Identification Methodology.

There will not be a direct conversion from legacy to S/4 HANA, however there will be a mapping to ensure all the valid and active legacy Catalog Code Groups & Codes are considered for data migration. 

The data from legacy system includes:

1. All Catalog Code Groups & Codes that are mapped to S/4 HANA Catalog Profiles

The data from legacy system excludes:

1. All Catalog Code Groups & Codes that are not mapped to S/4 HANA Catalog Profiles

For reference, the Catalog Code Groups & Codes in S/4 HANA are not transformed based on the legacy mapping, but they are derived based on the logic of the Asset Identification Methodology.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2, WP2	Valid Catalog Code Groups and Catalog Codes	40000	S/4HANA	40000

Additional Information

Multi-language Requirement

TBC

Document Management

N/A

Legal Requirement

N/A

Special Requirements

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	Requirement
T352C

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
1007-001	C3	Duplicate Catalog Code Group Description	Catalog Code Group & Codes as per Relevancy Criteria where the Code Group Description is used by more than one Catalog Code Group.	All key fields	PF2, WP2
1007-002	C1	Missing Catalog Code Group Descriptions	Catalog Code Group & Codes as per Relevancy Criteria where there are blank Catalog Code Group Descriptions.	All key fields	PF2, WP2
1007-003	C2	Catalog Code Group Descriptions with Informal Words	Catalog Code Group & Codes as per Relevancy Criteria which contain [Informal Words] in the Catalog Code Group Description	All key fields	PF2, WP2
1007-004	C3	Duplicate Catalog Codes by Description	Catalog Code Group & Codes as per Relevancy Criteria where the Code Description is used by more than one Catalog Type + Catalog Code Group Combination.	All key fields	PF2, WP2
1007-005	C1	Missing Catalog Code Descriptions	Catalog Code Group & Codes as per Relevancy Criteria where there are blank Code Descriptions.	All key fields	PF2, WP2
1007-006	C2	Catalog Code Descriptions with Informal Words	Catalog Code Group & Codes as per Relevancy Criteria which contain [Informal Words] in the Catalog Code Group or Code Descriptions.	All key fields	PF2, WP2
1007-007	C1	Company Code incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Company Code (T001)	All key fields	PF2, WP2
1007-008	C1	Plant incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Plant (T001W)	All key fields	PF2, WP2
1007-009	C1	Incorrect Plant / Company Code Combination	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Plant / Company Code Combination (T001K)	All key fields	PF2, WP2
1007-010	C1	Inspection catalog type ind incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Inspection catalog type ind (TQ15)	All key fields	PF2, WP2
1007-011	C1	Defect Class incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Defect Class (TQ17)	All key fields	PF2, WP2
1007-012	C1	Maintenance planner group incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Maintenance planner group (T024I)	All key fields	PF2, WP2
1007-013	C1	Notification Type incorrect.	Catalog Code Group & Codes as per Relevancy Criteria with Invalid Notification Type (TQ80)	All key fields	PF2, WP2
1007-014	C1	Legacy Catalog Code and Code Group which are not mapped	Legacy Catalog Code and Code Group which do not have mapped S/4 HANA values	All key fields	PF2, WP2

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 following represents the high-level process for DCT:

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

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

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

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
Verify Record Count	Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Data team to verify that all fields below meet pass the checks: 1. Mandatory Fields 2. Field and Value Mapping Correctness 3. Null Checks 4. Text Length Checks
Review error reports	Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

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

Completeness

Task	Action
Verify Record Count	Business team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business  to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off data)

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible

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
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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
Verify Count	Data team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue, or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Data team to verify that the Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Business

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

Completeness

Task	Action
Verify Count	Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Key Assumptions

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

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history