My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 12.0 Patch Set 1 (Doc ID 2454366.1)

Last updated on JANUARY 16, 2020

Applies to:

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

Details

Oracle Communications Billing and Revenue Management 12.0 Patch Set 1 (12.0.0.1.0) is released on 28 September 2018.
This announcement lists the enhancements and fixes delivered in Oracle Communications Billing and Revenue Management (BRM) 12.0 Patch Set 1.


Patch ID: 28630668

Key Enhancements

Billing Enhancements for Improved Performance for Large Wholesale Accounts

Wholesale business accounts with large account hierarchies can affect the billing and invoicing performance if the accounts had a large number of billing items to be processed. This enhancement allows BRM to consolidate the charges, discounts, A/R items, bill items, journals, and taxes across the services under the wholesale business account and perform the A/R operations, billing, and invoicing at the wholesale business account level. This improves the billing and invoicing performance for wholesale accounts with large hierarchies.

Billing Enhancements for Improved Performance for Large Wholesale Accounts

Billing Care Enhancements

  1. Billing SDK supports customizing the purchase flow and assets display
  2. Billing Care now allows you to search for:
    • Specific bills by using bill number
    • The last generated bill
    • Bills generated between specific dates by using date range
  3. Billing Care supports
    • Backdated account creation and product purchase
    • Creating wholesale accounts and billing hierarchies
    • Customizing product information post account creation
    • Deferred actions
    • Multi schema
    • Undefined payment method

Certifications

With this patch set BRM 12.0 has been certified with

Billing Care and Business Operations Center are now certified with

For more information see product documentation.

Summary of fixes to customer-reported tickets delivered in BRM 12.0 Patch Set 1:

Customer Reported Fixes in BRM

SR Number

Bug Number

Issue Fixed

3-15289852771

26810954

Web Services Manager was not fully compliant to SOAP 1.2 format.

3-15224841731

26810956

27241793

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

3-15019554421

26913721

After a service transfer from one account to another using the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode, the UNIQUENESS_T table was not updated with the correct account POID causing a mismatch with the correct account POID in the SERVICE_T table.

3-15423599201

26954698

For a quarterly billing cycle, the accounting dates were calculated incorrectly and this resulted in incorrect accounting periods.

3-14874018361

26961858

Refunding a fixed discount was incorrectly causing the refund of extra charges or other charges.

3-15698161021

26968649

Conversion Manager was throwing an error when the input XML contains a comma (,) in it.

3-15795611881

26980059

During product cancellation, while setting the product's charged period dates based on proration settings, the in-advance bill period was also being considered and this was causing inconsistencies.

3-15360658251

26990857

27577925

Authorization was incorrectly granting more than the available shared resource.

3-15704767301

27001622

In Collections Manager, when a scenario is replaced with another, the due date calculated for collection actions was incorrect.

3-15224336401

27001628

In Collections Manager, there was a deadlock situation during the collections process.

3-15833386211

27001631

When getting the aggregated information about a resource from BRM, the process was failing if the events for those resources were purged in the system.

3-15122787861

27016775

After the backdated modification of the discount end time (END_T), the charges were calculated incorrectly if sequential discounting was enabled.

3-15504857121

27023170

The PIN_ERR_LOG_FLIST function was generating core dump when any field in the flist logged was null.

3-15377635591

27049618

The 32-bit BRM client applications were not working properly with large files on Linux platforms.

3-15805511541

27060891

When the pin_collections_process utility was run, if the event POID was sent as null in the input flist while calling the PCM_OP_AR_RESOURCE_AGGREGATION opcode, it was dumping core instead of returning a proper error message.

3-15808938171

27067419

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

27067422

The discount purchase was failing when the discount validity was set to full or none.

NA

27116849

The tax percentages were not properly getting accumulated in the balance impact of the rated event.

3-15833122031

27130470

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

3-15600725291

27159336

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

27159380

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

27159381

There was a need to reassign the range for custom fields.

3-16016616727

27178506

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

3-15943051481

27181445

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

3-16240915721

27199237

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

3-15979537621

27202235

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

3-15997352581

27213533

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

3-16129441831

27219879

The pin_recover utility in the -rfr mode was not updating the result to zero in the charge event.

3-11520912431

27223026

The subscription transfer workflow was not allowing to use the custom logic to control the rerate requests through policy.

3-15695482521

27226303

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

3-14772175791

27229728

While loading offer profiles into BRM , the "Double Free Or Corruption" error was displayed.

3-16342460241

27236217

Rated Event Loader Daemon did not process backlog files and went into sleep mode.

3-15233536061

27244352

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

3-15767584081

27263078

Duplicate events were created for the same period for cycle-forward products and the events did not have any balance impacts associated with them.

3-16228876211

27266272

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

3-16419713011

27269943

The host name was not validated properly during the BRM installation in silent mode.

3-16013792861

27274074

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

3-15922064081

27274076

For time-based full discounts, BRM was incorrectly calculating the discount amount.

3-16186268621

27277544

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

3-16306116151

27288519

For accounts with multiple bill units, write off reversal was failing as the reversal items pointed to one bill unit.

3-16386155841

27304029

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

3-16117097141

27304030

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

3-16335738541

27309569

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

27309573

The pin_deposit utility was not collecting pre-authorized charges.

3-16103454181

27337657

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

3-16407795601

27362564

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

27369059

System discounts for cycle arrear events were not applied properly.

3-15223564141

3-15882582121

27389701

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

3-15832032811

27415116

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

3-16323836501

27418546

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

27425461

When installing BRM in silent mode, the response file required the database system user password which was a potential security risk. 

3-16634162461

27448146

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

3-16380399871

27463239

Launching Suspense 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-16174721771

27463244

The General Ledger job was taking more time than expected and required a performance update. 

3-16264990561

27507372

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

3-16547489391

27523584

Rerating after purchasing a discount was not working as expected. 

3-16250465901

27523592

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

3-16628324941

27539381

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

3-15870945191

27539388

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

27552474

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

3-15922729871

27584537

Conversion Manager was not handling migration of accounts with quarterly bill cycles properly. 

3-16512320161

27591136

27738257

When event adjustment was done after tax-only adjustment, the tax jurisdiction information was not updated properly in the balance impact of the event adjustment. 

3-15903641491

3-16506227591

27613611

27613617

28149096

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

 

3-16653172661

27613636

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

3-16932753911

27621461

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

3-13832582461

27667959

While recovering the failed payment, duplicate transaction IDs were observed and this was due to running two applications to recover the same failed payment, one was pin_recover and the other was a custom application, in parallel. 

3-16984338771

27667961

The General Ledger job was taking more time than expected and required a performance update. 

3-16818528141

27684532

In Collections Manager, if the PCM_OP_COLLECTIONS_GET_ACTION_HISTORY opcode was triggered with a transaction having a database number different from that of the collection event user, the opcode was failing. 

3-15685481061

27691744

For an account with multiple bill units, a payment reversal for a backdated account level payment was having effective date as the current system date instead of the back date. 

3-16969300921

27745481

The Oracle Data Manager process was failing with dumping core when processing the Account Receivables workflow. 

3-17041510991

27745484

BRM was not providing options to control or customize workflow over rerate requests which were created as part of subscription transfer operation. 

3-16813237871

27745489

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

3-16449323311

27751025

The PCM_OP_AR_RESOURCE_AGGREGATION opcode was returning incorrect aggregated amount. 

3-16825381141

27771916

The cancel discount operation was not setting the validity dates properly for discounts for which the end dates were in previous cycles. 

3-16736341981

27795345

If sequential discounting was enabled, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was not working properly for in-advance billing periods. 

3-17062080421

27816387

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

3-16926420921

27881741

When an event was rerated twice, the tax jurisdiction was not handled properly for adjustment events. 

3-16672265011  

27881743              

When the same product was purchased twice, cancelling one of the product deleted the provisioning tag from both the products. 

3-17181472981

27881746

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. 

3-16778875601

27891324

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 

3-17204427041

27894048

The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan. 

3-17010229176

27894050

During item adjustment, the search operation got into a infinite loop. 

3-16428542811

27938633

The dm_fusa front end was not receiving data after the connection manager established connection with it. 

3-17136830661  

27938637

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 (/). 

3-16509283701

27938640

The PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode was not allowing to add or modify the event data in its workflow through the PCM_OP_BILL_POL_GET_EVENT_SPECIFIC_DETAILS policy opcode. 

3-17133778471

27956401

In Collections Manager, the collection write-off was failing for the bill unit in collection. 

3-16882624611

27979521

The PCM_OP_SEARCH base opcode was failing when the template included a nested select query with the grouping by clause. 

3-17025208951

27993358

During billing, the grantor information in the rollover bucket was incorrectly set to null. 

3-17399412831

27993360

In LDAP Manager, the entry update operation was failing. 

NA

28007850

When rating an event, sponsored products were ignored. 

3-17087785401

28020470

If a service had two products and when one product was cancelled, the EFFECTIVE_T value of the service was also updated. This was not allowing the processing of usage events for the other product. 

3-17232910091                 

28089237

Quarterly cycles were getting merged which caused issues in applying charges. 

3-17433817794

28089239

The date format in Web Services Manager could not be configured based on the Java's SimpleDateFormat specification. 

3-17578946441

28119224

When in-advance billing was enabled, purchasing discount with a future date to become valid on ACTG_NEXT_T resulted in validation errors. 

3-17548004211

28123147

Coversion Manager was not providing an option to capture bill_accounting_cycles_left and next_bill_t information for migration. 

3-17548989291

28141241

The dm_ldap process was failing to start when SSL was enabled. 

3-17298474221

28141243

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. 

3-16478416701                 

28159376

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. 

3-17558077599  

28200056

After purchasing the monthly cycle forward product, the newsfeed for the same did not include the bill unit information. 

3-17120015936                 

28220691

When there were multiple bill adjustments, reallocation of the payment was done incorrectly. 

3-17331083621                 

28247287

The bill generated using Bill Now was not including all items due for billing. 

3-17302144931                 

28255178

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

NA

28259108

When an APN Map was reloaded using a semaphore, the rating functionality did not consider the new APN Map configuration. 

3-17558202851                 

28261961

BRM was considering the regular monthly cycle forward event as backdated if the billing was run after the specified in-advance billing days in the same month. 

3-17600593901  

28261967

For cycle forward events, having discounts the newsfeed functionality was not working. 

3-17306790271  

28278327

Setting purchase start dates for first usage products was not allowed by using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode. 

3-7711865221                   

28281697

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. 

3-17586682391                 

28334999

In case of sequential discounting, expired or ended discounts were also applied when new discounts were purchased. 

3-17681700281                 

28342603

When an account was created, the ACCOUNT_NO value was not updated correctly in the UNIQUE_ACCT_NO_T table. 

3-17540344751                 

28342608

The event adjustment for the product configured for deferred taxes was not updating the tax jurisdiction information in the balance impacts correctly. 

3-16857082511  

28366495

There were memory leaks observed in the PCM_OP_TCF_AAA_STOP_ACCOUNTING opcode workflow. 

3-17834273241  

28366497

There was a memory leaks observed in the op_tcf_aaa_search_session workflow. 

3-17223827112

28379547

In a BRM system integrated with ECE, External Manager (EM) Gateway was causing errors which led to data inconsistency. 

NA

28379549

When the updated pricing data was loaded using semaphore, the charges were calculated incorrectly. 

3-17307745081

28379551

With in-advance billing, the scale was calculated incorrectly as zero for a valid purchased product having an end date set. 

3-17867436786

28415082

The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan. 

3-16017296621  

28463456

The rerating flow was not updating the session_obj and rerated_obj information correctly. 

3-16159206021  

28466613

When doing a plan transition, it was not possible to override the resource balance granted or add any custom workflow. 

3-15944105871

28359386

28359381

In Collections Manager, if schedule object was either completed or cancelled, it was effective only for collection group owners, but not for members. 

 

 

Customer Reported Fixes in Billing Care

SR Number

Bug Number

Description

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

27423362

When an attempt was made to open details using the account number hyperlink in the Payment Suspense Page Audit trail, it was opening the incorrect Suspense Account page. 

3-16726467291

27500263

When a payment was made and then reversed, if a comment was added under reversal section, it was not visible unless the Payment Details dialog box was reopened. 

3-16982060751

27698947

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

3-15485573861

27722599

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

3-16918562891

27771469

If a bill contains charges from subordinate bill units, the items were getting over allocated. 

3-17110341365                 

27823059

The first column was Name in the Allocate Adjustment screen instead of Account. 

3-17102959567                 

27828889

The Payment Allocation screen displayed the account POID instead of the account number. 

3-17069559841

27874943

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. 

3-16991351901

27874945

While purchasing product/discount, the dates were not displaying correctly if there were timezone differences. 

3-16770126831

27924915

Using the Billing Care SDK, it was not possible to customize the purchase deal screen and add a few custom fields. Also it was not possible to display the new fields in the asset display screen, changing the start /end date and change the overridden amount. 

3-17270002631

27931964

If a bundle was purchased with an override amount, the override amount was not accepted if it included ",". 

3-17304458501

27938642

The date in the Payment Reversal page after posting a comment was not displayed correctly unless the page was refreshed. Also, the first comment was not visible. 

3-17515609821

28206783

Whenever a customization was added to Billing Care, the cache was not getting refreshed automatically. The user had to clear the browser cache and relogin. 

3-17402905141                 

28220688

The override amount was not being retained when the product status was changed to active. 

3-17346452171

28261963

The search results in the Payment Suspense screen was not displaying all the records as per the set pagination limit. 

3-17876082331

28431427

The Account Details page for an account with multiple bill units was taking more time to open which was leading to time out. 

3-17885661511

28543514

When a credit adjustment was applied to a bill with no dues, the Event Adjustment column in the adjust event actions screen was showing only the tax part of the event adjustment instead of the full adjustment amount. 

3-17489789341

28543965

The DataModelGenerator utility was not generating custom XSD for custom objects available in BRM. 

3-17847475681                 

28543979

When Billing Care submitted the batch payments through Lockbox file, the entire file was rolled back if it included under payments. 

3-17943001841                 

28543981

Account details were not being displayed in the Billing Care Collections Page after implementing custom collections scenario and customizing the policy opcode. 

 

 

 

 

 

 

 

 

 

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
 Billing Enhancements for Improved Performance for Large Wholesale Accounts
 Billing Care Enhancements
 Certifications
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.