| Status | |
|---|---|
| Owner | |
| Stakeholders | WELENSKY-ext, DaveERGUIZA-ext, Pinky Love TEE-ext, Paul JOSHI-ext, Aditya VILARES, 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 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 (QPGR.STATUS = 2)
The data from legacy system excludes:
- All inactive Catalog Code Groups and Codes defined in the source systems (QPGR.STATUS <> 2)
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.
| 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 Code Groups and Codes from PF2 and WP2 as Catalog Code Groups and Codes 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 | Mandatory (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
| 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 |
Note: Each Catalog Code Group must have at least 1 entry for Catalog Code
6. 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 must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish
7. 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 | Mandatory (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
8. 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 |
| QPCT | CODE | QCODE | Code | CHAR | 4 | 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 ApplicableExtraction
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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
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 |
|---|---|---|---|---|
| Not Applicable |
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.
- The extracted report will be loaded into the required structure using the DCT.
- Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.
Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.
1. Catalog Code Group DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Mandatory Allowed values from: TQ15-KATALOGART |
| CODEGRUPPE | Code Group | Mandatory Follow Naming Convention: X (First character for catalog type)-NN (Technical Object Type)-NN (Sequential Number)
OTH-Catalog Profile_Technical Object Type_Naming Convention |
| STATUS | Status of Master Record | Non-Editable Default to "2" |
2. Catalog Code Group Short Text DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Mandatory Key to link to Catalog Code Group |
| CODEGRUPPE | Code Group | Mandatory Key to link to Catalog Code Group |
| SPRACHE | Language | Mandatory 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 | Mandatory 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) |
3. Catalog Code Group Long Text Header DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Non-Editable Key to link to Catalog Code Group Direct Mapping from Catalog Code Group Long Text Line: KATALOGART field |
| CODEGRUPPE | Code Group | Non-Editable Key to link to Catalog Code Group Direct Mapping from Catalog Code Group Long Text Line: Catalog field: CODEGRUPPE field |
| LTEXTV | Long Text Exists for the Code Group | Non Editable Default to "X" |
| TDOBJECT | Texts: application object | Non-Editable Direct Mapping from Catalog Code Group Long Text Line: TDOBJECT field |
| TDNAME | Name | Non-Editable Direct Mapping from Catalog Code Group Long Text Line: TDNAME field |
| TDID | Text ID | Non-Editable Direct Mapping from Catalog Code Group Long Text Line: TDID field |
| TDSPRAS | Language Key | Non-Editable Direct Mapping from Catalog Code Group Long Text Line: TDSPRAS field |
Note: The Catalog Code Group Long Text Header is derived from the unique values of the Catalog Code Group Long Text Line upon save for the following fields:
- Catalog
- Code Group
- Texts: applicable object
- Name
- Text ID
- Language Key
4. Catalog Code Group Long Text Line DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Mandatory Key to link to Catalog Code Group |
| CODEGRUPPE | Code Group | Mandatory Key to link to Catalog Code Group |
| TDOBJECT | Texts: application object | Non-Editable Default to "QKATALOG" |
| TDNAME | NAME | Non-Editable (Derived upon save) Character 1-3: Direct Mapping to Client Number (eg 100) Character 4: Direct Mapping to Catalog (eg 5) Character 5-12: Direct Mapping to Code Group (eg 5-01-01) Character 13: Direct Mapping to Language (eg E) Sample: "10055-01-01 E" |
| TDID | Text ID | Non-Editable Default to "QPGT" |
| TDSPRAS | Language Key | Mandatory Must be either one of the following: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish |
| CLUSTD_TAG | Tag column | Non-Editable Default to "*" |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
5. Catalog Code DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Non-Editable Direct Mapping from Catalog Code Short Text: KATALOGART field |
| CODEGRUPPE | Code Group | Non-Editable Direct Mapping from Catalog Code Short Text: CODEGRUPPE field |
| CODE | Code | Non-Editable Direct Mapping from Catalog Code Short Text: CODE field |
Note: The Catalog Code is derived from the unique values of the Catalog Code Short Text upon save for the following fields:
- Catalog
- Code Group
- Code
6. Catalog Code Short Text DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Mandatory Key to link to Catalog Code Group |
| CODEGRUPPE | Code Group | Mandatory Key to link to Catalog Code Group |
| CODE | Code | Mandatory Follow Naming Convention: NN (Last 2 number in Code Group) NN (Sequential Number) |
| SPRACHE | Language | Mandatory 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 | Mandatory 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) |
7. Catalog Code Long Text Header DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Non-Editable Direct Mapping from Catalog Code Long Text Line: KATALOGART field |
| CODEGRUPPE | Code Group | Non-Editable Direct Mapping from Catalog Code Long Text Line: CODEGRUPPE field |
| CODE | Code | Non-Editable Direct Mapping from Catalog Code Long Text Line: CODE field |
| LTEXTV | Long Text Exists for the Code | Non-Editable Default to "X" |
| TDOBJECT | Texts: application object | Non-Editable Direct Mapping from Catalog Code Long Text Line: TDOBJECT field |
| TDNAME | Name | Non-Editable Direct Mapping from Catalog Code Long Text Line: TDNAME field |
| TDID | Text ID | Non-Editable Direct Mapping from Catalog Code Long Text Line: TDID field |
| TDSPRAS | Language Key | Non-Editable Direct Mapping from Catalog Code Long Text Line: TDSPRAS field |
Note: The Catalog Code Long Text Header is derived from the unique values of the Catalog Code Long Text Line upon save for the following fields:
- Catalog
- Code Group
- Code
- Texts: applicable object
- Name
- Text ID
- Language Key
8. Catalog Code Long Text Line DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| KATALOGART | Catalog | Mandatory Key to link to Catalog Code |
| CODEGRUPPE | Code Group | Mandatory Key to link to Catalog Code |
| CODE | Code | Mandatory Key to link to Catalog Code |
| TDOBJECT | Texts: application object | Non-Editable Default to "QKATALOG" |
| TDNAME | Name | Non-Editable (Derived upon save) Character 1-3: Direct Mapping to Client Number (eg 100) Character 4: Direct Mapping to Catalog (eg 5) Character 5-12: Direct Mapping to Code Group (eg 5-01-02) Character 13-15: Direct Mapping to Code (eg 0233) Character 16 -21: Default to "000001" (Version number) Character 12: Direct Mapping to Language (eg E) Sample: "10055-01-02 0233000001E" |
| TDID | Text ID | Non-Editable Default to "QPCT" |
| TDSPRAS | Language Key | Mandatory Must be either one of the following: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish |
| CLUSTD_TAG | Tag column | Non-Editable Default to "*" |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| 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.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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 – 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
1. Catalog Code Group
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPGR | STATUS | Status of Master Record | S/4 Hana | QPGR | STATUS | Status of Master Record | Direct Mapping |
2. Catalog Code Group Short Text
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGT | KATALOGART | Catalog | S/4 Hana | QPGT | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGT | CODEGRUPPE | Code Group | S/4 Hana | QPGT | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPGT | SPRACHE | Language | S/4 Hana | QPGT | SPRACHE | Language | Direct Mapping |
| 4 | DCT | QPGT | KURZTEXT | Short Text | S/4 Hana | QPGT | KURZTEXT | Short Text | Value Mapping: OTH_Informal Words and OTH_Informal Characters Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings. |
3. Catalog Code Group Long Text Header
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPGT | LTEXTV | Long Text Exists for the Code Group | S/4 Hana | QPGT | LTEXTV | Long Text Exists for the Code Group | Direct Mapping |
| 4 | DCT | STXH | TDOBJECT | Texts: application object | S/4 Hana | STXH | TDOBJECT | Texts: application object | Direct Mapping |
| 5 | DCT | STXH | TDNAME | Name | S/4 Hana | STXH | TDNAME | Name | Direct Mapping |
| 6 | DCT | STXH | TDID | Text ID | S/4 Hana | STXH | TDID | Text ID | Direct Mapping |
| 7 | DCT | STXH | TDSPRAS | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Direct Mapping |
4. Catalog Code Group Long Text Line
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | STXL | TDOBJECT | Texts: application object | S/4 Hana | STXL | TDOBJECT | Texts: application object | Direct Mapping |
| 4 | STXL | TDNAME | TDOBNAME | Name | S/4 Hana | STXL | TDNAME | Name | Direct Mapping Sample: "10055-01-01 E" |
| 5 | DCT | STXL | TDID | Text ID | S/4 Hana | STXL | TDID | Text ID | Direct Mapping |
| 6 | DCT | STXL | TDSPRAS | Language Key | S/4 Hana | STXL | TDSPRAS | Language Key | Direct Mapping |
| 7 | DCT | STXL | CLUSTD_TAG | Tag column | S/4 Hana | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 8 | DCT | STXL | CLUSTD_LINE | Text Line | S/4 Hana | STXL | CLUSTD_LINE | Text Line | Direct Mapping |
5. Catalog Code
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping A Global Value Mapping (Catalog Code Group and Code) is created to reference old Catalog Code Group and Code. |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping A Global Value Mapping (Catalog Code Group and Code) is created to reference old Catalog Code Group and Code. |
| 3 | DCT | QPCT | CODE | Code | S/4 Hana | QPCT | CODE | Code | Direct Mapping A Global Value Mapping (Catalog Code Group and Code) is created to reference old Catalog Code Group and Code. |
6. Catalog Code Short Text
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPCT | CODE | Code | S/4 Hana | QPCT | CODE | Code | Direct Mapping |
| 4 | DCT | QPCT | SPRACHE | Language | S/4 Hana | QPCT | SPRACHE | Language | Direct Mapping |
| 5 | DCT | QPCT | KURZTEXT | Short Text for Code | S/4 Hana | QPCT | KURZTEXT | Short Text for Code | Value Mapping: OTH_Informal Words and OTH_Informal Characters Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings. |
7. Catalog Code Long Text Header
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPCT | CODE | Code | S/4 Hana | QPCT | CODE | Code | Direct Mapping |
| 4 | DCT | QPCT | LTEXTV | Long Text Exists for the Code | S/4 Hana | QPCT | LTEXTV | Long Text Exists for the Code | Direct Mapping |
| 5 | DCT | STXH | TDOBJECT | Texts: application object | S/4 Hana | STXH | TDOBJECT | Texts: application object | Direct Mapping |
| 6 | DCT | STXH | TDNAME | Name | S/4 Hana | STXH | TDNAME | Name | Direct Mapping |
| 7 | DCT | STXH | TDID | Text ID | S/4 Hana | STXH | TDID | Text ID | Direct Mapping |
| 8 | DCT | STXH | TDSPRAS | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Direct Mapping |
8. Catalog Code Long Text Line
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | QPGR | KATALOGART | Catalog | S/4 Hana | QPGR | KATALOGART | Catalog | Direct Mapping |
| 2 | DCT | QPGR | CODEGRUPPE | Code Group | S/4 Hana | QPGR | CODEGRUPPE | Code Group | Direct Mapping |
| 3 | DCT | QPCT | CODE | Code | S/4 Hana | QPCT | CODE | Code | Direct Mapping |
| 4 | DCT | STXL | TDOBJECT | Texts: application object | S/4 Hana | STXL | TDOBJECT | Texts: application object | Direct Mapping |
| 5 | DCT | STXL | TDNAME | Name | S/4 Hana | STXL | TDNAME | Name | Direct Mapping Sample: "10055-01-02 0233000001E" |
| 6 | DCT | STXL | TDID | Text ID | S/4 Hana | STXL | TDID | Text ID | Direct Mapping |
| 7 | DCT | STXL | TDSPRAS | Language Key | S/4 Hana | STXL | TDSPRAS | Language Key | Direct Mapping |
| 8 | DCT | STXL | CLUSTD_TAG | Tag column | S/4 Hana | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 9 | DCT | STXL | CLUSTD_LINE | Text Line | S/4 Hana | STXL | CLUSTD_LINE | Text Line | Direct Mapping |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| Catalog Code Group and Code | Mapping of legacy Catalog Code Group and Code to S/4 HANA Catalog Code Group and Code |
| OTH_Informal Words | List of Informal Words and the words used to replace |
| OTH_Informal Characters | List of Informal Characters |
| OTH-Catalog Profile_Technical Object Type_Naming Convention | List of technical object type with the Catalog Profile naming convention |
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
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:
- 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
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 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
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 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.
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.