Financial Message ID Sequencing Needs to be Reset After Upgrade to Not Cause Duplicates
Last updated on SEPTEMBER 14, 2017
Applies to:Oracle Health Insurance Claims Adjudication - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After upgrading from 2.14 to 2.16, message ID sequencing for financial message ID needs to be reset to use a sequencing range that will not conflict with existing message IDs converted from 2.14. Currently the message IDs are starting at sequence number 1.
The sequencing should start at a number that is higher than the converted messages.
The impact is that downstream systems do not know how to account for duplicate financial message IDs
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms