| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to upload Materials - Purchasing View into S/4 HANA as part of the Material Data Migration.
Link to MDS: DD-FUN-050 Master Data Standard_2020-Material master-Purchasing data
Conversion Scope
The scope of this document covers the approach for converting active Materials - Purchasing View from Legacy Source Systems into S/4HANA following the Materials Master Data Design Standard.
This object is migrated after Material Basic Data and Material General Plant, therefore only materials in scope for the object "2019 - Materials Basic Data View" and have Plants in scope as per the object "2010 - Materials - General Plant Data / S.Loc Data", are in scope for this object. Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules. Furthermore, as per the MDS for 2019, materials with specific Material Types will not be extended to the Purchasing View, while all other Material Types will be. Currently the Material Types not extended are IBAU and ZBAS, but this may change. Therefore this MDS must be reviewed for changes to this rule as part of the preparation of a Syniti ADMM Transform run.
The Service Master will be loaded as Materials in the Target. The relevancy rules for this are also covered in the object "2019 - Materials Basic Data View".
| Source | Scope | Source Approx. No. of Records | Target System | Target Approx. No. of Records |
|---|---|---|---|---|
| PF2, WP2 | Materials: The Material Master Records will be extracted that meet the relevancy criteria of Material Basic Data. Material Type will further refine this list to Materials relevant for the Purchasing View. Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria to be created as Materials and Material Type will further refine this list to records relevant for the Purchasing View. | Materials: Services: ** As per relevancy criteria | S4H | 207,315 ** ** This will change based on the Material Deduplication Process |
Predecessor Object
Material Master - Basic View (2019) → Materials - Additional data (2021) → Materials - General Plant Data / S.Loc Data (2010) → Materials Purchasing View (2020).
Additional Information
Multi-language Requirement
Not Applicable
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Field Description | Data Type | Length | Requirement | Updated in Predecessor Object | Updated in Another Object |
|---|---|---|---|---|---|---|---|
| MARC | MATNR | Material Number | CHAR | 18 | Required | 2010 | |
| MARC | WERKS | Plant | CHAR | 4 | Required | 2010 | |
| MARA | MEINS | Base Unit of Measure | UNIT | 3 | Required | 2019 | |
| MARA | BSTME | Order Unit | UNIT | 3 | Conditional | 2019 | |
| MARA | VABME | Variable Order Unit | CHAR | 1 | Conditional | 2019 | |
| MARA | MATKL | Material Group | CHAR | 9 | Required | 2019 | |
| MARC | EKGRP | Purchasing Group | CHAR | 3 | Conditional | ||
| MARC | MMSTA | Material Status (Plant-Specific) | CHAR | 2 | Conditional | 2005 | |
| MARC | MMSTD | Valid From | DATS | 8 | Conditional | 2005 | |
| MLAN | TAXIM | Tax Indicator for Material | CHAR | 1 | Required | ||
| MARC | MFRGR | Material Freight Group | CHAR | 4 | Conditional | ||
| MARC | KAUTB | Automatic PO allowed | CHAR | 1 | Required | ||
| MARC | KZKRI | Critical Part | CHAR | 1 | Conditional | ||
| MARA | MFRPN | Manufacturer Part Number | CHAR | 40 | Conditional | 2019 | |
| MARA | MFRNR | Manufacturer | CHAR | 10 | Conditional | 2019 | |
| MARC | HERKL | Country of Origin | CHAR | 3 | Conditional | ||
| MARC | WEBAZ | GR Processing Time | DEC | 3 | Conditional | 2005 |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System | Syniti Report Required |
|---|---|---|---|---|---|---|
| 1 | High | Purchasing Group Missing | If MARC-EKGRP is Blank and To-Be Material Type NOT IN ('IBAU','ZBAS') then include in the report. | MARA-MATNR, MARC-WERKS | PF2 & WP2 | YES |
| 2 | Medium | Country Of Origin Missing | if MARC-HERKL is Blank AND | MARA-MATNR, MARC-WERKS | PF2 & WP2 | YES |
| 3 | Medium | Validity Date Missing for Material Status (Plant-Specific) | If MARC-MMSTA contains a value and MARC-MMSTD is Blank then include in the report | MARA-MATNR, MARC-WERKS, MARC-MMSTA | PF2 & WP2 | YES |
| 4 | Medium | GR Processing Time Missing | If MARC-WEBAZ is Blank AND (To-Be Material Type = 'ZDIR' OR 'ZIND') then include in the report | MARA-MATNR, MARC-WERKS, MARA-MTART | PF2 & WP2 | YES |
Conversion Process
The high-level process for Materials, where the source is PF2 & WP2, is represented by the diagram below:
The high-level process for Services, where there is no source data, is represented by the diagram below:
Field Governance Rules | |||||
These governance rules apply to the individual fields within the data record. | |||||
Rule # | Field Label | Rule Description | Validation Method | Conditional Logic | Cleansing Rule (see above) |
1 | MARA-MATNR & MARC-WERKS | Only records where the material or service has been loaded into the Target, i.e. it is relevant. | Upfront Automated | Fields in the Material & Plant XREFs | |
2 | MARA-MTART | if To-Be Material Type = 'IBAU' or 'ZBAS' then DO NOT extend Material to Purchasing View | Field in the Material Type XREF | ||
3 | MARC-MMSTD | The field is only required to be maintained if the Plant Material Status (MARC-MMSTA) is applied to a material. | Upfront Automated | MARC-MMSTA is not Blank | Rule 3 |
4 | MARC-HERCL | This field is only applicable for Material types associated with Spares - ZIND, UNBW and NLAG and ZDIR direct materials for Brazil. | Upfront Automated | To-Be Material Type IN ('ZIND','UNBW','NLAG') OR | Rule 2 |
5 | MARC-WEBAZ | This is only applicable for ZDIR and ZIND materials, but this is not mandatory. | Ongoing Manual | To-Be Material Type = 'ZDIR' OR 'ZIND' | Rule 4 |
Data Privacy and Sensitivity
Not Applicable
Extraction
The source for Purchasing data for Materials is PF2 & WP2. This will be extracted by Syniti and the Relevancy criteria, as specified in object "2019 - Materials Basic Data View" and Material Type relevant to the Purchasing View, applied to identify the records that are applicable for the Target load.
There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from a DCT (see below in the DCT section for more details).
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
1 | Extract data from source system based on relevancy rule | Syniti |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Materials - Purchasing View data with exception of some fields which require transformation as mentioned in the transformation rule.
There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from the DCT specified below. It will be populated by Business for relevant services which they want to migrate.
Materials - Purchasing View DCT Rules
| Field Name | Field Description | Rule | Description |
|---|---|---|---|
| MARC-MATNR | Material Number | Read-only field | |
| MARC-WERKS | Plant | Exists in Plant XREF as a To-Be Plant | Organizational unit where material is maintained/used (e.g., manufacturing site, storage location). |
| MARA-MEINS | Base Unit of Measure | Read-only field provided for context | Unit of measure in which stocks of the material are managed. |
| MARA-BSTME | Order Unit | Read-only field provided for context | Specifies the unit of measure used when creating purchase orders for the material. |
| MARA-VABME | Variable Order Unit | Read-only field provided for context | Determines if you are allowed to use multiple or variable order units when creating Purchase Orders for the material. |
| MARA-MATKL | Material Group | Read-only field provided for context | Classification key grouping materials with similar characteristics for reporting/purchasing. |
| MARA-MFRPN | Manufacturer Part Number | Read-only field provided for context | General part number assigned by the manufacturer. |
| MARA-MFRNR | Manufacturer | Read-only field provided for context | Vendor or producer of the material. |
| MARC-EKGRP | Purchasing Group | Value in Check Table T024 | Buyer or group of buyers responsible for procurement activities of the material. |
| MARC-MMSTA | Material Status (Plant-Specific) | Value in Check Table T141 | Controls whether a material can be procured, produced, or sold in a plant. |
| MARC-MMSTD | Valid From | If MARC-MMSTA contains a value then MARC-MMSTD must have a value else Blank | Date from which the material status or conditions are effective. |
| MLAN-TAXIM | Tax Indicator for Material | Value in Check Table TMKM1 | Defines if material is taxable, non-taxable, or exempt for purchasing. |
| MARC-MFRGR | Material Freight Group | Value in Check Table TMFG | Groups materials for freight calculation and logistics handling. |
| MARC-KAUTB | Automatic PO allowed | X or Blank. Default X. | Allows automatic generation of POs from requisitions without manual intervention. |
| MARC-KZKRI | Critical Part | X or Blank Default Blank. | Used if we consider this Material a critical part from a planning perspective and/or we want it to be part of every inventory Count while running Cycle Counting. This indicator will be sent to Maestro/kinaxis as part of the Material Master Interface. |
| MARC-HERKL | Country of Origin | Value in Check Table T005 | Country where the manufacturer is located. |
| MARC-WEBAZ | GR Processing Time | Value >= 0 | Time (in days) between goods receipt and availability for use. |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Materials and Plants in scope to be loaded must be identified so that we can limit the extraction to this sub-set of data. | Syniti |
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 ADMM 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 ADMM.
- Prepare target-ready data in the structure and format that is required for loading via the 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 |
4 | Review the MDS for 2019 to check what Material Types must not be extended to the Purchasing View and update the rule if required | 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 & WG2 | MARC | MATNR | Material Number | S/4HANA | MARC | MATNR | Material Number | Map Source to Target using Material XREF |
2 | PF2 & WG2 | MARC | WERKS | Plant | S/4HANA | MARC | WERKS | Plant | Map Source to Target using Plant XREF |
PF2 & WG2 | MARC | EKGRP | Purchasing Group | S/4HANA | MARC | EKGRP | Purchasing Group | Map Source to Target using Purchasing Group XREF | |
PF2 & WG2 | MARC | MMSTA* | Material Status (Plant-Specific) | S/4HANA | MARC | MMSTA | Material Status (Plant-Specific) | Copy As-Is | |
PF2 & WG2 | MARC | MMSTD* | Valid From | S/4HANA | MARC | MMSTD | Valid From | If MARC-MMSTA contains a value then Copy As-Is else Blank | |
PF2 & WG2 | MLAN | TAXIM | Tax Indicator for Material | S/4HANA | MLAN | TAXIM | Tax Indicator for Material | Copy As-Is | |
PF2 & WG2 | MARC | MFRGR | Material Freight Group | S/4HANA | MARC | MFRGR | Material Freight Group | Copy As-Is | |
PF2 & WG2 | MARC | KAUTB | Automatic PO allowed | S/4HANA | MARC | KAUTB | Automatic PO allowed | Copy As-Is | |
PF2 & WG2 | MARC | KZKRI | Critical Part | S/4HANA | MARC | KZKRI | Critical Part | Copy As-Is | |
PF2 & WG2 | MARC | HERKL | Country of Origin | S/4HANA | MARC | HERKL | Manufacturer Country | Copy As-Is | |
PF2 & WG2 | MARC | WEBAZ** | GR Processing Time | S/4HANA | MARC | WEBAZ | GR processing time | Copy As-Is |
*MMSTA & MMSTD: These fields are also in the Conversion Spec for 2005, Material Master - MRP Views. Simran, from the S2P Functional Team, has confirmed that they are more relevant to Purchasing.
**WEBAZ: This field is also in the Conversion Spec for 2005, Material Master - MRP Views. ***
Transformation Mapping
Mapping Table Name | Mapping Table Description | Link |
|---|---|---|
Material | XREF | |
| Plant | XREF | Conversion Specification - Mappings |
| Purchasing Group | XREF | Conversion Specification - Mappings |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
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 |
| 5 | 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 the appropriate load tool.
- Once the data is loaded into 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
| Item # | Configuration Item |
|---|---|
| MM Config Values | |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1 | Material Master - Basic View (2019) |
| 2 | Materials - General Plant Data / S.Loc Data (2010) |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Data | Source Material not linked to a Target Material in the XREF | Fix incorrect data |
| Data | Source Plant not linked to a Target Plant in the XREF | Fix incorrect data |
| Data | Source Purchasing Group not linked to a Target Purchasing Group in the XREF | Fix incorrect data |
Data | Duplicates | Fix incorrect data |
Load | Authorization errors | Apply for the applicable authorization permission and retry |
Load | Technical load failures - If using MC - Simulation errors, etc | Investigate error and rectify. Retry simulation and/or load |
Config | Configuration is missing in the Target System | Missing config added in the Target System |
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 - Purchasing Data is in scope based on data design.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||