Managing object dependencies and their associated objects is essential for successful variant configuration and classification functionality. Situations involving long and intertwined networks, complex configurable products, multilevel BOMs, and series of tasks or operations should have correct assignment of dependencies to control the business process. A foolproof and technical approach to ensure correct relationship between dependencies and their objects can be time-saving and confidence building to the VC community. Experiential learning gained through multiple years in this area is shared here. This will help to validate the dependencies and their assignments to correct objects. This content if correctly utilized will help those in the area of variant configuration or classification in the following ways.
- Finding out the assignment of object dependencies to configuration objects or objects containing a specific object dependency
- To extract the code that is written in the dependency through the use of database tables.
- To keep an exact replica of the dependencies and their assignments in documented form.
Now let us see how the dependencies and their associated objects can be extracted. It involves the following steps.
Every object used in variant configuration has a field in its core database tables called KNOBJ. The core database table refers CABN for characteristics, CAWN for individual characteristic values, KLAH for classes, CUCO for configuration profile, PLPO / PLPOD for standard network activities and AFVC for operations in service orders. The field KNOBJ in these tables serve as the primary tool to identify object dependencies assigned to them.
- On passing these KNOBJ field to CUOB-KNOBJ, it is possible to find the internal number of the dependency assigned to these objects. The internal number is represented in the field CUOB- KNNUM. The field CUOB-KNTAB also represents the object to which the dependency is assigned to. This field will have the values as CABN, CAWN, KLAH, CUCO, PLPOD etc in each record representing the objects to which the dependency is assigned.
- CUOB-KNNUM should be provided as input in CUKB-KNNUM to extract the name of the dependency as mentioned in the field CUKB-KNNAM.
- Same input to CUKN-KNNUM will give the exact code in the dependency shown in the field KUKN-KNBLK.
- To download the entire code for the dependency from CUKN, following points need to be adhered to.
- Output should be in SE16 standard list only
- In output user settings, the field “Check Conversion Exits” field should be checked on
- While downloading the field KNBLK, it should be saved in an excel sheet. After opening the excel sheet, contents should be copied to a text document to ensure that the codes are represented in user friendly way.
If this logic is clearly understood, it is easier to get the relationship between object dependencies with the entire list of configuration objects. This can serve as powerful tool while creating many standard networks, BOMs etc and provide better control.
I will look at some other topic to write something about, soon!