Last updated on JUNE 02, 2016
Applies to:Siebel Loyalty Engine - Version 8.1.1  to 18.104.22.168 SIA  [Release V8]
Information in this document applies to any platform.
Checked for relevence 06/29/12
**** Checked for relevance on 8th August 2014 ****
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms