9 Fixed Issues in This Release

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

Topics in this document:

• Fixed Issues in BRM

• Fixed Issues in ECE

• Fixed Issues in PDC

• Fixed Issues in Billing Care

• Fixed Issues in Business Operations Center

• Fixed Issues in BRM Thick Clients

Fixed Issues in BRM

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

• Fixed Issues in BRM 15.2
• Fixed Issues in BRM 15.1
• Fixed Issues in BRM 15.0.1

Fixed Issues in BRM 15.2

Table 9-1 lists the customer-reported issues that were resolved in BRM 15.2.

Table 9-1 Fixed Issues in BRM 15.2

Bug Number	Description
37972350	Authentication failures occurred when session/notify events were active and the login POID was NULL, which was required in the header; validation now ensured the login POID was present before authenticating during session/notify events. This has been fixed.
37815166	If a caller issued a commit after a transaction failure, the BRM eai_js utility waited indefinitely for an end or abort event, impacting other transactions in the same session to sync with ECE. This has been fixed.
38067868	Cyrillic characters were loaded into BRM as garbled values by REM; the loader now explicitly set UTF-8 during BRM database loading to ensure correct character storage. This has been fixed.
37786703	Creating a backdated Ordered Balance Group triggered billing unexpectedly. This has been fixed.
38473359	When an offer was purchased with future-dated validity, grants were unavailable until pin_cycle_fees was run, causing delays and potential service disruption; support for early grants was added to pin_cycle_fees. This has been fixed.
38267665	Overriding price using a price tag for backdated purchases by passing end_t did not work as expected. This has been fixed.
38284666	pin_cycle_fees with the -file option did not correctly pick up services from the file. This has been fixed.
38341647	The date range was incorrect for backdated purchase override; a check was added for the event type and the current pin_virtual_time to return the correct date ranges. This has been fixed.
38415518	For performance, invoicing searches were limited to items and events from the last 60 days; when item_t was not partitioned and items were older than 60 days, the filter caused items to be missed. This has been fixed.
38436152	Errors occurred in billing, product purchase, and cancel operations for accounts with cycle arrears offers when granted_bal was NULL. This has been fixed.
38505108	PCM_OP_BILL_DEBIT failed with PIN_FLD_FLAGS not found. This has been fixed.
37878283	The config_billing_delay entry was obsoleted from the CM pin.conf and pin_billd pin.conf files and was supported only via a business parameter. This has been fixed.
37815162	Accounts migrated with pin_cmt -deploy_ece did not sync OfferingOverrideList to ECE even when /purchased_product had PIN_FLD_OFFERING_OVERRIDE_VALUES_OBJ; a new notification event was introduced to address this. This has been fixed.
38499160	A performance issue was observed with dm_kafka asynchronization operations; asynchronization performance was optimized. This has been fixed.
38693594	Stack trace printing was adjusted to prefer the pstack utility; if unavailable, built-in backtrace functions were used instead. This has been fixed.
37674156	Failures occurred when generating a corrective invoice for a parent–child account after reversing all charges via adjustments. This has been fixed.
38666568	When a payment was made backdated, billing was triggered for all previous months unexpectedly. This has been fixed.
38154207	An enhancement was added to support Sequential Discounting for the PriceTag override feature.
38210703	In the discount-only charge refund and reapply flow, the product cycle start time was incorrectly used as the effective time, causing incorrect balance retrieval; the effective time was no longer applied for discount-only charge flows. This has been fixed.
38305897	A discount with Proration set to “Apply to Full Cycle” that was added mid-cycle to a Discount Sharing Group was prorated; logic was adjusted to send the correct cycle dates for shared discounts. This has been fixed.
38598048	Rerating of usage events caused incorrect balances because purchased discounts linked to different balance groups were incorrectly considered duplicates and excluded, leading to incorrect balance retrieval. This has been fixed.
37819989	In wholesale billing, items created between child billing and parent billing were associated with the wrong bills; their status became closed after parent billing and they were subsequently impacted incorrectly by later processes. This has been fixed.
38602748	Discounts purchased during the delayed billing period were incorrectly applied to the next cycle, causing incorrect charges in the current bill. This has been fixed.
38602755	Charges were not prorated when an account was closed after services were inactivated. This has been fixed.
38554064	When an Ordered Balance Group was created and a type-only group sharing discount was not present, it was not added automatically; type-only group sharing discounts were now added during Ordered Balance Group creation. This has been fixed.
38598049	With two offers using MCF, one granting resources with in-advance billing, pin_cycle_fees failed to trigger the noncurrency in-advance bucket on the first run. This has been fixed.
38305895	When pin_multidb was set to 1, pin_cycle_fees did not process secondary schema accounts because the search targeted only the primary database; searches were adjusted to use the incoming database. This has been fixed.
38330647	The utility pin_discount_cleanup -close did not work for Secondary Schema Accounts because purchased discount returned NULL. This has been fixed.
37991083	Creating multiple backdated Discount Sharing Groups triggered billing unexpectedly. This has been fixed.
38436155	An enhancement was added to support price tag override functionality for item-type products. This has been fixed.
38419022	Reusing an MSISDN for a new account upon discount purchase did not work as expected. This has been fixed.
38441525	When Monthly/Daily Cycle Forward offers were configured to track consumption, only a single in-advance bucket was created; a policy opcode (PCM_OP_BILL_POL_SPEC_CYCLE_FEE_INTERVAL) was introduced to support passing the relevant flag. This has been fixed.
38527240	After account reactivation for 30-day MCF, cycle fee end dates were incorrectly updated; updates were skipped when the unit of time was days or weeks to keep the end date consistent after reactivation. This has been fixed.
38515968	Refunds were incorrect when a tailor-made offer was canceled backdated. This has been fixed.
38473366	PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO and PCM_OP_SUBSCRIPTION_SET_PRODINFO were enhanced to allow calling PCM_OP_SUBSCRIPTION_CRUD_OFFER_OVERRIDE with flag=7 to read the /offer_override_values object. This has been fixed.
37839721	MTA framework changes were made to check the count of results for processing to aid custom MTA applications. This has been fixed.
37827297	The item’s MOD_T was not updated for undefined payment types; logic was corrected to update MOD_T when item values changed. This has been fixed.
38079933	pin_cmt performance for migrating customers from a legacy system was improved.
38593020	dm_fusa was enhanced to support Paymentech DN/PDN001 reply records for network-tokenized card transactions and the simulator was updated to send DN records, preventing false failures while maintaining existing authorization behavior.
38463072	A performance issue occurred when running pin_cycle_fees with -regular_cycle_fee due to locking a shared balance group during fee processing; the MTA framework was enhanced to group and process records in a scalable manner. This has been fixed.
37712263	A performance issue was identified when running the pin_event_extract utility. This has been fixed.
37909376	When PIN_FLD_AR_BILLINFO_OBJ was 0 in item_t, the GL report incorrectly populated the next entry’s item_no with the previous item’s POID, causing inaccurate mapping; logic was corrected to populate the right item_no. This has been fixed.
38402805	A REL performance issue was observed in an upgraded setup; queries were tuned to improve performance. This has been fixed.
37960114	API performance degradation and incorrect charging occurred for certain tailor-made products. The implementation was simplified to remove an expensive API call and use a lightweight flag-based approach.
37809648	In certain scenarios, service lifecycle status changes requested through CUST_UPDATE_SERVICES were not applied if a similar change was performed earlier. This has been fixed.
38468243	Multiple login or alias updates in a single transaction failed because changes were only kept in the transaction flist and not written to the database until commit; logic was updated to write changes before committing. This has been fixed.
37742964	Debug messages appeared even when logging was turned off. This has been fixed.
38527234	Starting in 15.0, the default TSTAMP value changed from PVT to 0. Support was added for a configuration parameter to preserve the previous default behavior when required. This has been fixed.
38010689	When a cycle arrears offer was set to charge during inactivation, account inactivation during subsequent billing did not work as expected. This has been fixed.
37878899	Dynamic tax calculation was incorrect when the tax end date and cycle end date were the same. This has been fixed.
38629101	Discount calculation was incorrect due to the wrong ordering of the discount list. This has been fixed.
38205096	While performing an event adjustment, an unexpected failure was reported. This has been fixed.
37943801	Granted balance was incorrect after a bill run for a cycle event because it was not updated in the cache. This has been fixed.
38067864	During backdated deal purchase, cycle charges were not applied. This has been fixed.
38473371	During rerating, itemized tax calculation did not occur, resulting in an incorrect tax amount. This has been fixed.
38489199	When multiple bill units and balance groups were configured, rerating back-out adjustments were applied to the default balance group instead of the service-level balance group, causing balance discrepancies. This has been fixed.
37804335	For non-aligned products with in-advance billing, purchases made after the 28th day of the month caused the billing cycle to split, creating unintended buckets. The behavior was corrected so that the cycle is no longer split for such purchases. This has been fixed.
37798343	Automated Monitor Sharing Group creation failed in a few scenarios. This has been fixed.
37742194	While executing PCM_OP_DEVICE_ASSOCIATE in a multi-schema environment to associate a device in a secondary schema to an account in a secondary schema using a transaction established for the primary schema, the operation failed. This has been fixed.
37798347	Non-currency resources were refunded in full when preponing the product cycle end date. The fix ensured PIN_RATE_FLG_PRO_NORMAL was not set when preponing a product’s cycle end date, provided the cycle end_t was less than charge_to_t. This has been fixed.
37809649	PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO returned an error for sequential discounts. This has been fixed.
37766815	When the ChangeStartTimeOnActivation business parameter was disabled and an inactive product was reactivated, the product was charged from the date of inactivation. It is now charged from the date of activation. This has been fixed.
37679503	A runtime error occurred while executing the PCM_OP_SUBSCRIPTION_ORDERED_BALGRP opcode. This has been fixed.
37702817	For explicit calls to the PCM_OP_SUBSCRIPTION_PURCHASE_FEES opcode, offering override date ranges were not supported. This was enhanced to include offering override date ranges in the products array within the rates array. This has been fixed.
37697171	Refunds occurred during plan transitions for resources marked as FULL charge. A check was added to ensure the POID respects prorated settings. This has been fixed.
38681587	When a discount configured as “Don’t Apply to This Cycle” was applied through a Discount Sharing Group and later removed using PCM_OP_SUBSCRIPTION_ORDERED_BALGRP, the refund was prorated instead of fully refunded. This has been fixed.
38629103	A discrepancy was observed in bill item allocation. This has been fixed.
38300201	Granted balance was incorrect when a deal was canceled with price_tag enabled. The fix skipped updating rate flags with PIN_RATE_FLG_PRO_FORCED when date splitting was not used. This has been fixed.
38205102	A link object was missing in refund events for quarterly accounts during termination and termination cancellation. Link objects are now populated for in-advance billing so that both refund events reference the same link object. This has been fixed.
38311172	Refunds were generated even when products were configured to charge on cancellation for cycle arrears products. The fix ensures the usage map flag is honored, preventing refunds in such cases. This has been fixed.
38205105	Support for when_t was added to the PCM_OP_CUST_MODIFY_CUSTOMER opcode, enabling the creation of schedule objects. This has been fixed.
38229899	Refund allocation between old and new bills during the billing delay period was enhanced through a new business parameter, allocate_refund_to_charge_item. When disabled (0), refunds apply to the next bill. When enabled (1, default), refunds apply to the original charge item. This has been fixed.
37954752	When PCM_OP_SUBSCRIPTION_SHARING_GROUP_MODIFY was invoked without effective_t, sharing group dates were updated using the current time. The logic now uses end_t as effective_t when effective_t is not provided. This has been fixed.
37856214	When item type was configured as individual, cancellation and renewal charges for CF products canceled before billing were applied to the same item. The logic was updated so that cancellation and renewal charges are applied to separate items. This has been fixed.
37925658	First-month refunds for backdated cancellations were not generated when apply_charge_on_inactive_or_cancel_product was enabled due to incorrect rate flag handling. This has been fixed.
38116876	A PIN_ERR_NULL_PTR error occurred when a NULL rate POID was encountered during day-range rating. A NULL check was added to prevent this issue. This has been fixed.
38122199	Canceling a “Don’t Apply to This Cycle” discount via a Discount Sharing Group resulted in prorated refunds instead of full refunds. This has been fixed.
38050750	Purchase of discount deals failed when ValidateDiscountDependency was enabled due to incorrect pointer de-referencing. This has been fixed.
37925657	Tax data loading from the database was incorrect. Tax codes are now ordered by elem_id during loading. This has been fixed.
38073193	Tax-only adjustments were not handled correctly for events with multiple tax balance impacts. The logic was enhanced to compare and adjust only balance impacts with matching record IDs. This has been fixed.
36963137	Duplicate disputes appeared on the AR actions page for wholesale parent accounts. The fix ensures that only parent and rolled-up child AR items are returned. This has been fixed.
37873897	The ExcludePercentForZeroTaxAmt parameter was not fetched during retrieval using pin_bus_params -r. This parameter is now correctly read from the database. This has been fixed.
38165137	Transferred amounts from child accounts in wholesale hierarchies were incorrectly displayed in the UI. Transferred amounts are now updated only for non-wholesale accounts. This has been fixed.
38127027	PCM_OP_SUBSCRIPTION_CRUD_OFFER_OVERRIDE was not updating date ranges correctly. This has been fixed.
37708896	XML parsing failed when setXIncludeAware was unsupported. The code now gracefully handles UnsupportedOperationException, allowing parsing to proceed. This has been fixed.
38193443	A NULL POID passed to object-related functions caused failures. A NULL POID check using PIN_POID_IS_NULL was added. This has been fixed.
38365830	PCM_OP_BILL_GROUP_DELETE_MEMBER failed due to a NULL pointer. A new flag was introduced based on the AMS business parameter. This has been fixed.
38240835	Zero-tax scenarios with multiple jurisdictions were not supported. The Event_Over_Adjust_Enable feature was enhanced to handle these cases. This has been fixed.
37739576	The Event_Over_Adjust_Enable functionality did not work as expected when the tax amount was zero. It was enhanced to correctly support scenarios where the tax amount is zero. This has been fixed.
38702961	A core dump occurred during event adjustment when using the tax-only flag. This was resolved by implementing proper cookie management, specifically by resetting cookie pointers after each iteration of the PIN_FLD_EVENTS array. This has been fixed.
38262743	A check was implemented for the available tax amount to adjust accordingly. This has been fixed.
38352939	PCM_OP_AR_GET_ACTION_ITEMS returned an error for WholesaleEnabled business profiles if end_t was not passed. The time filtering logic was modified to handle the case where PIN_FLD_END_T is optional for wholesale billing scenarios. This has been fixed.
38289461	PCM_OP_AR_EVENT_ADJUSTMENT did not return a result and ended abruptly. A check was added to prevent calling PCM_OP_BILL_ITEM_TRANSFER when no event was adjusted. This has been fixed.
38616503	Object uniqueness was deleted in a separate transaction, which could not be rolled back with the abort opcode. Deletion of uniqueness objects is now handled in the same transaction. This has been fixed.
38544103	Object uniqueness was deleted in a separate transaction, which could not be rolled back with the abort opcode. Deletion of uniqueness objects is now handled in the same transaction. This has been fixed.
38629108	During rerating, cycle events were not calculated correctly, leading to incorrect cycle charges. The logic was updated to ensure appropriate cycle events are accurately identified and applied during rerating. This has been fixed.
38549206	There was an issue pulling images during brm_wsm deployment from authenticated repositories. An imagePullSecrets helper was added in the brm_wsm deployment spec to enable successful image pulls. This has been fixed.
38640475	Changes were made in /data/sequence. All sequences (/data/sequence objects) are now supported to handle increment values. By default, the increment value is 1.
38116868	Balance synchronization for the billing time discount event resulted in incorrect balances. Synchronizing ECE balances was skipped for the relevant event. This has been fixed.
38205098	Due to the absence of an object description, a false alarm was raised even though there was no functional impact. The error was reduced to a warning to avoid the false alarm. This has been fixed.
38240837	Timeouts occurred due to full table scans during execution of the PCM_OP_AR_GET_BAL_SUMMARY and PCM_OP_AR_GET_ACCT_BILLS opcodes. Pruning conditions were improved and additional optimizations were made to the SQL queries.
38661431	Event end_t was rounded during set_product_status, which caused incorrect balances to be fetched. The original start_t and end_t are now kept when they are already present in the event. This has been fixed.
38038404	During rerating, if the current balance was zero, the balance impact was skipped from back out, causing an incorrect granted balance after rerate. This has been fixed.
38346752	An opcode's timeout and start time were not returned correctly because the Java PCM thread string used a colon (:), which conflicted with the delimiter used in C-PCM, leading to incorrect correlation ID parsing. This has been fixed by parsing the delimiter in reverse to occur.
38205090	Tax was not applied when bill_now was called directly for subordinate accounts. The bill_now flow was modified to ensure tax is applied correctly for subordinate accounts.
38463074	The issue occurs when a wild array entry (PIN_FLD_CYCLE_FEES ARRAY [*] NULL array ptr) is added to the cache during "read with null" scenarios, causing it to leak into the READ_OBJ output and leading rating logic to incorrectly pick up ARRAY[*] instead. This has been fixed.
38473361	The tax selector referenced by multiple products was deleted when a single product was removed, resulting in unknown references of tax selectors in other product references. This has been fixed.
38154209	By default, the maximum size specified for the PIN_FLD_INVOICE_DATA field of the /event object is 4000. This value can now be changed in the database by enabling the extended data type capability.
38549202	PARSE_TSTAMP_ERR occurred during migration import. The has been fixed by replacing the HashMap with a ConcurrentHashMap to handle concurrent access and prevent such errors.
38446640	The Last_status_t was set using the Created_T field at the account level. It has been updated to use the Effective_T field instead because some accounts were activated after they were created. This has been fixed.
38451548	The poid_db did not update correctly because the process changed the deploy_status first, which prevented the poid_id from updating. The order was changed so that the poid_id is updated before the deploy_status. This has been fixed.
38395952	The name field under the GROUP_T table was not populated. Support was added to update the name field under GROUP_T. This has been fixed.
38484377	nzos_Write executed nzos_ServiceWrite only once upon encountering NZERROR_SSLWouldBlockErr, which could prevent the data from being completely flushed. The logic has been modified so that nzos_ServiceWrite is executed repeatedly.
38473363	During the write sequence, when an error occurred in nzos_Write, the SSL logic retried the write operation indefinitely. The fix ensures that retries are performed only for NZERROR_OK and NZERROR_SSLWouldBlockErr, avoiding infinite retries. This has been fixed.
38181771	In cases of multiple bill units for an account, if a refund was initiated without mentioning the refund item, it failed. As part of the fix, the item object is dropped when it does not match the current bill unit. This has been fixed.
38605060	During rerating, when the Billing day of month (BDOM) changed within the delay period, the system incorrectly used the old BDOM, leading to wrong cycle calculations for rerating cycle events. The rerating log was updated. This has been fixed.
38644781	When the cycle_tax event was associated with a secondary balance_group, during rerating, because the cycle_tax event does not have service_obj, the default account-level balance_group was picked for creating the rerated adjustment events. This has been fixed.
37888538	While modifying the tax selector, the old object was deleted and a new object was created, which resulted in an error during audit-based rating. The code was modified to update the existing /tax_selector object when it is modified. This has been fixed.
38415519	During rerating, monetary resources were assigned to incorrect items because BRM could not determine the correct item type in the absence of the item type selector configuration. This has been fixed.
38116871	A credit limit exceeded issue was reported during product purchase in BRM 15.1. To resolve it, syncing of ECE balances was skipped during processing of the in-advance cycle event. This has been fixed.
38176206	After upgrading to BRM 15.0.1, unrated events were created incorrectly because multiple selectors were added when rating failed for non-matching RPS. The fix ensured only one selector is added to the rating output so that events are processed This has been fixed.
38165140	During the reload process, the tax selector object was passed in the rate plan instead of the name, causing it to be overridden with a null value. A condition was added to validate the tax selector object in the rate plan during PCM_OP_WRITE_FLDS. This has been fixed.
38576441	Normal events were incorrectly excluded from auto-allocation during rerating due to an invalid event check. The fix ensures only backdated events remain unallocated, while normal events are allocated as expected. This has been fixed.
38419018	During tax calculation, an incorrect locale reference was used for updating the tax amount, which led to wrong quantity calculations. The locale information is now derived from each individual tax entry. This has been fixed.
38213618	During calc_only rerating, and in the case of multiple balance groups, the balance cache was not updated for the non-default balance group, resulting in incorrect balances. This has been fixed.
38576438	During cancellation, more than the actual charge amount was refunded when multiple tax rates were configured. The solution involved passing the original purchase event reference (PIN_FLD_LINK_OBJ) to the tax calculation opcode. This has been fixed.
38681584	For sub-balance impacts involving sponsorship objects, granted_bal was not updated. Granted_bal is now updated for sub-balance impacts with sponsorship objects. This has been fixed.
38549207	The tax rate for backdated adjustments was not applied correctly when there was a tax rate change. The logic was modified to skip using the item's created_t for the req_date_t field in backdated AR actions. This has been fixed.
38294245	When a product was set to start on first use, the system wrongly changed the event start and end times to a rounded cycle time. This caused errors in other systems that rely on the exact time. The system now keeps the original exact time. This has been fixed.
38305883	Ordered balance group creation failed when a member account was created, added to a DSG, and an ordered balance group was created in the same transaction. To fix the issue, a mandatory get was avoided as the transaction cache may not have had account info. This has been fixed.
37902619	In a single transaction, when multiple operations were executed on different balance groups, the balances maintained in the transaction were updated with the wrong balance. A code fix updated the correct balance in the transaction balances. This has been fixed.
38395950	Validation failures during multi-service plan transitions resulted in PIN_ERR_CREDIT_LIMIT_EXCEEDED. Code was enhanced to correctly handle plan transition scenarios and to prevent updates to the named transaction for syncing ECE balance. This has been fixed.
38395954	Balance synchronization for the billing time discount event resulted in incorrect balances. Changes were made to skip synchronizing ECE balances for the relevant event. This has been fixed.
38473373	The pin_rollover MTA used constant values in step search queries to retrieve valid buckets for rollover. These constants changed with each search, leading to different database execution plans and causing significant delays. This has been fixed.
38419020	The service status was not updated correctly before running the lifecycle state change post-opcode execution, causing the status change to go into an infinite loop. A fix ensures that the service status is updated correctly. This has been fixed.
38330644	The BRM real-time pipeline did not consider correct balances for discount evaluation. While merging BRM and ECE balances, BRM balances did not include sub-balance buckets, resulting in wrong balance updates. The fix fetches BRM sub-balances before merging. This has been fixed.
37708847	Issue with bal_grp_sub_bals_t.granted_bal value being 0 instead of null. A PL/SQL script was provided to set the granted_bal column to 0 wherever it is Null. This has been fixed.
38193440	Removing the PIN_FLD_ACTION field in SET_DD caused an error when the field was not present, which led to subsequent actions failing. The logic was updated to drop the field only when PIN_FLD_ACTION exists in the flist. This has been fixed.
37775911	There was an issue with lengthy queries. The SQL query buffer size was increased to accommodate lengthy queries, and the pinlog message buffer size was increased to log those queries in full length in the log file. This has been fixed.
38538941	The search query length exceeded the allocated buffer, resulting in a failed search operation. The buffer size was increased to accommodate larger queries. This has been fixed.
38549196	PARTITION_MIGRATE was being added even when it was not associated with the base table, which caused incorrect configuration updates. The logic now adds PARTITION_MIGRATE only when it is actually available for the base table. This has been fixed.
38339962, 37861241	When PCM_OP_DEVICE_CREATE was called inside a transaction, the system could not open the PCP context to DM, which caused the global device check to fail. The fix now passes a local context to PCM_OP_GLOBAL_SEARCH so the search runs outside the transaction. This has been fixed.
37850318	If a user executed pin_deploy replace in a multi-schema setup where the table was not present in the secondary schema, the operation failed. The request from pin_deploy was changed to ADD for PCM_OP_SET_DD by modifying PIN_FLD_ACTION. This has been fixed.
37697177	Bal(NCR) did not return the correct balance when used directly in the base_expression configuration. A fix was delivered to return the consolidated balance (cache balance + delta amount) for the Bal(NCR) expression config. This has been fixed.
38121732	Changes were made to folders of the batch_pipeline pod. The following folders were included for the batch_pipeline pod: ifw/formatDesc/Formats/TriggerBill and ifw/iScriptLib/iScriptLib_RevenueAssurance. This has been fixed.
38358151	Non-monetary resource IDs in pin_config_export_gl.xml did not load correctly because only a few bytes of the resource ID string were copied during processing. The code was updated to use the actual string length in the pin_strlcpy call. This has been fixed.
37978133	There was an issue with the default value while creating views. The column’s (related OBJ_DB) default value is now set correctly in the secondary schema while creating the views. This has been fixed.
38380929	When a cycle arrears product was inactivated, the charged dates were not updated properly, leading to incorrect cycle arrears fees. The charged dates are now updated properly during cycle arrears product inactivation. This has been fixed.
38204656	There was an issue with static functions. Unused static functions pinlog_time_round_to_midnight_apply_offset and pinlog_set_next_path_to_open were removed from pinlog.h. This has been fixed.
38499309	A NULL pointer de-reference caused a segmentation fault. A NULL check was added for the pointers to avoid NULL pointer de-references. This has been fixed.
38451547	Appropriate dependencies were shipped with the BRM environment to support WSImport execution. Dependencies were added for impl_generator. The pin_wsgen script was also updated to generate Java stub files and implementation classes.

Fixed Issues in BRM 15.1

Table 9-2 lists the customer-reported issues that were resolved in BRM 15.1.

Table 9-2 Fixed Issues in 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. This 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 canceled 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 Receivable 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 an ORA-0100 error. This has been fixed.
36684361	CMT sometimes was not able to convert Extension Date Field to Unix Timestamp. 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.

Fixed Issues in BRM 15.0.1

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

Table 9-3 Fixed Issues in 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	Timeouts on the CMT loader were causing 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.

Fixed Issues 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):

• Fixed Issues in ECE 15.2
• Fixed Issues in ECE 15.1
• Fixed Issues in ECE 15.0.1

Fixed Issues in ECE 15.2

Table 9-4 lists the customer-reported issues that were resolved in ECE 15.2.

Table 9-4 Fixed Issues in ECE 15.2

Bug Number	Description
37876932, 38041505	The Get ECE Balances operation from BRM did not return the reserved amount information correctly. This has been fixed.
38176354	It was observed that if there was a PVC connectivity issue while retrieving the credential stored in the wallet, the JMS connection was not established and an exception was thrown. This has been fixed with a retry mechanism.
38576616	It was observed that the item sponsor was not created for the current month after incremental loading. This has been fixed.
37773442	For debit_unit and debit_amount operations, when the impact passed in was more than the actual available resource, reverse rating was performed to impact only the available resource without generating any ceiling breach notifications. This has been fixed, and reverse rating for debit_unit and debit_amount operations is now removed from the configuration.
37815338	If the tax codes were not defined in PDC but were defined in charging-settings.xml, ECE applied taxes correctly but with an error message. This is now changed to a warning, indicating that PDC should be used to define tax codes.
38208344	After active session cleanup, when the old session was terminated and the old session’s last usage request had an RSU, it was incorrectly rated as a USU with mid-session rating, impacting balances. This has been fixed.
38205310	While publishing the cycle forward notification event to the JMS queue, errors were observed due to an incorrect product type value. This occurred only when renewable balance items were present and usageStartTime was later than the renewable balance item’s validity. This has been fixed.
38311364	In previous releases, while rating daily bundles with a conditional RUM, the recurring bundle timestamp was incorrectly set to the following day. This has been fixed.
37859424	In some cases, the cycle forward notification to BRM was not generated properly due to incorrect timestamps. This has been fixed.
38229336	When multiple charging requests were sent to ECE within the same second, and if the deployment had timestamp-overriding logic (for example, time-zone adjustments) implemented in the preOCS extension, ECE responded with DIAMETER_UNABLE_TO_COMPLY (5012). This has been fixed.
37883420	In some cases, ECE incorrectly responded with 4012 even when a quota grant was available. This has been fixed.
37634578	The Diameter Gateway did not log the correct CCA message when the setBypass method was invoked from the Gy extension. This has been fixed.
37833671	When ECE responded with DIAMETER_CREDIT_LIMIT_REACHED (4012) at the MSCC level, the command-level logs incorrectly indicated DIAMETER_SUCCESS (2001). This has been fixed.
38706461	When the user could not be resolved in ECE, the Diameter Gateway response was DIAMETER_SUCCESS instead of DIAMETER_USER_UNKNOWN. This has been fixed.
37944973	ECE added extra MSCC entries corresponding to the rating groups, with incorrect service identifiers, causing failures at the Diameter Gateway. This has been fixed.
37861418	For a subscriber lifecycle state change, multiple LIFECYCLE_TRANSITION_NOTIFICATION_EVENT events were generated for the same subscriber, resulting in a large number of audit entries. This has been fixed.
38412733	If a subscriber whose PUID was recently updated was deleted, any SLR request referencing the old PUID resulted in a timeout instead of returning user-unknown. This has been fixed.
38473559	HTTP Gateway returned “No handler found” when a 5G SA (Nchf) REST API conforming to v2 was intercepted for processing. This has been fixed by adding API version validations.
38439629	After restarting ECE, the audit product details were incorrect. This has been fixed.
37850449	Even if a PayGo offer existed, an FUI was triggered when the limit was exceeded instead of charging with PayGo. This has been fixed.
38671791	In previous releases, when multiple services belonged to the same account and both services were for the same user, calls between these two services were not rated as CUG. This has been fixed.
38230091	With TTC configured, incorrect calculation of unrated quantity for a conditional bundle caused an FUI with Final Unit Action as Terminate to be sent in CCA, even though the customer had sufficient balance. This has been fixed.
37902757	In some cases, LockContentionException was thrown in the rating flow. This has been fixed and a new configuration for retries during contention was introduced to enable and control the number of retry attempts.
37882351	With a tax configuration defined and synchronized from PDC, taxation during the last few days of validity was not properly applied in ECE. This has been fixed.
38010068	With a discount sharing group that included products of the same customer within the same billing unit, when a usage request was sent from a member product, the itemType for the owner was incorrectly assigned as /item/sponsor. This has been fixed.
38033203	When multiple balance item IDs existed for the same balance item code, balance impacts were incorrectly applied. This has been fixed.
38358318	When generating CHF CDRs, if a request with a particular ISN was retransmitted due to a link failure and subsequent requests were sent with a greater ISN, negative durations were observed in CDRs. This has been fixed.
37902761	When generating CHF CDRs, if a failover occurred, subsequent partial CDRs were not generated from the secondary for the same continuing session because the CDR gateway was unable to fetch the correct DB connection from the federated configuration. This has been fixed.
37798589	Under race conditions, the Diameter Gateway responded with DIAMETER_UNABLE_TO_COMPLY because the corresponding Sy session was not retrievable. This has been fixed.
38073370	SNRs were generated for balance buckets that were already exhausted, leading to multiple SNRs. This has been fixed.
36745232	Get ECE Balances operation from BRM did not return original balance information correctly. This has been fixed.
38005612	For a few specific accounts, the rating operation failed due to cleanup of balances while there was an active reservation for a session. This has been fixed.
38010076	It was not possible to drop service login information (Public User Identity) from threshold notification payloads during notification generation. This has been fixed by providing a PUID enrichment API in both threshold and credit breach extensions, allowing modification of the PUID list from extensions.
37820664	Extending ECE to invoke BRM opcodes through BRM Gateway was not allowed from update extensions. This has been fixed.
37839932	The command pin_cmt -deploy_ece did not send offering override details to ECE. This has been fixed.
37833652	In some cases, the price tag feature did not work with END_T as NULL when purchasing the product or discount. This has been fixed.
38181911	In some cases, when a deal in BRM was canceled, no SNR was generated from ECE. This has been fixed.
38341835	When BRM Gateway encountered an error, it did not log the correct opcode information that it was trying to invoke in BRM. This has been fixed.
37876936	PUIDs for threshold breach down events were null in the update extension for terminate requests only. This has been fixed.
38373102	ECE did not have the latest and greatest charge offer information. This has been fixed.
38726895	PricingUpdater consumption of pricing objects was very slow, requiring API latency improvements. This has been fixed.
37861420	Customer Updater removed the customer entry from the ECE cache during lock release. This has been fixed.
38068078	After incremental loading of the customer from BRM to ECE, the consumption rule for a balance element was set incorrectly to NONE even when it had a valid value. This has been fixed.
37839929	The Helm chart templates did not include the TZ parameter for time zone and it had to be added manually. This has been fixed by adding the TZ parameter to all Helm chart templates with the default value “UTC”.
38205307	Active session cleanup triggered a large number of rated events as part of the terminate request. This has been fixed.
37924394	The ECE database grew rapidly because retention policy was not configured properly. This has been fixed.
38738545	It was observed that the rerating flow triggered from BRM did not create backout events. This has been fixed.
37871948	In the post-rating stage, incorrect item assignment was observed. This has been fixed.
38159899	Discounting for percentage-based discounts showed incorrect calculations. This has been fixed.
37700425	Multiple occurrences of customer_in_transaction reason codes were reported as failures in ECE logs. However, in OCOMC, the corresponding error codes were NULL. This has been fixed.
38282235	In some cases, when the item ID was blank, REF did not generate rate events. This has been fixed.
37865182	The session ID and client routing data were set to null when triggering the SNR notification using the SamplePostChargingExtension. As a result, notifications lacked these details and defaulted to Kafka partition 0 instead of the intended partition. This has been fixed.
38640633	When ECE split a charge into two buckets: one before a grant and one after, the impact types were set incorrectly. This has been fixed.
38726891	In some cases, ECE threw exceptions during balance management for current balance after a rating impact. This has been fixed.
37701611	If the post-rating extension was enabled, ECE incorrectly overrode the net quantity information in the unratedNetOriginalQty map with the rated quantity. This has been fixed.
37700495	For mid-session CDR rating use cases, ECE did not evaluate resource depletion for sending an FUI, which was incorrect. This has been fixed.
37654336	ECE threw exceptions when: Multi-RUM and multi-tariff rating was used An extension was enabled One of the tariffs was single-RUM rated The extension’s rating results did not have entries for all RUMs This has been fixed.
37702994	During rating, an incorrect item type was applied to delayed usage tax when ItemRule was configured based on zoneValue. This has been fixed.
38330839	ECE sent an FUI and DIAMETER_CREDIT_LIMIT_REACHED (4012) in MSCC while the customer still had resource balance. This has been fixed.
37845610	For some subscriber accounts, ECE incorrectly added balance buckets that had no granter and had infinite validity. This has been fixed.
37642427 37642429	Notifications were not sent to the correct partitions from ECE. This has been fixed.
37773470	When a subscriber initiated a session and terminated it immediately, resulting in zero used quantity, ECE responded with the 5031 DIAMETER_RATING_FAILED error. This has been fixed.
38587898	Uninitialized policy counters were considered zero and were not skipped. In some deployments, they needed to be skipped. This has been fixed with the configuration parameter considerUninitialisedBalanceAsZeroForPolicy, with the default set to true, aligning with the previous behavior.
38671788	Around tariff time change (TTC), when balance was available to consume before TTC and not available after TTC, ECE incorrectly sent an FUI when the request came before TTC and there was balance available to consume. This has been fixed.
38719152	For a two-site deployment, when a failover occurred with one site down, ECE did not generate SNR and RAR from the failed-over site. This has been fixed.
37660815	In some cases, there were a large number of entries in balanceItemModifiedDuringUpdateActivity, causing a timeout for the Get ECE Balances BRM operation. This has been fixed.
38235941	In a two-site (active/hot-standby) deployment setup, the attributes in JConsole MBeans were different between the primary site and the secondary site. This has been fixed.
37850456	With an ECE deployment provisioning a renewable offer, when the GSU size was greater than the available free units, the user was blocked for further usage. This has been fixed.
38297072	ECE incorrectly returned GSU for some add-on offers even after an FUI was sent in the response for the previous request. This has been fixed.
37845118	SLA incorrectly had policy counter status for expired balances. This has been fixed.
38122407	In a TTC scenario, validityTime was reduced by 60 seconds, causing inconsistency in validityTime. This has been fixed.
37850453	Rating did not work as expected in a multi-tier charge rate plan configuration with rollovers. This has been fixed.
37839927	With an ECE deployment provisioning a renewable offer, reload notifications were not triggered as expected according to defined threshold percentages. This has been fixed.
37831802	The following issues were reported and fixed: When there was insufficient balance and partial rating occurred, the grant was zero when the post-rating extension was called; also, when multiple grants were made for a resource, a separate bucket should not have been created for the same resource. When USU was zero and an active reservation existed, the consumed reservation was wrongly updated when the post-rating extension was called. Error code 4012 was sent in CCA along with a valid GSU.
37847881	RG-level termination prevented the user from receiving an RAR for a top-up event. This has been fixed.
37839923	With an ECE deployment provisioning a renewable offer, the renewal fee was wrongly updated for renewable offers when relimits were purchased. This has been fixed.
37796899	With an ECE deployment provisioning a renewable offer, unused free units were not rolled over after billing. This has been fixed.
37833658	For a subscriber with a daily bundle offer and an offer profile configured, once the tier was reached an SNR was triggered as expected. However, for the same session that continued until midnight, an additional SNR was triggered. This has been fixed.
37815333	Discount trigger conditions were not evaluated correctly. When ECE evaluated alteration offerings, it did not update the balance snapshot with the recent impacts from the charge offer evaluations. As a result, the alteration condition on the balance element was not satisfied during alteration offering evaluation, and balance reservation was not made correctly. This has been fixed.
37833661	A spike was observed in the Coherence Journal backlog because every time there was a write to the Customer cache, POF_AUDITED_USED_PRODUCT_SHARING_AGREEMENTS was serialized but not deserialized. It was added to the evolutionData object and stored in cache. This has been fixed.
37773467	For a rating during midnight, ECE responded with a Diameter 4012 error. This has been fixed.
38655624	For offline rating for mobile services, ECE threw exceptions, resulting in suspense management of those error CDRs. This has been fixed.
38294417	When rating was performed for an account with discount sharing, for usage that qualified for sharing ECE threw exceptions. This has been fixed.
38294423	ECE sent incorrect GSU for usage in the last minute of the product/balance validity expiration when checkReservationOverImpact was enabled for linear rating. This has been fixed.
38294427	When processing a USU greater than the GSU, the extra usage was not processed for charging with PayGo or for recording an overage. This has been fixed.
37878920	Due to a rounding issue, an incorrect GSU was granted during rating for update requests. This occurred when the rating period was split because of different validity periods of the balance buckets, and while calculating the quantities for each split, a rounding error caused a trailing one in the quantity range, leading ECE to grant an incorrect GSU. This has been fixed.
37888746	In the ECE prerating extension, if an RSU was altered using the alterRequestedUnits API, ECE threw an exception without considering the altered RSU for rating. This has been fixed.
38016191	Incorrect discounting occurred due to rounding issues while splitting the rating period. This has been fixed.
38441721	Duplicate SNR and threshold breach notifications were triggered for the same balance. This has been fixed.
38038595	When an alteration plan with range [0-quantityPassed] was further split based on different discount objects, the calculated impact was not in sync with the sum of the impacts after splitting. This has been fixed.
38176356	The quantity range split was not performed correctly for peak and off-peak in ECE during rating. This has been fixed.
37876930, 38154332	In some cases, a subscriber account could use services even after the service was set to inactive for system-level charge offers. This has been fixed.
38358321	BRM Gateway did not receive messages from JMS after being idle for 2–3 hours because it lost the connection to JMS and the connection was not reinitialized. This has been fixed.

Fixed Issues in ECE 15.1

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

Table 9-5 Fixed Issues in 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 preference information was not exposed in the 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 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 timing out at the 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 an 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 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 an 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 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 the old session was getting a success response after being overridden by a 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, the Diameter Gateway timeout for SNR/SNA was permanently set to 10 seconds. This has been fixed. Now, it is a configurable option and can be set in milliseconds. This is to avoid long wait times 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 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 worker node 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, a 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 has the flexibility to choose only 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 context 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 configuration file 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 committed 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 levels. 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 midsession 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 on the 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 a new metric type has been 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, 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 a 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 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 an 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.

Fixed Issues in ECE 15.0.1

Table 9-6 lists the customer-reported issues that were resolved in ECE 15.0.1.

Table 9-6 Fixed Issues in 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.

Fixed Issues 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):

• Fixed Issues in PDC 15.2
• Fixed Issues in PDC 15.1
• Fixed Issues in PDC 15.0.1

Fixed Issues in PDC 15.2

Table 9-7 lists the customer-reported issues that were resolved in PDC 15.2.

Table 9-7 Fixed Issues in PDC 15.2

Bug Number	Description
38499223	Certain configured pricing values for rounding up charge offers were not persisted as defined, causing runtime pricing discrepancies. This has been fixed.
38441625	Republishing to a specific target engine encountered issues that were resolved by improving the publishing framework and performance. This has been fixed.
38458958	Exporting offers with special characters failed because the tool parsed the offer name incorrectly; a separator option was introduced to resolve it. This has been fixed.
38499754	Offer migration introduced discrepancies in balance grant and consumption configuration that led to unexpected rating results. This has been fixed.
37905218	Tax code configuration created in PDC was not preserved in order when published to BRM; a new column was added and the PDC UI was enhanced to rank tax codes. This has been fixed.
38414032	During discount configuration, higher-value tier limits were auto-adjusted, preventing intended upper-bound values. This has been fixed.

Fixed Issues in PDC 15.1

Table 9-8 lists the customer-reported issues that were resolved in PDC 15.1.

Table 9-8 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.

Fixed Issues in PDC 15.0.1

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

Table 9-9 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.

Fixed Issues in Billing Care

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

• Fixed Issues in Billing Care 15.2
• Fixed Issues in Billing Care 15.1
• Fixed Issues in Billing Care 15.0.1

Fixed Issues in Billing Care 15.2

Table 9-10 lists the customer-reported issues that were resolved in Billing Care 15.2.

Table 9-10 Fixed Issues in Billing Care 15.2

Bug Number	Description
37595260	Reopening the Allocate Payment dialog box from the payment details displayed a blank context menu and lost the initially displayed allocation details. This has been fixed.
37575660	Searching an account by service ID in a multischema environment exhibited performance issues. This has been fixed.
37574073	With both bill and event disputes open, the event dispute was shown twice and the due and open dispute amounts were incorrect. This has been fixed.
37573747	Previously performed A/R action news feed items were not rendered properly in the UI. This has been fixed.
37697179	Batch payment reversal validation populated reversal fields with refund-event data and validation failed; parsing an account with a large number also failed. This has been fixed.
37674154	News feed entries during Product Cancel were populated with the service login instead of the external user. This has been fixed.
37629143	Account search by login was case-sensitive, resulting in no results in some cases. This has been fixed.
37602623	The Allocate Payment page did not consistently display the remaining amount to be allocated when the unallocated amount was large. This has been fixed.
38229901	Service creation through the Billing Care REST API did not enforce uniqueness for service alias values, allowing duplicates. This has been fixed.
38205108	In the Spanish version of Billing Care, the Payment Suspense screen did not display fields such as Allocate and Auto Allocate. This has been fixed.
38085431	Performing a full recycle of payments from Suspense created an extra entry in the event table. This has been fixed.
38025505	Reason codes provided during the create a wire transfer batch were not persisted in BRM. This has been fixed.
37727589	Percentage Item Adjustment performed from a Portuguese-language browser was mapped to the wrong item. This has been fixed.
38415522	Performing a plan transition using the Billing Care REST API mapped plans incorrectly; the logic was improved and a transitionOn field was introduced to capture transitions accurately. This has been fixed.
38305887	During Event Adjustment from Billing Care, the reason codes block did not render properly in the UI. This has been fixed.
37844646	Enhanced the Get Bundles For An Account and Get Offer Details APIs to include granted balance and granted balance object details. Additionally, enhanced Get Balance Groups for the Bill Unit API to return granted balance sub-balances for non-currency balances.

Fixed Issues in Billing Care 15.1

Table 9-11 lists the customer-reported issues that were resolved in Billing Care 15.1.

Table 9-11 Fixed Issues in Billing Care 15.1.

Bug Number	Description
37586445	The 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 was displaying for manual discounts in asset section. The 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, when clicking Noncurrency Resources, the pop-up was not displayed correctly. The pop-up is larger than in BRM 12, and the arrow does not point to the Noncurrency Resources 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	The improper display of an error message during refunds in Billing Care has been resolved.
37206352	The Newsfeed Recurring Charge link is redirecting to Account Charges instead of Subscription. This has been fixed.
37232898	When clicking the Validate button, Billing Care displayed a 'Records in Batch' error. When a custom reversal was being made using Billing Care, in some cases conditional logic was searching for payment in the /event/billing/charge table instead of /event/billing/payment. The conditional logic for custom payments was modified to search for payment in correct table.
37146842	While performing an event adjustment, the percent (%) symbol was not 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 and search alias list values other than the 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 Billing Care, 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	The event view was getting distorted and the Show More button was not visible. This has been fixed.
36541425	Comments and notes from a 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 dialog 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.

Fixed Issues in Billing Care 15.0.1

Table 9-12 lists the customer-reported issues that were resolved in Billing Care 15.0.1.

Table 9-12 Fixed Issues 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.

Fixed Issues 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:

• Fixed Issues in Business Operations Center 15.2
• Fixed Issues in Business Operations Center 15.1
• Fixed Issues in Business Operations Center 15.0.1

Fixed Issues in Business Operations Center 15.2

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

Table 9-13 Fixed Issues in Business Operations Center 15.2

Bug Number	Description
38602753	A scheduled custom job could not be edited from the Jobs Timeline page because the edit context menu did not appear. This has been fixed.
38106480	Setting the BRM virtual time through Business Operations Center applied a one-hour offset for non-DST dates, while timestamps during DST periods were set correctly. This has been fixed.

Fixed Issues in Business Operations Center 15.1

No customer-reported issues were resolved in Business Operations Center 15.1.

Fixed Issues in Business Operations Center 15.0.1

No customer-reported issues were resolved in Business Operations Center 15.0.1.

Fixed Issues in BRM Thick Clients

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

• Fixed Issues in BRM Thick Clients 15.2
• Fixed Issues in BRM Thick Clients 15.1
• Fixed Issues in BRM Thick Clients 15.0.1

Fixed Issues in BRM Thick Clients 15.2

No customer-reported issues were resolved in the 15.2 release of the BRM thick clients.

Fixed Issues in BRM Thick Clients 15.1

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

Table 9-14 Fixed Issues in BRM Thick Clients 15.1

Bug Number	Description
36971995	Update Number Category is not working in Number Administrator Tool. This has been fixed.

Fixed Issues in BRM Thick Clients 15.0.1

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

Table 9-15 Fixed Issues 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.