3 Summary of Customer-Reported Fixes
The Oracle Communications Billing and Revenue Management (BRM) 15.0 release includes customer-reported bug fixes.
Topics in this document:
Customer-Reported Fixes in BRM 15.0.1
Table 3-1 lists the customer-reported issues that were resolved in BRM 15.0.1.
Table 3-1 Customer-Reported Fixes for BRM 15.0.1
| Bug Number | Description |
|---|---|
| 35377607 |
When values in the pin.conf configuration file were set as environment variables, the BRM pin.conf reader would remove the last character from the variable value if the length of the environment variable key and value were equal. This has been fixed. |
| 35904016 |
In the set of files provided to Rated Event Manager (REM) by ECE, ECE was returning the files in a different order, causing a NULL pointer exception. This has been fixed by sorting the temporary files in natural order and the done files in reverse order, to ensure that the header file is always processed last. |
| 35937539 |
Memory leaks were detected when pin_deploy was run for very large batches. This has been fixed. |
| 35949445 |
When the PCM_OP_BILL_ITEM_TRANSFER opcode was called, the transfer of the credit amount to a new bill was failing. This has been fixed. The PCM_OP_BILL_ITEM_TRANSFER opcode has been modified to make the credit transfer possible. |
| 36008442 |
Rated Event Manager (REM) was unable to deserialize events due to the addition of the field PIN_FLD_GRANTED_BAL in the EVENT_ESSENTIALS_T table. This has been fixed. |
| 36048820 |
There was no policy hook available for modifying the input flist of PCM_OP_SUBSCRIPTION_PURCHASE_DEAL. This has been fixed. A new policy hook has been added to the PCM_OP_SUBSCRIPTION_POL_PREP_OFFERRING policy opcode to customize the input flist being sent to the PCM_OP_SUBSCRIPTION_PURCHASE_DEAL, PCM_OP_SUBSCRIPTION_PURCHASE_PRODUCT, and PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcodes. Through this policy hook, the user can modify the flist and add custom logic to override default pricing amounts for both /purchased_product and /purchased_discount. |
| 35863453 |
While invoking the cancel discount opcode, if the PIN_FLD_END_T field was passed, it was not being set to the PIN_FLD_EFFECTIVE_T field, due to which wrong charges were applied. This has been fixed by setting the PIN_FLD_END_T field to PIN_FLD_EFFECTIVE_T. |
| 35884131 |
When a product was configured with multiple events, one of the events failed due to a credit limit exceeded error with rating status 29 but the other events were successful. Additionally, cycle fee dates were not getting updated for successful events. This has been fixed. |
| 36032625 |
When a charge offer with an annual subscription event was purchased, during the PCM_OP_BILL_MAKE_BILL opcode execution, unnecessary updates were made to the BILL_INFO_T and PURCHASED_PRODUCTS_T table, which was causing a billing performance issue. This has been fixed. |
| 36032623 |
When a non-currency resource containing a grantor_obj as NULL was being canceled, the validity of the sub-balance of the non-currency resource was being updated to the current time. This has been fixed. |
| 36076651 |
After upgrading from BRM 12.0 Patch Set 3 to Patch Set 7, charging dates were rounded to midnight. Due to this, any customization in FM_SUBSCRIPTION_POL_SPEC_CYCLE_FREE_INTERVAL.C updated the PIN_FLD_CHARGED_TO_T based on customer-specific time zones. Due to the rounding issue, customization to PIN_FLD_CHARGED_TO_T was being overridden in FM_SUBSCRIPTION_CYCLE_UTILS.C and rounded off to midnight. This has been fixed. |
| 36041326 |
Memory leaks were detected when the PCM_OP_SUBSCRIPTION_CRUD_OFFER_OVERRIDE opcode was invoked with the offering_override_values POID. This has been fixed. |
| 36047468 |
The partition_utils utility was not logging the SQL statements to the partition_utils.log file when invoked with the purge option. This has been fixed. |
| 35937536 |
When the PCM_OP_BILL_ITEM_TRANSFER opcode was invoked from a batch payment, the session object was missing for credit_items. This issue has been fixed by setting the PIN_FLD_SESSION_OBJ field, which is now sent as part of the input flist. |
| 35937542 |
After upgrading from BRM 12.0 Patch Set 3 to 12.0 Patch Set 7, when the PCM_OP_PYMT_TOPUP opcode was invoked after a checkpoint, an incorrect error was getting logged. This has been fixed. |
| 36066780 |
There was an issue with setting the font size of text in Customer Center. This issue is fixed by giving the Java option -Dfontsize. |
| 35863980 |
When PCM_OP_SUBSCRIPTION_CANCEL_PRODUCT was called from pin_cycle_fees -defer_cancel, there was no option to pass the flag to retain the rollover bucket. Due to this, the rollover bucket from the previous month was ending. This issue has been fixed by changing the PCM_OP_SUBSCRIPTION_POL_SPEC_CANCEL policy opcode to accommodate the action flags used to retain the rollover bucket. |
| 35979292 |
When billing was run, cycle_forward was called first with defer mode, then with normal mode. During defer mode, the product was being rated in calc_mode even though the product was not eligible to be rated. This issue has been fixed by making changes to avoid calc_only rating if the product is not eligible to be rated. The get_purchased_offerrings() call has been optimized to return the results quickly. |
| 35892698 |
When a product was purchased with multiple quantities and then canceled with partial quantity, the product status was shown as canceled. This caused a synchronization issue with ECE. This has been fixed. |
| 35856189 |
When the 31-day billing feature was disabled, if a non-aligned monthly cycle-forward product was purchased on a date after the 28th, cycle alignment dates were incorrect. This has been fixed. |
| 35863982 |
When an account-level product was canceled, a lock at the account level locked all balance groups in that account, causing issues with concurrent transactions. This is fixed now by passing LOCK_DEFAULT flags, which locks only account-level balance groups. |
| 36450389 |
A CDR was getting suspended in a delayed billing period where the current_bal was 0 and the next_bal was negative. This has been fixed. |
| 36215710 |
The PCM_OP_LOAN_GET_LOAN opcode has been enhanced to display profile details when a flag is passed. When this flag is passed, the credit_limit and available_loan_limit are retrieved from the profile. |
| 35937533 |
Issues were reported with SEL while loading the suspended events. This has been fixed. Unique custom control files are dynamically generated for each suspense file during the pre-processing stage of Suspense Manager. |
| 36272404 |
The PCM_OP_AR_GET_ACCT_BILLS opcode is enhanced to return PIN_FLD_TOTAL_DUE of the bill. |
| 36272406 |
When PCM_OP_RATE_GET_PRODUCT was invoked, it was not reading from the CM cache during execution, even though the rate_pre_cache_product_and_disc business parameter was set to 10. This has been fixed. |
| 36277112 |
Timeout errors on the CMT loader were resulting in errors. This has been fixed. The generation of POID logic was changed for multi-schema scenarios. |
| 36314282 |
When Bill Now was run for two bill units having the same account at the same time, a deadlock would occur due to which Bill Now would fail. This has been fixed. |
| 36317969 |
When the PCM_OP_BAL_TRANSFER_BALANCE opcode was invoked with FEE_FLAG set to 3, it returned multiple zeros for the PIN_FLD_TRANSFER_FEE field in the return flist. This has been fixed. The PCM_OP_BAL_TRANSFER_BALANCE opcode has been changed to honor the rating_max_scale pin.conf entry instead of using the maximum scale for precision. |
| 36357638 |
Compilation of FM_SUBSCRIPTION_POL was failing after upgrading to BRM 12.0 Patch Set 8. This has been fixed. |
| 36359985 |
When the PCM_OP_AR_EVENT_ADJUSTMENT opcode was invoked, it returned a generic error description for all errors. This has been fixed. The PCM_OP_AR_EVENT_ADJUSTMENT opcode returns the error message from the error buffer. |
| 36378649 |
For an add-on purchase, the original balance got accumulated instead of being synchronized in the ECE cache. This has been fixed. |
| 36430111 |
In a hierarchical setup, the child's due amount was getting added in an intermediate non-paying parent's due amount, because of which the exact amount of child's due was not calculated. This issue has been fixed by adding a new business parameter add_child_due_in_intermediate_parent_bill to add only the child's due value when the parameter is set. |
| 36434781 |
THRESHOLD_FROM and THRESHOLD_TO of the pipeline IFW_PRICEMDL_STEP table supported up to 15-digit decimal only. This has been fixed. The fields are modified to support up to 28 digits when MAX28DIGIT_DECIMAL_SUPPORT=Y is enabled. |
| 36196199 |
An enhancement is made to generate PRE_EXPIRY and POST_EXPIRY notifications at the granular level to enable or disable in-advance and post-expiry notifications. |
| 36076657 |
Memory leaks were detected when invoking the PCM_OP_CREATE_OBJ opcode. This has been fixed. |
| 36130454 |
The PCM_OP_PYMT_VALIDATE opcode has been modified to store tokens in case of an error from Paymentech. |
| 36041556 |
The PCM_OP_ZONEMAP_POL_GET_LINEAGE opcode was taking a prolonged time to return results. This has been fixed. |
| 36475412 |
Proration of a fixed discount was not correctly calculated, due to which an incorrect discount was calculated. This has been fixed. |
| 36477707 |
Memory leaks were detected in dm_oracle. This has been fixed. |
Customer-Reported Fixes in ECE 15.0.1
Table 3-2 lists the customer-reported issues that were resolved in ECE 15.0.1.
Table 3-2 Customer-Reported Fixes for ECE 15.0.1
| Bug Number | Description |
|---|---|
| 36475576 |
The login ID information was populated twice in the ECE customer cache, leading to a discrepancy in reservations. This has been fixed. |
| 36383434 |
In an active-active deployment of ECE, if site 1 had issues causing the SMF to route the request to site 2, HTTP Gateway instances on both site 1 and site 2 had a delayed response. This caused SMF to terminate the session without a proper error response. This has been fixed. |
| 36531368 |
In an active-active deployment of ECE, the query execution was failing due to an ambiguous column error. This has been fixed. |
| 35932874 |
When multiple custom notifications were generated for the same charging request, the latest notification was overwriting the previous one. This has been fixed. |
| 36531355 |
The customerLoader utility was not working with the RAC database on a cloud native deployment. This has been fixed. |
| 36531265 |
Kafka JMX metrics were not integrated with ECE metrics. This has been fixed. |
| 36444027 |
ECE was not exposing the balance element name and description in the balance element cache to be used for post-rating and post-charging extensions. This has been fixed. |
| 36100003 |
During the rating flow involving a discount sharing group for a nested child in the hierarchy, the balances were not getting impacted correctly. This has been fixed. |
| 36420095 |
In an ECE active-active deployment, if one site went down, the state cache was federated, marking the other site's state as INITIAL, causing an outage in both sites. This has been fixed. |
| 35655619 |
The validity time was incorrectly sent as zero with CCR-U being received exactly at the TTC time point. This has been fixed. |
|
36226848 35886498 |
ECE was not generating a Final Unit Indicator (FUI), despite all allowances being consumed. This has been fixed. |
| 36184594 |
If tax configurations were not done correctly in ECE, a NULL pointer exception was sent. This has been fixed. A detailed error message is shown. |
| 35024526 |
With beat configuration in force for data usage, the GSU calculation was incorrect when the allowances were closer to depletion. This has been fixed. |
| 35908570 |
With beat configuration in force for data usage, the quantity considered for rating was different from the unit credit offer purchased for the subscriber. This has been fixed. |
| 29623177 |
When a discount sharing group was configured for roaming usage, ECE was not impacting the correct balances. This has been fixed. |
| 36173763 |
Rated events from ECE were occasionally lost from the Rated Event Manager when aggregation of rating periods was done as an extension. This has been fixed. |
| 36222061 |
In some cases, when a change bundle was triggered in BRM, incorrect offers were picked in the charging flow when processing the usage requests. This has been fixed. |
| 35102930 |
With the beat rounding configured, the RUM and attribute names were not matching because the GSU was calculated incorrectly. This has been fixed. |
| 33050423 |
When a log level was updated from JConsole, the ECS log was showing an error. This has been fixed. |
| 30850916 |
When doing a rolling upgrade of the Diameter Gateway, some nodes were not restarted successfully. This has been fixed. |
| 35839527 |
For the FUI redirect scenario, the validity time in the CCA was incorrect. This has been fixed. |
|
29415790 29520574 |
When percentage-based discounts were configured, the discounting calculations were incorrect. This has been fixed. |
| 36118855 |
With TTC configured, it was not evaluated correctly during the charging flow in some cases, leading to positive balances. This has been fixed. |
| 36032774 |
For CCRs with USUs less than the last GSU, the reservation done in ECE was incorrect. This has been fixed. |
| 36357760 |
ECE components were not writing the ERROR log to STDOUT/Console after enabling the subscriber tracing feature. This has been fixed. |
Customer-Reported Fixes in PDC 15.0.1
Table 3-3 lists the customer-reported issues that were resolved in PDC 15.0.1.
Table 3-3 Customer-Reported Fixes for PDC 15.0.1
| Bug Number | Description |
|---|---|
| 36178051 |
When searching for pricing objects in the PDC UI, an issue occurred when viewing columns in the search results. This has been fixed by removing the binding and visible properties from the search results columns. |
| 36200892 |
The PDC UI was not allowing the user to create multiple Discount Rules that would use the same Discount Trigger. This has been fixed by clearing the UI cache to allow different Discount Rules to use the same Discount Trigger. |
| 36236648 |
When creating a Discount Filter, if the GLID was set and then unset and the pricing name was set, an empty <glid></glid> tag was added in the export XML file, causing a null pointer exception in ECE. This has been fixed by adding NULL checks to ensure that the empty <glid></glid> tag is not NULL and its length is greater than 0. |
| 36289593 |
When migrating pricing data to PDC, multiple NULL pointer errors were reported. This has been fixed. |
| 36183071 |
Migration issues were reported for Batch Rating Engine wholesale configurations. This has been fixed. |
| 36340782 |
When creating a charge offer with a tax exemption selector that doesn't have a service associated with it, a Null Pointer Exception was reported from the PDC UI. This has been fixed. |
Customer-Reported Fixes in Business Operations Center 15.0.1
No customer-reported issues were resolved in Business Operations Center 15.0.1.
Customer-Reported Fixes in Billing Care 15.0.1
Table 3-4 lists the customer-reported issues that were resolved in Billing Care 15.0.1.
Table 3-4 Customer-Reported Fixes in Billing Care 15.0.1
| Bug Number | Description |
|---|---|
| 36493186 |
Memory leaks were detected during the Get Bill Unit Summary for an Account API call. This has been fixed. |
| 36486781 |
After the deployment of a patch, the due amount was not being displayed properly in the Billing Care Switch Bills area. Additionally, when Bill Now was run for the first time, the bill did not contain the due amount. However, the bills generated after you ran Bill Now did contain the due amount. This has been fixed. |
| 36441031 |
A parent account's past due of its intermediate bills displayed only its own due and did not include its children's due. This has been fixed. |
| 36289159 |
In the Billing Care AR actions settlement dialog box, the note's comments link would get overshadowed by the OK and Cancel buttons, preventing the addition of further notes. This has been fixed. A vertical scroll bar has been added to the comment link to enable the addition of more notes. |
| 36169195 |
The quantity field of the purchase API did not take decimal values. Due to this, the user was unable to purchase a partial quantity. This has been fixed. |
| 36118752 |
The Billing Care REST API was failing to retrieve the asset details for services with newly added BRM fields with field numbers greater than 1,000,000. This has been fixed. |
| 35964173 |
Event details in Billing Care UI did not appear properly upon clicking Show More. This has been fixed. |
| 35953767 |
The correct event dispute settled date was not visible. This has been fixed. |
| 36275014 |
Billing Care was storing the billingcare pod's IP address instead of the actual CSR machine's IP address in the PIN_FLD_NAP_IP_ADDRESS field of the /user_activity object. This has been fixed. Billing Care now uses the X-Forwarded-For header value for the actual CSR machine's IP address. In addition, you can use the Billing Care SDK to customize the behavior for setting values in the /user_activity object. See "Tracking CSR Activity for Audit Purposes" for more information. |
| 35937051 |
The PROGRAM_NAME field was not being sent to the BRM server from Billing Care. This has been fixed. The program name has now been set to BillingCare when accessed via Billing Care. The program name has been set to BillingCareREST when accessed via REST APIs. |
Customer-Reported Fixes in BRM Thick Clients 15.0.1
Table 3-5 lists the customer-reported issues that were resolved in the 15.0.1 release of the BRM thick clients.
Table 3-5 Customer-Reported Fixes in BRM Thick Clients 15.0.1
| Bug Number | Description |
|---|---|
| 36343237 |
The user was unable to change the currency symbol in Payment Center. This has been fixed. |
| 36293588 |
When events were sorted in Event Browser in Customer Center, if the user would navigate to the marked events screen and then to the event browser screen, the table would no longer be sorted as it was previously. This has been fixed. |
| 36118751 |
In Customer Center, during the account creation flow, the cycle start relative flag in the product's plans tab screen was not active. This has been fixed. |