Web Service Method ApplyProductPromotion Does Not Check Product Cardinality In Promotion Level

(Doc ID 1103654.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel eConfigurator - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.

Symptoms


Web Servcie ApplyProductPromotion does not consider promotion cardinality constraints.

ApplyProductPromotion doesn't add product components with the specified default cardinality under Promotion.


For example:

Customizable Product CP1
> P1, min 0, max 1, default card 0
> P2, min 0, max 1, default card 0

Promoition
>CP1
>>P1, min 0, max 1, default card 1
>>P2, min 0, max 1, default card 1

Output of ApplyProductPromotion doesn't contain P1 and P2 under CP1.
Adding same promotion through GUI P1 and P2 are added.>>>>

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