Purpose

The purpose of this document is to define the conversion approach to create conversion for Object 1080 Mixing Ratios.

Mixing Ratios are the ratios which are maintained for mixed costing. Mixing ratios are weighting factors assigned to the procurement alternatives. This weighting factor is obtained from the planning department based on the usage of the procurement alternatives during the planning year. The pre-requisites for maintaining mixing ratios are production version and production alternatives. 

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 1080 - Mixing Ratios.

Key tables and fields: 

The tables mentioned below are the main tables used for Mixing Ratios in S4.

• CKMLMV001 – This table in SAP is primarily used to store Procurement Alternatives data. This table contains various fields that hold specific information or linking keys about procurement alternatives such as Procurement alternatives, object type, valuation area etc.
• CKMLMV003 – This table in SAP stores information related to mixing ratios. The table stores information of mixing ratios with reference to the procurement alternatives and production version.

     Table: CKMLMV001 is the central table for defining procurement alternatives in SAP S/4HANA, which is a pre-requisite for migrating mixing ratios. The key fields of this table are:  

• MATNR – The MATNR is the material number of the material for which the procurement alternative is being maintained.
• WERKS – The WERKS is the plant in which the material will be costed.
• OTYP – The OTYP (Object type) field identifies the object type e.g. “BA – Procurement Alternative”, “PR – Procurement Process”, “EB-Sales Order Stock”, “LA – Activity type” etc.
• KALNR – This field stores the procurement alternative/Process number. A procurement alternative represents one of a number of different ways of procuring a specific material. You can control the level of detail in which the procurement alternatives are represented through the controlling level. Depending on the processing category, there are single-level and multilevel procurement alternatives. For example, "purchase order" is single-level procurement and "production" is multilevel procurement.
• BTYP – The process categories differentiate between the different types of procurement or consumption of materials. For example, the process categories "production" and "purchase order" represent two different methods of procuring a material. Since different methods of procurement or consumption are handled by the SAP System in different ways, the system updates different types of data. On the basis of this data, characteristics can be derived and used to create procurement processes, procurement alternatives, and consumption alternatives. E.g. “BB-Purchase Order”, “BF-Production”, “BL-Subcontracting” etc.
• SEPZ_NAME_ND - This field helps define a user defined name for procurement alternatives / consumption alternative. This can be defined by the user using controlling levels and which can be used to identify transactions in the ML data.

     Table: CKMLMV003 is the central table for defining mixing ratios in relation to procurement alternatives in SAP S/4HANA:  

• MATNR – The MATNR is the material number of the material for which the procurement alternative and mixing ratio(s) are being maintained.
• WERKS – The WERKS is the plant in which the material will be costed and for which the mixing ratios will be maintained.
• KALNR_BAL – This field is a key field and stores the procurement alternative number. A procurement alternative represents one of a number of different ways of procuring a specific material. You can control the level of detail in which the procurement alternatives are represented through the controlling level. Depending on the processing category, there are single-level and multilevel procurement alternatives. For example, "purchase order" is single-level procurement and "production" is multilevel procurement.
• KALNR_IN – This field is a key field and stores the procurement process number. It is a process in Product Cost Controlling that calculates and displays the costs incurred in the process of procuring materials. A procurement process identifies such a process for one or more materials. A process can produce multiple materials simultaneously (such as when co-products are involved), while a procurement alternative represents the procurement of a single material. Depending on the process category, the procurement process can be single-level or multilevel.
•  MGTYP – The Quantity structure type is a key field and it is used in costing with quantity structure. When costing, this controls if and how mixed costing is performed. The quantity structure type is used to determine which procurement alternatives will be used with what mixing ratio for the materials involved in the costing.  Therefore, it determines for how long the mixing ratios are valid.
• GJAHR – The year stores the year information for which the mixing ratio is being maintained. While maintaining mixing ratios, it is important to maintain the year.
• PERIO – The period stores the period specific information for which the mixing ratio is valid.
• LOSGR_PC – The costing lot size in the material master record is usually used as a basis for costing all materials within one low-level code. If these materials (such as semi-finished products) are used in materials (such as finished products) in the next-highest low-level code, the costing results are converted to the costing lot size of the material costed (in this case, the finished product) to calculate the material costs for the finished product.
• MEINS_PC – This field displays the unit of measure in which the quantity is displayed.
• ALDAT_PC – This field displays the date with which the quantity structure is selected for the cost estimate with quantity structure.
• MISCH_VERH – This field provides the weightage to be applied to individual procurement alternative when the cost estimate is executed using the mixed cost estimate. This can be entered in equivalence numbers or percentages.

The mixing ratios can be extracted from the legacy SAP system and loaded to S4 Hana via Syniti. However, SAP has not provided a standard migration object for migration of mixing ratios and hence, for the conversion of this object, the data/details will be extracted from ECC and transformed as applicable for S4HANA in Syniti and will be loaded to S4, using LTMC or a custom program.

Conversion Scope

The scope of this document covers the approach for converting active Mixing ratios from Legacy Source Systems (ECC) into S/4HANA following the Master Data Design Standard - DD-FUN-050 Master Data Standard_1080 – Mixing ratios.

The data from legacy system includes:

1. Active and valid records for Mixing ratios which are still in use/valid and have validity date is >= cutover date i.e. CKMLMV003-GJAHR = Cutover year and CKMLMV003-BRDAT is the latest date. To combine tables CKMLMV001 and CKMLMV003 use MATNR (Material), WERKS (Plant) and KALNR_BAL (Procurement Alternative). In CKMLMV001 the procurement alternative field is KALNR whereas in CKMLMV003 it is KALNR_BAL. So the logic would be CKMLMV001-KALNR=CKMLMV003-KALNR_BAL

The data from legacy system excludes:

1. All Mixing ratio records which have a validity date in the past and are not in use in any exposure

List of source systems and approximate number of records <All plants in PF2 and WP2 for which mixing ratios have been maintained for the cutover year will be relevant for migration. This information will be available in the table CKMLMV003 in PF2 and WP2 system >

Additional Information

Multi-language Requirement

None

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The Target design of the object 1080 – Mixing Ratios is based on the MDS - DD-FUN-050 Master Data Standard_1080 – Mixing Ratios Master Data is as below

The technical design of the target for this conversion approach. 

Table – CKMLMV001: Procurement Alternatives

Table – CKMLMV003: Process model: Receipts / mixing strategies

Data Cleansing

For the purpose of the Object 1080 – Mixing Ratios, it is expected that only the relevant data will be extracted to the S4 system. Data cleansing is not relevant for extraction. 

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. 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 LSMW or a custom program to upload the mixing ratios to S4.

Data Privacy and Sensitivity

Extraction

Extraction of data from a source into S4. There are 2 possibilities:

1. The data exists in the source. Syniti connects to the source system, then “extracts, transforms and loads” the data into S4. There are 3 approaches:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Data is loaded to the repository from the provided source system extract/report. This approach is considered if we cannot connect to the source system.
2. The extraction will be based on the signed off extraction rules.
3. The relevancy criteria for mixing ratios (if any) as captured in the relevancy criteria sheet will be considered.

Extraction Run Sheet

Note: Only materials identified as relevant for migration as per conversion spec 2010 and 2019 would be considered as in-scope for mixing ratios. 

Selection Screen

Data Collection Template (DCT)

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

The Pre Load validations are performed by Project Team

Completeness

Accuracy

The Pre Load validations are performed by Project Team

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
3. 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 Mixing ratios.
4. 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

Load Phase and Dependencies

The load phase for this object is ideally relevant for pre-cutover Phase 4

Configuration

Below configurations must exist to facilitate the conversion of this object.

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

Completeness

Accuracy

Key Assumptions

• Relevancy rules have been thoroughly validated and signed off by business.
• All relevant configurations have been maintained.

See also

Change log