fbpx

Variant Configuration -Technical

Sales order Creation with Variant Configuration

by
The creation of sales order with variant configuration characteristics will be a little tricky one.
we have to use the below  Function module(FM) –
For Creation : SD_SALESDOCUMENT_CREATE
For Changes: SD_SALESDOCUMENT_CHANGE
 
one of the advantage of using this FM is that this will support all document types like Sales order, Scheduling agreements, Customer independent Requirements.

In the following section we will see the usage of this FM to create a simple Customer Independent requirement (MD81) with the variant configuration values passed on to the same.The below are the fM structure you need to work with

 

ORDER_HEADER_IN
ORDER_ITEMS_IN
SALES_SCHEDULES_IN
SALES_CFGS_REF
SALES_CFGS_INST
SALES_CFGS_VALUE

ORDER_HEADER_IN:

 

StructureFieldValueLogic
ORDER_HEADER_INREFOBJTYPEBUS2032Fixed
 REFOBJKEYRAMIRO1Fixed
 DOC_TYPE`01Fixed

ORDER_ITEMS_IN

 

StructureFieldValueLogic
ORDER_ITEMS_INITM_NUMBER10Fixed
 HG_LV_ITEM0 
 PO_ITM_NO10Fixed
 MATERIAL Dyanamic
 PLANT Dyanamic
 TARGET_QTY Dyanamic
 REQMTS_TYPKEKFixed
 MATERIAL_LONG Dyanamic

Note: In this structure the “common mistake” most of them do is not filling in the po_itm_no- if this is not filled then the SO will not be created with the characteristics values

SALES_SCHEDULES_IN

Structure Field Value Logic
SALES_SCHEDULES_IN ITM_NUMBER 10 Fixed
  SCHED_LINE 1 c
  REQ_DATE   Dynamic
  REFOBJKEY RAMIRO1 Fixed

SALES_CFGS_REF

Structure Field Value Logic
SALES_CFGS_REF POSEX 10 Fixed
  CONFIG_ID `000001 Fixed
  ROOT_ID `00000001 Fixed
  COMPLETE T Fixed
  CONSISTENT T Fixed
  CBASE_ID_TYPE G Fixed

SALES_CFGS_INST

Structure Field Value Logic
SALES_CFGS_INST CONFIG_ID `000001 Fixed
  INST_ID `00000001 Fixed
  OBJ_TYPE MARA Fixed
  CLASS_TYPE 300 Fixed
  OBJ_KEY   Dynamic-This will be Material Number
  OBJ_TXT    
  QUANTITY 10 Dynamic
  QUANTITY_UNIT TO Fixed
  COMPLETE T Fixed
  CONSISTENT T Fixed
  OBJECT_GUID   Dynamic-This will be Material Number
  PERSIST_ID_TYPE G Fixed

SALES_CFGS_VALUE

Structure Field Value Value Value
SALES_CFGS_VALUE CONFIG INST_ID CHARC VALUE
  `000001 `00000001 Charcteritics 1 Value 1
  `000001 `00000001 Charcteritics 2 Value 2
  `000001 `00000001 Charcteritics 3 Value 3

Variant Configuration – ALE Message Types

by

If you are working in a Variant configuration environment, then one of the best practices to transfer the VC – Master data between the Clients / Box is to use the ALE Methods.

The below list of message types can be a quick reference for Inward / Outward.

Outward:
MATMAS – Material master
BOMMAT -BOMs: Material BOM
CHRMAS -Class system: Characteristics master
CLFMAS -Class system: Classification master
CLSMAS -Class system: Classes master
CNPMAS -Configuration profile
DEPNET -DEPNET
ECMMAS-Engineering Change Management
KNOMAS -Global object dependencies

UPSMAS -ALE Distribution Unit (MASTER)
VFNMAS -Variant function
VTAMAS -Structure of the variant table
VTMMAS -Contents of variant table

INWARD:

MATMAS -MATM -Material Master
BOMMAT -BOMM -BOMs: Material BOM
CHRMAS -CHRM -Class system: Characteristics master
CLFMAS -CLFM -Class system: Classification master
CLSMAS -CLSM -Class system: Classes master
CNPMAS -CNPM -Configuration profile
DEPNET -DEPN -DEPNET
ECMMAS -ECMM -Engineering Change Management
KNOMAS -KNOM -Global object dependencies

UPSMAS -UPSM -ALE Distribution Unit (MASTER)
VFNMAS -VFNM -Variant function
VTAMAS -VTMAM Structure of variant table
VTMMAS -Contents of variant table

Variant Configuration – Formal Parameter not valid

by

Error Message: E28086 Formal parameter MATERIAL_XX not valid for: ZVC_XXX_YYY (Line 1)

Generally to read a value from the table we will define the C’stics from table and the C’stics from the class.

LHS = RHS

On LHS= we will be giving the Table Characteristics value

and on RHS = We will be giving the value from the Variant class.

In case if you are maintaining a DB link to the VC table, then more attention to be given to the C’stics when procedure is created.

Here you should ensure that we are giving the C’stic value from the Class and not the table. If we make any mistake then the Error E28086 bound to Happen.

VC-Inconsitency in Sales order due to removed characteristics

by

In the variant configuration scenario, there can be instances to discontinue a  characteristics from the Class.
So people generally remove them from the class.
During the removal system generally provides a warning message and we over ride the same.
In such case if they are already used in the sales order, there are chances for creating the inconsistency in the sales order configuration( VC).

When we face such situations in the configuration we will be seeing the inconsistency icon as below. The red color x mark indicates the inconsistency.

If we need to over come this then double click the red X and it takes to the below window.
In this the name of the missing character will be displayed.
 
Now you can delete the inconsistency by clicking the Delete button.
 As  you check the same configuration, now it will be complete. 

Note: In case if this was helpful or if there is a better approach for this problem do write a comment.


 
 

Finding the Inconsistent / Incomplete configured materials

by

As we work on the Variant configuration. There are instances where we will have incomplete / Inconsistent configurations.

The reason for me for many things. But in case if you need to find the list of materials that are like this.

Then we have 2 options to find them

1. Use the report RCU_MAINTAIN_IBASE_STATUS.

* This helps to find the inconsistent configuration for sales order/ material/Class etc.

2. You can use the standard CL30N using the classification  report.

 Let me know if this was helpful and if you are looking for support on this subject do leave a comment.

Transfer of the Materail Variant and Configurable Materials Char & values

by

When we work with the variant configuration environment and in case of interfaces with the Third party system.Then there will be requirement to transfer the Material along with the char values to other systems.

It is recommended to use the standard IDOC methods. 

We have the MATMAS message type to transfer the material. But generally when you try to transfer using this message, the char  and the values will not be transmitted automatically.

In such case kindly check the setting in the OMT0. In this you need to activate the tranfser of char values.

 Once done then the IDOCS will carry the char values in the segments.

Do leave your comment  if this was helpful for you.

Variant Configuration Technical

by

This Post will contain the details of the tables/ Function modules / Reports part of the VC.

Report:
********
1. RCU_CHECK_CONFIGURATION
    *This helps to check the consistency

2. RIBCHECKIBIN

3. RIBCHECKIBST

4. RCU_FIND_STRING_IN_DEP : This Report helps you find the Object dependencies based on syntax.

Function Modules:
***************
1. IBCD_GET_CD_CONFIGURATION

2. V45CU_CONFIG_HAS_CHANGES
     *This will help to find if there was any changes to the variant configuration data in the sales order. 

3. CARD_TABLE_READ_ENTRIES – To get data from the VC Tables

3. CARD_TABLE_READ_ENTRIES – To get data from the VC Tables