Status
Owner	HANCOCK-ext, John CLARKE-ext, Steve BUOSI-ext, Angelo SLOAN-ext, Anthony
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 upload Materials - Purchasing View into S/4 HANA as part of the Material Data Migration.

Link to MDS: DD-FUN-050 Master Data Standard_2020-Material master-Purchasing data

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.

This object is migrated after Material Basic Data and Material General Plant, therefore only materials in scope for the object "2019 - Materials Basic Data View" and have Plants in scope as per the object "2010 - Materials - General Plant Data / S.Loc Data", are in scope for this object. Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules. Furthermore, as per the MDS for 2019, materials with certain Material Types will not be extended to the Purchasing View, while all other Material Types will be. Currently the Material Type not extended is the To-Be Material Type ZBAS, but this may change. Therefore this MDS must be reviewed for changes to this rule as part of the preparation of a Syniti ADMM Transform run.

As an additional relevancy requirement Plant Extensions where MARC-MMSTA = Z0 for WP2 and either Z4 or ZZ for PF2 must be excluded from the migration. Note that the existing rule of excluding a Plant Extension where MARC-LVORM = 'X' still applies.

The Service Master will be loaded as Materials in the Target. The relevancy rules for this are also covered in the object "2019 - Materials Basic Data View".

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

Materials: The Material Master Records will be extracted that meet the relevancy criteria of Material Basic Data. Material Type will further refine this list to Materials relevant for the Purchasing View.

Materials:
PF2: 115,853**
WP2: 81,288**
** As per Material relevancy criteria

Plants (See CNV-2010):
2.4 Million, depending on Plant consolidation

S4H

Materials:
197,141 **
** This will change based on the Material Deduplication Process

Plants (See CNV-2010):
TBC, depending on Plant consolidation

DCT

Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria to be created as Materials and Material Type will further refine this list to records relevant for the Purchasing View.

Services:
PF2: 9,821**
WP2: 353**
** As per Material relevancy criteria

S4H

10,174 **
** This will change based on the Material Deduplication Process

Predecessor Object

Material Master - Basic View (2019) → Materials - Additional data (2021) → Materials - General Plant Data / S.Loc Data (2010) → Materials Purchasing View (2020).

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.

Not Applicable

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	Field Description	Data Type	Length	Requirement	Updated in Predecessor / Other Object
MARC	MATNR	Material Number	CHAR	18	Required	2010
MARC	WERKS	Plant	CHAR	4	Required	2010
MARA	MEINS	Base Unit of Measure	UNIT	3	Required	2019
MARA	BSTME **	Order Unit	UNIT	3	Conditional	~~2019~~ **
MARA	VABME **	Variable Order Unit	CHAR	1	Conditional	~~2019~~ **
MARA	MATKL	Material Group	CHAR	9	Required	2019
MARC	EKGRP	Purchasing Group	CHAR	3	Conditional
MARC	MMSTA	Material Status (Plant-Specific)	CHAR	2	Conditional
MARC	MMSTD	Valid From	DATS	8	Conditional
MLAN	TAXIM	Tax Indicator for Material	CHAR	1	Required
MARC	MFRGR	Material Freight Group	CHAR	4	Conditional
MARC	KAUTB	Automatic PO allowed	CHAR	1	Required
MARC	KZKRI	Critical Part	CHAR	1	Conditional
MARA	MFRPN	Manufacturer Part Number	CHAR	40	Conditional
MARA	MFRNR	Manufacturer	CHAR	10	Conditional
MARC	HERKL	Country of Origin	CHAR	3	Conditional
MARC	WEBAZ	GR Processing Time	DEC	3	Conditional	2005

** BSTME and VABME are no longer in CNV_2019 so they must be included here.

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	Syniti Report Required
1	High	Purchasing Group Missing	If MARC-EKGRP is Blank then include in the report.	MARA-MATNR, MARC-WERKS	PF2, WP2 & DCT	YES
2	Medium	Country Of Origin Missing **	if ( MARC-HERKL is Blank ) AND ( T001W-LAND1 = 'BR' ) AND ( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR ( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( To-Be MARC-KZKRI = 'X' ) ) ) then include in the report **	MARA-MATNR, MARC-WERKS	PF2 & WP2	YES
3	~~Medium~~	~~GR Processing Time Missing~~****	~~If MARC-WEBAZ is Blank AND (To-Be Material Type = 'ZDIR' OR 'ZIND') then include in the report~~	~~MARA-MATNR, MARC-WERKS, MARA-MTART~~	~~PF2 & WP2~~	~~YES~~

** This rule has been clarified by Dean Leighton in a Google Chat with Jasleen Madhok, John Hancock and Steve Clarke on Wednesday 12 November 2025.
**** This report is not required because the field is owned by MRP and they will have and manage a cleansing report if required.

Conversion Process

The high-level process for Materials, where the source is PF2 & WP2, is represented by the diagram below:

SyWay Project > CNV-2020 Materials - Purchasing View > image-2025-10-23_10-50-21.png

The high-level process for Services, where there is no source data, is represented by the diagram below:

SyWay Project > CNV-2020 Materials - Purchasing View > image-2025-10-23_10-51-50.png

Field Governance Rules
These governance rules apply to the individual fields within the data record.
Rule #	Field Label	Rule Description	Validation Method	Conditional Logic	Cleansing Rule (see above)
1	MARA-MATNR & MARC-WERKS	Only records where the material or service has been loaded into the Target, i.e. it is relevant.	Upfront Automated	Fields in the Material & Plant XREFs
2	MARA-MTART	if To-Be Material Type = 'ZBAS' then DO NOT extend Material to Purchasing View else extend Material to Purchasing View		Field in the Material Type XREF
3	MARC-HERKL	This field is only applicable for Plants in Brazil with Material types associated with ZDIR or Spares (ZIND) or Capital Spares (UNBW, NLAG) and Critical Part = Active. **	Upfront Automated	( T001W-LAND1 = 'BR' ) AND ( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR ( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( MARC-KZKRI = 'X' ) ) ) **	Rule 2

** This rule has been clarified by Dean Leighton in a Google Chat with Jasleen Madhok, John Hancock and Steve Clarke on Wednesday 12 November 2025.

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Not Applicable

Extraction

The source for Purchasing data for Materials is PF2 & WP2. This will be extracted by Syniti and the Relevancy criteria, as specified in object "2019 - Materials Basic Data View" and Material Type relevant to the Purchasing View, applied to identify the records that are applicable for the Target load.

There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from a DCT (see below in the DCT section for more details).

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	Syniti

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

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.

There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from the DCT specified below. It will be populated by Business for relevant services which they want to migrate.

Materials - Purchasing View DCT Rules

Field Name	Field Description	Rule	Tool Tip
MARC-MATNR	Material Number	Required	The Service Master Number will be used to identify the corresponding Target Material Number.
MARC-WERKS	Plant	Exists in Plant XREF as a To-Be Plant and use dropdown.	Organizational unit where material is maintained/used (e.g., manufacturing site, storage location).
MARA-BSTME	Order Unit	Value in Check Table T006	The unit in which the material is ordered from vendors (may differ from Base UoM).
MARC-EKGRP	Purchasing Group	Value in Check Table T024	Buyer or group of buyers responsible for procurement activities of the material.
~~MARC-MMSTA~~***	~~Material Status (Plant-Specific)~~	~~Value in Check Table T141. Default to Blank.~~	~~Controls whether a material can be procured, produced, or sold in a plant.~~
~~MARC-MMSTD~~***	~~Valid From~~	~~If MARC-MMSTA contains a value then MARC-MMSTD must have a value else Blank~~	~~Date from which the material status or conditions are effective.~~
MLAN-TAXIM	Tax Indicator for Material	Value in Check Table TMKM1	Defines if material is taxable, non-taxable, or exempt for purchasing.
MARC-MFRGR	Material Freight Group	Value in Check Table TMFG	Groups materials for freight calculation and logistics handling.
~~MARC-KAUTB~~***	~~Automatic PO allowed~~	~~X or Blank. Default X.~~	~~Allows automatic generation of POs from requisitions without manual intervention.~~
~~MARC-KZKRI~~****	~~Critical Part~~	~~X or Blank Default Blank.~~	Used if we consider this Material a critical part from a planning perspective and/or we want it to be part of every inventory Count while running Cycle Counting. This indicator will be sent to Maestro/kinaxis as part of the Material Master Interface.
MARA-MFRPN	Manufacturer Part Number		General part number assigned by the manufacturer.
MARA-MFRNR	Manufacturer		Vendor or producer of the material.
MARC-HERKL	Manufacturer Country	Value in Check Table T005	Country where the manufacturer is located.
MARC-WEBAZ**	GR Processing Time	Value >= 0	Time (in days) between goods receipt and availability for use. Only capture a value here if the Material is for a Service (Material Type ZSER). For other materials this field is captured in the MRP Views.

** MARC-WEBAZ is in the Conversion Spec for 2005, Material Master - MRP Views, however the DCT is for Services and Services will not get the MRP Views so the field has been included to capture this data if required.
*** The MRC fields MMSTA, MMSTD and KAUTB are now defaulted in the Transformation section so they must be removed from the DCT.
**** MARC-KZKRI has been updated with CR0445. It now has default value which is done in the Transformation Rules.

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Materials and Plants in scope to be loaded must be identified so that we can limit the extraction to this sub-set of data.	Syniti

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 ADMM 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 ADMM.
Prepare target-ready data in the structure and format that is required for loading via the 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	Verify that Material data is extracted from both source systems.	Syniti / S2P Data Team
2	Verify that Services data is extracted from the DCT.	Syniti / S2P Data Team
3	Verify that the Material Number XREF has been updated for both material and service data.	Syniti
4	Review the MDS for 2019 to check what Material Types must not be extended to the Purchasing View and update the rule if required	S2P Data Team
5	Transformation jobs are ready for execution.	Syniti
6	Generate Load Files.	Syniti

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2,WP2,DCT	MARC	MATNR	Material Number	S/4HANA	MARC	MATNR	Material Number	Map Source to Target using Material XREF
2	PF2,WP2,DCT	MARC	WERKS	Plant	S/4HANA	MARC	WERKS	Plant	Map Source to Target using Plant XREF
	PF2,WP2,DCT	MARA	BSTME	Order Unit	S/4HANA	MARA	BSTME	Order Unit	Copy As-Is
	PF2,WP2,DCT	MARA	VABME	Variable Order Unit	S/4HANA	MARA	VABME	Variable Order Unit	Default to Blank
	PF2,WP2,DCT	MARC	EKGRP	Purchasing Group	S/4HANA	MARC	EKGRP	Purchasing Group	Map Source to Target using Purchasing Group XREF
	PF2,WP2,DCT	MARC	MMSTA	Material Status (Plant-Specific)	S/4HANA	MARC	MMSTA	Material Status (Plant-Specific)	Default to Blank
	PF2,WP2,DCT	MARC	MMSTD	Valid From	S/4HANA	MARC	MMSTD	Valid From	Default to Blank
	PF2,WP2,DCT	MLAN	TAXIM	Tax Indicator for Material	S/4HANA	MLAN	TAXIM	Tax Indicator for Material	Copy As-Is For ECC, use the following to go from MARC to MLAN: MARC-WERKS = T001W-WERKS, MARC-MATNR = MLAN-MATNR AND T001W-LAND1 = MLAN-ALAND
	PF2,WP2,DCT	MARC	MFRGR	Material Freight Group	S/4HANA	MARC	MFRGR	Material Freight Group	Copy As-Is
	PF2,WP2,DCT	MARC	KAUTB	Automatic PO allowed	S/4HANA	MARC	KAUTB	Automatic PO allowed	Default to X. This field may be updated as a follow-on activity during cut-over after the load.
	PF2,WP2,DCT	MARC	KZKRI***	Critical Part	S/4HANA	MARC	KZKRI***	Critical Part	Default to: if MARA-MTART IN ('UNBW','NLAG') and PIR > EUR 15k then X else Blank PIR > EUR 15K will have been calculated when determining MARA-MTART = UNBW or NLAG, therefore store the result of this calc in a table so it can be referenced here.
	PF2,WP2,DCT	MARA	MFRPN	Manufacturer Part Number	S/4HANA	MARA	MFRPN	Manufacturer Part Number	Copy As-Is
	PF2,WP2,DCT	MARA	MFRNR	Manufacturer	S/4HANA	MARA	MFRNR	Manufacturer	Copy As-Is
	PF2,WP2,DCT	MARC	HERKL	Country of Origin	S/4HANA	MARC	HERKL	Country of Origin	Copy As-Is
	DCT only	MARC	WEBAZ**	GR Processing Time	S/4HANA	MARC	WEBAZ**	GR Processing Time	Copy As-Is WHERE Source = DCT and S4H.MARA-MTART = 'ZSER' ELSE ignore

** MARC-WEBAZ is in the Conversion Spec for 2005, Material Master - MRP Views, however Service Materials will not get this View, so it will be captured in the DCT, along with all the other data for Services. If the DCT is used for Material Types other than ZSER then this value must be excluded.
*** MARC-KZKRI has been updated with CR0445.

Transformation Mapping

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

Mapping Table Name	Mapping Table Description	Link
Material	XREF	Conversion Specification - Mappings
Plant	XREF	Conversion Specification - Mappings
Purchasing Group	XREF	Conversion Specification - Mappings

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Data has been extracted from sources systems	Syniti
2	Deduplication is completed	Syniti & S2P Data Team
3	Configuration should be completed - (Config documents should be complete)	S2P Functional Team
4	Ensure DCT completeness	S2P Data Team
5	Value mapping and XREF tables are ready	Syniti & 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	The number of records presented after relevancy checks and validation, as well as the number of records in the DCT, needs to be correct compared to the staged data in Syniti ADMM.
Completeness check	All fields required as per mapping template rules must be completed. Syniti ADMM standard validity reports checking each field in Syniti must be built.

Accuracy

Task	Action
Conversion Accuracy	Verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM standard reports..
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
Completeness Check	Business should compare legacy record counts, taking into account the reduction from the relevancy and deduplication processes, against the record count in the preload table.

Accuracy

Task	Action
Conversion Accuracy	Business team to verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM reports/SAP reports.

Load

The load process includes:

Execute the automated data load into target system using the appropriate load tool.
Once the data is loaded into the target system, it will be extracted and prepared for Post Load Data Validation.

Load Run Sheet

Item #	Step Description	Team Responsible
1	Verify data extracted	Data Specialist/Functional - S2P
2	Verify data combined from both source systems and DCT	Data Specialist/Functional - S2P
3	Verify Material, Plant and Purchasing Group XREFs are ready	Data Specialist/Functional - S2P
4	Stage data for transformations	Syniti
5	Run transforms	Syniti
6	Execute pre-load report	Syniti
7	Validate preload report - release	Data Specialist/Functional - S2P
8	Prepare and simulate	Syniti
9	Pre-load verification and approval to load	Functional/Data Owner - S2P
10	Load to S4	Syniti
11	Complete Jira steps, Volumes and Timings	All - where applicable
12	Execute post-load report	Syniti
13	Post-load report verification/validation	Data Specialist/Functional/Data Owner - S2P
14	Object load completion approval	Data Owner - S2P

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
	MM Config Values

Conversion Objects

Object #	Preceding Object Conversion Approach
1	Material Master - Basic View (2019)
2	Materials - General Plant Data / S.Loc Data (2010)

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
Data	Source Material not linked to a Target Material in the XREF	Fix incorrect data
Data	Source Plant not linked to a Target Plant in the XREF	Fix incorrect data
Data	Source Purchasing Group not linked to a Target Purchasing Group in the XREF	Fix incorrect data
Data	Duplicates	Fix incorrect data
Load	Authorization errors	Apply for the applicable authorization permission and retry
Load	Technical load failures - If using MC - Simulation errors, etc	Investigate error and rectify. Retry simulation and/or load
Config	Configuration is missing in the Target System	Missing config added in the Target System

Post-Load Validation

Project Team

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

Post-Load Steps

Step Description	Team Responsible
Execute post-load report	Syniti
Post-load report verification/validation	Data Specialist/Functional/Data Owner - S2P
Object load completion approval	Data Owner - S2P

Completeness

Task	Action
Verify Count	The number of records presented in the post-load needs to be compared to the preload – Syniti report
Field by field check	Compare source data staged in the preload tables to target data in the load tables.

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	The number of records presented in the preload needs to be compared to the post-load Syniti report.
Missing data	Check missing data which was supposed to be loaded.
Reconciliation	Participate in Post-load walkthroughs.
Field by field check	Perform random Field by Field checks by comparing source data staged in the preload tables to target data in the load tables.

Accuracy

Task	Action
Conversion Accuracy	Verify that the data in S/4 HANA was loaded correctly via Syniti post-load reports.

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.

Any additional key assumptions.

Purpose

Conversion Scope

Predecessor Object

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Selection Screen

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

Post-Load Steps

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history