Purpose

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

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

REGULAR MATERIALS

We will carry out the following steps:

1) Establish a detailed set of relevancy rules for materials by consulting with the Business, Functional and Integration teams

2) Identify all duplicate materials in the Legacy systems with the help of tools developed by Syniti, and subsequently cleanse or merge the data

3) Analyse all current Material Types in Legacy and set the mapping for S4H accordingly. Where it is not possible for a one to one mapping between types we will work with the business to identify the correct mapping on a material level.

4) We will carry out cleansing tasks where needed across all material fields (for example, material descriptions and languages)

5) We will provide value mapping tables where needed for S4H compliance or where standardization is required (for example, Units of Measure)

6) We will provide detailed transformation rules for Syniti, working with our Functional and Integration teams

Relevancy Rules

REGULAR MATERIALS

1. All materials created in the previous 6 months will be included unless flagged for deletion
2. All Material Types will be considered unless they are on the Exclusion list as follows: Material Types PROD (PF2 & WP2), ZIMM, ZIRT (PF2), ZINT (WP2), 731 (PF2) to be excluded. Also Maintenance Assemblies to be excluded (MTypes Z750 (PF2), ZIBA (WP2)).
3. Material Types ZUNB, ZBOM, ZPRC (WP2) will be included regardless of activity (unless flagged for deletion).
4. For Services we will include materials where MARA.MTART = ZDIE (WP2) or Z710, Z720, Z732, ZB20 (PF2). We will also include materials where MARA.MEINS = PRT or LE, or where MARA.MTPOS_MARA = LEIS.
5. We will only include materials that are extended to Plants currently in scope, according to the Enterprise Structure (excluding ZPRC material type as these do not require plant extension). If any material has no valid extensions, to any in scope plants, but open transactions/stock exist within these corresponding in scope plants, then we will include these materials as part of relevancy.
6. We will include for migration all materials that have activity over the previous
7. All materials created in the previous 6 months will be included unless flagged for deletion
8. 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).
9. 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
10. 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.
11. Additionally, we can check material movements by querying MKPF/MSEG tables for the last 48 months for non ZIND/ZABF materials and , or 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.
12. 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'.
13. 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)

14. We will include BOM data for materials in scope using tables: MAST/STKO/STPO. We will include all Production, Plant Maintenance and Sales BOMs and their related components. MAST data will include BOM Usage (STLAN) 1 (Production), 4 (Plant Maintenance) & 5 (Sales and Distribution). STKO data will include BOM Category STKO.STLTY = E (Equipment) F (Functional Location) & M (Material). All BOM components will be included in relevancy regardless of activity (unless flagged for deletion). Exclude any deleted records STKO.LOEKZ, STKO.LKENZ= X, STPO.LKENZ = X.
15. 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
16. Deletion Flags (Table/Field) are as follows: MARA.LVORM = 'X' MARA.MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system) MARA.MSTAV = 50,51
17. :
    1. For procurement data use EKKO/EKPO tables where EKKO.LOEKZ = "" (blank) EKPO.LOEKZ = "" (blank) 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. This applies to the following Order Categories only, Process Orders (AUFK.AUTYP = 40) and Maintenance Orders (AUFK.AUTYP = 30) where AUFK.LOEKZ = "" (blank).
    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 SL date (EORD.BDATU) has not expired. Check that EINA.LOEKZ = "" (blank)  and EINE.LOEKZ = "" (blank). Check that PIR dates, (EINA.LIFBI) and (EINE.PRDAT), have not expired.
18. 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.
19. We will include for migration all materials that have open documents including the following:
    1. Open PO where (EKPO.EREKZ ≠ 'X') and (EKKO.BSTYP = F) and STO where (EKPO.ELIKZ ≠ 'X'), (EKKO.BSTYP = F) and (EKKO.BSART = UB/UBNI).
    2. Open contracts and scheduling agreements where (EKKO.KDATE has not expired) and (EKKO.BSTYP = K)
    3. Open SO. VBUK.GBSTK = ('A','B') VBUK.VBTYP = C
    4. Open WO. Use AUFK for checking open Process orders (AUFK.AUTYP = 40) and Maintenance Orders (AUFK.AUTYP=30). Link field AUFK.OBJNR to JEST.OBNR to get status codes not equal to TECO AND JEST.INACT ≠ 'X'.
20. Have current stock/inventory

    1. For current stock/inventory use the following tables:

       MARD

       MKOL (Consignment stock)

       MSKA (Sales Order stock)

       MSLB (Special stock)

       MSPR (Project stock)

21. We will include BOM data for materials in scope using tables: MAST/STKO/STPO. We will include all Production and 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 STKO.STLTY = E (Equipment), F (Functional Location) & M (Material). Exclude inactive BOMs (STKO.STLST = 02). All BOM components will be included in relevancy regardless of activity (unless flagged for deletion). Exclude any deleted records STKO.LOEKZ, STKO.LKENZ= X, STPO.LKENZ = X.
22. 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
23. Deletion Flags (Table/Field) are as follows: MARA.LVORM = 'X' MARA.MSTAE = Z4, ZZ (PF2 system) Z0 (WP2 system) MARA.MSTAV = 51
24. Materials with the word '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***'
25. 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 that EBAN.LOEKZ = "" (blank). Check valid Purchase Org/ Plant /Company Code according to the Enterprise Structure.
26. 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
27. Include all materials all materials with PIRPLIR (Planned Independent Requirements). Check table PBIM/PBED for materials PBIM.MATNR. Check PBIM.LOEVR ≠ 'D'. Check PBIM.WERKS for in scope Plants.
28. Include all materials with planned orders for external procurement. Check table PLAF. Check date PLAF.PSTTR for previous 4 years activity. Check for special procurement in field PLAF.SOBES = 0. 

SERVICE MATERIALS - Data Analysis

1. Material Types in Scope, include materials where MARA-MTART is one of the following: ZSER, SERV, DIEN, ZDIE OR MARA-MTART is in ('Z710', 'Z720', 'Z732') and the base unit of measure (MEINS) is either 'PRT' or 'LE';
2. Recently Created Materials: All materials created within the last 6 months (based on MARA-ERSDA) must be included, unless flagged for deletion;
3. Enterprise Structure Relevancy: Only include materials that are extended to objects in scope according to the enterprise structure:
   a. Company Codes in scope
   b. Plants in scope
   c. Purchasing Organizations in scope
   d. Sales Organizations in scope

4. Materials With Historical Activity (Last 60 Months), those are relevant for migration if they had documented activity in the previous 60 months, based on:
   a. Procurement activity:
      - Use EKKO/EKPO tables.
      - Exclude records where EKKO.LOEKZ is C or X.
      - Exclude items where EKPO.LOEKZ is L or S.
      - Use EKPO.AEDAT for activity date filtering.
   b. Sales activity:
      - Use VBAK/VBAP tables.
      - Use VBAK.ERDAT for activity date filtering.

5. Are relevant for migration, the materials that had activities over the previous 60:
   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 
6. 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') 

Source Approx No. of Records

No. of Records

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. 

Additional Information

MDS Documents

MDS Link

Pending Approval 

Additional Information

MDS Documents

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
• Additional Supplier languages that are possible: 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

Not Applicable

Target Design

This section defines the structure and configuration of the target system in SAP S/4HANA. It specifies how each target field is designed, including data types, field lengths, and business rules, ensuring alignment between functional requirements and technical implementation for the conversion process.

The technical design of the target for this conversion approach.

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

Not Applicable

Target Design

This section defines the structure and configuration of the target system in SAP S/4HANA. It specifies how each target field is designed, including data types, field lengths, and business rules, ensuring alignment between functional requirements and technical implementation for the conversion process.

The technical design of the target for this conversion approach.

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

Data Cleansing

Data Cleansing

Conversion Process

The high-level process is represented by the diagram below:

Image Added

The high level process for Classes that will be captured in a DCT are represented by the diagram below:

Image Addede

Data Privacy and Sensitivity

Extraction

The source for Basic data for Materials is PF2 & WP2.  This will be extracted by Syniti based on the Relevancy criteria.

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Materials & Service Master

Enrichment DCT for Material Type 

When you will rerun?
How will you maintain old decisions

Extraction Dependencies

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:

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Inclusion table/Exclusion Table

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Google Drive Live Link
url https://docs.google.com/spreadsheets/d/1ycO3yrVqQufSK-M9IhUEGp9YQQ8wQP4A/edit?gid=87624989#gid=87624989

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.

2019-002

C1

Description format

2019-003

C1

UoM alignment

All material UoMs to adhere to or be mapped to S4 ISO standard.

2019-004

C1

Check Gross and Net Weights

Check for missing weights and that Gross Weight >= Net

2019-006

C1

Duplicate materials/services excluded

Check for materials with same Long/Short Description

Conversion Process

The high-level process is represented by the diagram below:

Image Removed

The high level process for Classes that will be captured in a DCT are represented by the diagram below:

Image Removede

Data Privacy and Sensitivity

Extraction

The source for Basic data for Materials is PF2 & WP2.  This will be extracted by Syniti based on the Relevancy criteria.

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Materials & Service Master

Material Description (Short Text)

LANGUAGE EN

MTPOS_MARA

Extraction Dependencies

1

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:

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

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

5

Transformation jobs are ready for execution.

Syniti

Generate Load Files.

Syniti

Transformation Rules

Transformation Mapping

Material Type

Mapping of legacy Material Types to target system value

Material Group

Mapping of legacy Material Groups to target system value

Transformation Dependencies

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

Value mapping and XREF tables are ready

Syniti & S2P Data Team

Pre-Load Validation

Project Team

Completeness

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

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

Completeness

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

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:

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

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

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Post-Load Steps

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also Next Steps: 

We are adding list of all tasks which need to be completed for Material master data preparation for migration.

Change log

Workflow history