Loyalty Redemption Performance When Using Redemption Concurrency Slow

(Doc ID 1947220.1)

Last updated on SEPTEMBER 29, 2016

Applies to:

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


Redemption Concurrency functionality was introduced in onwards to avoid redemptions being used twice. Please see the Siebel Loyalty Administration Guide> Setting Up Siebel Loyalty Redemptions> Addressing Concurrent Redemption Transactions, which discusses this and ACR 802: Provides Bulk Administration enhancements and redemption concurrency functionality.


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