| Status | Update in progress |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create 2005 - Material Master MRP views
in S/4 HANA.
Material Master - MRP Views are now used to make some of the Planning activities in both systems (PF2 & WP2). Most of the materials used in the planning process have these views updated, as they contain relevant information about the planning process. The aim is to get the conversion into S4 HANA in a standard way, so it can be used in the new planning processes already defined by the functional team and validated with the business.
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.
The data from legacy system may include:
- Uncleansed data or duplicated records
The data from legacy system excludes:
- All materials flagged for deletion
- Any blocked or obsolete materials
- Any inactive materials that are out of scope
Conversion Scope
The scope of this document covers the approach for converting active from Legacy Source Systems into S/4HANA following the Master Data Design Standard.
The data from legacy system includes:
- Materials > 3 years active
- Materials used in BOMS
- Materials used in Recipes
- Materials used in Planning Process
The data from legacy system excludes:
- All materials flagged for deletion
- Any blocked or obsolete materials
- Any inactive materials that are out of scope
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Material Master MRP views will be extracted from source systems. 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. | 750,0000 | S4 HANA | 600,000 After cleansing |
| WP2 | Material Master MRP views will be extracted from source systems. 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. | 500,000 | S4 HANA | 600,000 After cleansing For both systems |
Additional Information
Multi-language Requirement
Consider all languages in Scope for the Material Master (MAKT) system
Legal Requirement
N/A
Special Requirements
N/A
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MARA | MEINS | MEINS | Unit of measure in which stock of the material is managed. | UNIT | 3 | C |
| MARC | DISGR | DISGR | The MRP group contains all the materials from the point of view of MRP for assigning special control parameters for the total planning run. | CHAR | 4 | C |
| MARC | EKGRP | EKGRP | Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities. | CHAR | 3 | C |
| MARC | MAABC | MAABC | Indicator that classifies a material as an A, B, or C part according to its consumption value. | CHAR | 1 | C |
| MARC | MMSTA | MMSTA | Indicates whether, for a specific plant, the material may be used in specific areas. | CHAR | 2 | C |
| MARC | MMSTD | MMSTD | Date from Which the Plant-Specific Material Status Is Valid | DATS | 8 | C |
| MARC | DISMM | DISMM | Key that determines whether and how the material is planned. | CHAR | 2 | V1, V2, ND, X0 |
| MARC | MINBE | MINBE | If the stock falls below this quantity, the system flags the material for requirements planning. | QUAN | 13 | C |
| MARC | FXHOR | FXHOR | The planning time fence specifies a period within which no automatic changes are to be made to the master plan. | NUMC | 3 | NU |
| MARC | LFRHY | LFRHY | Key that determines the day on which the material is planned and ordered. | CHAR | 3 | NU |
| MARC | DISPO | DISPO | Material planning classification. | CHAR | 3 | C |
| MARC | DISLS | DISLS | Key that determines which lot-sizing procedure the system uses within materials planning to calculate the quantity to be procured or produced. | CHAR | 2 | C |
| MARC | BSTMI | BSTMI | Minimum procurement quantity. | QUAN | 13 | C |
| MARC | BSTMA | BSTMA | Quantity that is not allowed to be exceeded during procurement. | QUAN | 13 | C |
| MARC | MABST | MABST | Quantity of the material in this plant that may not be exceeded. | QUAN | 13 | C |
| MARC | TAKZT | TAKZT | The system uses the takt time if a requirement is covered by several receipt elements due to restrictions on lot size such as maximum lot size (with all lot-sizing procedures) or rounding value (with fixed lot size with splitting). | DEC | 3 | C |
| MARC | AUSSS | AUSSS | Percentage scrap that occurs during production of the material if the material is an assembly. | DEC | 5 | C |
| MARC | RDPRF | RDPRF | Key that the system uses to adjust the order proposal quantity to deliverable units. | CHAR | 4 | C |
| MARC | BSTRF | BSTRF | Value to a multiple of which the system rounds up the procurement quantity. | QUAN | 13 | C |
| MARC | DIBER | DIBER | The indicator is set by the system when one MRP area is defined for the material | CHAR | 1 | C |
| MARC | BESKZ | BESKZ | Indicator that defines how the material is procured. | CHAR | 1 | C |
| MARC | KZECH | KZECH | Defines when batches have to be determined when using the PP/WM interface. | CHAR | 1 | C |
| MARC | SOBSL | SOBSL | Allows the definition of the procurement type more exactly. | CHAR | 2 | C |
| MARC | LGPRO | LGPRO | In the case of a material produced in-house, this is the key of the storage location that is copied to the planned order, production order, or run schedule quantity. | CHAR | 4 | C |
| MARC | RGEKZ | RGEKM | Determines whether the backflush indicator is set in the production order. | CHAR | 1 | C |
| MARC | VSPVB | VSPVB | The supply area is used as an interim storage area on the shop floor which is used to provide materials directly at the production line. | CHAR | 10 | C |
| MARC | FABKZ | FABKZ | Determines whether it is possible to generate JIT delivery schedules in addition to forecast schedules for a material specified in a purchase scheduling agreement. | CHAR | 1 | NU |
| MARC | LGFSB | LGFSB | Key of the storage location that is proposed in the purchase requisition in materials planning for subsequent storage of the material. | CHAR | 4 | C |
| MARC | EPRIO | BF_GROUP | A key for the stock determination strategy. | CHAR | 4 | C |
| MARC | KZKUP | KZKUPMAT | The indicator detemines that the material is a co-product | CHAR | 1 | C |
| MARC | SCHGT | SCHGT | The indicator defines the material as bulk | CHAR | 1 | C |
| MARC | DZEIT | DZEIT | Specifies the time in workdays needed to produce the material in-house. | DEC | 3 | C |
| MARC | PLIFZ | PLIFZ | Number of calendar days needed to obtain the material or service if it is procured externally. | DEC | 3 | C |
| MARC | WEBAZ | WEBAZ | Number of workdays required after receiving the material for inspection and placement into storage. | DEC | 3 | C |
| MARC | MRPPP | MRPPP | Three-character number (numeric or using letters) that identifies a planning calendar in PPC (production planning and control). | CHAR | 3 | C |
| MARC | FHORI | FHORI | Key that the system uses to determine the floats required for scheduling an order. You define the following floats with the scheduling margin key | CHAR | 3 | NU |
| MARC | EISBE | EISBE | Specifies the quantity whose purpose is to satisfy unexpectedly high demand in the coverage period | QUAN | 13 | C |
| MARC | LGRAD | LGRAD | Percentage specifying what proportion of the requirement is to be covered by the warehouse stock. | DEC | 3 | C |
| MARC | RWPRO | RWPRO | The range of coverage profile contains the parameters for calculating the dynamic safety stock. This is a statistical calculation on the basis of average daily requirements. | CHAR | 3 | C |
| MARC | EISLO | EISLO | The quantity that defines the lower limit for safety stock. This value cannot be exceeded. | QUAN | 13 | C |
| MARC | SHFLG | SHFLG | You use this indicator to switch on the safety time actual range of coverage for a material in MRP. | CHAR | 1 | C |
| MARC | SHZET | SHZET | In this field, you define the number of workdays for the safety time/actual range of coverage. | NUMC | 2 | C |
| MARC | SHPRO | SHPRO | he period profile for the safety time / actual range of coverage contains the periods (stating to/from date) with the safety time/actual range of coverage that is valid for each period. | CHAR | 3 | C |
| MARC | PERKZ | PERKZ | Indicator specifying the periods in which the material's consumption values and forecast values are managed. | CHAR | 1 | C |
| MARC | PERIV | PERIV | The fiscal year variant is used to define the fiscal year. | CHAR | 2 | C |
| MARC | AUFTL | AUFTL | Indicator that defines how the system splits forecast requirements into smaller time intervals where the MRP type is forecast-based planning and the period indicator is not "day". | CHAR | 1 | C |
| MARC | STRGR | STRGR | The strategy group groups all the planning strategies that can be used for a particular material. The planning strategy represents the procedure used for planning a material and is (technically speaking) controlled by the MRP types | CHAR | 2 | C |
| MARC | VINT1 | VINT1 | Determines the consumption period (in workdays) for backward consumption. | NUMC | 3 | C |
| MARC | VRMOD | VRMOD | The consumption mode controls the direction on the time axis in which requirements are consumed. | CHAR | 1 | C |
| MARC | VINT2 | VINT2 | Determines the consumption period (in workdays) for forward consumption. | NUMC | 3 | C |
| MARC | MISKZ | MISKZ | Defines whether the material is available for Subassembly planning with final assembly, gross requirement planning, subassembly planning without final assembly | CHAR | 1 | C |
| VBAP | VPMAT | VPMAT | Material number whose planned independent requirements the system uses to consume the sales order of the material in question if you use the planning strategy, "planning with planning material". | CHAR | 18 | C |
| VBAP | VPWRK | VPWRK | Key which specifically identifies the plant from which the planned independent requirements of the reference material comes from | CHAR | 4 | C |
| MDIP | VPREF | VPREF | Factor that the system uses to convert the quantity of the current material, measured in the base unit of measure, to the base unit quantity of the planning material. | CHAR | 6 | C |
| MARA | MEINS | MEINS | Unit of measure in which stocks of the planning material are managed. | UNIT | 3 | C |
| MARC | MTVFP | MTVFP | Specifies whether and how the system checks availability and generates requirements for materials planning. | CHAR | 2 | C |
| MARC | WZEIT | WZEIT | The total replenishment lead time is the time needed before the product is completely available again, that is, after all BOM levels have been procured or produced. It is not calculated by the system, but defined in this field as the total of the in-house production time(s) and/or the planned delivery time(s) of the longest production path. | DEC | 3 | C |
| MARC | KZPSP | KZPSP | The indicator determines if the system takes all stock and MRP-relevant units (inward/outward movement) in the project stock segments for all documents without account assignment into consideration. | CHAR | 1 | C |
| MARC | STDPD | STDPD | Number uniquely identifying the configurable material | CHAR | 18 | C |
| MARC | SBDKZ | SBDKZ | Indicator determining whether the individual or collective requirement is allowed for the dependent requirements of the material. | CHAR | 1 | NU |
| MARC | KAUSF | KAUSF | Percentage of scrap that occurs during production of the material if the material is a component. | DEC | 5 | C |
| MARC | VERKZ | CK_VERK1 | The system flags the inndicator if a production version exists | CHAR | 1 | C |
| MARC | KZBED | KZBED | Defines whether the system groups together dependent requirements for the material on a daily basis when analyzing requirements planning. | CHAR | 1 | NU |
| MARC | AHDIS | AHDIS | This indicator controls whether dependent requirements are relevant to MRP or not. Dependent requirements include dependent reservations and stock transfer requirements. | CHAR | 1 | NU |
| MARC | KZAUS | KZAUS | Identifies the material as a part to be discontinued and includes it in the discontinued parts procedure in materials planning. | CHAR | 1 | NU |
| MARC | AUSDT | AUSDT | Date from which the stocks of the material are to be used up. As soon as no more stock exists for this material, it is to be replaced by the follow-up material | DATS | 8 | NU |
| MARC | NFMAT | NFMAT | Number of the material that the system uses in materials planning to replace the material to be discontinued once its warehouse stock is depleted. | CHAR | 18 | NU |
| MARC | SAUFT | SA_SAUFT | Authorizes the material for repetitive manufacturing. | CHAR | 1 | NU |
| MARC | SFEPR | SFEPR | Controls, via order type, whether you are working with make-to-order repetitive manufacturing, based on sales orders, or with make-to-stock repetitive manufacturing, based on no specific orders | CHAR | 4 | NU |
| MARC | MDACH | MDACH | This key is used for the function "Actions in the planned order" and defines the sequence of the actions that can be carried out for the planned order. | CHAR | 2 | NU |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 01 | 2005-01 | Active Materials | According to the Material definition and the material/Plant mapping, only active materials for the last 3 years are going to be migrated | Only active materials will be migrated | PF2 /WP2 |
| 02 | 2005-02 | Material UOM | Check The new/ migrated UOM matches with the material Change Issue UOM in Work Scheduling View to match with Basic UOM /alternative UOM | Materials already maintained with the appropriate UOM | PF2 /WP2 |
| 03 | 2005-03 | MRP Type Please check whether the materials has ND | Delete materials with NO procurement type, else ask the business to complete | No materials with ND MRP type has to be migrated | PF2 /WP2 |
| 04 | 2005-04 | Material Lot Sizing Procedure | Change/ Update Lot Size accordingly | Lot size updated accordingly | PF2 /WP2 |
| 05 | 2005-05 | Procurement Type (Check if Procurement type is correct /empty) | Delete materials with NO procurement type, else ask the business to complete | Procurement type updated accordingly to all materials to be migrated | PF2 /WP2 |
| 06 | 2005-06 | MRP Controllers | Change/ Update MRP Controller as per the logic. For materials W/O Values, Check if material is valid or not, then update | MRP Controllers are updated for all materials | PF2 /WP2 |
| 07 | 2005-07 | GR Processing Time | Change / Update GR Processing Time, according to the logic for each material. For materials w/o values, update accordingly | GR Processing time is updated according to the Governance rules | PF2 /WP2 |
| 08 | 2005-08 | Availability Check Rule | Check Availability Check Rule in MRP 3 view. Check the logic and select the right one. For materials with KP Check rule, check validity, else change | Availability Check Rule must be checked in order to comply with the business rules and for all materials to be migrated | PF2 /WP2 |
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
E
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in
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 data from source system based on relevancy rule | SyWay Data Team |
2 | Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. | SyWay Data Team |
| 3 | Sinity will extract data and convert it into SQL data base ad share with the team | Sinity team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| 1 | Material Number | Rule must follow the Material / Plant combination as a result of the new Plant/Material Mapping for the S4 HANA system |
| 2 | Unit of measure | Materials need to be transformed with the updated Unit of Measure as a result of the transformation given. |
| 3 | MRP Type Please check whether the materials has ND | Transform the old values in the field for MRP type into de new one |
| 4 | Material Lot Sizing Procedure | Transform the existing Lot sizing procedure according with the new template value |
| 5 | Procurement Type | Check the rule for converting F/E/X materials |
| 6 | MRP Controllers | |
| 7 | GR Processing Time | |
| 8 | Availability Check Rule |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
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 |
|---|---|---|
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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 |
|---|---|---|
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 |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- 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. | ||||