Status
Owner	CASTRO MONCAYO-ext, Jose Luis
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

T

The purpose of this document is to define the conversion approach to create 2005 - Material Master MRP views
in S/4 HANA.

Material Master - MRP Views are now used to make some of the Planning activities in both systems (PF2 & WP2). Most of the materials used in the planning process have these views updated, as they contain relevant information about the planning process. The aim is to get the conversion into S4 HANA in a standard way, so it can be used in the new planning processes already defined by the functional team and validated with the business.

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.

The data from legacy system may include:

1. Uncleansed data or duplicated records
   
   

The data from legacy system excludes:

1. All materials flagged for deletion
2. Any blocked or obsolete materials
3. Any inactive materials that are out of scope

Conversion Scope

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

The data from legacy system includes:

1. Relevancy Criteria 1
2. Relevancy Criteria 2
3. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

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
MARC	AUSME	AUSME	Unit of issue	UNIT	3	C
MARC	FRTME	FRTME	Production unit	UNIT	3	C
MARC	MMSTA	MMSTA	Material Status	CHAR	2	C
MARC	MMSTD	MMSTD	Valid From	DATS	8	C
MARC	FEVOR	FEVOR	Prodn Supervisor	CHAR	3	R List of customizing values and mapping with AS IS will be build as per
MARC	LGPRO	LGPRO	Storage Location	CHAR	4	R List of customizing values and mapping with AS IS will be build as per
MARC	SFCPF	CO_PRODPRF	Prod. Sched. Profile	CHAR	6	R : Mapping with As Is values and to be values to be provided
MARC	MATGR	MATNRGROUP	Mat. Grouping	CHAR	20	NU
MARC	SERNP	SERAIL	Serial Number Profile	CHAR	4	NU
MARA	SERLV	SERLV	SerLevel	CHAR	1	NU
MARC	OCMPF	OCM_GPROFILE	Overall profile	CHAR	6	NU
MARC	KZKRI	KZKRI	Indicator: Critical part	CHAR	1	C
MARC	KZECH	KZECH	Batch entry	CHAR	1	C
MARA	XCHPF	XCHPF	Batch Management Requirement Indicator	CHAR	1	C
MARC	INSMK	INSMK	Post to Inspection Stock	CHAR	1	C
MARA	XGCHP	XGCHP	Approved Batch Record Required	CHAR	1	NU
MARC	XCHPF	XCHPF	Batch Management Requirement Indicator for Plant	CHAR	1	C
MARC	UNETO	UNETO	Underdel. Tol.	DEC	3	C
MARC	UEETO	UEETO	Overdeliv. Tol.	DEC	3	C
MARC	UEETK	UEETK	Indicator: Unlimited Overdelivery Allowed	CHAR	1	C
MARC	RUEZT	RUEZT	Setup time	DEC	5	C
MARC	TRANZ	TRANZ	Interoperation	DEC	5	C
MARC	DZEIT	DZEIT	In-house production time	DEC	3	C
MARC	BEARZ	BEARZ	Processing time	DEC	5	C
MARC	BASMG	BASMG	Base quantity	QUAN	13	C

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
01	CNV-01	Material is not active or is deleted	Materials that are not used for more than 3 years, no subject to migrate	Only active materials during the last 3 years will be migrated	PF2/WP2
02	CNV-02	Material is not an "E" Procurement type	Materials with "E" Procurement needs to have Work Scheduling View	Materials with no "E" procurement are out of scope	PF2/WP2
03	CNV-03	Production Scheduling Profile is missing	Materials with WS View in Material Master must have Production Scheduling  Profile	Materials with no Prod. Sched Profile needs to be updated by the business	PF2/WP2
04	CNV-04	Production Supervisor is Missing	Materials with WS view and No Prod Supervisor filled, needs to be checked by the Data Owner	Prod Supervisor has been updated for all relevant materials	PF2/WP2
05	CNV-05	Production Storage Location is missing	Materials with WS view need to have Production Storage location defined	Prod Storage Location needs to be updated for all relevant materials	PF2/WP2
06	CNV-06

Conversion Process

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

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
1	Extract from MARC all Material/Plant relevant as Procurement Type E, and be updated as "A" means that the Work Scheduling view is updated	Sinity / Data Team
2	Extract data from source system based on relevancy rule	SyWay Data Team
3	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team
4	Sinity will extract data and convert it into SQL data base ad share with the team	Sinity team

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
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
1	PF2/WQ2	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

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Material Type	Mapping of legacy Material Types to target system value
Material Group	Mapping of legacy Material Groups to target system value
Product Hierarchy	Mapping of legacy Product Hierarchies to target system value

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

The following pre-load validations will be performed by the 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

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

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

Workflow history