My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 22 (Doc ID 2475525.1)

Last updated on AUGUST 15, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.21.0 [Release 7.5.0]
Information in this document applies to any platform.

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 22 (7.5.0.22.0) is released on 21 November 2018.
This announcement lists the enhancements and fixes delivered in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 22.

Patch ID: <Patch 28377280>

Key Enhancements

Improved Resiliency with Continued Elastic Charging Engine Operations without BRM: In previous releases, ECE was using the Portal Object IDs (POIDs) generated in BRM for tracking rated events and bill items created in ECE. In case of any connectivity failures between BRM and ECE, ECE was unable to continue with charging for the incoming usage requests. With this enhancement, ECE can generate POIDs necessary for charging without depending on a running BRM instance and hence makes the charging functionality resilient. This also helps during operational maintenance that may require a restart of BRM.

Improved BRM-to-ECE Data Synchronization: In the previous releases, sometimes there was a lag between the BRM database and the ECE cache update when the BRM data commit failed. During the lag, the BRM and ECE data were unsynchronized. With this enhancement even if there is a data commit failure, the data consistency between BRM and ECE are maintained.

Wildcard support for service and event names in rating: During design time, Pricing Design Center now supports wildcard (*) in item type selectors for services and events. You can use the wildcard to substitute one 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. Both the real-time rating engine and batch rating engine have been enhanced in BRM to support wildcard in item type selectors for services and events. If wildcard is used in the services and events, 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.

Secure Communication between LDAP Data Manager and Connection Manager: With this patch set, BRM now supports Transport Layer Security (TLS) to provide secure communication between LDAP Data Manager and Connection Manager (CM), making your deployment more secure.

Enhanced Data Protection: With this patch set, BRM includes functionality that help protect your customers’ data with the following:

Certifications:

For more information on the above feature enhancements, see BRM Documentation. 

Customer-Reported Fixes

 

Activity/Notification Framework

Customer Reported Issues on Activity/Notification Framework

SR Number

Bug Number

Description

3-17181472981

27881744

For billing cycles which spans across multiple months, newsfeed was getting created for the /event/notification/service_item/make_bill event for each accounting cycle.
This has been fixed. Now the newsfeed is generated only for the last accounting cycle in the multi month billing cycle. This fix is part of the activity module in Portal_Base package and it is recommended for customers to apply this fix.

3-17558077599

28200055

After purchasing the monthly cycle forward product, the newsfeed for the same did not include the bill unit information. Especially when the account had multiple bill units, it was difficult to correlate the newsfeed with the bill unit information and such newsfeed appears for all bill units in Billing Care. This has been fixed and bill unit information is available as part of the monthly cycle forward product purchase newsfeed. This fix is part of the activity module in Portal_Base package and it is recommended for customers using Billing Care to apply this fix.

3-17600593901

28261965

For cycle forward events, having discounts the newsfeed functionality was not working. This was when the account has a 100% discount on the product purchase fee event, the newsfeed generation was failing. This has been fixed. This fix is part of the activity module in Portal_Base package and it is recommended for customers using Billing Care to apply this fix.

Account Receivables 

Customer Reported Issues on Account Receivables

SR Number

Bug Number

Description

3-16512320161

27738256

When event adjustment was done after 100% tax-only adjustment, the tax jurisdiction information was not updated properly in the balance impact of the event adjustment. This was causing the adjustment to capture incorrect tax jurisdiction information.
This has been fixed. In addition, the fix has been tested for zero percent tax and the tax amount becoming zero cases as well. This fix is part of the Account Receivables module in Portal_Base package and it is recommended for customers using this module to apply this fix.

3-16449323311

27751024

While calculating the adjusted amount, PCM_OP_AR_RESOURCE_AGGREGATION opcode was not considering the tax balance impacts causing it to return incorrect aggregated amount.

This has been fixed. This fix is part of the Account Receivables module in Portal_Base package and it is recommended for customers using this module to apply this fix.

3-17120015936 

28220689

After multiple bill adjustments, reallocation of the payment was done incorrectly. It was also noticed that the due amount of the account was also corrupted.

This has been fixed. This fix is part of the account receivables module in Portal_Base package and it is recommended to apply this fix.

3-17302144931 

28255174

Even if there was no amount left for adjustment, BRM was allowing adjustment up to the full adjustment amount.

This has been fixed with a validation on the amount left for adjustment.This fix is part of the account receivables module in Portal_Base package and it is recommended to apply this fix.

3-17540344751  

28342606

After a 100% tax only event adjustment, if you perform an event adjustment, then the tax-jurisdiction array in the event balance impacts included non-zero value for the tax adjusted which is incorrect and did not have proper values for the fields in the array.

This has been fixed. This fix is part of the account receivables module in Portal_Base package and it is recommended to apply this fix.

 

Batch Rating

Customer Reported Issues on Batch Rating

SR Number

Bug Number

Description

3-17376756441

28259131

When an APN Map was reloaded using a semaphore, the rating functionality did not consider the new APN Map configuration. So the rating was continuing to use the old APN Map configurations.

This has been fixed. This fix is part of the Pipeline Manager package and it is recommended for customers using this to apply this fix.

Billing Management

Customer Reported Issues on Billing Management

SR Number

Bug Number

Description

3-16509283701

27938638

After an event is rated for a specific service and balances updated in BRM, in the Customer Center on Balance > Bill In Progress > Service tab, the charge column was indicating the amount that did not include corresponding tax amount and also the tax amount was not shown separately anywhere in the screen.
This has been fixed by providing a way to custom build the information that needs to be added to the event structure using policy opcode PCM_OP_BILL_POL_GET_EVENT_SPECIFIC_DETAILS which is called by PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode.
This fix is part of the billing management of Portal_Base package and it is recommended to apply this fix.

3-17025208951

27993356

During billing, the grantor information in the rollover bucket was incorrectly set to null. The billing flow was invoking PCM_OP_BILL_DEBIT which was updating the grantor information.

This has been fixed and now the billing flow will not change the existing grantor information when rolling over the balances. This fix is part of the billing management of Portal_Base package and it is recommended to apply this fix.

3-17331083621 

28247286

The bill generated using Bill Now was not including all items due for billing. This has been fixed. Now the search for items has been updated to extract items from the actual last_bill_t timestamp until the date, so that the items are not missed for billing. This fix is part of the customer and billing management of Portal_Base package and it is recommended for customers using Bill Now functionality to apply this fix.

3-17062080421

27816385

Even after paying the bill amount, the bill amount from the last bill was displayed as balance brought forward.

This has been fixed. This fix is part of the billing management in Portal_Base package and it is recommended for customers to apply this fix.

 

Billing Care

Customer Reported Issues on Billing Care

SR Number

Bug Number

Description

3-16918562891

27771471

In a bill unit hierarchy, if a bill contains charges from subordinate bill units, during the allocation of amount to those items it was found that the items were getting over allocated.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17110341365 

27823058

In Billing Care, the Detailed Allocate Adjustment screen was showing the first column as “Name” and Detailed Allocate Payment screen was showing the first column as “Account”. But for both it should have been “Account”.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17102959567 

27828886

In Billing Care, the Payment Allocation screen displayed the account POID instead of the account number.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17069559841

27874942

In Billing Care, when a payment was first applied to an account and then moved to suspense and then again allocated to another account and then moved to suspense, the Audit Trail was not updated correctly. It was still showing the first account.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-16991351901

27874944

In a BRM deployment, where the Billing Care time zone is different from the BRM sever time zone, when purchasing a product or discount, the start date was not matching the product purchase date in the Billing Care UI. The mismatch was found to be due to the difference in the time due to time zones.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17270002631

27931961

In Billing Care, If a bundle was purchased with an override amount, the override amount was not accepted if it included resource symbol and/or comma in it. For example 1,000.00 and $1000.00 was not accepted.
This has been fixed by removing formatting symbols (comma, resource symbol etc) from the amount field in Purchase Product/Discount configure screen. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17304458501

27938641

In Billing Care, when you post a new comment in the Payment Reversal page, the date information and earlier comments were not displayed correctly unless the page was refreshed.
This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17515609821

28206781

When Billing Care was loading updated custom javascripts, the user had to clear the browser cache manually and relogin.

This has been fixed by making customRegistry.js non-cacheable and gets loaded with a timestamp in the query parameters, so that the browser reads the updated version every time without the need for clearing the browser cache. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17402905141 

28220686

In Billing Care, the override amount was not being retained when the product status was changed to active.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17346452171

28261962

In Billing Care, the search results in the Payment Suspense screen was not displaying all the records as per the set pagination limit.

This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17876082331

28431425

The Account Details page for an account with multiple bill units was taking more time to open, in some cases as high as 7 minutes, and this was leading to time out.
This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-15288812761

27730464

In Billing Care, the Event screen was inconsistent while showing events.  Sometimes the event description box was showing just item and sometimes it was showing two items.
This has been fixed and now the Events screen in Billing Care shows the events and the details consistently. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-16951952221

27764509

In Billing Care, lengthy bill numbers and amount details were not displayed properly. In the Adjustments and Payment Allocation views that columns of the grid window displaying bill numbers and amount details were not resizable.
This has been fixed and now you can resize the columns of the grid window so that the entire length of bill numbers and amount details can be viewed.
This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-16770126831

27924914

Using the Billing Care SDK, it was not possible to customize the purchase deal screen and add custom fields. It was also not possible to display the new fields in the asset display screen, changing the start /end date and change the overridden amount.
The Billing Care SDK has been enhanced to support the above requirements.
This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17410770761

28047574

In Billing Care, any backdated cancellation was not prorating the charges.
This has been fixed. Now backdated cancellations made from Billing Care prorates cycle charges.
This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-17556441791

28466515

In Billing Care, when displaying newsfeed for an account having a payment moved to suspense, selecting “Show Payment in Suspense” option was incorrectly navigating to the Payment Search page instead of displaying the suspended payment.
This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

3-18258591791

28622335

In Billing Care, after a non-currency adjustment, the user interface was not rendered properly.
This has been fixed. This fix is part of the Billing Care package and it is recommended for customers using this package to apply this fix.

 

Business Operations Center 

Customer Reported Issues on  Business Operations Center

SR Number

Bug Number

Description

3-17161825201

27788397

In Business Operations Center, if the SERVICE_HOST parameter in the bocui-config.properties file was set to the host name, the Internet Protocol (IP) address could not be used in the Business Operations Center URL. If the parameter was set to the IP address, the host name could not used in the Business Operations Center URL.
This has been fixed by removing the dependency on the SERVICE_HOST parameter. This fix is part of the Business Operations Center package and it is recommended for customers using this application to apply this fix.

 

Collections Manager

Customer Reported Issues on Collections Manager

SR Number

Bug Number

Description

3-16932753911

27621457

In Collections Manager, when an account had two bill units, a paying bill unit and a non-paying bill unit, the aging due for the account was calculated incorrectly.

This has been fixed. This fix is part of the Collections Manager in Portal_Base package and customers using collections must apply this fix.

3-16818528141

27684530

When Collections Manager opcode PCM_OP_COLLECTIONS_GET_ACTION_HISTORY was called by opening a transaction from outside, the opcode was throwing error "bad cm_change_dm_connection", if the database number of the transaction was different from that of the collection event user.
This has been fixed by encapsulating the transaction in a new context. This fix is part of the Collections Manager in Portal_Base package and customers using collections must apply this fix.

3-17133778471

27956400

In Collections Manager, the collection write-off was failing for the bill unit in collection.
This has been fixed and the schedule status gets updated to completed after the write-off action. This fix is part of the Collections Manager in Portal_Base package and customers using collections must apply this fix.

3-15944105871

28359385

In Collections Manager, schedule objects were created for both the group as well as the members in the group. When the scheduled task was completed or cancelled, only the group schedule object was purged and the member level schedule objects were left undeleted causing them to grow substantially in number.
This has been fixed. Now the schedule objects will be created only for the group and not for individual members, as group schedule object itself will take care of the child level task as well. This fix is part of the Collections  Manager in Portal_Base package and it is recommended to apply this fix.

 

Conversion Manager

Customer Reported Issues on Conversion Manager

SR Number

Bug Number

Description

3-17548004211

28123146

Conversion Manager was not providing an option to capture bill_accounting_cycles_left and next_bill_t information for migration. Due to this migration of quarterly billing customers with the right information in ACTG_LAST_T, ACTG_NEXT_T, ACTG_FUTURE_T fields was not possible. For a quarterly billing customers the information in these fields were similar to that in the monthly billing customers which was incorrect. For example, for a quarterly billing customer migrated on 08-May-2018, with next bill on 01-Aug-2018, the expected values must be ACTG_LAST_T = 01-May-2018, ACTG_NEXT_T = 01-June_2018 and ACTG_FUTURE_T = 01-Jul-2018, but it was showing incorrect dates.
This has been fixed, by capturing bill_accounting_cycles_left and next_bill_t information to deduce the remaining fields. This fix is part of the Conversion Manager in Portal_Base package and it is recommended for customers using Conversion Manager to apply this fix.

 

Customer Center

Customer Reported Issues on Customer Center

SR Number

Bug Number

Description

3-16910009551

27730467

In the Event Browser of Customer Center, the account status was not displayed appropriately and it was defaulting it to Active.

This has been fixed.
This fix is part of the Customer Center package and customers using Customer Center must apply this fix.

3-17274051251

27924912

In Customer Center, when the Show All Parents option was selected from the Hierarchy tab of a child account, the parent account disappeared from the Account Hierarchy section.
This has been fixed. This fix is part of the Customer Center package and it is recommended for customers using it to apply this fix.

3-17284651441

27945964

Customer Center was allowing to open more than the maximum number of accounts specified. The property account.view.open.max in Customized.properties file in the lib directory was not working correctly.
This has been fixed and verified for both partial loading and bulk loading of accounts into Customer Center. This fix is part of the Customer Center package and it is recommended for customers using this package to apply this fix.

3-17294590691

27986159

In Customer Center, after viewing event details by navigating through a bill, the Event Browser was not showing any data, unless the Customer Center was relaunched.
This has been fixed and you will be able to view events through event browser after navigating through a bill. This fix is part of the Customer Center package and it is recommended for customers using this package to apply this fix.

3-17296204671

27986161

In Customer Center, it was not possible to hide the bill date field through customization. With this fix an extension hook is provided to customize Customer Center to hide bill date field
Customization steps
1. Open the CCSDK_Home/CustCntr/custom/Customized.properties file in a text editor.
2. Add the following after the comment statements:
com.portal.app.cc.PBillDetailsPage.subclass = com.custom.CustomBillDetail
3. Customizing Product Attribute page.
 - create a class CustomBillDetail which extends PBillDetailsPage
 - call super() in constructor.
 - override showHideSummaryFields and hide the bill date & label like shown below.
NOTE: Rest customization steps needs to be followed from CCSDK documentation.
Example:
package com.custom;
import com.portal.app.cc.PBillDetailsPage;
public class CustomBillDetail extends PBillDetailsPage{
       protected void showHideSummaryFields() {
              super.showHideSummaryFields();
              mBillDateLbl.setVisible(false);
              mBillDate.setVisible(false);
       }
}
This fix is part of the Customer Center package and it is recommended for customers using this package to apply this fix.

3-17247811981

27993351

The Event Browser in Customer Center was not showing time information with the date.
This has been fixed. For displaying the time information along with date, a new entry Infranet.eventbrowser.datetime.format=true should be added to Infranet.properties of Customer Center. This fix is part of the Customer Center package and it is recommended for customers using this package to apply this fix.

 

Customer Management 

Customer Reported Issues on Customer Management

SR Number

Bug Number

Description

3-17681700281

28342601

After upgrading to patch set 21, when an account was created, the ACCOUNT_NO value was not updated correctly in the UNIQUE_ACCT_NO_T table.

This has been fixed. This fix is part of the customer management in Portal_Base package and it is recommended to apply this fix.

3-17912151191

28370208

The PCM_OP_CUST_DELETE_ACCT opcode was not deleting the corresponding /purchased_bundle objects.
This has been fixed and delete account opcode deletes all information pertaining the account including /purchased_bundle objects.
This fix is part of the customer management of Portal_Base package and it is recommended to apply this fix.

 

Integrations

Customer Reported Issues on Integration

SR Number

Bug Number

Description

3-7711865221 

28258830

When BRM was processing orders by using JCA Adapter, if the CM instance goes down, the JCA Adapter was unable to restore the transaction state. As a result, the subsequent orders could not be processed without restart. There was an exception thrown by connection close request, and this is handled gracefully. This fix is part of the JCA Adapter in Portal_Base package and it is recommended for customers using this to apply this fix.

 

LDAP Manager 

Customer Reported Issues on LDAP Manager

SR Number

Bug Number

Description

3-17399412831

27993359

In LDAP Manager, the entry update operation was failing. This was due to the presence of PIN_FLD_DN and PIN_FLD_DN_FLAGS in the input to the operation.
This has been fixed. The LDAP Manager will ignore the presence of this fields, so that the operation is successful. This fix is part of the LDAP Manager of Portal_Base package and it is recommended for customers using dm_ldap to apply this fix.

3-17548989291

28141240

After enabling SSL for LDAP Data Manager (dm_ldap) with “-dm enable_ssl 1” configuration set in the pin.conf, the dm_ldap process was failing to start and hence it was not possible for creating an account such that a corresponding entry was made into the ldap directory server.
This has been fixed. The issue was due to dm_ldap linking with Oracle 11g database client libraries, while BRM required 12c libraries for SSL. LDAP Data Manager has been updated to use the 12c database client libraries. You need to install 12c database client libraries with this fix.
This fix is part of the LDAP Manager of Portal_Base package and it is recommended for customers using dm_ldap to apply this fix.

Payments   

Customer Reported Issues on Payments

SR Number

Bug Number

Description

3-15853592531

27632733
28045166

BRM was not processing payments with stored credential framework (such as CIT/MIT) for VISA credit cards. With this enhancement BRM can now process such payments.
This fix is part of the customer management, payments module Portal_Base package. Customers using payment processing must apply this fix.

3-16798260391

27771918

Running the pin_deposit utility was creating charge events.

This has been fixed to consider existing checkpoints so that new checkpoints are not unnecessarily created leading to multiple charge events.
This fix is part of the payment module in Portal_Base package and it is recommended for customers using this module to apply this fix.

3-17757279581

28342610

When a zero-amount payment was initiated by using CIT or MIT-enabled Payment Data Manager calling PCM_OP_PYMT_COLLECT opcode, the payment was failing.

This has been fixed. This fix is part of the payments module in Portal_Base package and it is recommended to apply this fix.

3-17757279623

28387496
28573588

In Paymentech Data Manager, there was no flexibility to set the transaction type for payments.
This has been fixed. Payment Data Manager has been enhanced to support setting transaction type in detail record. The value of
transaction type is read from PIN_FLD_TYPE under PIN_FLD_TRANSACTIONS array in the input for payments.
This fix is part of the payments in Portal_Base package and if you are using Paymentech Data Manager, it is recommended to apply this fix.

 

Rating

Customer Reported Issues on Rating

SR Number

Bug Number

Description

3-13130030441

28007849

In the rating flow, if there existed any sponsor products, they were not considered for rating and this resulted in incorrect balance impacts.
This has been fixed and sponsored products are considered at the higher priority than other products for rating. This fix is part of the real time rating module of Portal_Base package and it is recommended to apply this fix.

3-17298474221

28141242

After loading the rated events from Pipeline Manager, it was found that MOD_T of the corresponding items and journals were less than the CREATED_T. For pipeline rated events the timestamps are determined at the time of loading into BRM. Due to multi-threaded processing of rated events from Pipeline Manager, it was possible that a later event got loaded first which determined the created_t of a new item or journal, but an event with an earlier timestamp was loaded later.
This has been fixed. This fix is part of the Rated Event Loader (REL) of Portal_Base package and it is recommended for customers using REL to apply this fix.

3-16506227591

28149094

In a RAC database setup with SCAN configuration, the Rated Event Loader (pin_rel) was not able to connect to database using database TNS alias and JDBC thin driver. The Rated Event Loader was exiting indicating out of memory error.
This has been fixed. Two options are available to customers to connect Rated Event Loader to the database. A new optional configuration has been added to Infranet.properties of pin_rel, namely “infranet.rel.service_name”. When service_name has a configured value, it will use the service_name along with configured database host and port to create a URL for connection to database. If the service_name is not configured, it will use the TNS alias to connect to the database.
This fix is part of the Rated Event Loader (REL) of Portal_Base package and it is recommended for customers using REL to apply this fix.

 

Server Platform 

Customer Reported Issues on Server Platform

SR Number

Bug Number

Description

3-17136830661

27938636

It was not possible to locate the Secure Sockets Layer (SSL) client wallet file due to the use of back slash (\) in the resource path instead of a forward slash (/). While loading the SSL wallet file as a resource, the resource location could contain ‘\’ character in Windows environment. But as per Java specification, the resource location could only contain ‘/’ character. So that wallet was not being searched correctly in its CLASSPATH and was failing to locate it.
This has been fixed by changing the resource location to use ‘/’ character even on Windows. This fix is part of the core Portal_Base package and it is recommended for all customers to apply this fix.

3-17697487631

28187119

BRM was using different versions of HTTP Client jar files for different operational scripts. During the upgrade to Patch Set 21 all scripts were not updated to use the same version of HTTP Client i.e., version 4.5.3.  This has been fixed. This fix is part of the Portal_Base package and it is recommended for customers to apply this fix.

3-17489100311

28251457

In Pipeline Manager, starting the batch rating engine with SSL enabled resulted in the ERR_INFRANET_GDD_INIT_FAILED error. This was SSL connection error between Pipeline Manager and Connection Manager (CM) and has been fixed.
This fix is part of the core Portal_Base package and it is recommended for customers using Pipeline Manager to apply this fix.

3-17223827112

28379546

In a BRM system integrated with ECE, External Manager (EM) Gateway, any BRM initiated operation that requires to update ECE cache, updates the data in BRM and in the same transaction updates it in ECE cache through EM Gateway; once it is committed in ECE, the transaction is committed in BRM database. During this, if there was an error during the pre-commit phase of BRM transaction, then there used to be data inconsistency between BRM and ECE.
This has been fixed. The ECE commit is now triggered only after the BRM commit succeeds.
For this the following updates are necessary in the pin.conf of CM:
- cm em_group ece PCM_OP_ECE_POST_COMMIT
- cm ece_post_commit_enabled 1
Also the following updates are necessary for ECE to participate in the post commit trigger for transactions from BRM. This requires ECE to be upgraded to 11.3.0.9.0.
1. Edit ECE_HOME/config/management/charging-settings.xml file and add the
   below biz config parameters.
     brmPostCommitEnabled="true"
     updateRequestServerTimeout="20000"
2. Edit the ECE_HOME/config/charging-cache-config.xml file and add below
   cache mapping entry
        <cache-mapping>
            <cache-name>CustomerInBrmTransactionLock</cache-name>
            <scheme-name>default-federated-non-expiry</scheme-name>
        </cache-mapping>
This fix is part of the core Portal_Base package and ECE package and it is recommended to apply this fix.

3-17796627641

28466538

Indexes were getting rebuilt every time the audit tables were purged and in the process it was failing.
This has been fixed. This fix is part of the core Portal_Base package and it is recommended to apply this fix.

3-18126737181

28549499

The pin_recover utility was failing during the search for payments due for recovery.
When you run the following in $PIN_HOME/apps/pin_billd:
pin_recover -vendor fusa -verbose -recover_payment -pay_type 10003
It was failing due to search template not being constructed correctly.
This has been fixed. This fix is part of the Portal_Base package and it is recommended to apply this fix.

3-17747525701

28399779

The Oracle Data Manager (DM) was logging the warning message as error message. This has been fixed. This fix is part of the DM framework in Portal_Base package and it is recommended to apply this fix.

3-16428542811

27938631

The dm_fusa front end was not receiving data after the connection manager established connection with it.
This has been fixed. A new parameter “qm_fe_read_fail_interval” has been introduced in dm_fusa’s pin.conf to configure the time (in milli-seconds) to wait before retrying to read. This provides a configurable wait on second and third read operations, while reading the input from CM to resolve any delays of data reception. The reason for delay could be a network glitch or a busy CM due to higher loads of data.
This fix is part of the server_platform in Portal_Base package and it is recommended for customers using dm_fusa to apply this fix.

3-16882624611

27979519

The PCM_OP_SEARCH base opcode was failing when the template included a nested select query with the grouping by clause. This was causing errors while purchasing or cancelling of products and during billing for some accounts that may need nested select queries through Oracle Data Manager.
This has been fixed. This fix is part of the server_platform in Portal_Base package and it is recommended to apply this fix.

 

Services AAA Framework 

Customer Reported Issues on Services AAA Framework

SR Number

Bug Number

Description

3-17834273241

28366496

There was a memory leak observed in the op_tcf_aaa_search_session workflow. This has been fixed.
This fix is part of the Services AAA Framework, in Portal_Base package and if you are using Services AAA Framework it is recommended to apply this fix.

3-16672265011

27881742

When the same product was purchased twice, the service_telco_features_t table was populated with the provisioning tag of the product twice. Cancelling one of the product and then cancelling the deal with the cancelled product removed the tag preset for the active product. The expected behavior should be that it should only delete the provisioning tag for the product which was cancelled.
This has been fixed. This fix is part of the Services AAA Framework module in Portal_Base package and it is recommended for customers to apply this fix.

3-16857082511

28366494

There were memory leaks observed in the PCM_OP_TCF_AAA_STOP_ACCOUNTING opcode workflow. This has been fixed.
This fix is part of the Services AAA Framework, real time rating module and customer management in Portal_Base package and it is recommended to apply this fix.

 

Subscription Management

Customer Reported Issues on Subscription Management

SR Number

Bug Number

Description

3-16159206021

27288693

When doing a plan transition, it was not possible to override the resource balance granted or add any custom workflow. This has been fixed to allow the overriding the granted balance and you can add a custom workflow during the plan transition.
This fix is part of the subscription management in Portal_Base package and customers using plan transition must apply this fix.

3-17041510991

27745483

BRM was not providing options to control or customize workflow over rerate requests which were created as part of subscription transfer operation.
A business_param “transfer_rerate_requests” has been provided under /config/business_params for subscription to enable or disable the rerate request transfer.
This fix is part of the subscription management in Portal_Base package and it is recommended for customers using this module to apply this fix.

3-16825381141

27771914

The back-dated cancel discount operation in which the discount end date was in previous cycle, was not setting the validity dates properly. This has been fixed.
This fix is part of the subscription management in Portal_Base package and it is recommended for customers using this module to apply this fix.

3-16736341981

27795344

If sequential discounting was enabled, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was not working properly for in-advance billing periods. The discount refund and reapply were not done correctly for in advance periods. Now it has been fixed.
This fix is part of the subscription management module in Portal_Base package and it is recommended for customers using sequential discounting to apply this fix.

3-16926420921

27881740

When an event was rerated twice, the tax jurisdiction was not handled properly for adjustment events. The first rerating was reverting the charges properly, but second rerating after purchasing another product was not working correctly. This had been fixed. This fix is part of the subscription management module in Portal_Base package and it is recommended for customers using rerate/rebill functionality to apply this fix.

3-16778875601

27891286

In a prepaid environment, when the subscriber's balance was lower than the required balance for a purchase and if a deal was purchased, BRM displayed the credit limit exceeded error. In addition, signal 11 was observed in Connection Manager.
This has been fixed. This fix is part of the subscription management module in Portal_Base package and it is recommended for customers to apply this fix.

3-17204427041

27894047

The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan (FROM_PLAN) after moving to the new plan (TO_PLAN).
This has been fixed. This fix is part of the subscription management module in Portal_Base package and it is recommended for customers using plan transition to apply this fix.

3-17010229176

27894049

During item adjustment flow, the search operation for a billable item was going into an infinite loop.
This has been fixed to handle the search operation efficiently and optimally. This fix is part of the subscription management module in Portal_Base package and it is recommended for customers to apply this fix.

3-17232910091 

28089235

Quarterly cycles were getting merged which caused issues in applying charges. For example, create an account with cycle start as 1st Jan and move the virtual time to 2nd April and bill the account for one quarterly cycle. Then purchase a backdated quarterly recurring cycle product from 15th Feb. During this the expected result was to have two cycle events generated – one with zero charge for the period of 15th Feb to 31st Mar, and the other from 1st April to 30th June. Or a consolidated event from 15th Feb to 30th June. Instead one event from 15th Feb to 31st Mar was only generated.
This has been fixed. This fix is part of the subscription management module in Portal_Base package and it is recommended for customers to apply this fix.

3-17578946441

28119223

When in-advance billing was enabled, purchasing discount with a future date to become valid on ACTG_NEXT_T resulted in validation errors.
For example, for an account A1, purchase a monthly cycle forward discount in such a way that it starts from the next accounting start date. You will see a validation error on the END_T. This has been fixed.
This fix is part of the subscription management module in Portal_Base package and it is recommended for customers to apply this fix.

3-16478416701 

28159375

When an adjustment was applied in BRM, the revision number for the balance group was set incorrectly to zero causing data inconsistency between BRM and ECE. This has been fixed.
This fix is part of the subscription management module in Portal_Base package and it is recommended for customers to apply this fix.

3-17558202851 

28261959

For an account with cycle products configured for in-advanced billing, if the billing was run after the specified in-advance billing days, BRM was considering the regular monthly cycle forward event as backdated and was causing the charges to accumulate into the items and bill for the next cycle. This has been fixed. This fix is part of the subscription management and billing modules in Portal_Base package and it is recommended for customers to apply this fix.

3-17306790271 

28278326

Setting purchase start dates for first usage products was not allowed by using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode. This has been fixed. The validation has been altered to allow setting start date if it is not set for first usage products. This fix is part of the subscription management and billing modules in Portal_Base package and it is recommended to apply this fix.

3-17307745081

28379550

With in-advance billing, when the product was cancelled,  the scale was calculated incorrectly as zero for the valid purchased product having an end date set.
This has been fixed and the scale is now set correctly.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.

3-16017296621

28463525

The rerating flow was not updating the session_obj and rerated_obj for cycle discounts correctly. When the rerating was done on cycle discounts,

  • Adjustment was created properly, and negative balance impacts was done successfully. This also correctly updated the session object with the original event.
  • But when the shadow rerated event was created, it did not update session_obj with the original event causing it to be not picked up in the corrective invoice.
  • Also rerated_obj of adjustment was not updated with the new shadow event.

This has been fixed. Now when the shadow event is created, the corresponding session object is updated with the original event and the rerated_obj of adjustment is updated with the new shadow event.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.

3-17732092221

28490339

During billing, if the product's END_T is same as ACTG_NEXT_T, END_T in the corresponding cycle-arrear event was incorrectly set. This was causing Pipeline Manager to set incorrect validity dates for the resource validity buckets.
This has been fixed. A check has been added to skip setting date if END_T matches exactly with ACTG_NEXT_T.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.
 

3-18039304221

28543517

During subscription transfer, automatic account creation (AAC) details of the source service was not copied to the newly created service. If a service S1 having AAC_PROMO_CODE was transferred from account A1 to account A2, the service transfer was happening, but the AAC_PROMO_CODE was missing in the transferred service.
This has been fixed.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.

3-17768551081

28588794

When an account with sequential discounting was updated using the PCM_OP_CUST_MODIFY_CUSTOMER opcode, multiple discount balance impacts were created, instead of just one.
This has been fixed.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.

3-18187073311

28631059

A memory leak was observed in the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode flow.
This has been fixed.
This fix is part of the subscription management in Portal_Base package and it is recommended to apply this fix.

 

Web Services Manager 

Customer Reported Issues on Web Services Manager

SR Number

Bug Number

Description

3-17433817794

28089238

The date format in Web Services Manager could not be configured based on the Java's SimpleDateFormat specification. The format was fixed as "yyyy:mm:ddThh24:mi:ss". This has been fixed with the following configurable options in Infranet.properties of Web Services Manager.
webservices.output.date.prefixunixtstamp=true 
webservices.output.date.format=dd/mm/yy hh:mm a
You can configure the format as per SimpleDateFormat specification of Java. If the field is not configured, the default format used would be "yyyy:mm:ddThh24:mi:ss" and unix time stamp is not prefixed.
Please note that the XSL transformation has been modified to use <xsd:string> instead of <xsd:datetime>, so that the timestamp is treated as String/Anytype henceforth. If you have generated the custom webservices WAR it is advised that you regenerate using the new XSL transformation, so that the new configurable options for date formats are considered.
This fix is part of the Web Services Manager package and it is recommended for customers to apply this fix.

3-17592184931

28366498

Web Services Manager was not logging the opcode’s output data and the time taken to execute the web service call in the XML format. The input data was printed in XML format, but the output data was printed only in the Flist format.
This has been fixed.  Web Services Manager has been enhanced to print

  • Opcode input and output in XML
  • Opcode Name as String
  • Latency in milliseconds - with details on individual latencies for XML to Flist, opcode execution in CM and Flist to XML operations.
  • Total round trip latency.

This fix is part of the Web Services Manager package and it is recommended to apply this fix.

 

 

 

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
 Customer-Reported Fixes
 
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.