3 Summary of Customer-Reported Fixes

Learn about the customer-reported bug fixes included in Oracle Communications Billing and Revenue Management (BRM).

Topics in this document:

Customer-Reported Fixes in BRM

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications Billing and Revenue Management (BRM):

Customer-Reported Fixes in BRM 15.1

Table 3-1 lists the customer-reported issues that were resolved in BRM 15.1.

Table 3-1 Customer-Reported Fixes for BRM 15.1

Bug Number Description
36616116

A discrepancy existed between the 'item_total' value in the 'item_t' table and the 'amount' value in the 'event_bal_impacts_t' table for certain events.

This has been fixed. The REFPlugin now updates the 'rel_sub_process_t' status to UPDATE_ERROR for the session where the update error occurred.
36907043

When load cleanup failed in REM, but session deletion succeeded, partially loaded data could not be cleaned up.

This has been fixed. Now, session data is deleted only after load cleanup completes successfully.
37315280

In the default implementation, Rated Event Formatter (REF) is configured with the same value for data and done directories, so an error is seen when the control file directory is not the same as the data file directory in ECE's REF configuration.

The has been fixed. REF plugin has now been modified to use different data, done and header directories.

36606358

Row lock contention on the 'event_bal_impacts_t' table occurred when processing a large number of events for a small number of accounts.

To resolve this, a new parameter, update_by_balgrp, was added to the REL Infranet.properties and REM Infranet.properties files. This parameter enables each updater thread to process data for a set of balance groups (nearly mutually exclusive, depending on the number of threads), thereby reducing contention.

36801678

The PIN_FLD_OFFERING_OBJ field was missing from the purchase discount and purchase product arrays in the response to a WebService request for pcmOpSubscriptionGetPurchasedOfferings.

This has been fixed.
37106470

Wrong comment is found in the cm_cache.h file.

This has been fixed.
36982701 update_data_sequence was returning the same sequence twice. This has been fixed. The stored procedure is updated to retrieve unique header numbers using appropriate transaction control.
37129887 The PIN_SEQUENCE package was enhanced to support encoding of POIDs based on local timezones and DST calculations via geographical timezones.
37023412 There was an issue about discount cycle validity flags information in docs. The docs are now updated with the correct information.
36694622

In previous releases, discount was not getting overridden with price_tags for billing time discount event.

This has been fixed.
36668921

Discounts were not being overridden with price_tags for purchase fee events due to incorrect start/end dates used for filtering tags.

This has been fixed. Correct START/END dates are now used for purchase events.
36846461 Few of the opcodes were missing in the WebServicesManager config role. This has been fixed.
36830570

When an offer is configured as enforceCreditLimit set to OUTSTANDING_AMOUNT is purchased, it is failing.

This has been fixed.
36825390 MTA framework is enhanced to incorporate use of complex search queries involving EXTRA_RESULTS and LINKED_OBJ fields.
37058432

The /offering_override_values buffer contained invalid values for migrated accounts.

This issue has been fixed. A NULL character is now added to the end of the buffer to align the results.
36496077

When an offer with a future-dated cancellation was processed using pin_cycle_fee -defer_cancel, the overridden offer was incorrectly selected for cancellation, resulting in charges not being generated.

This has been fixed.
36524503 pin_cycle_fees utility was not splitting events for multi-month previous cycle charges, instead it created a long cycle event for multiple previous months. The utility is fixed to split the events for each month and assign these events to appropriate bills.
36601478

Previously, in skip billing scenarios, config_billing_delay was set without errors when billing was first run for the parent account.

This has been fixed. The utility now throws an error when parent billing is run first.
36916957

In wholesale billing scenarios in certain cases balances are not rolled up to the parent.

This has been fixed.

36963929 The item's MOD_T is not getting updated in case of undefined payment types billing. The issue is fixed to correctly modify MOD_T value with updates in items values.
36568144 The /offering_override_value storable class was not getting populated post migration due to PERCENT getting appended in the dat file. Fix was provided to not append PERCENT if not passed in the input XML.
37168980

Previously, /offering_override_value was not getting created when a service was being transferred across accounts.

This has been fixed.
36658766

In previous releases, when pin_update_balances utility was run from the pje pod, it was throwing an error.

This has been fixed.
37117470

PCM_OP_SUBSCRIPTION_POL_CRUD_OFFER_OVERRIDE flag could not be overridden because of the missing override flag entry.

This has been fixed.
37084589

The RATE_ECE_EVENT was sending granted sub-balances for the same resource with identical data in a single event. BRM merges these sub-balances when the data matches. However, the granted_bal was not aggregated during the merge.

This has been fixed.
37018577

The PIN_FLD_COUNT field was missing in the output flist of the PCM_OP_COLLECTIONS_GET_AGENT_ACTIONS opcode.

This has been fixed.
36868376 A new policy opcode is added to modify the response of the PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode.
36633403

Incorrect tax was calculated for event adjustment.

This has been fixed.
37158826

CMT was sometimes not able to convert timestamp into UNIX epoch format due to which loading was failing.

This has been fixed.
36514273

Granted and current balance mismatch during balance transfer from user balance to sharer balance.

This has been fixed.
36608425

After rerating on cancelled product, granted_bal was not having correct value.

This has been fixed.
36648809

Memory corruption during cache creation was detected.

This has been fixed.
36664759

There was an issue detected while loading tax codes.

This has been fixed.

37079678 Invalid FLIST pointer encountered as Bad flist ptr in event-level adjustment . The "Bad flist ptr" error in event-level adjustment has been fixed by implementing pointer validation and improving error handling.
36999465

The PCM_OP_AR_GET_BILL_ITEMS opcode failed when the Service ID was included in the input.

This has been fixed. The search functionality has been optimized to handle cases with more than 32 service objects, now correctly returning all items that match the specified Service ID.
37273396

When the Bill Now operation was executed, tax calculation occurred at the parent account level, and the cycle_tax interval was ignored. To resolve this issue, changes were implemented to calculate tax at the subordinate account level.
37196387

Pending Recv was turning negative when charge was given back to an account.

This has been fixed.
36535839 Payment was getting reversed when effective date was before the account creation date. Payment reversal is fixed to throw an appropriate error.
36548780 Tax calculation was wrong when wholesale billing was enabled. This has been fixed. Tax calculation is corrected during prebill dispute and settled post billing for a subordinate account at event level.
36573111

pin_cycle_fees was throwing on ORA-0100 error.

This has been fixed.
36684361

CMT sometimes was not able to convert Extension Date Field to Unix Timest.

This has been fixed.
36553365

Multiple ordered balance group were not getting created in case of account-level group sharing discount during migration.

This has been fixed.
37417558 dm_oracle was not able to enqueue messages greater than 4000 bytes as read-only transaction was opened from the publish FM. Publish FM has been fixed to send read write transaction to dm_oracle if no external transaction is present.
36815638 Failure in suspense preprocessing. To fix the issue, supported special character parsing as part of suspense preprocess script.
37344933 Long running sessions on rel_event_extract_sync while REL loading because the process was holding lock for longer time doing backup of interim files (due to NFS mount point having huge number of files). To fix the issue, changes were done in pin_rel_handle_interim_files.pl (which does backup of interim files) to fetch the file from header file for ECE rated CDR.
36916956

While publishing an offer, all the rate plans in the product are added for each event, which results in unrelated rate plans are being included under usage maps.

This has been fixed.
37014868 BTDs valid for mid-cycle were not being applied for discounting due to validity checks on the secondary billinfo. The fix now ensures these BTDs are correctly applied, even for secondary billinfo.
37355584

The pin_state_change utility was processing services with lifecycle states lacking transitions, resulting in longer completion times. The code has been modified to set the expiration_t of these services to 0 and adjust the MTA search criteria to exclude services with expiration_t set to 0.

36543957

The EFFECTIVE_T and INSTANTIATED_T fields were not being published under ProductPurchaseEvent, causing product rating validation failures in ECE during bundle changes. The fix now publishes these fields.
36524496 Balance synchronization during in-advance cycle events led to incorrect balances. To resolve this, balance synchronization between BRM and ECE was skipped during these events.

Customer-Reported Fixes in BRM 15.0.1

Table 3-2 lists the customer-reported issues that were resolved in BRM 15.0.1.

Table 3-2 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 decimals 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

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications Elastic Charging Engine (ECE):

Customer-Reported Fixes in ECE 15.1

Table 3-3 lists the customer-reported issues that were resolved in ECE 15.1.

Table 3-3 Customer-Reported Fixes for ECE 15.1

Bug Number Description
37458266

In previous releases, tax calculation was found to be incorrect in some cases.

This has been fixed.
36902533

In previous releases, with non-linear rating disabled the overages were incorrectly calculated.

This has been fixed.
37592478

In previous releases, subscriber login information was missing for some users in the Public User identity (PUI) cache. Due to this, the accounts were not properly synchronized between BRM and ECE.

This has been fixed.

37222930 In previous releases, subscriber preferences information was not exposed in HTTP Gateway PreOCS extension. With this release, to enable customization requiring this information, a new method getSubscriberPreferences(), is exposed under interface HTTPPreOCSExtensionContext.
37377275

In previous releases, the item type was incorrectly evaluated for some tax events.

This has been fixed.
37422815 In previous releases, ECE was not processing CancelFeeEvent received from BRM, causing a mismatch. This has been fixed. A new configuration for CancelFeeEvent is added in the payloadconfig_ece_sync.xml and pin_notify files.
36797014

In previous releases, with prepaid life cycle management configured, it was observed that even after depleting prepaid balances the account life cycle was remaining as "Active".

This has been fixed.
36887034

In previous releases, there was an issue inserting rated events into the cache due to the size considerations.

This has been fixed.

36982850

In previous releases, for midsession CDR flow and also initiate CCR flow, during the consumed units rating SNR was not generated even if there was a balance impact or breach.

This has been fixed.
37009196

In previous releases, it was not possible to disable Diameter Gateway log messages even after setting appropriate log levels.

This has been fixed.

37201299

In previous releases, there was an issue for a Diameter Gateway to connect with an alternative peer.

This has been fixed.

37196553

In previous releases, in some cases Diameter Gateway Sy timeout errors were observed.

This has been fixed.
37453520

In previous releases, for a cloud native deployment of ECE, if Diameter mediation specification was updated, a restart of Diameter Gateway was needed.

This has been fixed.

37486214

In previous releases, while passing unsupported auth-application-Id (4321) in CER, the request was getting timeout at Network as Diameter Gateway was neither logging nor sending a 5010 error. This has been fixed. Also a new return code of PROTOCOL_FAILURE has been added if an unsupported auth-application-Id is passed.
37531168 In previous releases, for period-based rating, the session end time was considered as event time and this was resulting in incorrect balance impacts. This has been fixed. For non linear rating, event time has been updated to be the session start time, so that the product and balance available at the session start will be considered for rating.
37486215 In previous releases, QoS information AVP was included in CCA response which is incorrect as per 3GPP standard. This has been fixed. QoS Information AVP is dropped from the CCA response, but it is made available in the extension hooks for any customizations.
37486217

In previous releases, Diameter Gateway was incorrectly converting IMEISV information into ASCII text format during usage processing.

This has been fixed.
37196552 In previous releases, BRM Gateway was doing a retry for an unqualified error code from BRM. This has been fixed. Now BRM Gateway will not retry or send the event to suspense if BRM returns an error code that is not qualified for further processing.
37506173

In previous releases, EM Gateway was observed to have transaction lock issues contributing to higher latencies.

This has been fixed.
37569779

In previous releases, BRM Gateway was not using the correct connection pool values, resulting in degraded performance.

This has been fixed.
36674050

In previous releases, EM Gateway was observed to have transaction lock issues contributing to higher latencies.

This has been fixed.
37491496

In previous releases, the TMP files were not removed after the formatting was completed by Rated Event Formatter.

This has been fixed.
37443639

In previous releases, if an account was closed, then any late CDR for that account was not successfully rated, after ECE restart.

This has been fixed.
37486218

The customer data loading from BRM into ECE was taking more time than the previous releases.

This has been fixed.
37248470

In previous releases, it was observed that the SUBSCRIPTION_CYCLE_FORWARD notification event was getting generated even if subscriptionCycleForwardMode was set to NONE in the ECE application configuration.

This has been fixed.
37016384

In previous releases, during customer account provisioning flow if the cache persistence database connectivity was down, ECE was returning en error. Fetching the recurring bundle information when the database was not accessible was also causing an error.

This has been fixed. Now, even when the database is down, ECE will not try to write or fetch any information from the database, and hence will not return an error. These operations will wait until the database is back up and running.
37583719

In previous releases, there was an issue when inserting objects into Aggregate Object Usage cache, causing an exception.

This has been fixed.
36648960

In previous releases, with some charge offer configurations with multiple tiers, ECE was not moving to the next available tier when the previous tier resource was completely consumed, incorrectly generating an FUI.

This has been fixed.
37212324

In previous releases, rounding inconsistencies were observed when you charge and discount the same amount, resulting in an impact which was not expected.

This has been fixed.
37201735

In previous releases, while rating with a charge offer that includes multiple tiers, even though a valid offer with resource (like PAYGO) was available, incorrectly FUI was being triggered.

This has been fixed.
37377276

In previous releases, ECE was incorrectly evaluating value maps in a charge selector.

This has been fixed.
37543960

In previous releases, SYSTEM_ERROR was being thrown by Diameter Gateway while processing usage requests.

This has been fixed.
37519961

In previous releases, during rating flow for a session that includes an MSCC with multiple rating groups, if there was a CREDIT_CEILING_BREACH/NO_RATED_QUANTITY for one rating group the failure response was terminating the complete session.

This has been fixed.
37502574

In previous releases, when processing a mid-session CDR trigger during billing activities, Diameter Gateway was responding with the error DIAMETER_UNABLE_TO_COMPLY (5012).

This has been fixed.
37496441

In previous releases, when rateZeroQuantity was enabled, the rating for requested service units (RSU) was incorrect.

This has been fixed.
36825557

In previous releases, when doing a rolling upgrade of ECE with the continued processing of usage requests, ECE was throwing some exceptions.

This has been fixed.
37033252

In previous releases, while creating and dropping of rated event partitions in the ECE database, it was impacting the system performance.

This has been fixed.
37079871

In previous releases, SYSTEM_ERROR was being thrown by Diameter Gateway while processing usage requests.

This has been fixed.
37374826

In previous releases, for some rated events, the impact category was missing during the rerating process.

This has been fixed.
36648958

In previous releases, the ECE persistence job was failing whenever there existed an uncommitted transaction in the CDR Store table.

This has been fixed.
36528779

In previous releases, with duplicate detection enabled through terminatedSessionHistoryCacheEnabled, ECE was rejecting unique session id requests that were not actually duplicate.

This has been fixed.
36839216

In previous releases, Sy STR on old session was getting success response after overridden with new SLR request.

This has been fixed.
37232222

In previous releases, SNRs were only logged but were not published to JMS. There was no issue publishing to Kafka.

This has been fixed.
37443638

In previous releases, Diameter Gateway timeout for SNR/SNA was hardcoded to 10 seconds.

This has been fixed.

Now, it is a configurable option and can be set to milliseconds. This is to avoid long wait time for SNA for each thread and disconnection of diameter peer.
36700237 In previous releases, the failureHandling was not returned in 5G chargingDataResponse. This has been fixed. Now it is returned as per specifications with a default value RETRY_AND_TERMINATE in case of a failure.
37201732 In previous releases, chargingDataResponse was not customizable when byPassOcs had been enabled.

This has been fixed.
37018779

In previous releases, rolling upgrade was failing.

This has been fixed.
36710009

In previous releases, failure occurred when NRF nfProfileJsonRequestPayload was used in the ECE cloud native setup.

This has been fixed. Now you can now define the complete NRF JSON payload in charging-settings.yaml or in any mounted directory accessible from the pod, and provide the path accordingly.

36784694 36897225

In previous releases, traffic was rejected after double transitions between prepaid and postpaid types for the same MSISDN.

This has been fixed. Now the MSISDN is reusable after type and state transitions.
36951437

In previous releases, there was an error in EM gateway logs during ECE_POST_COMMIT operation after a customer was deleted in BRM.

This has been fixed.

37315428

In previous releases, there was no option to suppress generation of threshold breach notifications for update operation types.

This has been fixed.
37212326

In previous releases, billing was failing with credit limit exceeded error in ECE during the update flow.

This has been fixed.
37407715 In previous releases, CHF charging response took the workernode IP. This has been fixed. Now it will configure according to the presence or absence of cluster specific configuration.
37349372 In previous releases, the content type of the header was incorrect. This has been fixed. Now the right content type will be added in the request.
37467607 In previous releases, there was service barring value mismatch between the BRM database and ECE cache. This has been fixed. Now warning message has been added to identify such issues.
37507908

In previous releases, for an active-active deployment with federation across the sites enabled, incorrect sequencing of updates was causing overwriting of balance information.

This has been fixed by checking the version of the cached object and the federated object for a decision to update.
36596518

In previous releases, account and service termination had been failing while publishing to ECE when terminated first time and was successful on second attempt.

This has been fixed.
36825556 In previous releases, Sy AVP 278 Origin-State-ID was missing. This has been added.
36887032

In previous releases, after restarting of ECE, expiration time details were incorrect in audit product.

This has been fixed.
37491494

In previous releases, junk characters were loaded in ECE for special characters from the pricing XML.

This has been fixed. Now support for special characters is enabled.
36905213

In previous releases, the CreateJmsNotificationQueue script failed during target server validation.

This has been fixed.
37212322

In previous releases, both THRESHOLD_BREACH_EVENT and AGGREGATED_THRESHOLD_BREACH_EVENT notifications were getting generated, which was unnecessary.

This has been fixed. Now, ECE have flexibility to chooses only either of the one.
37484058

In previous releases, service context cache was growing too much and also notifications were not evenly distributed in Apache Kafka.

This has been fixed. Now, Coherence getALL call has been enhanced to keep service contact cache optimized.
37196093 In previous releases, NoSQL support was not there for cleanup of orphan CDRs. This has been added. Now NoSQL support is enabled for orphan CDR cleanup.
36608442

In previous releases, when you configured a price plan with beats and quantity ranges, during usage processing there was an issue with beat creation resulting in incorrect ranges.

This has been fixed.
36882605

In previous releases, when processing usage, a new item was getting created at the service level instead of using the existing item at the account level.

This has been fixed. Now, if the item already exists at the account level, it is used for processing the usage.
37523393

In previous release, ECE was throwing an exception in TTC worst cost rating flow.

This has been fixed.
37519453 In previous releases, in some cases rated events were not loaded into the BRM database. This has been fixed. Additional logging has been added to capture the cases when the payload lacks details leading to loading failures.
36535856

In previous releases, threshold breach was not being generated in the consumed rating for time-based resources.

This has been fixed.
37278722

In previous releases, it was observed that the prepaid subscriber status was changing to RECHARGE_ONLY even when balance was available.

This has been fixed.
37217081 In previous releases, cycle forward notification was not triggered during certain scenarios. This has been fixed.
35959781 In previous releases, 5G usage was failing due to missing fields in the ece-persistence.yaml file. This has been fixed. Now ECE Persistence playlist has been updated to add all required fields after an upgrade.
36535857

In previous release, custom selectors were not getting initialized in ECE, causing exceptions during the process.

This has been fixed.
37185151

In previous releases, actual quantity in newly created tax_on_charge rating was null by default. This has been fixed. Now actual quantity has no default static null value.
36954343

In previous releases, subscription ID was not present in Diameter Gateway logs for 5030 errors. This has been fixed.
37458264 In previous releases, for an active-active deployment, it was observed that federation of data across sites was not working correctly. Now measures have been taken to improve the federation with additional checks of the objects being federated. You can now have an option to disable federation through application configuration prior to the replicateAll command.
36002219

In previous releases, PDP-Address AVP was added as part of the PS_Information AVP for the CCA responses, which is not required as per 3GPP standards.

This has been fixed. Now this AVP has been removed from CCA as per 3GPP specs.
37594714

In previous releases, ECE was throwing an error when loading Kafka SSL configurations from the Helm chart.

This has been fixed.
37489273

In previous releases, when ECE was deployed in a cloud native environment in Active-Active mode, cache imbalance error was observed when one of the worker nodes in one of the sites was taken down for upgrade activity.

This has been fixed.
36648957 In previous releases, it was observed that incorrect logs were overloading production deployments. This has been fixed. Now ERROR/WARN log messages are moved to INFO log level, so as not to overload the log files.
37490875

In previous releases, the ./query.sh -P option was not working properly.

This has been fixed.
36716164 In previous releases, rating logic considered the end time of CDR instead of start time. This has been fixed. Now you can select start or end time for balance impact based on offer eligibility selection mode.
36902532

In previous releases, non currency and currency impacts were not commited to the BRM database during certain scenarios.

This has been fixed.
37028366

In previous releases, when saveNonCounterGrantDuringOngoingSession was enabled, the balances were not updated properly during certain charging scenarios.

This has been fixed. Now accumulator flag has been included which commits the balance only after terminate requests.
37443151

In previous releases, even if there existed a renewable balance from which you could consume from, FUI was triggered after base free units were consumed. This has been fixed.
36611222

In previous releases, during a session the consumed reservation information in the active session object was not updated correctly in some scenarios.

This has been fixed.
36486976

In previous releases, when a change bundle event was sent from BRM to ECE during an ongoing session, the balance consumption recorded was incorrect.

This has been fixed.
36610823

In previous releases, during an ongoing session, even after all available allowances were exhausted, an FUI was not sent to the network.

This has been fixed.
36611240

In previous releases, there was an issue during the cache object serialization causing an exception.

This has been fixed.
36745230

In previous releases, there were logs generated for Warning messages for missing optional attributes at product and account level.

This has been fixed. Now these messages are moved to INFO level.
36682958

In previous releases, it was observed that duplicate CDRs were being loaded into BRM from ECE.

This has been fixed. Now Rated Event Formatter has been enhanced to resolve this issue.
37142914

In previous releases, GSU was not granted correctly for certain scenarios.

This has been fixed.
37174434

In previous releases, threshold breach notifications were being triggered when update was received just before the end of balance expiry.

This has been fixed.

37490545

In previous releases, there was issue in Kafka event publishing due to some null values in the customerId and productId fields.

This has been fixed.
36579806

In previous releases, in some cases, SNR and Threshold Breach Notification were not getting generated even when the required conditions were met.

This has been fixed.
36511071

In previous releases, advice of charge (AoC) notification was sent only with terminate requests and was not sent out for mid-session triggers to generate a rated event.

This has been fixed.
35053454

In previous releases, there was an issue when querying the grid for customer data and the Coherence grid was returning an exception.

This has been fixed.
35359172

In previous releases, FUI was not triggered even if the balance was exhausted.

This has been fixed.
36669103

In previous releases, Diameter Gateway was throwing an error for mapping of AVP 2050 PDN-Connection-Charging-ID.

This has been fixed.
37404154

In previous releases, SLR Intermediates and STR were getting timed out intermittently at client side.

This has been fixed.
37404160

In previous releases, there was a mismatch in Sy Request Error code metrics for RC 5002.

This has been fixed.
37355718 In previous releases, there was no metric to capture latency of CCR-I in ECE. This has been fixed. Now new metrics type added in Diameter Gateway to capture this CCR-I latency.
37404157

In previous releases, Sy session cleanup activity caused overload in ECE.

This has been fixed.

36165017 In previous releases, both current and original balances were updated. This has been fixed. Now only the current balance is updated with the impact amount, and the original balance will not be updated.
36825553 In previous releases, as the renewal was getting triggered before base free units were consumed causing rating errors. Now a custom map has been exposed in active session to assist customization in this workflow.
36581955

In previous releases, there was an error in Rated Event Formatter when non counter grant was impacted.

This has been fixed.

36648956

In previous releases, ECE rating performance was impacted during CDR event processing.

This has been fixed. Now performance has been improved for specific scenario where overload issue was found.
36750015

In previous releases, originalBalance in ECE cache was returned incorrectly for overage grant.

This has been fixed.

37638135

In previous releases, during a MSCC request processing if there was an exception in one request, it was propagated to other requests failing the entire MSCC request.

This has been fixed. Now if there is exception while processing just one of the requests, then the other requests will be processed as expected.
36531339

In previous releases, for period-based rating session end time was considered as event time and this was resulting in incorrect balance impacts.

This has been fixed.
36616270

In previous releases, in SNR scenarios for the same sharing agreement, ECE was producing two SNRs in place of one - one with correct puid and the other without puid.

This has been fixed.

Customer-Reported Fixes in ECE 15.0.1

Table 3-4 lists the customer-reported issues that were resolved in ECE 15.0.1.

Table 3-4 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

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications Pricing Design Center (PDC):

Customer-Reported Fixes in PDC 15.1

Table 3-5 lists the customer-reported issues that were resolved in PDC 15.1.

Table 3-5 Customer-Reported Fixes for PDC 15.1

Bug Number Description
36500070 An issue with balance elements precision, when changed precision rounding is not happening properly in BRM. Issue is fixed to send correct precision values for certain objects in PDC transformation.
36352255 An error is thrown while updating the transaction_type in VERTEX_QUANTUM type to 0. An enhancement is done to PDC to support zero configuration for CODE1 and CODE2 fields
36507086

In PDC UI not able to add more than 1000 packages to package list.

This has been fixed.
36586780

PDC UI throws ADF exception error while creating a new rule for USC Selector.

This has been fixed.
37431227

PDC UI throws an error when browser language is set to English and create a new offer, while adding tax information in the charge details section.

This has been fixed.

Customer-Reported Fixes in PDC 15.0.1

Table 3-6 lists the customer-reported issues that were resolved in PDC 15.0.1.

Table 3-6 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 Billing Care

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications Billing Care:

Customer-Reported Fixes in Billing Care 15.1

Table 3-7 lists the customer-reported issues that were resolved in Billing Care 15.1.

Table 3-7 Customer-Reported Fixes for Billing Care 15.1.

Bug Number Description
37586445

Allocate Payments table doesn't show any data when navigated from unallocated payments of an account.

This has been fixed.
37569365 An enhancement is made to Billing Care to allow searching accounts based on Service ID when a service has multiple aliases for a service.
37572544

While opening AR action details from Newsfeed, Billing Care was throwing console error " dateConverter is not defined".

This has been fixed.

37473243

Wrong expiry date is displaying for manual discounts in asset section. Timezone offset JSON which is coming from REST is not sorted.

This has been fixed.

36853154 There was an issue when custom messages are added in newsfeed reason codes file were not appearing in the newsfeed table on UI for any AR actions. This issue is fixed now. Now any additional/custom strings added in PIN_FLD_MESSAGE will appear in the Newsfeed table as expected.
37387552

In Billing Care Application when we click on non currency resources the pop-up is not displaying properly , the pop-up size is very big when as compare to BRM12 and the arrow is also not pointing to the non currency resource block.

This has been fixed.

37411978

Settlement of Grant full and deny of disputes is not working as the amount field is missing while invoking the fm_ar_event_settlement input flist.

This has been fixed.

37294560 Improper Display of Error Message While Performing Refund through Billing Care is resolved.
37206352

NewsFeed Recurring Charge Link is redirecting to Account Charges instead of Subscription.

This has been fixed.
37232898 Billing Care Error in 'Records in Batch' when clicking the 'Validate' button. When a custom reversal was being made using Billing Care, in some cases conditional logic was searching for payment in /event/billing/charge table instead of /event/billing/payment. I have modified the conditional logic for custom payments to search for payment in correct table
37146842

While performing Event Adjustment % symbol was not being displayed.

This has been fixed.
36724768 Unable to process refund when specified using ITEMS[] instead of ITEM_OBJ. This issue is fixed now. Billing Care will first check ITEM_OBJ for individual refunds. If ITEM_OBJ is null, it will process refunds using ITEMS[].
32772351 Enhancement is made to display/search of alias_list values other than 0th index.
36757363 Scroll bar is missing on Payment Details screen in Billing care 15. Scroll bars have been added to the Payment Details and Make Payment dialogs to ensure that the footer sections and buttons remain visible to the user.
36732558 When trying to change Prepaid Lifecycle State from ACTIVE to RECHARGEONLY through BillingCare, getting the following error and the action freezes: "Cannot deserialize value of type `int` from String "ui-id-15": not a valid `int` value".

This has been fixed.

36337328

Event view is getting distorted & "Show More" button is not visible.

This has been fixed.
36541425 Comments/notes from billing care batch payment file not appear in detail page . comments from the batch file will be stored in "/event/billing/payment/PAYMENT_METHOD" in the "PIN_FLD_DESCR" field of the respective payment.
36549679 When the "Add Filters" button was being clicked for "Collections", the resulting filter dialogue box was overflowing for some resolutions resulting in the above issue. This issue is fixed now. Modified the filter dialogue box's position and size and added a scroll bar to prevent this issue from recurring.

Customer-Reported Fixes in Billing Care 15.0.1

Table 3-8 lists the customer-reported issues that were resolved in Billing Care 15.0.1.

Table 3-8 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 Business Operations Center

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications Business Operations Center:

Customer-Reported Fixes in Business Operations Center 15.1

Table 3-9 lists the customer-reported issues that were resolved in Business Operations Center 15.1.

Table 3-9 Customer-Reported Fixes for Business Operations Center 15.1

Bug Number Description
XXXX

XXXX

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 BRM Thick Clients

See the following for a list of customer-reported issues that were fixed for each release of Oracle Communications BRM thick clients:

Customer-Reported Fixes in BRM Thick Clients 15.1

Table 3-10 lists the customer-reported issues that were resolved in the 15.1 release of the BRM thick clients.

Table 3-10 Customer-Reported Fixes in BRM Thick Clients 15.1

Bug Number Description
36971995

Update Number Category is not working in Number Administrator Tool.

This has been fixed.

Customer-Reported Fixes in BRM Thick Clients 15.0.1

Table 3-11 lists the customer-reported issues that were resolved in the 15.0.1 release of the BRM thick clients.

Table 3-11 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.