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

Compare with Current View Page History

« Previous Version 14 Next »

Status

  Approved

Owner

PUN-ext, Eddy 

Stakeholders

WELENSKY-ext, Dave ERGUIZA-ext, Pinky LoveVILARES, inesLEIGHTON-ext, Dean Betty Yue; Aurelia Stefanescu ; [Syniti POD Lead]; [Syniti Consultant]

Purpose

The purpose of this document is to define the conversion approach to create Catalog Code Groups & Codes in S/4 HANA.

Catalog Code Groups and Codes are part of the classification system. They help categorize and standardize data for reporting, analysis, and operational purposes.

A Code Group is a collection of related codes that belong to a specific catalog. It organizes codes into logical groups for easier management and selection.

A Code is an individual entry within a code group that represents a specific value or description. It is used to classify or describe an task, damage, or cause.

Syensqo utilizes Catalog Code Group and Codes within the SAP S/4HANA system to define and manage its assets' Object Type, Cause, Action, Failure mode and Task.


Conversion Scope

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

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

Catalog Code Groups and 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 and 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 and Codes are considered for data migration. 

The data from legacy system includes:

  1. All Catalog Code Groups and Codes defined in the source systems

The data from legacy system excludes:

  1. Not applicable since all Catalog Code Groups and Codes defined in the source systems are considered valid


For reference, the Catalog Code Groups and 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
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Catalog Code Groups and Codes will be collected via DCT. An initial extract of the relevant Catalog Code Groups and Codes will be provided in google sheet format to assist business in decision making on including any relevant Catalog Profiles from PF2 and WP2 as Catalog Profile in S/4 HANA.

Any additional Catalog Code Groups and Codes that need to be created to support the new design may be added in the DCT.

A review and standardization will be done across all Catalog Code Groups and Codes in the DCT. 

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. 

40,000S/4HANA40,000















Additional Information

Multi-language Requirement

Catalog Code Groups and Codes description will be made available in English.

Multi language is supported for Catalog Code Groups and Code. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Catalog Code Groups and Code.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable


Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
T352C









































Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1007-001C1Legacy Catalog Code Groups and Codes which are not mappedLegacy Catalog Groups and Code which do not have mapped S/4 HANA valuesAll key fieldsPF2, WP2








Conversion Process

The following represents the high-level process for DCT:

Data Privacy and Sensitivity

Not Applicable


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 DescriptionTeam 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 data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam Responsible

Not applicable










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 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 DescriptionTeam Responsible

1

Ensure all mapping tables are up to date.

Syniti

2

In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance

Syniti

3

Go to Process Area Launch and Process the Object – Catalog Code Groups and Codes

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Execute the transformation to prepare the target tables

Syniti

6

Validate data from pre-load and invalid reports by region 

Business/Data owner

7

Generate export(load) file (If load tool is not dspIntergrate)

Syway Data Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping 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

TaskAction

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

TaskAction

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

Completeness

TaskAction

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

TaskAction

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 DescriptionTeam Responsible

TBC










Load Phase and Dependencies

Configuration

Item #Configuration Item
1Language Key




Conversion Objects

Object #Preceding Object Conversion Approach

Not Applicable




Error Handling

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

Completeness

TaskAction

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

TaskAction

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 and Codes is in scope based on data design and any exception requested by business.
  • Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
  • Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
  • All Catalog Code Groups and Codes in the source systems are "active" as they are defined in configuration


See also

Change log

Version Published Changed By Comment
CURRENT (v. 14) Mar 13, 2026 07:26 PUN-ext, Eddy
v. 102 Mar 11, 2026 13:15 PUN-ext, Eddy
v. 101 Feb 02, 2026 14:41 PUN-ext, Eddy
v. 100 Feb 02, 2026 14:38 PUN-ext, Eddy
v. 99 Feb 02, 2026 14:35 PUN-ext, Eddy
v. 98 Jan 30, 2026 14:31 PUN-ext, Eddy
v. 97 Jan 30, 2026 14:31 PUN-ext, Eddy
v. 96 Jan 29, 2026 14:12 PUN-ext, Eddy
v. 95 Jan 29, 2026 14:09 PUN-ext, Eddy CR0280-Additional DCTs for Approved Conversion Specs
v. 94 Jan 29, 2026 14:08 PUN-ext, Eddy

Go to Page History

Workflow history

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

  • No labels