My Oracle Support Banner

Release of Oracle Communications Pricing Design Center Release 11.2 Patch Set 1 (Doc ID 2475433.1)

Last updated on MAY 03, 2021

Applies to:

Oracle Communications Pricing Design Center - Version to [Release 11.2.0 to 12.0.0]
Information in this document applies to any platform.


Oracle Communications Pricing Design Center (PDC) was released on 21 Nov 2018

This announcement lists the enhancements and fixes delivered in Oracle Communications Pricing Design Center (PDC)

Patch ID: <Patch 28738471>

Key Enhancements:

Support for Wildcard in Item Type Selectors:

PDC now supports wildcard (*) in item type selectors for services and events. You can use the wildcard to substitute one or more characters in the service or event name to indicate that any value is acceptable; for example, /service/telco/gsm*. The following elements are added in PDC to support wildcard: applicableToAllChildServices and applicableToAllChildEvents. By setting the true or false value to these elements, you can indicate whether the item type selector is applicable to child services or events.

If wildcard is used in the services and events, Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE), real-time rating engine, and batch rating engine use the applicableToAllChildServices and applicableToAllChildEvents values to identify if the services or events are applicable for all child services or events. If the value is set to true, the item type selector is considered for all the child services and events. If the value is set to false, the child services or events are not considered.

PDC Synchronizes Event Data Using Event Types:

Earlier, event data was synced from BRM to PDC based on the entries in pin_event_map file. With this enhancement, the BRM event data is synchronized with PDC based on the event type defined in BRM. If the event type is set to NONE in BRM and the corresponding event is mapped in the pin_event_map file, the event synchronizes with PDC. However, you should modify the event type in BRM from NONE to the relevant event type and then run the SyncPDC utility again if you want to use this event type for creating a pricing component. If the event type is set to one of the acceptable values (other than NONE) say USAGE_PREPAID, the event will be synchronized with PDC and can be used for pricing configurations even if there is no entry for the event in pin_even_map file.

After you create an event and synchronize it with PDC, it is not recommended to modify the event type of the event. However, if you have set the incorrect event type, you can modify the incorrect event type by updating it in BRM and then synchronizing in PDC. You can modify the event type only for the custom events. For example, if the event type for the parent event /event/session/telco/gprs is set as USAGE_PREPAID and the event type for the child event /event/session/telco/gprs/primary is set as NONE, you must change the event type for the child event as USAGE_PREPAID in BRM, synchronize it with PDC, and then publish to ECE. See "Synchronizing and Publishing Event Type to ECE" for synchronizing the modified data to PDC and publishing it to ECE.

Summary of fixes to customer-reported tickets delivered in

SR Number BUG Number   Description
3-18290388561 28632162     The Users could not migrate configuration objects due to the Unmatch EDR Field Type error. A few OOB field types were appearing as a string in the system. This is fixed now after changing the string to block type and migrating the metadata. Anyone using the PDC migration utility should apply this fix. This patch will replace the migration package.
3-17657000571 28156929 When importing an item type selector, NullPointerException was encountered because default ItemSpec was not set. This has been fixed by adding a validation. Now, at least one default ItemSpec is available for an ItemTypeSelector. This fix needs to be applied by anyone using ItemType Selector. The patch will replace the ImportExportPricing package.
3-17835230721 28335312 PDC real-time rating transformation engine was converting time stamps incorrectly for bundles. This was resulting in validation failures during publishing since the bundle or product timestamps were not aligned. This is corrected now by aligning timestamps. This fix needs to be applied by everyone using PDC. This patch will replace the Transformation package.
3-18417583781 28918885 During PDC migration, the process was aborting if there are any errors for which the length exceeded 4000 characters. This is fixed now by considering only the first 3999 characters of the error message and ignoring the rest so that the process can continue. Also, users could not migrate pricing objects that were using the BRE fields belonging to the CUST_A because these fields were not being migrated to PDC as part of metadata migration. This has been fixed by migrating CUST_A fields associated with the service /service to PDC. This fix is applicable for anyone using CUST_A fields in their deployments and using migration. This patch will replace the migration package.


















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

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