| Status | Revision in Progress |
|---|---|
| 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 |
KLAH | VONDT | VONDAT | Valid From | DATS | 8 | System Default |
KLAH | BISDT | BISDAT | Valid To | 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 | Optional |
KLAH | PRAUS | GLKLAFZ | Same Classification/ Do Not Check | CHAR | 1 | Mandatory |
KSML | IMERK | ATINN | Internal characteristic | NUMC | 10 | Mandatory |
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
KLART | Class Type | Mandatory. Should be from the values defined below 023-Batch Class |
CLASS | Class number | Mandatory. Ensure no duplicate. |
| VONDT | Valid From | Default to Current Date |
| BISDAT | Valid To | Default to 31.12.2999 |
KSCHL | Description | Mandatory.
|
STATU | Class status | Default to "1" |
KLAGR | Class Group | Optional. Must be a valid class group. |
PRAUS | Same Classification | Optional 3 Values exists
|
Characteristic Assignment DCT Rules
CLASS | Class number | Mandatory. Class Number as per Class DCT. |
IMERK | Internal characteristic | Mandatory. Characteristic Name as per Characteristic DCT |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| NA | ||||
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.Batch Class DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
KLART | Class Type | Direct Mapping |
KSCHL | Description | Direct Mapping |
STATU | Class status | Direct Mapping |
KLAGR | Class Group | Direct Mapping |
VONDT | Valid-From Date | Direct Mapping |
BISDT | Valid-to date | Direct Mapping |
PRAUS | Same Classification/ Do Not Check | Direct Mapping |
| IMERK | Internal characteristic | Direct Mapping |
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 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2&WP2 | KLAH | KLART | Class Type | SyWay - ERX | KLAH | KLART | Class Type | |
| 2 | PF2&WP2 | KSML | DATUV | Valid-From Date | SyWay - ERX | KSML | DATUV | Valid-From Date | |
| 3 | PF2&WP2 | SWOR | KSCHL | Description | SyWay - ERX | SWOR | KSCHL | Description | |
| 4 | PF2&WP2 | KLAH | STATU | Class status | SyWay - ERX | KLAH | STATU | Class status | |
| 5 | PF2&WP2 | KLAH | KLAGR | Class Group | SyWay - ERX | KLAH | KLAGR | Class Group | |
| 6 | PF2&WP2 | KLAH | VONDT | Valid-From Date | SyWay - ERX | KLAH | VONDT | Valid-From Date | |
| 7 | PF2&WP2 | KLAH | BISDT | Valid-to date | SyWay - ERX | KLAH | BISDT | Valid-to date | |
| 8 | PF2&WP2 | KLAH | PRAUS | Same Classification/ Do Not Check | SyWay - ERX | KLAH | PRAUS | Same Classification/ Do Not Check | |
| 9 | PF2&WP2 | KLAH | BGRKP | Class maintenance authorization group | SyWay - ERX | KLAH | BGRKP | Class maintenance authorization group | |
| 10 | PF2&WP2 | KLAH | BGRKL | Class authorization group | SyWay - ERX | KLAH | BGRKL | Class authorization group | |
| 11 | PF2&WP2 | KLAH | BGRSE | Authorization group for finding objects | SyWay - ERX | KLAH | BGRSE | Authorization group for finding objects | |
| 12 | PF2&WP2 | KLAH | ANZUKZ | Indicator Assignments Exist | SyWay - ERX | KLAH | ANZUKZ | Indicator Assignments Exist |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| KSML | Characteristics of a Class |
| KLAH | Class Header Data |
| SWOR | Classification System: Keywords |
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 DCT & Load File Count | SCM 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. |
Verify Consent | Verify the appropriate consents for the records have been obtained by the business/Data Owners and properly recorded |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SCM Data team to verify that all the data in the load table/file is accurate as per signed-off DCT contents and transformation rules with below 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. |
Verify Consent | Verify that the appropriate consents for the records have been obtained by the business and properly recorded |
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 approach: Migration Cockpit using Staging Tables
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure Pre-load sign-offs are obtained. | SCM Data team |
2 | Go to the load tool and select the correct load Program. | SCM Data team |
3 | Proceed with Data load. | SCM Data team |
4 | Validate few records loaded by accessing standard transactions. | SCM Data team |
5 | Generate the post load reports in the tool. | SCM Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | SCM Data team |
7 | Resolve defects by re-upload and re-generate post load reports if necessary. | SCM 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. | SCM Data team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| NA | NA |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| NA | NA |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Configuration | <configuration> is not valid/missing | If it is a missing configuration item, then engage Functional team to expedite and fix the error in the system. |
Invalid Data | <parameter> is not valid. | The parameter entry needs to be reviewed If it is an invalid data, business needs to review and correct the source of the data either in PE1 or if it’s mapped in DCT. |
Technical Setup | Interface / Connection issue within target system’s landscape | N/A – the data will be loaded directly to S/4HANA environment |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Verify the count | Verify that the record count in the post-load file is the same as the record count based on the relevancy (including any deduplication) results |
Accuracy
| Task | Action |
|---|---|
Data Accuracy | SCM Data team to verify that all the data in the post load table/file is accurate as per signed-off transformation rules and DCT contents |
Error Reports | Verify that all necessary error reports have been validated, and that errors have been addressed. |
Data Consistency | Verify that the data loaded is correctly reflected in T-Code: CL01or Table: KSML/KLAH. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Verify that the record count in the post load file is the same as the record count based on the relevancy (including deduplication) results |
Validate Loaded Data | Validate, as per the load files signed-off, that all records were created |
Accuracy
| Task | Action |
|---|---|
Data Accuracy | Verify that all the data in the S/4HANA table is accurate as per signed-off DCT contents and transformation rules For mock loads, the post load data validation will be as per scrambled data, thus data accuracy is not to be checked against DCT which holds the actual data. Post-load data to be validated against the pre-load report (scrambled data). |
Verify Relationships | Verify that each Vendor have been assigned to the appropriate Business Partner correctly |
Key Assumptions
- The Master Data Standards document is a evolving document where value mappings/validation checks are still being finalized as we are currently in the detailed phase as of September 2025.
- Batch Characteristics is in scope based on data design and any exception requested by business.