Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 126.96.36.199 SIA  and later
Information in this document applies to any platform.
On the vanilla 8.1.1.x vanilla application when you inactivate constraint rules it causes inconsistent results when you customize existing order line items with engine picked component products. The application behavior is inconsistent based on the existence of other constraints for component products in the same class relationship.
The deletion of an existing component product on a sales order, added already by a constraint that has been changed to inactive, depends surprising if any second constraint is active for the same relationship.
Steps to reproduce the problem:
Complex Product “CxP” Definition has a relationship R1 for class Discount with 2 child products in the domain and 2 constraints as follows:
--- "Discount 25%"
--- "Discount 50%"
--- Constraint = When (1 = 1) requires selection of Discount 25% from R1
--- Constraint = When (1 = 1) requires selection of Discount 50% from R1
A Sales Order is created for the complex product and 2 child component products as follows:
Line Number, Product, Action Code
1 CxP - New Item
1.1 Discount 25% - Engine Picked
1.2 Discount 50% - Engine Picked
Then Inactivate the constraint that adds Discount 50% and release the new product definition for “CxP”. Customize line item again for CxP and the “Discount 50%” is removed as expected with the message:
“Path: DISCOUNT 50% -- Action: Delete Product“
Then Cancel the configurator without saving the changes.
Then also Inactivate the second constraint that adds Discount 25% and release CxP. Customize the line item for CxP and UNEXPECTANTLY neither of the 2 component products are deleted for Discount 50% and 25%
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