My Oracle Support Banner

Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 10 (Doc ID 1940583.1)

Last updated on MAY 12, 2021

Applies to:

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

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 10 is released on 31 October 2014.

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

Patch ID: <Patch 19678435>

 

Key Enhancements in BRM 7.5 Patch Set 10:

For more details about these changes and enhancements, please refer to BRM documentation.

Collections Manager supports Reversal of Written-Off Bill Units

With this patch set you can now revisit the written-off bill units in Collections Manager to accept either the full or partial payment at bill unit level, thus improving revenue collection support for a written off debt allowing you to maximize revenue.

Payments supported with Credit Card tokenization with Paymentech 

With this patch set, BRM now supports secured payments which use credit card tokens with Paymentech instead of the actual credit card number. These tokens are stored and managed securely within the BRM database. BRM also provides migration support to move the existing credit card numbers into unique tokens generated by Paymentech.

Certifications

With this patch set, BRM is now certified with

With this patch set, BRM will now make use of OpenSSL supplied by the operating system vendor. 

 

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

 

SR Number

Bug Number

Issue Fixed

3-7153450471

16965406, 19352822

Payment Tool was not honoring access with the permissions defined in /service/admin_client. The only way to access was to define permissions in Permissioning Center for access.

3-7730960101

17834397, 17928712, 19368177

The pin_trial_bill_accts utility was taking a very long time to process accounts for trial billing. This was observed for large account hierarchies.

3-7752886781

17970904

For an account when a proration enabled product was purchased or canceled on cycle boundaries, the proration was getting into effect, but it was not necessary to do the proration when the dates were aligned to the cycle dates.

3-8546674701

18389662, 19143314

In Customer Center, when modifying products that had a relative offset period set to an absolute date, the date was defaulting to 31-Dec-1969 rather than the absolute date corresponding to the relative offset that was defined earlier.

3-8657352981

18425860

Real-time pipelines for rerating and discounting were not supporting the EDRTrace feature.

3-8668009771

18433221

In Customer Center, the units in Products - Product Details tab were disappearing when choosing between Relative and Date options.

3-8389236441

18475426

From BRM 7.5 Patch Set 7, the link edit between libportal.so and Oracle 11g client libclntsh.so was failing while building custom applications.

3-8781616941

18508380

The pin_mass_refund utility was not working for bill units with open item accounting.

3-8380836155

18511978

When Connection Manager Master Process (CMMP) was used as a load balancer, the switching of transaction state was occurring even for non-transactional opcodes, which was then resulting in an ERR_TRANS_ALREADY_OPEN error.

3-8331979191

18519249

When using Conversion Manager, the actual values provided for deal_obj_db and plan_obj_db were disregarded and these parameters were always incorrectly set to 1.

3-8834248071

18546684, 19207928

The subscription-level balance monitor was correctly updated with subscription-level adjustments when the subscription service POID was passed in the input flist of the PCM_OP_AR_ACCOUNT_ADJUSTMENT opcode. This information was not correctly documented in the opcode specification.

3-8835796891

18546903

The Customer Center SDK method was setting the date incorrectly in the PAIDateField class.

3-8826336531

18614306

In Event browser, the Connection Manager (CM) connection was not released even after closing the window.

3-8902318711

18665392

Multiple warning messages were displayed when launching Customer Center from a web browser.

3-8674415121

18699624

When using Conversion Manager, the timestamp fields of uniqueness table were wrongly populated based on the system date.

3-7560575581

18739065

The BRM general ledger reports considered revenue to be billed based on the end time of the corresponding bill period. For example, if the bill period is Jan 1 - Feb 1, but the actual bill run is on Feb 3, the revenue is considered billed on Feb 1. With this release, you can now set the new UseActualBilledTimeForGLReport billing business parameter to consider the revenue billed to be on the actual bill run date.

3-8640746111

18752383

When using Conversion Manager, if pin_cmt_deploy was run multiple times for same stage ID, it was resulting in inconsistent data in the au_profile_t and au_service_t audit tables.

3-7617935901

18791573

When the discount was applied to the same non-currency resource as the charge, the base amount for a sequential discount was incorrectly calculated.

3-8735434341

18826015, 19569009

When submitting duplicate payments for the same account in a single batch of payment tool, both payments were being applied on the account without any check for over allocation to items. This was resulting in a negative account balance. With this release, a new business parameter, ItemOverAllocation, is added to determine whether any item can be allocated beyond its due. By default the value of the business parameter is enabled.

3-8926475921

18903914

When publishing events from eai_js, the format of the timestamps sent out was incorrect.

3-8777861598

18948667

During migration with Conversion Manager, while trying to update bal_grp_t as first day of previous month, the effective date in bal_grp_t was incorrectly set to created_t instead of effective_t.

3-8951132071

18957536

Conversion Manager was hanging with java.lang.NullPointerException in the java stack trace.

3-9074661021

19021970, 19341890, 19342928

BRM was not supporting querying the latest real time balances information from Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE).

3-8956489561

19031334

When timestamp rounding is enabled for all the non-currency resource grants due to the cycle forward event, bal_grp_sub_bals_t.valid_from in the granted sub balance were rounded to midnight only and there was no option to control this rounding for purchase grants. With this release, a new business parameter, TimestampRoundingForPurchaseGrant, is added for rating. This business parameter works along with the timestamp_rounding parameter in the pin.conf file. When the business parameter is enabled and the timestamp_rounding parameter in the pin.conf file is also enabled, the purchase grant will be rounded to midnight. By default, the value of the business parameter is set to 1 (enabled).

3-9000971543

19052369

A client patch did not specify a build number.

3-9107610731

19055312

When multiple transactions were active, FCT_ApplyBalance was not properly renaming the notification files to have .xml extension. It was picking up only the latest stream for verifying and renaming only the corresponding notification file.

3-9084752364

19062931

When in maintenance mode, updating the cycle end date was not working. It was always defaulting to the next cycle end date.

3-9097643431

19067183

It was not possible to configure an RSC_Map using rateplan code, even though using a rateplan code was more intuitive than rateplan identifier. With this release, you can now set the optional boolean UserRatePlanCode registry parameter to use rateplan code. The default is FALSE. To use rateplan code, set the parameter to TRUE.

3-9065871071

19078159, 19259074

The pin_rel utility was not updating the /journal objects with events corresponding to zero event balances. With this release, you can now set the ZeroEventBalances business parameter to update the /journal objects with events corresponding to zero event balances. By default, the value for of the business parameter is 0, which is not to include the zero event journal balances. To include zero event journal balances, set the business parameter to 1.

3-8900925751

19128368

While migrating non-currency resources using Conversion Manager, the realtime_cntr and rec_id fields of the existing sub_balances were not properly updated.

3-9277903901

19158265, 19329665

The PIN_FLD_GEOCODE and PIN_FLD_TAXPKG_TYPE fields were missing from PCM_OP_BAL_GET_ACCT_BILLINFO JCA XSD file, due to which the information in these fields were not passed to the opcode for proper opcode functionality.

3-9267909481

19164918

In multi-schema account migration using Conversion Manager, when other accounts were created using standard account creation opcodes, the POID_ID0 field of the /uniqueness object was not mangled resulting in an unique constraint violation error.

3-9044443971

19170129

When a service for an account having purchased discounts was inactivated first and later the service was reactivated and the discount was repurchased, the discounts were not getting applied.

3-8841891961

19172383

When purchasing one-time deal to an existing service, the Customer Center plans tab was showing the correct product name, but the deal name was incorrect.

3-8894533131

19194696

While calculating payment incentives, the TOTAL_DUE (that included the previous dues) was incorrectly mapped instead of just the current month due. Due to this the payment incentive calculation was incorrect.

3-8963911221

19194698

During migration using Conversion Manager, the group object ID values were not properly populated and this was causing operations like PCM_OP_BILL_DEBIT to fail, which in turn was accessing the group sharing objects.

3-9311090061

19202345

The pin_discount_cleanup utility was crashing.

3-9294585111

19217389

When more than one discount was present with sequential discounting enabled, the discount calculation was incorrect and impacted the balances.

3-9347295804

19219139

When trying to launch Customer Center with Java Webstart, the JAR resources in JNLP file are not signed by same certificate error message appeared.

3-9527135271

19227016

Every time the BufferLimit and/or StoreLimit parameters were updated, the index was getting recreated for FCT_DuplicateCheck in Pipeline Manager. This was taking a long time to complete and there was no control to make it optional.

3-9121968561

19227161

When a bunch of accounts were migrated in bulk using Conversion Manager, the timestamps for created_t, effective_t, and mod_t were inconsistent in the UNIQUENESS_T and AU_UNIQUENESS_T tables.

3-9028194391

19236913

When using Conversion Manager with multi-threading, an ArrayIndexOutOfBoundsException exception was thrown.

3-9028022821

19246390

When data was migrated from older releases like Portal 7.2.1 to BRM 7.5, FCT_DuplicateCheck was failing due to the way the search key was derived. Earlier to BRM 7.5, the search key was directly inserted into the database, whereas in BRM 7.5 a hashed value was being inserted. So on a migrated instance, the FCT_DuplicateCheck plug-in was failing, because it was expecting a hashed key rather than the actual key.

3-9219324731

19246395

When unit was DAYS, daylight saving time (DST) was not considered for calculating the relative time, which resulted in incorrect values for the product cycle timestamps.

3-9309315781

19246403

During the delay period, a backdated cancellation was pushing the discount refund to the next bill cycle.

3-9348642551

19254938

The ERA Extension APIs used the local time rather than the UTC time. This was resulting in inconsistent behavior.

3-9302735771

19276557

During the inactivation of a subscription, an incorrect end_t was calculated and was being used.

3-9309315781

19276560

When two discounts were configured with sequential discounting enabled, canceling one discount was causing the other discount to be applied during the next cycle instead of current cycle.

3-9320949131

19284834

When the product end date was changed within the cycle, the cycle forward charges were getting unnecessarily applied even though the charges were already applied.

3-9375886241

19295129

Open billing was failing because of locking of balance groups.

2-5816784

19304275

During plan transition, there was an issue with credit limit exceeding for prepaid scenarios.

3-9389962401

19305846

A tailor-made product that had a future cycle_start in the current cycle was getting skipped.

3-9248293521

19323346

In Customer Center, it was not possible to transfer balance if it had a negative decimal amount.

3-9198088431

19323348

During plan transition, if there were any common services, the service orders were created only for deactivation and the rest of the activities through the provisioning flow were not considered.

3-9362428291

19334711

If you were not using tailor-made products, the locks on the derived rateplans were not getting released. This was increasing the number of locks in the system, and over a period of time they reached a critical point, which was resulting in shutting down the pipeline process. With this release, the locks on the rateplans are released properly. Additionally, you can set the TailormadeProductsSearch business parameter to disabled to skip locking the rateplans.

3-9373391501

19336565

During the BRM 7.5 Patch Set 8 installation, pin_setup was failing. This was due to the installation scripts pointing to Perl 5.8.0 instead of newly packaged Perl 5.18.2.

3-8855926111

19344824

In Pricing Center, whenever a rate description was modified for a product, a new rate object was created, without deleting the old rate object.

3-9138903801

19344829

In Pipeline Manager, even after reloading APN Map by passing a semaphore, it was still referring to old data.

3-7051155361

19408407

When a zone map was updated while the zoning PCM_OP_ZONEMAP_POL_GET_LINEAGE policy opcode was being run, sometimes it went into an infinite loop, and the process was hanging.

3-9416116906

19408411

In some scenarios the total tax from the written-off balance impacts was not matching those of the actual item totals.

3-9469185811

19445384

When the input data for collections did not contain the POID values, the process was dumping core.

3-8628294001

19445804

The rating pipeline stops and was erroring out with ERR_THREAD_EXCEPTION and invalid state change errors due to a local variable being accessed simultaneously across two different transactions in the FCT_EventOrder plugin.

3-9352596531

19466104

In a Services Framework enabled environment, when an account with a discount was first created and later the service was activated, the end date of the discount was getting set during the activation.

3-9508509961

19487669

When processing a CIBER record type 22 for Mobile Terminating Call with an Initial Cell Site field value 11 spaces (blank), the CIBER InProcessing pipeline rejected the call record with an error.

3-9436828911

19508032

The PCM_OP_BILL_ITEM_REFUND opcode was throwing a TRANS_ALREADY_OPEN error.

3-8612866981

19523820

When a system product was configured to give incentives to the customers who paid their dues before the due date, the payment incentives were not applied to customers who came out of collections making an over payment.

3-9383592677

19533783

When a product was purchased with a future cycle start date, the existing discounts, if any, were not applied properly.

3-7791124141

19561370

When fetching data from database in double format, rounding issues were identified in the Rogue Wave library.

3-9445909211

19561375

The pin_dd_schema was not working due to the updated version of Perl.

3-9294386997

19569312

Purify tests at customer site indicated that the subscription module read memory that was earlier freed.

3-9513444631

19587204

When updating a discount's purchase, cycle, and usage dates information, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was throwing an error.

NA

19616033

The PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode was not returning tax only disputes information to be displayed in Customer Center.

 

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