My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 12.0 Patch Set 2 (Doc ID 2587265.1)

Last updated on MARCH 12, 2021

Applies to:

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

Details

Oracle Communications Billing and Revenue Management (BRM) 12.0 Patch Set 2 (12.0.0.2.0) is released on 10 September 2019.
This announcement lists the enhancements and fixes delivered in Billing and Revenue Management 12.0 Patch Set 2.

Patch ID: 30094488

Key Enhancements:

New Features in BRM:

Deploying BRM Services on a Cloud Native Environment: BRM, Oracle Communications Pricing Design Center (PDC), Billing Care, and Business Operations Center now support their deployment on a cloud native environment, allowing you to harness the benefits of cloud with the services of BRM.

Wholesale Billing Enhancements: With this enhancement, the following are supported in wholesale billing:

Additional Card Security Presence Values Supported for Card Validation or Authorization: You can customize BRM opcodes to send other card security presence values (such as 9 (No Value)) in the input flist to Paymentech DM. You can use the PIN_FLD_AVAILABLE flist field to provide the card security presence value. 

Card Security Code Is Now Masked in Logs: The PIN_FLD_SECURITY_ID value is masked during logging. The card security codes passed in this field appear as masked fields in logs.

Display Bills Generated Before Moving the Account to a Hierarchy: It is now possible to view the bills that are generated before and after moving the account to a hierarchy with the details (such as item list, event details, A/R actions, and payments) in Billing Care.

Managing Discount Validity Starting or Ending in Future Cycles: With this enhancement, during billing, BRM identifies the discounts that starts or ends in the next billing cycle and sets the discount validity and proration appropriately. For example, if proration for a discount is set to Full discount, full discount is applied even if the discount validity ends in the middle of the next billing cycle.

Wildcard in Item Type Selectors: Oracle Communications Pricing Design Center (PDC) now supports wildcard (*) in item type selectors. By setting the true or false value for the applicableToAllChildServices and applicableToAllChildEvents elements in PDC, you can configure whether all the child services or events of a service or event must be considered for item assignment.

BRM Supports POID Generation in ECE: With this enhancement, POIDs can be generated in ECE. ECE uses Rated Event Formatter to generate the required POIDs.

Support for Stored-Credential Transactions for Payments: BRM now supports payment transactions with stored credentials for VISA, MasterCard, Diners, Discover, JCB, and American Express cards.

Support for Migration of Legacy Data into BRM and ECE in Real Time: Now you can migrate the legacy data completely or incrementally into the BRM system by using the pin_cmt utility and also load all the migrated data into ECE synchronously (in real time).

Support for Migrating Hierarchical Accounts Using Same Input File: Now you can migrate the legacy hierarchical account groups to BRM even if the parent and child accounts in the groups are present in the same XML input file.

Event Rounding Rules Can Be Used for Adjustments: You can now use the rounding rules configured for events in adjustments. For example, if you configured usage events with six decimal precision, the event-level adjustment on the usage fee is rounded to six decimal precision.

New Staging Directory for Exported G/L reports: The pin_ledger_report utility now creates a staging directory named, TEMP_GL_REPORT_STAGING, in the same location as the OutputDirectory and stores the output G/L report files temporarily in this directory before moving them to the OutputDirectory.

BRM Client Applications Supported from 12.0 Patch Set 2

The following BRM client applications are now released in BRM 12.0:

Component

Description

Customer Center

BRM now supports Customer Center (including Customer Center SDK). You can now use Customer Center or Oracle Communications Billing Care for customer management tasks. For more information, see the Customer Center Online Help.

Collections Center

BRM now supports Collections Center. You can now use Collections Center or Billing Care for collections or debt management tasks. For more information, see the Collections Center Online Help.

Configuration Center

BRM now supports Configuration Center.

Field Validation Editor

BRM now supports Field Validation Editor to define how to validate customer data.

Payment Center

BRM now supports Payment Center. You can now use Payment Center or Billing Care instead for payment management tasks. For more information, see the Payment Center Online Help.

Payment Tool

BRM now supports Payment Tool. You can now use Payment Tool or Billing Care for processing payments. For more information, see the Payment Center Online Help.

Pricing Center

BRM now supports Pricing Center. You can now use Pricing Center or Pricing Design Center for creating product offerings for BRM. For more information, see the Pricing Center Online Help.

New Features in Billing Care:

SDK Enhancements for Customizing Billing Care: You can now use the Billing Care SDK and OPSS policies to perform the following in Billing Care:

View Bills Generated Before Moving the Account to a Hierarchy: It is now possible to view the bills that are generated before and after moving the account to a hierarchy in the account's Bills > Switch Bills menu.

Support for Account Number and Bill Number in Billing Care Embeddable URLs: It is now possible to use account number and bill number instead of the corresponding POIDs in Billing Care URLs that are embedded in external applications.

Embeddable URLs for Purchase Package and Purchase Bundle Screens: It is now possible to embed Purchase Package and Purchase Bundle screens into external applications.

New Features in Business Operations Center

Workflow Job to Automate Billing Process: It is now possible to run a workflow job, which can include billing, payment collections, invoices, and refunds. Workflow jobs enable you to automate an end-to-end billing process for better operational efficiency.

 

Customer Reported Fixes in Oracle Communications Billing and Revenue Management 12.0 Patch Set 2

Customer Reported Fixes in BRM 12.0 PS2

Customer Reported Fixes in BRM 12.0 PS2

SR Number

Bug Number

Description of the Issues Fixed

3-15091245471

26618794

 In order to avoid duplicate tax calculation and incorrect tax adjustments, the is_tax_calculated flag was introduced earlier for pipeline rated events. But this caused an issue in the tax calculation during the event adjustment, when the event included had more than one tax balance impact.

This has been fixed.

3-15286560801

27123464

 It was not possible to set the promise-to-pay date as the system date.

This has been fixed. Now, additional validations are added to ensure that the promise-to-pay date is greater than the system date.

3-15853592531

27632734

 Paymentech Data Manager (DM) now supports Customer-Initiated Transaction (CIT) and Merchant-Initiated Transaction (MIT) for processing VISA credit cards.

3-17434540731

27993355

 The POID_ID required an increase in the number of bits from its current value of 44 bits because the allocated range of Portal object IDs (POID) were not sufficient.

This has been now increased to 51 bits.

3-17757279581

28342613

 A payment of zero amount was failing in BRM with an error because there was PIN_FLD_PAYMENT value was not set in the response.

This has been fixed.

3-17757279623

28387497

 BRM was not providing flexibility to set the transaction type for payments processed through Paymentech DM in the PCM_OP_PYMT_POL_PRE_COLLECT policy opcode.

This has been fixed.

3-17747525701

28444532

 Oracle Data Manager was incorrectly logging an error message when insufficient back ends were configured.

This has been fixed and now a warning message is displayed.

3-17796627641

28466602

 Indexes were rebuilt every time the audit tables were purged.

This has been fixed. The purge_audit_tables.pl script has been modified and the indexes are not rebuilt if the $rebuild_indexentry in the BRM_home/sys/archive/oracle/purge_audit_tables.conf file is set to no, where BRM_home is the directory in which you installed BRM components. If this entry is not set or set to any other value, the indexes are rebuilt every time the audit tables are purged.

3-17732092221

28490340

 During the billing process, the end date in a cycle arrear event was set incorrectly when the product end date was the same as the actg_next_t value. This caused the resources to have incorrect validity dates.

This has been fixed.

3-18370747541

28521329

 Paymentech DM now supports CIT and MIT for processing Mastercard, Japan Credit Bureau (JCB), and Diners Club credit cards.

This has been fixed.

3-18039304221

28543518

 During subscription transfer, Adaptec AdvancedRAID Controller (AAC) details (for example, PIN_FLD_AAC_PROMO_CODE) of the service from the source account were not copied to the new service created at the destination account.

This has been fixed.

3-18126737181

28549500

 The pin_recover utility was failing while searching for payments to be recovered.

This has been fixed.

3-17564929691

28552543

 Web Services Manager was always sending the date-time stamp information in Universal Time Coordinated (UTC) as part of the response without considering the actual timezone.

This has been fixed to send the date-time stamp as per the time zone configuration in the BRM_home/deploy/web_services/Infranet.properties file.

3-17790987201

28556710

 

The rerate process did not update the original event.

This has been fixed and some additional criteria has been added to identify and update the corresponding original event during rerating.

3-17612813861

28588801

 During the sequential discounting, non-applicable events were also considered while calculating the periods.

This has been fixed.

3-17757279623

28596194

 The fm_pymt module was not sending transaction type to Paymentech DM.

This has been fixed. Now, transaction type is used by Paymentech DM to identify the type of payment, for example, recurring, installment, and so on.

3-17697487631

28603124

 The scripts in BRM_home/bin was using two different versions of HTTPClient libraries, 4.4 and 4.5.3.

This has been fixed to use only 4.5.3 version.

3-17223827112

28607064

 In a BRM deployment with Oracle Communications Elastic Charging Engine (ECE) as charging engine, when the BRM Oracle Data Manager commit failed, the BRM data was not in synchronization with the ECE cache data.

This has been fixed by triggering a commit to ECE only after the BRM Oracle Data Manager commit is successful.

3-18187073311

28631061

 In the subscription opcode PCM_OP_SUBSCRIPTION_SET_PRODINFO, a memory leak was observed.

This has been fixed.

3-17444287241

28638444

 In the subscription module, during the product cancellation, an incorrect scale for refund was used.

This has been fixed.

3-17803665231

28671913

 The EVENT_POID_LIST required to store longer strings than it was allowed (4000 characters) in the database.

This has been fixed.

3-18188014831

28678759

 A memory leak was observed in flist to string conversion routine.

This has been fixed.

3-17547976531

28689682

 During rerating, the impact type for PIN_IMPACT_TYPE_TAX_RERATED was not being set to PIN_IMPACT_TYPE_TAX, and this was leading to incorrect tax amounts in the invoices.

This has been fixed.

3-17920861571

28700838

 Backdated adjustments were not displayed in the corrective invoices.

This has been fixed.

3-17722323998

28774361

 The PaymentDeallocation feature allows bill adjustment on a zero due bill or a partially paid bill. The same behavior has been now implemented for item and event-level adjustments.

If BillPaymentDeallocation is enabled, do the following to allow the item and event-level adjustments:

  1. Unallocate the payment applied on the corresponding bill item.
  2. Do the item or event-level adjustment.
  3. Reallocate the payment back to the bill item.

If the payment amount is more than the due amount after the adjustment is done, then some unallocated amount is stored in /item/payment. This unallocated amount is displayed in the Adjustment/Payments not applied tab of Customer Center.

3-17519084381

28774366

 If an error is thrown in ECE, the error was always set to PIN_ERR_BAD_VALUE. Hence, it was not possible to identify the actual error details.

This has been fixed.

In case the output flist of the PUBLISH_ECE_EVENT operation contains ERROR_DESCR set to Credit Ceiling Breached, the ebuf is set to PIN_ERR_CREDIT_LIMIT_BREACHED instead of PIN_ERR_BAD_VALUE.

3-18383751591

28780635

 There was an issue of wrong selection of item type when dealing with in-advance billing events. /item/adjustment was created instead of /ite/mcycle_forward_arrear for a cycle_forward_arrear event when billing in-advance was set.

This has been fixed.

3-16906450911

28786829

 The PCM_OP_BILL_MAKE_BILL_NOW opcode was resetting the error buffer set by a policy customization in the workflow.

This has been fixed.

3-17857064951

28794484

 In the subscription module, if END_T passed was earlier than the cycle/purchase/update end dates, then the cycle start and end dates were set incorrectly leading to validation error.

This has been fixed.

3-18482634741

28812794

 The Conversion Manager failed to load data into uniqueness table due to the presence of double quotes.

This has been fixed to parse and omit double quotes in the uniqueness-related functions.

3-18482428661

28812798

 The PCM_OP_AR_BILL_ADJUSTMENT opcode had memory leaks.

This has been fixed.

3-18310735251

28824835

 The Connection Manager module had some memory leaks.

This has been fixed.

3-18505486831

28837038

 In the subscription module, for a backdated purchase done on the billing day of the month, the end date for the event was incorrectly set and this was causing wrong validity periods for the resources both in BRM and Pipeline Manager.

This has been fixed.

3-17857944451

28843066

 The Load Price List utility was failing with core dump while committing or retrieving price list.

This has been fixed.

3-16250214071

28848746

 The Billing Care user interface was not displaying the details of a bill that was generated before the account was moved into a hierarchy.

This has been fixed.

3-18473654211

28848748

 The transaction opening workflow was not returning an error, while trying to open a transaction on a non-existent object.

This has been fixed with proper checks for existence of an object before the object is tried for a lock to open the transaction on it.

3-18631761901

28871778

 The file name format of the General Ledger (G/L) reports generated in XML were different.

This has been fixed to restore the earlier naming format.

3-18664098401

28873152

 Any auditable updates to the account creates an entry in the audit table for au_account_t. In addition, for a transaction that requires data from the audit table, searching in au_account_t was taking considerable time. In such cases, the updates had to fetch effective_t from account_t if au_account_t returned null.

This has been fixed.

3-18368278231

28905266

 When an account is deleted using a wrapper opcode that invokes PCM_OP_CUST_DELETE_ACCT opcode, an error in the workflow did not roll back the changes to /uniqueness object.

This has been fixed.

3-18263789131

28923379

 The PCM_OP_BILL_MAKE_BILL opcode finalized the bill when the workflow was invoked by a process other than pin_bill_accts indicated by the program name field.

This has been fixed to finalize the bill only through the pin_bill_accts utility.

3-19353513291

28944041

 For PCI compliance, it was required to mask the PIN_FLD_SECURITY_ID field in the card attributes structure for enhanced card security.

3-18447694071

28944043

 Paymentech DM has been enhanced to support Card Security Presence and to send Fraud Format Indicator (FR) record when this field is present.

3-18664468631

28944047

 

Paymentech returned duplicate CIT and MIT transaction IDs.

This has been fixed and transaction IDs for CIT and MIT records are generated in a random manner.

3-18713081091

28977386

 Oracle Data Manager was not responding for a long time when PIN_ERR_NO_MEM was returned from the flist copying method.

This has been fixed.

3-18399785331

28997123

 In the subscription module, when multiple discounts were purchased with different validity dates in the same deal, the discounts rules were not set correctly for the individual discounts. The discount validity dates of the first discount was used for all other discounts in the deal.

This has been fixed.

3-18310735251

29017375

 The Connection Manager was dumping core when running pin_deferred_act and pin_bill_day utilities due to memory management issues.

This has been fixed.

3-18370747541

29023518

 Due to the scope of the header file, the customer management module was throwing a symbol look up error.

This has been fixed.

3-18855799201

29036175

 In the subscription module, during the product cancellation operation, the refund amount was calculated incorrectly if it includes in-advance charges. This was due to considering event end date instead of cycle end date for calculating the scale for refund.

This has been fixed.

3-18452678921

29042246

 During the billing delay period for a deployment with the billing delay configuration, any discount cancellation operation was not applying refunds. Only during the delay period this inconsistency was observed as the accounting dates available in the bill unit would not be updated and still reflect the previous cycle information.

This has been fixed with proper checks to handle such events in the delay period.

3-18889790481

29042248

 A memory leak was observed in the customer registration module.

This has been fixed.

3-18793585311

29042250

 In some cases, PCM_OP_EXEC_PROC was not returning the correct response.

This has been fixed.

3-18919001443

29120662

 A memory leak was observed in the Paymentech DM.

This has been fixed.

3-18919001133

29120695

 When creating /payinfo/cc objects, any custom fields passing into the workflow were not dropped, which caused a schema error.

This has been fixed.

3-18693381421

29127140

 In the subscription module, the PCM_OP_SUBSCRIPTION_CANCEL_DEAL opcode caused segmentation fault core dump while processing discounts.

This has been fixed.

3-16749719711

29141791

 When rerating was done before billing, the invoice data received from ECE was not present in the rerated event. Instead, original invoice data was populated in the rerated event.

This has been fixed.

3-18964843081

29146203

 The modify customer operation was not applying the cycle discount information passed in the input due to missing Portal object ID (POID) information in PIN_FLD_DEAL_INFO.

This has been fixed.

3-18125409791

29151194

 In the subscription module, canceling a purchased product with the cycle start date in the future and the purchase and usage start dates in the past, updated the cycle, purchase, and usage start dates.

This has been fixed to update only the cycle start date.

3-18578426961

29151195

 For a purchased product, if either purchase, usage, or cycle end date was changed, the end date for purchase, usage, and cycle were updated.

This has been fixed to update only the date that is changed.

3-18980345811

29174549

 In Collections Manager, the PCM_OP_COLLECTIONS_GROUP_CREATE opcode had memory leaks.

This has been fixed.

3-18644785641

29178997

 Event adjustment was not working as expected if the amount or percentage was not provided in the input. The expectation was to do 100% event adjustment if the amount or percentage value was not provided.

This has been fixed.

3-15270580261

29204382

 In an Application Integration Architecture (AIA) deployed environment, during any transaction where the request is sent from BRM to ECE, if an error occurred in ECE, then AIA was not able to capture the error from BRM.

This has been fixed.

3-15122386111

29221143

 The discount validity rules were not set for the discounts starting or ending in a future cycle as the accounting dates were prone to change.

This has been fixed to identify the discounts during billing that have start or end dates in the next billing cycle and set the validity rules appropriately.

3-18536623001

29265113

 In case of a discount sharing scenario, when multiple reauthorization requests are created, the reservation quantity was not updated and it stayed at sum of the quantity of the first authorization and last reauthorization. In this case, it was possible to reauthorize sessions indefinitely and certain limits were also not enforced. This was leading to revenue leakage.

This has been fixed.

3-19157592761

29278528

 In the subscription module, the plan transition opcode resulted in segmentation fault dumping core.

This has been fixed.

3-18741993071

29342746

 While rating with sponsored product, the credit limit check was done both on the sponsored product and the user product. Due to this, a credit limit breach was reported when the user product sub-balance was positive.

This has been fixed by removing the credit limit check on the user product while rating with the sponsored product.

3-19360664961

29342749

 CPU usage for the Connection Manager module reached and stayed at 100%.

This has been fixed.

3-19278553351

29370866

 In the subscription module, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode failed for an account-level discount.

This has been fixed.

3-18738247231

29376633

 In the Pipeline Manager Framework, a memory leak was reported while converting decimal to string.

This has been fixed.

3-19425603631

29395724

 In a Service Lifecycle Management (SLM)-enabled deployment, when a deal was purchased with balance as zero, the service state was immediately set to recharge_only. This caused usage processing issues in ECE.

This has been fixed. Now, status is not changed to recharge_only as soon as the purchase is completed.

3-19456180091

29409245

 In the subscription module, during the product cancellation operation, the validity end dates for non-currency resources of an in-advance cycle was wrongly set.

This has been fixed.

3-19353513291

29428268

 During the pin_collect process for payments, an error indicating PIN_ERR_PARTIAL was thrown, especially with CIT and MIT transactions.

This has been fixed.

3-17880290091

29441735

 During the billing process, few items were incorrectly filtered during final billing, and it was due to item pruning in cases of billing suppression, suspension, or resume billing.

This has been fixed.

3-18995075711

29441740

 When a back-dated account with a multi-month cycle was moved into a hierarchy, the child account's PIN_FLD_ACTG_NEXT_T did not align with that of the parent account.

This has been fixed. Changes have been made to ensure that the dates are aligned.

3-18731886071

29448150

 Event adjustment was not working properly for tax-only adjustments.

This has been fixed.

3-19391743111

29448154

 The PCM_OP_COLLECTIONS_GET_AGENTS_ACTIONS output flist did not return the PIN_FLD_COUNT field. As a result, the custom logic failed.

This has been fixed.

3-19100404921

29448156

 In the subscription module, the product cancellation operation did not report missing validity information.

This has been fixed.

3-19498301501

29454752

 Non-CIT and MIT were failing in an attempt to access the unavailable data.

This has been fixed with appropriate null checks and error handling.

3-18953049631

29460620

 In the subscription module, incorrect discount amount was calculated when a discount was applied on a back-dated cycle forward monthly charge.

This has been fixed.

3-19555740471

29463336

 In the subscription module, the pin_cycle_fees utility was not selecting the tailor made products when run in the Cancel mode.

This has been fixed.

3-19125464031

29480201

 The AAA Services Framework, PCM_OP_TCF_AAA_AUTHORIZE opcode, had a memory leak.

This has been fixed.

3-19522425971

29496597

 When a discount was purchased in deferred mode, and it was canceled subsequently before the actual start of the discount, the cycle, purchase, and usage start dates were not updated to align with the end dates.

This has been fixed.

3-19525755941

29514020

 During billing, price-overridden products were not considered properly for rating.

This has been fixed.

3-19583668901

29514025

 For a discount-sharing group, when balances were concurrently updated using the multithreaded application (MTA) framework, the balance updates were not made correctly obtaining necessary lock to the balance group.

This has been fixed.

3-19611604151

29526005

 It was not possible to run multiple Rated Event (RE) Loader processes in parallel. When multiple RE Loader processes were run in parallel, the row lock contentions rendered the processes non-responsive.

This has been fixed.

3-19579803191

29533564

 The PCM_OP_PYMT_COLLECT opcode was not working for transaction ID with a length more than 16 characters.

This has been increased to 22 characters to be consistent with the Paymentech (fusa) specifications.

3-19579899441

29533569

 Wrong quantity for the event was picked up for rating. The event matching logic was considering the events based on the order in which they appeared.

This has been changed to the longest match event and now that is considered first, overriding the order of events.

3-19586933771

29533572

 Tax percentage was not added even if the tax calculation was not using any third-party tax engines.

This has been fixed. Changes are done to check tax_pkg_type for zero-tax amount cases.

3-19568382071

29557884

 In Oracle Communications Billing Care, it was not possible to track the user making any changes or updates in the News Feed section.

This has been fixed. The external user data is persisted as PIN_FLD_EXTERNAL_USER in the /newsfeed storable class.

3-17713284711

29557888

 For an offer, if an usage event was rated that had 0 (zero) charge and then the offer was changed and rerating was 1 (one), there was no adjustment event created nor a new usage event was created with 0 charge.

This has been fixed. Now, a new event with 0 charge is created and the general ledger ID (G/L ID) corresponding to the offer is impacted.

3-19600571011

29584658

 If the price of an one-time charge product is changed post billing and rerating and corrective invoicing is done, the rerated charge was not reflecting in the invoice.

This has been fixed.

3-19624443371

29590523

 The RE Loader was failing with the error "too many open files" and required an update to handle maximum number of files.

This has been fixed.

3-19733153701

29596720

 The pin_deferred_act utility was generating an error message in certain cases while dropping array elements, such as PIN_FLD_TELCO_FEATURES.

This has been fixed.

3-19136247751

29622932

 A bill was not including the charges during service activation from deferred actions on the bill date.

A new business parameter, BillDeferredActions, has been introduced in the Billing instance of the /config/business_params object.

By default, the BillDeferredActions parameter is disabled and the charges are added to the next bill. If you set the BillDeferredActions parameter to enabled, the charges are included in the current month bill.

3-19793794931

29634985

 Even when a migration failed, the Conversion Manager was reporting it as success.

This has been fixed.

3-19682040123

29673013

 It was not possible to synchronize the account data loaded into BRM with ECE by using the Conversion Manager. By default, the BRM data is published to ECE asynchronously, which could potentially lead to inconsistent data between BRM and ECE, if there are any synchronization failures.

Also, it was not possible to migrate the hierarchical accounts into BRM if the parent and child accounts are in the same files and the parent accounts were not loaded first.

This has been fixed. You can now perform the following:

  • Loading the migrated account data in BRM into ECE synchronously (in real-time).
  • Migrate parent and child accounts into BRM using the same input file.

3-19495959241

29681830

 In Billing Care, it took longer time to display the Account page. It was due to the PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode, delaying loading of accounts to the Account page.

This has been fixed.

3-19188771891

29714064

 When a product was canceled, refund was not going through if the product was purchased on Day 28 through Day 31 of a month with 31-day billing enabled and the next billing date did not exist in the subsequent month.

This has been fixed.

3-19855701651

29795746

 BRM triggered ECE_POST_COMMIT in ECE even when the transaction was aborted.

This has been fixed.

3-20125667971

29808545

 Any operation that included the PROFILE_SUBSCRIBER_PREFS_T table was causing a full table scan.

This has been fixed by introducing an index on the table.

3-19875296431

29820123

 For the pin_mass_refund utility, performance issues were observed.

This has been fixed.

3-20042957751

29858023

 In the plan transition flow, a new notification event /event/notification/plan/transition/post_deal_cancel was required to be sent soon after cancellation.

This has been added.

3-19883527851

29867410

 During the cancellation of a cycle-forward event, the subscription module did not fetch all the related events for reversal of charges.

This has been fixed.

3-17856477511

29871639

 In the discounting module of Pipeline Manager, after unloading existing configuration, a memory leak was observed while loading the new configuration, which was causing the growth of the used memory.

This has been fixed.

3-18860602351

29900322

 In the adjustment workflows, the decimal rounding precision was different from the configured precision for usage events.

This has been fixed.

3-19682040123

29920007

 In Conversion Manager, data errors were reported while migrating balances. These errors were due to unreleased database connections from the previous tasks.

This has been fixed.

3-20036936261

29937126

 During the billing process, it was observed that the next item POID list of the service object was corrupted.

This has been fixed.

3-20178161421

29960514

 While running the pin_del_closed_accts utility, NO_MEM error occurred. In such cases, memory was not cleared.

This has been fixed.

3-19106227471

29966023

 There were memory management issues in the Oracle Data Manager when search operation was performed using the PCM_OP_BILL_ITEM_ADJUSTEMENT opcode. This was because the search returned a huge number of events crossing the high watermark for the Data Manager process.

This search template has been fixed to retrieve the calculated sum from the database instead of retrieving huge number of records and calculating the sum.

3-19353513291

29966026

 The Paymentech DM was not supporting Zero Value Account Verification (ZVAV) for American Express cards.

This has been fixed.

3-19820667561

30031382

 The RE Loader Daemon could not process certain files resulting in unprocessed files pending in the input directory.

This has been fixed.

3-20153617841

30095369

 The RE Loader process witnessed an unaccounted growth in memory due to memory leak.

This has been fixed.

3-20574457081

30156863

 The create_analytics_procedures_UTF8.plb is now included.

3-18188837141

3-18861774371

28653606 29428272

 The Daylight Saving Time calculation was incorrect for Brazil.

This has been fixed.

3-17847235401

28923384 28975424

 The RE Loader process was not gracefully shutdown, when it was still processing files.

This has been fixed. Now, the RE Loader continues to process the pending files and then shuts down. A new configuration entry, batch.shutdown.interval, is introduced in the BRM_Home/apps/pin_rel/Infranet.properties file to set the shutdown interval in seconds. By default, this entry is set to 2.

 

Customer-Reported Fixes in Billing Care 12.0 Patch Set 2

 

Customer-Reported Fixes in Billing Care 12.0 Patch Set 2

SR Number

Bug Number

Description of the Issues Fixed

3-16951952221

27764510

 In the Allocate Adjustment and Payment Details dialog boxes, the columns were not resizable for simple and advanced views.

This has been fixed and the columns are resizable now.

3-17556441791

28466526

 In News Feed, when the Show Payment in Suspense link was clicked for a suspended payment, a payment suspense search page opened in a new browser tab.

This has been fixed and clicking the link now opens the suspended payment record.

3-17876252841

28543516

 Terminating or Inactivating discounts for a service was throwing an error.

This has been fixed.

3-18195333761

28624766

 In Billing Care Asset view, clicking Show Rate Customizaton was throwing an error, if the number of products purchased was more than 150.

This has been fixed.

3-18219886801

28664596

 There was an issue with amount formatting and rounding for Singapore dollar currency.

This has been fixed.

3-18101672221

28671904

 Billing Care is now enhanced to support account number and bill number instead of the corresponding Portal object IDs (POID) in the flows where Billing Care URLs are embedded in the external applications.

3-18306721201

3-18501913282

28671910

28853673

 It was not possible to log in to Billing Care from a new browser tab using a bookmarked URL, if there was a browser tab already logged in with Billing Care.

This has been fixed.

3-18306549191

28707428

 The Today date filter was not working in the payment suspense flow.

This has been fixed and the payment suspense search template has been corrected.

3-18484143531

28764136

 Billing Care is now enhanced so that the JavaScript files changes are not required in the account number sorting during account search implemented through software development kit (SDK).

3-18377594101

28768197

 There was an issue while displaying the suspended payment details when the Move, and View in Payment Suspense link was clicked in the payment details page.

This has been fixed.

3-18455941571

28806804

 Posting multiple comments (notes) was causing connection issues.

This has been fixed and the connection is released to the free pool on completion of note update.

3-18508445081

28806805

 Some of the dependent classes for generating reports were not shipped as part of the REST WAR files package.

This has been fixed and the missing dependencies are now included.

3-18298738421

28837041

 The connection to BRM was lost after timeout exception was thrown for the operations wrapped under a transaction.

This has been fixed.

3-18506198641

28854728

 Transfers between billable credit and debit items were treated as accounts receivable. This resulted in incorrect breakup of charges under the Bills tab.

This has been fixed.

3-18504936078

28905269

 While navigating to accounts receivable action details, after selecting a refund type accounts receivable action, the Back button was not working and its label was missing.

This has been fixed.

3-18613272481

28905272

 It was not possible to install Billing Care REST in silent mode.

This has been fixed.

3-18504936134

28912852

 Billing Care now displays a tooltip in the Bill ID field of the following dialog boxes: Payment Details, Payment Details Item Affected, Account Adjustment, and Account Adjustment Details.

3-18504936071

28912854

 The Cancel link was not working for the notes in the Event Adjustment Details dialog box.

This has been fixed.

3-18801505311

29048170

 When switching between bills, there was an issue with the Bills tab Show/Hide link.

This has been fixed.

3-18605545081

29161373

 The Purchase Package and Purchase Deal flows are now supported as embeddable URLs.

3-16250214071

29161376

 Billing Care is now enhanced to display bills that were generated before the account was moved under a hierarchy.

3-18979119339

29161377

 It was not possible to enter special characters for the Billing Care Wallet Password field.

This has been fixed.

3-18987020121

29178999

 For the bills in progress, wrong dates were displayed in the Item Adjustment dialog box.

This has been fixed and the current billing cycle dates are displayed.

3-19112468071

29272365

 The Refund Bill dialog box was displaying an error that the amount was greater than 999.99.

This has been fixed.

3-19040269941

29272368

 There were performance issues with the bill details view. It was taking more time to load particularly for the flows involving Billing Care URLs embedded in other applications.

This has been fixed.

3-19133358468

29290979

 The collection actions scheduled dates were one day older than the actual due date.

This has been fixed to show the correct scheduled dates.

3-19120021761

29290981

 If an account is created using customer center with a country, for example USA, and the same account was opened in Billing Care, a different country was displayed in the account profile details.

This has been fixed.

3-19076461581

29323429

 There were alignment issues with the labels of the Tax Setup dialog box under Financial Setup.

This has been fixed.

3-18957602481

29349021

 Discounts which were overridden as part of product purchase were not displayed in the breakup of the Original Charge or Discount or Net details in the Events dialog box.

This has been fixed.

3-19161875121

29376636

 It is now possible to display custom error messages on the Billing Care user interface when purchasing a bundle.

3-19152779561

29376640

 It was not possible to link purchase reason and notes to a particular add-on purchase event.

This has been fixed. A new method has been introduced, which retrieves the list of all the purchase events that can be used in the Billing Care SDK to assign to the notes.

3-18937531041

29395718

 To improve the performance of the Assets user interface, lazy loading of the assets has been implemented. By default, limited service information is retrieved and when the customer service representatives expand the particular service card, the additional service and offer details are retrieved.

3-19317248768

29428269

 The Bill in progress text was displayed twice in the Events page header.

This has been fixed.

3-19374947041

29435523

 After installation, Business Operation Center was opening with a blank screen.

This has been fixed.

3-19172328801

29441732

 Overdue days were shown incorrectly as the last configured period of the aging buckets.

This has been fixed to show the actual overdue days. A new popup has been added to list the age of the overdue balances as per the aging bucket configuration.

3-19375982111

29441738

 Reason code was missing in the make payment flow.

This has been fixed and the reason code is added now.

3-19549400461

29493386

 The Event Adjustment dialog box can now be customized to separate both Adjust the Amount field and Adjust the Percent field. Also, there was an issue with tax only adjustment.

This has been fixed.

3-18127339011

29511807

 There was a performance issue while retrieving users who had access to the Payment Suspense screen because all the configured users were queried.

This has been fixed and it is now possible to query only users associated with a specific role who has the required screen access.

3-18930292991

29520395

 The Billing Care SDK is now enhanced to support implementing the logic to restrict the deal list based on the role of the customer service representative. See Billing Care SDK Guide.

3-19083734451

29629576

 The Billing Care SDK is now enhanced to support implementing the logic for filtering deals list to display manual discount deals only. See Billing Care SDK Guide.

3-19040270003

29629577

 Object serialization error was logged in the Oracle Entitlements Server client weblogic logs.

This has been fixed.

3-19317720898

29645139

 The future dated add on purchase were purchased with wrong dates.

This has been fixed.

3-18784241191

29649643

 Billing Care is now enhanced to display the external user names (login user) in News Feed to clearly highlight who has made changes on the account or have performed any account receivables actions. See Billing Care SDK Guide.

3-19083920361

29705003

 It is now possible to customize Billing Care to include start date and end date based filtering for add on deal purchase.

3-19533307321

29759310

 In the Billing Care Item Adjustment dialog box, it is possible to see the total amount for which adjustment is done. But it does not display how much other amount was adjusted against specific item.

This has been fixed.

3-19530710241

29759312

 To improve performance, Billing Care has been enhanced to disable direct click on the Assets view from the Home tab through customization. It is now possible to search through service ID to go to the Assets page which display only services associated with the search criteria.

3-19549400461

29789695

 The Oracle Entitlements Server obligation check was throwing an exception. A null value check on adjustment amount when percentage only adjustment is done using customization was not introduced to avoid this exception.

This has been fixed.

 

Customer Reported Fixes in Business Operations Center 12.0 Patch Set 2

Customer Reported Fixes in Business Operations Center 12.0 Patch Set 2

SR Number

Bug Number

Description

3-18689185011

28602921

 The SERVICE_HOST parameter in Business Operations Center configuration properties file restricted login with IP address when the paramater was set as hostname, and restricted login with hostname when the parameter was set as IP address.

This has been fixed. Dependency on the SERVICE_HOST parameter has been removed to construct REST URL.

3-18758155401

29033987

 The Business Operations Center silent installer has been enhanced to update wallet with Secure Shell user and BRM connection keys.

3-19190623931

29290982

 During validation, the Business Operations Center installer was not accepting special character for passwords in the Wallet field.

This has been fixed. Now, special characters in addition to numbers and characters are accepted.

3-19558733471

29699403

 The Business Operations Center failure report was showing Account Portal object ID (POID) instead of the account number.

This has been fixed and the report now shows the account number.

 

 

 

 

 

 

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:
 New Features in BRM:
 New Features in Billing Care:
 New Features in Business Operations Center
 Customer Reported Fixes in Oracle Communications Billing and Revenue Management 12.0 Patch Set 2
 Customer Reported Fixes in BRM 12.0 PS2
 Customer-Reported Fixes in Billing Care 12.0 Patch Set 2
 Customer Reported Fixes in Business Operations Center 12.0 Patch Set 2
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.