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)

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.

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.

Conversion Process

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

Data Privacy and Sensitivity

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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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