My Oracle Support Banner

Financial Message ID Sequencing Needs to be Reset After Upgrade to Not Cause Duplicates (Doc ID 2307667.1)

Last updated on SEPTEMBER 23, 2019

Applies to:

Oracle Health Insurance Claims Adjudication - Version 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




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.