Status	Approved
Owner	PUN-ext, Eddy
Stakeholders	WELENSKY-ext, Dave ERGUIZA-ext, Pinky Love TEE-ext, Paul JOSHI-ext, Aditya VILARES, ines LEIGHTON-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 and 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:

All active Catalog Code Groups and Codes defined in the source systems

The data from legacy system excludes:

All inactive Catalog Code Groups and Codes defined in the source systems

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

Source

Scope

Source Approx No. of Records

Target System

Target 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,000

S/4HANA

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

1. Catalog Code Group:

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
QPGR	STATUS	QLOESCHKZ1	Status of Master Record	CHAR	1	Mandatory

2. Catalog Code Group Short Text

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGT	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGT	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
QPGT	SPRACHE	SPRAS	Language	CHAR	1	Mandatory
QPGT	KURZTEXT	QKTEXTGR	Short Text	CHAR	40	Mandatory

Note: Each Catalog Code Group must have 1 entry for each language in scope: English,French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish

3. Catalog Code Group Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
QPGT	LTEXTV	QLTEXTGRP	Long Text Exists for the Code Group	CHAR	1	Checked if Long Text Exist
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory

Note:

Long Text is not mandatory, only load when there is data
One Long Text Header must have at least 1 Long Text Line

4. Catalog Code Group Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
STXL	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory
STXL	CLUSTD (Tag)	TDFORMAT	Tag column	CHAR	1	Mandatory
STXL	CLUSTD (Line)	TDLINE	Text Line	CHAR	72	Mandatory

5. Catalog Code Short Text

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
QPCT	CODE	QCODE	Code	CHAR	4	Mandatory
QPCT	SPRACHE	SPRAS	Language	CHAR	1	Mandatory
QPCT	KURZTEXT	QTXT_CODE	Short Text for Code	CHAR	40	Mandatory

Note: Each Catalog Code Group must have 1 entry for Catalog Code

6. Catalog Code Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
QPCT	CODE	QCODE	Code	CHAR	4	Mandatory
QPCT	LTEXTV	QLTEXTCODE	Long Text Exists for the Code	CHAR	1	Checked if Long Text Exist
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory

Note:

Long Text is not mandatory, only load when there is data
One Long Text Header must have at least 1 Long Text Line

7. Catalog Code Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QPGR	KATALOGART	QKATART	Catalog	CHAR	1	Mandatory
QPGR	CODEGRUPPE	QCODEGRP	Code Group	CHAR	8	Mandatory
STXL	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory
STXL	CLUSTD (Tag)	TDFORMAT	Tag column	CHAR	1	Mandatory
STXL	CLUSTD (Line)	TDLINE	Text Line	CHAR	72	Mandatory

Catalog Code Groups and Codes Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Catalog Code Groups and Codes information follows the Master Data Standard document that is located here.

Data Cleansing

No data cleansing is required for Catalog Code Groups and Codes in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Catalog Code Groups and Codes data will be populated directly in the Data Collection Template (DCT).

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		Not Applicable

Conversion Process

The high-level process is represented by the diagram below:

Collection will be done manually in the Data Collection Template for the following scenarios:

For sites not on SAP-PF2 or WP2 systems
For new Catalog Groups and Codes that need to be created to support the to-be design

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

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.
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
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
	Not Applicable

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.

1. Catalog Code Group DCT Rules

Field Name

Field Description

Rule

KATALOGART

Catalog

Allowed values from: TQ15-KATALOGART

CODEGRUPPE

Code Group

Follow Naming Convention:

X (First character for catalog type)-NN (Technical Object Type)-NN (Sequential Number)

The Catalog Type must match KATALOGART
The Technical Object Type must exist in the following mapping table:

OTH-Catalog Profile_Technical Object Type_Naming Convention

STATUS

Status of Master Record

Default to "2"

2. Catalog Code Group Short Text DCT Rules

Field Name	Field Description	Rule
KATALOGART	Catalog	Key to link to Catalog Code Group
CODEGRUPPE	Code Group	Key to link to Catalog Code Group
SPRACHE	Language	For each Catalog Code Group record, there must be a single record each for the following languages: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish
KURZTEXT	Short Text	Text must be translated according to the language key Cannot have duplicate records based on corresponding language text (eg 2 Catalog Code Groups cannot have the same English language key Text, or 2 Catalog Code Groups cannot have the same Spanish language key texts)

Extraction Dependencies

Item #	Step Description	Team 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 Syniti Migrate to make the data Target ready:

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
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	Obtain DCT Sign-off from Business.	SyWay Data Team
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 error reports	Business/Data owner
7	Generate load files	SyWay Data Team

Transformation Rules

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

Transformation Mapping

Mapping Table Name	Mapping Table Description
Catalog Code Groups	Mapping of legacy Catalog Profile to S/4 HANA Catalog Code Groups.
OTH_Informal Words	List of Informal Words and the words used to replace
OTH_Informal Characters	List of Informal Characters

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	Syniti
2	Ensure all Transformation mappings are up to date.	Syniti

Pre-Load Validation

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

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:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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
1	Ensure Pre-load sign-offs are obtained.	SyWay Data team
2	Go to the load tool and select the correct load Program.	SyWay Data team
3	Proceed with Data load.	SyWay Data team
4	Validate few records loaded by accessing standard transactions.	SyWay Data team
5	Generate the post load reports in the tool.	SyWay Data team
6	Log errors as defects, if any and address resolutions. Close defects.	SyWay Data team
7	Resolve defects by re-upload and re-generate post load reports if necessary.	SyWay 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.	SyWay Data team

Load Phase and Dependencies

Pre-Cutover

Configuration

Item #	Configuration Item
1	T002-Language Key
2	TQ15-Catalog

Conversion Objects

Object #	Preceding Object Conversion Approach
	Not Applicable

Error Handling

Error Type	Error Description	Action Taken
Configuration	Invalid Language Key	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Catalog	Engage Functional team to expedite and fix the error in the system

Post-Load Validation

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 Catalog Code Groups and Codes data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

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 Catalog Code Groups and Codes 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.
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.

Change log

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

Mar 24, 2026	Actor	Type	Activity	Version
Approved	TAN-ext, Charmaine	State	changed state to Approved at 9:16 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v103
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 9:16 am [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Mar 18, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '25 Mar, 2026 07:25 am' at 7:25 am
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 7:25 am	v103
Tech Review	MOUSSA-ext, Eva	State	gave Syniti Team Review approval at 7:25 am CR0281 v. 103 approved
		State	changed expiry date to '23 Mar, 2026 07:25 am' at 7:25 am
		State	changed state to Tech Review at 7:25 am CR0281 v. 103 approved	v103
Pending adjustment	MOUSSA-ext, Eva	State	changed state to Pending adjustment at 7:24 am	v103

Workflow history

Space shortcuts

Page tree

CNV-1007 Catalog Code Groups & Codes

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history