| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders |
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.
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
- 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, Z760, ZDLG, ZIRT will be excluded. Maintenance Assemblies are excluded (MTypes Z750, ZIBA).
- For Services we will include materials where MARA.MTYPE = 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.
- 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.
- 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') VBUK.VBTYP = C
- 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 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). 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.
- 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 = Z4, ZZ (PF2 system) Z0 (WP2 system) MARA.MSTAV = 51
- 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 PLIR (Planned Independent Requirements). Check table PBIM/PBED for materials PBIM.MATNR. Check PBIM.LOEVR ≠ 'D'. Check PBIM.WERKS for in scope Plants.
- 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.
| 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 |
| PF2,WP2 | Service master records currently reside in the ASMD table, totaling approximately 38,000 for PF2-020 and 900 for WP2. | 39,528 (PF2 38,644 and WP2 884) | S4H | 4,475 (PF2 4,171 and WP2 304) |
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
- 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.
Target Design
The technical design of the target for this conversion approach.
| Sequence | Table | Technical Field | Field Description | Field Format | Field Length | Requirement |
| 001 | MARA | MATNR | Material Number | Text (CHAR) | 18 | Required |
| 002 | MARA | MBRSH | Industry Sector | Text (CHAR) | 1 | Required |
| 003 | MARA | MAKTX | Description | Text (CHAR) | 40 | Required |
| 004 | MARA | SPRAS | Language Key | Text (CHAR) | 1 | Required |
| 005 | MARA | MTART | Material Type | Text (CHAR) | 4 | Required |
| 006 | MARA | MEINS | Base Unit of Measure (ISO Format) | Text (CHAR) | 3 | Required |
| 007 | MARA | MATKL | Material Group | Text (CHAR) | 9 | Required |
| 008 | MARA | BISMT | Old Material Number | Text (CHAR) | 40 | Required |
| 012 | MARA | SPART | Division | Text (CHAR) | 2 | Required |
| 013 | MARA | PRDHA | Product Hierarchy | Text (CHAR) | 18 | Conditional |
| 014 | MARA | MSTAE | Cross-Plant Product Status | Text (CHAR) | 2 | Conditional |
| 015 | MARA | MSTDE | Valid-From Date | Date | Conditional | |
| 017 | MARA | MTPOS_MARA | General Item Category Group | Text (CHAR) | 4 | Required |
| 019 | MARA | BRGEW | Gross Weight | Number (NUMC) | 13,3 | Conditional |
| 020 | MARA | NTGEW | Net Weight | Number (NUMC) | 13,3 | Conditional |
| 021 | MARA | GEWEI | Unit of Weight (ISO Format) | Text (CHAR) | 3 | Conditional |
| 022 | MARA | VOLUM | Volume | Number (NUMC) | 13,3 | Conditional |
| 023 | MARA | VOLEH | Volume Unit | Text (CHAR) | 3 | Conditional |
| 024 | MARA | GROES | Size/Dimensions | Text (CHAR) | 32 | Conditional |
| 025 | MARA | EAN11 | GTIN | Text (CHAR) | 18 | Conditional |
| 026 | MARA | NUMTP | GTIN Category | Text (CHAR) | 1 | Conditional |
| 027 | MARA | RMATP | Ref Material for Packaging | Text (CHAR) | 40 | Conditional |
| 028 | MARA | MAGRV | Material Group: Packaging Materials | Text (CHAR) | 4 | Conditional |
| 029 | MARA | NORMT | Industry Standard Description | Text (CHAR) | 18 | Conditional |
| 031 | MARA | WRKST | Basic Material | Text (CHAR) | 48 | Conditional |
| 034 | MARA | PROFL | DG Indicator Profile | Text (CHAR) | 3 | Conditional |
| 035 | MARA | KZUMW | Environmentally Relevant | Text (CHAR) | 1 | Conditional |
| 051 | MARA | ANP | ANP Code | Number (NUMC) | 9 | Conditional |
| 052 | MARA | /SAPAPO/MATGROUP-GRPTYPE | Product Group Type | Text (CHAR) | 2 | Conditional |
| 053 | MARA | /SAPAPO/MATGROUP-GROUPVALUE | Product Group | Text (CHAR) | 18 | Conditional |
Data Cleansing
| 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 | PF2/WP2 | ||
2019-003 | C1 | UoM alignment | All material UoMs to adhere to or be mapped to S4 ISO standard. | PF2/WP2 | |
2019-004 | C1 | Check Gross and Net Weights | Check for missing weights and that Gross Weight >= Net | PF2/WP2 | |
2019-005 | C1 | Duplicate materials | Check for materials with same Long/Short Description | PF2/WP2 | |
2019-006 | C1 | Material Types | Identify which material types can not have a one to one mapping for S4 due to multiple ECC materials either having incorrect type or cannot be identified correctly with current setup. Compile a list of materials/types in question, and work with the business to establish the correct mapping. | PF2/WP2 | |
2019-007 | C1 | Verify overlaps OR duplicated descriptions between ASMD/MARA | Verify for overlaps / duplications between: ASMDT-ASMD_TEXT (Service Master Description – EN) Compare records on the same system and cross system for English language | PF2/WP2 |
Conversion Process
The high-level process is represented by the diagram below:
The high level process for Classes that will be captured in a DCT are represented by the diagram below:
e
Data Privacy and Sensitivity
Not ApplicableExtraction
The source for Basic data for Materials is PF2 & WP2. This will be extracted by Syniti based on the Relevancy criteria.
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). | Syniti |
| 2 | Validate the extracted data volumes against ECC totals to ensure completeness before applying any filtering (count check per Material Type and per Plant). | Syniti |
| 3 | Apply exclusion criteria (e.g. deletion flags, obsolete status). | Syniti |
| 4 | Include recent transactional linkage (e.g., materials used in open PO, SO, or movements) within last 5 years for indirect/waste materials and 4 years for all others. | Syniti |
| 5 | Validate UoM conversions and ensure all Base Units (MEINS) exist in UoM ISO mapping table. | Syniti/Data Team |
| 6 | Generate Google Sheet report pre-populated with PF2 and WP2 extracted data for Business validation | Syniti/Data Team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Data Collection Template (DCT)
Materials & Service Master
| SAP Structure | SAP Field | Type | Length | Field Description | Importance | Long Description |
| MARA - General Material Master Data (client-level basic material data) | ||||||
| MARA | MATNR | CHAR | 18 | Material Number | mandatory for sheet | Material Number* A key that uniquely identifies the product. |
| MARA | MTART | CHAR | 4 | Material Type | mandatory for sheet | |
| MARA | MATKL | CHAR | 9 | Material Group | ||
| MARA | MBRSH | CHAR | 1 | Industry Sector | Industry Sector Key that specifies the branch of industry to which the product is assigned. Default to 'C' (Chemical Industry) | |
| MARA | MAKTX | CHAR | 40 | Material Description (Short Text) LANGUAGE EN | mandatory for sheet | Description* Text that describes the product in more detail. Note: You can maintain additional descriptions for languages other than those provided on the 'Basic Data' sheet. |
| MARA | SPRAS | LANG | 2 | Language Key | mandatory for sheet | Language Key* Please provide the language for the product description. |
| MARA | MEINS | UNIT | 3 | Base Unit of Measure | mandatory for sheet | Base Unit of Measure (ISO Format)* |
MARA | EAN11 | CHAR | 18 | International Article Number (EAN/UPC) | GTIN The GTIN on the Basic Data sheet always relates to the base unit of measure. Note: if you have additional GTIN's for this unit please enter them on the Additional GTIN sheet. The GTIN entered here is always the Main GTIN. With internal number assignment, you enter the GTIN category but not a GTIN. | |
| MARA | NUMTP | CHAR | 2 | Category of International Article Number | GTIN Category The EAN category defines the following attributes of the corresponding EAN: Type/method of number assignment (internal and/or external number assignment) and details as to whether alphanumerical EANs are allowed Check-digit algorithm that checks whether a check digit is required Prefix (for perishables EANs) Length of the EAN. | |
| MARA | SPART | CHAR | 2 | Division | Division A way of grouping products, or services. The system uses divisions to determine the sales areas and the business areas for a product, or service. Please maintain the division for all sales relevant products. | |
| MARA | BISMT | CHAR | 18 | Old Material Number | Old Material Number Number under which you have managed the product so far or still manage it, for example, in another system or in a card index. The maximum length of field Old Product Number is identical with the defined length for product numbers in your system. | |
| MARA | PRDHA | CHAR | 18 | Product Hierarchy | ||
| MARA | NORMT | CHAR | 18 | Industry Standard Description | Industry Standard Description Description of the product in accordance with the appropriate industry standard (such as ANSI or ISO). This field is purely for information. | |
| MARA | GROES | CHAR | 40 | Size/Dimensions | Size/Dimensions Text field that you can use as you like, for example, to record the size or dimensions of the product. The data you enter is merely for information and is not used by the system. | |
| MARA | MTPOS_MARA | CHAR | 4 | General Item Category Group | General Item Category Group Products grouping that helps the system to determine item categories during sales document processing. | |
| MARA | BEGRU | CHAR | 4 | Authorization Group | Authorization Group The authorization group enables you protect access to certain objects. | |
| MARA | MSTAE | CHAR | 2 | Cross-Plant Material Status | Cross-Plant Material Status The product status determines how a product is handled in different applications and in business operations (for example, purchasing, products planning, usage in bills of material ..). If a product has a product status, the system will issue either a warning or an error message (depending on which status you have chosen) if the product is used. Note: The cross-plant product status restricts the usability of the product for all plants. Please see further information in the migration object documentation under Mapping instructions. | |
| MARA | MSTDE | DATS | 8 | Date from Which the Material Status Is Valid | Valid-From Date Date from which the cross-plant product status is valid. | |
| MARA | ANP | NUMC | 9 | ANP Code (Brazil Localization) | ANP Code For Brazil only ! Identifies the products that are controlled by the Brazilian Oil Agency. | |
| MARA | BRGEW | QUAN | 15 | Gross Weight | Gross Weight Gross weight expressed in the unit of weight specified by you in the Unit of weight field. The system can use the gross weight at a later stage, depending on what kind of capacity check you run, to check storage bin capacity for warehouse management purposes. | |
| MARA | NTGEW | QUAN | 15 | Net Weight | Net Weight Net weight expressed in the unit of weight specified by you in the Unit of weight field. | |
| MARA | GEWEI | UNIT | 3 | Weight Unit | Unit of Weight (ISO Format) Unit referring to the gross weight or net weight of the product. If a product is created with sales data, the field unit of weight gets mandatory. Please provide an entry in this field or a default unit of weight is defined in product groups settings. | |
| MARA | VOLUM | QUAN | 15 | Volume | Volume Space that the product occupies per unit of volume. The volume refers to the unit specified in the "Volume unit" field. The volume and its unit always refer to the base unit of measure. | |
| MARA | VOLEH | UNIT | 3 | Volume Unit | Volume Unit If you specify a volume, you have to enter the corresponding volume unit here. | |
| MARA | MAGRV | CHAR | 4 | Material Group: Packaging Materials | Product Group: Packaging Materials Groups together products that require similar packaging products. | |
| MARA | WRKST | CHAR | 4 | Basic Material | Identifies the basic material grouping for cross-material analysis and logistics grouping. | |
| MARA | PROFL | CHAR | 3 | Dangerous Goods Indicator Profile | Classifies materials according to dangerous-goods regulations and drives checks during delivery, transport, and storage. | |
| MARA | KZUMW | CHAR | 1 | Environmentally Relevant | Marks materials subject to environmental handling requirements, including recycling and hazardous-disposal considerations. | |
| /SAPAPO/MATGROUP | GRPTYPE | CHAR | 2 | Product Group Type | Defines the type or category of the grouping in APO, affecting how the group behaves in planning. | |
| /SAPAPO/MATGROUP | GROUPVALUE | CHAR | 18 | Product Group | Stores the value of the product group, enabling APO classification and planning hierarchies (DP, SNP, PP/DS). | |
Extraction Dependencies
| 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 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
- 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 | 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 |
| 6 | Generate Load Files. | Syniti |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2/WQ2 | MARA/DCT | MATNR | Material Number | S/4HANA | MARA | MATNR | Material Number | Generate new Material number in Target System and maintain mapping in reference (XREF) table |
| 2 | PF2/WQ2 | MARA/DCT | MBRSH | Industry Sector | S/4HANA | MARA | MBRSH | Industry Sector | Industry - C - Chemical Industry (for Syensqo) |
| 3 | PF2/WQ2 | MARA/DCT | MTART | Material Type | S/4HANA | MARA | MTART | Material Type | Map from source to target using Material Type mapping table |
| 4 | PF2/WQ2 | MARA/DCT | MAKTX | Description | S/4HANA | MARA | MAKTX | Description | General Rule for short description, applicable to all material types except ZSER, VERP and Raw materials within ZDIR - Maximum number of 40 characters All capital letters Do not use double quotes (") to represent inches. If necessary, use two single quotes (') Use comma (,) or space to separate the words Do not include supplier specific information, they can be added to the Material PO text long description which will be printed on PO Include Material Description explaining the product details, size and packaging container ex: ALKAMULS BR 200 KG METAL DRUM Do not include Special characters in description. The Description field contains details used to define the item. This field is used as the internal product description and prints on purchase orders (but not sales orders) & is mandatory for all items. For Packaging materials, Material type - VERP Material group - 24110000 Containers, Short description rule - Packaging name + capacity + basic material (of pallet- Type of pallet : WOOD, STEEL or PE) + characteristics Material group - 24140000 Packing supplies , Short description rule - Packaging name + dimensions + capacity + specific characteristics (if exists) Material group - 55121600 Labels , Short description rule - Material + Packaging name + dimensions + product name For Raw Materials, Material type - ZDIR with combination of Purchasing category Purchasing category- Chemicals, Alcohols, Amines, Minerals, Metals, Steam and Industrial gases, Surfactants, Thickeners & Waxes and Oils Short description rule - chemical description+ concentration + weight + packaging type e.g. CARBON DIOXID 99% 25KG CYL Purchasing category - Fibers and Yarns, Mat group -11151512 Glass Fiber, Short description rule - Glass Style - Width (Metric + US) - Finish – ‘Glass Fabric’ - Line or Country(If needed) Mat group - 11151500 Other Fiber, Short description rules basis Fiber type- Carbon Style - Weight(gsm) - Width (Metric + US) - Fiber Type used - Tow - Twist - Line or Country(If needed) e.g. 8HS 372GSM 42IN T300 3K ST (FR) Aramid Style - Width (Metric + US) - Finish – ‘Aramid Fabric’ - Line or Country(If needed), e.g. 120 50IN CS-800 ARAMID FABRIC Astroquartz Style - Width (Metric + US) - Finish – ‘Astroquartz Fabric’ - Line or Country (If needed), e.g. 503 38IN A1100S ASTROQUARTZ FABRIC Purchasing category - Resins, Short description rule - Brand/Chemical name - Product – Form (If Required) - Country (If Required) - Weight - Pkg size, e.g. ARALDITE MY9663 WGT PK SIZE Purchasing category - Solvents, Short description rule - Brand/Chemical Name (Purity if required)- Weight - Pkg Size, e.g. ACETONE (99%) WGT PK SIZE For Service Materials, Mat type - ZSER Maximum number of 40 characters All capital letters Use comma (,) or space to separate the words Include Service description e.g. ‘Cleaning services’ |
| 5 | PF2/WQ2 | MARA/DCT | SPRAS | Language Key | S/4HANA | MARA | SPRAS | Language Key | Default language - English Alternative criteria for maintenance of text is to support regulatory with Syway Suppliers about the Purchase order text, thereby Supplier languages should also be maintained basis languages maintained in Business partner - Suppliers master data. |
| 6 | PF2/WQ2 | MARA/DCT | MEINS | Base Unit of Measure (ISO Format) | S/4HANA | MARA | MEINS | Base Unit of Measure (ISO Format) | |
| 7 | PF2/WQ2 | MARA/DCT | MATKL | Material Group | S/4HANA | MARA | MATKL | Material Group | |
| 8 | PF2/WQ2 | MARA/DCT | BISMT | Old Material Number | S/4HANA | MARA | BISMT | Old Material Number | For scenarios where 1 ECC material is merged to 1 S4 Material, Old Material No field needs to be populated with ECC material no. The BAAN no and description will be stored on classification. For scenarios where multiple ECC materials are merged into 1 S4 Material, Golden record should be identified and needs to be populated on the old material no field in this view. Other materials can be maintained in Old Material No characteristic on classification. |
| 9 | PF2/WQ2 | MARA/DCT | SPART | Division | S/4HANA | MARA | SPART | Division | Required to determine for which division the material will be created. This field is populated depending on the division configure in the system. The division value applicable is: 01-Product |
| 10 | PF2/WQ2 | MARA/DCT | PRDHA | Product Hierarchy | S/4HANA | MARA | PRDHA | Product Hierarchy | Select the product hierarchy relevant for the material. Each product hierarchy is made up of levels, with each level representing a more specific characteristic or grouping—like Category > Subcategory > Product Type. Only material with material type ZDIR will be relevant for Product Hierarchy. Field Value is determined from: |
| 11 | PF2/WQ2 | MARA/DCT | MTPOS_MARA | General Item Category Group | S/4HANA | MARA | MTPOS_MARA | General Item Category Group | Select the general item category group relevant for the material. |
| 12 | PF2/WQ2 | MARA/DCT | BRGEW | Gross Weight | S/4HANA | MARA | BRGEW | Gross Weight | Copy from source to target system |
| 13 | PF2/WQ2 | MARA/DCT | NTGEW | Net Weight | S/4HANA | MARA | NTGEW | Net Weight | Copy from source to target system |
| 14 | PF2/WQ2 | MARA/DCT | GEWEI | Unit of Weight (ISO Format) | S/4HANA | MARA | GEWEI | Unit of Weight (ISO Format) | Copy or map from source to target system in adherence to S4H ISO Data Standard |
| 15 | PF2/WQ2 | MARA/DCT | PROFL | DG Indicator Profile | S/4HANA | MARA | Compliance Relevant Indicator | Compliance Relevant Indicator to be set for materials/material groups related to chemicals. The Indicator is visible in the view within the Fiori App “Manage Product Master Data (ID: F1602)” under the Product Compliance tab in Manage Product Master. Additionally, you can refer to the backend table field MARA–CHML_CMPLNC_RLVNCE_IND, where the corresponding values are stored. | |
| 16 | PF2/WQ2 | MARA/DCT | KZUMW | Environmentally Relevant | S/4HANA | MARA | Compliance Relevant Indicator | Compliance Relevant Indicator to be set for materials/material groups related to chemicals. The Indicator is visible in the view within the Fiori App “Manage Product Master Data (ID: F1602)” under the Product Compliance tab in Manage Product Master. Additionally, you can refer to the backend table field MARA–CHML_CMPLNC_RLVNCE_IND, where the corresponding values are stored. |
Transformation Mapping
| Mapping Table Name | Mapping Table Description | Link |
|---|---|---|
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 | |
| BUoM | Mapping of Base Unit Of Measure |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | All Material Type mapping has been completed and mapping table in place | S2P Data Team |
2 | Data has been extracted from sources systems | Syniti |
3 | Deduplication is completed | Syniti & S2P Data Team |
4 | Configuration should be completed - (Config documents should be complete) | S2P Functional Team |
5 | Ensure DCT completeness | S2P Data Team |
| 6 | Value mapping and XREF tables are ready | Syniti & S2P Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Record Count | The number of records presented after relevancy checks and validation, as well as the number of records in the DCT, needs to be correct compared to the staged data in Syniti ADMM. |
Completeness check | All fields required as per mapping template rules must be completed. Syniti ADMM standard validity reports checking each field in Syniti must be built. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM standard reports.. |
Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
Completeness
| Task | Action |
|---|---|
Completeness Check | Business should compare legacy record counts, taking into account the reduction from the relevancy and deduplication processes, against the record count in the preload table. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business team to verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM reports/SAP reports. |
Load
The load process includes:
- Execute the automated data load into target system using 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 | 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
| Object # | Preceding Object Conversion Approach |
|---|---|
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Config | Configuration is missing in the Target System | Missing config to be added in the Target System |
Data | Duplicates | Fix incorrect data |
Post-Load Validation
Project Team
Post-Load Steps
Step Description | Team Responsible |
Execute post-load report | Syniti |
Post-load report verification/validation | Data Specialist/Functional/Data Owner - S2P |
Object load completion approval | Data Owner - S2P |
Completeness
| Task | Action |
|---|---|
Verify Count | The number of records presented in the post-load needs to be compared to the preload – Syniti report |
Field by field check | Compare source data staged in the preload tables to target data in the load tables. |
Accuracy
| Task | Action |
|---|---|
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.). |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | The number of records presented in the preload needs to be compared to the post-load Syniti report. |
Missing data | Check missing data which was supposed to be loaded. |
Reconciliation | Participate in Post-load walkthroughs. |
Field by field check | Perform random Field by Field checks by comparing source data staged in the preload tables to target data in the load tables. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the data in S/4 HANA was loaded correctly via Syniti post-load reports. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Materials - Basic Data is in scope based on data design and any exception requested by business.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||