My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 21 (Doc ID 2392069.1)

Last updated on AUGUST 16, 2019

Applies to:

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

Details

 

Oracle Communications Billing and Revenue Management 7.5 Patch Set 21 (7.5.0.21.0) is released on 26 April 2018.

This announcement lists the enhancements and fixes delivered in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 21.

Patch ID: <Patch 27603295>

Key Enhancements

Delay Interval Can be Configured for Resolving Failed Payments

In previous releases, when the pin_recover utility and a custom application were run in parallel to resolve failed credit card or debit card payments, duplicate transaction IDs were created for such transactions.

With this patch, a new entry, event_search_delay, has been introduced in the BRM_home/apps/pin_billd/pin.conf file to specify the delay interval for resolving failed payments. You can now run the pin_recover utility with event_search_delay to delay the search of events so that pin_recover processes only the events that were created before the specified delay interval.

 

BRM 7.5 Is Now Certified with Perl 5.26.1

With this patch set, BRM 7.5 is certified with Perl 5.26.1.

For more information, see BRM Documentation.

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

Customer Reported Fixes for BRM

SR Number

Bug Number

Issues Fixed

3-15808938171

27067418

 When using Conversion Manager for loading data, the parent account and account receivable details could not be provided at bill-unit level. This was causing issues if the account had multiple bill units.

3-15600725291

27159334

 The audit data retrieved from the database was not in the correct order. As a result, the rerating process was not creating charging events. 

3-16022883521

27159379

 When setting the discount validity dates on cycle boundaries, the discount validity rules were not considered for calculation and this resulted in incorrect discounts. 

3-16016616727

27178505

 Rerating was failing for usage events created on the billing day. 

3-15943051481

27181444

 For hierarchical accounts, bill-level adjustments were not getting synchronized with ECE properly. 

3-16117097141

27183213

 The value for the StopBillClosedAccounts business parameter was always getting set to 1 irrespective of the value specified. 

3-16240915721

27199236

 When applying cycle discounts, full discounts could not be applied due to incorrect discount start dates set by the set_discountinfo opcode. 

3-15979537621

27202234

 When accounts had hierarchical bill units, account deletion was failing. 

3-15997352581

27213532

 When the fetch size reached the maximum limit, the pin_bill_accts utility reported a performance issue. 

3-15695482521

27226302

 In BRM, it was possible to allocate the same adjustment to a bill twice. 

3-15233536061

27244351

 There was no option to disable journal creation for zero (0) balance records. 

3-16380399871

27252301

 Launching Customer Center with Java WebStart had issues due to the version mismatch between the shipped version (4.5.3) and the version specified (4.4) in the orasoft.jnlp file. 

3-16228876211

27266271

 When PDC was used for configuring pricing objects, there was some issue in the Item Type Selector configuration due to format mismatch. 

3-16013792861

27274073

 The discount purchase operation was not considering the appropriate rate plan resulting in incorrect calculation of the discount period. 

3-16186268621

27277543

 When a service configured to have only discounts was terminated, an error was thrown. 

3-16386155841

27304026

 Even if the log level was set to ERROR, some debug messages were getting recorded in the log files. 

3-16335738541

27309568

 The input data for the payment policy opcode, PCM_OP_PYMT_POL_PRE_REFUND, did not contain all the required information for policy processing. 

3-16344647651

27309572

 The pin_deposit utility was not collecting pre-authorized charges. 

3-16407795601

27323287

 In Customer Center, when the permission to access account receivables (/accounttool/araccess) was set to read-only, the customer service representative (CSR) was not able to view the adjustment details from the Bill Details or Item Details page. 

3-16103454181

27337655

 When making adjustments, if the adjustment amount was more than the actual due amount, an inconsistent behavior was observed. 

3-13406072941

27362563

 In multischema systems, after the service transfer, the /uniqueness object was created with the POID of the secondary database instead of the primary database. 

3-15683377181

27369058

 If the sequential discounting was enabled, the system-level discount if configured, was not applied for cycle arrear events. 

3-15833122031

27380777

 There was an issue with state enumerations that was causing a core failure in BRM. 

3-15728021501

27408003

 Customer Center was not supporting the customization of the Account Navigator class.

Customer Center has been enhanced to support this customization.

3-15832032811

27415115

 Rerating events after changing the accounting cycle day of month (DOM) was incorrectly impacting the balances. 

3-16323836501

27418545

 The PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS opcode was not considering the latest or current hierarchy to calculate the amount due from aging buckets. 

3-16634162461

27448145

 When the billing delay was configured, auto-triggered billing from ECE was generating a final bill instead of a partial bill. 

3-16264990561

27507370

 When a product configured with the cycle arrear event was cancelled with a backdated date, the refund was not applied properly. 

3-16547489391

27523583

 Rerating after purchasing a discount was not working as expected. 

3-16250465901

27523591

 When a child account was moved under a parent account, the usage charges were not included in the correct bill. 

3-14581820771

27527125

 Even after cancelling a discount, it remained active and also the discounted amount was not reversed until the end of the current cycle. 

3-16628324941

27539378

 In some cases, while disconnecting a service, the PCM_OPCUST_SET_STATUS opcode was entering a deadlock. 

3-15870945191

27539384

 If sequential discounting was enabled, the subscription discounting was getting applied on top of the system-level discount. This was causing errors in some scenarios. 

3-16424349221

27552473

 During rerating, additional tax balance impacts were created. As a result, the adjustment calculated was incorrect. 

3-16850439811

27554937

 In Cutomer Center, the posted date in the Item Details page was incorrect. 

NA

27577924

 When the credit limit threshold was breached, the authorization was granted for the amount more than the available balance. 

3-15405314431

27584540

 Payment Tool was crashing when an offline payment was allocated for written-off accounts. 

3-16395624221

27606734

 If the cycle DOM for a deactivated service was updated and the service was reactivated after the delay period, duplicate events were retrieved and refunded during the product cancellation. 

3-16653172661

27613632

 During cancellation of a product configured with in-advance billing, incorrect START_T and END_T were set in the events. 

3-17005468741

27677138

 There was a memory issue reported when calling the PCM_OP_ACT_USAGE opcode with a large input flist. 

3-16813237871

27745488

 When the EventAdjustmentDuringcancellation flag was enabled, the flist data corruption issue occurred intermittently, which was dumping core. 

3-15223564141

3-15882582121

26557885

27389700

 Web Services Manager was returning the Cannot intialize error when triggering the opcodes. 

3-15224841731

26810955

27168883

 When the tiered taxation was applied, the tax information was consolidated instead of keeping it separate for each tier. 

3-15903641491

3-16506227591

27613610

27613616

 Rated Event Loader (pin_rel) was exiting due to the out of memory error. 

 

Customer reported fixes in Billing Care

SR Number

Bug Number

Issues Fixed

3-15485573861

26608782

 In Billing Care, in the Payment Details dialog box, the payment allocation table was not aligned properly. 

3-16877587301

27123466

 In Billing Care, it was not possible to customize the Payment Suspense flow to display the last suspended date.

Billing Care has been enhanced to support this customization.

3-16426973211

27375507

 In Billing Care, it was not possible to save the notes in the Payment Details dialog box when the amount was more than 999 and when the payment was added by using opcode. 

3-16877587301

27423360

 In Billing Care, in the Payment Suspense interface, the account number link on the Audit Trail for the Moved to Suspense From entry was opening an incorrect account. 

3-16877587301

27500262

 In Billing Care, the Make a Payment and Reverse Payment dialog boxes were not displaying the notes entered during payments and payment reversals respectively. 

3-16982060751

27698944

 In Billing Care, a performance issue was reported while listing the deals during a product purchase operation. 

 

 

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
 
 Summary of fixes to customer-reported tickets delivered in 7.5 Patch Set 21
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.