My Oracle Support Banner

Loyalty Member Attributes in Transactions created in Batch Are Calculated Incorrectly when Transactions are Cancelled (Doc ID 2665363.1)

Last updated on MARCH 18, 2022

Applies to:

Siebel Loyalty Engine - Version [IP2013] and later
Information in this document applies to any platform.


On : [IP2013] version and higher, Loyalty

In the scenario where multiple Transactions are created in Batch, when having them later cancelled, the Member Attributes are calculated incorrectly.

The issue can be reproduced at will with the following steps:

1 - Create a Member Attribute:

Loyalty Program > Program level attributes> Member attributes > "ABC Coffee" - Type: Number

Make sure the "Cancel Action' is set to "Cancel Change"



2 - Modify existing Accrual Promotion and add an "Update Attribute" Action:

"Accrual" Promotion

> Rule: Give Points


1 Assign Points

2 Update Attribute > "ABC Coffee" with Transaction.Points



3- Use SOAP UI to create 4 Transactions and process all of them:

2- Repeated the above for each of the other 3 Products

3- Last Transaction has ABC Coffee = 4444 as expected

4- Cancel each of the Transactions in the UI

5- Process them:

ABC Product - ABC Coffee = 3333

PS Generic Vehicle - ABC Coffee = 2222

Penalty Charges - ABC Coffee = 1111

Write-in Package Each - ABC Coffee = 0

So, when importing them 1 by one (not in Batch), the "Cancel Change" action subtracts the Points accrued from the Member Attribute

In the case of a Batch it is subtracting the Member Attribute from the Attribute Value in the Accrued Item





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.