Status	Revision in Progress
Owner	RAYUDU-ext, Narasimha Kumar
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

List of source systems and approximate number of records

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.

Batch Class

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KLAH	KLART	KLASSENART	Class Type	CHAR	3	Mandatory
KLAH	CLASS	KLASSE_D	Class Number	CHAR	18	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	Conditional
KLAH	PRAUS	GLKLAFZ	Same Classification/ Do Not Check	CHAR	1	Mandatory
KSML	IMERK	ATINN	Internal characteristic	NUMC	10	Mandatory

Characteristics Assignments

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KLAH	CLASS	KLASSE_D	Class Number	CHAR	18	Mandatory
KSML	IMERK	ATINN	Internal characteristic	NUMC	10	Mandatory

Batch Class Descriptions and 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

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.

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

Not Applicable

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

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

The top-level unit of control for classes.
Each class must be assigned to exactly one class type. There is no connection between the individual class types.
You maintain class types in Customizing for Classification.

Possible entries for class type:
001 = Material Class
017 = Document Management
023 = Batch Class
200 = Material (Configurable Objects) Class
300 = Variants Class
052 = Customer-material info record

Mandatory

Fixed Value - 023

CLASS

Class Number

Number used to uniquely identify a change master record.

Need to follow the naming Convention which will distinguish across different functions

For Eg:

Function - XX (QM, SC, Etc.)

Business Unit - XXX (NOV -Nova Care SPL - Specialty Polymers)

Product Type - XXXX (POLY, RESI Etc., )

Sequential Number - XXX (001, 002...999)

QM-NOV-POLY-001

Mandatory

Class Name - Need to follow the naming Convention which will distinguish across different functions (Eg; Vendor Classification or EAM Characteristics)

KSCHL

Description

For each class, the first record of each language will be processed as description, and the other records of this language will be processed as keywords.
For example, if you input three records of language 'EN' in a class number, then the first record will be processed as description, the second and the third one will be processed as keywords.

Descriptions need to follow a standard naming convention across all characteristics.
Use similar formats for similar types of characteristics
Avoid abbreviations unless they are commonly accepted by Syensqo

STATU

Class status

This key determines:
•whether a class can be maintained
•whether objects can be allocated to a class
•whether the class can be used for selecting objects
Possible values are dependent on the class type:
'0' = In preparation
'1' = Released
'2' = Locked
If it is not filled, the released value '1' will be set automatically

Mandatory

Fixed Value as 1 - Released

KLAGR

Class Group

The class group is used to group together related classes.

The class group is used for finding classes quickly via a match code.

Conditional

Need to select the appropriate characteristics group for the batch characteristics. As these are configurable values, these are TBD until Functional defines it.

VONDT

Valid-From Date

The class validity starts from this date. If it is not set the current system date will be used as valid-from date.

Mandatory

System Default as Current Date

When the load file is generated, Current Date should be captured.

BISDT

Valid-to date

The date until the class can be used. If it is not set, HIGH-Date (31.12.9999) will be used as valid-to date.

Mandatory

System Default as 31.12,2999

PRAUS

Same Classification/ Do Not Check

This field is to define the system check for identical characteristic values.
An activated check, checks if the class with the same values was already assigned to different objects.
Possible entries for the field 'Check for Same Classification':
▪ empty(no entry) - No Check for Same Classification
▪ 'W' - Check for Same Classification with Warning
▪ 'E' - Check for Same Classification with Error Message

Optional

3 Values exists

Do not check (System Default) - System defaults to this option
Warning Message
Check with Error

Characteristic Assignment DCT Rules

CLASS

Class number

Number used to uniquely identify a change master record.

Need to follow the naming Convention which will distinguish across different functions

For Eg:

Function - XX (QM, SC, Etc.)

Business Unit - XXX (NOV -Nova Care SPL - Specialty Polymers)

Product Type - XXXX (POLY, RESI Etc., )

Sequential Number - XXX (001, 002...999)

QM-NOV-POLY-001

Mandatory.

Class Number as per Class DCT.

IMERK

Internal characteristic

Name that uniquely identifies a characteristic.

Mandatory.

Characteristic Name as per Characteristic DCT. Relevant Characteristics need to selected by Business.

Class Descriptions Keyword Data Construction Rules

CLASS

Class number

Number used to uniquely identify a change master record.

Need to follow the naming Convention which will distinguish across different functions

For Eg:

Function - XX (QM, SC, Etc.)

Business Unit - XXX (NOV -Nova Care SPL - Specialty Polymers)

Product Type - XXXX (POLY, RESI Etc., )

Sequential Number - XXX (001, 002...999)

QM-NOV-POLY-001

Mandatory.

Class Number as per Class DCT.

KLART

Class Type

The top-level unit of control for classes.
Each class must be assigned to exactly one class type. There is no connection between the individual class types.
You maintain class types in Customizing for Classification.

Possible entries for class type:
001 = Material Class
017 = Document Management
023 = Batch Class
200 = Material (Configurable Objects) Class
300 = Variants Class
052 = Customer-material info record

Mandatory.

Should be from the values defined below

023-Batch Class

SPRAS

Language Key

Please enter here the language of your description (ISO format).

EN - English

FR - French

IT - Italian

ZH - Mandarin

PT - Portuguese

DE - German

ES - Spanish

XX - Brazilian Portuguese

KSCHL

Keyword

For each class, the first record of each language will be processed as description, and the other records of this language will be processed as keywords.
For example, if you input three records of language 'EN' in a class number, then the first record will be processed as description, the second and the third one will be processed as keywords.

Mandatory.

Keywords should be on the Title Case.

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Extract data from source systems PF2 and WP2	Syniti
2	Populate in a report in a Downloadable format	Syniti
3	Data is populated in the DCT or uploaded from downloaded Excel template	Business/Data Owners
4	If the data is uploaded to DCT in bulk via excel template, any upload errors need to be reviewed and corrected	Business/Data Owners
5	The data which has passed validation checks in DCT will be used for transformation/further processing	Business/Data Owners

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.
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
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.	SCM Data Team
2	In dspMigrate, select the wave – S4/HANA – P2F-SCM	Syniti
3	Go to Process Area Launch and Process the Object – Batch 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

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	Direct Mapping
2	PF2&WP2	KLAH	CLASS	Class Number	SyWay - ERX	KLAH	CLASS	Class Number	Direct Mapping
3	PF2&WP2	SWOR	KSCHL	Description	SyWay - ERX	SWOR	KSCHL	Description	Direct Mapping
4	PF2&WP2	KLAH	STATU	Class status	SyWay - ERX	KLAH	STATU	Class status	Direct Mapping
5	PF2&WP2	KLAH	KLAGR	Class Group	SyWay - ERX	KLAH	KLAGR	Class Group	Direct Mapping
6	PF2&WP2	KLAH	VONDT	Valid-From Date	SyWay - ERX	KLAH	VONDT	Valid-From Date	Direct Mapping
7	PF2&WP2	KLAH	BISDT	Valid-to date	SyWay - ERX	KLAH	BISDT	Valid-to date	Direct Mapping
8	PF2&WP2	KLAH	PRAUS	Same Classification/ Do Not Check	SyWay - ERX	KLAH	PRAUS	Same Classification/ Do Not Check	Direct Mapping
12	PF2&WP2	KSML	IMERK	Internal characteristic	SyWay - ERX	KSML	IMERK	Internal characteristic	Direct Mapping

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:

Mandatory Fields
Field and Value Mapping Correctness
Null 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

1.

KLAGR - Class Group. Table/View: V_CLG (Class Groups)

SAP Customizing Implementation Guide -> Cross-Application Components -> Classification System -> Classes -> Define Class Groups

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.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 22)	Nov 18, 2025 18:07	RAYUDU-ext, Narasimha Kumar
v. 22	Nov 18, 2025 17:59	RAYUDU-ext, Narasimha Kumar	Tooltip Updated.
v. 21	Oct 15, 2025 13:58	RAYUDU-ext, Narasimha Kumar
v. 20	Oct 15, 2025 13:50	RAYUDU-ext, Narasimha Kumar	Language & Chars Assignment
v. 19	Oct 08, 2025 14:18	RAYUDU-ext, Narasimha Kumar	Added Config Item dependencies
v. 18	Oct 02, 2025 14:56	RAYUDU-ext, Narasimha Kumar	Updated Peer Review comments
v. 17	Oct 02, 2025 00:35	RAYUDU-ext, Narasimha Kumar
v. 16	Oct 01, 2025 15:10	RAYUDU-ext, Narasimha Kumar
v. 15	Oct 01, 2025 13:27	RAYUDU-ext, Narasimha Kumar
v. 14	Oct 01, 2025 11:31	RAYUDU-ext, Narasimha Kumar

Go to Page History

Mar 18, 2026	Actor	Type	Activity	Version
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:41 pm	v23
Nov 18, 2025
Edited following Approval	RAYUDU-ext, Narasimha Kumar	Edit	updated the page at 5:59 pm
	RAYUDU-ext, Narasimha Kumar	State	changed state to Edited following Approval at 4:59 pm	v22
Nov 07, 2025
Approved	MCARDLE-ext, Edward	State	changed state to Approved at 7:31 pm	v21
Lead Approval	MCARDLE-ext, Edward	State	changed expiry date to '14 Nov, 2025 07:31 pm' at 7:31 pm
		State	gave Minor change approval at 7:31 pm
		State	changed state to Lead Approval at 7:31 pm	v21

Workflow history

Space shortcuts

Page tree

CNV-1046 Classes Type: 023 ( Batch)

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Batch Class

Batch Class Descriptions and Keywords

Data Cleansing

Conversion Process

Extraction

Selection Screen

Data Collection Template (DCT)

Batch Class DCT Rules

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