Purpose

The purpose of this document is to define the conversion approach for the object 2014 - Material Master Accounting View 2 in S4HANA.

The document details out the field list, extraction criteria, scoping, mapping, transformation logic, generation of the pre-load file and loading of the same with respect to the object 2014- Accounting View 2 of the Material Master.

The overall accounting views govern how a material is valuated financially within a specific valuation area (typically plant or company code). It directly influences inventory valuation, cost accounting, and integration with the General Ledger Accounting. 

The accounting 2 view of material master deals with two key aspects

- Additional material prices that need to be maintained for tax or commercial reasons
- LIFO/FIFO calculations

Key data/fields maintained in the Material Master- Accounting View 2 are as below:

Fields MBEW-BWPRS (Tax Price 1), MBEW-BWPS1 (Tax Price 2) and MBEW-VJBWS (Tax Price 3) deal with any country specific requirement for material valuations

Fields MBEW-BWPRH (Commercial price 1), MBEW-BWPH1 (Commercial price 2) and MBEW-VJBWH (Commercial price 3) deal with valuation based on commercial laws of some countries.

Fields MBEW-XLIFO (LIFO/FIFO relevant) and MBEW-MYPOL (LIFO/FIFO pool) are used if material valuation needs to be done LIFO/FIFO basis

The accounting view 2 is mainly optional maintenance and used only when there are specific requirements.

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

In SAP ECC, the Accounting View 2 is maintained for Materials which are mainly as below 

Reference: PF2 - where the total value is more than 0 and one of the Tax Prices or Commercial Prices have been maintained

Reference: WP2 - where the total value is more than 0 and one of the Tax Prices or Commercial Prices have been maintained

The target design in S4HANA for maintaining the Accounting View 2 is as below

• Tax Price 1 to 3 - Optional maintenance with no special or country requirements
• Commercial Price 1 to 3 - Optional maintenance with no special or country requirements
• LIFO/FIFO Valuation - No values being maintained 

The converted records for Material Master - Accounting View 2 will be loaded into the target S/4HANA system as overall load of Material Masters including different views, using standard SAP LTMC.

Conversion Scope

The scope of this document covers the conversion approach for the Object 2014 - Material Master Accounting View 2 from Legacy Source Systems into S/4HANA following the DD-FUN-050 Master Data Standard_2014-Materials Accounting 2

The data from legacy system includes:

1. Active Material Master that are in use (Production or Procurement) -Materials are relevant in table MARA (General Material Data) and MARC (Plant Data for Material)
2. The Materials must exit in table MBEW for Valuation Area (reference table T001K) or Company Code (Reference Table T001) in scope for conversion

List of source systems and approximate number of records

Note: the below numbers are from MBEW tables. The number can be lesser if the valuation areas not in scope is excluded.

Additional Information

Multi-language Requirement

Not applicable

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

So far there isn't any requirement for special handling / external system for the Tax Price 1 to 3 and Commercial Price 1 to 3. 

Target Design

The to be target design relevant for Accounting View 2 of the Material Master based upon the MDS "DD-FUN-050 Master Data Standard_2012-Materials Accounting 2" is as below:

The technical design of the target for this conversion approach.

Data Cleansing

For the purpose of the Object 2014 - Material Master Accounting View 2, the data cleansing should happen in the source systems PF2, WP2 as per below cleansing activity. The business cleansing is expected to be done by the business.

1. Data cleansing will be based on the relevancy as defined in Conv Spec 2010 (Materials - General Plant Data / S.Loc Data) and 2019 (Materials – Basic View).

Based upon the above rules for cleansing, the data will be extracted from source systems WP2, PF2 and will be checked in Syniti. The below checks to be done and reports to be generated.

For the object 2014 (Material Master - Accounting View 2, the same cleansing report applies as mentioned in the Conversion Specification for object 2012 - Material Master Accounting View 1.

Conversion Process

The generic high-level process steps for the conversion are as below:

1. Extraction:
   1. Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
   2. DCT: The DCT to be prepared if the data to be transformed and is part of the load file is not available in the Source system
2. Transform 
   1. Transform fields by applying the fields and value mapping in the Syniti 
   2. Generate and validate Pre-load files
3. Load
   1. Load the validated Pre-load file using SAP's LTMC using Material Valuation. 

However, with respect to object 2014- Material Master - Accounting View 2, the conversion process will depend upon the overall cutover/migration strategy of Material Master and its accounting view 1 and costing view 1`<To be finalised by Functional team>, in view of the mandatory Material Ledger activation in S4HANA. In view of the to be design for object 2014 Material Master Accounting view 2 being optional maintenance, the conversion process will be one to one where applicable.

Standard LTMCs for Material Master and Material Valuations to be used.

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 Syniti. 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 Syniti 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 Syniti This is to be conducted using DCT (Data Collection Template) in Syniti

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

Below selection parameters to apply for extraction from table MBEW from source systems WP2 and PF2.

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Object 2014 Material Master - Accounting View 2 data with exception of some fields which require transformation as mentioned in the transformation rule. (only for enrichment, as of now this is a provision for DCT)

2014 - Material Master 2 Accounting View 
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 Syniti 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
      
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 for extraction

Transformation Rules for DCT

Transformation Mapping

Below value mapping tables should be constructed in Syniti 

Transformation Dependencies

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team
Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. The load process includes:

   1. Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of Material Master and Material Valuation. 
   2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE) 

Load Template 

The LTMC template for Material Valuation

LTMC Template Material Valaution.xml

Load Run Sheet

Load Phase and Dependencies

The load phase for this object is ideally relevant for Pre-Cutover. TBC by S2P team

Configuration

Conversion Objects

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

Post-Load Validation

Project Team

Completeness

Accuracy

Business

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

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object 2014 is in scope based on data design and any exception requested by business.
• The load for this object will be performed along with/ as parr of overall Material Master Load 

See also

Change log