Status
Owner	BAJAJ-ext, Manoj
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 for the object 2015 - Material Master Costing View 2
in S/4 HANA.

The Costing View 2 of the Material Master holds plant-specific costing parameters used in cost estimates, valuation, and financial planning. It complements Costing View 1 and is critical for materials with BOM/routing-based costing.

The key data maintained in the Costing View 2 of the Material Master is mainly the planned price and the date it is effective from for the relevant material. It is supplementary view and derives most of the information from the Costing View 1 of the Material Master. The fields for maintaining the Planned Prices are applicable dates are part of the table MBEW (Material Valuation)

 The Costing View 1 and 2 of the Material Master in S4HANA is similar to that of ECC which is defined by the table MBEW and MBEWH however below changes in S4HANA become important considerations for the conversion:

• The Table MBEW is still applicable but due to introduction of Universal Journal, the costing data is integrated 
• Material Ledger activation is mandatory in S4HANA even though actual costing for some Company Codes may not be applicable
• The planned prices as stored in MBEW will be dependent upon To Be design and accordingly picked up in the costing runs

In SAP ECC, the costing view 2 is maintained for Materials which are mainly as below 

(Reference: PF2 - Approx number of Materials - 4300 where the planned price is maintained)

• Material Ledger is active for the Valuation Area
• The Valuation Classes are as below:
  • Z000 - Main Raw Materials
  • Z050 - Other Raw Materials
  • Z051 - Packaging 
  • Z100 - Finished Goods Manufacturing
• The Costing View 2 is also maintained for some other valuation classes and also for materials where ML active indicator is blank. 
• Materials with blocked or marked for deletion status
  These cases will need to be validated and cleansed as part of the Master Data Services (MDS) process prior to migration.

(Reference: WP2 - Approx number of Materials - 30 where the planned price is maintained)

• Material Ledger is not active for the Valuation Area
• The Valuation Classes are as below:
  • Z100 - CS Raw Materials
  • Z110 - CS Packaging
  • Z130 - Trading Goods
  • Z150 - Finished Products

• Materials with blocked or marked for deletion status
  These cases will need to be validated and cleansed as part of the Master Data Services (MDS) process prior to migration.

The target design in S4HANA for maintaining the Planned Prices and effective dates as of now is relevant only for valuation classes pertaining to Raw Materials. <TBC>

The converted records will be loaded into the target S/4HANA system as overall load of Material Masters including different view, using standard SAP mechanisms such as BAPIs (e.g., BAPI_OBJCL_CREATE or BAPI_MATERIAL_SAVEDATA), IDOCs, or direct table loads where applicable, ensuring that all materials in scope have consistent and appropriate information related to Costing Views of the relevant Materials.

Conversion Scope

The scope of this document covers the approach for converting active the Object 2015 - Material Master Costing View 2 from Legacy Source Systems into S/4HANA following the Data Object 2015 Master Data Design Standard. The Planned Prices (Fields MBEW-ZPLP1 to MBEW-ZPLP3 and corresponding dates (Fields MBEW-ZPLD1 to MBEW-ZPLD3) as per the intended design <TBC> will be applicable for only valuation classes pertaining to Raw Materials (Type ROH)

The data from legacy system includes:

1. Active Material Master that are in use (Production or Procurement)
2. The Materials must exit in table MBEW for Valuation Area or Company Code in scope for conversion
3. Active Material Masters where one of the Planned Prices (Fields MBEW-ZPLP1 to MBEW-ZPLP3) is maintained
4. Materials are used in the Costing Runs or exit in a BOM used in Costing Sheet
5. The BOM must exist if the Material has "With Quantity Structure" (Field - MBEW-EKALR) indicator active

The data from legacy system excludes:

1. Materials which are not in use either for Production or for Procurement 
2. Materials belong to Plants or Company Codes which are not in scope for S4HANA 
3. Materials are not in use in Costing 
4. Materials for which neither of the Planned prices (Fields MBEW-ZPLP1 to MBEW-ZPLP3) are maintained
5. Materials for which there is no value available in "Total Value" (Field MBEW-SALK3)

List of source systems and approximate number of records

(Note: Target numbers expected to be lower after cleansing)

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Material Masters as per the above specified relevancy will be extracted from the MBEW table with the prerequisites as mentioned in the inclusion relevancy	4300	S4HANA	4300
WP2	Material Masters as per the above specified relevancy will be extracted from the MBEW table with the prerequisites as mentioned in the inclusion relevancy	40	S4HANA	30

Additional Information

Multi-language Requirement

Not applicable

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

No localization or specific requirements

No third-party system relevant for source 

Target Design

The target technical design based on the Master Data Standard for the object 2015 - Material Master Costing View 2 is as follows:

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MBEW	MATNR	MATNR	Material Number	CHAR	18	Required
MBEW	BWKEY	BWKEY	Valuation Area	CHAR	4	Required
MBEW	BWTAR	BWTAR	Valuation Type	CHAR	10	TBC
MBEW	ZPLP1	DZPLP1	Planned Price 1	CURR	13	Optional
MBEW	ZPLP2	DZPLP2	Planned Price 2	CURR	13	Optional
MBEW	ZPLP3	DZPLP3	Planned Price 3	CURR	13	Optional
MBEW	ZPLD1	DZPLD1	Planned Price 1 date	DATS	8	Optional
MBEW	ZPLD2	DZPLD2	Planned Price 2 date	DATS	8	Optional
MBEW	ZPLD3	DZPLD3	Planned Price 3 date	DATS	8	Optional

Data Cleansing

The data source will be from PF2 and WF2 systems for the active Company Codes and Plants in scope for S4HANA migration. The Data cleansing with respect to the object-2015, Material Master - Costing View 2, will be applicable only for those valuation classes which has a planned price maintained in one of the fields (MBEW-ZPLP1, MBEW-ZPLP2 or MBEW-ZPLP3) but is not intended as per To-be S4HANA design <TBC>

The data cleansing/relevancy check to be done in Synity based upon the To-be valuation classes relevant for Material Costing View 2.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
01	High	Check Material MATNR and Valuation Class	Valuation Classes not relevant for this view (to be maintained in the Syniti)	Show the Materials not relevant for CNV-2015	PF2 and WP2
02	High	Material is not valid	Check MATNR is available in MARA and MARC table	Show the erroneous	PF2 and WP2
03	High	Duplicate Records	Check MATNR across valuation areas (BWKEY)	Show the duplicate records	PF2 and WP2

Conversion Process

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

Data Privacy and Sensitivity

Not applicable except materials having export control.

Extraction

Extract data from a source into Syniti. There are 2 possibilities:

1. The data exists. Syniti connects to the source and loads the data into Synity. 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 Synity cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state).  The data is manually collected by the business directly in Synity This is to be conducted using DCT (Data Collection Template) in Synity

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
01	Extract from MBEW all MATNR (material masters) where MBEW-ZPLP1 or MBEW-ZPLP2 or MBEW-ZPLP3 is not equal to blank	Data Team
02	Extract from MBEW is by valuation area (BWKEY) in scope for migration	Data Team

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
SE16N Table MBEW	Material (MATNR)			Leave blank
SE16N Table MBEW	Valuation Area (BWKEY)	Multiple		Enter the legacy Valuation Areas (Plant)
SE16N Table MBEW	Planned Price 1 (ZPLP1)	Selective		"Select not equal"  Value to be entered: Blank
SE16N Table MBEW	Planned Price 2 (ZPLP2)	Selective	To be extracted after Extraction done for ZPLP1	"Select not equal"  Value to be entered: Blank
SE16N Table MBEW	Planned Price 3 (ZPLP2)	Selective	To be extracted after Extractions done for ZPLP1 and ZPLP2	"Select not equal"  Value to be entered: Blank

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

CNV 2015 - As the data is from the source systems PF2 and WP2 and will be transformed along with other views of the Material Master, the need for DCT as of now is not foreseen.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
01	Extract from MBEW as per the selection parameters mentioned in the selection screen section with the given sequence	Synity/Data team
02	For the Dress Rehearsals and Actual Cutover, the month end activities including the costing run in the PF2 and WP2 for the in-scope Plants/company code should be completed	Business Users

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:

1. 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 Syniti Migrate
2. 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
01	Prepare Load files with the necessary rules and including the value mapping.	Syniti / S2P Team
02	Validate the loading with the Business as per GBU reports	S2P, R2R Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
01	PF2/WP2	MBEW	MATNR	Material	S4HANA	MBEW	MATNR	Material	Value Mapping for Valuation Area/ Valuation Class
02	PF2/WP2	MBEW	BWKEY	Valuation Area	S4HANA	MBEW	BWKEY	Valuation Area	Value Mapping for Valuation Area/ Valuation Class
03	PF2/WP2	MBEW	BKLAS	Valuation Class	S4HANA	MBEW	BKLAS	Valuation Class	Value Mapping for Valuation Area/ Valuation Class
04	PF2/WP2	MBEW	B	Valuation Class

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
01	Valuation Area Changes: Mapping of Valuation Area (BWKEY) should exist	S2P Functional
02	Extraction for Data Transformation need to be validated by the business at GBU level	Business

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team

Completeness

Task	Action
Date Team Validates the Pre	specific details of what and how the task needs to be performed e.g. which reports are being used etc.
Business Validated the Pre

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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

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

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

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

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object 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.

Change log