Last updated on OCTOBER 27, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.2.1 to 7.3.0]
Information in this document applies to any platform.
For BRM 7.0 to 7.3 upgrade, and taking the following three files from the <Patch 17173291>:
There is a flaw in the upgrade_account_product_split.sql logic for updating the /data/sequence (poid_id=311) for PIN_SEQUENCE_TYPE_PACKAGE_ID sequence :
It will always go into the IF clause, because in 7.0 this sequence PIN_SEQUENCE_TYPE_PACKAGE_ID does not exist. It never goes into the ELSE clause so the HEADER_NUM ends up being 1 after the upgrade is done.
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