Impact of Disabling PK_IFW_STZ Constraint on IFW_STANDARD_ZONE Table
(Doc ID 2504412.1)
Last updated on OCTOBER 02, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management version 220.127.116.11.0, as per business requirements, there is a need to use shared zone model for different rate plans, which implies creating same combination of "ZONEMODEL", "ORIGIN_AREACODE", "DESTIN_AREACODE", and "SERVICECODE" in IFW_STANDARD_ZONE table.
As there is a constraint PK_IFW_STZ on this table which does not allow having same combination of "ZONEMODEL", "ORIGIN_AREACODE", "DESTIN_AREACODE", "SERVICECODE" in IFW_STANDARD_ZONE table, this constraint has to be disabled.
Question: What is the impact if this constraint is disabled?
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