My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 18 (Doc ID 2259714.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 18 (7.5.0.18.0) is released on 28 April 2017.

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

Patch ID: <Patch 25596735>

 

Key Enhancements

 Account Receivables Enhancements

In previous releases, you could perform bill-level adjustments only for the remaining due amount (current bill due) for a fully or partially paid bill. But with this release you can improve the performance of bill level adjustments for fully or partial paid bills.

 Billing Enhancements

With this release you can collect the G/L data even for Trial Billing.

 BillingCare Enhancements

BillingCare SDK now provides customization options for setting up search criteria for suspended payments based on your business requirements.

 Customer Management Enhancements

Now you can speed up the retrieval of product details during product purchase by configuring the system to fetch information directly from database, rather than by reading a large number of rate-plans in cache.

 Certifications

BRM 7.5 is now certified with Perl 5.24.0.

 

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

 

SR Number

Bug Number

Issues Fixed

3-14061077121

25550034

After assigning a role (user) to an account, suspense payment allocation to that account was failing.

3-14098212791

25550036

 During an adjustment, when an amount was entered with a comma or an amount with a comma was edited, the adjustment operation failed.

3-14068138991

25597318

 In Oracle Communications Billing Care, when a payment was made to an account and then moved to suspense, followed by a role (user) assignment, upon querying the system, the correct assignee was not fetched by the user interface.

3-14472451743

25725595

 In Billing Care, in the Hierarchy screen, instead of displaying the account number, the account POID was displayed.

3-6840187551

16452443

 When a billing delay was configured with a specific time zone, the account was not billed immediately after the delay period, because the delay end date was not rounded to midnight.

3-8680637521

18413221

 During migration, Conversion Manager was not updating the profile_serv_extrating_t.status information.

3-12068971221

22681654

 When the PCM_OP_CUST_MODIFY_CUSTOMER opcode is invoked to transfer a balance group to a new bill unit, fm_subs_service_balgrp_transfer_create_event returns an error indicating PIN_ERR_NONEXISTANT_POID.

3-12542642001

23152228

 While adding a zone map, Oracle Data Manager displayed an error even when the zone added was correct.

3-13207523901

24491176

 Connection Manager returns a validation error because of inconsistent length of the PI_USER_ID, CORRELATION_ID, and EXTERNAL_USER_ID columns in the USER_ACTIVITY_T table.

3-13305792511

24668579

 After terminating a sharing group profile, the subsequent billing process failed because of the invalid ordered balance group for recurring cycle fees.

3-13524642831

24951997

 When there was a database connection time out, Oracle Data Manager was dumping core.

3-13573525811

25029365

25449664

 Vertex Data Manager rounds off only up to five decimals, while Vertex Communications Tax Q (CTQ) Series 6 supports the number of decimal places.

3-13338336781

25063374

 While recording an activity in BRM by calling PCM_OP_ACT_ACTIVITY, Connection Manager returns the PIN_ERR_NO_MEM error.

3-12947507881

25091034

 Issues in shared memory management was causing Oracle Data Manager to exit with a core dump.

3-13472287511

25123938

25183512

 Due to thread safety issues, Pipeline Manager was crashing when CRITICAL errors were reported in multiple pipelines at the same time.

3-13542781371

25135167

 For a cycle arrears charge, when a prorated discount was configured at the account level and it was valid only till the middle of cycle, the prorated discount was not applied if both the discount and the service were cancelled on the same date.

3-13625140111

25153115

 A backdated purchase deal operation was not considering the backdated timestamp that was provided as input in the END_T table.

3-13546068891 3-14381630221

25153126

25754938

 Oracle Data Manager front-end process appeared to be stuck when writing an error message.

3-13113661251

25153130

 Notification to DM_AQ fails when published using a new PCM context.

3-13795594741

25212239

 The billing process found to have performance issues when the system encountered large number of rate plans.

3-13398571066

25216293

 When a backdated cycle arrears product was cancelled, the discount was not refunded.

3-13313629991

25239758

 Vertex Data Manager did not capture the additional details that CTQ was sending about jurisdiction tax information.

3-13799140661

25252132

 In Customer Center, when the permission (/accounttool/araccess) to access account receivables was set to read-only, the customer service representative (CSR) was not able to view the events data.

3-13620339771

25257283

 When a CSR’s account credentials with only the admin_client service was used, Developer Center did not connect to BRM.

3-13734860181

25260496

 Generation of product subscription report through Oracle Business Intelligence Publisher (BIP) took much longer time than expected.

3-13352676671

25286694

 BRM JCA Resource Adapter had issues connecting to BRM.

3-13821721911

25291179

 When tax-only adjustment was done on an event that had a charge, discount, and a tax-balance impact, the tax amount calculated was incorrect.

3-13830581521

25330942

 Pipeline Manager was not considering an additional custom block in the recycle pipeline.

3-13977677641

25366578

 When the reversal of suspense payment was done, the specified reason code was not considered.

3-13966999801

25368307

 There was a data corruption issue in the PCM_OP_AR_REVERSE_WRITEOFF opcode that was making DB_ID of POIDs invalid.

3-14032769211

25390783

 During rerating with ECE, the PCM_OP_RATE_ECE_RATE_EVENT opcode was generating an error because BRM did not support currency-based rate plan in the rerating workflow.

3-13443399571

25392597

25533633

 BRM was not supporting Discover Diner's club cards.

3-13994227971

25392601

 If the first customer order was a separate step after the account creation, Bill Now was failing with errors. This was due to calling the PCM_OP_ACT_USAGE opcode in the Bill Now workflow in the CALC_ONLY mode. In this case, the cycle dates were calculated incorrectly leading to the error while fetching the required rate plans.

3-13587184518

25392708

 In the Payment Details dialog, Billing Care required viewing and traceability of payments by showing both transaction ID and payment ID.

3-13993841711

25428475

 There were some issues with refunds because the original charge information was a mandatory input for the operation.

3-14074130271

25533630

 The Trial Billing process was not generating journals.

 Support for generating journals can be added by setting the value of the PerfAdvancedTuningSettings field in the billing instance to 64.

3-14114368231

25548992

 BRM Vertex Data Manager was not caching the location and rate data even though caching was enabled in the CTQ configuration files.

3-12997396951

25549663

 When PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO was invoked, the configured discount for recurring fees was not applied correctly.

3-14143676731

25590020

 Billing failed when the PCM_OP_ACT_USAGE was called in the billing workflow in the CALC_ONLY mode. While fetching the required rate plans, the cycle dates were calculated incorrectly leading to an error.

3-13264171831

25590023

 In Pipeline Manager, because the charge packets were not populated with proper RUM_ID, pipeline was not differentiating between multi-RUM and single-RUM scenarios, which resulted in incorrect rated and unrated quantity during re-authorization.

3-14057864471

25590026

 When transferring a balance group, the value of END_T was not being used as-is, which was causing the validity of the bundle being set to a wrong time stamp.

3-13747453381

25594145

 When a cycle arrears product with the prorate_full configuration was cancelled on the same day as purchase, the discount proration was done, which is incorrect.

3-13791538961

25651351

 In Customer Center, there was an issue in creating a customer account with some specific plans.

3-14307011981

25651354

 When a user logs in to Collections Center as an agent, the refresh functionality did not work properly and the account information was not displayed.

3-14370068511

25744510

 In Customer Center, when allocating an adjustment to a bill (with bill numbers in a custom format), an error was encountered.

3-14249145251

25822151

 Direct Debit checkpoint payment was failing to create proper event records in the BRM database. This occured because it did not call the PCM_OP_RATE_POL_POST_RATING opcode in the workflow for a failed check pointed payment.

 

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