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 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.10 [23021] and later
Information in this document applies to any platform.

Symptoms

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:

  1. Add andi root to a quote 
  2. Customize it and add 2 andi1 (2 separate instances, not quantity=2) 
  3. Enter andi promo into the promotion field for andi root 
  4. --> 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

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms