Siebel Loyalty Administration Guide > Setting Up Siebel Loyalty Redemptions >

Addressing Concurrent Redemption Transactions

Concurrent redemptions occur when two redemption transactions are processed by the Loyalty engine at the same time. Concurrent redemptions may result in a member having a negative point balance, if the member does not have enough points to redeem for both the redemption transactions.

Even if each of the concurrent redemptions is smaller than the member's balance in the point type, the two redemptions combined might be greater than the member's balance. Because the redeemed points are consumed only when the Loyalty engine writes to the database, the engine might approve both transactions without realizing that the two combined use more points than the member's total balance.

If you choose to prevent redemption concurrency, then transactions of the type Redemption and the subtype Product are validated and processed using a business component whose fields are validated before being written to the database, to check whether the total points redeemed by a member are greater than that member's point balance. If a transaction is not valid, then it is rejected with an error message saying that another redemption transaction is being processed for the member.

NOTE:  This behavior is specific to redemption processing, and it does not affect other flows, such as accrual processing or tier processing. If the action Redeem Points is used in an accrual promotion or tier promotion, then concurrent redemptions cannot be prevented.

This feature is made optional because it can potentially slow performance. By default, this feature is switched on, but you can turn it off, if you do not need it. This feature is controlled by the user property Redemption Concurrency in the LOY Processing Engine business service. Leave the default value of Y if you want to avoid redemption concurrency.