Constraint in multilevel VC is not able to set value in second try.

[former_member735309]

I'm setting value for higher level characteristics by using value of lower level characteristics. i have used

1. same lower level configurable material 3 times in higher level BOM so i can configure them at lower level configuration.

2. Used constraint and PART_OF ( <char>, <char> ,"<BOM item num> ) function to set value into high level characteristics.

3. lets say material are at 10, 20,30 position, i am setting value with same lower characteristic to 3 higer characteristic like val1 = val if PART_OF ( <char>, <char> ,0010 ) , val2 = val if PART_OF ( <char>, <char> ,0020 ) , val3 = val if PART_OF ( <char>, <char> ,0030 )

the configuration is working fine in cu50 and first time in sales order but in sale order once i save the order and try to reconfigure material, i thiink constraint is not picking value and inconsistancy is raised. if anybody having experience of multilevel VC and faced similar problem can provide guidance. it will be greatly appreciated.

[a__engfehr · Accepted solution]

Hello, what you are trying to do is certainly possible and everything sounds correct from what you've posted. Are you making sure your BOM is re-exploding so that the lower level values update and the constraint "fires" again? Have you tried to run a trace on the constraint?

[former_member735309 · Accepted solution]

Hi Andrew, thanks,

The lower-level materials are getting selected using selection conditions ( this is based on higher-level characteristics ). I am fairly new in multi-level VC so is there anything special that has to be done to "making sure your BOM is re-exploding" when configuration is done in sales order? I have tried trace but with no interesting result there.

[a__engfehr · Accepted solution]

When you enter the configuration a second time, it might be good to clear out any values that are related to the constraints, then enter your new values. When you click the results button it re-explodes the BOM . That way you can see what is happening before you leave the configuration screen and get an error. You should have the results screen turned on and validate if the BOM did in fact change based on your new values.

Is it working when you change values in CU50 or does CU50 also only work the first time you configure something? Do you have multi-level BOM explosion in your profile? Do the lower levels also have multi-level? Have you verified that the selection condition is still valid when you are changing values or is it possible another dependency is causing the inconsistent? Unfortunately there are many variables to try to troubleshoot.

The best advice I can give you is that what you are doing is correct and to keep trying to troubleshoot. A constraint using the part_of syntax to pull up values from lower level in a multilevel kmat works whether it's the 1st or the 1000th time you are changing high level values.

[former_member735309 · Accepted solution]

Hi Andrew, thanks again for taking the time, this gives me many ideas to troubleshoot.

Configuration works everytime in CU50 and result is consistent even if I change values. I will check by clearing value of constraint-related characteristics to verify the BOM exploding part. Hope it works.

[a__engfehr · Accepted solution]

Ok good luck. Last thought- if everything is working in CU50 correctly you may need to get an ABAP person involved to debug your sales order screens. There may be some custom userexit preventing the configuration to change. Standard SAP allows for change mode VA02/VA22 to change configurable material values.