My Oracle Support Banner

No Validation is While Updating The Provisioning-tag Which is Impacting Existing Configuration (Doc ID 2469664.1)

Last updated on MARCH 19, 2019

Applies to:

Oracle Communications Pricing Design Center - Version 11.1.0.11.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.0.11.0 version, Server for PDC

ACTUAL BEHAVIOR

No validation is while updating the provisioning-tag which is impacting existing configuration

Created a provisioning tag which has been mapped with TelcoGprs. After that created a charge-offer/alteration-offer using this provisioning-tag.
Now some other developer has created the same provisioning tag which has been mapped with TelcoGsm. So the existing configuration has been overridden by syncPDC.No error is visible untill and unless tried to load the old TelcoGprs charge-offe/alteration-offer.

EXPECTED BEHAVIOR

Customer expectation is while loading the provisioning-tag through syncPDC it should validate the existing configuration and throw error and restrict the user to make this configuration update.

STEPS

The issue can be reproduced at will with the following steps:

1. Create the below provisionng tag in BRM and load the same

<BusinessConfiguration
  xmlns="http://www.portal.com/schemas/BusinessConfig"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.portal.com/schemas/BusinessConfig business_configuration.xsd">  /service/telco/gprs
  
[brm]$ load_config_provisioning_tags -v pin_offer_profile_provisioning_tags.xml
parsing command line options...
reading logging information...
parser initialization...
parsing document...
opening PCM connection...
flist initialization...
starting transaction...
deleting existing object(s)...
getting data from DOM tree...
creating configuration object...
creating configuration object...
creating configuration object...
creating configuration object...
commiting transaction...
closing PCM connection...
Success.

2. Run SyncPDC to sync it into PDC

[brm]$ tail -f /home/brm/admintools2/logs/syncpdc.log
Next syncPDC is scheduled to run at 12 Jun 2018 23:59:00.000 (every 1 day)
==================== Starting SynPDC on 06-12-2018 07:07:54 ==========================================
Creating PID file ..
Starting SyncPDC with JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
PLEASE ENTER KEY PASSWORD TO DECRYPT THE PASSWORD(S) :
Clean up work item SYNC_EVENT...
Work item SYNC_EVENT started (item 1 of 8).
  Processing EXTRACT work action...
  Processing ANALYZE work action...
  Processing TRANSFORM work action...
  Processing LOAD work action...
Work item SYNC_PROVISIONING_TAG started (item 7 of 8).
  Processing EXTRACT work action...
  Processing ANALYZE work action...
  Processing TRANSFORM work action...
  Processing LOAD work action...
Work item SYNC_PROVISIONING_TAG completed.
Clean up work item SYNC_BUSINESS_PROFILE...
Work item SYNC_BUSINESS_PROFILE started (item 8 of 8).
  Processing EXTRACT work action...
  Processing ANALYZE work action...
  Processing TRANSFORM work action...
  Processing LOAD work action...
Work item SYNC_BUSINESS_PROFILE completed.

Next syncPDC is scheduled to run at 12 Jun 2018 23:59:00.000 (every 1 day)

3. Create one ChargeOffer or Alteration offer using this provisioning tag.

4. Modify the provisioning tag as below and then load it into BRM followed by syncPDC  /service/telco/gsm
  
5. Try to load the chargeOffer/Alteration Offer which you have created in step 3. You will get similar type of below error.

Validation error 2 is: ProductAttributeSpec "TelcoGprs" does not match the ProductAttributeSpec "[TelcoGsm]" defined in the provisioning tag "DA-PCS"


Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.