Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.3.0]
Checked for relevance on 20-Jul-2016.
When using opcode PCM_OP_PRICE_SET_PRICE_LIST for purging of PC configuration entities: /product, /discount, /plan and /deal, it was discovered that dependencies were not correctly handled.
Load PC configuration into DB (File PC_config):
a. Deal#1 contains Product#A
b. Deal#2 contains Product#A
TEST1: Purge Deal#1 and Product#A within a single transaction
Result: Flist was processed with error, Product #A can not be purged because it was referenced to existing Deal#2
=> This was CORRECT BEHAVIOUR
TEST2: Purge Deal#2 and Product#A within a single transaction
Result: Flist was successfully processed, Deal#2 & Product#A were purged from DB config objects. Deal#1 remained in the DB with reference on non-existing Product#A
=> This was INCORRECT BEHAVIOUR
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