Hi,
I need help to solve an Issue on the variant configuration of the alternative super BOMS.
Scenario: i can create a car with two types of different types.
SKU version 1 -> wheels1 with the CHAR1 = A
SKU version 2 -> wheels2 with the CHAR1 = B
It means that we have to different Semifinished products with a different value in the class 200 CLASS_WHEELS
in which there's the CHAR1,
SKU so from a process point of view has two alternative BOMS in which in the first there's WHEELS1 and in the second there's the WHEELS2.
In the variant configuration of the SKU we have two characteristics ( CHAR1 and V2_CHAR1 ) to define the characteristics that has to generate different versions.( I don't know if there is an altertive way to configure different characteristics for different versions)
to search the wheels I have a K-class item in the BOM with the 200 class CLASS_WHEELS.
For the first alternative, it's automatic the matching of CLASS_WHEELS-CHAR1 with the CHAR1 of the BOM.
For the second alternative I have the problem because in the CLASS_WHEELS there isn't the V2_CHAR1 because the attribute is always CLASS_WHEELS-CHAR1 and also writing a dependency that does $SELF.CHAR1 = $ROOT.V2_CHAR1 i have an error because in the second alternative the CHAR1 is empty so i don't have this one in the instance and the dependency terminate in error.
How can i manage this kind of alternative boms?
Thanks in advance.