Added Custom Attributes Are Not Saved to PDC Metadata
(Doc ID 2942533.1)
Last updated on APRIL 21, 2023
Applies to:Oracle Communications Pricing Design Center - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Steps to reproduce:1. Extract metadata from PDC2. Add custom attribute to EventDelayedSessionTelcoGsm.3. Import the XML.4. Validate in ECE Cache that the attributes are present, restart ECE services for the changes to reflect.5. In BRM extract the podl file for the /event/delayed/session/telco/gsm6. Add new attributes to it (different from what was added in metadata.xml)7. Load the podl with replace option8. Restart dm_oracle and cm process.9. Wait for the scheduled syncpdc to execute.10 Once the syncpdc is executed, Extract the metadata from PDC Actual result:The metadat.xml looses the changes that were done in Step2. Expected result:The metadata.xml and the ECE cache (PDCNameMapping) retains the custom attribute added in Step2. Abrivations:PDC - Pricing Design Center.ECE - Elastic Charging Engine.BRM - Billing and Revenue Management.
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