Poor Loyalty Batch Engine Performance When Expiring Accruals
(Doc ID 1363533.1)
Last updated on OCTOBER 03, 2024
Applies to:
Siebel Loyalty Engine - Version 8.1.1.4 [21225] to 8.1.1.9 [23016] [Release V8]Information in this document applies to any platform.
Symptoms
When Loyalty Batch Engine is setup to expire accruals, the user property "LOY Queue Manager SearchSpec: Batch" on the LOY Member Accrual Item business component is not applied to the SQL statement. Instead all records are retrieved resulting in poor performance as the number of accruals grow.
(([Pt Exp Lvl Cd] = [Calc PEL Tier Level cd] AND [Expiration Date] < Today() AND [Expire Points Flag] = 'Y' AND [Expire Extension] < TimeStamp() AND [Points Remaining] > 0) OR ([Pt Exp Lvl Cd] = [Calc PEL Pt Type Lvl Cd] AND [Expiry Basis Code] = [Calc EB Acc Actvity Cd] AND [Calc AAEF] AND [Points Remaining] > 0) OR ([Pt Exp Lvl Cd] = [Calc PEL Pt Type Lvl Cd] AND ([Expiry Basis Code] = [Calc EB Period Cd] OR [Expiry Basis Code] = [Calc EB Fixed Day Cd]) AND [Expiration Date] < Today() AND [Points Remaining] > 0))
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |