Status	Revision in Progress
Owner	HANCOCK-ext, John
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create in S/4 HANA.

Link to MDS

https://docs.google.com/spreadsheets/d/1TgwpSzKWdvKLDVwew81ItuhuHr6ETBg8/edit?usp=sharing&ouid=107239989344593412774&rtpof=true&sd=true

Conversion Scope

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

From the current system landscape, Material data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both organizations. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

Relevancy Rules

This object is migrated after Material Basic Data, therefore only materials in scope for object "2019 - Materials Basic Data View" are in scope for this object. Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules.

List of source systems and approximate number of records

Source

Scope

Source Approx No. of Records

Target System

Target Approx

No. of Records

PF2,WP2

The Material Master Records (Additional Data) will be extracted/collected via DCT. An initial extract of the relevant data will be provided in Google Sheet format to assist business in decision making on including any relevant data from Source Systems.

Any additional data that need to be created to support the new design may be added in the DCT.

A data review and standardization will be done across all Info Records in the DCT.

700,000

S4H

300,000

Additional Information

Multi-language Requirement

Multi language is supported for Materials - PO Text. Login via a different language will show the description displayed in the logon language if the language key is maintained.

The following languages are allowed:

Core languages: EN - English, FR - French, IT - Italian and ZH - Mandarin.
Additional languages: PT - Brazilian Portuguese, DE - German, ES - Spanish, ~~TH - Thai~~ (descoped by CR0086).
Supplier languages that are possible: FR - French, EN - English, ES - Spanish, DE - German, IT - Italian, NL - Dutch, PT - Brazil Portuguese, ZH - Mandarin, PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Field Description	Data Type	Length	Requirement
MARA	MATNR	Material Number	Automatic	40	Mandatory
MAKT	SPRAS	Language	CHAR	1	Required
MAKT	MAKTX	Description	CHAR	40	Required
MARM	MEINH	Alternative Unit of Measure (ISO Format)	CHAR	3	Conditional
MARM	UMREN	Denominator for Conversion to Base Unit	DEC	5	Conditional
MARM	UMREZ	Numerator for Conversion to Base Unit	DEC	5	Conditional
MARA	MEINS	Base Unit of Measure	CHAR	3	Automatic
MARM	EAN11	GTIN	CHAR	18	Conditional
MARM	NUMTP	GTIN Category	CHAR	2	Conditional
MARM	LAENG	Length	QUAN	13,3	Conditional
MARM	BREIT	Width	QUAN	13,3	Conditional
MARM	HOEHE	Height	QUAN	13,3	Conditional
MARM	MEABM	Unit for Length/Width/Height(ISO Format)	CHAR	3	Conditional
MARM	BRGEW	Gross Weight	QUAN	13,3	Conditional
MARM	NTGEW	Net Weight (derived)	QUAN	13,3	Automatic
MARM	GEWEI	Unit of Weight (ISO Format)	CHAR	3	Conditional
MARM	VOLUM	Volume	QUAN	13,3	Conditional
MARM	VOLEH	Volume Unit (ISO Format)	CHAR	3	Conditional
T002T	SPTXT	Language Key	CHAR	2	Conditional
STXL	CLUSTD	Long Text (Text ID: GRUN)	CHAR	132	Conditional
T002T	SPTXT	Language Key	CHAR	2	Conditional
STXL	CLUSTD	Long Text (Text ID: IVER)	CHAR	132	Conditional

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Source System
2021-001	C1	UoM alignment	All material AUoMs to adhere to S4 standardization	PF2/WP2
2021-002	C1	Additional Descriptions	Material descriptions must adhere to S4 standardization so no special characters etc and must not exceed character limit	PF2/WP2
2021-003	C1	Additional Dimensions	Additional data must align with Basic Data	PF2/WP2

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

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	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

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
1	Data cleansing of legacy Material data must be completed. If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.	Business

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	SyWay S2P Data Team
2	<Add steps from Syniti Migrate here>	SyWay S2P Data Team
3	Review and Validate Error and Preload Reports	SyWay S2P Data Team
4	Generate Load Files	SyWay S2P Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
001	PF2/WG2	S_MARA	MATNR	Material Number	S/4HANA	S_MARA	MATNR	Material Number	Generate new Material number in Target System and maintain mapping in reference table
002	PF2/WG2	S_MARM	MEINH	Alternative Unit of Measure (ISO Format)	S/4HANA	S_MARM	MEINH	Alternative Unit of Measure (ISO Format)	Copy from source to target system
003	PF2/WG2	S_MARM	UMREN	Denominator for Conversion to Base Unit	S/4HANA	S_MARM	UMREN	Denominator for Conversion to Base Unit	Copy from source to target system
004	PF2/WG2	S_MARM	UMREZ	Numerator for Conversion to Base Unit	S/4HANA	S_MARM	UMREZ	Numerator for Conversion to Base Unit	Copy from source to target system
005	PF2/WG2	S_MARM	EAN11	GTIN	S/4HANA	S_MARM	EAN11	GTIN	Copy from source to target system
006	PF2/WG2	S_MARM	NUMTP	GTIN Category	S/4HANA	S_MARM	NUMTP	GTIN Category	Copy from source to target system
007	PF2/WG2	S_MARM	LAENG	Length	S/4HANA	S_MARM	LAENG	Length	Copy from source to target system
008	PF2/WG2	S_MARM	BREIT	Width	S/4HANA	S_MARM	BREIT	Width	Copy from source to target system
009	PF2/WG2	S_MARM	HOEHE	Height	S/4HANA	S_MARM	HOEHE	Height	Copy from source to target system
010	PF2/WG2	S_MARM	MEABM	Unit for Length/Width/Height(ISO Format)	S/4HANA	S_MARM	MEABM	Unit for Length/Width/Height(ISO Format)	Copy from source to target system
011	PF2/WG2	S_MARM	BRGEW	Gross Weight	S/4HANA	S_MARM	BRGEW	Gross Weight	Copy from source to target system
012	PF2/WG2	S_MARM	GEWEI	Unit of Weight (ISO Format)	S/4HANA	S_MARM	GEWEI	Unit of Weight (ISO Format)	Copy from source to target system
013	PF2/WG2	S_MARM	VOLUM	Volume	S/4HANA	S_MARM	VOLUM	Volume	Copy from source to target system
014	PF2/WG2	S_MARM	VOLEH	Volume Unit (ISO Format)	S/4HANA	S_MARM	VOLEH	Volume Unit (ISO Format)	Copy from source to target system
015	PF2/WG2	S_MARA	MAKTX	Description	S/4HANA	S_MARA	MAKTX	Description	Copy additional descriptions in multiple languages from source to target system
016	PF2/WG2	S_MARA	SPRAS	Language Key	S/4HANA	S_MARA	SPRAS	Language Key	Copy from source to target system

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
1	Ensure DCT tables completeness	SyWay S2P Data Team
2	Value Mappings are according to the latest design - <List of Value Mappings>	SyWay S2P Data Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	SyWay S2P 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.

Accuracy

Task

Action

Conversion Accuracy

SyWay S2P Data Team to verify that all fields below meet pass the checks:

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

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 Run Sheet

Item #	Step Description	Team Responsible
1	Go to <Load Tool>	SyWay S2P Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay S2P Data Team
3	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay S2P Data Team
4	Proceed with full load if steps 2 and 3 are validated	SyWay S2P Data Team
5	Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03	SyWay S2P Data Team
6	Generate post load report if step 5 is validated	SyWay S2P Data Team

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
Verify Count	SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.

Accuracy

Task	Action
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Business

Completeness

Task	Action
Verify Count	Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the Material data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Key Assumptions

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

Change log

Version	Published	Changed By
CURRENT (v. 8)	May 05, 2026 07:00	HANCOCK-ext, John
v. 85	Apr 22, 2026 11:43	HANCOCK-ext, John
v. 84	Apr 21, 2026 10:40	HANCOCK-ext, John
v. 83	Apr 21, 2026 07:51	HANCOCK-ext, John
v. 82	Apr 13, 2026 13:29	HANCOCK-ext, John
v. 81	Apr 09, 2026 07:35	HANCOCK-ext, John
v. 80	Mar 31, 2026 17:54	HANCOCK-ext, John
v. 79	Mar 17, 2026 10:55	MADHOK-ext, Jasleen
v. 78	Mar 16, 2026 21:10	MADHOK-ext, Jasleen
v. 77	Mar 03, 2026 10:22	HANCOCK-ext, John

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

From Mar 31, 2026 to May 05, 2026	Actor	Type	Activity	Version
Revision in Progress	HANCOCK-ext, John	Edit	updated the page at 5:54 pm
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:47 pm	v79
From Feb 03, 2026 to Mar 17, 2026
Edited following Approval	BUOSI-ext, Angelo , MADHOK-ext, Jasleen and HANCOCK-ext, John	Edit	multiple updates from BUOSI-ext, Angelo , MADHOK-ext, Jasleen and HANCOCK-ext, John
	HANCOCK-ext, John	Comment	commented 3:24 pm Gaurav confirmed that this is a copy from target - please check
	HANCOCK-ext, John	Edit	updated the page at 3:21 pm
	NAVANDAR-ext, Divya	Comment	commented 3:15 pm I dont find this field in MEAN structure. Is this EANTP? Please help to update.
		Comment	commented 3:02 pm If it needs to be copied, please add in transformation rules.
		Comment	commented 3:02 pm If it needs to be copied, please add in transformation rules.

Workflow history

Space shortcuts

Page tree

CNV-2021 Materials - Additional Data

Purpose

Conversion Scope

Relevancy Rules

This object is migrated after Material Basic Data, therefore only materials in scope for object "2019 - Materials Basic Data View" are in scope for this object. Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules.

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

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

Workflow history