LOY Transactions are getting processed twice, duplicating Accruals and Redemptions
(Doc ID 1171373.1)
Last updated on OCTOBER 06, 2021
Applies to:Siebel Loyalty Engine - Version 8.1.1  to 126.96.36.199 SIA  [Release V8]
Information in this document applies to any platform.
Loyalty Batch transaction engine is being processed twice, generating duplicated accruals and redemptions.
The duplicated transactions comes from a legacy system, where the related data got imported via EIM. During the processing, duplicated accruals and redemptions are created.
By changing the parameter LOYEngineQueueObjects to have "Transaction:1", this has greatly reduced the chance of this occurring. However, it impact the performance and a permanent fix its required.
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