Status	Approved
Owner	BUOSI-ext, Angelo HANCOCK-ext, John CLARKE-ext, Steve
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to upload Materials - Class Type 001 into S/4 HANA as part of the Material Data Migration.

Link to MDS: DD-FUN-050 Master Data Standard_2017-Material master - Class Type 001

Conversion Scope

The scope of this document covers the approach for converting active Class data linked to Class Type 001 from Legacy Source Systems into S/4HANA following the Material Master Data Design Standard.

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

Scope is Classes that fall under CLASS TYPE 001 and are linked to Material records that have been identified as part of Basic Data.

Service Master records that will become Materials in the target are out of scope. See the mail from Simran. Service Master Data Used in 2017 CLASS TYPE 001 in S4H.eml

Gross values not taking into account if linked to relevant Materials

WP2: 22,838

PF2: 5,167

S4H

28,000

Jira Task to track the Classes that will be added to CLASS TYPE 001: PDM-770 - Getting issue details... STATUS

Configuration Document containing the above classes: <To Be Add>

Predecessor Objects

Material (Characteristics of CLASS TYPE -001) → Material - Class Type 001.

Additional Information

Multi-language Requirement

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

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

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

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

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

Change log

Version	Published	Changed By	Comment
CURRENT (v. 5)	Dec 01, 2025 17:36	CLARKE-ext, Steve
v. 46	Dec 01, 2025 16:35	CLARKE-ext, Steve
v. 45	Dec 01, 2025 16:15	CLARKE-ext, Steve
v. 44	Dec 01, 2025 16:01	CLARKE-ext, Steve
v. 43	Dec 01, 2025 15:53	CLARKE-ext, Steve
v. 42	Dec 01, 2025 15:51	CLARKE-ext, Steve	Added DCT and Transform Rules for KSML
v. 41	Nov 17, 2025 10:32	CLARKE-ext, Steve
v. 40	Nov 17, 2025 10:11	CLARKE-ext, Steve
v. 39	Nov 13, 2025 13:59	CLARKE-ext, Steve
v. 38	Oct 28, 2025 15:35	CLARKE-ext, Steve

Go to Page History

Workflow history

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

Dec 03, 2025	Actor	Type	Activity	Version
Approved	JAIN-ext, Gaurav	State	changed state to Approved at 8:15 am	v47
Edited following Approval	JAIN-ext, Gaurav	State	gave Minor change approval at 8:15 am
Dec 01, 2025
	CLARKE-ext, Steve	Comment	commented 5:45 pm There is no link. I asked Simran about this for 2018. She responded: there is no config document for this as this is master data
		Comment	commented 5:42 pm We are not using any mappings
		Comment	commented 5:41 pm This is if there are no descriptions in the 7 allowed languages.
		Edit	updated the page at 5:36 pm
		Comment	commented 5:29 pm This is already documented above in Multi-language Requirement. I will update it to indicate that it is now mandatory that a description is required for each core and additional language. I have updated the Transformation Rules for the Descriptions to include: "There must be a description for each of the Core and Additional languages. If a language is missing take if from English." Syniti are aware that SPRAS is a key.
	MADHOK-ext, Jasleen	Comment	commented 4:50 pm CLARKE-ext, Steve Configuration table link is required.
		Comment	commented 4:49 pm CLARKE-ext, Steve What Transformation tables are required?
		Comment	commented 4:44 pm CLARKE-ext, Steve what is this rule?
		Comment	commented 4:44 pm CLARKE-ext, Steve Please add 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.
	CLARKE-ext, Steve	Edit	updated the page at 3:51 pm

Workflow history

Space shortcuts

Page tree

CNV-2017 Materials - Class Type 001

Purpose

Conversion Scope

Predecessor Objects

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