Last updated on APRIL 11, 2016
Applies to:Siebel Loyalty Manager - Version 126.96.36.199.4 [IP2014] and later
Information in this document applies to any platform.
On : 188.8.131.52.4 [IP2014] version, Loyalty
The requirement is to update all the LOY Members and their member key ids to a different key id, while the batch engine is running.
The member key id will be updated using the EAI approach. During all these updates on member there might be new transactions getting created for this member via batch process (ASYNC process), and these transactions would be getting processed.
The requirement is to make the updates while keeping the processing running.
What could be the possible issues following this approach.
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