| Status | |
|---|---|
| Owner | |
| 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 - 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):
- Company Codes in scope
- Plants in scope
- Purchasing Orgs in scope
- 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:
- 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
- For sales data use VBAK/VBAP tables
- 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.
- 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:
- Open PO and STO. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = F)
- Open contracts and scheduling agreements. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = K)
- Open SO. VBUK.GBSTK = ('A','B')
- 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
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:
- Open PO/STO
- Open contracts and scheduling agreements
- Open SO
- 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.
| 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 |
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
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
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.
DOMD Documents
The mapping document can be accessed using the link below.
202511XX | Extraction Pending |
Material Master: Source ECC Material (all material types in scope) → Target S4H Material Master
| Source Field Information | Transformation/Business Rules | Target Field Information | |||||||||||||||||||||
| Sequence | Technical Source Table | Field Description | 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 |
| 001 | MARA | Material Number | MATNR | Text (CHAR) | 40 | Default Value | <EMPTY> | - Mandatory for Migration Cockpit | Material Number | YES | YES | Text (CHAR) | 18 | S_MARA | MATNR | ||||||||
| 002 | MARA | Material Type | MTART | Text (CHAR) | 4 | - Mandatory for Migration Cockpit | Material Type | YES | YES | Text (CHAR) | 4 | S_MARA | MTART | ||||||||||
| 003 | MARA | Material Group | MATKL | Text (CHAR) | 9 | Material Group | Text (CHAR) | 9 | S_MARA | MATKL | |||||||||||||
| 004 | MARA | Industry Sector | MBRSH | Text (CHAR) | 1 | Update Target Field using the Source field as-is | Industry Sector | Text (CHAR) | 1 | S_MARA | MBRSH | ||||||||||||
| 005 | MARA | Description | MAKTX | Text (CHAR) | 40 | - Mandatory for Migration Cockpit | Description | YES | YES | Text (CHAR) | 40 | S_MARA | MAKTX | ||||||||||
| 006 | MARA | Language Key | SPRAS | Text (CHAR) | 1 | - Mandatory for Migration Cockpit | Language Key | YES | YES | Text (CHAR) | 1 | S_MARA | SPRAS | ||||||||||
| 007 | MARA | Base Unit of Measure (ISO Format) | MEINS | Text (CHAR) | 3 | - Mandatory for Migration Cockpit | Base Unit of Measure (ISO Format) | YES | YES | Text (CHAR) | 3 | S_MARA | MEINS | ||||||||||
| 008 | MARA | Change Number | AENNR | Text (CHAR) | 6 | Change Number | Text (CHAR) | 6 | S_MARA | AENNR | |||||||||||||
| 009 | MARA | Revision Level | REVLV | Text (CHAR) | 2 | Revision Level | Text (CHAR) | 2 | S_MARA | REVLV | |||||||||||||
| 010 | MARA | GTIN | EAN11 | Text (CHAR) | 18 | GTIN | Text (CHAR) | 18 | S_MARA | EAN11 | |||||||||||||
| 011 | MARA | GTIN Category | NUMTP | Text (CHAR) | 1 | GTIN Category | Text (CHAR) | 1 | S_MARA | NUMTP | |||||||||||||
| 012 | MARA | Division | SPART | Text (CHAR) | 2 | Division | Text (CHAR) | 2 | S_MARA | SPART | |||||||||||||
| 013 | MARA | Old Material Number | BISMT | Text (CHAR) | 40 | Old Material Number | Text (CHAR) | 40 | S_MARA | BISMT | |||||||||||||
| 014 | MARA | Product Hierarchy | PRDHA | Text (CHAR) | 18 | Product Hierarchy | Text (CHAR) | 18 | S_MARA | PRDHA | |||||||||||||
| 015 | MARA | Batch Management Required Ind. | XCHPF | Text (CHAR) | 1 | Batch Management Required Ind. | Text (CHAR) | 1 | S_MARA | XCHPF | |||||||||||||
| 016 | MARA | Has Empties | MLGUT | Text (CHAR) | 1 | Has Empties | Text (CHAR) | 1 | S_MARA | MLGUT | |||||||||||||
| 017 | MARA | Valid From | DATAB | Date | Valid From | Date | S_MARA | DATAB | |||||||||||||||
| 018 | MARA | Deletion Date | LIQDT | Date | Deletion Date | Date | S_MARA | LIQDT | |||||||||||||||
| 019 | MARA | Industry Standard Description | NORMT | Text (CHAR) | 18 | Industry Standard Description | Text (CHAR) | 18 | S_MARA | NORMT | |||||||||||||
| 020 | MARA | Size/Dimensions | GROES | Text (CHAR) | 32 | Size/Dimensions | Text (CHAR) | 32 | S_MARA | GROES | |||||||||||||
| 021 | MARA | Laboratory / Design Office | LABOR | Text (CHAR) | 4 | Laboratory / Design Office | Text (CHAR) | 4 | S_MARA | LABOR | |||||||||||||
| 022 | MARA | External Product Group | EXTWG | Text (CHAR) | 18 | External Product Group | Text (CHAR) | 18 | S_MARA | EXTWG | |||||||||||||
| 022 | MARA | General Item Category Group | MTPOS_MARA | Text (CHAR) | 4 | General Item Category Group | Text (CHAR) | 4 | S_MARA | MTPOS_MARA | |||||||||||||
| 023 | MARA | Authorization Group | BEGRU | Text (CHAR) | 4 | Authorization Group | Text (CHAR) | 4 | S_MARA | BEGRU | |||||||||||||
| 024 | MARA | Cross-Plant Product Status | MSTAE | Text (CHAR) | 2 | Cross-Plant Product Status | Text (CHAR) | 2 | S_MARA | MSTAE | |||||||||||||
| 025 | MARA | Valid-From Date | MSTDE | Date | Valid-From Date | Date | S_MARA | MSTDE | |||||||||||||||
| 026 | MARA | Quality Manag. in Procurement Is Active | QMPUR | Text (CHAR) | 1 | Quality Manag. in Procurement Is Active | Text (CHAR) | 1 | S_MARA | QMPUR | |||||||||||||
| 027 | MARA | ANP Code | ANP | Number (NUMC) | 9 | ANP Code | Number (NUMC) | 9 | S_MARA | ANP | |||||||||||||
| 028 | MARA | Gross Weight | BRGEW | Number (NUMC) | 13,3 | Gross Weight | Number (NUMC) | 13,3 | 3 | S_MARA | BRGEW | ||||||||||||
| 029 | MARA | Net Weight | NTGEW | Number (NUMC) | 13,3 | Net Weight | Number (NUMC) | 13,3 | 3 | S_MARA | NTGEW | ||||||||||||
| 030 | MARA | Unit of Weight (ISO Format) | GEWEI | Text (CHAR) | 3 | Unit of Weight (ISO Format) | Text (CHAR) | 3 | S_MARA | GEWEI | |||||||||||||
| 031 | MARA | Length | LAENG | Number (NUMC) | 13,3 | Length | Number (NUMC) | 13,3 | 3 | S_MARA | LAENG | ||||||||||||
| 032 | MARA | Width | BREIT | Number (NUMC) | 13,3 | Width | Number (NUMC) | 13,3 | 3 | S_MARA | BREIT | ||||||||||||
| 033 | MARA | Height | HOEHE | Number (NUMC) | 13,3 | Height | Number (NUMC) | 13,3 | 3 | S_MARA | HOEHE | ||||||||||||
| 034 | MARA | Unit for Length/Width/Height(ISO Format) | MEABM | Text (CHAR) | 3 | Unit for Length/Width/Height(ISO Format) | Text (CHAR) | 3 | S_MARA | MEABM | |||||||||||||
| 035 | MARA | Volume | VOLUM | Number (NUMC) | 13,3 | Volume | Number (NUMC) | 13,3 | 3 | S_MARA | VOLUM | ||||||||||||
| 036 | MARA | Volume Unit | VOLEH | Text (CHAR) | 3 | Volume Unit | Text (CHAR) | 3 | S_MARA | VOLEH | |||||||||||||
| 037 | MARA | Capacity Usage | CAPAUSE | Number | 15 | Capacity Usage | Number | 15 | S_MARA | CAPAUSE | |||||||||||||
| 038 | MARA | Compliance Relevant | CHML_CMPLNC_RLVNCE_IND | Text (CHAR) | 1 | Compliance Relevant | Text (CHAR) | 1 | S_MARA | CHML_CMPLNC_RLVNCE_IND | |||||||||||||
| 039 | MARA | Product Is Configurable | KZKFG | Text (CHAR) | 1 | Product Is Configurable | Text (CHAR) | 1 | S_MARA | KZKFG | |||||||||||||
| 040 | MARA | Order Unit of Measure (ISO Format) | BSTME | Text (CHAR) | 3 | Order Unit of Measure (ISO Format) | Text (CHAR) | 3 | S_MARA | BSTME | |||||||||||||
| 041 | MARA | Purchasing Value Key | EKWSL | Text (CHAR) | 2 | Purchasing Value Key | Text (CHAR) | 2 | S_MARA | EKWSL | |||||||||||||
| 042 | MARA | State of Variable Purchase Order Unit | VABME | Text (CHAR) | 1 | State of Variable Purchase Order Unit | Text (CHAR) | 1 | S_MARA | VABME | |||||||||||||
| 043 | MARA | Internal Product Number | BMATN | Text (CHAR) | 18 | Internal Product Number | Text (CHAR) | 18 | S_MARA | BMATN | |||||||||||||
| 044 | MARA | Manufacturer Part Number | MFRPN | Text (CHAR) | 40 | Manufacturer Part Number | Text (CHAR) | 40 | S_MARA | MFRPN | |||||||||||||
| 045 | MARA | Manufacturer Number | MFRNR | Text (CHAR) | 10 | Manufacturer Number | Text (CHAR) | 10 | S_MARA | MFRNR | |||||||||||||
| 046 | MARA | Manufacturer Part Profile | MPROF | Text (CHAR) | 4 | Manufacturer Part Profile | Text (CHAR) | 4 | S_MARA | MPROF | |||||||||||||
| 047 | MARA | Transportation Group | TRAGR | Text (CHAR) | 4 | Transportation Group | Text (CHAR) | 4 | S_MARA | TRAGR | |||||||||||||
| 048 | MARA | Cross-Distribution Chain Product Status | MSTAV | Text (CHAR) | 2 | Cross-Distribution Chain Product Status | Text (CHAR) | 2 | S_MARA | MSTAV | |||||||||||||
| 049 | MARA | DG Indicator Profile | PROFL | Text (CHAR) | 3 | DG Indicator Profile | Text (CHAR) | 3 | S_MARA | PROFL | |||||||||||||
| 050 | MARA | Environmentally Relevant | KZUMW | Text (CHAR) | 1 | Environmentally Relevant | Text (CHAR) | 1 | S_MARA | KZUMW | |||||||||||||
| 051 | MARA | In Bulk/Liquid | ILOOS | Text (CHAR) | 1 | In Bulk/Liquid | Text (CHAR) | 1 | S_MARA | ILOOS | |||||||||||||
| 052 | MARA | Highly Viscous | IHIVI | Text (CHAR) | 1 | Highly Viscous | Text (CHAR) | 1 | S_MARA | IHIVI | |||||||||||||
| 053 | MARA | Valid From Date for Status | MSTDV | Date | Valid From Date for Status | Date | S_MARA | MSTDV | |||||||||||||||
| 054 | MARA | Material Category | ATTYP | Text (CHAR) | 2 | Material Category | Text (CHAR) | 2 | S_MARA | ATTYP | |||||||||||||
| 055 | MARA | Product Group: Packaging Materials | MAGRV | Text (CHAR) | 80 | Product Group: Packaging Materials | Text (CHAR) | 80 | S_MARA | MAGRV | |||||||||||||
| 056 | MARA | Packaging Product Type | VHIART | Text (CHAR) | 80 | Packaging Product Type | Text (CHAR) | 80 | S_MARA | VHIART | |||||||||||||
| 057 | MARA | Allowed Packaging Weight | ERGEW | Text (CHAR) | 13 | Allowed Packaging Weight | Text (CHAR) | 13 | S_MARA | ERGEW | |||||||||||||
| 058 | MARA | Unit of Allowed Packaging Weight | ERGEI | Text (CHAR) | 80 | Unit of Allowed Packaging Weight | Text (CHAR) | 80 | S_MARA | ERGEI | |||||||||||||
| 059 | MARA | Allowed Packaging Volume | ERVOL | Text (CHAR) | 13 | Allowed Packaging Volume | Text (CHAR) | 13 | S_MARA | ERVOL | |||||||||||||
| 060 | MARA | Unit of Allowed Packaging Volume | ERVOE | Text (CHAR) | 80 | Unit of Allowed Packaging Volume | Text (CHAR) | 80 | S_MARA | ERVOE | |||||||||||||
| 061 | MARA | Packaging Product Is Closed Packaging | KZGVH | Text (CHAR) | 1 | Packaging Product Is Closed Packaging | Text (CHAR) | 1 | S_MARA | KZGVH | |||||||||||||
| 062 | MARA | Excess Volume Tolerance for HU | VOLTO | Number | 3 | Excess Volume Tolerance for HU | Number | 3 | S_MARA | VOLTO | |||||||||||||
| 063 | MARA | Period Indicator for Shelf Life | IPRKZ | Text (CHAR) | 80 | Period Indicator for Shelf Life | Text (CHAR) | 80 | S_MARA | IPRKZ | |||||||||||||
| 064 | MARA | Storage Conditions | RAUBE | Text (CHAR) | 80 | Storage Conditions | Text (CHAR) | 80 | S_MARA | RAUBE | |||||||||||||
| 065 | MARA | Temperature Conditions Indicator | TEMPB | Text (CHAR) | 2 | Temperature Conditions Indicator | Text (CHAR) | 2 | S_MARA | TEMPB | |||||||||||||
| 066 | MARA | Hazardous Product Number | STOFF | Text (CHAR) | 40 | Hazardous Product Number | Text (CHAR) | 40 | S_MARA | STOFF | |||||||||||||
| 067 | MARA | Number of Goods Receipt/Issue Slips | WESCH | Number | 13 | Number of Goods Receipt/Issue Slips | Number | 13 | S_MARA | WESCH | |||||||||||||
| 068 | MARA | Indicator: Approved Batch Rec. Required | XGCHP | Text (CHAR) | 1 | Indicator: Approved Batch Rec. Required | Text (CHAR) | 1 | S_MARA | XGCHP | |||||||||||||
| 069 | MARA | Total Shelf Life | MHDHB | Number | 4 | Total Shelf Life | Number | 4 | S_MARA | MHDHB | |||||||||||||
| 070 | MARA | Minimum Remaining Shelf Life | MHDRZ | Number | 4 | Minimum Remaining Shelf Life | Number | 4 | S_MARA | MHDRZ | |||||||||||||
| 071 | MARA | Indi. for the Shelf Life Expiration Date | SLED_BBD | Text (CHAR) | 80 | Indi. for the Shelf Life Expiration Date | Text (CHAR) | 80 | S_MARA | SLED_BBD | |||||||||||||
| 072 | MARA | Storage Percentage | MHDLP | Number | 3 | Storage Percentage | Number | 3 | S_MARA | MHDLP | |||||||||||||
| 073 | MARA | Rounding Rule for Calculation of SLED | RDMHD | Text (CHAR) | 80 | Rounding Rule for Calculation of SLED | Text (CHAR) | 80 | S_MARA | RDMHD | |||||||||||||
| 074 | MARA | Serial Number Profile | SERIAL | Text (CHAR) | 80 | Serial Number Profile | Text (CHAR) | 80 | S_MARA | SERIAL | |||||||||||||
| 075 | MARA | Relevant for Hazardous Substances | HAZMAT | Text (CHAR) | 1 | Relevant for Hazardous Substances | Text (CHAR) | 1 | S_MARA | HAZMAT | |||||||||||||
| 076 | MARA | ABC Indicator | MAABC | Text (CHAR) | 1 | ABC Indicator | Text (CHAR) | 1 | S_MARA | MAABC | |||||||||||||
| 077 | MARA | Country/Region of Origin | HERKL | Text (CHAR) | 3 | Country/Region of Origin | Text (CHAR) | 3 | S_MARA | HERKL | |||||||||||||
| 078 | MARA | Purchasing Group | EKGRP | Text (CHAR) | 3 | Purchasing Group | Text (CHAR) | 3 | S_MARA | EKGRP | |||||||||||||
| 079 | MARA | Tax Classification | TAKLV | Text (CHAR) | 1 | Tax Classification | Text (CHAR) | 1 | S_MARA | TAKLV | |||||||||||||
| 80 | MARA | Loading Group | LADGR | Text (CHAR) | 4 | Loading Group | Text (CHAR) | 4 | S_MARA | LADGR | |||||||||||||
| 081 | MARA | Indicator: Quality | PSTATQ | Text (CHAR) | 1 | Indicator: Quality | Text (CHAR) | 1 | S_MARA | PSTATQ | |||||||||||||
| 082 | MARA | Indicator: Sales | PSTATV | Text (CHAR) | 1 | Indicator: Sales | Text (CHAR) | 1 | S_MARA | PSTATV | |||||||||||||
| 083 | MARA | Indicator: Storage | PSTATL | Text (CHAR) | 1 | Indicator: Storage | Text (CHAR) | 1 | S_MARA | PSTATL | |||||||||||||
| 084 | MARA | Indicator: Purchasing | PSTATE | Text (CHAR) | 1 | Indicator: Purchasing | Text (CHAR) | 1 | S_MARA | PSTATE | |||||||||||||
Material Master: Source ECC Service Master → Target S4H Material Master
| Source Field Information | Transformation/Business Rules | Target Field Information | |||||||||||||||||||||
| Sequence | Technical Source Table | Field Description | 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 |
| 001 | ASMD | Activity Number | ASNUM | Text (CHAR) | 18 | Default Value | <EMPTY> | - Mandatory for Migration Cockpit | Material Number | YES | YES | Text (CHAR) | 18 | S_MARA | MATNR | ||||||||
| 002 | ASMD | Material Group | MATKL | Text (CHAR) | 9 | Mapping Rule | If Source Field is empty do not send the data, ElseApply data conversion based on the MAPPING_FILE | - Mandatory for Migration Cockpit | Material Group | YES | YES | Text (CHAR) | 9 | S_MARA | MATKL | ||||||||
| 003 | ASMD | Base Unit of Measure | MEINS | UNIT | 3 | Mapping Rule | If the source field exists in the MAPPING_FILE, apply the corresponding data conversion and update the target field accordingly. | - Mandatory for Migration Cockpit | Base Unit of Measure (ISO Format) | YES | YES | Text (CHAR) | 3 | S_MARA | MEINS | ||||||||
| 004 | ASMD | Service Category | ASTYP | Text (CHAR) | 4 | ||||||||||||||||||
| 005 | ASMD | Package Number | PAKNR | NUMC | 10 | ||||||||||||||||||
| 006 | ASMD | International Article Number (EAN/UPC) | EAN11 | Text (CHAR) | 18 | Copy AS-IS | Update target field using the source field AS-IS | GTIN | Text (CHAR) | 18 | S_MARA | EAN11 | |||||||||||
| 007 | ASMD | Category of International Article Number (EAN) | NUMTP | Text (CHAR) | 2 | Copy AS-IS | Update target field using the source field AS-IS | GTIN Category | Text (CHAR) | 1 | S_MARA | NUMTP | |||||||||||
| 008 | ASMD | General Purchasing Status for Service | MSTAE | Text (CHAR) | 2 | Mapping Rule | If the source field exists in the MAPPING_FILE, apply the corresponding data conversion and update the target field accordingly. | Cross-Plant Product Status | Text (CHAR) | 2 | S_MARA | MSTAE | |||||||||||
| 009 | ASMD | Validity Date for “Purchasing” Status | MSTDE | DATS | 8 | Update 1:1 | Copy from source AS-IS | Valid-From Date | Date | S_MARA | MSTDE | ||||||||||||
| 010 | ASMD | Valuation Class | BKLAS | Text (CHAR) | 4 | S_MARA | |||||||||||||||||
| 011 | ASMD | Hierarchy Service Number | LSTHI | Text (CHAR) | 18 | S_MARA | |||||||||||||||||
| 012 | ASMD | Primary Language for Object Texts | MLANG | LANG | 1 | S_MARA | |||||||||||||||||
| 013 | ASMD | Numerator for Conversion of MEINS into IWEIN | IWUMZ | DEC | 5 | S_MARA | |||||||||||||||||
| 014 | ASMD | Denominator for Conversion (MEINS ↔ IWEIN) | IWUMN | DEC | 5 | S_MARA | |||||||||||||||||
| 015 | ASMD | Unit for Work | IWEIN | UNIT | 3 | S_MARA | |||||||||||||||||
| 016 | ASMD | Formula Number | FORMELNR | Text (CHAR) | 10 | S_MARA | |||||||||||||||||
| 017 | ASMD | Short Text Change Allowed | CHGTEXT | Text (CHAR) | 1 | S_MARA | |||||||||||||||||
| 018 | ASMD | Tax Tariff Code | TAXTARIFFCODE | Text (CHAR) | 16 | S_MARA | |||||||||||||||||
| 019 | ASMDT | Language | SPRAS | Text (CHAR) | 2 | YES | YES | S_MAKT | SPRAS | ||||||||||||||
| 020 | ASMDT | Description | ASKTX | Text (CHAR) | 40 | YES | YES | S_MAKT | MAKTX | ||||||||||||||
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 |
|---|---|---|---|---|---|
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
Summarize Data Privacy and Sensitivity Requirements, if anyExtraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; 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 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 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
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)
Service Master
20251028 |
| Field Name | Data Type | Length | Description | Rule |
| ASNUM | CHAR | 18 | Activity Number (Service master number) | |
| MATKL | CHAR | 9 | Material Group (for service) | |
| MEINS | UNIT | 3 | Base unit of measure | |
| ASTYP | CHAR | 4 | Service category | |
| PAKNR | NUMC | 10 | Package number (for service) | |
| EAN11 | CHAR | 18 | International Article Number (EAN/UPC) | |
| NUMTP | CHAR | 2 | Category of International Article Number (EAN) | |
| SPART | CHAR | 2 | Division | |
| BEGRU | CHAR | 4 | Authorization Group | |
| MSTAE | CHAR | 2 | General Purchasing Status for Service | |
| MSTDE | DATS | 8 | Validity date for “Purchasing” status | |
| BKLAS | CHAR | 4 | Valuation class | |
| LSTHI | CHAR | 18 | Hierarchy service number | |
| MLANG | LANG | 1 | Primary language for object texts | |
| LGART | CHAR | 4 | Wage Type | |
| LBNUM | CHAR | 3 | Short description of service type | |
| AUSGB | NUMC | 4 | Edition of service type | |
| STLVPOS | CHAR | 18 | Standard Service Catalog Item | |
| TAXIM | CHAR | 1 | Tax indicator for service (Purchasing) | |
| IWUMZ | DEC | 5 | Numerator for conversion of MEINS into IWEIN | |
| IWUMN | DEC | 5 | Denominator for conversion (MEINS <-> IWEIN) | |
| IWEIN | UNIT | 3 | Unit for Work | |
| FORMELNR | CHAR | 10 | Formula Number | |
| CHGTEXT | CHAR | 1 | Short Text Change Allowed | |
| TAXTARIFFCODE | CHAR | 16 | Tax tariff code (import processing) | |
| SPRAS | LANG | 1 | Language Key | |
| ASKTX | CHAR | 40 | Service Short Text | |
| KZLTX | CHAR | 1 | Indicator: long text exists (Yes = X) | |
| TXASP | CHAR | 1 | Primary-language indicator for text segment | |
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
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. | 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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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
Use the exact name and reference this section in the “Transformation rules” above| 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
The following pre-load validations will be performed by the 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:
|
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:
- 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
The load process encompasses all activities required to transfer transformed data into the target SAP S/4HANA system.
The process includes the following steps:
- Data Load Execution: Execute the automated data load into the target system using the approved load tool (e.g., Migration Cockpiti). If automation is not possible, perform a controlled manual upload using the provided load file,
- Loading Method and Sequence: Define and document the loading method (e.g., Direct Input, BAPI, IDoc, Web Service, or OData API) and ensure that the load sequence or dependency between related objects is clearly established,
- Error Handling: Include error-handling requirements, specifying alerting mechanisms and the expected corrective actions in case of load failures or inconsistencies.
Extraction/Transformation Methods and File Types
Data is extracted and transformed using Syniti ADM, and the staging area of Migration Cockpit staging area will be updated accordingly.
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 |
Loading Method
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 - Basic 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.