LoyEngineBatch Task Creates Duplicate Records In The S_LOY_ACRL_ITM Table For Points Transfer
(Doc ID 2671518.1)
Last updated on MAY 31, 2020
Applies to:Siebel Loyalty Engine - Version 15.4 [IP2015] and later
Information in this document applies to any platform.
When processing a Loyalty transaction, the accrual id is being created twice
When a Loyalty transaction is processed, there should only be one accrual id.
The issue can be reproduced at will with the following steps:
1. Create data for the Loyalty transaction (in this case the data is created via EIM)
2. Run the batch engine
3. When the batch is complete review the transaction for accruals, there are duplicate accrual id's.
4. This only occurs for transactions where 'Points Transfer' is used
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