Release of Oracle Communications Billing and Revenue Management 7.5 Patch Set 16 (Doc ID 2177932.1)

Last updated on MARCH 20, 2023

Applies to:

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

Details

Oracle Communications Billing and Revenue Management 7.5 Patch Set 16 is released on 31 August 2016.
This announcement lists the enhancements and fixes delivered in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 16.

Patch ID: <Patch 24383183>

Key Enhancements:

Event Notification Configuration Enhancement

With this patch set, you can efficiently update event types in pin_notify using wild cards for a better design time experience. For more information please see BRM Documentation

Certifications:

With this patch set, Web Services Manager is certified on Oracle WebLogic Server 12c Enterprise Edition 12.2.1.

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

SR Number	Bug Number	Issues Fixed
3-5055201651	13566849	When a cycle product with proration was canceled, the cycle charges were not calculated correctly.
3-7845445021	17508188	The PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode was returning all payments irrespective of the threshold value. Opcode Flist Reference has been updated to reflect the actual behavior.
3-9985216391	20183379	The description of closed_t field in the bill object was not correctly indicating when this field was updated.
3-10667223261	20996132	Payment Tool was timing out due to a performance issue with the PCM_OP_AR_GET_BAL_SUMMARY opcode.
3-11100306391	21501457 24298600	The dm_vertex was failing with an error when multiple tax information was passed as input.
3-11274029641	21881000	When a balance group was transferred from one account to another, the return flist did not contain the required newly purchased product information for the destination account.
3-11515873601	22006333	When the pin_inv_accts utility was run, deadlocks were observed on account balance groups.
3-11580848801 3-12114762961	22158896 22740631	The pin_dd_to_schema script was not generating the complete XSD schema for storable classes.
3-11642142981	22573754 22588436 22588437 22627808	The INVOICE_DATA value for rerated batch usage events was incorrect when the INVOICE_DATA string length exceeded 4000 characters.
3-12036976641	22582506	The PCM_OP_IC_DAILY_LOADER opcode was failing when it was run by using Universal Event (UE) Loader.
3-11642142981	22588436 22588437 22627808	If the size of the PIN_FLD_INVOICE_DATA field was greater than 4000 bytes, the PIN_FLD_INVOICE_DATA field was ignored and the invoice displayed a zero amount.
3-10705203421	22655347	Even when bill suppression was enabled, zero-valued bill items were being created at the time of billing.
3-10750802301	22724240	If rerating was done in a delayed billing period, rolled-over resources from the last completed accounting cycle were not processed properly, leading to incorrect resource balance impacts.
3-11932780481	22730114	When importing data into BRM by using Conversion Manager, the service-level promotion data was rejected.
3-12000405661	22748339	When a price list was updated in Pricing Design Center (PDC) and synchronized with BRM, the PCM_OP_PRICE_SET_PRICE_LIST opcode failed with an error.
3-11880725231	22763774	Corrective billing operation was not calling the PCM_OP_BILL_POL_SPEC_BILLNO opcode when the bill number format was customized.
3-11618027191	22811706	Pricing Center was throwing an error when a product with a rate plan was selected.
3-11959116791	22831805	Customer Center was not validating the override amount and discount amount entered for purchase and cycle fees against the amount range set by using Permissioning Center.
3-11698443221	22834515	In a multischema system, payments made for written-off accounts or for accounts in the secondary schema, which are not billed for a few cycles, were not successful if made through Payment Tool.
3-12036318891	22834701	The PCM_OP_BAL_GET_ECE_BALANCES opcode reference included the PIN_FLD_BALANCES array instead of the PIN_FLD_BAL_IMPACTS array.
3-12374243801	22859580	When a hierarchy of accounts was billed, and a bill search was done after the billing, the results were incorrect because the search operation was not grouping the results based on the parent bill object.
3-11598661051	22900599	When a subscription was transferred from account A to account B and then back to account A, Pipeline Manager was failing to rate any usage for services associated with account A.
3-11615508101	22900605	While rerating rated events for hierarchical accounts with sponsor groups, if any of the original event had a sponsor balance impact, an item transfer was incorrectly triggered.
3-12222709621	22900611	The file description handlers opened by the pin_rel utility were not closed even after successfully processing the rated event files, and this was causing an error.
3-12340452461	22914083	Customer Center was accepting only 10-digit voucher PIN instead of 12 digits.
3-12268786281	22965000 22997214	Even if pin_virtual_time was enabled, Pipeline Manager was using the system time instead of pin_virtual_time, resulting in inconsistent output.
3-12284111761	22969395	Java Portal Communication Module (Java PCM) was only supporting the PIN_XML_BY_SHORT_NAME type of XML files as input for the xmlToFlist API, and this was impacting the performance of Java PCM. The XmlToFlist API now supports even the PIN_XML_BY_NAME type of XML files as input.
3-12077416621	22974343	JCA Resource Adapter was not considering the timeout (in milliseconds) configuration.
3-12403659151	22999620	Taxes were incorrectly applied because the PCM_OP_CUST_POL_TAX_CALC policy opcode selected incorrect locales for applying tax.
3-12380336861	23010127	There were performance issues while trying to delete a payment method from a bill unit.
3-12202890451	23016705	DAT_AccountBatch did not consider the ProfilesNotLoadedIntoEdr registry entry for retrieving account data from the BRM database. This was resulting in incorrect charging of the account.
3-12377373051	23038870	The pin_collect utility was not considering daylight saving time (DST) when start and end dates were specified.
3-12283528931	23082792	While deploying Web Services Manager on the Tomcat server, an error was displayed.
3-12454313361	23130331	Batch rating of corporate or large accounts with each account having large number of services was affecting the performance of Pipeline Manager. The performance of Pipeline Manager for batch rating of large accounts is now improved.
3-12545355561	23133662	The Java server was not handling all types of exceptions and hence any custom service using the java server was exiting abnormally.
3-12323233041	23153186	In Payment Tool, after changing the password for the first time, the password was not expiring even after the specified number of days.
3-12486171031	23173729	The cycle fees were calculated incorrectly for accounts migrated with multiple rate plans.
3-12388438191	23189574	When the product end date was the same as the product start date, the refund for the product was applied twice if auto-triggered billing was enabled for the account.
3-12342817211	23209097	When multiple discounts were configured in the cascade mode and the credit check was enabled, the charge packets were incorrectly split. This was leading to errors.
3-12373678031	23209908	When the discount offer was configured in PDC and then purchased for an account in BRM, the discounts in that offer were not applied even if the discount offer was configured to be effective immediately after the purchase.
3-11852984381	23235096	Pipeline Manager was incorrectly considering only older item POIDs for billing even after running Bill Now.
3-12445911211	23246386	Pipeline Manager was sometimes failing with errors without handling the situation gracefully.
3-11495174191	23251348	When a product was purchased, a previously canceled discount was considered for calculating the discount for that product even if no discounts were purchased for that product.
3-11878456711	23251354	A cascade discount which is of low priority was applied even after the entire charge packet was evaluated and discounted by the sequential discount.
3-12504192321	23259588	When a deal was purchased, the workflow was internally invoking the PCM_OP_ACT_USAGE opcode twice in the CALC_ONLY mode. This was leading to errors.
3-12434179761	23259597	In Pricing Center, when you select an existing discount and click the Detailed Discount info tab, the following error was displayed: There is already a discount in the database with this name. Enter another name, and try again
3-12643536841	23275535	The performance of the credit profile search function has now been improved.
3-12587445691	23275537	In Customer Center, Event Browser was sorting the events based on date instead of month.
3-12558102191	23275541	If billing cycle frequency was changed from monthly to quarterly, the CHARGED_TO_T table was not in synchronization with the NEXT_BILL_T table.
3-12641416411	23282974	When a monthly cycle product was deactivated and reactivated on the same day, the refund amount was not rounded properly because of rounding discrepancies.
NA	23305816	After updating Public User Identity (PUID) for a customer, if rerating was run, it failed with error.
3-12240382681	23313608	The tax exemption was not properly taken into consideration for bill-level adjustments and was leading to incorrect tax calculation.
3-12166242231	23313612 23321069	The performance of the agent tasks list filter in Collections Center has been improved.
3-12465715931	23321067	When a SIM number of a customer was changed, the SERVICE_ALIAS_LIST_T table was not populated with the change. As a result, the customer was not able to use the service.
3-12337146091	23324796	The Collections Scenario object was updated even if there was no change in its data.
3-11873951621	23338036	The pin_rerate utility was not supporting any custom fields.
3-12718771361	23345973	Billing was failing due to an issue with journals update.
3-12437095421	23477401	The Subscriber Lifecycle Management (SLM) feature did not support changing the states manually.
3-12431591421	23484524	When the billing DOM of a customer was changed, the old billing DOM was considered for billing instead of the new billing DOM.
3-12654995364	23484529	JCA Resource Adapter was substituting NULL POIDs with -1. This was causing opcodes to fail.
3-12592091731	23504062	The PCM_OP_CUST_DELETE_PAYINFO opcode was dumping core while logging errors.
3-11221300411	23511636	After a discount was canceled, it was not refunded to the customer.
3-11999870941	23511638 23625091	When a subscription transfer was performed, the validity dates were not properly synchronized and in some cases valid-to dates were earlier than valid-from dates.
3-12462917501	23525693	Updating the data dictionary in a multi-schema system by using the pin_deploy utility with the replace parameter failed with an error.
3-12817579931	23540419	The applicable discounts were not triggered for accounts migrated by using Conversion Manager.
3-12199073961	23541931	The pin_event_extract utility was dumping core while processing large records.
3-12522649241	23562128	The Connection Manager (CM) was taking an unusually long time to cache impact categories for large rate plans.
3-12444157381	23562131	It was not possible to remove the invoice payment type or override any default payment types in the pay_type entry in the pin_collections configuration file.
3-12480280741	23568900	The dm_fusa was not supporting the new two (2) series Bank Identification Number (BIN) range.
3-12647476131	23572494 23750675	The dm_vertex did not support detailed tax override input to Vertex CTQ limiting its functionality.
3-12648686821	23584601	The pin_cycle_fees utility was passing incomplete information to the MTA_WORKER_JOB_DONE policy opcode.
3-12800014741	23584604	It was not possible to add regular expressions for event types in the BRM_home/sys/data/config/pin_notify file.
3-12703847971	23591943	While migrating accounts by using Account Migration Manager, the data in the EVENT_ESSENTIALS_T table was not completely migrated.
3-12289669581	23632579	The refund for a backdated cancellation was applied to an incorrect bill.
3-12021174581	23643943	The PCM_OP_SUBSCRIPTION_SHARING_GROUP_SET_PARENT opcode was failing in cases where a discount sharing group existed, but it was not associated with any discount.
3-12910977581	23645760	The LoadPriceList utility was failing with errors while updating discount descriptions.
3-12837866961	23697852	It was not possible to start Customer Center after upgrading from BRM 7.5 Patch Set 11 to BRM 7.5 Patch Set 15.
3-12865935611	23698566	When the time-stamp rounding was disabled, discounts were not calculated properly because of incorrect cycle start dates for purchased discounts.
3-12341554256	23699332	In Payment Tool, the channel ID was not properly assigned to individual payments.
3-12452686011	23717288	The EAI Java Server or eai_js was failing due to memory corruption.
3-12749292641	23724483	When some events were already generated for an account for the billing cycle and later in the same billing cycle if the charge or discount sharing was configured for that account, billing failed with error.
3-12831213851	23731708	If selective rerating was performed based on product IDs, the discount-only events were not considered for rerating.
3-12228822261	23734922	Parallel discounts were not working when one of the charges was a noncurrency resource and the discounts also impacted the same noncurrency resource.
3-12819905941	23736820	Customer Center was not supporting the new MasterCard two (2) series range.
3-12918802781	23743609	The PCM_OP_SUBSCRIPTION_READ_ACCT_PRODUCTS opcode was using an incorrect search template.
3-12588673231	23748049	When rerating after a subscription transfer, adjustments created for an event with a time stamp earlier to the subscription transfer were incorrectly referring to the new bill unit instead of the original bill unit.
3-12108079471	24288417	When corrective billing was run, the pin_inv_export utility generated both original and corrected invoices.
3-12972611701	24296212	When the pin_deferred_act utility was run for multiple refunds to an account, the corresponding balance group was not locked resulting in multiple threads accessing the same balance group at the same time causing incorrect results.
3-12570234591	24370489	The pin_round_beid function was affecting the performance of ledger reports generation.