| Status | |
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach for the object 2012 - Material Master Accounting View 1 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 2012- Accounting View 1 of the Material Master.
The accounting view governs 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.
Key data/fields maintained in the Material Master- Accounting View 1 are as below:
General Valuation Data
These section of the Accounting View 1 of the Material Master contains the fields that controls the valuation behavior and integration.
- Material Master - Field MBEW-MATNR
This field represents the Material Master for which the accounting and costing views are created. The material number must exist in the table MARA (basic table for Materials) - Total Stock - Field MBEW-LBKUM
This field stores the valuated quantity. The quantity gets updated upon the movement of stocks such as goods receipt, goods issue or scrapping. This field is available for display and not directly maintained in the Accounting View 1. The field gets updated in the MBEW table upon valuation. - Valuation Class- Field MBEW-BKLAS
Determines the G/L account for inventory postings based upon the account determination configuration (Table T030) - Valuation Category - Field MBEW-BWTTY
This is used for split valuation i.e. to valuate a material differently, e.g. in-house or external. In Syensquo, this field is not to be used in S4HANA as per the MDS - Valuation Type - Field MBEW-BWTAR
This is used for split valuation i.e. to valuate a material differently, e.g. in-house or external. In Syensquo, this field is not to be used in S4HANA as per the MDS - Price Determination - Field CKMLHD-MLAST
This field controls how prices are calculated in the Material Ledger. Below values are available to be maintained- 2: Transaction-based price- this indicator to be used for the case when ML actual costing is not active
- 3: Periodic Price - this indicator to be used for the case where actual costing to be run for the material
Prices and Value
These section of the Accounting View 1 of the Material Master contains the fields that stores the prices and values of a Material.
- Standard Price - Field MBEW-STPRS
This is the standard price of the material applicable for the valuation area (plant). The field is updated with numerical value - Moving Average Price - Field MBEW-VERPR
This is the moving average price of the material applicable for the valuation area (plant). The field gets updated with numerical value upon goods receipts, invoice postings, and price changes when Price Control = V. This field also denotes the periodic unit price that gets updated upon actual costing if the material ledger is active and relevant for costing of the material. - Unit Price- Field MBEW-PEINH
This field represents the Unit price for the different prices. In order to avoid rounding impacts, it is recommended to set the unit price to 100 or 1000 units - Price Control- Field MBEW-VPRSV
This field indicates the price control used to valuate stock/quantity of the material. There are two options available:- S: Standard Price
- V: Moving Average Price
- Total Value- Field MBEW-SALK3
This field stores the values i.e. total quantity multiplied by the price
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 1 is maintained for Materials which are mainly as below
Reference: PF2 - where the total value is more than 0.
- Approx 112220 plus records across 94 valuation areas
- The Valuation Classes and the count of Material are as below in PF2 where material has a value (MBEW-SALK3 not equals to 0) as on 22nd Sept'2025
Index Valuation Class Valuation Class Description Records with Price Control S Records with Price Control V Total 1 Z000 Main Raw Materials 1247 59 1306 2 Z049 Interplant Raw Material 2 0 2 3 Z050 Other Raw Materials 112 93 205 4 Z051 Packaging 800 340 1140 5 Z053 Semi-Finished Goods 2 0 2 6 Z054 Utilities 3 1 4 7 Z055 Gen & tec goods non packg 2423 89963 92385 8 Z057 Waste 39 7 46 9 Z058 Spare Parts 5 8397 8402 10 Z05A Assets- Quantity mgmt 1 167 168 11 Z05L Solid Fuels 0 4 4 12 Z05P Light Fuel Oil 0 1 1 13 Z05R* Gen & tec goods non packg 0 7 7 14 Z05Y* Utilities 0 2 2 15 Z061* Semi-Finished Goods 50 24 74 16 Z100 Finished Goods 2985 2324 5309 17 Z101 Finished Goods Purch. 100 3168 3172 Total 7770 104458 112228
Note:
- Valuation Classed marked with * to be confirmed as these seem to be duplicate.
- There are 2 records which do not have a valuation class. (not included above)
- The above numbers do not include the materials which have been set with "mark for deletion"
Reference: WP2 - where the total value is more than 0.
- Approx 145580 plus records across 243 valuation areas
- The Valuation Classes and the count of Material are as below in WP2 where material has a value (MBEW-SALK3 not equals to 0) as on 22nd Sept'2025
Index Valuation Class Valuation Class Description Records with Price Control S Records with Price Control V Total 1 Z100 CS Raw Materials 4987 378 5365 2 Z110 CS Packaging 1946 573 2519 3 Z120 CS Spare Parts 0 126159 126159 4 Z125 CS Spare Parts assets IFRS 0 33 33 5 Z130 CS Trading Goods 1171 59 1230 6 Z140 CS Intermediates 1232 0 1232 7 Z150 CS Finished Products 6166 1 6167 8 Z160 CS Spare Parts consum>BOM 0 2265 2265 9 Z170 CS Other operating supplies 0 442 442 10 Z175 CS Office supplies 0 156 156 Total 15502 130066 144568
Note:
- Valuation Classed marked with * to be confirmed as these seem to be duplicate.
- There are 17 records which do not have a valuation class. (not included above)
- The above numbers do not include the materials which have been set with "mark for deletion"
The target design in S4HANA for maintaining the Accounting View is as below
- Price Valuation: All materials that participates to manufacturing or semi-finished of finished goods (part of the BOM) should be managed at standard price with actual costing activated.
- The rest of materials should manage at moving average price without actual costing
Note: In case of by-products, the price will be at standard price but without actual costing - Apart from above the accounting classification will also be another factor in maintaining this view based on valuation class
- The field MBEW-MLMAA (ML Active) is set to active in S4HANA by default
The converted records for Material Master - Accounting View 1 will be loaded into the target S/4HANA system as overall load of Material Masters including different view, using standard SAP LTMC.
Conversion Scope
The scope of this document covers the conversion approach for the Object 2012 - Material Master Accounting View 1 from Legacy Source Systems into S/4HANA following the DD-FUN-050 Master Data Standard_2012-Materials Accounting 1
The materials relevant for valuation will be either having the price control indicator (MBEW-VPRSV) as S-Standard or V-Moving Average and accordingly the applicable price will be either maintained upon creation of a new material or updated based on the material movements.
For the purpose of the conversion, the standard price will be maintained in the field MBEW-STPRS (Standard Price) along with relevant price determination which will be used to arrive at the Total Value (MBEW-SALK3) upon the initial stock upload using movement type 561.
Data Relevancy for object 2012:
The data from legacy system includes:
- 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)
- The Materials must exit in table MBEW for Valuation Area (reference table T001K) or Company Code (Reference Table T001) in scope for conversion
- Active Material Masters where one of the Prices, Standard (Fields MBEW-STPRS) or Moving Average (Field MBEW-VERPR) is not blank
- The BOM must exist if the Material has "With Quantity Structure" (Field - MBEW-EKALR) indicator active
- 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:
- Material for which there is no stock available in "Total Stock (Field MBEW-LBKUM)
For the purpose of conversion, only those records which are active in Base table MARA and have a stock value will be considered. Accordingly, below approximated number of records are considered as scope for conversion, which may be reduced after cleansing.
| 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) | 112250 | S4HANA | 112250 |
| WP2 | Materials Masters, active in table MARA, with value (MBEW-SALK3) not equals to 0 (Zero) | 144600 | S4HANA | 144600 |
Additional Information
Multi-language Requirement
Not applicable
Document Management
Not applicable
Legal Requirement
Not applicable
Special Requirements
Below are the special requirements with respect to Material Master Accounting View 1:
- As the Material Ledger is going to be active in S4HANA by default, the price control indicator of the source materials needs to align where applicable
- The costing run in the legacy system must have been completed has part of the month end activity in the cutover month
- The standard price must be maintained before the initial Material Load happens with movement type 561
No localization or specific requirements
No third-party system relevant for source
Target Design
The to be target design relevant for Accounting View 1 of the Material Master based upon the MDS "DD-FUN-050 Master Data Standard_2012-Materials Accounting 1" is as below:
The technical design of the target for this conversion approach.
Table | Field | Data Element | Field Description | Data Type | Length (Decimals) | Requirement |
MBEW | MATNR | MATNR | Material Number | CHAR | 18 | Required |
MBEW | BWKEY | BWKEY | Valuation Area | CHAR | 4 | Required |
MBEW | LBKUM | LBKUM | Total Value | QUAN | 13 | This field will be updated upon initial stock upload |
MBEW | BWTAR | BWTAR | Valuation Type | CHAR | 10 | Not in use |
| MBEW | BKLAS | BKLAS | Valuation Class | CHAR | 4 | Required |
MBEW | MLAST | MLAST | Price determination indicator | CHAR | 1 | Required |
MBEW | PEINH | PEINH | Unit price | DEC | 5 | Required |
MBEW | BWTTY | BWTTY | Valuation Category | CHAR | 1 | Optional |
MBEW | STPRS | STPRS | Standard Price | CURR | 13 | Required |
MBEW | MLMAA | CK_ML_MAAC | Material Ledger Active | CHAR | 1 | Required |
MBEW | EKLAS | EKLAS | Valuation Class for Sales Order Stock | CHAR | 4 | Optional |
MBEW | QKLAS | QKLAS | Valuation Class for Project Stock | CHAR | 4 | Optional |
MBEW | VPRSV | VPRSV | Price Control | CHAR | 1 | Required |
MBEW | VERPR | VERPR | Moving Avg Price | CURR | 13 | Optional |
MBEW | SALK3 | SALK3 | Inventory value | CURR | 13 | This field will be updated upon initial stock upload |
MBEW | ZKPRS | ZKPRS | Future Price | CURR | 13 | Optional |
MBEW | ZKDAT | ZKDAT | Future Price From | DATS | 8 | Optional |
MBEW | STPRV | STPRV | Previous Price | CURR | 13 | Optional |
| MBEW | LAEPR | LAEPR | Date of last price change | DATS | 8 | Optional |
Data Cleansing
For the purpose of the Object 2012 - Material Master Accounting View 1, 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.
- Identify all Materials that are not in use for Production, Procurement for the last two years and set them as "marked for deletion"
- 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"
- 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 relevant for this view (to be maintained in the Syniti) Valuation classes in scope are mentioned in the above section called Conversion purpose. | 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 | Check 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:
- Extraction:
- Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
- 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
- Transform
- Transform fields by applying the fields and value mapping in the Syniti
- Generate and validate Pre-load files
- Load
- Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable.
However, with respect to object 2012- Material Master - Accounting View 1, the conversion process will depend upon the overall cutover/migration strategy <To be finalised by Functional team>, in view of the mandatory Material Ledger activation in S4HANA. The common practice/approach and steps followed are as below:
- Master Data: Load Material Master
Load material master data with all relevant views including Accounting and Costing views
The price control S or V as decided is set in the Accounting View - Material Valuation: Load Material Valuation
Data to be loaded includes Price Control, current standard price, current moving average price (if the price control is V) - Open PO, Production orders
Load open Purchase Orders and Production Orders if any - Load Inventory balances
Data to be loaded for stock quantity per plant/valuation area
This will update the total stock and value view in the accounting view - Material Ledger Costing - If the price control is S
Run costing (CK40N) in the S4HANA
Release standard price via CK24
As of now, this conversion specification is meant for updating the Accounting View 1 of the Material Master as part of the Material Master Load.
Standard LTMCs for Material Master and Material Valuations to be used.
Data Privacy and Sensitivity
Not applicable except materials having export control.
Extraction
Extract data from a source into Syniti.
There are 2 possibilities:
- The data exists. Syniti connects to the source and loads the data into Synity. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer
- Only if Synity 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 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)
Target Ready Data Collection Template will be created for Object 2012 Material Master - Accounting View 1 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)2012 - Material Master 1 Accounting View
DCT Rules
Field Name | Field description | Rule |
MBEW-MATNR | Material | Material Number for which Price needs to be maintained |
MBEW-BWKEY | Valuation Area | Business to enter Plant of the Material |
MBEW-PEINH | Price Unit | Business to enter price unit if the Material Price unit is changing from legacy |
MBEW-MLAST | Price determination indicator | Business to enter price determination indicator as 2 for the case without ML actual costing, or MAP or 3 for the case of actual costing to be run for the material |
MBEW-VPRSV | Price Control | Business to enter S for Standard or V for Moving Average Price |
MBEW-STPRS | Standard Price | Business to enter standard price if the Material has price control as S |
MBEW-VERPR | Moving Average Price | Business to enter standard price if the Material has price control as V |
Extraction Dependencies
Below dependencies apply for extraction.
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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti
- 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. | Ensure that Signed off DCT from business has been received and maintained in Syniti | Syniti/Data team |
5 | Execute transformation for the object | Syniti team |
6 | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Syniti/Data team |
7. | Generate Pre-Load reports. | Syniti team |
8. | Generate data load count. | Syniti team |
9. | Log errors as defects, if any and address resolutions. Close defects. | Syniti/Data team |
10. | Re-transform and re-validate the Pre-load reports if necessary. | Syniti/Data team |
11. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
12. | Analyse and resolve any pre-load defects logged by business. | Syniti/Data team |
13. | Repeat steps 5 to 11 if necessary | Syniti/Data team |
14. | 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 | BKLAS | Valuation Class | S4HANA | MBEW | BKLAS | Valuation Class | Value Mapping for Valuation Area/ Valuation Class |
| 4 | PF2/WP2 | MBEW | BWTAR | Valuation Type | S4HANA | MBEW | BWTAR | Valuation Type | Leave Blank |
| 5 | PF2/WP2 | MBEW | MLAST | Price determination indicator | S4HANA | MBEW | MLAST | Price determination indicator | 2 for the case without ML actual costing, or MAP 3 for the case of actual costing to be run for the material (Value as per DCT) |
| 6 | PF2/WP2 | MBEW | PEINH | Unit price | S4HANA | MBEW | PEINH | Unit price | Value as per DCT |
| 7 | PF2/WP2 | MBEW | VPRSV | Price Control | S4HANA | MBEW | VPRSV | Price Control | Value as per DCT |
| 8 | PF2/WP2 | MBEW | STPRS | Standard Price | S4HANA | MBEW | STPRS | Standard Price | Value as per DCT or leave blank |
| 9 | PF2/WP2 | MBEW | VERPR | Moving Average Price | S4HANA | MBEW | VERPR | Moving Average Price | Value as per DCT or leave blank |
| 10 | PF2/WP2 | MBEW | MLMAA | Material Ledger Active | S4HANA | MBEW | MLMAA | Material Ledger Active | Set to X "active" |
Transformation Mapping
Below value mapping tables should be constructed in SynitiMapping 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 | Ensure that Signed off DCT from business has been received and maintained in Syniti | Syniti/Data team |
| 5 | Confirm on the extracted values | Syniti, Data and business |
Pre-Load Validation
Project Team
The Pre Load validations are performed by Project TeamCompleteness
Task | Action |
Generation of | Mandatory field check.
|
Record Count | Record Count Confirm the record counts in preload summary report
|
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.
Review the data report to ensure mapping value is not missing in tool. |
Integration/Reference checks | Validate links to tables MARA, MARC, and valuation classes in T025 |
Business Value Checks |
(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:
- 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.
- 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 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 |
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
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
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 price unit (i.e. in KGs or other UOM) is correctly maintained Check the right price control |
| Value Check | Check values from the preload and post load. Check quantities are matching |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Object 2012 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
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||
