Status
Owner	CASTRO MONCAYO-ext, Jose Luis
Stakeholders	GERVAIS, Pascal NICASTRI-ext, Michele

Purpose

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

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

Conversion Scope

Material Master - PPDS 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. As this is a new view a complete new DCT will be needed, as NO migration data on Scope.

We need to create a NEW Layout to fill in for the new data per material / Plant combination

The data from legacy system may include:

1. As per materials, the rule for this view will follow the rules for the CNV-2019 CNV-2019 Materials - Basic Data View 
   
   
2. Additional to this, the following criteria needs to be followed to create the view: All Direct materials as MRP type X0, will need to have PPDS view and the data to complete the design process in Syensqo.
3. All ZMAT materials and Z700 will be called in S4HANA ZDIR. These material types will be the ones to have PPDS View. 

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

The data from legacy system includes:

1. PF2 (ROW & CN)
2. WP2 (ROW & CN)

The data from legacy system excludes:

1. This Conversion Specification does not include the WPX system (CUI Objects).
   

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	All planning materials	15,000	S4 HANA	TBD
WP2	All Planning materials	30,000	S4 HANA	TBD
	N/A

Additional Information

Multi-language Requirement

System Multi-language standard definition

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

N/A

Target Design

Fields in Scope for PPDS view

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	R
T001W	WERKS	WERKS	Plant ID	CHAR	4	R
MARA	MEINS	MEINS	Unit of measure in which stock of the material is managed.	UNIT	3	R
MARA	PPSKZ	PPSKZ	Indicator for Advanced Planning	CHAR	1	C
MARC	SCM_PRIO	/SAPAPO/PRIO	Priority of Product	INT1	3	C
MARC	SCM_RRP_TYPE	/SAPAPO/PPS_PLANNING_TYPE	PP Planning Procedure	CHAR	1	C
MARC	SCM_RRP_SEL_GROUP	/SAPAPO/RRP_SEL_GROUP	Planning Group	CHAR	2	C
MARC	SCM_PEG_FUTURE_ALERT	/SAPAPO/DM_PEGGING_FUTUR_ALERT	Alert threshold for early receipts	DEC	11	C
MARC	SCM_PEG_PAST_ALERT	/SAPAPO/DM_PEGGING_PAST_ALERT	Alert Threshold for Lateness	DEC	11	C
MARC	SCM_GET_ALERTS	/SAPAPO/GET_ALERTS_FOR_PROD	Product Alerts	CHAR	1	C

Data Cleansing

No Data to clean as this is a new view in the Materials

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
		N/A

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

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 forCNV-2006 Materials PPDS view data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule
MATNR	Material Number
WERKS	Plant ID
MEINS	Unit of measure in which stock of the material is managed.
PPSKZ	Indicator for Advanced Planning
SCM_PRIO	Priority of Product
SCM_RRP_TYPE	PP Planning Procedure
SCM_RRP_SEL_GROUP	Planning Group
SCM_PEG_FUTURE_ALERT	Alert threshold for early receipts
SCM_PEG_PAST_ALERT	Alert Threshold for Lateness
SCM_GET_ALERTS	Product Alerts

Extraction Dependencies

No extraction of DATA as this is a new view in the Material Master

Item #	Step Description	Team Responsible
	N/A

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	Prepare Load files with the necessary rules and including the value mapping.	Sinity / MFG Team
2	Create the DCT file according to the Loading template in Sinity tool, else with the "Migrate your Data" tool in S4/HANA	Sinity / MFG Team
3	Validate the loading with the Business as per GBU reports	MFG Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
CNV-1	N/A	MARA	MATNR	Material Number	S4 HANA	MARA	MATNR	Material Number	COPY - MARA-MATNR
CNV-2	N/A	T001W	WERKS	Plant ID	S4 HANA	T001W	WERKS	Plant ID	COPY T001W-WERKS
CNV-3	N/A	MARA	MEINS	Unit of measure in which stock of the material is managed.	S4 HANA	MARA	MEINS	Unit of measure in which stock of the material is managed.	COPY MARA-MEINS
CNV-4	N/A	MARA	PPSKZ	Indicator for Advanced Planning	S4 HANA	MARA	PPSKZ	Indicator for Advanced Planning	DCT
CNV-5	N/A	MARC	SCM_PRIO	Priority of Product	S4 HANA	MARC	SCM_PRIO	Priority of Product	DCT
CNV-6	N/A	MARC	SCM_RRP_TYPE	PP Planning Procedure	S4 HANA	MARC	SCM_RRP_TYPE	PP Planning Procedure	DCT
CNV-7	N/A	MARC	SCM_RRP_SEL_GROUP	Planning Group	S4 HANA	MARC	SCM_RRP_SEL_GROUP	Planning Group	DCT
CNV-8	N/A	MARC	SCM_PEG_FUTURE_ALERT	Alert threshold for early receipts	S4 HANA	MARC	SCM_PEG_FUTURE_ALERT	Alert threshold for early receipts	DCT
CNV-9	N/A	MARC	SCM_PEG_PAST_ALERT	Alert Threshold for Lateness	S4 HANA	MARC	SCM_PEG_PAST_ALERT	Alert Threshold for Lateness	DCT
CNV-10	N/A	MARC	SCM_GET_ALERTS	Product Alerts	S4 HANA	MARC	SCM_GET_ALERTS	Product Alerts	DCT

Transformation Mapping

N/A

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	DCT is built and tested	Sinity/Data Team
2	Data Transformation load files need to be validated by the business at GBU level	Business Data Owners
3	All Value mapping tables needs to be finished	Sinity/MFG Data Team
4	All Data dependencies has to be finished. Any delay can bring delays on this	All

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Business Validates the load file	Send the Load file to the Business Representatives for all plants, so the can validate the data
Mock 1 test needs to happen before	1st Mock load (manual) can occur first and before the load can occur
Count before and after	Review the items as count before the load in the Transformation files and check it after

Accuracy

Task	Action
Record Errors	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
To check Data Accuracy checking count of records to load and loaded	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.
Count before and after	Review the items as count before the load in the Transformation files and check it after

Accuracy

Task	Action
Data owners to grant that the records in the load files are okay and according with the rules and mappings	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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 file and pick 5 data registers, load manually without any tool. See what happens. If all okay, proceed with the next step.	MFG Data Team
2	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	MFG Data Team
3	Proceed with the full load if steps one and two were succeed.	MFG Data Team
4	Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03	MFG Data Team
	Generate post load report if step 5 is validated	MFG 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
1- Pre Cutover	Plant Planning Parameters
2- Pre Cutover	Plant & Storage location parameters
3 - Pre Cutover	Material Types configuration
4 - Pre Cutover	Valuation Class Configuration
5 - Pre Cutover	MRP Groups Configuration
6- Pre cutover	MRP Controllers Configuration
7- Pre Cutover	Availability check Configuration
8- Pre Cutover	Purchasing Groups Configuration
9- Pre Cutover	All configurations and Setup of PPDS embedded solution

Conversion Objects

Object #	Preceding Object Conversion Approach
2019	Materials - Basic View
2020	Materials - Purchasing View
2010	Materials - General Plant Data / S. Location Data

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
Check Data Records count	Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count)

Accuracy

Task	Action
Check Data loading tool log	Check whether after the loading process, any logs from the tool, to verify them and take actions

Business

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

Completeness

Task	Action
Check Data load register count	Download Post Load Reports from The Tool 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
Check Error log from the loading tool	Check whether after the loading process, any logs from the tool, to verify them and take actions

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