| 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 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. 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 relevancy rules for object "2016 Service Master record (Lean Services)" are in scope. Click here to so to the Conversion Spec for 2016 to see the full set of relevancy rules.
| 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
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.
Not Applicable
Target Design
With Functional input, document the technical design of the target fields that are in the scope of this document.
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
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 | Syniti Report Required |
|---|---|---|---|---|---|---|
| 1 | High | Purchasing Group | Field is Blank. | MARA-MATNR, MARC-WERKS | PF2 & WP2 | Is this required? |
| 2 | Medium | GR processing time | Field is Blank. | MARA-MATNR, MARC-WERKS | PF2 & WP2 | Is this required? |
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
Summarize Data Privacy and Sensitivity Requirements, if anyNot 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
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 |
|---|---|---|---|---|
| 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
List the steps that need to occur before extraction can commence
| 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 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 | Verify that data is extracted from both source systems. | Syniti / S2P Data Team |
2 | Obtain DCT Sign-off from Business. | S2P Data Team |
3 | Transformation jobs are ready for execution. | Syniti |
| 4 | Review and Validate Error and Preload Reports. | Syniti |
| 5 | 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 | Copy As-Is | |
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 | Manufacturer Country | 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 |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” aboveMapping Table Name | Mapping Table Description | Link |
|---|---|---|
Material | XREF | |
| Plant | XREF | MM Config Values - Plants |
| Purchasing Group | XREF | MM Config Values - Purchasing Group |
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) | Syniti & S2P Data Team |
4 | Ensure DCT tables completeness | S2P Data Team |
| 5 | Value mapping and XREF tables are ready | Syniti & 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 | The number of records presented after relevancy checks and validation needs to be correct compared to the staged data in Migrate. |
Completeness check | All fields required as per mapping template rules must be completed. Validity reports checking each field in Syniti must be built. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Data 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 DSP 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
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
Completeness Check | All fields required as per mapping template rules must be completed. Validity reports checking each field in ADMM must be built to help check. |
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the Source systems and the DCT are equal to the total number of records in the Preload and Load Sheets. |
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 |
8 | Execute pre-load report | Syniti |
9 | Validate preload report - release | Data Specialist/Functional - S2P |
10 | Prepare and simulate | Syniti |
11 | Pre-load verification and approval to load | Functional/Data Owner - S2P |
12 | Load to S4 | Syniti |
13 | Complete Jira steps, Volumes and Timings | All - where applicable |
14 | Execute post-load report | Syniti |
15 | Post-load report verification/validation | Data Specialist/Functional/Data Owner - S2P |
16 | Object load completion approval | Data Owner - S2P |
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 |
|---|---|
| Not Applicable | |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1 | Material Master - Basic View (2019) |
| 2 | Materials - General Plant Data / S.Loc Data (2010) |
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 |
|---|---|---|
| Data | Source Material not linked to a Target Material | Fix incorrect data |
| Data | Source Plant not linked to a Target Plant | 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 |
Post-Load Validation
Project Team
The following post-load validations will be performed by the 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 to target data. |
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 | 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. |
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/SAP 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 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.