Differences In Pipeline Schema After Upgrade To BRM 7.5PS2

(Doc ID 1569873.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.

Goal

When upgrading from BRM 7.4PS13 to BRM7.5PS2, we have noticed the following:-

Following columns to constraints PK_ICA
IC_DAILY_ALTERNATE/BILL_DIRECTION/PK_ICA/UNIQUE
IC_DAILY_ALTERNATE/BILLRUN/PK_ICA/UNIQUE
IC_DAILY_ALTERNATE/ENTRY_TYPE/PK_ICA/UNIQUE
IC_DAILY_ALTERNATE/ENTRY_TYPE_SEQ/PK_ICA/UNIQUE
IC_DAILY_ALTERNATE/SERVICECLASS/PK_ICA/UNIQUE
IC_DAILY_ALTERNATE/TIMEZONE/PK_ICA/UNIQUE

Following columns to constraints PK_ICD
IC_DAILY/BILL_DIRECTION/PK_ICD/UNIQUE
IC_DAILY/BILLRUN/PK_ICD/UNIQUE
IC_DAILY/ENTRY_TYPE/PK_ICD/UNIQUE
IC_DAILY/ENTRY_TYPE_SEQ/PK_ICD/UNIQUE

Following lengths to column are 10 instead of 255
IFW_ZONE.RESULT/VARCHAR2/255
IFW_ZONE.ZONE/VARCHAR2/255

Constraints PK_ICA, PK_ICD were added with 7.4PS14 and there is the script update_v7.0.8_v7.0.9.sql that contains the new columns to add to the constraints.

Should we run the script update_v7.0.8_v7.0.9.sql and alter the column RESULT and ZONE of IFW_ZONE to VARCHAR2(255)?
 

Solution

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