My Oracle Support Banner

Release of Oracle Communications Pricing Design Center Release 12.0 Patch Set 1 (Doc ID 2454913.1)

Last updated on JUNE 27, 2022

Applies to:

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

Details

Oracle Communications Pricing Design Center (PDC) 12.0.0.1.0 was released on 28 Sep 2018

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

Patch ID: 28630301

Key Enhancements:

Support for Rolling Back the PDC Patch Set

PDC now allows you to roll back a PDC patch set. For example, if you experience issues after installing PDC 12.0.0.1.0, you can roll back PDC to 12.0.

Support for Secure Communication With the PDC Database

PDC now supports Secure Sockets Layer (SSL)-enabled database to ensure secure communication between the PDC application and database.

Summary of fixes to customer-reported tickets delivered in 12.0.0.1.0:

 

SR Number Bug Number Description
3-10534989821 20881534 (Patch Set 1) When the Save as option was used to copy a component, it was not copying only the component instead it copied the internally referenced components along with the component. This has been fixed.
3-11060700391 21575971 (Patch Set 1) After importing setup components, there were no rows created in certain tables which was causing issues. This has been fixed. When you install BRM, its installation scripts populate the sample data, including setup and pricing components. When using PDC, this data should not be initiated in BRM, but it should be defined in PDC and published to the BRM database. To ensure that PDC and BRM are integrated properly, you must clean up the BRM sample data before you start using PDC. See the discussion about cleaning the sample data in PDC Installation Guide.
3-11937523761 22488798 (Patch Set 1) The ImportExportPricing utility with the -d (delete) parameter worked only for obsoleting a setup component and only if the component was not referenced by any other component. After the component was made obsolete, it could not be used by any other components. This has been fixed.
3-13611868831 25091591 (Patch Set 1) Import of metadata was failing with a constraint violation if PDC was integrated with ECE. Recreate the index without COMPRESS ADVANCE LOW to fix this issue.
3-14513897441 25932012 (Patch Set 1) SyncPDC was failing if /event/realtimeDiscount class existed in the BRM database. Delete this class from the BRM database to fix this issue.
3-16039294067 27040318 (Patch Set 1) Syncpdc was failing during the transformation of the event if the usage class length was more than 4K, the maximum size of the column. This has been fixed.
3-15079324011 27756978 (Patch Set 1) PDC Weblogic Server managed server was logging verbose Eclipse Link messages (up to the FINE level) in the Weblogic Server log (nohup.out). The FINE level was not appropriate for Production environments. This has been fixed.
3-17231759901 27840554 (Patch Set 1) The BRM Integration Pack installation was failing because of certain privilege issues. A SYSDBA user credential was required to proceed. This has been fixed. The PDC Installer now accepts any user with database privileges not restricting to the SYSDBA user in the System Database Credentials screen.
NA 27881855 (Patch Set 1) When a rateable usage metric (RUM) was disassociated from all services and events in the service-event map, importing the RUM into PDC caused NULL pointer exception in the real-time rating transform engine. This has been fixed.
3-17267227961 27925018 (Patch Set 1) For the same recurring charge product definition, the rate was generated as fixed amount in the case of pricing center but as scaled amount in PDC. PDC actually supports fixed amount for recurring charges. This has been fixed.
3-17126536791 27963192 (Patch Set 1) When SyncPDC was run after changing the length of a field in the storable class associated with a custom event in BRM, the change was not reflected in the event definition in the PDC database. This has been fixed.
3-17317338671 28094045 (Patch Set 1) The high-volume PDC tables were not getting purged which was leading to performance issues. This has been fixed.
3-16272784751 28171359 (Patch Set 1) For chargeshares, the General Ledger ID was migrated as Undefined instead of Not Set. This has been fixed.
3-17677726731 28262068 (Patch Set 1) The USC_MAP was case sensitive whereas the ZONE_RESULT was case insensitive.This has been fixed. The USC_MAP is also case insensitive

Actions

 

Contacts

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
Details
 Key Enhancements:
 Support for Rolling Back the PDC Patch Set
 Support for Secure Communication With the PDC Database
 Summary of fixes to customer-reported tickets delivered in 12.0.0.1.0:
Actions
Contacts
References

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