My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 23 (Doc ID 2620775.1)

Last updated on MARCH 12, 2021

Applies to:

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

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 23 (7.5.0.23.0) is released on 20 December 2019.

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

Patch ID: <Patch 30343682>

Key Enhancements

View Bills Generated Before Moving the Account to a Hierarchy

In previous releases, when an account was moved to a hierarchy as a child account, the bills generated for the account earlier were not displayed in the bills list.

With this enhancement, you can view the bills that are generated before and after moving the account to a hierarchy in the account's Bills > Switch Bills menu. For more information, see the discussion about switch bills in the Billing Care Online Help.

 

Managing Discount Validity Starting or Ending in Future Cycles

In previous releases, the discount proration was not set properly if the discount validity was starting or ending in a future cycle.

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.

For more information on discount validity, see the discussion about configuring discount validity in PDC (Pricing Design Center) User's Guide if you are using PDC or the Pricing Center Online Help if you are using Pricing Center.

 

Support for Stored-Credential Transactions for Payments

Credit card networks, such as VISA, MasterCard, Diners, Discover, JCB, and American Express, support the stored credential framework. They allow the merchants to use stored credentials for transactions. A stored credential is a payment information (such as an account number or a payment token) of a card holder stored by a merchant or its agent, a payment facilitator, or a staged digital wallet operator to process future transactions for the card holder. The Paymentech card processors also support customer-initiated or merchant-initiated transactions with stored credentials.

With this enhancement, BRM supports payment transactions with stored credentials for VISA, MasterCard, Diners, Discover, JCB, and American Express cards. You can also customize BRM to support stored-credential transactions for other card networks. When VISA, MasterCard, Diners, Discover, JCB, and American Express cards are used for payments, the PCM_OP_PYMT_COLLECT opcode sends the following information required for card transactions to Paymentech Data Manager (dm_fusa) and stores the responses received from Paymentech DM (Data Manager) for future transactions:

You can override this information sent to Paymentech DM based on your business requirements. If you do not want to store credentials for future transactions, you can remove this information from the input passed to the PCM_OP_PYMT_COLLECT opcode.

 

Additional Card Security Presence Values Supported for Card Validation or Authorization

For credit card validations or authorizations, Paymentech Data Manager (dm_fusa) sends the Fraud Format Indicator (FR) or Product Record (PFR) record with the card security presence value. When the card security code (such as VISA CVV2) is present in the PIN_FLD_SECURITY input flist field, Paymentech DM sets the card security presence value to 1 and sends the FR or PFR record for validation by default.

With this enhancement, 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

BRM applications may log flists containing the sensitive customer data. In previous releases, the card security code, such as VISA CVV2 or American Express CID, passed in the PIN_FLD_SECURITY_ID input flist field was not masked and appeared as clear text in the logs.

With this enhancement, the PIN_FLD_SECURITY_ID value is masked during logging. The card security codes passed in this field appear as masked fields in logs.

 

Pipeline Manager Can Now Support 28-Digit Decimal

You can now configure Pipeline Manager to support 28-digit decimal rather than the default of 15-digit decimal.

To configure Pipeline Manager to support up to 28-digit decimal, set the MAX28DIGIT_DECIMAL_SUPPORT environment variable to Y before you start Pipeline Manager and its services.

 

Certifications

With this patch, BRM 7.5 is certified with

 

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

 

Customer Reported Fixes

SR Number

Bug Number

Description

-

27152358

In Customer Center, it was not possible to purchase a new deal because the screen would go blank.

This has been fixed.

3-17434540731

27993353

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) was not sufficient.

This has been now increased to 51 bits.

3-17547976531

28075612

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

This has been fixed.

3-18127339011

28527055

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

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

3-17876252841

28543515

Terminating or inactivating the discounts for a service was throwing an error.

This has been fixed.

3-17885661511

28543513

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

This has been fixed.

3-17564929691

28552542

Web Services Manager was 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-18125409791

28576658

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

28624763

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

This has been fixed.

3-17444287241

28638443

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

This has been fixed.

3-18298738421

28640180

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

This has been fixed.

3-17255866551

28643229

Customer Center did not support updating the size of fields in the Product details panel.

This has been fixed by providing customization hooks.

3-17456393961

28649189

Plan transitions were failing due to missing grantor information.

This has been fixed.

3-18582577041

28653605

A cycle forward event was one day shorter during the DST switch for Brazil.

This has been fixed.

3-18219886801

28664595

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

This has been fixed.

-

28671903

The Billing Care embedded flow was expecting account and bill POIDs in place of account and bill numbers.

This has been fixed.

3-17803665231

28671912

The EVENT_POID_LIST was required to store longer strings than was allowed (4,000 characters) in the database.

This has been fixed.

3-18188014831

28678756

A memory leak occurred in the flist-to-string conversion routine.

This has been fixed.

3-17920861571

28700836

Backdated adjustments were not displayed in corrective invoices.

This has been fixed.

3-18306549191

28707427

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

28746436

When a write-off reversal was done at the bill unit level, it was not creating a corresponding event for tax (that is, /event/billing/writeoff_reversal/tax).

This has been fixed.

3-18377594101

28768195

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

28774360

The BillPaymentDeallocation feature allows bill adjustments on zero-due bills or partially paid bills. This behavior has now been implemented for item- and event-level adjustments as well.

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

  1. Unallocate the payment applied on the corresponding bill item.
  2. Adjust the item or event.
  3. Reallocate the payment to the bill item.

If the payment amount is more than the amount due after the adjustment, 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

28774364

If an error is thrown in ECE (Elastic Charging Engine), 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.

3-18383751591

28780634

The wrong item type was selected when dealing with in-advance billing events. An /item/adjustment event was created rather than an /item/cycle_forward_arrear event for cycle forward arrear events.

This has been fixed.

3-16906450911

28786828

28714307

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

28794483

In the subscription module, if END_T was earlier than the cycle, purchase, or update end dates, the cycle start and end dates were set incorrectly. This led to a validation error.

This has been fixed.

3-18455941571

28806803

Posting multiple comments or notes was causing connection issues.

This has been fixed. The connection is now released to the free pool when a note update completes.

3-18482634741

28812793

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

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

3-18482428661

28812797

The PCM_OP_AR_BILL_ADJUSTMENT opcode had memory leaks.

This has been fixed.

3-18310735251

28824833

The CM module had some memory leaks.

This has been fixed.

3-18578426961

28825321

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

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

3-18505486831

28837035

In the subscription module, when a purchase was backdated on the billing day of month, the event's end date was set incorrectly. This caused incorrect validity periods for the resources in both BRM and Pipeline Manager.

This has been fixed.

3-17857944451

28843065

The loadpricelist utility was failing with a core dump when committing or retrieving a price list.

This has been fixed.

3-16250214071

28848745

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

This has been fixed.

3-18473654211

28848747

When trying to open a transaction on a non-existent object, the workflow was not returning an error.

This has been fixed by checking for the existence of an object before trying to lock the object and open a transaction on it.

3-18501913282

3-18306721201

28853675

28671908

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

This has been fixed.

3-18506198641

28854726

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

This has been fixed.

3-18606199551

28866702

There was an issue with upgrading to Patch Set 21.

This has been fixed.

3-18631761901

28871777

The file name format for general ledger (G/L) reports generated in XML were different.

This has been fixed to restore the earlier naming format.

3-18368278231

28905265

When an account was deleted by using a wrapper opcode that called the PCM_OP_CUST_DELETE_ACCT opcode, an error in the workflow would not trigger a rollback to changes in the /uniqueness object.

This has been fixed.

3-18504936078

28905268

When navigating to the 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-18608897451

28905271

It was not possible to install Pricing Configuration Center in silent mode.

This has been fixed.

3-18504936134

28912851

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

3-18504936071

28912853

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

This has been fixed.

3-18263789131

28923378

The PCM_OP_BILL_MAKE_BILL opcode finalized a bill when the workflow was called by a process other than pin_bill_accts.

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

3-18592651071

28923380

In Customer Center, the Event Browser text labels were not being displayed for date-pickers in customer event browser templates.

This has been fixed.

3-19353513291

28944040

For PCI (Payment card industry) compliance, it was required to mask the PIN_FLD_SECURITY_ID field in the card attributes structure for enhanced card security. See "Card Security Code Is Now Masked in Logs".

3-18447694071

28944042

The Paymentech DM now supports Card Security Presence and sends a Fraud Format Indicator (FR) record when this field is present. See "Additional Card Security Presence Values Supported for Card Validation or Authorization".

3-18664468631

28944046

Paymentech was returning duplicate CIT (Cardholder Initiated Transaction) and MIT (Merchant Initiated Transaction) transaction IDs.

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

3-18713081091

28977385

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

This has been fixed.

3-18453203791

28997119

In the Customer Center Product Details page, when setting the start or end date of a product, the calendar box was dynamically changing. This caused inconveniences when the user scrolled through the months by clicking the up and down arrows.

This has been fixed.

3-18399785331

28997122

In the subscription module, when multiple discounts were purchased with different validity dates in the same deal, the discount 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

29017374

The CM (Connection Manager) module had some memory leaks.

This has been fixed.

3-17847235401

29020323

28923382

RE (Rated Event) Loader was not shutting down gracefully when it was still processing files.

This has been fixed. Now, RE Loader finishes processing any pending files before shutting down. You can use a new configuration entry, batch.shutdown.interval, 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.

3-18370747541

29023517

28521328

28739771

The scope of a header file caused the customer management module to throw a symbol look-up error.

This has been fixed.

3-18855799201

29036174

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

This has been fixed.

3-18930292991

29039454

Billing Care SDK (Software Development Kit) now supports implementing the logic to restrict the deal list based on the role of the customer service representative. See Oracle Communications Billing Care SDK Guide.

3-18452678921

29042243

During a billing delay period, discount cancellation operations were not applying refunds. This inconsistency occurred because the bill unit's accounting dates still reflected the previous cycle's information.

This has been fixed by adding checks to handle these type of events during the delay period.

3-18889790481

29042247

A memory leak occurred in the customer registration module.

This has been fixed.

3-18793585311

29042249

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

This has been fixed.

3-18919001443

29120661

A memory leak occurred in the Paymentech DM.

This has been fixed.

3-18919001133

29120694

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

29126519

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

This has been fixed.

3-18943590851

29127132

The Paymentech simulator was sending an invalid number of bytes for non-CIT/MIT transactions that followed a CIT/MIT transaction.

3-18693381421

29127138

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

This has been fixed.

3-16749719711

29141790

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

29146202

The modify customer operation was not applying cycle discount information that was passed in the input. This was caused by a missing Portal object ID (POID) in PIN_FLD_DEAL_INFO field.

This has been fixed.

3-16250214071

29161375

Billing Care now displays bills that were generated before an account was moved under a hierarchy.

3-18605545081

29162143

The Purchase Package and Purchase Deal flows are now supported as embeddable URLs. See "Embeddable URLs for Purchase Package and Purchase Bundle Screens" for more information.

3-19083734451

29170772

The Billing Care SDK now supports implementing the logic for filtering deals lists to display manual discount deals only. See Oracle Communications Billing Care SDK Guide.

3-18980345811

29174545

(Patch 23) In Collections Manager, the PCM_OP_COLLECTIONS_GROUP_CREATE opcode had memory leaks.

This has been fixed.

3-18644785641

29178996

29174538

Event adjustment was not working as expected when 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-18987020121

29178998

The wrong dates were displayed in the Item Adjustment dialog box for bills in progress.

This has been fixed. The current billing cycle dates are now displayed.

3-15270580261

29204381

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

29219680

In Billing Care, the labels in the Tax Setup dialog box were misaligned.

This has been fixed.

3-19167494161

29223948

During rerating, the event search workflow was not considering the configured event_start_timestamp parameter in the pin_event_extract.cfg file, but instead it was taking the event END_T.

This has been fixed.

3-19012827981

29240929

In Conversion Manager, when the input payload contained more than one service, balance, or account, the XML payload's instance_type was set incorrectly.

This has been fixed.

3-19140579111

29243585

To boost Customer Updater performance, indexes were added.

3-18536623001

29265112

In discount sharing, when multiple re-authorization requests were created, the reservation quantity was not updated and it stayed at the sum of the quantity of the first authorization and last re-authorization. It was possible to reauthorize sessions indefinitely and certain limits were not enforced. This caused revenue leakage.

This has been fixed.

3-19112468071

29272363

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

This has been fixed.

3-19040269941

29272366

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

This has been fixed.

3-19157592761

29278527

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

This has been fixed.

3-19133358468

29290978

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

29290980

When an account was created in Customer Center with one country, such as USA, and then the same account was opened in Billing Care, a different country was displayed in the account profile details.

This has been fixed.

3-12647683891

29303584

When the billing day of month was 28, 29, 30, or 31, its next cycle date was calculated incorrectly.

This has been fixed.

3-19317248768

29315565

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

This has been fixed.

3-18741993071

29342745

When rating with a sponsored product, the credit limit check was done both on the sponsored product and the user product. This caused a credit limit breach to be reported when the user product sub-balance was positive.

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

3-19360664961

29342747

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

This has been fixed.

3-18957602481

29349019

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

This has been fixed.

3-19278553351

29370863

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

This has been fixed.

3-18738247231

29376632

The Pipeline Manager Framework had a memory leak while converting decimal to string.

This has been fixed.

3-19161875121

29376635

You can now display custom error messages in the Billing Care user interface when purchasing a bundle.

3-19152779561

29376637

Purchase reasons and notes could not be linked to a particular add-on purchase event.

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

3-18937531041

29395717

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

29395723

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

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

3-19456180091

29409244

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

This has been fixed.

3-19479366521

29428056

When using the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO or PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode, the purchase START_T was not getting rounded, even if timestamp rounding was enabled. This resulted in errors when purchase START_T was later than cycle START_T.

This has been fixed.

3-19353513291

29428267

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

29428271

The Daylight Saving Time calculation was incorrect for Brazil.

This has been fixed.

3-19172328801

29441730

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

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

3-17880290091

29441734

During the billing process, a few items were incorrectly filtered during final billing. This was caused by item pruning in cases of billing suppression, suspension, or resume billing.

This has been fixed.

3-18731886071

29448149

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

This has been fixed.

3-19100404921

29448155

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

This has been fixed.

3-19498301501

29454751

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

29463335

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

This has been fixed.

3-19125464031

29480200

In the AAA (Authentication Authorization and Accounting) Services Framework, the PCM_OP_TCF_AAA_AUTHORIZE opcode had a memory leak.

This has been fixed.

3-19549400461

29493382

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

This has been fixed.

3-19525755941

29514018

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

This has been fixed.

3-19583668901

29514023

When balances were concurrently updated in discount-sharing groups using the multi-threaded application (MTA) framework, balance updates were not made correctly obtaining the necessary lock to the balance group.

This has been fixed.

3-19611604151

29526004

Multiple Rated Event (RE) Loader processes could not be run in parallel, because the row lock contentions rendered the processes non-responsive.

This has been fixed.

3-19672982621

29532921

The purchase of discounts was failing after enabling sequential discounting in scenarios in which the cycle beginning was earlier than the product commit date.

This has been fixed.

3-19579803191

29533562

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

This has been increased to 22 characters to be consistent with the Paymentech specification.

3-19579899441

29533566

The wrong quantity for an event was picked up for rating, because the event-matching logic was considering the events based on the order in which they appeared.

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

3-19586933771

29533571

A tax percentage was not added even when tax calculation was not using third-party tax engines.

This has been fixed by now checking tax_pkg_type for zero-tax amount cases.

3-14912351881

29549092

The billing process was applying incorrect taxes when running the billing account as the brand user.

This has been fixed.

3-17713284711

29557885

For an offer, when usage events with a zero charge were rated and then the offer was changed and rerating was one, no adjustment event was created and no new usage event was created with zero charge.

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

3-19600571011

29584656

When the price of a one-time charge product was changed post-billing and rerating and corrective invoicing was done, the rerated charge was not reflected in the invoice.

This has been fixed.

3-19624443371

29590501

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

This has been fixed.

3-19733153701

29596718

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

This has been fixed.

3-19793794931

29634984

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

This has been fixed.

3-19317720898

29645138

Future-dated add-on purchases were being purchased with the wrong dates.

This has been fixed.

3-19040270003

29646959

An object serialization error was logged in the Oracle Entitlements Server client WebLogic logs.

This has been fixed.

3-19495959241

29681829

In Billing Care, it took a longer time to display the Account page. This 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-19083920361

29705002

You can now customize Billing Care to include start date- and end date-based filtering for add-on deal purchases.

3-19188771891

29714062

When a product was canceled, a refund was not applied when 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-19533307321

29759307

The Billing Care Item Adjustment dialog box can display the total amount for which an adjustment is done. However, it does not display how much other amount was adjusted against the specific item.

This has been fixed.

3-19530710241

29759311

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

3-20045914941

29783828

30286681

The condition expression for evaluating discounts was 15-digit decimal by default. The condition evaluation was incorrect when this limit was exceeded.

This has been fixed by optionally setting the limit to 28 digits with the new MAX28DIGIT_DECIMAL_SUPPORT environment variable before the Pipeline Manager is started.

3-19549400461

29789694

The Oracle Entitlements Server obligation check was throwing an exception. A null value check for the percentage-only adjustment was done using customization was not introduced to avoid this exception.

This has been fixed.

3-18860602351

29795751

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

This has been fixed.

3-18941949321

29808541

When the adjustment opcode was part of another bigger transaction, the error buffer was not reflecting the actual error condition. For a local transaction, the error buffer was required to be cleared, and only the result and description information was required to be returned.

This has been fixed.

3-19875296431

29820120

The pin_mass_refund utility was having performance issues.

This has been fixed.

3-19408274651

29833414

In Billing Care, the Timezone name string and offset were not supported for handling DST using the brmserver.timezone parameter.

This has been fixed.

3-20063381831

29837456

In Billing Care, the account hyperlink from the Bills tab of a child account to a parent account was not working.

This has been fixed.

3-20042957751

29858022

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

This has been added.

3-19883527851

29867408

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

This has been fixed.

3-20246843021

29869223

The CM was continuing to start even when there were timeout errors.

This has been fixed by adding proper error checks during the start-up.

3-17856477511

29871638

In the discounting module of Pipeline Manager, a memory leak occurred after unloading the existing configuration and then loading a new configuration. This caused a growth in the used memory.

This has been fixed.

3-20178161421

29960513

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

This has been fixed.

3-19106227471

29966022

There were memory management issues in the Oracle DM when a search was performed by 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 DM process.

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

3-19353513291

29966024

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

This has been fixed.

3-19820667561

30031381

The RE Loader Daemon was not processing certain files, resulting in unprocessed files pending in the input directory.

This has been fixed.

3-18778333321

30072014

BRM was generating cycle events for the first usage enabled plan during rerating, even if those events were billed.

This has been fixed to generate the appropriate adjustment or shadow events.

3-20153617841

30095367

RE Loader had an unaccounted growth in memory due to a memory leak.

This has been fixed.

3-19814604931

30108677

The pin_cycle_fees utility with the cancel option was not cancelling inactive products.

This has been fixed by adding a new inactive option to the utility.

3-19581140931

30120447

Processing real-time usage with the PCM_OP_ACT_USAGE opcode resulted in degraded performance. This occurred when a large number of system products were loaded for every child CM process.

This has been has been fixed by caching the details during the CM startup.

3-20224205751

30125967

During rerating, the rollover amount was getting doubled and a rollover event was not generated.

This has been fixed.

3-20407424651

30133927

In an expired discount sharing group, the partial billing was failing.

This has been fixed so that it now checks the validity of the discount sharing group and then exits gracefully.

3-20674561991

30135334

There were issues reported by Fortify scans in the following SDK source code: fm_cust_pol_valid_all.c, sample_who.c, and BRMAdapterServletClient.java.

This has been fixed.

3-20586831151

30146957

In Customer Center, when searching for payments in the Payments tab, the All entry in the Bill Unit drop-down was not displaying all payments made for the account.

This has been fixed.

3-20237831311

30146960

When a bill was paid in full with zero due, subsequent adjustments to the bill was allocated incorrectly.

This has been fixed.

3-19783315511

30158955

After a failed transaction in a batch, the pin_deposit utility was failing subsequent transactions.

This has been fixed.

3-20656807751

30175032

In Customer Center, users with read-only permission were not allowed to copy information from the application.

This has been fixed to allow users to copy the service ID from the Services tab.

3-19908575371

30187911

There were issues while generating HTML invoices using invoice formatter, indicating a duplicate variable date definition.

This has been fixed.

3-19261875971

30187915

During event adjustments, the corresponding tax calculation had rounding errors.

This has been fixed.

3-19849106481

30228174

In a custom workflow, if the same transaction was used to commit data into the BRM database and also publish to Oracle Advanced Queue DM, the data was committed to the database but the message was not published to Oracle Advanced Queue DM.

This has been fixed. The message now also gets published when there is no exclusive transaction for Oracle Advanced Queue DM.

3-20313924221

30228178

The pin_del_closed_accounts utility had a memory leak.

This has been fixed.

3-19215540181

30249956

Schema validation in Web Services Manager was working incorrectly, allowing the workflow to continue to process the request with an incorrect payload.

This has been fixed.

3-20747428241

30258066

Bill adjustments were incorrect for bills that contained one or more settled disputes.

This has been fixed.

3-20860270631

30276797

Even though a service was mapped to its own balance group, an item adjustment for that service was wrongly updating the account balance group.

This has been fixed.

3-19953272721

30287776

When a discount's end date was modified, PIN_FLD_CYCLE_END_T was incorrect. This caused the refund and reapplication of the discount to not work correctly.

This has been fixed.

3-20622939101

30287779

If the customer canceled a discount after running Bill Now in a delay period, the charges were applied to the closed item in the wrong bill.

This has been fixed.

3-20955329641

30291797

A discount of 100% on a non-currency charge failed when multiple charge packets of multiple non-currency resources had both positive and negative charges.

This has been fixed by properly segregating the charges for each resource and calculating the total for each resource to apply discounts.

3-19814604931

30292967

The pin_discount_cleanup did not support cleaning up inactive discounts.

This was fixed by adding a new close_inactive mode to the utility.

3-20800040981

30292972

In Billing Care, the Account page was not loaded when an account had multiple bill units. The Oracle Data Manager threw a "search TEMPLATE too big" error. The search failed because it exceeded 2048 characters.

This has been fixed now by optimizing search template.

3-20573079451

30292977

When balances were transferred between two balance groups by using the PCM_OP_BILL_ITEM_TRANSFER opcode, notifications were not generated.

This has been fixed.

3-20212984941

30327228

When the tax jurisdiction information was in multiple array elements, taxes were not considered during event adjustments. This caused incorrect balance impacts.

This has been fixed.

3-20342294551

30332377

In Billing Care, the security headers were missing as part of the response for each request to the server.

This has been fixed.

Security headers like X-FRAME-OPTIONS, X-XSS-Protection, Strict-Transport-Security, Expect-CT, and X-Content-Type-Options were added to the response for each request to the server.

3-21148367731

30360252

The advanced discounting pipeline was returning PIN_ERR_BAD_VALUE when it was called from the pin_cycle_fees utility.

This has been fixed.

3-20926194821

30385890

The cycle date was calculated incorrectly when rerating quarterly cycle events.

This has been fixed.

3-21108633031

30392334

When two cycle events existed for the same product and period (due to a discount  purchase), the rerated cycle event was not able to match the previous cycle event. Thus, the rerated cycle event was not populated with PIN_FLD_SESSION_OBJ.

This has been fixed.

3-21242387561

30406782

Real-time rerating was failing for a charge offer when the PIN_FLD_RATING_PRODUCTS information was truncated due to a string length limit.

This has been fixed by increasing the string length.

3-20841881041

30406789

During billing, incorrect products were selected for applying folds.

This has been fixed.

3-19793726101

30410948

A purchase fee was applied twice, even when the purchase was done only once.

This has been fixed.

3-20670583751

30411711

The Account Synchronization DM (dm_ifw_sync) was not supporting timeout for its database connection.

This has been added now.

3-17157581651

30418718

In Billing Care, there was no support for the following:

  • Disabling backdated account creation and backdated service purchases
  • Enabling backdated product activation in the purchase bundle flow

This has been added now.

3-21313665271

30457058

The Rated Event Loader daemon was not shutting down gracefully while processing rated events from ECE. In addition, when restarting, the daemon was not picking up pre-existing *.bc files.

This has been fixed.

3-20926194821

30462363

The PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode called PCM_OP_SUBSCRIPTION_FEES even when PIN_FLD_PURCHASE_START_T was not passed. The calc_cycle_from_cycle_start_t entry in the CM configuration file affected the generation of the cycle arrear event.

This has been fixed.

3-21158170251

30462365

When you created two discount sharing groups, one with the current dated EFFECTIVE_T and the other for backdated EFFECTIVE_T, the backdated discount sharing group was not considered for valid backdated usage.

This has been fixed.

3-21203320841

30510693

Back-date validation failed when timestamp rounding was disabled and a full discount was purchased. The full discount rounded the discount's START_T to ACTG_LAST_T. When the discount's START_T was earlier than the timestamp of the last status change, validation failed.

This has been fixed.

3-19907943331

30521542

The Paymentech Data Manager (dm_fusa) backend was reaching 100% CPU utilization when a verification request was sent and not returning from the call.

This has been fixed.

3-21274191101

30521551

BRM now supports extended ranges for newly added cards for China UnionPay BIN.

3-20087766421

30526514

Paymentech Manager has been updated to support real-time account updater and China UnionPay card BIN (Bank Identification Number) ranges.

3-20815136391

30528413

In Billing Care, it was not possible to process batch payments with custom payment templates that use out of the box payment types.

This has been fixed.

3-21084025481

30541400

In Billing Care, it was not possible to view Bill Adjustment details for adjustments done using custom opcodes without notes.

This has been fixed.

 

 

 

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
 View Bills Generated Before Moving the Account to a Hierarchy
 Managing Discount Validity Starting or Ending in Future Cycles
 Support for Stored-Credential Transactions for Payments
 Additional Card Security Presence Values Supported for Card Validation or Authorization
 Card Security Code Is Now Masked in Logs
 Pipeline Manager Can Now Support 28-Digit Decimal
 Certifications
  Summary of fixes to customer-reported tickets delivered in 7.5 Patch Set 23
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.