Release Of Oracle Communications Billing And Revenue Management 7.4 Maintenance Patch Set 1
(Doc ID 1358821.1)
Last updated on AUGUST 20, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0]
Information in this document applies to any platform.
Oracle Communications Billing and Revenue Management 7.4 Maintenance Patch Set 1 is released on 19 September 2011.
This announcement lists new, enhanced features of various components introduced in Oracle Communications Billing and Revenue Management (BRM) 7.4 Maintenance Patch Set 1.
NOTE: Please note that this patch set (Maintenance Patch Set 1), will become a pre-requisite for future patch sets on 7.4.
Patch IDs: 12754752, 13000786
Patch 12754752 contains main packages and BRM Client tools in English.
Patch 13000786 contains BRM Client tools localized in French and Spanish languages.
Summary of fixes to customer-reported tickets delivered in Maintenance Patch Set 1:
|SR Number||Bug Number||Description|
|3-2159138641||10161736||BRM now supports Oracle RAC database functionality through BRM Java API.|
|11926162||JCA Resource Adapter now supports additional ISO-8601 date formats.|
|3-3280303471||12312982||Payment Tool now processes files with batch sizes over 1,000 payments.|
|3-3607926261||12558264||Customer Center now passes the values for PIN_FLD_REASON_ID and PIN_FLD_REASON_DOMAIN_ID in the input flist to PCM_OP_AR_EVENT_SETTLEMENT based on the reason selected in the Settle Event Dispute dialog box.|
|3-3620990281||12561334||When rerating a previously rerated event (re-rerating), the impact type is now reset in case of PIN_IMPACT_TYPE_TAX_RERATED to PIN_ IMPACT_TYPE_TAX when backing out the event balance impacts.|
|3-3853144597||12674177||The loadpricelist utility now retrieves the products based on a specific service type and generates the XML file.|
|3-3727230661||12606736||While performing item adjustment with tax, a message is now displayed if the
taxation switch is not enabled for real-time taxation.
|3-1575538711||12667980||In previous releases, during billing, the database was queried multiple times for the same input search criteria. This led to performance issues.
To improve performance, the calls to the database for the same input search criteria are identified and the search results that are fetched from the previous call are used for billing instead of searching again in the database.
|3-2939633801||11877010||Customer Center now correctly displays the details of the charges per rated usage.|
|3-3632522551||12564169||In the case of a reversal batch with a bad reason code in the middle, BRM now successfully processes all the records, including the records before and
after the bad reversal code.
|12353430||When an account-level deal is associated with multiple account-level products and each deal is associated with an MCF/MCA event, if an account purchases this deal, after billing, there is a cumulative item for each event instead of individual items.|
|12381371||pin_rel no longer throws an error while loading recycled files.|
|3-3636639091||12575645||You can now update the registry values for the IgnoreEdrOnLock feature through the semaphore.|
|3-3697132591||12595658||If an error occurs when calling the PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS opcode, BRM now throws an error message and exits.|
|3-3687186161||12621954||Payment Center search now works correctly for custom/default payment methods when details from the payment attributes are used as search criteria.|
|3-2240904591||12627327||Previously, when a PartialBilling event was generated, it was followed by an ERR_STREAM_EOF error. This no longer occurs.|
|3-3870813761||12701368||In Linux, you can now successively send the kill -USR1 proc id command.|
|3-3625068021||12559729||In Payment Center, while recycling a suspended payment, two new payment items are created, and they both are now assigned correct G/L IDs.|
|3-2709584431||12586180||The IN clause of the search template is now created properly for PCM_OP_AR_GET_ACTION_ITEMS. The buffer size is now calculated based on the latest change in the search template.|
|3-3387301471||12586182||For paying accounts that have more than one /billinfo object, the names of the balance_groups are now correctly returned in the PCM_OP_BAL_GET_ACCT_BAL_GRP_AND_SVC opcode when the flag is 5.|
|3-3584198491||12625762||Payment is now allocated to an item if its transaction is open within the same transaction with pymt_collect command.|
|3-3617369621||12683314||The cycle_start notification event is now correctly generated only when there is a qualified product.|
|3-1777336591||12394066||Numerous opcodes were changed to enable multischema option for payments.|
|3-3277476571||12529468||The current dm_vertex executable works with Vertex CTQ 1.01.06.
A new dm_vertex_ctq10013 executable is added to support older Vertex CTQ 1.00.13.
|3-3277476571||12531451||dm_vertex now does not core dump with Canadian Tax Request.|
|3-3576485531||12616965||In case of hierarchy accounts with one parent and many child accounts, balance monitoring now includes all the charges. All the charges are rolled up to the parent /balance_group/monitor object.|
|3-3527936161||12691670||Changes were made to fix the error that occurs while deleting a schedule object in secondary schema from primary schema.|
|3-3617369621||12710989||Ordered Balance Group data is now refreshed when the service goes for an update from the database while processing a call details record.|
|3-3914106721||12725547||pin_collect does not fail in the secondary schema. Changes were made to set the database number correctly when the Revenue Assurance optional component is enabled.|
|New APIs were provided to use in the case of RAC databases. Changes were made to the Web Service and the pin_inv_doc_gen utility to use the new APIs instead of the single DB API.|
|3-3383178111||12580568||Support is now added for Polish locale with locale ID pl_PL.|
|3-3658294601||12674852||If billing is delayed for any account and it is pending for more than one cycle, the billing process will not set the billed item's effective_t. The item's effective_t will now be set to the end of the corresponding billing cycle.|
|3-4087158871||12751140||RE Loader stored procedure will now load the records successfully without failing at records with zero balance impact.|
Key Enhancements in BRM 7.4 Maintenance Patch Set 1
For more details about these changes and enhancements, please refer to BRM Maintenance Patch Set 1 documentation.
Vertex CTQ 2.00.x / STQ 4.x Certification
With this patch set, BRM now supports Vertex Communications Tax Q Series (CTQ) 2.00.x and Vertex Communications Sales Tax Q Series 4.x on Solaris, Linux and HP-IA platforms.
Multi Schema support for Payment UI Clients and Devices
With this patch set, you can now use Payment Center and Payment Tool in a multi schema environment. Also the Device Management framework in BRM now supports multi schema deployments.
Java Runtime 1.6 support
With this patch set, BRM 7.4 is now certified on Java Runtime Environment (JRE) 1.6.
The pin_inv_doc_gen utility now supports Oracle 11g RAC databases.
This patch set also includes BRM client tools localized in French and Spanish languages.
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