Purpose
The purpose of this document is to define the conversion approach to create EAM Class in S/4 HANA.
Legacy Plant Maintenance Class is using a diverse range of formats across the different systems. There are instances where the same classes are duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM classes will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active EAM Classes from Legacy Source Systems into S/4HANA following the EAM Class Master Data Design Standard.
Grouping of objects with particular features can be achieved by creating Classes in the S/4 HANA system. A large number of objects can be managed and logically organized using this functionality.
Syensqo will utilize SAP Classification system (class and characteristic functionality) to assign any additional data attributes to following objects:
- PM Assembly
- Equipment
- Functional Location
- </Start CR0164>
Document Management (DIR)</End CR0164> - Task list
- Measuring Points
- Maintenance Plans
Classes allow you to group objects based on specific criteria that you define.
- Classes are created for specific object types.
- The Class Type determines which object types can be classified within a given class.
- Characteristics are assigned to classes to describe the objects being classified.
- When assigning a characteristic to a class, its values can be customized or overwritten as needed.
From the current source systems’ perspective, Class and Characteristic concepts already exist (but in slightly different structure). Class data values are independently managed between PF2 and WP2. While these have been identified as source systems, a considerable amount of data construction will be required to support the production of data load sheets in the desired format.
The data from legacy system includes:
- Classes (KLAH-CLASS) with below Class Type (KLAH-KLART)
- 001-Material Class
- 002-Equipment Class
- 003-Functional Location
- </Start CR0164>
017-Document Management (DIR)</End CR0164> - 018-Task List Class
- 037-Measuring Point Class
- 080-Maintenance Plans Class
- Status (KLAH-STATU) = 1 (Released)
The data from legacy system excludes:
- Not Applicable
List of Tables to extract for this object is maintained here: Extract Table Register
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 | Class will be collected via DCT. An initial extract of the relevant classes will be provided in google sheet format to assist business in decision making on including any relevant classes from PF2 and WP2 as EAM Class. Any additional classes 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 classes in the DCT. Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. Note: A full Data Construct will be created for Class, as the SyWay design is changing and a complete standardization will be performed. While data may already exist, it cannot be easily transformed to align with the new SyWay data setup. | 1,500 | 3,000 |
Additional Information
Multi-language Requirement
EAM Class description will be made available in English.
Multi language is supported for EAM Class. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Class.
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. Class
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| KLAH | STATU | KLSTATUS | Class status | CHAR | 1 | Mandatory |
| KLAH | KLAGR | KLASSENGR | Class Group | CHAR | 10 | |
| KLAH | VONDT | VONDAT | Valid-From Date | DATS | 8 | Mandatory |
| KLAH | BISDT | BISDAT | Valid-to date | DATS | 8 | Mandatory |
| KLAH | PRAUS | GLKLAFZ | Same Classification/ Do Not Check | CHAR | 1 | Mandatory |
2. Class Descriptions / Keywords
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| SWOR | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| SWOR | KSCHL | KSCHL | Keyword | CHAR | 40 | Mandatory |
| SWOR | POSNR | POSNR | Order Number of Description | CHAR | 3 | Mandatory |
Notes:
Each Class must have 1 Description for each language, which also serves as the primary keyword. The required languages are English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish.
Where applicable, additional keywords will be added for specific languages as needed.
3. Characteristic Assignment
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| KSML | IMERK | ATINN | Internal characteristic | NUMC | 10 | Mandatory |
| CABN | ATNAM | ATNAM | Characteristic Name | CHAR | 30 | Mandatory |
| </Start CR0240> | ||||||
| KSML | POSNR | KPOSNR | Item Number | CHAR | 3 | Mandatory |
| </End CR0240> | ||||||
Data Cleansing
No data cleansing is required for Classes in the legacy systems. If any cleansing is deemed necessary, it will be performed outside of the systems.
As a result, the cleansed Characteristics 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 new classes 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 as reference point to identify the records that are applicable for the data construction in the DCT.
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
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 EAM Class 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.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Format:
- Line 1: Mandatory / Conditional
- Line 2: Remaining text
1. Class Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| CLASS | Class Name | Mandatory. NAMING CONVENTION: Class Name for Functional Location and Equipment will be: EAM_X_XX_XXX: Classes shall be created such that they can be Reusable. A General Class(EAM_9999) shall be created to group all the Characteristics that range across all the Master Data Objects |
| KLART | Class Type | Mandatory. Allowed Values: 001-Material Class Classes are created within the class type for the respective technical objects |
| KLAGR | Class Group | Conditional. If the Class belongs to a group of similar Classes, assign it to the appropriate Class group. Otherwise, leave the field blank.
|
| VONDT | Valid-From Date | Conditional.
|
| BISDT | Valid-to date | Conditional.
|
| KSCHL_EN | Description (English) | Mandatory. Ensure that this Class Description is in English. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_FR | Description (French) | Mandatory. Ensure hat this Class Description is in French. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_IT | Description (Italian) | Mandatory. Ensure that this Class Description is in Italian. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_ZH | Description (Mandarin) | Mandatory. Ensure that this Class Description is in Mandarin. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_PT | Description (Brazilian Portuguese) | Mandatory. Ensure that this Class Description is in Portuguese. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_DE | Description (German) | Mandatory. Ensure that this Class Description is in German. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
| KSCHL_ES | Description (Spanish) | Mandatory. Ensure that this Class Description is in Spanish. Class description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: |
2. Additional Class Keyword Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| CLASS | Class number | Mandatory. Class Number + Class Type: Should exist in Class Data Construction Rules DCT |
| KLART | Class Type | Mandatory. Class Number + Class Type: Should exist in Class Data Construction Rules DCT |
| POSNR | Order Number of Description | Mandatory. The numbering must start from 002 and increase sequentially (e.g., 002, 003, 004 etc.). The sequence should follow the same order in which the keywords are displayed on the SAP screen. |
| KSCHL_EN | Keyword (English) | Mandatory. Ensure that this Keyword is in English. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_FR | Keyword (French) | Mandatory. Ensure that this Keyword is in French. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_IT | Keyword (Italian) | Mandatory. Ensure that this Keyword is in Italian. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_ZH | Keyword (Mandarin) | Mandatory. Ensure that this Keyword is in Mandarin. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_PT | Keyword (Brazilian Portuguese) | Mandatory. Ensure that this Keyword is in Portuguese. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_DE | Keyword (German) | Mandatory. Ensure that this Keyword is in German. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
| KSCHL_ES | Keyword (Spanish) | Mandatory. Ensure that this Keyword is in Spanish. Keyword should be in Title Case. Duplicate Keywords will not be allowed. |
Note: Populate only if we require additional Keywords for the Class.
3. Characteristic Assignment Data Construction Rules
| Field Description | Rule | |
|---|---|---|
| CLASS | Class number | Mandatory. Class Number + Class Type: Should exist in Class Data Construction Rules DCT |
| KLART | Class Type | Mandatory. Class Number + Class Type: Should exist in Class Data Construction Rules DCT |
| ATNAM | Characteristic Name | Mandatory. Should exist in Characteristics DCT for the same Class Type. |
</Start CR0240> POSNR_CHAR </End CR0240> | </Start CR0240> Order Number of Characteristic </End CR0240> | </Start CR0240> Mandatory. The numbering must start from 001 and increase sequentially (e.g., 001, 002, 003 etc.). The sequence should follow the same order in which the Characteristics assignment to Class are displayed on the SAP screen. </End CR0240> |
Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| Field Name | 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:
- 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
- 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 – Class | 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 | Syniti |
Transformation Rules
1. Class
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class Name | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | KLAH | STATU | Class status | Default to "1" |
| 4 | DCT | KLAH | KLAGR | Class Group | S/4 Hana | KLAH | KLAGR | Class Group | Direct Mapping |
| 5 | DCT | KLAH | VONDT | Valid-From Date | S/4 Hana | KLAH | VONDT | Valid-From Date | If has value in DCT, Direct Mapping. If blank, derive the date as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "1009" and Field Name = "KLAH-VONDT". |
| 6 | DCT | KLAH | BISDT | Valid-to date | S/4 Hana | KLAH | BISDT | Valid-to date | If has value in DCT, Direct Mapping. Otherwise, Default to 31129999 |
| 7 | - | - | - | - | S/4 Hana | KLAH | PRAUS | Same Classification/ Do Not Check | Default to "X" (Tick box checked) *Need to translate for LTMC Load* |
2. Class Description / Keyword
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_EN | Description (English) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "E" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_FR | Description (French) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "F" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_IT | Description (Italian) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "I" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_ZH | Description (Mandarin) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "1" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_PT | Description (Brazilian Portuguese) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "P" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_DE | Description (German) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "D" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_ES | Description (Spanish) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "S" |
| 5 | - | - | - | - | S/4 Hana | SWOR | POSNR | Order Number of Description | Default to "001" |
3. Additional Class Keyword
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_EN | Description (English) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "E" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_FR | Description (French) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "F" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_IT | Description (Italian) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "I" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_ZH | Description (Mandarin) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "1" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_PT | Description (Brazilian Portuguese) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "P" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_DE | Description (German) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "D" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | SWOR | KSCHL_ES | Description (Spanish) | S/4 Hana | SWOR | KSCHL | Description | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | SWOR | SPRAS | Language Key | Default to "S" |
| 5 | DCT | SWOR | POSNR | Order Number of Description | S/4 Hana | SWOR | POSNR | Order Number of Description | Direct Mapping |
4. Characteristic Assignment
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KLAH | CLASS | Class number | S/4 Hana | KLAH | CLASS | Class number | Direct Mapping |
| 2 | DCT | KLAH | KLART | Class Type | S/4 Hana | KLAH | KLART | Class Type | Direct Mapping |
| 3 | DCT | CABN | ATNAM | Characteristic Name | S/4 Hana | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D |
</Start CR0240> | |||||||||
| 4 | DCT | KSML | POSNR_CHAR | Order Number of Characteristic | S/4 Hana | KSML | POSNR | Item Number | Direct Mapping |
</End CR0240> | |||||||||
Note: Class Number + Class Type: Should exist in Class Header
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| Class A2D | Old to New Class A2D |
| Characteristic A2D | Old to New Characteristic A2D |
| OTH_Migration_Date Relevant Values A2D | Dates to be defaulted for A2D objects for each Migration Cycle |
List of Transformation Mappings with additional details is maintained here: Transformation Mappings
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | SyWay Data Team |
| 2 | Ensure all Transformation mappings are up to date. | SyWay Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the 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 Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT 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 Keys |
| 2 | TCLA-Class Types |
| 3 | TCLG-Class Groups |
| 4 | TCLU-Class Status |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1015 | Characteristics |
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 Class Type | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Class Group | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Class Status | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid or Inactive Characteristic assigned | Expedite whether the master data is changed in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | SyWay A2D 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 | Verify that the EAM Class 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 EAM Class 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. (If applicable for Cleansing)
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- Not all legacy Plant Maintenance (PM) Classes need to be mapped to S/4 HANA PM Classes. If any of the successor objects is dependent on a PM Class field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the PM CLass.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||