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 Batches with Classification Data in S/4 HANA based on Master Data Standards DD-FUN-050 Master Data Standard_1048-Batch Master.

Batches are used extensively used in Syensqo Legacy System and used for below purposes.:

Quality Control

Each batch can be tested and its quality attributes recorded. SAP enables linking quality results to specific batches, ensuring only compliant products are shipped.

Inventory Management

Batches help manage inventory by expiration date, production date, or quality status.
Enables First-Expired-First-Out (FEFO) or First-In-First-Out (FIFO) inventory strategies.

Production Efficiency

Batches allow for detailed production planning and tracking.

Batch is activated at Material Level and it is unique.

Conversion Scope

The scope of this document covers the approach for converting active Batches & Classification Data from Legacy Source Systems into S/4HANA following the Master Data Design Standard.

The data from legacy system includes:

Materials in Scope
Materials marked as Batch in MARA/MARC
Batches in Stock (MCHB) - Inventory Exists
- MCHB-CLABS is GT 0 Or
  MCHB-CUMLM is GT 0 Or
  MCHB-CINSM is GT 0 Or
  MCHB-CEINM is GT 0 Or
  MCHB-CSPEM is GT 0
Valuation Type (MCHA-BWATR) is Blank
Plants in Scope

The data from legacy system excludes:

Batches marked for Deletion

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Batches in Stock	193K	SyWay-ERP	190K
WP2	Batches in Stock	20K	SyWay-ERP	20K

Additional Information

Multi-language Requirement

NA

Document Management

NA

Legal Requirement

NA

Special Requirements

NA

Target Design

The technical design of the target for this conversion approach.

Batch Basic Data

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MCH1	MATNR	MATNR	Material Number	CHAR	80	Mandatory
MCH1	CHARG	CHARG_D	Batch Number	CHAR	10	Mandatory
MCH1	HSDAT	HSDAT	Date of Manufacture of the batch	DATS	10	Optional
MCH1	VFDAT	VFDAT	Shelf Life Expiration Date of the batch	DATS	8	Optional
MCH1	VERAB	VERAB	Batch available from date	DATS	8	Optional
MCH1	ZUSCH	DZUSCH	Unrestricted or Restricted	CHAR	1	Optional
MCH1	QNDAT	QNDAT	Date of next inspection	DATS	8	Optional
MCH1	LIFNR	LIFNR	Supplier's Account Number	CHAR	80	Optional
MCH1	LICHA	LICHA	Supplier batch	CHAR	15	Optional
MCH1	LWEDT	LWEDT	Date of last goods receipt	DATS	8	Optional
MCH1	HERKL	HERKL	Country/Region of Origin	CHAR	3	Optional
MCH1	HERKR	HERKR	Region of Origin	CHAR	3	Optional
MCH1	MTVER	MTVER	Export/Import Group	CHAR	4	Optional
MCH1	FVDT1	FVDT1	Date for free use	DATS	8	Optional
MCH1	FVDT2	FVDT2	Date for free use	DATS	8	Optional
MCH1	FVDT3	FVDT3	Date for free use	DATS	8	Optional
MCH1	FVDT4	FVDT4	Date for free use	DATS	8	Optional
MCH1	FVDT5	FVDT5	Date for free use	DATS	8	Optional
MCH1	FVDT6	FVDT6	Date for free use	DATS	8	Optional

Classification CHAR Values

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
AUSP	OBJEK	CUOBN	Key of Object to be Classified	CHAR	10	Mandatory
AUSP	ATINN	ATINN	Internal characteristic	NUMC	10	Mandatory
AUSP	ATZHL	WZAEHL	Characteristic value counter	NUMC	3	Mandatory
AUSP	ATWRT	ATWRT	Characteristic Value	CHAR	70	Mandatory

Classification NUM Values

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
AUSP	OBJEK	CUOBN	Key of Object to be Classified	CHAR	10	Mandatory
AUSP	ATINN	ATINN	Internal characteristic	NUMC	10	Mandatory
AUSP	ATZHL	WZAEHL	Characteristic value counter	NUMC	3	Mandatory
AUSP	ATFLV	ATFLV	Internal Floating Point Value From	NUMC	16	Optional
AUSP	ATFLB	ATFLB	Internal Floating Point Value To	NUMC	16	Optional
AUSP	ATCOD	ATCOD	Code for Value Dependency	CHAR	1	Optional

Classification CURR Values

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
AUSP	OBJEK	CUOBN	Key of Object to be Classified	CHAR	10	Mandatory
AUSP	ATINN	ATINN	Internal characteristic	NUMC	10	Mandatory
AUSP	ATZHL	WZAEHL	Characteristic value counter	NUMC	3	Mandatory
AUSP	ATFLV	ATFLV	Internal Floating Point Value From	NUMC	16	Optional
AUSP	ATFLB	ATFLB	Internal Floating Point Value To	NUMC	16	Optional

Batch Data at Plant Level

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MCHA	MATNR	MATNR	Material Number	CHAR	80	Mandatory
MCHA	CHARG	CHARG_D	Batch Number	CHAR	10	Mandatory
MCHA	WERKS	WERKS	Plant	CHAR	4	Optional
MCHA	BWTAR	BWTAR	Valuation Type	CHAR	10	Optional

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
TBD

Conversion Process

The high-level process is represented by the diagram below:

1. Source = PF2/WP2:

SyWay Project > CNV-1048 Batch Master with Classification data > image-2025-10-29_17-38-58.png

2. Source = DCT

Collection will be done manually in the Data Collection Template:

Data Privacy and Sensitivity

NA

Extraction

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:
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.
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
1	Legacy System Extraction (PF2 & WP2) based on the Relevancy Rules from Table: MCH1 and AUSP ( Key to Connect is Field MCH1-CUOBJ_BM pass it & AUSP-OBJEK.	Syniti
2	Extract the Class Number and Characteristics in Material and Batch Combination. These will be used when assigning Legacy data to New Class and Characteristics	Syniti

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.

NA

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Batch Master data with exception of some fields which require transformation as mentioned in the transformation rule.

All rules specified below should be documented as a tooltip in the DC Page.

Format:

Line 1: Mandatory / Conditional

Line 2-4: Remaining text

Batch Master Basic Data

Table	Field	Description	Rules
ZlegacyMatnr	NA	Legacy Material Number	Mandatory Legacy Number to be populated
MCH1	MATNR	Material Number	Mandatory To Be Material Number
MCH1	CHARG	Batch Number	Mandatory Batch Number
MCH1	HSDAT	Date of Manufacture of the batch	Optional This date specifies the date of manufacture of the batch.
MCH1	VFDAT	Shelf Life Expiration Date of the batch	Optional Expiration Date - This field can be interpreted as the best-before date (minimum shelf life) or the shelf life expiration date (maximum shelf life).
MCH1	VERAB	Batch available from date	Optional Date as from which the batch is available.
MCH1	ZUSCH	Unrestricted or Restricted	Optional Specifies that the batch is included in restricted-use stock. If the criterion is met, enter X. If not leave empty and the status of the batch is set to unrestricted.
MCH1	QNDAT	Date of next inspection	Optional Defines the date for the next recurring inspection for the batch.
MCH1	LIFNR	Supplier number	Optional With the supplier number, information from the supplier master record. Need to get new BP Vendor from XREF
MCH1	LICHA	Supplier batch	Optional Number under which the batch is managed at the supplier's.
MCH1	LWEDT	Date of last goods receipt	Optional Date on which the last goods receipt for a purchase order or production order for this batch was posted.
MCH1	HERKL	Country/Region of Origin	Optional Key of the country/region in which the product has been produced.
MCH1	HERKR	Region of Origin	Optional You can enter a region of the country/region from which the goods originate.
MCH1	MTVER	Export/Import Group	Optional A grouping of products for export and import.
MCH1	FVDT1	Date for free use	Optional Any additional date to be captured if any.
MCH1	FVDT2	Date for free use	Optional Any additional date to be captured if any.
MCH1	FVDT3	Date for free use	Optional Any additional date to be captured if any.
MCH1	FVDT4	Date for free use	Optional Any additional date to be captured if any.
MCH1	FVDT5	Date for free use	Optional Any additional date to be captured if any.
MCH1	FVDT6	Date for free use	Optional Any additional date to be captured if any.
NA	NA	Class Number	Depending on the Characteristics values, a Class need to be assigned here.

Classification CHAR Values

Table

Field

Description

Rules

AUSP

ATINN

Internal characteristic

Mandatory

Enter here the name of the characteristic.

AUSP

ATZHL

Characteristic value counter

Mandatory

The item number is only an additional technical key to allow multiple values in the file and to prevent errors by the duplicate record check.
It is not mapped to a target field.
Please maintain a number from 001 to 999 per multiple value.

AUSP

ATWRT

Characteristic Value

Mandatory

Enter here the value of the characteristic for data type

Classification NUM Values

Table	Field	Description	Rules
AUSP	ATINN	Internal characteristic	Mandatory Enter here the name of the characteristic.
AUSP	ATZHL	Characteristic value counter	Mandatory The item number is only an additional technical key to allow multiple values in the file and to prevent errors by the duplicate record check. It is not mapped to a target field. Please maintain a number from 001 to 999 per multiple value.
AUSP	ATFLV	Internal Floating Point Value From	Optional Numerical Value from (Floating point) NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set when pressing Enter. The value is related on the Unit of measure maintained in the characteristic.
AUSP	ATFLB	Internal Floating Point Value To	Optional Numerical Value to (Floating point) (only used in intervals) NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set by the Spreadsheet, when pressing Enter. The value is related on the characteristic's Unit of measure.
AUSP	ATCOD	Code for Value Dependency	Optional Relational operators to define the intervals with the following input options: Code Operator Value1(Value From) Operator Value2(Value To) 1 EQ = 2 GE >= LT < 3 GE >= LE <= 4 GT > LT < 5 GT > LE <= 6 LT < 7 LE <= 8 GT > 9 GE >= For example: VALUE_FROM: 20 VALUE_TO: 28 VALUE_RELATION: 2 Imported value: 20 - < 28

Classification CURR Values

Table	Field	Description	Rules
AUSP	ATINN	Internal characteristic	Mandatory Enter here the name of the characteristic.
AUSP	ATZHL	Characteristic value counter	Mandatory The item number is only an additional technical key to allow multiple values in the file and to prevent errors by the duplicate record check. It is not mapped to a target field. Please maintain a number from 001 to 999 per multiple value.
AUSP	ATFLV	Internal Floating Point Value From	Optional Currency Value from (Floating point) Values can be entered with or without a decimal separator, for example 1000 or 1000.99. The value is related to the Currency code. Missing decimals are automatically set by the Spreadsheet, when pressing Enter. You can ignore them on currencies without decimals, for example JPY.
AUSP	ATFLB	Internal Floating Point Value To	Optional Currency Value To (Floating point) (used in intervals) Values can be entered with or without a decimal separator, for example 1000 or 1000.99. The value is related to the Currency code. Missing decimals are automatically set by the Spreadsheet, when pressing Enter. You can ignore them on currencies without decimals, for example JPY.

Batch Data at Plant Level

Table	Field	Description	Rules
ZlegacyMatnr	NA	Legacy Material Number	Mandatory Legacy Number to be populated
MCHA	MATNR	Material Number	Mandatory Key uniquely identifying the material.
MCHA	CHARG	Batch Number	Mandatory Key uniquely identifying the batch. The quantity or partial quantity of a certain product that has been produced according to the same recipe, and represents one homogenous, non- reproducible unit with unique specifications.
ZlegacyPlant	NA	Legacy Plant Number	Mandatory Legacy Plant to be populated
MCHA	WERKS	Plant	Mandatory Key uniquely identifying a plant. In Logistics a plant is an organizational unit for dividing an enterprise according to production, procurement, maintenance, and products planning.
MCHA	BWTAR	Valuation Type	Optional The valuation types allowed for a product are determined by the valuation category. In case of single batch valuation or split valuation please enter the number of the existing valuation type of your product. Further information can be found in the migration object documentation under mapping instructions.

Extraction Dependencies

List the steps that need to occur before extraction can commence

1

Ensure that the necessary cleansing activities in legacy sources (PF2 & WP2) are complete

Data Team / 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 Syniti ADMM 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 Syniti ADMM
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

1

Run Relevancy in Syniti tool from MCHA, MCH1 and AUSP

Syniti

Transformation Rules

Batch Basic Data

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2 & WP2	MCH1	MATNR	Material Number	SyWay-ERX	MCHA	MATNR	Material Number	Key uniquely identifying the material. Derive the Material Number via legacy to SyWay Material Number from Cross Reference Tables
2	PF2 & WP2	MCH1	CHARG	Batch Number	SyWay-ERX	MCHA	CHARG	Batch Number	Direct Mapping
3	PF2 & WP2	MCH1	HSDAT	Date of Manufacture of the batch	SyWay-ERX	MCHA	HSDAT	Date of Manufacture of the batch	Direct Mapping
4	PF2 & WP2	MCH1	VFDAT	Shelf Life Expiration Date of the batch	SyWay-ERX	MCHA	VFDAT	Shelf Life Expiration Date of the batch	Direct Mapping Depending on how it is defined, this field can be interpreted as the best-before date (minimum shelf life) or the shelf life expiration date (maximum shelf life).
5	PF2 & WP2	MCH1	VERAB	Batch available from date	SyWay-ERX	MCHA	VERAB	Batch available from date	Direct Mapping
6	PF2 & WP2	MCH1	ZUSCH	Unrestricted or Restricted	SyWay-ERX	MCHA	ZUSCH	Unrestricted or Restricted	Direct Mapping
7	PF2 & WP2	MCH1	QNDAT	Date of next inspection	SyWay-ERX	MCHA	QNDAT	Date of next inspection	Direct Mapping
8	PF2 & WP2	MCH1	LIFNR	Supplier number	SyWay-ERX	MCHA	LIFNR	Supplier number	Derive the Supplier Number via legacy to SyWay BP Number from Cross Reference Tables
9	PF2 & WP2	MCH1	LICHA	Supplier batch	SyWay-ERX	MCHA	LICHA	Supplier batch	Direct Mapping
10	PF2 & WP2	MCH1	LWEDT	Date of last goods receipt	SyWay-ERX	MCHA	LWEDT	Date of last goods receipt	Direct Mapping
11	PF2 & WP2	MCH1	HERKL	Country/Region of Origin	SyWay-ERX	MCHA	HERKL	Country/Region of Origin	Direct Mapping
12	PF2 & WP2	MCH1	HERKR	Region of Origin	SyWay-ERX	MCHA	HERKR	Region of Origin	Direct Mapping
13	PF2 & WP2	MCH1	MTVER	Export/Import Group	SyWay-ERX	MCHA	MTVER	Export/Import Group	Direct Mapping
14	PF2 & WP2	MCH1	FVDT1	Date for free use	SyWay-ERX	MCHA	FVDT1	Date for free use	Direct Mapping
15	PF2 & WP2	MCH1	FVDT2	Date for free use	SyWay-ERX	MCHA	FVDT2	Date for free use	Direct Mapping
16	PF2 & WP2	MCH1	FVDT3	Date for free use	SyWay-ERX	MCHA	FVDT3	Date for free use	Direct Mapping
17	PF2 & WP2	MCH1	FVDT4	Date for free use	SyWay-ERX	MCHA	FVDT4	Date for free use	Direct Mapping
18	PF2 & WP2	MCH1	FVDT5	Date for free use	SyWay-ERX	MCHA	FVDT5	Date for free use	Direct Mapping
19	PF2 & WP2	MCH1	FVDT6	Date for free use	SyWay-ERX	MCHA	FVDT6	Date for free use	Direct Mapping
20	PF2 & WP2		CLASSNUM	Class Number	SyWay-ERX				Note: this field to be extracted and transformed to a new Class number. If characteristics of one of the Classification CHAR Value , NUM Values or Classification CURR or Values. With this, If the class is provided the system creates all the values for characteristics with reference to a table field automatically during migration.

Classification CHAR Values

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
21	PF2 & WP2	AUSP	OBJEK	Key of Object to be Classified	SyWay-ERX	AUSP	OBJEK	Key of Object to be Classified	Key uniquely identifying the material. Derive the Material Number via legacy to SyWay Material Number from Cross Reference Tables
22	PF2 & WP2	AUSP	ATINN	Internal characteristic	SyWay-ERX	AUSP	ATINN	Internal characteristic	Need to derive from Cross reference Table for Old Characteristics Vs New Characteristics.
23	PF2 & WP2	AUSP	ATZHL	Characteristic value counter	SyWay-ERX	AUSP	ATZHL	Characteristic value counter	If a characteristic has multiple values, assign an internal counter number to each value, sequencing them from 001 to 999.
24	PF2 & WP2	AUSP	ATWRT	Characteristic Value	SyWay-ERX	AUSP	ATWRT	Characteristic Value	Direct Mapping. Need to validate the Characteristics values with allowed values in DCT-Characteristics.

Classification NUM Values

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
25	PF2 & WP2	AUSP	OBJEK	Key of Object to be Classified	SyWay-ERX	AUSP	OBJEK	Key of Object to be Classified	Key uniquely identifying the material. Derive the Material Number via legacy to SyWay Material Number from Cross Reference Tables
26	PF2 & WP2	AUSP	ATINN	Internal characteristic	SyWay-ERX	AUSP	ATINN	Internal characteristic	Need to derive from Cross reference Table for Old Characteristics Vs New Characteristics.
27	PF2 & WP2	AUSP	ATZHL	Characteristic value counter	SyWay-ERX	AUSP	ATZHL	Characteristic value counter	If a characteristic has multiple values, assign an internal counter number to each value, sequencing them from 001 to 999.
28	PF2 & WP2	AUSP	ATFLV	Internal Floating Point Value From	SyWay-ERX	AUSP	ATFLV	Internal Floating Point Value From	Direct Mapping Numerical Value from (Floating point) TIME values must have the format HHMMSS, for example 112855. DATE values must have the format YYYYMMDD, for example 20151231. Ignore the automatically set decimals. NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set. This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).
29	PF2 & WP2	AUSP	ATFLB	Internal Floating Point Value To	SyWay-ERX	AUSP	ATFLB	Internal Floating Point Value To	Numerical Value to (Floating point) (only used in intervals) TIME values must have the format HHMMSS, for example 112855. DATE values must have the format YYYYMMDD, for example 20151231. Ignore the automatically set decimals. NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set. This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).
30	PF2 & WP2	AUSP	ATCOD	Code for Value Dependency	SyWay-ERX	AUSP	ATCOD	Code for Value Dependency	Direct Mapping

Classification CURR Values

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
31	PF2 & WP2	AUSP	OBJEK	Key of Object to be Classified	SyWay-ERX	AUSP	OBJEK	Key of Object to be Classified	Key uniquely identifying the material. Derive the Material Number via legacy to SyWay Material Number from Cross Reference Tables
32	PF2 & WP2	AUSP	ATINN	Internal characteristic	SyWay-ERX	AUSP	ATINN	Internal characteristic	Need to derive from Cross reference Table for Old Characteristics Vs New Characteristics.
33	PF2 & WP2	AUSP	ATZHL	Characteristic value counter	SyWay-ERX	AUSP	ATZHL	Characteristic value counter	If a characteristic has multiple values, assign an internal counter number to each value, sequencing them from 001 to 999.
34	PF2 & WP2	AUSP	ATFLV	Internal Floating Point Value From	SyWay-ERX	AUSP	ATFLV	Internal Floating Point Value From	Direct Mapping Numerical Value from (Floating point) TIME values must have the format HHMMSS, for example 112855. DATE values must have the format YYYYMMDD, for example 20151231. Ignore the automatically set decimals. NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set. This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).
35	PF2 & WP2	AUSP	ATFLB	Internal Floating Point Value To	SyWay-ERX	AUSP	ATFLB	Internal Floating Point Value To	Numerical Value to (Floating point) (only used in intervals) TIME values must have the format HHMMSS, for example 112855. DATE values must have the format YYYYMMDD, for example 20151231. Ignore the automatically set decimals. NUM values can be entered with or without a decimal separator, for example 1000 or 1000.99. Missing Decimals are automatically set. This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).This value also dependent on Unit of Measure field assigned in Characteristics DCT (Field-CABN-MSEHI).

Batch Data at Plant Level

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
36	PF2 & WP2	MCHA	MATNR	Material Number	SyWay-ERX	MCH1	MATNR	Material Number	Key uniquely identifying the material. Derive the Material Number via legacy to SyWay Material Number from Cross Reference Tables
37	PF2 & WP2	MCHA	CHARG	Batch Number	SyWay-ERX	MCH1	CHARG	Batch Number	Direct Mapping
38	PF2 & WP2	MCHA	WERKS	Plant	SyWay-ERX	MCH1	WERKS	Plant	Derive the Plant via legacy to SyWay To-Be Plant from Cross Reference Tables
39	PF2 & WP2	MCHA	BWTAR	Valuation Type	SyWay-ERX	MCH1	BWTAR	Valuation Type	Direct Mapping

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Legacy Mapping of Class to S/4 HANA Class	zLegacyclass
Legacy Mapping of Characteristics to S/4 HANA Characteristics	zLegacycharac
Legacy Mapping of Materials to S/4 HANA Material Number	zLegacymaterial
Legacy Mapping of Supplier Number to S/4 HANA BP Number	ZLegacyBP
Legacy Mapping of Plant to S/4 HANA BP Number	ZlegacyPlant

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF2 & WP2 source tables – MCHA, MCH1 & AUSP	Syniti
4	Ensure that all required Configurations are in S/4HANA	SyWay-Functional Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Load File Count	SCM Data Team to verify that the total number of relevant records from the load file 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 relevancy rules 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

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

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the the 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.

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

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
1	CNV-1047 Batch Characteristics of Class Type: 023
2	CNV-1046 Classes Type: 023 ( Batch)

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 (ex. invalid payment terms). If it is an invalid data, business needs to review and correct the source of the data either in Legacy Systems PF2 and WP2.
Technical Setup	Interface / Connection issue within target system’s landscape	N/A – the data will be loaded directly to S/4HANA environment
Authorisation Error	<USER ID> is not authorised to access Business Partner create	Contact Basis to obtain Fire Fighter ID or fix the authorisation setup

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: MSC03N or Table: MCHA & AUSP.

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
Verify Data Accuracy	Verify that all the data in the target tables is accurate as per signed-off transformation rules
Review Post Load Error Reports	Verify that all necessary post load error reports have been validated, and that errors have been addressed.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records are in the target system

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 Master and Classification data is in scope based on data design and any exception requested by business.

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Batch Basic Data

Classification CHAR Values

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Classification CHAR Values

Extraction Dependencies

Transformation

Transformation Run Sheet

Batch Basic Data

Classification CHAR Values

Classification NUM Values

Classification CURR Values

Batch Data at Plant Level

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