My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 12 (Doc ID 2015452.1)

Last updated on MAY 12, 2021

Applies to:

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

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 12 is released on 29 May 2015.
This announcement lists the enhancements and fixes delivered in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 12. 

Patch ID: <Patch 20873429>

 

Note 1:

If you are upgrading to BRM 7.5 Patch Set 12, install the mandatory interim <patch 21231092>, which enables BRM to work with the following releases:

 

Note 2:

Localization patches are available for download for the following languages:



Key Enhancements

Billing Enhancements for Improved Performance


Customer Management Enhancements

With this patch set, the following enhancements are available


Rated Event Loader Enhancements

With this patch set, Rated Event Loader (REL) has been enhanced to load pre-processed events from Elastic Charging Engine (ECE) of BRM.

Rating Enhancements

With this patch set, the following rating enhancements have been included:


Security Enhancements

With this patch set, BRM is now more secured with the support of secured communication (SSL/TLS) between

 

Summary of fixes to customer-reported tickets delivered in 7.5 Patch Set 12:

SR Number

Bug Number

Issues fixed

3-5896168931

14498154

When cleaning up the completed rerate jobs with the pin_rerate utility, the process was returning with error and the purging was not successfully completed.

3-7755663121

17422610

When accounts were migrated using Conversion Manager, the billinfo POID was populated with the type as /billinfo% instead of /billinfo and the ID was incorrect.

3-7705325011

17666544, 17736769

With Conversion Manager, when migrating accounts, bad files were getting generated for purchased products and purchased discounts.

3-7930330891

17766399

Conversion Manager was not:

  • Assigning credit profiles correctly. The credit limit and credit floor were populated with zero instead of NULL.
  • Supporting the credit_thresholds_fixed tag.

3-8235143371

18511981

In Conversion Manager, during the migration of accounts with profiles related to extended rating attributes, the reference count value in profile_serv_extrating_t was always set to 1, instead of the actual value.

3-8855539641

18673846

When generating an invoice for an account with sponsored charges rolled up, the events from /config/invoice_events were not considered and hence the invoice event types were not filtered for the sponsored charges.

3-7596524091

19140671, 20558999

The Rated Event (RE) Loader was failing with the POID range issue.

3-9424735361

19488357

The PCM_OP_SUBSCRIPTION_SET_BUNDLE opcode was resulting in balance group locking, due to an unnecessary rating call for the /event/billing/suppression, /event/billing/bundle, /event/billing/bundle/create, and /event/billing/bundle/modify events for which the RUM information was not properly configured in the /config/rum object.

3-9513800701

19688970, 20564179

When a terminate request (AAA) in Direct Debit mode was processed for an unbilled account, intermittent timeouts were observed.

3-9500867391

19896391

The duplicate check functionality was not working as expected in Pipeline Manager and was resulting in an unique constraint violation error when trying to persist in the database.

3-8254002681

19911447

Loading the USC Map DAT module was taking a lot of memory, when .* was used as a regular expression.

3-9765366348

19919863

When the pin_ledger_report utility was run in export mode it was failing.

3-9984434411

20187975

The watermark on a duplicate invoice generated through BIP was constant and there was no provision to configure a different watermark. With this release, you can now configure the watermark using the entries in Infranet.properties file.

3-9753446251

20197522

The start time of an active session was being incorrectly modified during reauthorization. This was impacting the incorrect balance buckets.

3-9495753081

20220828

When the collections process was trying to add a config scenario data to its cache, a message was incorrectly logged as an error into the log file.

3-9829284161

20229069

When a monthly cycle forward non-currency resource deal, which was providing resources one month in advance and without proration, was canceled, valid_to of respective sub balance in bal_grp_sub_bals_t was not updated based on the cancellation date.

3-9951038171

20229074

The pin_ledger_report utility in detailed mode was not returning the correct report due to incomplete calculations without account number and item number information.

3-9484526921

20236481, 20462699

 The best pricing calculation was incorrectly calculating the alternative price during rerating.

3-10000421741

20262918

For an account with multiple balance groups, with an active session in progress, the subsequent authorization or re-authorization flows involving discounting were reporting a credit check failure.

3-7427949411

20301369

Due to the lack of synchronization of threads for logging, for higher log levels the threads were waiting longer times affecting performance.

3-10031473161

20310218

When a product was canceled, the applicable credits were not applied.

3-10023359921

20318012

With Number Administration Center, the device.useglobalsearch = true configuration parameter was not actually resulting in a global search.

3-9885466281

20331918

With Collections Manager, PCM_OP_COLLECTIONS_TAKE_ACTION opcode was failing when run through PCM_OP_ACT_SCHEDULE opcode without the required DUE_T information.

3-10003034921

20331920

For an account with tax exemptions, the tax calculation flow was incorrectly dropping the data related to exemptions and subsequently causing the account to be taxed.

3-9704723441

20345113

Whenever a rollover product end date coincides with the billing date for the account, the rollover was not happening properly.

3-10117682977

20371184

A discount configured with scale of zero (0) was causing the discount to be applied twice.

3-9712476101

20375902

In Customer Center, an error message was displayed when viewing a plan detail containing an offering which was deleted from the system.

3-10010476311

20375906

While rating an event, the rating cache was returning invalid information resulting in incorrect balance impacts.

3-10019459157

20386251

When billing day of the month was updated with the offset of more than two cycles, the valid_to field was incorrectly populated based on next_t instead of future_t.

3-9985167281

20393441

When an account closure is scheduled using Customer Center for a future date creating a scheduler object, it was observed that the last_status and laststat_cmnt fields were updated even before the actual status change.

3-10037858781

20401985

When a product with the Charge for the entire cycle proration setting was purchased for an account and canceled before the cycle ended, the entire charges for the product was incorrectly refunded.

3-10144245101

20416284

When an account was created with a long cycle, the sub balances with non-currency resources were having an incorrect valid_to value.

3-9953216281

20422775

While discounting, rounding was done incorrectly if the precision was more than 15 digits after decimal point.

3-10176053261

20432187

With Automated Monitor Setup (AMS) configuration for Balance Monitoring, for every rerating request, an extra rerating job was created causing an accumulation of rerating jobs.

3-10187518331

20436888

When calling PCM_OP_SUBSCRIPTION_SET_PRODINFO to set cycle_end_t to 0, the values for charged_from_t was incorrectly aligning with charged_to_t and cycle_fee_start_t was incorrectly aligning with cycle_fee_end_t.

3-10105991631

20450292

During trial billing, for a purchased product starting from billing DOM, charge_from was incorrectly calculated.

3-10128809191

20452428

In a multidatabase system, the offer profile tables were not replicated.

3-10117542611

20462695

While purchasing a deal, the purchased product's purchase or cycle or usage end date was set one day less than the expected date.

3-10180364211

20471105

In a multischema environment, the payment reversals could be done multiple times from each schema, because the lookup for an already executed payment reversal was not processed globally across all the schema, for a particular payment.

3-10051409151

20479692

The Plan Transition was failing for member services when it required a status update to those member services.

3-8959105771

20527047

When Login Exclusion was configured, the system was still performing a login search first instead of just the aliases search for that login.

3-8892430511

20534430

The PCM_OP_SUBSCRIPTION_READ_ACCT_PRODUCTS opcode was generating core due to an uninitialized cookie after each iteration.

3-10000209801

20583621

The PCM_OP_SUBSCRIPTION_CANCEL_DISCOUNT opcode was not saving the value passed in for PIN_FLD_DESCR into the generated cancel event.

3-10353697641

20645464

During the subscription transfer operation, a rerate job was created with an incorrect start date.

3-10334546841

20654250

Rerating operation was failing when trying to back out monitor update events belonging to a previous bill cycle.

3-10301779691

20677976

When a subscriber who had entered into a Promise-To-Pay agreement, even after fulfilling the agreement by paying an amount more than actually promised, the subscriber was not coming out of the Promise-To-Pay agreement.

3-10375299561

20720288

With a billing DOM of first of a month, ACTG_NEXT_T set to 1 and advance_bill_cycle also set to 1, for the month of March the value of ACTG_FUTURE_T was incorrectly set.

3-10286852131

20733490

The PCM_OP_BULK_DELETE_OBJ opcode was failing to delete when called from within a transaction on an object type without specifying any objects to delete.

3-10249511381

20736200, 20802638, 20816269

The performance of pin_ledger_report was degraded due to the introduction of the get_gl_bill_t stored function.

3-9529076071

20785075

MTA's search feature was not working.

3-10179553901

20785078

In the Suspense Manager, while reprocessing a suspended CDR, there was an error when querying for the EDR version information and when parsing the recycled CDR for rating.

3-10450819691

20785084

The charged amount values against individual RUMs were incorrect in the Charge Packets for fixed charge calls when such calls overlapped multiple time zones.

3-10341449171

20805907

During the step search, when an error condition was met, step_end was not explicitly called resulting in further errors.

3-10434604941

20827663

In Collections Manager, the Next Payment Due field name was changed to Payment Due because it was not correctly representing the field.

3-10438654581

20832904

In Collections Manager, the Promise-To-Pay actions agent information was not updated.

3-9771430971

20839673

When the pin_inv_accts utility was run with PIN_BILL_FLG_SKIPPED_BILL, the utility was not adding information on failed bill objects into failed accounts' audit objects. This used to leave incomplete failed accounts audit objects.

3-10018355111

20843636

The data manager for IMDB Cache (TimesTen) was generating core.

3-10127021691

20854256

 A row lock contentions were observed during transactions opened when pin_deferred_act was run.

 

 

 

 

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
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.