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

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.

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

Materials: The Material Master Records will be extracted that meet the relevancy criteria of Material Basic Data.

Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria.

Materials:
PF2: 115,853**
WP2: 81,288**

Services:
PF2: 9,821**
WP2: 353**

** As per relevancy criteria

S4H

207,315

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

Target Design

The technical design of the target for this conversion approach.

Table	Field	Field Description	Data Type	Length	Requirement	Updated in Predecessor 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	2019
MARA	MFRNR	Manufacturer	CHAR	10	Conditional	2019
MARC	HERKL	Manufacturer Country	CHAR	3	Conditional
MARC	WEBAZ	GR processing time	DEC	3	Conditional

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	High	Purchasing Group	Confirm all procured materials have Purchasing Data in place and confirm Purchasing Group mapping to S4 target value	*** How to tell if a mat is procured. Mat Status (MARC-MMSTA) = Procured	PF2/WP2
2	?	PIR alignment	Check that procured materials have PIR in place	*** Is this the right place to do this or should it be done in PIR object or is it already being done in PIR object	PF2/WP2
3	?	Manufacturer Country is blank at Basic Data and Plant level
4	?	GR processing time	All material Purchasing data requirements to be confirmed		PF2/WP2

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

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

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

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

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

Change log

Version	Published	Changed By	Comment
CURRENT (v. 15)	Apr 27, 2026 14:10	CLARKE-ext, Steve	Material Freight Group MARC-MFRGR is no longer needed
v. 85	Apr 21, 2026 11:09	CLARKE-ext, Steve
v. 84	Apr 21, 2026 07:44	CLARKE-ext, Steve
v. 83	Apr 13, 2026 15:07	CLARKE-ext, Steve
v. 82	Apr 09, 2026 07:12	CLARKE-ext, Steve
v. 81	Apr 03, 2026 18:02	CLARKE-ext, Steve	documenting the link between MARC and MLAN via T001W
v. 80	Apr 02, 2026 10:12	CLARKE-ext, Steve	Change for CR0445 affecting MARC-KZKRI: remove from DCT and default based on rule in Transformation Rules
v. 79	Mar 30, 2026 17:04	CLARKE-ext, Steve	Including the additional relevancy requirement based on MARC-MMSTA
v. 78	Mar 23, 2026 16:38	CLARKE-ext, Steve	updating logic for Country of Origin cleansing report
v. 77	Feb 20, 2026 10:41	BUOSI-ext, Angelo

Go to Page History

Workflow history

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

Apr 28, 2026	Actor	Type	Activity	Version
Approved	NAVANDAR-ext, Divya	State	changed state to Approved at 8:25 am	v86
Revision under Review	NAVANDAR-ext, Divya	State	gave Minor change approval at 8:25 am
Apr 27, 2026
	CLARKE-ext, Steve	Edit	updated the page at 2:10 pm Material Freight Group MARC-MFRGR is no longer needed
Apr 21, 2026
	CLARKE-ext, Steve	Comment	commented 11:10 am Done. I have updated MMSTD, the date field, while MMSTA is the status field.
	CLARKE-ext, Steve	Edit	updated the page at 11:09 am
	NAVANDAR-ext, Divya	Comment	commented 9:37 am As discussed in the chat as on 21st April 2026, use the conversions TCURR from SAPWP2 source only for Wp2 and PF2.

Workflow history

Space shortcuts

Page tree

CNV-2020 Materials - Purchasing View

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

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