Status
Owner	BAJAJ-ext, Manoj
Stakeholders	PILLAY-ext, Lawrence GARCIA-ext, Angel Luis KUMAR-ext, Rajib

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

Index	Remarks	Number of Records
1	Number of records with Tax Price 1	2
2	Number of records with Tax Price 2	10671
3	Number of records with Tax Price 3	1
4	Number of records with Commercial Price 1	11
5	Number of records with Commercial Price 2	0
6	Number of records with Commercial Price 3	4
7	Number of records with LIFO indicator	6535

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

Index	Remarks	Number of Records
1	Number of records with Tax Price 1	12429
2	Number of records with Tax Price 2	14103
3	Number of records with Tax Price 3	717
4	Number of records with Commercial Price 1	655
5	Number of records with Commercial Price 2	22
6	Number of records with Commercial Price 3	15
7	Number of records with LIFO indicator	16

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) - Relevancy of at least two years
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 Prices, Standard (Fields MBEW-STPRS) or Moving Average (Field MBEW-VERPR) is not blank
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
6. The total value of the material is not equal to 0 i.e. field MBEW-SALK3 is not blank

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 standard or moving average prices (Fields MBEW-STPRS or MBEW-VERPR) are maintained
5. Materials for which there is no value available in "Total Value" (Field MBEW-SALK3)
6. Material for which there is no stock available in "Total Stock (Field MBEW-LBKUM

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.

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Materials Masters, active in table MARA, with value (MBEW-SALK3) not equals to 0 (Zero) and having Tax Price 1 or Tax Price 2 or Tax Price 3 maintained	10680	S4HANA	10680
PF2	Materials Masters, active in table MARA, with value (MBEW-SALK3) not equals to 0 (Zero) and having Commercial Price 1 or Commercial Price 2 or Commercial Price 3 maintained	15	S4HANA	15
WP2	Materials Masters, active in table MARA, with value (MBEW-SALK3) not equals to 0 (Zero) and having Tax Price 1 or Tax Price 2 or Tax Price 3 maintained	27250	S4HANA	27250
WP2	Materials Masters, active in table MARA, with value (MBEW-SALK3) not equals to 0 (Zero) and having Commercial Price 1 or Commercial Price 2 or Commercial Price 3 maintained	55	S4HANA	55

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MBEW	MATNR	MATNR	Material code	CHAR	18	R
MBEW-	BWKEY	BWKEY	Plant	CHAR	4	R
MBEW-	BWPRS	BWPRS	Tax Price 1	CURR	13	O
MBEW-	BWPS1	BWPS1	Tax Price 2	CURR	13	O
MBEW-	VJBWS	VJBWS	Tax Price 3	CURR	13	O
MBEW-	ABWKZ	ABWKZ	Devaluation Indicator	NUMC	2	O
MBEW	BWPRH	BWPRH	Commercial price 1	CURR	13	O
MBEW	BWPH1	BWPH1	Commercial price 2	CURR	13	O
MBEW	VJBWH	VJBWH	Commercial price 3	CURR	13	O
MBEW	XLIFO	XLIFO	LIFO/FIFO relevant	CHAR	1	O
MBEW	MYPOL	MYPOOL	LIFO/FIFO pool	CHAR	4	O

Data Cleansing

For the purpose of the Object 2014 - Material Master Accounting View 3, 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. Identify all Materials that are not in use for Production, Procurement for the last two years and set them as "marked for deletion"
2. Identify all Materials that does not have any stock (Field: MBEW-LBKUM) and if these materials are not part of the BOM or any open purchase order then set them as "marked for deletion"
3. Identify all Materials that does not have any value (MBEW-SALK3) and if these materials are not part of the BOM or any open purchase order then set them as "marked for deletion"

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1.	High	Material is not valid	Check MATNR is available in MARA and MARC table	Report showing records in error	PF2, WP2
2	High	Check Material MATNR and Valuation Class	Valuation Classes not relevant for this view (to be maintained in the Syniti)	Report showing records in error	PF2, WP2
3	High	Material with no stock	Check Material MATNR is not having LBKUM (Quantity) lower than or equal to 0	Report showing records in error	PF2, WP2
4	High	Material with no value	Check Material MATNR is not SALK3 (Value) lower than or equal to 0	Report showing records in error	PF2, WP2
5	High	Price Check	Price Check - Check Tax or Commercials Prices are numeric and not negative value	Report showing records in error	PF2, WP2

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

Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable. 

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

None

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
1.	Extract from table MBEW all MATNR (material masters) where MBEW-BKLAS (Valuation Class) is not blank	Syniti Team
2.	Extract from table MBEW all MATNR (material masters) where MBEW-SALK3 (Total Value) is not blank	Syniti Team
3.	Extract from table MBEW all MATR (material masters) where MBEW-LBKUM (Total Stock) is not blank	Syniti Team
4.	Repeat Req # 1 to 3 if required	Syniti Team

Selection Screen

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

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
SE16N Table MBEW	Material (MATNR)	NA		Leave Blank
SE16N Table MBEW	Valuation Area (BWKEY)	Multiple	Yes	Enter the legacy Valuation Areas (Plant)
SE16N Table MBEW	Total Stock (LBKUM)	Selective	Yes	"Select not equal"  Value to be entered: Blank
SE16N Table MBEW	Total Value (SALK3)	Selective	Yes	"Select not equal"  Value to be entered: Blank
SE16N Table MBEW	Valuation Class (BKLAS)	Selective	Yes	"Select not equal"  Value to be entered: Blank

Data Collection Template (DCT)

Not applicable for object 2014 

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1.	Any period / year end close activities including costing runs have been fully completed	Business
2.	Data Cleansing (such as setting the Flag for Deletion at Master level) has been done	Business
3.	The total value is reconciled in MM and FI	Business
4	The prices and units to be loaded have been confirmed and reconcile to total value to be loaded	Business

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

Item #	Step Description	Team Responsible
1.	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti	Data team
2.	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3.	Confirm the value mappings as maintained in the Syniti	Data team
4	Execute transformation for the object	Syniti team
5	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Syniti/Data team
6	Generate Pre-Load reports.	Syniti team
7	Generate data load count.	Syniti team
8	Log errors as defects, if any and address resolutions. Close defects.	Syniti/Data team
9	Re-transform and re-validate the Pre-load reports if necessary.	Syniti/Data team
10	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11	Analyse and resolve any pre-load defects logged by business.	Syniti/Data team
12	Repeat steps 4 to 11 if necessary	Syniti/Data team
13	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/WP2	MBEW	MATNR	Material	S4HANA	MBEW	MATNR	Material	Source Material Number to Target Material Number
2	PF2/WP2	MBEW	BWKEY	Valuation Area	S4HANA	MBEW	BWKEY	Valuation Area	Value Mapping for Valuation Area/ Valuation Class
3	PF2/WP2	MBEW	BWPRS	Tax Price 1	S4HANA	MBEW	BWPRS	Tax Price 1	Same value as source or blank
4	PF2/WP2	MBEW	BWPS1	Tax Price 2	S4HANA	MBEW	BWPS1	Tax Price 2	Same value as source or blank
5	PF2/WP2	MBEW	VJBWS	Tax Price 3	S4HANA	MBEW	VJBWS	Tax Price 3	Same value as source or blank
6	PF2/WP2	MBEW	ABWKZ	Devaluation Indicator	S4HANA	MBEW	ABWKZ	Devaluation Indicator	Blank
7	PF2/WP2	MBEW	BWPRH	Commercial price 1	S4HANA	MBEW	BWPRH	Commercial price 1	Same value as source or blank
8	PF2/WP2	MBEW	BWPH1	Commercial price 2	S4HANA	MBEW	BWPH1	Commercial price 2	Same value as source or blank
9	PF2/WP2	MBEW	VJBWH	Commercial price 3	S4HANA	MBEW	VJBWH	Commercial price 3	Same value as source or blank
10	PF2/WP2	MBEW	XLIFO	LIFO/FIFO relevant	S4HANA	MBEW	XLIFO	LIFO/FIFO relevant	Blank
11	PF2/WP2	MBEW	MYPOL	LIFO/FIFO pool	S4HANA	MBEW	MYPOL	LIFO/FIFO pool	Blank

Transformation Mapping

Below value mapping tables should be constructed in Syniti 

Mapping Table Name	Mapping Table Description
Material	Mapping of Old vs New Material based on the Source MATNR number to target MATNR
Valuation Area	Mapping of legacy ECC valuation area to S4HANA valuation area
Valuation Class	Mapping of legacy ECC valuation area to S4HANA valuation area

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings as maintained in the Syniti	Data team
4	Confirm on the extracted values	Syniti/Data team

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team
Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Material has a source Material number reference Material exists in MARA Material is having a Valuation Area(Plan) assigned Material is having a Valuation Class assigned
Record Count	Record Count Confirm the record counts in preload summary report Total Records:  Valid Records: Invalid Records:
Business Confirmation	Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion Business Representatives to validate the pre-load file Agree with data team on the next steps for erroneous records
Exception	Establish exception rules and get approval, if applicable

Accuracy

Task	Action
Mandatory field mapping and transformation	Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.  Mandatory field check. Material has a source Material number reference Material exists in MARA Material is having a Valuation Area(Plan) assigned Material is having a Valuation Class assigned Review the data report to ensure mapping value is not missing in tool. Capture errors in the Data Error report.
Integration/Reference checks	Validate links to tables MARA, MARC, and valuation classes in T025
Business Value Checks	Total Value (SALK3) must be >0  (above checks are to be done for overall accounting and costing views of the material master)
Records in 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

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

Completeness

Task	Action
Check Data load register count	Business Data Owner/s to verify that the total number of relevant records to be converted is equal to the total number of records in the Preload file and Load Sheets for the valuation areas (plants) in scope.

Accuracy

Task	Action
Conversion accuracy	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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

Load Run Sheet

Item #	Step Description	Team Responsible
1	Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step.	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.	Data team
3	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
4	Validate few records loaded by accessing standard transactions from S/4HNA e.g. MM03	Data team
5	Generate post load report if step 5 is validated	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 1 to 5 if necessary.	Data team

Load Phase and Dependencies

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

Configuration

Item #	Configuration Item
1.	Controlling Area configuration
2.	Plants (WERKS) should exist
3.	Company Codes (BUKRS) should exist
4	Valuation Class (BJLAS) should exist
5	Material Type Configuration
6	Account determination for GL accounts in OBYC for valuation classes maintained

Conversion Objects

Object #	Preceding Object Conversion Approach
2019	Material Master Basic View
2012	Material Master Accounting View 1

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
Posting Period	Posting period is blocked for posting	Review project / cutover plan and ensure posting periods can be opened for postings
Valid Master	Material Master is not available	Ensure the material master has been created
ML active	Plant is not active for Material Ledger	Review project / cutover plan and ensure step for ML activation for all plants in S4 has been done

Post-Load Validation

Project Team

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

Completeness

Task	Action
Reconciliation of Record Count	Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count) Check for logs from Load and fix erroneous records, if any.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

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

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations

Accuracy

Task	Action
Field Checks	Check the prices for Tax or Commercial where applicable have been populated
Value Check	Check values (Tax or commercial Price) from the preload and post load.

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