Last updated on FEBRUARY 05, 2009
Applies to:Oracle Communications Billing and Revenue Management - Version: 220.127.116.11.0
This problem can occur on any platform.
After applying <<Patch 7281339>>, it worked fine when the gap number is small. However, when the gap
number is large, the seq_orig number and gap number are not updated. Also, this information is not getting logged in the process/pipeline log.
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