Status

Page Status

Owner

CASTRO MONCAYO-ext, Jose Luis ULLAH-ext, Colin

Stakeholders

GERVAIS, Pascal NICASTRI-ext, Michele

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 CNV-2005 Material Master - MRP views (4Views) from Legacy Source Systems into S/4HANA following the DD-FUN- 050 Master Data Standard_2005-Materials - MRP views, Master Data Design Standard.

The data from legacy system includes:

Materials > 3 years active

Materials used in BOMS

Materials used in Recipes

The scope of this document covers the approach for converting active Material Master - MRP Views (4 Views) from Legacy Source Systems into S/4HANA following the Material Master - MRP Material Master - MRP Views (4 Views), Master Data Design Standard.
According with the new Relevancy agreement, materials should have the following rules:

Image Added

Materials used in Planning Process

The data from legacy system

excludes

includes:

All materials flagged for deletion
Any blocked or obsolete materials
Any inactive materials that are out of scope

List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget 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,0000S4 HANA600,000 After cleansing

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement

Use the logic for Data Relevancy for the CNV-2019 Material Master - Basic Views and for the Plant/Material Relevancy logic for the CNV-2010 Materials - General Plant Storage location views
All materials created in the previous 6 months will be included unless flagged for deletion
Material Types ZUNB, ZBOM, ZPRC and UNBW will be included regardless of activity (unless flagged for deletion)
We will only include materials that are extended to the following (excluding ZPRC material type as these do not require plant extension):
1. Company Codes in scope
2. Plants in scope
3. Purchasing Orgs in scope
4. Sales Orgs in scope
Include only Material Types in scope
We will include for migration all materials that have activity over the previous 3 years, to include:
1. For procurement data use EKKO/EKPO tables (remove any records in EKKO/EKPO where LOEKZ = 'X') and use EKPO/AEDAT for previous 4 years filter
2. For sales data use VBAK/VBAP tables
3. For production data use AFKO/AFPO tables
Additionally, we can check material movements using MKPF/MSEG tables (and Transaction Types: IB,ID,IZ,RS,SI,WA,WE,WF,WH,WI,WL,WO,WQ,WR,WS,WV,WZ)
We will include for migration all materials that have open documents including the following:
1. Open PO
2. Open contracts
3. Open STO
4. Open SO
5. Open WO
Have current stock/open inventory
1. For Open Inventory use the following tables:
  MARD
  MKOL (Consignment stock)
  MSKA (Sales Order stock)
  MSLB (Special stock)
  MSPR (Project stock)
We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
1. Open PO
2. Open contracts
3. Open STO
4. Open SO
5. Open WO
Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
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***'
If any of the rules here stated change, please follow the updated version of the Material Master Basic Views
To Include materials that condition MARC.PSTAT='D' has to be included
These are the materials referred as ZDIR & ZIND:

New MTART

Type

Definition

Includes

ZDIR

Custom

Direct Materials

All the direct materials for Syensqo
- Raw materials
- Semi Finished
- Finished materials
- Production Packaging (Including returnable packaging that is included in the BOM)
- Traded goods
- Production Resource/Tool
- By-Product

Z700

Z705

Z707

Z717

Z730

Z741

ZMAT

ZPRC

Z709

ZIND

Custom

In Direct Materials

Materials that are not an input/output to/from Production

Z735

Z9C4

Z9K4

ZB04

ZDBS

ZDET

ZDIN

ZDLG

ZG04

- Purchased

ZI04

ZIIG

ZJ04

ZK04

ZS04

ZU04

ZV04

ZERS

ZHIB

ZIPR

ZIRN

ZGEN

Z731

- Inventory Managed

- No Sales

- Can be included in maintenance BOM's

- Serialized materials for equipment

UNBW

STD

Materials with no value

Materials with stock but no value

UNBW

The data from legacy system excludes:

All materials flagged for deletion
Any blocked or obsolete materials
Any inactive materials that are out of scope

List of source systems and approximate number of records

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	MATNR	MATNR	Material Number	CHAR	18	R
T001W	WERKS	WERKS	Plant ID	CHAR	4	R
MARA	MEINS	MEINS	Unit of measure in which stock of the material is managed.	UNIT	3	R
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	MAABC	MAABC	Indicator that classifies a material as an A, B, or C part according to its consumption value.	CHAR	1	C
MARC	DISMM	DISMM	Key that determines whether and how the material is planned.	CHAR	2	R
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	MRP Controller	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	NU
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	NU
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	Automatic
MARC	BESKZ	BESKZ	Indicator that defines how the material is procured.	CHAR	1	R
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	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	NU
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	KZKUP	KZKUPMAT	The indicator determines 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	NU
MARC	PERIV	PERIV	The fiscal year variant is used to define the fiscal year.	CHAR	2	NU
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	NU
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	NU
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	NU
VBAP	VPWRK	VPWRK	Key which specifically identifies the plant from which the planned independent requirements of the reference material comes from	CHAR	4	NU
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	NU
MARA	MEINS	MEINS	Unit of measure in which stocks of the planning material are managed.	UNIT	3	NU
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	NU
MARC	STDPD	STDPD	Number uniquely identifying the configurable material	CHAR	18	NU
MARC	SBDKZ	SBDKZ	Indicator determining whether the individual or collective requirement is allowed for the dependent requirements of the material.	CHAR	1	C
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 indicator if a production version exists	CHAR	1	S
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	C
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	C
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	C
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	Table	field	Field Description	Report Required	Source System
02	MARC	DISPO	MRP Controller	Report to include all materials w/o MRP Controller	PF2 /WP2
03	MARC	MTVFP	Availability Check	Report with Materials without Availability check with Procurement Type E, F ; X	PF2 /WP2
04	MARC	DISGR	MRP GROUP	Report to bring materials not having MRP Group	PF2 /WP2
05	MARC	DISMM	MRP TYPE	Report to bring Blank field as MRP type	PF2 /WP2
07	MARC	PLIFZ	Planned Delivery Time (Calendar days)	Report to bring all materials with Procurement type F without Planned Delivery time	PF2 /WP2
09	MARC	BESKZ	Procurement Type	Procurement type= E(internal production), or F(external procurement). Blank =not allowed X =not allowed Report To show all Blank Procurement type	PF2 /WP2
19	MARC	DZEIT	In-house Production Time	if Procurement type = E Report to have all the E materials without this vlaue	PF2/WP2
20	MARC	WEBAZ	Goods Receipt Time	Procurement type E without this value	PF2/WP2

Conversion Process

The high-level process is represented by the diagram below:

Image Added

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:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. 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
4	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)	Data 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.

Materials- MRP views (4 Views) - DCT Rules

Field Name	Field Description	Rule
MARA	MATNR	Material Number
MARA	MEINS	Unit of measure in which stock of the material is managed.
MARC	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.
MARC	MAABC	Indicator that classifies a material as an A, B, or C part according to its consumption value.

MARC	DISMM	Key that determines whether and how the material is planned.
MARC	MINBE	If the stock falls below this quantity, the system flags the material for requirements planning.
MARC	LFRHY	Key that determines the day on which the material is planned and ordered.
MARC	DISPO	MRP Controller
MARC	DISLS	Key that determines which lot-sizing procedure the system uses within materials planning to calculate the quantity to be procured or produced.
MARC	BSTMI	Minimum procurement quantity.
MARC	BSTMA	Quantity that is not allowed to be exceeded during procurement.
MARC	MABST	Quantity of the material in this plant that may not be exceeded.
MARC	AUSSS	Percentage scrap that occurs during production of the material if the material is an assembly.
MARC	RDPRF	Key that the system uses to adjust the order proposal quantity to deliverable units.
MARC	BSTRF	Value to a multiple of which the system rounds up the procurement quantity.
MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material
MARC	BESKZ	Indicator that defines how the material is procured.
MARC	KZECH	Defines when batches have to be determined when using the PP/WM interface.
MARC	SOBSL	Allows the definition of the procurement type more exactly.
MARC	RGEKZ	Determines whether the backflush indicator is set in the production order.
MARC	LGFSB	Key of the storage location that is proposed in the purchase requisition in materials planning for subsequent storage of the material.
MARC	KZKUP	The indicator determines that the material is a co-product
MARC	SCHGT	The indicator defines the material as bulk
MARC	DZEIT	Specifies the time in workdays needed to produce the material in-house.
MARC	PLIFZ	Number of calendar days needed to obtain the material or service if it is procured externally.
MARC	WEBAZ	Number of workdays required after receiving the material for inspection and placement into storage.
MARC	MRPPP	Three-character number (numeric or using letters) that identifies a planning calendar in PPC (production planning and control).
MARC	EISBE	Specifies the quantity whose purpose is to satisfy unexpectedly high demand in the coverage period
MARC	LGRAD	Percentage specifying what proportion of the requirement is to be covered by the warehouse stock.
MARC	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.
MARC	EISLO	The quantity that defines the lower limit for safety stock. This value cannot be exceeded.
MARC	SHFLG	You use this indicator to switch on the safety time actual range of coverage for a material in MRP.
MARC	SHZET	In this field, you define the number of workdays for the safety time/actual range of coverage.
MARC	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.
MARC	MTVFP	Specifies whether and how the system checks availability and generates requirements for materials planning.
MARC	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.
MARC	KAUSF	Percentage of scrap that occurs during production of the material if the material is a component.
MARC	VERKZ	The system flags the inndicator if a production version exists
MARC	KZAUS	Identifies the material as a part to be discontinued and includes it in the discontinued parts procedure in materials planning.
MARC	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
MARC	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.
MARC	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
MARC	VINT1	Determines the consumption period (in workdays) for backward consumption.
MARC	VRMOD	The consumption mode controls the direction on the time axis in which requirements are consumed.
MARC	VINT2	Determines the consumption period (in workdays) for forward consumption.
MARC	SBDKZ	Indicator determining whether the individual or collective requirement is allowed for the dependent requirements of the material.
MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Data Profiling. MARC table Data Profiling needs to happen before the extraction of data.	Sinity
2	The extraction can commence only if the data cleansing is finished, having the acceptance on the Business.

ransformation

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.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. 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	Prepare Load files with the necessary rules and including the value mapping.	Sinity / MFG Team
2	Create the DCT file according to the Loading template in Sinity tool, else with the "Migrate your Data" tool in S4/HANA	Sinity / MFG Team
3	Validate the loading with the Business as per GBU reports	MFG Data Team
4

Transformation Rules

Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
ECC QF2/WP2	T001W	WERKS	Plant Number relevant for material / plant mapping	S4 HANA	T001W	WERKS	Plant Number relevant for material / plant mapping	Value Mapping for Plant (Enterprise Structure Book)
ECC QF2/WP2	MARA	MATNR	Material Number	S4 HANA	MARA	MATNR	Material <number	Value Mapping for Material / Plant
ECC QF2/WP2	MARA	MEINS	Unit of measure in which stock of the material is managed.	S4 HANA	MARA	MEINS	Unit of measure in which stock of the material is managed.	Copy from MARA = MATNR - MEINS
ECC QF2/WP2	MARC	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.	S4 HANA	MARC	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.	Copy from Legacy
ECC QF2/WP2	MARC	MAABC	Indicator that classifies a material as an A, B, or C part according to its consumption value.	S4 HANA	MARC	MAABC	Indicator that classifies a material as an A, B, or C part according to its consumption value.	- IF field MARC-DISMM = 'ND' Default Blank, Update value as Provided by Business (Value Mapping for Plant/Material/ABC Class - IF field MARC-DISMM = 'V1' the field has the value 'X' & "Y"
ECC QF2/WP2	MARC	DISMM	Key that determines whether and how the material is planned.	S4 HANA	MARC	DISMM	Key that determines whether and how the material is planned.	ZDIR: X0 ZIND: V1/PD - No rule as of now for PD. Copy from ECC UNBW: V1 PPDS view: X0 Rest: ND Format rules (length, case, data type, decimal, date format) Length - 2 Data Type - CHAR
ECC QF2/WP2	MARC	MINBE	If the stock falls below this quantity, the system flags the material for requirements planning.	S4 HANA	MARC	MINBE	If the stock falls below this quantity, the system flags the material for requirements planning.	Copy from ECC.
ECC QF2/WP2	MARC	LFRHY	Key that determines the day on which the material is planned and ordered.	S4 HANA	MARC	LFRHY	Key that determines the day on which the material is planned and ordered.	Copy from ECC.
ECC QF2/WP2	MARC	DISPO	MRP Controller	S4 HANA	MARC	DISPO	MRP Controller	Copy from ECC
ECC QF2/WP2	MARC	DISLS	Key that determines which lot-sizing procedure the system uses within materials planning to calculate the quantity to be procured or produced.	S4 HANA	MARC	DISLS	Key that determines which lot-sizing procedure the system uses within materials planning to calculate the quantity to be procured or produced.	Lot size will be maintained as EX (lot for lot order), FX (fixed lot size), H1. Copy form ECC Format rules (length, case, data type, decimal, date format) Length - 2 Data Type - CHAR Allowed values or reference (ECC, config tables, DCT) MARC/T439T Multi-language field requirements NA Comments or special handling notes The key is used to manage the time aggregation of the requirements when the MRP live creates the receipts elements
ECC QF2/WP2	MARC	BSTMI	Minimum procurement quantity.	S4 HANA	MARC	BSTMI	Minimum procurement quantity.	Copy from ECC (Business will clean on source)
ECC QF2/WP2	MARC	BSTMA	Quantity that is not allowed to be exceeded during procurement.	S4 HANA	MARC	BSTMA	Quantity that is not allowed to be exceeded during procurement.	Copy from ECC (Business will clean on source)
ECC QF2/WP2	MARC	MABST	Quantity of the material in this plant that may not be exceeded.	S4 HANA	MARC	MABST	Quantity of the material in this plant that may not be exceeded.	Copy from ECC (Business will clean on source)
ECC QF2/WP2	MARC	AUSSS	Percentage scrap that occurs during production of the material if the material is an assembly.	S4 HANA	MARC	AUSSS	Percentage scrap that occurs during production of the material if the material is an assembly.	Copy from ECC.
ECC QF2/WP2	MARC	BSTRF	Value to a multiple of which the system rounds up the procurement quantity.	S4 HANA	MARC	BSTRF	Value to a multiple of which the system rounds up the procurement quantity.	Copy from ECC.
ECC QF2/WP2	MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material	S4 HANA	MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material	System Generated
ECC QF2/WP2	MARC	BESKZ	Indicator that defines how the material is procured.	S4 HANA	MARC	BESKZ	Indicator that defines how the material is procured.	- Default 'E', Update value 'F' as Provided by Business - IF MARC-SOBSL(sp proc) = 30 (subcontract), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL(sp proc) = 45 (STO), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL(sp proc) = 20 (ext. proc.), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL(sp proc) = 10 (cons.), MARC-BESKZ (proc type) = 'F'
ECC QF2/WP2	MARC	KZECH	Defines when batches have to be determined when using the PP/WM interface.	S4 HANA	MARC	KZECH	Defines when batches have to be determined when using the PP/WM interface.	Copy from ECC Multi-language field requirements NA Comments or special handling notes NA
ECC QF2/WP2	MARC	SOBSL	Allows the definition of the procurement type more exactly.	S4 HANA	MARC	SOBSL	Allows the definition of the procurement type more exactly.	- Default Blank, Update value as this: - IF MARC-SOBSL(sp proc) = 30 (subcontract), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL (sp proc) = 45 (STO), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL (sp proc) = 20 (ext. proc.), MARC-BESKZ (proc type) = 'F' - IF MARC-SOBSL (sp proc) = 10 (cons.), MARC-BESKZ (proc type) = 'F'
ECC QF2/WP2	MARC	RGEKZ	Determines whether the backflush indicator is set in the production order.	S4 HANA	MARC	RGEKZ	Determines whether the backflush indicator is set in the production order.	Copy from ECC.
ECC QF2/WP2	MARC	LGFSB	Key of the storage location that is proposed in the purchase requisition in materials planning for subsequent storage of the material.	S4 HANA	MARC	LGFSB	Key of the storage location that is proposed in the purchase requisition in materials planning for subsequent storage of the material.	Default Blank. Update by Value mapping
ECC QF2/WP2	MARC	KZKUP	The indicator determines that the material is a co-product	S4 HANA	MARC	KZKUP	The indicator determines that the material is a co-product	Copy from ECC.
ECC QF2/WP2	MARC	SCHGT	The indicator defines the material as bulk	S4 HANA	MARC	SCHGT	The indicator defines the material as bulk	Copy from ECC.
ECC QF2/WP2	MARC	DZEIT	Specifies the time in workdays needed to produce the material in-house.	S4 HANA	MARC	DZEIT	Specifies the time in workdays needed to produce the material in-house.	Copy from ECC.
ECC QF2/WP2	MARC	PLIFZ	Number of calendar days needed to obtain the material or service if it is procured externally.	S4 HANA	MARC	PLIFZ	Number of calendar days needed to obtain the material or service if it is procured externally.	Copy from ECC.
ECC QF2/WP2	MARC	WEBAZ	Number of workdays required after receiving the material for inspection and placement into storage.	S4 HANA	MARC	WEBAZ	Number of workdays required after receiving the material for inspection and placement into storage.	Copy from ECC.
ECC QF2/WP2	MARC	MRPPP	Three-character number (numeric or using letters) that identifies a planning calendar in PPC (production planning and control).	S4 HANA	MARC	MRPPP	Three-character number (numeric or using letters) that identifies a planning calendar in PPC (production planning and control).	Copy from ECC
ECC QF2/WP2	MARC	EISBE	Specifies the quantity whose purpose is to satisfy unexpectedly high demand in the coverage period	S4 HANA	MARC	EISBE	Specifies the quantity whose purpose is to satisfy unexpectedly high demand in the coverage period	Copy from ECC.
ECC QF2/WP2	MARC	LGRAD	Percentage specifying what proportion of the requirement is to be covered by the warehouse stock.	S4 HANA	MARC	LGRAD	Percentage specifying what proportion of the requirement is to be covered by the warehouse stock.	Copy from ECC.
ECC QF2/WP2	MARC	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.	S4 HANA	MARC	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.	Copy from ECC.
ECC QF2/WP2	MARC	EISLO	The quantity that defines the lower limit for safety stock. This value cannot be exceeded.	S4 HANA	MARC	EISLO	The quantity that defines the lower limit for safety stock. This value cannot be exceeded.	Copy from ECC.
ECC QF2/WP2	MARC	SHFLG	You use this indicator to switch on the safety time actual range of coverage for a material in MRP.	S4 HANA	MARC	SHFLG	You use this indicator to switch on the safety time actual range of coverage for a material in MRP.	Copy from ECC.
ECC QF2/WP2	MARC	SHZET	In this field, you define the number of workdays for the safety time/actual range of coverage.	S4 HANA	MARC	SHZET	In this field, you define the number of workdays for the safety time/actual range of coverage.	Copy from ECC.
ECC QF2/WP2	MARC	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.	S4 HANA	MARC	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.	Copy from ECC.
ECC QF2/WP2	MARC	MTVFP	Specifies whether and how the system checks availability and generates requirements for materials planning.	S4 HANA	MARC	MTVFP	Specifies whether and how the system checks availability and generates requirements for materials planning.	Value Mapping from Old to new by Material / Plant
ECC QF2/WP2	MARC	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.	S4 HANA	MARC	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.	Copy from ECC.
ECC QF2/WP2	MARC	KAUSF	Percentage of scrap that occurs during production of the material if the material is a component.	S4 HANA	MARC	KAUSF	Percentage of scrap that occurs during production of the material if the material is a component.	Copy from ECC.
ECC QF2/WP2	MARC	VERKZ	The system flags the indicator if a production version exists	S4 HANA	MARC	VERKZ	The system flags the indicator if a production version exists	System Generated
ECC QF2/WP2	MARC	KZAUS	Identifies the material as a part to be discontinued and includes it in the discontinued parts procedure in materials planning.	S4 HANA	MARC	KZAUS	Identifies the material as a part to be discontinued and includes it in the discontinued parts procedure in materials planning.	Copy from ECC.
ECC QF2/WP2	MARC	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	S4 HANA	MARC	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	Copy from ECC.
ECC QF2/WP2	MARC	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.	S4 HANA	MARC	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.	Copy from ECC.
ECC PF2/WP2	MARC	STRGR	Planning Strategy Group	S4 HANA	MARC	STRGR	Planning Strategy Group	Strategy group 40 (Planning with final Assembly) will be used for spare parts in plants without storage capacity ZIND (non-stock materials). Rest copy from ECC
ECC PF2/WP2	MARC	SBDKZ	Indicator determining whether the individual or collective requirement is allowed for the dependent requirements of the material.	S4 HANA	MARC	SBDKZ	Indicator determining whether the individual or collective requirement is allowed for the dependent requirements of the material.	Collective indicator "2" will be used for spare parts. (ZIND)
ECC PF2/WP2	MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material	S4 HANA	MARC	DIBER	The indicator is set by the system when one MRP area is defined for the material	Copy from ECC
ECC PF2/WP2	MARC	VINT1	Bwd consumption per.	S4 HANA	MARC	VINT1	Determines the consumption period (in workdays) for backward consumption.	Copy from ECC
ECC PF2/WP2	MARC	VRMOD	Consumption mode	S4 HANA	MARC	VRMOD	The consumption mode controls the direction on the time axis in which requirements are consumed.	Copy from ECC
ECC PF2/WP2	MARC	VINT2	Fwd consumption per.	S4 HANA	MARC	VINT2	Determines the consumption period (in workdays) for forward consumption.	Copy from ECC

Transformation Mapping

Mapping Table Name	Mapping Table Description
MARA	MATERIAL NUMBER TABLE
MARC	PLANT MATERIAL TABLE

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Data Cleansing Reports must be done	Sinity
2	Data Cleansing has to be finished or to be at least at 80%	Business / Data Team
3	Data Transformation load files need to be validated by the business at GBU level	Business Data Owners
3	All Value mapping tables needs to be finished	Sinity/MFG Data Team
4	All Data dependencies has to be finished. Any delay can bring delays on this	All

Pre-Load Validation

Project Team

Completeness

Task

Action

Business Validates the load file

Send the Load file to the Business Representatives for all plants, so the can validate the data

Mock 1 test needs to happen before

1st Mock load (manual) can occur first and before the load can occur

Count before and after

Review the items as count before the load in the Transformation files and check it after

Validation reports

Google Drive Live Link

url	https://docs.google.com/spreadsheets/d/1hNY2Vk_q3VWNbZHsvoX1C4aHUpkpFndX0RLyKCOUTWs/edit?gid=1447265869#gid=1447265869

Accuracy

Task

Action

Count of actual records in MARC in PF2

Data Team to verify that all fields below meet pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length Checks

Count of actual records in MARC in WP2

Data Team to verify that all fields below meet pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length Checks

Record Errors

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
To check Data Accuracy checking count of records to load and loaded	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.
Count before and after	Review the items as count before the load in the Transformation files and check it after

Accuracy

Task	Action
Data owners to grant that the records in the load files are okay and according with the rules and mappings	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System01Material is not activeCheck Whether the material has deletion flag or not02Check for all material / Plant combinations that has Procurement E (in house Production) has a BOM/ Recipe03Check whether the material status has an un active statusMaterial Plant Status. Check material status at Material /Plant level and check materials to have active status04Check whether the Procurement type is empty or different from E,F,XProcurement Type (Check if Procurement type is correct /empty)

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

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:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. 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 DescriptionTeam Responsible

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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 NameField DescriptionRule

Extraction Dependencies

Item #Step DescriptionTeam 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.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic

Transformation Mapping

Mapping Table NameMapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

1	Go to load file and pick 5 data registers, load manually without any tool. See what happens. If all okay, proceed with the next step.	MFG Data Team
2	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	MFG Data Team
3	Proceed with the full load if steps one and two were succeed.	MFG Data Team
4	Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03	MFG Data Team
	Generate post load report if step 5 is validated	MFG Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1- Pre Cutover	Plant Planning Parameters
2- Pre Cutover	Plant & Storage location parameters
3 - Pre Cutover	Material Types configuration
4 - Pre Cutover	Valuation Class Configuration
5 - Pre Cutover	MRP Groups Configuration
6- Pre cutover	MRP Controllers Configuration
7- Pre Cutover	Availability check Configuration
8- Pre Cutover	Purchasing Groups Configuration

Item #Step DescriptionTeam Responsible

Pre-Load Validation

Project Team

Completeness

TaskAction

Accuracy

TaskAction

Business

Completeness

TaskAction

Accuracy

TaskAction

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 DescriptionTeam Responsible

Load Phase and Dependencies

Configuration

Configuration Item

Item #

Conversion Objects

Object #	Preceding Object Conversion Approach
2019	Materials - Basic View
2020	Materials - Purchasing View
2010	Materials - General Plant Data / S. Location Datalist 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


Check Data Records count	Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count)

Accuracy

Action

Task	Action
Check Data loading tool log	Check whether after the loading process, any logs from the tool, to verify them and take actions	Task

Business

Completeness

Task	Action
Check Data load register count	Download Post Load Reports from The Tool 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
Check Error log from the loading tool	Check whether after the loading process, any logs from the tool, to verify them and take actions

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.

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 15, 2026	Actor	Type	Activity	Version
Update in progress	NAVANDAR-ext, Divya	Comment	commented 9:46 am Transformed MRP type PD + ZIND = 40, rest all copy
Apr 14, 2026
	CASTRO MONCAYO-ext, Jose Luis	Edit	updated the page at 10:55 am
Apr 10, 2026
	CASTRO MONCAYO-ext, Jose Luis	State	changed state to Update in progress at 12:30 pm	v38
Lead Approval	CASTRO MONCAYO-ext, Jose Luis	Edit	updated the page at 12:30 pm Align the fields according with the rules
Apr 08, 2026
	MCARDLE-ext, Edward	State	changed expiry date to '15 Apr, 2026 10:54 am' at 10:54 am
	MCARDLE-ext, Edward	State	changed state to Lead Approval at 10:54 am	v37

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 3

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Additional Information

Multi-language Requirement

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

ransformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Run Sheet

Transformation Mapping

Transformation Dependencies

Configuration

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history