Status	Revision in Progress
Owner	HANCOCK-ext, John
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Materials - Basic Data View in S/4 HANA.

---CHECKLIST - DATA TEAM---

1) Legacy systems (Logical Source and Target Systems are identified)
2) Extraction methods and file types
3) Scope relevancy criteria
4) Target structure/ Rules
5) MDS links
6) Cleansing rules
- 6a) Cleansing reports with technical information
- 6b) Profiling
- 6c) Cleansing reports which you need to be developed by Syniti
- 6d) Deduplication (with technical details of Table-Fields, Conditions)
- 6e) Frequency of running reports
7) Transformation - and for this DOMD template must be populate and final version of DOMD template should be copied to Transformation section in CSpecs
8) Configuration/Value mapping file link
9) Value Mappings (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
10) Load template link
11) Loading method (Processing Type is specified, i.e. Direct Input, BAPI, IDoc, Web Service, OData API, etc.)
12) Loading sequence or dependency
13Error handling requirements are specified / including alerting requirement / expected action on failure.
13) Data Analysis
14) Pre load validation
15) Post load validation
16) any Exceptions (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
17)Application log requirement if applicable to be specified.
18) Signoff

Conversion Scope

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

All materials created in the previous 6 months will be included unless flagged for deletion
Material Types ZUNB, ZBOM, ZPRC will be included regardless of activity (unless flagged for deletion). Material Types PROD, ZINT will be excluded. Maintenance Assemblies are excluded (MTypes Z750, ZIBA).
We will only include materials that are extended to the following according to the Enterprise Structure (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
We will include for migration all materials that have activity over the previous 48 months for non ZIND/ZABF materials, or 60 months for ZIND/ZABF materials:
1. For procurement data use EKKO/EKPO tables (remove any records in EKKO/EKPO where EKKO.LOEKZ = C,X EKPO.LOEKZ = L,S and use EKPO/AEDAT for date range
2. For sales data use VBAK/VBAP tables
3. For work order data use AUFK/AFKO/AFPO tables. Check date using AUFK.ERDAT. Enter Order Category AUFK.AUTYP 40 for Process Orders and 30 for Maintenance Orders.
4. Valid PIRs and Source List (this includes Not Deleted/Validity Date not expired/In scope Purchasing Orgs and Plants based on Enterprise Structure) Check tables EINA/EINE/EORD. Check EORD.NOTKZ is showing as not blocked Check that EORD.BDATU is greater than current date.
Additionally, we can check material movements by querying MKPF/MSEG tables for the last 48 months for non ZIND/ZABF materials and 60 months for ZIND/ZABF materials. Link MKPF.MBLNR (Document Number) to MSEG.MBLNR. Enter dates with MKPF.BLDAT. WP2 may have to be restricted to quarterly data due to the number of records. In MKPF.VGART (Transaction Types) add: IB,ID,IZ,RS,SI,WA,WE,WF,WH,WI,WL,WO,WQ,WR,WS,WV,WZ.
We will include for migration all materials that have open documents including the following:
1. Open PO and STO. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = F)
2. Open contracts and scheduling agreements. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = K)
3. Open SO. VBUK.GBSTK = ('A','B')
4. Open WO. Use AUFK for checking open Process orders. Link field AUFK.OBJNR to JEST.OBNR to get status codes not equal to TECO AND JEST.INACT ≠ 'X'.
Have current stock/open inventory
1. For Open Inventory use the following tables:
  MARD
  MKOL (Consignment stock)
  MSKA (Sales Order stock)
  MSLB (Special stock)
  MSPR (Project stock)
We will include all Production BOM data for materials in scope using tables: MAST/STKO/STPO. We will also include all Plant Maintenance BOMs and their related components. MAST data will include BOM Usage (STLAN) 1 (Production) & 4 (Plant Maintenance). STKO data will include BOM Category (STLTY) E (Equipment) & M (Material).
Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
1. Open PO/STO
2. Open contracts and scheduling agreements
3. Open SO
4. Open WO
Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
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***'
Include ZIND/ZABF materials with Purchase Requisition for the last 60 months. Check table EBAN. Check for validity date EBAN.ERDAT. Check EBAN.BSTYP = B. Check valid Purchase Org/Plant/Company Code according to the Enterprise Structure
Include non ZIND/ZABF materials with Purchase Requisition for the last 48 months. Check table EBAN. Check for validity date EBAN.ERDAT. Check EBAN.BSTYP = B. Check valid Purchase Org/Plant according to the Enterprise Structure
Include all materials with PIR(Planned Independent Requirements). Check table PBIM/PBED for materials PBIM.MATNR. Check PBIM.LOEVR ≠ 'D'. Check PBIM.WERKS for in scope Plants.

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.

1,200,000

S4H

260,000

Additional Information

MDS Documents

20251028

MDS pending

Data Extraction

Data has been extracted from Production and files are kept here:

202511XX

Extraction Pending

Extraction/Transformation Methods and File Types

Data is Extracted and Transformed by Syniti ADM, the staging area of the Migration Cockpit will be updated by Syniti.

Multi-language Requirement

Languages to be extracted (available on Source Systems)

SAP standard supports all ISO languages, ensure that all standard languages are considered in scope.

Material Master will have a default description available in English.
Multi language is supported for Materials. Login via a different language will show the description displayed in the logon language if the language key is maintained.

Core languages: EN - English, FR - French, IT - Italian and ZH - Mandarin.
Additional languages: PT - Portuguese, DE - German, ES - Spanish
Supplier languages that are possible: FR - French, EN - English, ES - Spanish, DE - German, IT - Italian, NL - Dutch, PT - Portuguese, ZH - Mandarin, PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional, SK - Slovak, Z9 - Brazil Portuguese.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Material Master: Source ECC Material → Target S4H Material Master

Source Field Information

Transform Rules

Target Field Information

Sequence

Technical Source Table

Field Name

Technical Source Field

Field Format

Field Length

Comments

Mapping Type

Transform Rule or Default Value

Validation Rule

Comments

Dataload Template

Sheet Name

Group

Field Description

Business Description

Check Table

Business Mandatory
Y/N/C

System Mandatory
Y/N/C

Type

Length

Decimal

Sap Table Name

Sap Field Name

MARA

Material Number

MATNR

Text (CHAR)

40

- Mandatory for Migration Cockpit

Text (CHAR)

40

S_MARA

MATNR

MARA

Material Type

MTART

Text (CHAR)

4

- Mandatory for Migration Cockpit

Text (CHAR)

4

S_MARA

MTART

MARA

Material Group

MATKL

Text (CHAR)

9

Text (CHAR)

9

S_MARA

MATKL

MARA

Industry Sector

MBRSH

Text (CHAR)

1

Text (CHAR)

1

S_MARA

MBRSH

MARA

Description

MAKTX

Text (CHAR)

40

- Mandatory for Migration Cockpit

Text (CHAR)

40

S_MARA

MAKTX

MARA

Language Key

SPRAS

Text (CHAR)

1

- Mandatory for Migration Cockpit

Text (CHAR)

1

S_MARA

SPRAS

MARA

Base Unit of Measure (ISO Format)

MEINS

Text (CHAR)

3

- Mandatory for Migration Cockpit

Text (CHAR)

3

S_MARA

MEINS

MARA

Change Number

AENNR

Text (CHAR)

6

Text (CHAR)

6

S_MARA

AENNR

MARA

Revision Level

REVLV

Text (CHAR)

2

Text (CHAR)

2

S_MARA

REVLV

MARA

GTIN

EAN11

Text (CHAR)

18

Text (CHAR)

18

S_MARA

EAN11

MARA

GTIN Category

NUMTP

Text (CHAR)

1

Text (CHAR)

1

S_MARA

NUMTP

MARA

Division

SPART

Text (CHAR)

2

Text (CHAR)

2

S_MARA

SPART

MARA

Old Material Number

BISMT

Text (CHAR)

40

Text (CHAR)

40

S_MARA

BISMT

MARA

Product Hierarchy

PRDHA

Text (CHAR)

18

Text (CHAR)

18

S_MARA

PRDHA

MARA

Batch Management Required Ind.

XCHPF

Text (CHAR)

1

Text (CHAR)

1

S_MARA

XCHPF

MARA

Has Empties

MLGUT

Text (CHAR)

1

Text (CHAR)

1

S_MARA

MLGUT

MARA

Valid From

DATAB

Date

S_MARA

DATAB

MARA

Deletion Date

LIQDT

Date

S_MARA

LIQDT

MARA

Industry Standard Description

NORMT

Text (CHAR)

18

Text (CHAR)

18

S_MARA

NORMT

MARA

Size/Dimensions

GROES

Text (CHAR)

32

Text (CHAR)

32

S_MARA

GROES

MARA

Laboratory / Design Office

LABOR

Text (CHAR)

4

Text (CHAR)

4

S_MARA

LABOR

MARA

External Product Group

EXTWG

Text (CHAR)

18

Text (CHAR)

18

S_MARA

EXTWG

MARA

General Item Category Group

MTPOS_MARA

Text (CHAR)

4

Text (CHAR)

4

S_MARA

MTPOS_MARA

MARA

Authorization Group

BEGRU

Text (CHAR)

4

Text (CHAR)

4

S_MARA

BEGRU

MARA

Cross-Plant Product Status

MSTAE

Text (CHAR)

2

Text (CHAR)

2

S_MARA

MSTAE

MARA

Valid-From Date

MSTDE

Date

S_MARA

MSTDE

MARA

Quality Manag. in Procurement Is Active

QMPUR

Text (CHAR)

1

Text (CHAR)

1

S_MARA

QMPUR

MARA

ANP Code

ANP

Number (NUMC)

9

Number (NUMC)

9

S_MARA

ANP

MARA

Gross Weight

BRGEW

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

BRGEW

MARA

Net Weight

NTGEW

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

NTGEW

MARA

Unit of Weight (ISO Format)

GEWEI

Text (CHAR)

3

Text (CHAR)

3

S_MARA

GEWEI

MARA

Length

LAENG

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

LAENG

MARA

Width

BREIT

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

BREIT

MARA

Height

HOEHE

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

HOEHE

MARA

Unit for Length/Width/Height(ISO Format)

MEABM

Text (CHAR)

3

Text (CHAR)

3

S_MARA

MEABM

MARA

Volume

VOLUM

Number (NUMC)

13,3

Number (NUMC)

13,3

3

S_MARA

VOLUM

MARA

Volume Unit

VOLEH

Text (CHAR)

3

Text (CHAR)

3

S_MARA

VOLEH

MARA

Capacity Usage

CAPAUSE

Number

15

Number

15

S_MARA

CAPAUSE

MARA

Compliance Relevant

CHML_CMPLNC_RLVNCE_IND

Text (CHAR)

1

Text (CHAR)

1

S_MARA

CHML_CMPLNC_RLVNCE_IND

MARA

Product Is Configurable

KZKFG

Text (CHAR)

1

Text (CHAR)

1

S_MARA

KZKFG

MARA

Order Unit of Measure (ISO Format)

BSTME

Text (CHAR)

3

Text (CHAR)

3

S_MARA

BSTME

MARA

Purchasing Value Key

EKWSL

Text (CHAR)

2

Text (CHAR)

2

S_MARA

EKWSL

MARA

State of Variable Purchase Order Unit

VABME

Text (CHAR)

1

Text (CHAR)

1

S_MARA

VABME

MARA

Internal Product Number

BMATN

Text (CHAR)

18

Text (CHAR)

18

S_MARA

BMATN

MARA

Manufacturer Part Number

MFRPN

Text (CHAR)

40

Text (CHAR)

40

S_MARA

MFRPN

MARA

Manufacturer Number

MFRNR

Text (CHAR)

10

Text (CHAR)

10

S_MARA

MFRNR

MARA

Manufacturer Part Profile

MPROF

Text (CHAR)

4

Text (CHAR)

4

S_MARA

MPROF

MARA

Transportation Group

TRAGR

Text (CHAR)

4

Text (CHAR)

4

S_MARA

TRAGR

MARA

Cross-Distribution Chain Product Status

MSTAV

Text (CHAR)

2

Text (CHAR)

2

S_MARA

MSTAV

MARA

DG Indicator Profile

PROFL

Text (CHAR)

3

Text (CHAR)

3

S_MARA

PROFL

MARA

Environmentally Relevant

KZUMW

Text (CHAR)

1

Text (CHAR)

1

S_MARA

KZUMW

MARA

In Bulk/Liquid

ILOOS

Text (CHAR)

1

Text (CHAR)

1

S_MARA

ILOOS

MARA

Highly Viscous

IHIVI

Text (CHAR)

1

Text (CHAR)

1

S_MARA

IHIVI

MARA

Valid From Date for Status

MSTDV

Date

S_MARA

MSTDV

MARA

Material Category

ATTYP

Text (CHAR)

2

Text (CHAR)

2

S_MARA

ATTYP

MARA

Product Group: Packaging Materials

MAGRV

Text (CHAR)

80

Text (CHAR)

80

S_MARA

MAGRV

MARA

Packaging Product Type

VHIART

Text (CHAR)

80

Text (CHAR)

80

S_MARA

VHIART

MARA

Allowed Packaging Weight

ERGEW

Text (CHAR)

13

Text (CHAR)

13

S_MARA

ERGEW

MARA

Unit of Allowed Packaging Weight

ERGEI

Text (CHAR)

80

Text (CHAR)

80

S_MARA

ERGEI

MARA

Allowed Packaging Volume

ERVOL

Text (CHAR)

13

Text (CHAR)

13

S_MARA

ERVOL

MARA

Unit of Allowed Packaging Volume

ERVOE

Text (CHAR)

80

Text (CHAR)

80

S_MARA

ERVOE

MARA

Packaging Product Is Closed Packaging

KZGVH

Text (CHAR)

1

Text (CHAR)

1

S_MARA

KZGVH

MARA

Excess Volume Tolerance for HU

VOLTO

Number

3

Number

3

S_MARA

VOLTO

MARA

Period Indicator for Shelf Life

IPRKZ

Text (CHAR)

80

Text (CHAR)

80

S_MARA

IPRKZ

MARA

Storage Conditions

RAUBE

Text (CHAR)

80

Text (CHAR)

80

S_MARA

RAUBE

MARA

Temperature Conditions Indicator

TEMPB

Text (CHAR)

2

Text (CHAR)

2

S_MARA

TEMPB

MARA

Hazardous Product Number

STOFF

Text (CHAR)

40

Text (CHAR)

40

S_MARA

STOFF

MARA

Number of Goods Receipt/Issue Slips

WESCH

Number

13

Number

13

S_MARA

WESCH

MARA

Indicator: Approved Batch Rec. Required

XGCHP

Text (CHAR)

1

Text (CHAR)

1

S_MARA

XGCHP

MARA

Total Shelf Life

MHDHB

Number

4

Number

4

S_MARA

MHDHB

MARA

Minimum Remaining Shelf Life

MHDRZ

Number

4

Number

4

S_MARA

MHDRZ

MARA

Indi. for the Shelf Life Expiration Date

SLED_BBD

Text (CHAR)

80

Text (CHAR)

80

S_MARA

SLED_BBD

MARA

Storage Percentage

MHDLP

Number

3

Number

3

S_MARA

MHDLP

MARA

Rounding Rule for Calculation of SLED

RDMHD

Text (CHAR)

80

Text (CHAR)

80

S_MARA

RDMHD

MARA

Serial Number Profile

SERIAL

Text (CHAR)

80

Text (CHAR)

80

S_MARA

SERIAL

MARA

Relevant for Hazardous Substances

HAZMAT

Text (CHAR)

1

Text (CHAR)

1

S_MARA

HAZMAT

MARA

ABC Indicator

MAABC

Text (CHAR)

1

Text (CHAR)

1

S_MARA

MAABC

MARA

Country/Region of Origin

HERKL

Text (CHAR)

3

Text (CHAR)

3

S_MARA

HERKL

MARA

Purchasing Group

EKGRP

Text (CHAR)

3

Text (CHAR)

3

S_MARA

EKGRP

MARA

Tax Classification

TAKLV

Text (CHAR)

1

Text (CHAR)

1

S_MARA

TAKLV

MARA

Loading Group

LADGR

Text (CHAR)

4

Text (CHAR)

4

S_MARA

LADGR

MARA

Indicator: Quality

PSTATQ

Text (CHAR)

1

Text (CHAR)

1

S_MARA

PSTATQ

MARA

Indicator: Sales

PSTATV

Text (CHAR)

1

Text (CHAR)

1

S_MARA

PSTATV

MARA

Indicator: Storage

PSTATL

Text (CHAR)

1

Text (CHAR)

1

S_MARA

PSTATL

MARA

Indicator: Purchasing

PSTATE

Text (CHAR)

1

Text (CHAR)

1

S_MARA

PSTATE

Material Master: Source ECC Service Master → Target S4H Material Master

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Source System
2019-001	C1	English description missing or EN description not English language	All materials require English description by default, so need to be provided if missing. Current EN descriptions not in English language need to be translated.	PF2/WP2
2019-002	C1	Description format	Material descriptions must adhere to S4 standardization so no special characters etc and must not exceed character limit	PF2/WP2
2019-003	C1	UoM alignment	All material UoMs to adhere to S4 standardization. Confirmation regarding EA/PC format.	PF2/WP2
2019-004	C1	Check Gross and Net Weights	Check for missing weights and that Gross Weight >= Net	PF2/WP2
2019-005	C1	Country of Origin	Check Country of Origin exists for procured materials	PF2/WP2
2019-006	C1	Duplicate materials excluded	Check for materials with same Long/Short Description Check Old Material Number field Check Materials with same EAN Check Materials with same Manufacturer Part Number Check Source List/PIR for identical set ups Check BOMs for identical components Where duplicates found, check if either has no activity	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 Material Master data (MARA) from PF2 and WP2 ECC systems according to the defined Relevancy Rules (scope by Material Type, and Activity).	SyWay Data Team
2	Validate the extracted data volumes against ECC totals to ensure completeness before applying any filtering (count check per Material Type and per Plant).	SyWay Data Team
3	Apply exclusion criteria (e.g., deletion flags, obsolete status, test materials, invalid UoM, invalid descriptions).	SyWay Data Team
4	Include recent transactional linkage (e.g., materials used in open PO, SO, or movements within last 3 years).	SyWay Data Team
5	Validate UoM conversions and ensure all Base Units (MEINS) exist in T006 (UoM ISO mapping).	SyWay Data Team
6	Generate Google Sheet report pre-populated with PF2 and WP2 extracted data for Business validation (showing only relevant fields from MDS_2019).	SyWay Data Team
7	Submit the validated dataset for peer review and final sign-off by Functional and Business teams before transformation load.	SyWay Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Service Master

20251028

DCT SYENSQO - Source data for Product.xlsx

Field Name	Data Type	Length	Description	Rule
EINA-MATNR	CHAR	18	Material Number	Required
EINA-MATKL	CHAR	9	Material Group	Conditional
EINA-LIFNR	CHAR	10	Vendor Number	Required
EINA-TXZ01	CHAR	40	Short Text	Required
EINA-MEINS	UNIT	3	Base Unit of Measure	Conditional
EINA-UMREZ	NUMC	5	Numerator for Conversion	Conditional
EINA-UMREN	NUMC	5	Denominator for Conversion	Conditional
EINE-EKORG	CHAR	4	Purchasing Organization	Required
EINE-ESOKZ	CHAR	1	Info Category (Standard/Subcontracting/Consignment)	Required
EINE-WERKS	CHAR	4	Plant	Conditional
EINE-EKGRP	CHAR	3	Purchasing Group	Conditional

Notes

The DCT must align with the field status of the target Info Record view and the Pricing Procedure schema approved by the Functional Team,
Where transformation logic applies (example PurchOrg, Plant, Incoterms, Currency), reference should be made to the Transformation Mapping Table maintained by the Data Governance team,
Once the final pricing configuration is frozen, this DCT can be regenerated with the exact condition types(per country - considering respective mapping), access sequences, and validity schema.

Target Ready Data Collection Template will be created for Materials - Basic Data View data with exception of some fields which require transformation as mentioned in the transformation rule.

Materials - Basic Data 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
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
2	PF2/WQ2	S_MARA	MBRSH	Industry Sector	S/4HANA	S_MARA	MBRSH	Industry Sector	Copy from source to target system
3	PF2/WQ2	S_MARA	MTART	Material Type	S/4HANA	S_MARA	MTART	Material Type	Map from source to target using Material Type mapping table
4	PF2/WQ2	S_MARA	MAKTX	Description	S/4HANA	S_MARA	MAKTX	Description	Copy from source to target system in adherence to S4H Data Standard (ie. descriptions to be cleansed so that non standard special characters are excluded)
5	PF2/WQ2	S_MARA	SPRAS	Language Key	S/4HANA	S_MARA	SPRAS	Language Key	EN description to be created if not available. Copy local descriptions from source if required.
6	PF2/WQ2	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 S4H Data Standard
7	PF2/WQ2	S_MARA	MATKL	Material Group	S/4HANA	S_MARA	MATKL	Material Group	Map from source to target using Material Group mapping table
8	PF2/WQ2	S_MARA	SPART	Division	S/4HANA	S_MARA	SPART	Division	Map from source to target in adherence to S4H Data Standard
9	PF2/WQ2	S_MARA	PRDHA	Product Hierarchy	S/4HANA	S_MARA	PRDHA	Product Hierarchy	Map from source to target using Product Hierarchy mapping table
10	PF2/WQ2	S_MARA	MTPOS_MARA	General Item Category Group	S/4HANA	S_MARA	MTPOS_MARA	General Item Category Group	Copy from source to target system
11	PF2/WQ2	S_MARA	BRGEW	Gross Weight	S/4HANA	S_MARA	BRGEW	Gross Weight	Copy from source to target system
12	PF2/WQ2	S_MARA	NTGEW	Net Weight	S/4HANA	S_MARA	NTGEW	Net Weight	Copy from source to target system
13	PF2/WQ2	S_MARA	GEWEI	Unit of Weight (ISO Format)	S/4HANA	S_MARA	GEWEI	Unit of Weight (ISO Format)	Copy from source to target system in adherence to S4H Data Standard
14	PF2/WQ2	S_MARA	PROFL	DG Indicator Profile	S/4HANA	S_MARA		Compliance Relevant Indicator	If DG Ind Profile or Environmentally Rel is populated/ticked then set Compliance Relevant Indicator to X in S4H
15	PF2/WQ2	S_MARA	KZUMW	Environmentally Relevant	S/4HANA	S_MARA		Compliance Relevant Indicator	If DG Ind Profile or Environmentally Rel is populated/ticked then set Compliance Relevant Indicator to X in S4H

Transformation Mapping

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
Lab/Office	Mapping of legacy Lab/Office values to target system value
Division	Mapping of legacy Division values to target system value
Authorization Group	Mapping of legacy Authorization Group values 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	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

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

Change log

Version	Published	Changed By
CURRENT (v. 81)	Apr 29, 2026 14:44	HANCOCK-ext, John
v. 313	Apr 28, 2026 13:55	HANCOCK-ext, John
v. 312	Apr 27, 2026 07:42	HANCOCK-ext, John
v. 311	Apr 21, 2026 08:04	HANCOCK-ext, John
v. 310	Apr 21, 2026 08:01	HANCOCK-ext, John
v. 309	Apr 21, 2026 07:51	HANCOCK-ext, John
v. 308	Apr 10, 2026 12:02	HANCOCK-ext, John
v. 307	Apr 09, 2026 14:07	HANCOCK-ext, John
v. 306	Mar 06, 2026 13:37	MADHOK-ext, Jasleen
v. 305	Mar 03, 2026 17:15	HANCOCK-ext, John

Go to Page History

Workflow history

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

From Apr 10, 2026 to Apr 29, 2026	Actor	Type	Activity	Version
Revision in Progress	HANCOCK-ext, John	Edit	updated the page at 12:02 pm Other contributors:
	JAIN-ext, Gaurav	Comment	commented 8:17 am Use MKPF-BUDAT for validity period
	JAIN-ext, Gaurav	Comment	commented 8:13 am update the logic in ETL to include AUTYP (note for self)
Apr 09, 2026
	JAIN-ext, Gaurav	Comment	commented 10:26 pm Hi HANCOCK-ext, John the mapping is based on target material type. So there will be dependency that Material Type determination while running the transformation. NAVANDAR-ext, Divya MCARDLE-ext, Edward - FYI
	HANCOCK-ext, John	State	changed state to Revision in Progress at 2:07 pm	v307
Approved	HANCOCK-ext, John	Edit	updated the page at 2:07 pm

Workflow history

Space shortcuts

Page tree

CNV-2019 Materials - Basic Data View

Purpose

---CHECKLIST - DATA TEAM---

Conversion Scope

Additional Information

MDS Documents

20251028

MDS pending

Data Extraction

Data has been extracted from Production and files are kept here:

202511XX

Extraction Pending

Extraction/Transformation Methods and File Types

Multi-language Requirement

Languages to be extracted (available on Source Systems)

Document Management

Legal Requirement

Special Requirements

Target Design

Material Master: Source ECC Material → Target S4H Material Master

Material Master: Source ECC Service Master → Target S4H Material Master

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

20251028

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