Applying a Promotion does not Resolve Max Cardinality Violation on Child Item from Relationship of Type Product
(Doc ID 1633716.1)
Last updated on MARCH 17, 2020
Applies to:Siebel CRM - Version 18.104.22.168  and later
Information in this document applies to any platform.
Applying a promotion to a line item does not resolve a maximum cardinality violation on a child product from a relationship with type=product.
Customer has following product - and promotion definition:
root product = andi root
relationship = r1, type = Product, product=andi1
promotion definition = andi promo
component = andi root (1,1,1) and andi1 (max card=1, default card=1)
(in other words: you can only have one child product andi1 when using the promotion)
How to reproduce:
- Add andi root to a quote
- Customize it and add 2 andi1 (2 separate instances, not quantity=2)
- Enter andi promo into the promotion field for andi root
- --> promotion is rolled back with error message:
A nonproceedable error was detected during processing of your last request. Your last request was rolled back
Looking into logfile, BatchValidate does not remove one andi1 and therefore promotion is invalid as it violates max cardinality
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document