Status
Owner	RAYUDU-ext, Narasimha Kumar
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

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:

1. Batch Class of Class Type: 023
2. Class Validity (Valid From and Valid To), Valid Date to be considered as Data of Extraction.
3. Class Groups
4. Characteristics Assignment 
5. Status as "1" - Released

The data from legacy system excludes:

1. Status as "0" - In Preparation
2. Status as "2" - Locked
3. 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

With Functional input, document the technical design of the target fields that are in the scope of this document.

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:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. 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

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

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.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

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 Syniti Migrate to make the data Target ready:

1. 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 Syniti Migrate
2. 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

Use the exact name and reference this section in the “Transformation rules” above

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

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

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.

Change log