Release of Oracle Communications Billing and Revenue Management 7.4 Patch Set 18
(Doc ID 1564992.1)
Last updated on SEPTEMBER 17, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]Information in this document applies to any platform.
Details
Oracle Communications Billing and Revenue Management 7.4 Patch Set 18 is released on 10 Jul 2013.
This announcement lists the fixes and enhancements in various components delivered in Oracle Communications Billing and Revenue Management (BRM) 7.4 Patch Set 18.
NOTE: Please note that the Maintenance Patch Set 1 is a pre-requisite for this patch, for server components including optional managers and also for client applications.
NOTE: BRM 7.4 Patch Set 18 is cumulative from BRM 7.4 Patch Set 12 and includes all the changes introduced from Patch Set 12 onwards.
Patch ID: 16658459
Summary of fixes to customer-reported tickets delivered in Patch Set 18:
SR Number |
Bug Number |
Issue Fixed |
3-5687642121 |
14097100 |
The BRM out-of-the-box report templates were generating an error while fetching the report data. This was due to the UTF-8 issue. |
3-3848978661 |
14362828 |
In the previous releases, the same refund amount was being shown twice: once in the billed-earned report and again in the previous-billed-earned report. |
3-5916852131 |
14538036 |
The FTP or SFTP was not working in BI Publisher. The pin_inv_doc_gen utility was changed not to construct a delivery request when the delivery configurations in pin_inv_doc_gen's Infranet.properties is set to an empty value. |
3-6056883991 |
14755552 |
In the previous releases, when profile sharing is used for CUG promotion, the CUG flag was not being set. |
3-6351718824 |
14793459 |
In the previous releases, the cancel event was not being generated for tailormade products. This has been fixed. The pin_cycle_fees utility in cancel mode will update the status of tailormade products when executed after end date. |
3-6166015201 |
15827569 |
In the previous releases, BRM was not always honoring the order in which item tags were specified in the config_item_tags.xml configuration file. Note: This fix may result in an undesired item tag being used if the incorrect order was producing the correct results. In this case, check the order and realign. |
3-5578174271 |
15878486 |
In the previous releases, the suspense manager was not displaying the recycle time in the local timezone. This has been fixed. A new entry, display.local.timezone, is introduced in the custom.properties file, which when set to true, will display all times in the local timezone. If set to false, the earlier behavior continues. |
3-6256008521 |
15897283 |
In the previous releases, CMT was not managing rollovers correctly. This has been fixed. A new element, RollData, is added in the Sub balances array in the CMT_Balances.xsd file. If RollData is populated in the XML, the CMT application will use the rollover specified in the XML, otherwise CMT will compute its own rolldata value based on UOR and Frequency. |
3-5967291991 |
15922534 |
It is essential to make sure that all the children are billed before billing the parent. A new billing business parameter, SkipCheckForSubordinatesBilled, has been added that will allow you to enable/disable checking that all the children are billed before billing the parent. The default is false, enabling the check. |
3-7331902991 |
15943877 |
In the previous releases, sometimes it is observed that there is a mismatch between the count of EDRs sent for recycling and the actual number of EDRs recycled. |
3-6246774861 |
15959593 |
In a parent child account scenario, if the child account is transferred, such as from prepaid to post paid, its /ordered_balgrp can have a new instance. This results in more than one /au_parent objects for the child service in the /au_ordered_balgrp resulting in SQL exceptions. |
3-6612054981 |
16059493 |
Whenever a BRM object is added or modified, the MOD_T field is updated with the timestamp of the operation. This was not happening for the /bill object. This has been fixed so that MOD_T is getting updated in the bill_t and billinfo_t tables. |
3-5398269781 |
16102995 |
In the previous releases, the deferred taxation performance was poor when there are entries in the temporary table of events not yet processed by RE Loader. |
3-6177090101 |
16191185 |
In the previous releases the Account Migration Manager (AMM) for migrating accounts across schemas was hanging at POST_MIGRATION_WAITING status. |
3-5363354871 |
16191191 |
When a 30 day proration is enabled and the end date of a discount is changed, the balance impacts were incorrect. |
3-6553157811 |
16191201 |
In case of a discount sharing group, when a product is canceled, the shared discount was not refunded. |
3-6625636981 |
16194470 |
In the previous releases, the purge utility execution was failing when a huge volume of data was involved. The queries are now modified to handle high volume data. |
3-6670592051 |
16195976 |
While creating an order in Voucher Administration Center, a deal is associated with the order. If it is a service level deal, then the deal details like Resource, Quantity, Amount, ValidFrom, ValidTo were not being displayed. |
3-6688704381 |
16212990 |
When the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode is invoked with flist having discount POID as NULL, it returned an error, but it did not close the transaction opened internally. This has been fixed. If the discount POID in the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode flist is NULL, the transaction will be aborted. |
3-5848566207 |
16216631 |
In the previous releases, the PCM_OP_RATE_EVENT opcode was not returning the custom information structures that are passed in rating input flist. |
3-6430427641 |
16228416 |
In the previous releases, while trying to do 100% Bill Level adjustment from the Customer Center, an incorrect GLID was being assigned. |
3-6746248491 |
16264023 |
In the previous releases, dm_oracle reports an error while trying to create the /reservation_list object for newly created accounts where the value of POID_IDS2 sequence is greater than 2147483647. |
3-6536108181 |
16273944 |
While creating duplicated EDRs, the FCT_SUSPENSE plugin was not populating all the fields correctly. There were fields missing in the duplicate EDR. |
3-6558232211 |
16290242 |
In a multischema environment, when pinlog_open was concurrently accessed, the pin_inv_accts utility sometimes failed. |
3-6496853051 |
16293978 |
In the previous releases, sometimes billing was failing with memory corruption error. |
3-6794353871 |
16314151 |
In the previous releases, when an account is suspended, the Monthly Cycle Forward charges with Prorate set to Y was applying the whole amount instead of the prorated amount. |
3-5937980521 |
16323157 |
In the previous releases, when the rollover events generated were high, rerating was resulting in an out of memory error. |
3-5316366321 |
16329172 |
In the previous releases, if a product was configured with Prorate=N with an in-advance billing, when canceling the product, the charges were not refunded correctly. For example, if the in-advance fee was collected for Jan and Feb on Jan 1st and the product was canceled on Jan 15th, the charges from Jan 16th to Jan 31st were also refunded. |
3-6762112098 |
16343193 |
When a database connection could not be established, dm_oracle prints the DB Username and Password in clear text in the dm_oracle.pinlog file. This has been fixed so that the passwords are not displayed in log files. |
3-6770524071 |
16346426 |
In a multischema setup, after terminating a transaction if you tried to open a new transaction on the same object type, it was throwing a TRANS_ALREADY_OPEN error. |
3-6398560431 |
16360209 |
In the previous releases, the item assignment was not correct after subscription transfer. |
3-6802673491 |
16367070 |
In the previous releases, if a product was purchased for an account (activated in the past) on the current date with the product start date in the future, the cycle fees applied was incorrect. |
3-6612054981 |
16409851 |
Whenever a BRM object is added or modified, the MOD_T field is updated with the timestamp of the operation. This was not being done by PIN_REL_UPDATER.SQL. After processing an EDR, MOD_T is getting updated in the bal_grp_t table. |
3-6878694537 |
16425433 |
In the FM_CUST_POL policy, Papua New Guinea was incorrectly spelt. |
3-6808115451 |
16426583 |
In the previous releases, Collection Center was dropping characters while writing them to the database. |
3-6804436351 |
16426596 |
In the previous releases, the suspended payments were under the customer account instead of the suspense account. |
3-6731225751 |
16431350 |
In the previous releases, dummy deal purchase was failing when the validate_deal_dependencies parameter was enabled. When the dummy deals is purchased, they will not be validated if they do not have any restrictions configured. |
3-5236524741 |
16452435 |
In Discount Sharing Group scenarios, where sequential discounting is enabled, updating the discount with an end date was not resulting in refund for member services. This has been fixed. |
3-6840187551 |
16452442 |
In the previous releases, when the timezone (TZ) is set to America/Sao_Paulo and billing delay is set, the account was not billed immediately after the delay period. In this case, the delay end time was not rounded to mid night. |
3-6878694537 |
16473836 |
In the FM_CUST_POL policy, country names and locales were missing. |
3-6645466991 |
16477207 |
In the previous releases, pipeline was triggering business event processing even when it was not meeting any of the conditions in DAT_Listener required to start business event processing. The listener's interleaving was not working as expected. |
3-6661589111 |
16484487 |
In the Suspense Management Center spanish version, there was an error in the label of bulk search criteria for purge. |
3-6204691689 |
16488470 |
In Pipeline Manager, while validating the number of fields in the input file, if the number of fields is one less than that defined in stream description, an incorrect error message was thrown. A check on the number of fields in the input file has been added, and now the appropriate error message is displayed. |
3-6385736491 |
16488477 |
In the previous releases, the batch controller was logging errors after successfully processing a rerate request file. |
3-6825956161 |
16502362 |
In the previous releases, the START_T value was incorrectly being set and was same as END_T in the credit-threshold notification xml. |
3-6743793501 |
16502368 |
The RUM quantity needs to be recalculated if the corresponding candidate product is not used. If the candidate product, selected is the very first product, then no recalculation is done. This has been fixed. the RUM is recalculated regardless of the current product location in the product list, as long as the rated quantity is still zero. |
3-6926130931 |
16539701 |
In the previous releases, multiple devices swapping in one request was generating an incorrect service order. |
3-6559585011 |
16572106 |
During the delayed billing period, if a monthly cycle arrear deal backdated to the previous month is purchased and then the end date of the same deal is updated to the end of the current month, the monthly charges are not calculated correctly. |
3-6898960621 |
16589547 |
If BRM is configured to generate separate tax event for write-offs, in cases where the event has more than one tax balance impact (with the same PIN_FLD_QUANTITY and TAX_CODE), the amounts in journal_t.cr_ar_net_amt and journal_t.cr_ar_tax_amt for a write-off entry are incorrect. If the event has more than one tax balance impact (with the same PIN_FLD_QUANTITY and TAX_CODE); then these multiple tax balance impacts are combined into one tax balance impact. |
3-6730679201 |
16600767 |
When moving accounts under a hierarchy from paying to non-paying type, an error occurred if the paying account being moved as non-paying is closed. |
3-6521951561 |
16600771 |
With this patch, the pin_bill_day utility was optimized to improve the performance of calculating cycle forward fees. |
3-6988827201 |
16607114 |
In the previous releases, pipeline was freezing when a semaphore was sent prior to the completion of the earlier one. |
3-6738918671 |
16612611 |
In the previous releases, during inactivation or cancellation on the same day as the billing date, fold was considering invalid buckets and was generating incorrect balances. |
3-6900498371 |
16613143 |
In the previous releases, an account level adjustment with tax was failing. |
3-5558210141 |
16621761 |
In the previous releases, rerating is run, the EARNED_START_T and EARNED_END_T values are set to the current time. Rerating now takes care of setting the earned period of the adjustment to match the cycle event for non-GL posted cycle events. In case the GL posting is already done for the event, the adjustment created from rerating will have EARNED_START_T and EARNED_END_T fields as the current time. |
3-6904646871 |
16629292 |
In a multischema setup, when calling the PCM_OP_PRICE_COMMIT_PRODUCT opcode to delete a product, it was deleting that product even if the product was purchased by an active account. |
3-6924316611 |
16656886 |
In the previous releases, when the credit control notifications were generated by pipeline, the time stamp of the call details were incorrect. A new field, TIMEZONE_ID, is added in the balance breach notification XML which has the UTC-offset value of the CDR. The XSD file is also updated accordingly with this new field. |
3-2203320611 |
16660463 |
In the previous releases, Pipeline Manager had intermittent issues with closing intermediate files. |
3-7042543211 |
16672127 |
In the previous releases, the pin_cycle_fees utility with purchase option was hanging when there were products with no purchase fee event defined. |
3-6901848941 |
16686140 |
Whenever a CDR was processed and filter set rule did not match, the "EDR index creation failed: illegal blocktype" error was logged. This error was being reported because of memory corruption. This has been fixed. The filter set data is now extracted from the global memory pool, thus avoiding any possible memory corruption. |
3-6069999361 |
16715859 |
For products with multiple /rate_plan objects, some of /rate_plan audit instances are not picked up by rating. As a result, the corresponding rates are not found during the cancellation process. This has been fixed to retrieve audit /rate_plan from a given product by their unique name and currency combinations. |
3-6967792101 |
16723614 |
In the previous releases, when the pin_ledger_report utility is run with the export option, the transaction was taking a long time and the commit was occurring only at the end. The option was ignoring the pin.conf's transaction_grouping parameter. This has been fixed so that you can now specify the number of accounts to include in each transaction. |
3-6688784471 |
16767269 |
In the previous releases, the PCM_OP_SEARCH opcode was not returning all the second level arrays and it was only returning the first second level array mentioned in the PIN_FLD_RESULTS. The PCM_OP_SEARCH opcode now returns all second level arrays mentioned in PIN_FLD_RESULTS. |
3-6837530731 |
16832782 |
In the previous releases, rerating failed in the case of item type product rerating, if PACKAGE_ID was not present in the purchase event. This occurred when a customer was created without a deal. |
3-7250955071 |
16945583 |
In the previous releases, the resource names containing numbers were being truncated due to which their validity was also being affected. |
3-4991121561 |
13897894 |
The iScript ISC_GetResourceBalance.isc was not available at IFW_home/iScriptLib/iScriptLib_Standard. This has been fixed now. Also, updated signature of getResourceBal function is used in the iScript. |
Key Enhancements in BRM 7.4 Patch Set 18
For more details about these changes and enhancements, please refer to BRM Patch Set 18 documentation.
General Ledger Data Enhancements
Since creating fewer journals improves system performance, you can now control the creation of journals for non-currency resources by setting the new NonCurrencyResourceJournaling business parameter.
Invoicing Enhancements
You can now use Oracle Business Intelligence Publisher (BI Publisher)11g to design, generate, and customize BRM invoice documents and reports.
Certifications
With this Patchset, BRM 7.4 is certified with Java 7
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 |