Status
Owner	HANCOCK-ext, John
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 Materials - Purchasing View in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting active Materials - Purchasing View 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

1. All materials created in the previous 6 months will be included unless flagged for deletion
2. These include Material Types ZUNB, ZBOM, ZPRC regardless of activity (unless flagged for deletion)
3. We will only include materials that are extended to the following (excluding ZPRC material type as these do not require plant extension):
   1. Company Codes in scope
   2. Plants in scope
   3. Purchasing Orgs in scope
   4. Sales Orgs in scope
4. Include only Material Types in scope
5. We will include for migration all materials that have activity over the previous 3 years, to include:
   1. For procurement data use EKKO/EKPO tables
   2. For sales data use VBAK/VBAP tables
   3. For production data use AFKO/AFPO tables
6. We will include for migration all materials that have open documents including the following:
   1. Open PO
   2. Open contracts
   3. Open STO
   4. Open SO
   5. Open WO
7. Have current stock - refer to MARD table
8. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
9. Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
   1. Open PO
   2. Open contracts
   3. Open STO
   4. Open SO
   5. Open WO
10. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
11. Materials with the word 'OBSOLETE' or 'DELETED' contained within the Short Description will be excluded. Also excluded are Materials where Short Description contains '**OBS', '**OBS**', '**OBS***', '*OBS*', '*OBS**', '***OBS***'

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 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	204,000

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

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
S_MARA	MATNR		Material Number	Automatic		Mandatory
S_MARC	WERKS		Plant	Configured		Mandatory
S_MARA	MEINS		Base Unit of Measure (ISO Format)	Configured		Mandatory
S_MARA	BSTME		Order Unit of Measure (ISO Format)	Configured		Mandatory
S_MARA	VABME		State of Variable Purchase Order Unit	Configured		Optional
S_MARC	EKGRP		Purchasing Group	Configured		Mandatory
S_MARA	MATKL		Material Group	Configured		Mandatory
S_MARC	MMSTA		Plant-Specific Material Status	Configured		Optional
S_MARC	MMSTD		Valid From Date for Status	Date		Optional
S_MARC	TAXIM		Tax Indicator	Configured		Optional
S_MARA	NRFHG		Material Disc In Kd	Configured		Optional
S_MARC	MFRGR		Material Freight Grp	Configured		Optional
S_MARC	KAUTB		Automatic Purchase Oder Allowed	Text	1	Optional
S_MARC	XCHPF		Batch Management Req. Indicator	Text	1	Optional
S_MARA	EKWSL		Purchasing Value Key	Configured		Mandatory
S_MARC	WEBAZ		GR Processing Time	Text	2	Mandatory
S_MARA	MFRPN		Manufacturer Part Number	Text	80	Optional
S_MARA	MFRNR		Manufacturer Number	Configured		Optional
S_MARA	MPROF		Manufacturer Part Profile	Configured		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
2020-001	C1	Purchasing Group	Confirm all procured materials have Purchasing Data in place and confirm Purchasing Group mapping to S4 target value		PF2/WP2
2020-002	C1	PIR alignment	Check that procured materials have PIR in place		PF2/WP2
2020-003	C1	Purchasing Value Key	All material Purchasing data requirements to be confirmed		PF2/WP2
2020-004	C1	GR processing time	All material Purchasing data requirements to be confirmed		PF2/WP2
2020-004	C1	Manufacturer Part No	All spares to have Manufacturer Part No populated		PF2/WP2

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

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

Materials - Purchasing View 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
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 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
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_MARC	WERKS	Plant	S/4HANA	S_MARC	WERKS	Plant	Map from source to target
003	PF2/WG2	S_MARA	MEINS	Base Unit of Measure (ISO Format)	S/4HANA	S_MARA	MEINS	Base Unit of Measure (ISO Format)	Map from source to target in adherence to Data Standard
004	PF2/WG2	S_MARA	BSTME	Order Unit of Measure (ISO Format)	S/4HANA	S_MARA	BSTME	Order Unit of Measure (ISO Format)	Map from source to target in adherence to Data Standard
005	PF2/WG2	S_MARA	VABME	State of Variable Purchase Order Unit	S/4HANA	S_MARA	VABME	State of Variable Purchase Order Unit	Copy from source to target system
006	PF2/WG2	S_MARC	EKGRP	Purchasing Group	S/4HANA	S_MARC	EKGRP	Purchasing Group	Map from source to target using Purchasing Group mapping table
007	PF2/WG2	S_MARA	MATKL	Material Group	S/4HANA	S_MARA	MATKL	Material Group	Map from source to target using Material Group mapping table
008	PF2/WG2	S_MARC	MMSTA	Plant-Specific Material Status	S/4HANA	S_MARC	MMSTA	Plant-Specific Material Status	Copy from source to target system
009	PF2/WG2	S_MARC	MMSTD	Valid From Date for Status	S/4HANA	S_MARC	MMSTD	Valid From Date for Status	Copy from source to target system
010	PF2/WG2	S_MARC	TAXIM	Tax Indicator	S/4HANA	S_MARC	TAXIM	Tax Indicator	Copy from source to target system
011	PF2/WG2	S_MARC	KAUTB	Automatic Purchase Oder Allowed	S/4HANA	S_MARC	KAUTB	Automatic Purchase Oder Allowed	Copy from source to target system
012	PF2/WG2	S_MARC	XCHPF	Batch Management Req. Indicator	S/4HANA	S_MARC	XCHPF	Batch Management Req. Indicator	Copy from source to target system
013	PF2/WG2	S_MARA	EKWSL	Purchasing Value Key	S/4HANA	S_MARA	EKWSL	Purchasing Value Key	Copy from source to target system
014	PF2/WG2	S_MARC	WEBAZ	GR Processing Time	S/4HANA	S_MARC	WEBAZ	GR Processing Time	Copy from source to target system

Transformation Mapping

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

Purchasing Group	Mapping of legacy Purchasing Groups 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	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	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
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:

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

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