| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Batch Classes (Class Type: 023) in S/4 HANA.
Currently, in the legacy systems, batch classes are created and assigned to materials to capture logistics and quality-related information through characteristic values. However, there may be multiple duplicate classes existing within the system, which need to be standardized across both legacy systems as part of the SyWay Design.
Batch Class 023 in SAP is designed to store and manage characteristics relevant to batches, supporting both logistics and quality requirements for effective batch management and traceability.
Conversion Scope
The scope of this document covers the approach for converting active and valid Batch Classes from Legacy Source Systems (PF2 & WP2) into S/4HANA following the Batch Class (Class Type: 023) Master Data Design Standard.
Standardizing these Batch Classes ensures a consistent structure for batch data across materials and processes.
The data from legacy system includes:
- Batch Class of Class Type: 023
- Class Validity (Valid From and Valid To), Valid Date to be considered as Data of Extraction.
- Class Groups
- Characteristics Assignment
- Status as "1" - Released
The data from legacy system excludes:
- Status as "0" - In Preparation
- Status as "2" - Locked
- No Characteristics Assignment
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Only Valid Batch Class and with Characteristics Assignment | 1816 | SyWay - ERX | TBD |
| WP2 | Only Valid Batch Class and with Characteristics Assignment | 34 | SyWay - ERX | TBD |
Additional Information
Multi-language Requirement
Not Applicable
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
KSML | DATUV | DATUV | Valid-From Date | DATS | 8 | System Default |
SWOR | KSCHL | KSCHL | Description | CHAR | 40 | Mandatory |
KLAH | STATU | KLSTATUS | Class status | CHAR | 1 | Mandatory |
KLAH | KLAGR | KLASSENGR | Class Group | CHAR | 10 | Mandatory |
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 |
KLAH | BGRKP | BGRKP | Class maintenance authorization group | CHAR | 3 | Mandatory |
KLAH | BGRKL | BGRKL | Class authorization group | CHAR | 3 | Mandatory |
KLAH | BGRSE | BGRSE | Authorization group for finding objects | CHAR | 3 | Mandatory |
KLAH | ANZUKZ | Indicator Assignments Exist | CHAR | 1 |
Data Cleansing
Data cannot be cleansed in Legacy Systems as there is already Classes assigned to materials and transaction data also exists and considering this, all class need to be standardized Globally and will be populated in Data Collection Template(DCT).
Conversion Process
The high-level process is represented by the diagram below:
Please note that the data may have to be loaded in multiple target systems (US instance, China instance and RoW).
Data Privacy and Sensitivity
Extraction
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 |
Data Collection Template (DCT)
- 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.
Class DCT Rules
zLegacyCLASS | Legacy Class number | Conditional: Legacy Class Number if comes from PF2 or WP2 Legacy Class Number: For reference only |
zLegacyKLBEZ | Legacy Description | Conditional: Legacy Class Description if comes from PF2 or WP2 Legacy Description: For reference only |
KLART | Class Type | Mandatory. Should be from the values defined below 023-Batch Class |
CLASS | Class number | Mandatory. Ensure no duplicate. |
SPRAS | Language | Mandatory. Default to "EN". English is required for all Classes. |
KLBEZ | Description | Mandatory.
|
STATU | Class status | Default to "1" |
KLAGR | Class Group | Mandatory. Must be a valid class group. |
VONDT | Valid From | 2 years prior to cutover date Hide since this is the default rule. |
BISDT | Valid To | 31.12.9999 |
zComment | Comments | Comments as per DCT Build |
Class DCT (Non-EN Language) Rules
zLegacyCLASS | Legacy Class number | Conditional: Legacy Class Number if comes from PF2 or WP2 Legacy Class Number: For reference only |
zLegacyKLBEZ | Legacy Description | Conditional: Legacy Class Description if comes from PF2 or WP2 Legacy Description: For reference only |
CLASS | Class number | Mandatory. Ensure no duplicate. |
SPRAS | Language | Mandatory. Populate for Languages not in English. Must be one of the installed language key : |
KLBEZ | Description | Mandatory.
|
zComment | Comments | Comments as per DCT Build |
Characteristic Assignment DCT Rules
CLASS | Class number | Mandatory. Class Number as per Class DCT. |
ATNAM | Characteristic Name | Mandatory. Characteristic Name as per Characteristic DCT |
zComment | Comments | Comments as per DCT Build |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow 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 |
|---|---|---|
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 |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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 |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.