| 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, therefore only materials in scope for object "2019 - Materials Basic Data View" are in scope for this object. Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules.
The Service Master will be loaded as Materials in the Target, therefore only services that meet the same Relevancy rules as for Materials are in scope for this object.
| 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. Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria. | Materials: Services: ** As per relevancy criteria | S4H | 207,315 |
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 | Required by Material Type? |
|---|---|---|---|---|---|---|---|
| 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 | ||
| MARC | MMSTD | Valid From | DATS | 8 | Conditional | ||
| 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 | Manufacturer Country | CHAR | 3 | Conditional | ||
| MARC | WEBAZ | GR processing time | DEC | 3 | Conditional |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System | Syniti Report Required |
|---|---|---|---|---|---|---|
| 1 | High | Purchasing Group | Confirm all procured materials have Purchasing Data in place and confirm Purchasing Group mapping to S4 target value | *** How to tell if a mat is procured. Mat Status (MARC-MMSTA) = Procured | PF2/WP2 | |
| 2 | ? | PIR alignment | Check that procured materials have PIR in place | *** Is this the right place to do this or should it be done in PIR object or is it already being done in PIR object | PF2/WP2 | |
| 3 | Medium | Manufacturer Country is blank at Basic Data and Plant level | Both MARA-HERCL and MARC-HERKL are blank | MARA-MATNR, MAKT-MAKTX (where MAKT-SPRAS='E') *** Is this necessary? | ||
| 4 | ? | GR processing time | All material Purchasing data requirements to be confirmed | *** Is this necessary? If so, what is the required report? | PF2/WP2 |
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 | |
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", 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. The DCT will only contain Services that meet the same Relevancy as Materials.
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.Materials - Purchasing View DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| MARC-MATNR | Material Number | Read-only field |
| MARC-WERKS | Plant | Exists in Plant XREF as a To-Be Plant |
| MARA-MEINS | Base Unit of Measure | Read-only field provided for context |
| MARA-BSTME | Order Unit | Read-only field provided for context |
| MARA-VABME | Variable Order Unit | Read-only field provided for context |
| MARA-MATKL | Material Group | Read-only field provided for context |
| MARA-MFRPN | Manufacturer Part Number | Read-only field provided for context |
| MARA-MFRNR | Manufacturer | Read-only field provided for context |
| MARC-EKGRP | Purchasing Group | Value in Check Table T024 |
| MARC-MMSTA | Material Status (Plant-Specific) | Value in Check Table T141 |
| MARC-MMSTD | Valid From | In the date format applicable for SAP data type DATS |
| MLAN-TAXIM | Tax Indicator for Material | Value in Check Table TMKM1 |
| MARC - MFRGR | Material Freight Group | Value in Check Table TMFG |
| MARC-KAUTB | Automatic PO allowed | X or Blank |
| MARC-KZKRI | Critical Part | X or Blank |
| MARC-HERKL | Manufacturer Country | Value in Check Table T005 |
| MARC-WEBAZ | GR Processing Time | ? |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Materials and Services in scope to be loaded as Material Master Basic Data must be identified before the extraction of Class data, so that we can limit the extraction to this sub-set of data. | Cutover |
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 | 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 |
|---|---|---|---|---|---|---|---|---|---|
001 | PF2/WG2 | 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 |
002 | PF2/WG2 | S_MARC | WERKS | Plant | S/4HANA | S_MARC | WERKS | Plant | Map from source to target |
003 | PF2/WG2 | 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 Data Standard |
004 | PF2/WG2 | S_MARA | BSTME | Order Unit of Measure (ISO Format) | S/4HANA | S_MARA | BSTME | Order Unit of Measure (ISO Format) | Map from source to target in adherence to Data Standard |
005 | PF2/WG2 | S_MARA | VABME | State of Variable Purchase Order Unit | S/4HANA | S_MARA | VABME | State of Variable Purchase Order Unit | Copy from source to target system |
006 | PF2/WG2 | S_MARC | EKGRP | Purchasing Group | S/4HANA | S_MARC | EKGRP | Purchasing Group | Map from source to target using Purchasing Group mapping table |
007 | PF2/WG2 | S_MARA | MATKL | Material Group | S/4HANA | S_MARA | MATKL | Material Group | Map from source to target using Material Group mapping table |
008 | PF2/WG2 | S_MARC | MMSTA | Plant-Specific Material Status | S/4HANA | S_MARC | MMSTA | Plant-Specific Material Status | Copy from source to target system |
009 | PF2/WG2 | S_MARC | MMSTD | Valid From Date for Status | S/4HANA | S_MARC | MMSTD | Valid From Date for Status | Copy from source to target system |
010 | PF2/WG2 | S_MARC | TAXIM | Tax Indicator | S/4HANA | S_MARC | TAXIM | Tax Indicator | Copy from source to target system |
011 | PF2/WG2 | S_MARC | KAUTB | Automatic Purchase Oder Allowed | S/4HANA | S_MARC | KAUTB | Automatic Purchase Oder Allowed | Copy from source to target system |
012 | PF2/WG2 | S_MARC | XCHPF | Batch Management Req. Indicator | S/4HANA | S_MARC | XCHPF | Batch Management Req. Indicator | Copy from source to target system |
013 | PF2/WG2 | S_MARA | EKWSL | Purchasing Value Key | S/4HANA | S_MARA | EKWSL | Purchasing Value Key | Copy from source to target system |
014 | PF2/WG2 | S_MARC | WEBAZ | GR Processing Time | S/4HANA | S_MARC | WEBAZ | GR Processing Time | Copy from source to target system |
Transformation Mapping
Purchasing Group | Mapping of legacy Purchasing Groups to target system value |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure DCT tables completeness | SyWay S2P Data Team |
2 | Value Mappings are according to the latest design - <List of Value Mappings> | SyWay S2P Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Record Count | 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 | 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
Completeness
| Task | Action |
|---|---|
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Go to <Load Tool> | SyWay S2P Data Team |
2 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay S2P Data Team |
3 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay S2P Data Team |
4 | Proceed with full load if steps 2 and 3 are validated | SyWay S2P Data Team |
5 | Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03 | SyWay S2P Data Team |
6 | Generate post load report if step 5 is validated | SyWay S2P Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA. |
Accuracy
| Task | Action |
|---|---|
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.). |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Material data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Materials - Purchasing 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. | ||||