Attribute Value Is Not Getting Updated Via Preference Constraint In Case Action Code Is Modify Or -
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
We need to update an attribute of a child product X with number of Products selected in a relationship Y in eConfigurator page.
It is working fine when Action code = Add, but when Action code = 'Modify' or '–', it is NOT working as Expected.
We created constraint with template "Constrain attribute value" which is working fine in case of new order. But when a modify order is created on asset,this constraint does not allow selecting any other product from relationship which is not expected result.
Steps to replicate:
1. Create the following product structure:
Attribute – CallingPackAttribute (free Form, Number and associated with Calling Pack Class 2)
Calling Pack Class 1 (associated with three simple products Calling Pack 1, Calling Pack 2 and Calling Pack 3)
Calling Pack Class 2 (Associated with simple product Calling Pack 4)
Root Product – Calling Pack with dynamic class relation ship with Calling Pack Class 1 and Calling Pack Class 2.
Resource - ABC
Constraint on root –
a). Provide - > Each item from Calling Pack Class 1 provides 1 to ABC
b). Require - > Any item of Calling Pack Class 1 from Calling Pack Class 1 requires selection of Calling Pack 4 from Calling Pack Class 2
c). Constrain Attribute Value - > The attribute Calling Pack Class 2 >> Calling Pack Class 2 >> CallingAttribute = ABC
2. Create one order for root product Calling Pack. Select any two children in it. You will end with resource ABC = 2 and product Calling Pack 4 auto selected with attribute set with value 2.
3. Now create asset for it.
4. Issue – When you create modify order, you won’t be able to select third product as it appears in red.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms