Variant Configuration -Technical
Variant Configuration – ALE Message Types
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
VC-Inconsitency in Sales order due to removed characteristics
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.
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
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
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
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