Upgrade Promotion With Incorrect Behaviour And Action Code (Doc ID 2276701.1)

Last updated on JUNE 14, 2017

Applies to:

Siebel Configurator Runtime - Version 15.18 [IP2015] and later
Information in this document applies to any platform.

Symptoms

On : 15.18 [IP2015] version, Order Management

ACTUAL BEHAVIOR
---------------
Upgrade Promotion with incorrect behaviour and action code


1) Create a root product which contains 1 Dynamic Class Relation and the Relationship domain have 2 Products ("Child product 1" and "Child product 2")

2) Create a source "Bundle Promotion A" based on component "Root Product" with the following configuration 
Min Cardinality = Max Cardinality = Default Cardinality = 1
Relationship domain contains only "Child Product 1" with default quantity = 1

3) Create target "Bundle Promotion B" based on component Root Product with the following configuration
Min Cardinality = Max Cardinality = Default Cardinality = 1
Relationship domain contains only "Child Product 2" with default quantity = 1

4) In installed asset contains Bundle Promotion A (so 3 products : Bundle Promotion A, Root Product and Child Product 1)

5) Action : select "Bundle Promotion A" in installed asset and run Upgrade Promotion process and select "Bundle Promotion B" as target Promotion


6) The Quote/Order is created with following line item 
- Bundle promotion A with action code = Delete ==> OK
- Bundle promotion B with action code = Add ==> OK
- Root Product with action code = Update ==> OK
- Child Product 1 with action code = - (Existing) ==> KO, The expected result may be the following:


the action code must be "Delete" and another line item associate to Child Product 2 must be created with action code Add


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