Redemption Design Processing Returns Incorrect Redeemed Values (LOY Promotion Designer) (Doc ID 1677632.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Loyalty Manager - Version 8.2.2.2 SIA[23016] and later
Information in this document applies to any platform.

Symptoms

In a loyalty program ensure you have 3 point types.

Create a redemption promotion: with following flags set to TRUE:
Admin/Base/Designer availability.
-> The promotion has NO criteria (for testing purpose)
-> It has 3 actions:
a. redeem points from Object Transaction > Attribute: Points/ specify point type as Point type 1
please note: Use from transaction NOT CHECKED
B. redeem points from Object Transaction > Attribute: Points/ specify point type as Point type 2
please note: Use from transaction NOT CHECKED
C. redeem points from Object Transaction > Attribute: Points/ specify point type as Point type 3
please note: Use from transaction NOT CHECKED

---//---

Then create a redemption designer flow using the following pattern:
Start > Base promotion created earlier > End

Create a redemption transaction with 10 points and process. The results are listed below:
10 points of points type 1 will be redeemed
20 points of points type 2 will be redeemed
30 points of points type 3 will be redeemed

This is incorrect!

Please note: if this promotion is applyed to a transaction as simple promotion (so not in a designer flow), then the results are as expected:
10 points of points type 1 will be redeemed
10 points of points type 2 will be redeemed
10 points of points type 3 will be redeemed

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