Summary of Customer-Reported Fixes

1 Summary of Customer-Reported Fixes

The Oracle Communications Billing and Revenue Management (BRM) 12.0 Patch Sets include multiple customer-reported bug fixes.

Topics in this document:

Customer-Reported Fixes in BRM

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

Customer-Reported Fixes in BRM 12.0 Patch Set 8

Table 1-1 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 8.

Table 1-1 Customer-Reported Fixes for BRM 12.0 Patch Set 8

Bug Number	Description
34909676	A user could not encrypt data using pin_crypt_app if the user was not defined in /etc/passwd. For a user authenticated by an external LDAP, there will be no entry in /etc/passwd. This was observed for apps linking to Oracle NZ ZT SDK. This has been fixed.
34595937	The pin_cycle_fees utility was fetching and updating canceled products, resulting in a deadlock and unnecessary performance issues. This has been fixed. The utility now prevents canceled products from being fetched, which improves performance.
34782991	If a closed bill returned an error, the cycle forward opcode was generating a core. This has been fixed. The code has been updated to exit gracefully without generating a core.
34909677	When an account or service was reactivated, all discounts were reactivated even if the discount was in inactive state before the account or service was reactivated. This has been fixed.
34770422	A recurring charge configured not to be charged when canceled was not being applied even if the service status was made inactive. If the status was not active, the product picked up for charging was later skipped and dropped before rating. This has been fixed.
34872438	When the pin_event_extract utility was run for backout and rerate, there was a failure while opening the pin_event_extract.cfg file. This has been fixed.
34504353	When there are multiple plans, during event creation, PIN_FLD_PROGRAM_NAME was not set due to which rerating was failing. This has been fixed.
34820222	When processing batch payments, for certain error conditions, the payment transaction was partially rolled back and an error buffer was cleared without logging the error. Because of this, though the payment failed event was recorded, the payment event itself was lost due to the partial roll back. This has been fixed. Now, errors are logged before clearing the error buffer.
34768047	In PCM_OP_SELECT_ITEMS, some fields were not getting copied over when the input flist was copied to an intermediate flist. This has been fixed.
34643637	When running trial billing for child accounts in a large hierarchy with -pay_type 10007 generates trial invoices for all child accounts in the system, it was observed that the database size was increasing exponentially. This was caused by memory leaks in invoicing. This has been fixed.
34872435	The pin_ledger_report utility was adding extra lines to the GL report. This has been fixed.
34763825	GL reports were generating empty reports for the secondary schema. This has been fixed.
34648175	Email notifications were not published to DM_AQ due to incorrect transaction handling. This has been fixed. Now, the transaction is committed for every email notification.
34574764	The items created as part of migrating subordinate accounts in wholesale billing hierarchies were not having some of the fields populated. This caused subordinate items to not get rolled up to the parent account. To fix the issue, changes were made to populate PIN_FLD_AR_BILL_OBJ, PIN_FLD_AR_ITEM_OBJ, and PIN_FLD_ITEM_CLASS for subordinate items for wholesale billing hierarchies.
34815112	The pin_monitor_balance utility was reporting errors for write-off reversal events. It was observed that the PIN_FLD_SUB_BALANCES array was truncated in the input for write fields. This occurred because the balance_large column of EVENT_ESSENTIALS_T table was not being completely read by dm_oracle when there were a large number of balance arrays. This has been fixed.
34699267	Performance issues were observed with pin_cycle_fees when run in -verbose mode. This occurred because it attempted to collect a list of unique account IDs that were processed using a linear search on a large flist. This has been fixed. It now avoids the search for verbose mode, and only calls it for revenue assurance mode.
34560096	The config credit profile search was resulting in a "No memory" error in production environments, because the customer had a huge number of credit profiles configured. This has been fixed. The code was modified to search only required credit profiles and update it in the global flist, instead of fetching the whole object.
34824478	In the billing flow, a rounding issue was observed for the bill's service charges. This has been fixed. Rounding with correct precision occurs when the GenerateJournalEpsilon business parameter is enabled.
34927430	A performance issue was observed with the opcode PCM_OP_AR_RESOURCE_AGGREGATION. To fix the issue, the PCM_OP_AR_RESOURCE_AGGREGATION opcode flow was modified to use PCM_OP_READ_FLDS instead of PCM_OP_SERACH, which eventually improves the opcode performance.
34459316	It was observed that the tax created by adjustments done during the delay period was not included in the final bill. This has been fixed.
34840219	The PDC synchronization performance was very slow. This has been fixed. Some of the search queries and the pin_flist_get_next function were optimized. PIN_FLIST_ELEM_TAKE_PREV is introduced to optimize few of iterations during the set_price_list flow. All these changes are controlled using an Infranet.properties entries. To use the optimized code, set the property infranet.ondemandcaching=1 in the load_price_list Infranet.properties file. If the property is not set, set_price_list will perform as earlier.
34932387	With open item accounting, corrective bills were not updating the current total and total due in the bills after bill adjustments. This caused mismatches, and corrective bills still showed the original amounts. This has been fixed.
34583876	It was observed that the journal update was taking longer than expected. To fix the issue, the journal table was updated using a stored procedure instead of using BRM opcodes.
34829048	The pin_recycle utility was forming a bad template and reporting an error. This was caused by an issue with string manipulation. This has been fixed.
34829050	When reactivation of closed accounts with stop_bill_closed_accounts was enabled, invoice items for new purchases were not displayed after reactivation. Due to performance reasons, invoicing searches for items within the last 60 days to reduce searching pruned partitions. When item_t was not partitioned and items were pre-created more than 60 days ago, a new invoicing business parameter DisableFilterItemByPruneTime was introduced to skip searches based on partition pruning time. The search now is done for all items.
34763827	It was observed that the parent CM process was doing the config refresh activity in another thread when the business parameter ConfigCacheRefreshInterval (2 minutes) was enabled. To fix the issue, the config refresh logic was moved from the multithreaded CM to separate child CM processes.
34824477	A fixed size was allocated for stored procedures in cache and was not configurable. This has been fixed. Changes were done to read the size from the CM pin.conf file so that users can configure the size according to business requirements.
34727941	The pin_wsdl_generator utility was throwing SAX parser exceptions as it was expecting to validate the XML file against a DTD file. Changes were made to set validation to false, so that the XML file is not validated against a DTD File.
34805598	The PIN_FLD_PROGRAM_NAME field was mandatory for the PCM_OP_CUST_CREATE_BAL_GRP opcode, but it was missing in the documentation. This has been fixed.
34703854	The pipeline was unable to start on Solaris if there was more than one iScript file in EvalScriptFiles. To fix the issue, a new input stream object was created for each file.
34629289	The PCM_OP_AR_GET_ACCT_BAL_SUMMARY opcode was throwing errors after deleting the last bill. To fix the issue, a check was introduced for last bill availability before fetching the same for processing.
34820221	The pipeline process was crashing when the customer login was found without having any valid service reference. To fix the issue, the error message "ERR_CUSTOMER_LOGIN_SERVICE_NOT_FOUND" was added. Also, a null check was added for the pointer variable.
34690037	Debug messages were logged incorrectly. This has been fixed. The validation message was moved from the discount trace to the normal level pipeline log when no usage map is found for the given event type.
34791706	The Balance Tab view for an account with multiple child accounts was taking approximately four minutes to load the page due to huge search results and corresponding processing time. This has been fixed. The search query now returns only the appropriate results.

Customer-Reported Fixes in BRM 12.0 Patch Set 7

Table 1-2 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 7.

Table 1-2 Customer-Reported Fixes for BRM 12.0 Patch Set 7

Bug Number	Description
34147509	The partition pruning condition was not being added for delayed events when the PCM_OP_SEARCH template contained a type-only POID and CREATED_T in its search arguments. The check for partitioned classes was skipped, causing the subsequent logic of adding the partition pruning condition not being run. This has been fixed.
33868116	When an environment variable was referenced in a pin.conf file in ${ENV} format and the environment variable was not defined, the Oracle DM process hung during startup. This has been fixed. The Oracle DM process now logs an error and exits gracefully.
34073234	The BRM cloud native CM service was not allowing external access using an IP address. Only one DNS name was supported in the TLS certificate. This has been fixed. You can now configure multiple DNS names and IP addresses in the TLS certificate.
34031791	The deployment of a large BRM storage model was failing because tablespace details were not getting updated correctly due to syntax issues while concatenating the Perl strings. This has been fixed.
34289048	The pin_multidb script was failing because internally PinResetSeq was failing. This was due to a CLASSPATH mismatch for ojdbc8.jar. This has been fixed. The correct CLASSPATH was updated for ojdbc8.jar and pin_multidb.pl to successfully complete the multischema configuration.
34043082	When 30-day proration was enabled, discount scale calculations were incorrect for sequential cycle discounts. This has been fixed.
34123644	The bill adjustment flow was not working when the BillPaymentDeallocation AR business parameter was enabled and the item array was sent in the input flist. This has been fixed. The opcode flow now unallocates the payment amount and performs the bill adjustment successfully.
34172078	Connection Manager (CM) was crashing while running the PCM_OP_AR_GET_BILL_ITEMS opcode because it was trying to read an object from an invalid output flist. Additional checks have been added in the PCM_OP_AR_GET_BILL_ITEMS opcode flow to report an error so that the CM will not crash.
34086305	The validity start and end dates for resources granted as part of purchase fees were calculated incorrectly. This has been fixed.
34246136	The Oracle DM process was running redundant queries, which degraded performance. This has been fixed.
34023158	When the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode was called, the start and end dates were updated incorrectly for deferred product purchases. This led to valid discounts not getting applied to products. This has been fixed.
34074210	When a charge offer included a maximum number of charge offer instances that a customer could own at one time, BRM included expired products in its count of active product instances. This has been fixed.
34043086	Cycle charges were not applied correctly when a product was activated and inactivated multiple times in a cycle. This has been fixed.
34391835	Multiple cycle arrears discounts were not applied correctly when they started and ended in the same cycle. This has been fixed.
34320482	When a service was suspended and unsuspended on the same day, the balance bucket for future months was not getting created even after running partial billing. The bucket was created only when the account was suspended and unsuspended again. This has been fixed.
34064240	Discounts were getting canceled completely even when only a partial quantity was canceled. This has been fixed so that the partial quantity is subtracted and the discount is not canceled.
34209613	The Paymentech DM was sending junk characters when sd_*_{dba,pdt,phone} was not configured. This has been fixed. The DM does not send junk characters in the M record and is also enhanced to send an empty M record so that defaults configured for Paymentech are used.
34125857	For payment inquiries, the debit number was not visible when the debit number was null in the BRM database for paid amount. This occurred because the PIN_FLD_DEBIT_NUM and PIN_FLD_CARD_TYPE fields were being dropped during calls to the PCM_OP_BILL_RCV_PAYMENT opcode. This has been fixed, and the logic is corrected to not drop these fields.
34175443	After account creation, duplicate packages were being displayed under subscriptions. This occurred because the grouping of purchased products was done using the plan POID and creation time. This has been fixed. The plan POID and package ID are now used for grouping.
34058072	Warning issues occurred when the declaration of variables was static in the header file and not used in the corresponding file where it was imported. This has been fixed by changing the location of variable declarations and definitions from the header file.
34052733	When the ApplyDiscountOnZeroCharge rating business parameter was disabled and the product scale was a non-zero value, a signal 11 error was generated during a call to PCM_OP_SUBSCRIPTION_SET_PRODINFO. This was caused by a memory release issue. This has been fixed.
34048119	A signal 11 error occurred in PCM_OP_CUST_COMMIT_CUSTOMER, because an flist was destroyed but the pointer was not assigned to null. This has been fixed.
34095404	When BRM opened a read-only transaction for an individual opcode that had only read operations, time-based consistency sometimes led to an ORA-01466 error. This has been fixed. If an ORA-01466 error occurs during read-only transactions, BRM now rolls back the transaction and retries the operation a configurable number of times.
34308528	Opcodes have been added to BRM Web Services. The following opcodes have been added in JCA15Adapter.rar, BrmWebServices.war, and infranetwebsvc.war: PCM_OP_SUBSCRIPTION_ORDERED_BALGRP PCM_OP_SUBSCRIPTION_ORDERED_BALGRP_BULK_MODIFY
34115373	While loading balances with credit profile fields in an input XML file, pin_cmt was throwing NullPointerException. This occurred because of a missing sequence in the REC_ID column of the CFG_CREDIT_PROFILE_T table. This has been fixed.
34052735	When the PIN_FLD_BUSINESS_PROFILE_OBJ input flist field in PCM_OP_CUST_COMMIT_CUSTOMER was set to a non-invoicing type, an iScript was not triggered. This has been fixed.
34223098	The cross-schema account hierarchy was failing because hierarchies can be built only with accounts residing in the same schema. The error message in the cm.pinlog file has been enhanced to include more meaningful error information.
33994664	When the ConfigCacheRefreshInterval system business parameter was enabled, the cache refresh for /config/provider_taxes happened every time taxation was requested in BRM. This has been fixed.

Customer-Reported Fixes in BRM 12.0 Patch Set 6

Table 1-3 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 6.

Table 1-3 Customer-Reported Fixes for BRM 12.0 Patch Set 6

Bug Number	Description
33599255	For events having multiple tax codes, tax-only adjustments were reversing the wrong amount and an additional amount was getting reversed. This has been fixed.
33705754	When timestamp rounding was disabled, cycle fee end dates were still being rounded. This lead to incorrect scale calculation. This has been fixed.
33389642	After the billing day of month (DOM) was changed within the delay period, the /schedule object's PIN_FLD_ACTG_FUTURE_T field was updated. When pin_bill_accts was run, the /schedule object's PIN_FLD_ACTG_FUTURE_T field was incorrectly being aligned to PIN_FLD_ACTG_NEXT_T. This has been fixed. Now, the /schedule object will not be created and instead the DOM will be updated in the /billinfo object, which will align with PIN_FLD_ACTG_FUTURE_T when billing is triggered.
33150179	Recurring fees were being applied when the subscriber was in a suspended state and the state was being changed from suspended to active. This has been fixed. PCM_OP_CUST_SET_STATUS passes a new flag to the PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS opcode, which indicates whether to skip applying the cycle fee.
33915097	BRM cloud native encountered an invoice export issue in which the formatter threw an java.lang.NoClassDefFoundError:oracle/xml/parser/v2/DOMParser error due to missing XML parser JAR files. This has been fixed. In the formatter image, the xml.jar and xmlparserv2.jar files have been added to $ORACLE_HOME/lib, and the orai18n-collation.jar file has been added to $ORACLE_HOME/jlib.
33803343	BRM 12.0 introduced functionality that allowed accounts to be charged cycle fees when they were inactive or canceled. After upgrading from BRM 7.5 to BRM 12.0, cycle fees were applied to existing accounts that had inactive or canceled services. This has been fixed. A new business parameter (ApplyChargeOnInactiveOrCancelledProduct) controls whether to use the new functionality or keep the BRM 7.5 behavior.
33899544	After an account was written off, the payment reversal did not trigger a write-off or write-off reversal when the payment was made before the account write off. A write-off reversal was triggered for payment reversal only when the payment was made after the account write-off. This has been fixed. Payment reversals now perform a write-off reversal and then write off the remaining due.
33830067	The range in pin_flds was incorrect for some tax-related fields. The range from custom fields was getting applied to base fields. This has been fixed.
33860907	The /service object was NULL for account level-discounts. In this case, when setting end dates for a discount, BRM incorrectly picked up the root account. This has been fixed. The correct /account object is updated now.
33910399	A NULL POID for a custom item was causing an error in the read_flds operation for the item. This has been fixed. NULL checks were added to allow read_flds only when a valid item POID is available.
33589197	During rerating, new rerated events were not generated because the product was configured to not charge after cancellation (which is the default option). To fix this issue, the offer's default configuration has been changed to Never stop charging. This allows new events to be created and balances to be correctly populated during rerating.
33935382	For resource buckets with in-advance billing, the validity of the resource bucket was inaccurate when the billing DOM was changed. This has been fixed so that validity dates are consistent even when the billing DOM is changed for a bucket with in-advance billing.
33910398	There was a requirement for charges to be applied to customers even when their service was inactive. A new business parameter, ApplyChargeOnInactiveOrCancelProduct, has been added so customers can decide whether to charge an inactive service or not.
33966621	Plan transitions were core dumping when external system operations resulted in an error during a custom call. This has been fixed by stopping the flist data from being destroyed.
33945645	When timestamp rounding was enabled, setting discount end dates was rounding the dates to midnight. This has been fixed.
33709249	Opening the Canceled Product tab in the Customized Plan table was resulting in a signal 11 error. This occurred because a NULL source string was copied to the destination string. This has been fixed. A NULL check was added to validate whether the source string is NULL. If NULL, the string copy function is not initiated.
33870612	The pin_rel utility generated an ORA-20003 error when dealing with sub-balance impacts with a 0 amount. This has been fixed.
33626806	An incorrect credit profile was being set for grants of daily bundles. This has been fixed. By default, the RE Loader procedure now sets the balance group's credit profile to 0 for currency resources and to 2 for non-currency resources.
33611926	While running the pin_ledger_report utility in -export mode, the default GL procedure was trying to insert duplicate rows in the LEDGER_REPORT_ACCTS_T table, resulting in a unique constraint violation error. This has been fixed. A new flist is used to create incremental objects.
33996955	Paymentech Data Manager (dm_fusa) was logging high watermark memory issues for large batches due to qm_shmsize's maximum limit of 512 MB. To fix this, the maximum limit of qm_shmsize was increased to 1024 MB.
33968093	When there was no change in the usage event price, after rerating, tax charges were backed out but not reapplied for that event. This has been fixed.
33935381	After rerating, rollovers were incorrect because a new rollover event was not getting created when delayed billing was enabled. This has been fixed.
33705198	The pin_deposit utility was creating additional checkpoints even though a checkpoint already existed. This has been fixed.
33705205	An issue occurred during discount cancellation when PDC was configured to prorate charges and discounts upon cancellation. Discounts were canceled but the /purchased_discount object's PIN_FLD_CYCLE_END_T field was set incorrectly. This has been fixed.
33390957	Due to credit limit checking, rerating failed when publishing backout events. This has been fixed. Credit limit checks are now ignored for backout events during rerating.
33206140	The Java API XMLToFlist and BRMXMLToFlist classes were converting the string "dummy" to an empty string. This has been fixed.
33560838	An incorrect value was added to the /item object's PIN_FLD_AR_ITEM_OBJ field when the DeferredTaxJournaling business parameter was set to 2 (enabled). This has been fixed.
33752787	The PCM_OP_CUST_COMMIT_CUSTOMER opcode was resulting in a signal 11 error during account creation. This has been fixed.
33694272	When External Manager (EM) Gateway was restarted, the prepare phase of JCA Adapter was resulting in an exception. This has been fixed. A flag was added to the handleException method to ensure that the transaction status is not changed during the transaction prepare state.
33860010	Unused variable warnings were noted during code compilation. This has been fixed by removing all variables that were declared but not utilized in the code.
33637310	Bill units that were eligible for collections were not entering the collections process. This has been fixed. The search template was modified for custom profiles used for validation of scenarios in the fm_collections_pol module.
33852732	During the event adjustment process, the tax exemption amount was double the desired amount. This occurred because the exemption was not handled correctly, resulting in an overflow of values. This has been fixed.
30215740	Fortify issues were found in fix_data_dictionary.sql and create_amt_mv_pkb.sql. This has been fixed.

Customer-Reported Fixes in BRM 12.0 Patch Set 5

Table 1-4 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 5.

Table 1-4 Customer-Reported Fixes for BRM 12.0 Patch Set 5

Bug Number	Description
33275372	During billing, the call to the update_transfer_event stored procedure was failing due to the length of event_poid_list, which had a variable size of 4000 but a database size of 32000. This has been fixed. The variable size has been updated to 32000.
33249053	The Java PCM returned an ERR_NO_SOCKET error when getting the output stream from the socket or when the socket channel received an IOException. ERR_NO_SOCKET was not being considered for reestablishing the socket connection. This has been fixed by introducing a STREAM_IO exception so that reconnect attempts will be done on the socket.
32992056	There were synchronization issues when the Java PCM connection pool was accessed by multiple concurrent threads. This has been fixed.
32788794	Files required for building the BRM Web Services Manager Docker image were not shipped with the BRM cloud native Dockerfiles package. This has been fixed. The required files are now included with the package.
33424947	The service monitor was getting created and pushed to Prometheus, resulting in an error. The has been fixed. The PodMonitor and ServiceMonitor will be created only when both Prometheus Operator is deployed and the corresponding BRM service is enabled.
33124301	Bill Now was not refunding discounts for cycle forward arrears products. When Bill Now was run, the charges were prorated when the apply_cycle_fees_for_bill_now business parameter was enabled. This has been fixed to pick the discount event for refund mode.
33296584	During billing, applying cycle forward charges failed when fetching rate plans. This has been fixed. Changes were done to skip fetching rate plans, which are not found in the database during billing.
33189662	When ECE granted noncurrency balances on first usage through a purchase event, the validity date of the granted balance was not timestamp rounded. For the same noncurrency balance, if consumption occurred on the same day through a purchase event, the validity dates were timestamp rounded. This caused a new bucket to be created rather than using the granted balance through first usage. This has been fixed. No timestamp rounding is done when consumption happens through a purchase event. The existing granted bucket resource will be used for the consumption instead of creating a new one.
33126712	When a recurring or one-time product was purchased with an end date, the sub_bal_validity end time of grants was being set as NEVER. This has been fixed. Now, the resource validity aligns to the product validity after enabling the business parameter RestrictResourceValidityToOffer under bus_params_multi_bal.xml.
33288689	After removal of the Xerces dependency, the JARs and CLASSPATH were not updated in BRM cloud native. This has been fixed. The XSLT engine parameter in the Infranet.properties file has been updated, and the Xerces JAR is removed from CLASSPATH.
33177179	If a product is configured with "stop charging only when cancelled", products were not being charged on service inactivation. This has been fixed. now and the product will be charges event after service inactivation
33198841	Only cycle arrears monthly events were being skipped during the cancellation of a product if it was already charged. This has been fixed.
32698080	A memory leak was reported in different FM components. This has been fixed.
32974824	There were performance issues reported with invoicing. When PIN_FLD_GL_ID was not found in PIN_FLD_INVOICE_DATE (which is called for each event), a new context was opened for each event in PCM_OP_INV_DECODE_INVOICE_DATA. This caused PIN_ERR_DM_CONNECT_FAILED and an error to be reported intermittently. This has been fixed. PCM_OP_ACT_POL_SPEC_EVENT_CACHE adds a default value for PIN_FLD_GL_ID if it is not passed in. If PIN_FLD_GL_ID is missing, one context is opened per invoice instead of per event.
33124299	Cycle_forward_arrear events were being assigned to the wrong items during the discounting flow. This has been fixed.
33126650	If fixed discounts that were not dependent on the product charge were configured, during product cancellation, corresponding discounts were getting refunded even though the product refund was zero. To fix this, use the new apply_discount_on_zero_charge business parameter. If this business parameter is disabled, discounting will not be called when the product scale after rating is zero.
33194360	When /event/billing/refund/cc was generated for failed payments, the PIN_FLD_ITEM_OBJ field was not being set. This caused the item object to not be selected. This has been fixed now to set the POID of PIN_FLD_ITEM_OBJ in /event/billing/refund/cc.
33036300	When the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode was called to modify a product before the product was activated and before a purchase fee was applied, the PIN_PROD_PURCHASE_CHARGED flag was set. This resulted in the purchase fee being skipped when the product was activated. This has been fixed by modifying the code to set PIN_PROD_PURCHASE_CHARGED only if the purchase fee is applied.
33008857	The Oracle DM was crashing when the PCM_OP_DELETE_FLDS opcode was called with PCM_OPFLG_LOCK_NONE. This has been fixed.
29283875	The BRM documentation mentioned that PCM_OP_SUBSCRIPTION_PURCHASE_PRODUCT takes absolute time for PIN_FLD_START_T and PIN_FLD_END_T. This implied that the date was an absolute date even though the input was always considered as relative to epoch time in terms of seconds. The documentation has been fixed to reflect the correct behavior.
32631247	The PCM_OP_COLLECTIONS_REPLACE_SCENARIO opcode was not canceling actions when called from custom code. This has been fixed.
32774746	The following opcodes were added to BRM Web Services and OracleBRMJCA15Adapter: PCM_OP_CUST_FIND_PROFILE PCM_OP_CUST_SET_TAXINFO PCM_OP_CUST_SET_BAL_GRP PCM_OP_CUST_CHANGE_BUSINESS_PROFILE
33380517	PCM_OP_CUST_DELETE_ACCT was deleting the /user_activity object. This has been fixed.
33321834	If the pcm_timeout_in_msecs parameter was set in the CM pin.conf file, the CM was not coming up. This has been fixed.
33510634	A memory leak was reported during a call to the PCM_OP_SUBSCRIPTION_CANCEL_PRODUCT opcode. This has been fixed.
33177178	The PIN_FLD_EVENT_POID_LIST data type was being changed to CLOB, and the DISTINCT search query was not accepting the CLOB data type. This has been fixed. The query was modified to a normal search query because POIDs in the item_t table are unique and duplicates are not possible.
33076623	When a refund was reversed, an /event/billing/refund/reversal event was generated without any balance impact. This has been fixed.
32554355	UEL considered any events with zero RUM quantity to be errors. This has been fixed. To suppress errors on ZERO_QUANTITY rating, enable the infranet.uel.ignore_zero_quantity_rating_status parameter in the Infranet.properties file.
33214373	Unexpected results occurred when rerating two accounts that were in a sharing group. This has been fixed. A new u option was added for rerating accounts in the sharing group properly.
33126690	Directly calling the PCM_OP_PRICE_SET_PRICE_LIST opcode failed when the discount trigger code or the discount rule code was longer than 10 characters. This has been fixed by extending the size of V_DSC_TRGR_CODE VARCHAR2 and V_DSC_RULE_CODE VARCHAR2 from 10 to 255 characters.
33184937	When UEL was checking for PIN_FLD_RATING_STATUS, the PCM_OP_ACT_USAGE opcode returned this field in all successful cases, resulting in failure. This has been fixed. UEL now ignores the PIN_FLD_RATING_STATUS output from PCM_OP_ACT_USAGE.
33076624	Some prepaid account balances were not synched from ECE to BRM. This has been fixed. An MTA application corrects the data in BRM by comparing its balances with the balances in ECE.
33314948	Transferring a service from one bill unit to another was failing in some cases because the flist was not initialized. Reading this flist data resulted in an error because it was pointing to an unknown memory location. This has been fixed.
33490938	The generate_hash function was throwing a “wallet does not contain the key” error because it couldn’t find ORACLE.CGBU.BRM.INVOICE_KEY. This has been fixed. A condition has been added to pin_config_editor to update the invoice key.

Customer-Reported Fixes in BRM 12.0 Patch Set 4

Table 1-5 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 4.

Table 1-5 Customer-Reported Fixes for BRM 12.0 Patch Set 4

Bug	Description
31937598	When the PCM_OP_BULK_WRITE_FLDS opcode was invoked to change an alias, the call failed with a PIN_ERR_STORAGE error. The opcode was locking balance groups and retrieving too much data, which caused excessive memory consumption. This has been fixed.
31890124	When performing a full adjustment on an event including multiple tax balance impacts with negative tax amounts, the output tax jurisdiction was being calculated incorrectly. This has been fixed.
32023845	In Customer Center, loading a large number of events in the Event Browser was taking a long time. This was because the step size for the search was limited to 10 and time zone details were being read one at a time while retrieving individual records. This has been fixed. Now: The step size is 500 by default, and you can change it in the CustomerCenter.properties file. Time zone details are retrieved as part of the search rather than read individually.
32434963	In Billing Care, the history page for batch payments was displaying the same result multiple times. This has been fixed.
32039813	Creating an account with a package containing an account-level bundle was failing. This has been fixed.
31180010	In Payment Center, deleted suspended payments are displayed by default. You can now choose to hide deleted suspended payments by setting the paymentsearch.showremoved property in paymentcenter.properties to false.
32078942	In Billing Care, when raising an event dispute with an amount greater than 1000, the reason codes list of values were not loading. This has been fixed.
31452531	In Billing Care, searching for a specific bill for a specific account was taking a long time. This was because the search was retrieving all accounts rather than just the specified account. This has been fixed.
31037692	In Billing Care, processing a batch payment file was taking a long time and the page was not refreshing. This has been fixed.
32052513	In Billing Care, navigation was very slow and the default search was taking a long time to load the results. This has been fixed.
30528415	In Billing Care, you could not select a batch payment template due to a missing custom payment type schema. This has been fixed. Billing Care now generates a schema for the custom payment object that uses the default /payinfo object and events.
32607344	Rated Event Loader was not deleting TMP_PROF tables for files that initially failed to load with an UPDATE_ERROR, but were subsequently successfully loaded. This has been fixed.
32258047	Daily batch jobs, such as trial billing and billing, were resulting in frequent core dumps. This has been fixed.
32687843	Synchronizing users with DM_LDAP was failing because the PIN_FLD_DN returned by PCM_OP_SEARCH was incomplete. The service that copied the DN internally had the wrong destination buffer size. This has been fixed.
32983797	The load_config utility was loading empty balance element names as empty when they contained special characters. This has been fixed. The utility now accepts UTF-8 encoded special characters in the value field of the input XML file.
32483033	The load_pin_customer_segment utility skipped customer segment descriptions that contained Latin Bosnian characters, so that the customer segment entry created in /config/customer_segment had no description. This has been fixed. The utility now accepts UTF-8 encoded special characters in the value field of the input XML file.
31155909	Exporting invoices with a large number of events (more than 2000) was failing. This has been fixed. The maximum string length allowed has been increased to 32000.
32124017	Universal Event Loader was failing frequently with an invalid_conf error when infranet.connection was configured in Oracle Wallet. This has been fixed.
32832165	The database was using multiple execution plans instead of a single shared one. This was because the batch controller was using literals. This has been fixed. Now searches for overdue and failed batch controller use bind variables.
31037694	Some of the values in the eai_js and batch controller Infranet.properties files did not support environment variables. This has been fixed. Now the InfranetUtil.substituteEnvVariable() utility function replaces the environment variable with its value for any configuration parameters using an environment variable.
31577118	Converting a large XML payload containing custom fields to BRM flist format using the XmlToFlist Java API was taking too long. This has been fixed.
32372260	When processing multiple opcodes as part of the same XA transaction, if JCA Adapter received unexpected XA_END messages before XA_PREPARE and XA_COMMIT messages, the XA transaction ID was disassociated and could not be retrieved when the XA_PREPARE and XA_COMMIT messages arrived. This caused the opcodes to fail. This has been fixed. The transaction ID is only disassociated when JCA Adapter receives an XA_END message if the transaction is not ongoing.
31972993	While running many web services in parallel, the Data Manager (DM) that handles Connection Manager (CM) clients was not matching external correlation IDs to the correct web services. This has been fixed.
31224153	When the CM was refreshing /config objects, child CM processes were stuck in a thread mutex lock, causing application clients like pin_bill_accts to stop responding. This was because the refresh thread was opening a new context with every refresh. This has been fixed. Now the same initially-opened context is re-used in every refresh.
31851731	When ConfigCacheRefreshInterval was set to a non-zero value and a configuration was updated while updating the business parameters, CM was unresponsive when it tries to update the cache after the specified interval. This has been fixed.
30318315	The PCM_OP_TRANS_POL_COMMIT and PCM_OP_TRANS_POL_ABORT opcodes were receiving a NULL input flist, so any subsequent opcodes could not perform customizations. This has been fixed. The input flist for these opcodes now matches that of PCM_OP_TRANS_OPEN.
32333625	The pin_ctl stop all command was not stopping with a Can't create semaphore file error because the registry path was incorrectly set. This has been fixed.
32146320	The pin_rel utility was first checking for database connection data from Oracle Wallet, then if it wasn't there, checking Infranet.properties. This was the opposite of the intended behavior. This has been fixed. The utility now checks Infranet.properties first, then Oracle Wallet.
32823431	When running billing for accounts with a /billinfo status of 10103, the BILLING_UPDATES procedure generated an error due to an invalid pointer reference that populated PIN_FLD_NAME incorrectly in input flist. This has been fixed.
32451031	When using Bill Now between regular cycles, for any pre-created items, charges were not being tagged to the correct bill item. This has been fixed.
32088651	Some of the BRM policy opcode files were failing Fortify vulnerability scans and were incorrectly being reported as risks. This has been fixed.
31111615	Correlation IDs are were stored in HashMap for the life time of Java processes, which occupied significant memory for long-running programs. This has been fixed. Now the correlation IDs are stored in a ThreadLocal variable, which allows them to be cleared as part of the thread exit. Correlation IDs now also store incremental numbers for salt values instead of 0.
31030685	Vulnerabilities were reported in BRM code when running Fortify scan static source analyzer. This has been fixed.
31589840	In BRM Cloud Native deployments, the following of the subscriber state configuration files were missing from Connection Manager pod: config_lifecycle_states.xsd config_lifecycle_states.xsl config_service_state_map.xsd This has been fixed.
31701623	During sequential discounting, discounts were being calculated incorrectly when they were closed and then purchased again. This has been fixed.
30771215	While configuring high availability for the connection between dm_oracle and RAC, after service relocation dm_oracle was being reconnected to a new instance with a double number of sessions. This has been fixed.
31029474	There was excessive logging in dm_oracle.log when debug logging was disabled, due to unconditional logging being set for stored procedures. This has been fixed.
31785123	Creating a relationship between two accounts was resulting in the following error: `PIN_ERR_UNKNOWN_EXCEPTION: force due_t = bulk_write_flds problem` This has been fixed. Now the error buffer in dm_oracle is cleared when a balance lock query returns no rows to the PCM_OP_BULK_WRITE_FLDS or PCM_OP_BULK_DELETE_OBJ opcodes.
31500865	When a while card (%) was used in PCM_OP_SEARCH, the opcode was returning a BAD_ARG error and extra conditions were added in the where clause for the partitioned classes. This has been fixed.
31939059	Running pin_crypt_upgrade_keys for a second time re-encrypts already upgraded data keys in the cryptkey_t table. This has been fixed. Now, a new upgraded column in cryptkey_t indicates if the keys have been upgraded, and pin_crypt_upgrade_keys upgrades only the keys with 0 in the upgraded column. dm_oracle inserts the value in the upgraded column when new cryptkey_t records are inserted.
31486823	pin_crypt_app did not support -update_dm_conf and -update_fusa_conf for AES encryption. This has been fixed.
30756021	The Infranet.properties files for the UEL and EAI JS processes did not accept environment variables. This has been fixed. For example, you can use `infranet.log.file=${custom_tracing_logdir}/test.log` in Infranet.properties, and the custom_tracing_logdir environment variable will be used to locate the log file.
31420362	The Infranet.properties files for the Rated Event Loader processes did not accept environment variables. This has been fixed. For example, you can use `infranet.log.file=${custom_tracing_logdir}/test.log` in Infranet.properties, and the custom_tracing_logdir environment variable will be used to locate the log file.
30891415	In the BRM 12.0 Patch Set 2 SDK package, the fm_bill_pol_pre_fold.c: file, which is no longer used, caused compilation errors. The file has been removed from packaging and installation.
31974952	Running Valgrind against BRM 12.0 Patch Set 3 generated Invalid Read errors due to a memory issue. This has been fixed.
31372474	When running pin_deferred_act, a MTA application that invokes PCM_OP_ACT_SCHEDULE_EXECUTE to run scheduled actions was not reporting error details when the opcode failed. This has been fixed.
31811046	When running pin_deferred_act with the verbose parameter, a MTA application was displaying the wrong number in the error record count. This has been fixed. The MTA framework now does not increase the error count when the exit flag is set due to the maximum number of errors being reached.
32029981	Communication performance issues were occurring with local Unix ports between CM and DM. This has been fixed by disabling SSL hostname verification in the SSL handshake for AF_UNIX domain and the local UNIX port setup.
32779799	Syntax issues in the PL/SQL package declaration were occurring due to CREATE OR REPLACE PACKAGE BODY pin_get_fields database calls. This has been fixed.
32929448	When a SQL session's NLS_DATE_LANGUAGE parameter is set with any European language other than American English, the Date_to_Poid() function of the partition_utils SQL script fails. This has been fixed by replacing the date format in to_date() function from "English 01-JAN-1970" to "01011970".
32550611	In ECE, if auditing is disabled for /service fields, because ECE reads /au_service when restarting processes, ECE fails to start up. This has been is fixed by enabling audit as default for the following fields: /service: LOGIN ALIAS_LIST ALIAS_LIST.NAME /account: ACCOUNT_NO
31864990	In BRM High Availability configuration, running threads were hanging when a host was down. This has been fixed with a connect timeout setting.
32618809	In Billing Care, validity dates appear incorrectly. Instead of displaying the valid to end date, the current date was shown as default. This has been fixed.
32230733	In Billing Care, on large databases, the assets page and services were not loading due to Billing Care retrieving all /schedule objects. This has been fixed. The query now only retrieve the selected /schedule objects.
31082441	In Billing Care, you can now add additional attributes to application cookies by using SDK configurations. For example, to add a new attribute, samesite, to the application-level cookies, you use the Billing Care SDK to add it as a value for the appCookieAttribute configuration key in CustomConfigurations.xml: <keyvals> <key>appCookieAttribute</key> <value>samesite=none; secure;</value> <desc>Semicolon seperated attributes to be added to all applicationcookies</desc> </keyvals> This key indicates that third party cookies are allowed on a secure channel.
32668401	By default, for payment failures, the BRM refund process merges refund items into one. This has been fixed. Refund items are not merged when the payment status is available and the value is failed.
32453170	When processing writeoffs, PCM_OP_AR_BILLINFO_WRITEOFF included overpayment and unallocated credit adjustments. This has been fixed. These are no longer included.
32955726	When processing a top-up, the BILL_DEBIT operation was making a credit limit check and the Connection Manager was throwing a ERR_CREDIT_LIMIT_EXCEEDED error. For top-ups, ECE does a credit limit check, so the check from BILL_DEBIT was a duplicate. This has been fixed. BILL_DEBIT no longer makes credit limit checks for top-ups from ECE.
32501964	If there is no THRESHOLDS field in the input flist for the PCM_OP_BILL_SET_LIMIT_AND_CR opcode, BRM adds the PIN_FLD_CREDIT_THRESHOLDS_FIXED field and calculates the value from existing values from other fields in the database, like PIN_FLD_CREDIT_LIMIT and PIN_FLD_CREDIT_FLOOR. Now you can use the PIN_FLD_FLAGS field in the PCM_OP_BILL_SET_LIMIT_AND_CR input flist to configure whether BRM uses the existing values from the database or sets PIN_FLD_CREDIT_THRESHOLDS_FIXED to NULL. To set it to NULL when no THRESHOLD field is sent, set PIN_FLD_FLAGS to 0x01. To use existing database values, do not set PIN_FLD_FLAGS.
32668400	In Business Operations Center, running PIN_STATE_CHANGE as a custom job fails with an incorrect parameters error. Business Operations Center did not support running PIN_STATE_CHANGE. This has been fixed.
32298772	In Customer Center, successfully run deferred collections actions were not displayed. This was because the corresponding /schedule objects were being deleted after successful completion of the pin_collections utility. This has been fixed. Now rather than deleting the /schedule objects, their status is updated and they are displayed in Customer Center.
32484030	The PCM_OP_COLLECTIONS_ADD_ACTION opcode was not performing customizations. This was because the opcode's process flow did not include the PCM_OP_COLLECTIONS_POL_CALC_DUE_DATE policy opcode. This has been fixed.
32416993	Suspend and terminate actions performed by the PIN_COLLECTIONS_PROCESS utility were failing with an `ERR_NOT_FOUND` error. This was because the action to close a service in a /billinfo was attempting to delete a field that was not present in the input flist. This has been fixed. The utility now checks that the field is present before processing the deletion.
32680325	Adding multiple subordinates to an account in multiple threads was taking a long time. This was because the INC_FLDS operation was running against the PIN_FLD_PARENT_FLAGS field of the parent account's /billinfo object. This has been fixed. The value of PIN_FLD_PARENT_FLAGS is no longer incremented with each subordinate. Now the value can be either 1 (if the account has subordinates) or 0 (if the account has no subordinates).
32812435	The PCM_OP_SUBSCRIPTION_PURCHASE_FEES opcode was resulting in a deadlock error. This was because item-type products were being cleaned up improperly. This has been fixed.
32950646	Exporting G/L reports into file with the pin_ledger_report utility was taking a long time and causing memory issues and errors. This was because the utility was reading all reports into memory before processing. This has been fixed. The incremental report and XML file generation logic has been moved to the database, and data is fetched from the memory in steps. For example, fetch 10000 rows at a time and generate the G/L report XML file for the fetched data.
32992054	Invoice processing was failing when INVOICE_DATA stored in the /event table contained special characters like `<, >, \|`, even if a backslash was used as an escape character. This has been fixed. The PCM_OP_INV_DECODE_INVOICE_DATA opcode now escapes these characters.
31745265	When a payments input flist has a PIN_FLD_TYPE_STR field with a value of CTI, the BRM server and dm_fusa now send Card Type Indicator (CTI) / Product Card Type Indicator (PCTI) record to Paymentech or the Paymentech simulator. Paymentech and the Paymentech simulator include the same field in the output flist response.
30909463	The PIN_SEPA utility now generates XML files in accordance with the latest EPC schema versions (Rulebook v7) for sepa_dd and sepa_ct requests.
31756692	When a payments input flist has a PIN_FLD_TYPE_STR field with a value of CTI, the BRM server and dm_fusa now send Card Type Indicator (CTI) / Product Card Type Indicator (PCTI) record to Paymentech or the Paymentech simulator. Paymentech and the Paymentech simulator include the same field in the output flist response.
32915574	The PIN_RECOVER utility now passes PIN_FLD_ACH and PIN_FLD_CHANNEL_ID to payment recovery so that payment items are populated with the proper values.
32680327	When the PCM_OP_PRICE_SET_PRICE_LIST opcode was updating /data/price_list_changed objects, row lock contention was occurring. This has been fixed. The /data/price_list_changed update now happens at the end of the transaction to decrease the lock interval.
32146557	While publishing a price plan modify event, multilevel rate plan selectors are now handled properly to add rate plans during the event publication.
31582718	BRM no longer requires a CM restart when adding a new balance element ID (BEID) in a PDC-enabled or non-PDC enabled environment. The default PDC check has been removed from the /config/beid refresh process flow.
32366586	When using multiple rate plan selectors, the rerating process was failing for cycle_event. This was because by incorrect event details were being sent to fetch the rate plan required to rate the event. This has been fixed. Now only required event details are sent for rating.
31831938	When a payments input flist has a PIN_FLD_TYPE_STR field with a value of CTI, the BRM server and dm_fusa now send Card Type Indicator (CTI) / Product Card Type Indicator (PCTI) record to Paymentech or the Paymentech simulator. Paymentech and the Paymentech simulator include the same field in the output flist response.
32554792	The OP_RATE_GET_PRODUCT opcode was crashing with a Signal 11 error at fm_rate_cache_clean_product_data. This was because audit data was not being handled properly for some scenarios when cleaning rate plans. This has been fixed.
33030795	During rerating, multiple item_obj_id0 were created for usage events. This was because incorrect item object references were used at the event level when creating new item objects. This has been fixed.
32779665	Balances in ECE were incorrectly updated after rerating due to events published to ECE having the improper balance group revision values. This has been fixed. Now the adjustment events are published after the balance group revisions are updated.
32402233	When OP_SUBSCRIPTION_TRANSITION_PLAN is called twice within the same transaction, all products purchased within the two calls were given the same value for PIN_FLD_PACKAGE_ID field. This has been fixed. The package_id transaction cache is now refreshed at the end of plan_transition to ensure a new package_id is assigned for the next call.
32718280	The RestrictResourceValidityToOffer business parameter restricts resource validity end time to the end time of the product during first usage. This behavior has been extended to be applicable against purchased products with a set end date so that the corresponding sub_bal_validity end time for grants is set to the product end date.
32434961	After a service transfer, any operations that have rounded event times (like deferred purchase, set_prodinfo, discount purchase or cancellation) failed to fetch the appropriate /balance_group. This was because the times were rounded to time values before the actual transfer time value. This has been fixed.
32381048	When canceling full discounts in previous cycles, purchase_end_t was not being set and the cancellation event was not generated. Instead, the end date was set to actg_next_t and the discount modify event was generated, as is the expected behavior for discounts being canceled in current or future cycles. This has been fixed. If discount_end is less than now_t, the full discount is canceled.
32078939	Sub-balance validity was not set while setting set_prodinfo. Discount cancellation was not the using the PIN_RATE_FLG_CUT flag passed in input. This has been fixed. The CANCEL_DISCOUNT, SET_DISCOUNTINFO, and SET_DISCOUNT_STATUS opcodes and the pin_discount_cleanup utility accept the PIN_RATE_FLG_CUT and -rate_flag_cut flags and set the sub-balance bucket validity end dates.
32146555	If the dates in /au_billinfo were incorrect, PCM_OP_SUBSCRIPTION_GET_ACTG_DATES was going in an infinite loop. This has been fixed. An error now appears if the dates in /au_billinfo are wrong.
32950651	The PCM_OP_CUST_SET_BILLINFO opcode was taking a long time to change an attribute in a parent's /billinfo. This was because a recursive call was made to all subordinate /billinfo objects, regardless of whether changes were made in the subordinate. This has been fixed. If there are no changed fields in the subordinates, the recursive call is skipped.
32846749	When discount with a set end date is purchased and backdated to previous accounting cycle after running billing, the discount validation fails and the discount is not considered for refunds. This has been fixed.
32751700	In the dm_vertex output flist, when setting the value of the PIN_FLD_RESULT field, the LocSetNameCriteria function call to Vertex STQ was returning a value in a variable that was used to take decision about pass or fail of jurisdiction validation. This has been fixed.
31811039	When an adjustment is done on a bill, its corrective bill and invoice should be generated immediately to avoid inconsistencies in the invoice. Generating a corrective bill and invoice after the next regular bill was causing the adjustment to appear in the regular bill and the corrective invoice. This has been fixed. Now you can choose to drop adjustment items from an invoice if they are allocated to other bills, like corrective bills, by setting the ARItemsInCorrectiveInvoice parameter in the bus_params_Invoicing.xml file. Setting this parameter will only show the adjustment item on the corrective bill.
30996236	Noncurrency event adjustment is not happening when the event has non-zero discount balance impact and zero amount charge balance impact. This has been fixed. Noncurrency discount balance impacts are now processed even if the event is not a discount-only event.
31356891	For most A/R action validation errors, the ebufp error buffer was not filled, but a description field was set with the error message in the return flist. This has been fixed. Now you can set the value of PIN_AR_SET_EBUF_ON_ERROR to 0x20 for A/R actions so that validation errors appear in the error buffer.
31831937	/item/payment were being dropped in next regular invoice when Accounts Receivable (AR) items in corrective invoices was enabled. This has been fixed. Only adjustment items allocated to other bills are dropped during corrective invoice generation.
32015905	Errors were being logged by the Connection Manager at PIN_ERR_LEVEL_ERROR instead of PIN_ERR_LEVEL_DEBUG. This has been fixed.
32175575	During wholesale billing, billing of parent account fails as virtual column was not handled. This has been fixed.
32095034	Memory leaks were observed in fm_bill_reverse.c and fm_pymt_item_search.c. This has been fixed.
31103984	pin_collections_process was having performance issue. This was because some SQL search statements were using literals instead of bind variables. This has been fixed.
31043161	The CMT Infranet.properties file did not accept environment variables. This has been fixed.
31074575	When loading a custom XML with pin_cmt, the RefObj of type billinfo was giving an incorrect POID. This has been fixed. The proper /billinfo POID is selected from the cmt_reference_t table.
32019959	The PCM_OP_PRICE_COMMIT_DISCOUNT opcode was creating hash tables for all discounts in the database, which would take longer the more discounts were in database. This has been fixed. You can now optionally disable hashing for discounts.
32058272	If no AAC_ACCESS information was passed in the input flists, the PCM_OP_CUST_MODIFY_CUSTOMER and PCM_OP_CUST_COMMIT_CUSTOMER opcodes copied it from PIN_FLD_ACCTINFO. This has been fixed. You can now pass AAC information in the PIN_FLD_SERVICES field. This lets you map the AAC_ACCESS field to populate the extended attributes field for ProductImpl in the ECE Customer Cache. If there are no AAC fields in PIN_FLD_SERVICES, the values in PIN_FLD_ACCTINFO are used instead.
32008567	When committing discounts, a row lock contention occurred on the IFW_DISCOUNTMASTER table. This was because the set_discount_master procedure was trying update the database table even when the discount master name value in the database and input was NULL. This has been fixed.
31366932	Unlike other standard database tables, such as POID_TYPE or PROFILE_BILLING_INFO_T, you could not create indexes for ACCOUNT_EXEMPTIONS_T to improve query performance. This has been fixed. You can now create indexes for ACCOUNT_EXEMPTIONS_T.
32105392	When performing a top-up for an active service with the PCM_OP_BILL_DEBIT opcode and when a service state moved from RECHARGE to ACTIVE, the service expiration date was not being extended. This has been fixed.
31791924	After upgrading BRM 7.5 PS16 to 7.5 PS23, the invoicing process was producing an error due to an issue in dm_oracle. dm_oracle was crashing at op_search_and_bulk_act due to a non-exisent class being passed in the input flist. This has been fixed.
31881022	Generating reports using pin_ledger_report in export mode causing memory issues. This was because the utility was reading the detailed report into memory even if it was not being used to generate the XML report. This has been fixed. Now the utility reads the detailed report only when generating the XML report.
31880134	Generating incremental reports using pin_ledger_report in export mode causing memory issues. This was because the utility was reading the detailed report from the database in a flist, then reading the previous report in the flist, and comparing them to generate the new incremental flist. This has been fixed. Now the incremental report generation logic is handled by the database. To implement this fix, after applying the patch, load one of the following files from the patch into the database, depending on your database character-set configuration: create_procedures_UTF8.plb create_procedures_AL32UTF8.plb
31826416	After upgrading from BRM 7.5 Patch Set 21 to Patch Set 23, the pin_inv_doc_gen utility for email was not updating invoice_status to 1. This has been fixed. For pin_inv_doc_gen, the OUTPUT_NAME field in the burst query now contains BILL_NO as a substring.
31060274	The dm_fusa data manager was crashing when the MT record in the response was not handled. This has been fixed. Now dm_fusa interprets MT records only if they are received. The simulator also simulates this scenario.
31024364	The the pin_mass_refund utility was failing with a `PIN_ERR_DEADLOCK` error. This was because the utility was locking balance groups with the PCM_OP_BILL_ITEM_REFUND opcode and accounts with the PCM_OP_BILL_ITEM_TRANSFER. This has been fixed. Now the accounts are also locked by PCM_OP_BILL_ITEM_REFUND and the balance groups are all locked in order.
31948875	Generic searches for /event/billing/charge/% events were failing. This was because the PIN_FLD_TRANSACTIONS field was being read in all searches, but this field only applies to /event/billing/charge/cc events, so any search results that were not /event/billing/charge/cc events failed. This has been fixed. Now PIN_FLD_TRANSACTIONS is read for /event/billing/charge/cc events only.
31143570	When the CM_OP_PYMT_COLLECT opcode was called by a custom wrapper opcode to create a customer, authorization was failing with a Signal 11 error, with a possible reason as a memory leak. The Connection Manager for fm_pymt_pol_apply_fee_parse_customer_segment was crashing. This has been fixed.
31634436	While creating a customer with a SEPA payment mode, IBAN validation was failing even for valid IBAN values. This has been fixed. IBAN validation is now performed according to ISO standards.
31757793	For SEPA payment types, banks were rejecting SDD files for transactions with zero charges. This has been fixed. Now SDD requests are suppressed when the amount is zero.
32146559	When committing discounts, if the discount trigger and master were reused, row lock occurred on the IFW_DISCOUNTMASTER table. This has been fixed.
32164299	When committing discounts with the PCM_OP_PRICE_COMMIT_DISCOUNT opcode, row lock contention was occurring on the DATA_T table. This was because the commit was occurring during long-running open transactions. This has been fixed. Now the commit is deferred until the transaction is committed.
30944081	A sponsored account was unable to rate traffic when its own sub-balance was positive. Rating was not adhering to the configured credit limit. This was because of an error in the credit limit check when charge offers had an impact on both the sponsored account and the owning account. This has been fixed. The credit limit is no longer checked on an account's sponsored balances.
31643234	The data auditing and rating processes were behaving inconsistently. This was because BRM was not publishing updated effective_t of products to ECE during the set_prodinfo flow. This has been fixed.
31960547	The wrong tax was applied on discount purchases. This was because the PIN_RATE_BAL_FLG_TAXABLE_OVERRIDDEN field was being set to the wrong value, and the amount_deferred for the discount impact was always being reset to zero, regardless of the value for the field. This has been fixed.
30963854	When rerating an already rerated account after running billing, the impact_type was not populating correctly for backout events generated after rerating after running billing. This has been fixed. The discount impact type is now reset during rerating.
31456478	The balance group ID and customer ID in ECE were mismatched. This was because the cookie used while fetching each balance group was corrupt. This has been fixed.
31218440	After the second rerating for a canceled product, the arrear_cycle event for last cycle was not generated. This has been fixed. The condition is now based on product status and events are generated for all cycles.
32112279	Rerating a conditional RUM impacted event was granting the conditional RUM balance impact again, but no debit occurred for the original conditional RUM balance impact. This was because the backout event was not being created, so balances were not updated properly. This has been fixed. During rerating, a backout event is now created when the session event's type is initiate or update.
31630568	During rerating, products were not returned based on priority. This has been fixed. Products are now returned in order from highest to lowest priority.
30883875	The PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode was creating triple reversals. This was because multiple refund events were being generated for same product if its end dates were set and then canceled in separate transactions. This has been fixed.
32212986	After a service transfer, while setting CYCLE_START_T, the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode was rounding the event_end_time to midnight before the transfer or cancellation time. This caused balances to be impacted on old balance group. This has been fixed. The transfer time is now used for event_end_t. Cancellation of cycle_arrears charges with zero scale was not being performed correctly. This was because the purchase, cycle, and usage end dates were not passed to apply_rate. This has been fixed.
31326055	Deleting a schedule object by calling the PCM_OP_ACT_SCHEDULE_DELETE opcode from custom code was taking a very long time. This was because the BAL_GRP_T table and the BRM root account were being locked. This has been fixed. Balance group locking is now skipped for root account objects.
31709680	Mismatched balances and issues applying taxes were occurring in bills. This was because discounts purchased in a delay period were being tagged to next bill, even if the original product charge event was tagged to current bill. This has been fixed.
31906427	In complex backdated order scenarios, discount claw back was not working properly when setting the end date of discount. This has been fixed.
30935307	With prorated discounts, discounts were counted inaccurately for the full cycle. This has been fixed. The proper end time is now read for canceled discounts. In sequential cycle flows for refunds, the PCM_OP_SUBSCRIPTION_CYCLE_FORWARD opcode is called with the modified end time so that it can provide appropriate refunds.
31884566	Discounts were not being applied if the purchased discount was backdated to the previous billing cycle. This has been fixed.
31384943	When backdating products with multiple rate tiers, discounts were being applied twice. This has been fixed.
31589007	In Subscription Management, enrichment from custom code in PCM_OP_CUST_POL_PREP_NAMEINFO was not being made for from some fields, such as PIN_FLD_EMAIL_ADDR and PIN_FLD_ZIP. The fields were still appearing as they were in the input flist of PCM_OP_CUST_CREATE_CUSTOMER, before customization. This has been fixed.
32324208	An incorrect refund was being created when purchasing a second instance of the same discount. This has been fixed.
31461126	Timestamps for services in STATE_EXPIRATION_T were not being rounded when the pin_state_change utility changed life cycle states, even when rounding was enabled. This has been fixed.
31797332	Transitioning plans with the PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was failing and the discount end dates were not being set properly. This has been fixed.
31510306	The product and discount purchase and cancellation events sent from BRM to ECE did not contain the exact POID revision, which caused ECE to work incorrectly. This has been fixed.
32078940	During service cancellation done on the same day as a service transfer, the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode was rounding end time, which caused invalid balance groups to be affected. This has been fixed. Rounding is no longer performed for cancellations.
32164301	During service cancellation done on the same day as a service transfer, the PCM_OP_SUBSCRIPTION_SET_PRODINFO, an error occurred when setting end dates for the product instance on the account receiving the transfer. This has been fixed.
32266270	Line-based taxes were being calculated incorrectly by dm_cvertex. This has been fixed.
31626614	When using a tax engine other than Vertex CTQ, you can use the following /config/business_params entry for billing: 0 PIN_FLD_PARAMS ARRAY [50] allocated 4, used 4 1 PIN_FLD_DESCR STR [0] "Specifies whether tax percentage should be added for zero tax amount. 0 - percentage is added for zero tax amount (default). 1 - do not add the percentage. The parameter is for cases where PIN_FLD_TAXPKG_TYPE = 0." 1 PIN_FLD_PARAM_NAME STR [0] "exclude_percent_for_zero_tax" 1 PIN_FLD_PARAM_TYPE INT [0] 1 1 PIN_FLD_PARAM_VALUE STR [0] "0" When the entry is enabled, PIN_FLD_TAXPKG_TYPE is set to 0, and the tax amount is 0, percentage will set to 0 in the PIN_FLD_BAL_IMPACTS field. The default behavior is to show percentage when the tax amount is 0.
31644822	During rating, BRM was using the first tax supplier on a purchase for all charge offers or products when a bundle contained multiple charge offers or a purchase contained multiple products, and the charge offers or products were assigned different tax suppliers. This has been fixed.
31757400	Zonemap values are case sensitive and we are supporting '#' as a valid character in a Zonemap string.
32246853	While performing a 100% event adjustment on a tier pricing charge event when there were multiple charge balance impacts, the discount was being applied multiple times. This has been fixed.
32595176	BRM was allowing a second request for full tax adjustment on an event that already had a full tax adjustment performed against it, without generating a proper error message. This generated and recorded a 0$ adjustment event in BRM. This has been fixed.
31690657	When contributor string was passed in the input flist of the PCM_OP_BILL_DEBIT opcode, a NULL value was set in the PIN_FLD_CONTRIBUTOR_STR field in the BAL_GRP_SUB_BALANCES_T table. This has been fixed. Now PCM_OP_BILL_DEBIT is checked for a contributor string, and the value of the string is used.
31168922	In Billing Care, opening a billing account with a large number of service accounts failed. This was because the data manager did not support a search query with more than 33 arguments. This has been fixed.
31859893	After performing BILL_NOW, the cycle tax was not adjusted for event level adjustments of a nonpaying child accounts. This was because the cycle tax event was generated for the parent account. This has been fixed. The BILL_NOW flow now checks the cycle tax on the parent account and considers whether the GenerateBillForChildBillnow parameter is enabled or disabled.
31445652	During product purchase, split charge packet range issues were causing errors in the discounting pipeline. This has been fixed.
32501968	After performing BILL_NOW, the cycle tax was not adjusted for event level adjustments of a nonpaying child accounts. This was because the cycle tax event was generated for the parent account. This has been fixed. The BILL_NOW flow now checks the cycle tax on the parent account and considers whether the GenerateBillForChildBillnow parameter is enabled or disabled.
32501970	After performing BILL_NOW, the cycle tax was not adjusted for event level adjustments of a nonpaying child accounts. This was because the cycle tax event was generated for the parent account. This has been fixed. The BILL_NOW flow now checks the cycle tax on the parent account and considers whether the GenerateBillForChildBillnow parameter is enabled or disabled.
31632773	The following Perl scripts were missing the use strict and use warnings Perl pragma compiler flags: partition_utils pin_bus_params pin_close_items pin_wsdl_generator This has been fixed.
32252778	The discounting pipeline was not starting after upgrade to BRM 12.0. This was because of a invalid index access of a string exception while processing a regular expression FSM. This has been fixed.
31356888	When a batch of events were submitted from Event Browser, the discounted events were being over-adjusted. This has been fixed.
31761529	The pin_deposit utility now considers existing checkpoints so that no more than one checkpoint is created.
31761429	Discounts are now considered while performing event-level accounts receivable actions.
31545961	Fixed plan transitions and their discount end dates are now set properly.
31660414	A check was added so that stored credential processing is not performed when the /payinfo object is not present.
31576857	The plan transition opcode was expecting certain fields even though they were optional. This has been fixed.
31595861	A check was added so that stored credential processing is not performed when the /payinfo object is not present.
31525930	When a charge is forced into a long cycle by the PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL policy opcode, the cycle is honored by merging the cycles into a long cycle depending on the flag value in output flist of the opcode.
31525906	The PIN_FLD_NAMEINFO field was deleted from any event (except /event/customer/nameinfo) before it was recorded in the BRM database. This has been fixed.
31505709	The Connection Manager (CM) no longer encounters errors when the ConfigCacheRefreshInterval parameter is set to a non-zero value.
31494552	The PIN_FLD_NAMEINFO field returned from the PCM_OP_CUST_POL_PREP_NAMEINFO policy opcode is now correctly appended to the return flist of PCM_OP_CUST_CREATE_CUSTOMER.
31225903	A Connection Manager (CM) child process Mutex lock issue occurred during a configuration object refresh. This has been fixed.
31225878	A memory issue that occurred when generating CorrelationId in PortalContext of pcm.jar and there was an issue in the salt counter value of the CorrelationId string. These have been fixed.
31225827	The Paymentech data manager (dm_fusa) and simulator now interpret the MT record only if it is received.
31110284	The impact type is now set properly in the backout event during the rerating process.
31761680	A core dump in the fm_pymt_pol.so library file has been fixed.

Customer-Reported Fixes in BRM 12.0 Patch Set 3

Table 1-6 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 3.

Table 1-6 Customer-Reported Fixes for BRM 12.0 Patch Set 3

Bug Number	Description
29548099	The BRM 12.0 SDK installation uses the source and PortalDevKit directories. The makefile expects the FM policy codes to be in PortalDevKit, but the installation actually copies them into the source directory. Because of this, makefile references were not resolving. This is now fixed. The include directory path is updated by creating a soft link as part of the core installation.
29760523	The number of CM connections in the environment was observed to be increasing to more than 40. This was because Java client applications connected to CM were idling beyond cm_timeout time, causing the CM to shut down. However, the socket connection remains in CLOSE_WAIT status. When the Java application becomes active again, it establishes a new socket connection and old socket still stays in CLOSE_WAIT even though the respective CM had shut down. This is now fixed; the CLOSE_WAIT connections are cleaned up.
29826061	GL.IS_REVENUE and GL.IS_AR functions in the GL Summary queries prevent parallelism. Including these function calls in the SQL for G/L summary causes the Oracle query optimizer to serialize execution of the queries. Changes are now made to enable parallelism for the functions IS_REVENUE and IS_AR and the query for unbilled_unearned report generation is altered to improve the performance.
30006029	In PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO and PCM_OP_SUBSCRIPTION_SET_PRODINFO, the Purchase Start Time was not getting rounded in the set_discountinfo call, even if timestamp rounding was enabled. Because of this, an error was reported if Purchase Start Time was greater than Cycle Start Time. The rounding logic is now added to fix this issue.
30063992	In a scenario where CIT/MIT is disabled but the transaction type customized, resubmitting a payment resulted in an otherwise blank PMT001 record to be sent. This caused Paymentech to respond with code 279 for the invalid record content. The resubmit scenario is now fixed and the PCM_OP_PYMT_COLLECT opcode will drop empty fields when CIT/MIT is disabled.
30072009	While validating mutually exclusive deals, in one case a function was not returning the correct value and validation was failing. This is now fixed and the function now returns the correct value.
30072015	For a plan with First Usage enabled, rerating was creating an unbilled cycle forward event. This is now fixed and appropriate flags are added in the rating call so that it will create an ADJUSTMENT/SHADOW event as applicable.
30078626	The script alter_column_dd_objects_table.source did not update some of the event subclasses in the system. This script is expected to update dd_objects_t.EVENT_TYPE with appropriate values for all events, but a few were missed. This is now fixed and missing event subclasses are added.
30093269	Billing Care was failing to fetch bills for a selected bill unit when there was a very large number of items present for a particular item subtype. This is now fixed so that the argument length for the query fetching data for the input item_sub_type will not exceed 4000 characters.
30108687	If a cycle product was moved to inactive state just before the product end date was reached, perhaps because the account was suspended, the product will never be canceled on its end date because pin cycle fees - cancel was not considering products in an inactive state. In ECE, there is a configuration to remove expired products from ECE cache. Since the above product had an end date, it will be removed from ECE cache. Now when the account is activated again, BRM will synchronize all active and inactive products with ECE. The inactive cycle product will fail in sync because the product is not available in ECE cache since it had already expired and was removed. Now an additional option, pin_cycle_fees - cancel –inactive, is introduced to also cancel inactive products, so that expired products will not be synced to ECE upon reactivating a customer account. It was not possible to reactive an inactive account because the products associated to the account were also inactive and were removed from the ECE cache. This is now fixed.
30120444	Product-based rerating was not working for One-Time Charge products using the -p option. This is now fixed so that when purchase fee event needs to be rerated, the corresponding action purchase event is added to events that needs to be rerated.
30120448	There was a performance issue while processing real-time usage for certain system-level usage products. The issue is resolved by caching system products and discounts during the CM startup instead of caching every time a child is spawned. This behavior is controlled via the business parameter RatePreCacheProductAndDisc.
30125969	Rerating was doubling the rollover amount, because the next billing cycle data was not being correctly returned and the rollover event was not getting generated. The logic related to getting the next billing cycle data during rerating was modified so that rollover event will now be generated.
30133930	Partial billing was failing for a few accounts that previously belonged to a discount sharing group, but were no longer part of the sharing group. During billing, the old discount sharing groups were being fetched. This is now fixed. The unwanted error is skipped and the behavior is changed to exit gracefully when BRM fetches an expired discount sharing group during billing, resulting in a failure.
30133932	Purchasing a discount was failing after enabling the sequential_cycle_discounting business parameter. This was happening because the calc_only rating was failing while fetching the rate plan if the cycle beginning was before product commit date. This is now fixed.
30146962	The bill adjustment amount was not allocated properly if any item in the bill had real-time tax and BILL_DUE or that ITEM_DUE is zero. The AR flow is now modified so that it calculates the tax of the item or bill only if the item or bill has some amount due, and accordingly picking that item for adjustment.
30158957	If one transaction failed when running pin_deposit, subsequent transactions were also not processing properly. This is now fixed. The pin_deposit flow is modified to clear the error buffer before processing subsequent transactions so that the program does not exit abruptly.
30187912	After the migration of XSLT transformation from Xalan to Oracle XDK-XSLT library, date formatting via Java's overloaded method was not working. As a result, the emailed invoice was unable to display the date/time in the user's expected format. New static methods are now added to format the date in customer's expected format using Java's SimpleDateFormat specification.
30187917	Extra tax amount was applied in case of event adjustment when the cancel event was sent in the input flist. The calculated tax amount was not rounded properly. This is now fixed to get the correct tax breakdown and the corresponding tax balance impact in the adjustment event.
30190209	The Rated Event Loader (RE Loader) process stopped abruptly with an out of memory issue. This was because of RE Loader daemon native memory growth, caused by a memory leak in JNI call. This is now fixed.
30205140	These business operations procedures were missing in the BRM 12.0 package and are now included: create_analytics_procedures_UTF8.plb and create_analytics_procedures_Al32UTF8.plb.
30211263	While using the load_config_item_types utility to import config_item_types.xml, item descriptions with special characters (like "ç", "ã") were not loaded into the database. This is now fixed and load_config_item_types now accepts European and special characters with UTF-8 encoding in the input XML file.
30228177	Messages were not committed to the DB when the flag to indicate that the external transaction is opened was set, but there was no external transaction and the publishing DM was waiting for TRANS_COMMIT which did not arrive because no external transaction was open. This has been fixed by modifying the code to properly identify if the PUBLISH_GEN_PAYLOAD is called with or without an external transaction.
30228179	Memory leaks were observed while deleting accounts with pin_del_closed_accts. This is now fixed.
30233959	Paymentech integration (dm_fusa) is now enhanced to support real-time update and China UnionPay cards.
30249952	By setting log_refresh_product and refresh_product_interval in the CM pin.conf, it is expected that the product cache would refresh regardless of the log level set. But the product cache was not refreshing for any log level. This is now fixed.
30249962	When the SOAP-based web services are invoked with invalid content in the XML input, it was observed that they print the XML parsing error message in the log file but continue further and call the opcode. This is now fixed. Change validations are now included to log the error and stop proceeding further.
30252742	Even when the CM received PIN_ERR_TIMEOUT during its startup, the CM continued to start. Appropriate checks are introduced before clearing the ebuf, so that any error occurred is stored and the CM does not start if PIN_ERR_TIMEOUT occurs.
30258068	A bill adjustment on a bill item containing a settled dispute is not working. This was because the settlement item transfer was fetching wrong session objects. This is now fixed.
30276798	While adjusting an event in a billinfo associated with a service-level balance group, the adjustment was getting created and the item being mapped under the default account level balance group. This impacted all AR transactions. This is now fixed. The balance group associated with the event is now being used.
30276799	To migrate /group/sharing/discounts data through the input XML file, the CMT XSD did not have option to provide the offering object for each discount separately. It had an option to specify offering_obj at the group level, so all the discounts under the discount sharing group would have same offering object . The CMT XSD is now modified to support offering objects per discount as well.
30287778	While processing refunds for cycle fees, the cycle fee opcode is called with modified end_t so it can provide appropriate refunds. This modified end_t skipped discounts in identify_discounts if they were canceled. However, this caused skipping of discounts even if it was applicable for the period. This is now fixed so that any discounts will be applied.
30287781	Charges were going to the wrong bill if there was a cancellation after running Bill Now in the delay period. Bill Now bills /item and changes its status. Then the cancellation charges were assigned to same /item even if it was closed, which caused a loss of revenue. This is now fixed and /item is considered only if it is in PENDING state.
30292968	pin_discount_cleanup was not considering inactive discounts for cleanup. This is now fixed to consider inactive discounts as well using the mode close_inactive.
30292978	You can now generate a notification event when a balance is transferred between two different balance groups using the opcode PCM_OP_BILL_ITEM_TRANSFER. This is now included when you use the /event/notification/billing/item/transfer notification event.
30327229	When an event adjustment is performed after a tax-only adjustment on the same event, some of the fields in the tax jurisdiction array were not correct. The issue happens because tax processing logic was exiting after processing the first tax jurisdiction array. The tax processing logic is now modified to consider all the taxes in the tax jurisdiction array present in the event.
30344746	The cycle fee event end date did not align to the next accounting cycle start date. There is a new optional registry entry GrantTimeZoneAlignmentControl which is now added to the FCT_Discount plugin. When GrantTimeZoneAlignmentControl registry entry is set to TRUE and the end date is configured as Relative to billing/account cycle for discount balance impact Resource Validity Period configuration, the end date will be aligned to corresponding accounting/billing cycle date.
30382891	Paymentech Real-Time Account Updater (RAU) support in dm_fusa was generating unwanted debug messages. This is now fixed and such messages are now removed.
30385891	The pin_rerate utility was behaving inconsistently for multiple scenarios. The cycle date calculation was wrong when rerating a quarterly cycle events. Fixed the issue while aligning cycle event dates.
30392335	When there are two cycle events for the same product/period due to a discount purchase, the rerated cycle event was not able to match the previous cycle event. As a result, the rerated cycle event was not populated with session_obj. This is now handled correctly.
30400747	A purchase fee was applied twice, even when the purchase was done only once. This has been fixed.
30406785	Real-time rerating was failing for a charge offer when the PIN_FLD_RATING_PRODUCTS information was truncated due to a string length limit. This has been fixed by increasing the string length.
30406793	During billing, incorrect products were selected for applying folds. This has been fixed.
30411712	The Account Synchronization DM (dm_ifw_sync) was not supporting timeout for its database connection. This has now been added.
30418717	The condition expression for evaluating discounts was a 15-digit decimal by default. The condition evaluation was incorrect when this limit was exceeded. This has been fixed. You can now optionally set the limit to 28 digits with the new MAX28DIGIT_DECIMAL_SUPPORT environment variable before the Pipeline Manager is started.
30457056 30661357	During service transfer from one account to another, the bill unit of the to-account was wrongly updated as self-paying. This has been fixed.
30457057	The Conversion Manager was reported to have performance issues in a deployment that includes Elastic Charging Engine. This has been fixed.
30457059	The Rated Event Loader daemon was not shutting down gracefully while processing rated events from ECE. In addition, when restarting, the daemon was not picking up pre-existing *.bc files. This has been fixed.
30462364	The PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode called PCM_OP_SUBSCRIPTION_FEES even when PIN_FLD_PURCHASE_START_T was not passed. The calc_cycle_from_cycle_start_t entry in the CM configuration file affected the generation of the cycle arrears event. This has been fixed.
30462367	When you created two discount sharing groups, one with the current datedEFFECTIVE_T and the other for a backdated EFFECTIVE_T, the backdated discount sharing group was not considered for valid backdated usage. This has been fixed.
30499867	During rerating, the event search workflow was not considering the configured event_start_timestamp parameter in the pin_event_extract.cfg file, but instead it was taking the event END_T. This has been fixed.
30505484	The Paymentech Data Manager was sending empty PMT001 records to Paymentech when Customer/Merchant Initiated Transactions (CIT/MIT) were disabled. This has been fixed.
30510695	Backdate validation failed when timestamp rounding was disabled and a full discount was purchased. The full discount rounded the discount's START_T to ACTG_LAST_T. When the discount's START_T was earlier than the timestamp of the last status change, validation failed. This has been fixed.
30516311	For an account, after a payment was allocated to cycle tax item of a bill, any bill level adjustment on the remaining amount was unsuccessful with an incorrect calculation of amount due. This has been fixed, to calculate the remaining cycle tax portion correctly soon after the payment allocation, so that during adjustment the remaining charge is calculated correctly.
30521545	The Paymentech Data Manager (dm_fusa) back end was reaching 100% CPU utilization when a verification request was sent and not returning from the call. This has been fixed.
30521547	The Discover Card BIN ranges were not in line with the official Discover Card ranges. This has been fixed.
30521553	BRM now supports extended ranges for newly added cards for China UnionPay BIN.
30537768	There were issues reported by Fortify scans in the following SDK source code: fm_cust_pol_valid_all.c, sample_who.c, and BRMAdapterServletClient.java. This has been fixed.
30543119	The advanced discounting pipeline was returning PIN_ERR_BAD_VALUE when it was called from the pin_cycle_fees utility. This has been fixed.
30548436	A discount of 100% on a noncurrency charge failed when multiple charge packets of multiple noncurrency resources had both positive and negative charges. This has been fixed by properly segregating the charges for each resource and calculating the total for each resource to apply discounts.
30548438	Paymentech Manager has been updated to support the real-time account updater and China UnionPay card BIN ranges.
30580542	The account deletion opcode was not deleting an account in ECE, if there were open sessions for the account. This has been fixed, allowing forced deletion of accounts in ECE, even if open sessions are found.
30588746 30684160	For an account, after a backdated product activation was done, the cycle events were assigned to incorrect items. This has been fixed.
30612469	With thirty day proration enabled, and sequential discounting disabled, there were cases of incorrectly calculated discounts for the month of February having less than 30 days. This has been fixed.
30617487	Rerating was not considering the actual start and end dates of discounts to compare with the period for which the rerating was being done, leading to incorrect charges. This has been fixed.
30623602	Support for the legacy AES encryption scheme (&aes\|... format data) was removed in BRM 12.0 release. It has now been added.
30633364	Conversion Manager was not able to do balance migration due to issues with validity dates. This has been fixed, by using the right validity dates from the balance buckets.
30661356	During rerating, a one time charge was not backed out for item-type products with delayed activation. This has been fixed. Also, BRM will no longer publish item type product and discount details to ECE with the ReratingComplete event.
30691495	The Paymentech simulator was returning a non-empty CIT/MIT transaction ID for MasterCard.
30700120	Discount validity rules were not getting set properly if the end details were given during discount purchase itself and purchase and end timestamp fell on different accounting cycles. This has been fixed, by setting discount validity rules correctly.
30702208	For some opcodes, specifications in XML and XSD were missing. These have been added.
30710324	When a cycle product was inactivated and then activated during the same accounting cycle, the proration flags were not set correctly, resulting in incorrect cycle charges. This has been fixed.
30756024	When bill-time discounting used current accounting dates, the rerating process was calculating discounts incorrectly for older cycles. This has been fixed.
30760716	BRM was not allowing amount-based tax only adjustments. The product has been enhanced to support amount-based tax only adjustments for both credit and debit amounts.
30761676	The offering object information was not passed into the PCM_OP_SUBSCRIPTION_POL_SPEC_CANCEL policy opcode, which was a limitation for extending the functionality around subscriptions. With this fix, PIN_FLD_OFFERING_OBJ is added to the input of the policy opcode.
30765776	With the sequential discounting enabled, there were a few issues: 1. The discount purchased on a modified product, canceled mid-cycle after purchase for full cycle, was applying the discount for full cycle. 2. The refund and reapply operations were going wrong if there were non-overlapping discounts in an accounting cycle. These have been fixed.
30806854	While rerating the recurring charge events for canceled products, the rerate object link was missing in the adjustment event. This caused issues during invoicing, as there was no link between the backed-out event and the rerated event. This has been fixed so that link is established between the backed-out and new event.
30806855	In the rerating flow, the offering object was not updated for a one time charging product with delayed activation, resulting in incorrect results. This has been fixed.

Customer-Reported Fixes in BRM 12.0 Patch Set 2

Table 1-7 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 2.

Table 1-7 Customer-Reported Fixes for BRM 12.0 Patch Set 2

Bug Number	Description
26618794	In order to avoid duplicate tax calculation and incorrect tax adjustments, the is_tax_calculated flag was introduced earlier for pipeline rated events. But this caused an issue in the tax calculation during the event adjustment, when the event included had more than one tax balance impact. This has been fixed.
27123464	It was not possible to set the promise-to-pay date as the system date. This has been fixed. Now, additional validations are added to ensure that the promise-to-pay date is greater than the system date.
27632734	Paymentech Data Manager (DM) now supports Customer-Initiated Transaction (CIT) and Merchant-Initiated Transaction (MIT) for processing VISA credit cards. See "Support for Stored-Credential Transactions for Payments".
27993355	The POID_ID required an increase in the number of bits from its current value of 44 bits because the allocated range of Portal object IDs (POID) were not sufficient. This has been now increased to 51 bits.
28342613	A payment of zero amount was failing in BRM with an error because there was PIN_FLD_PAYMENT value was not set in the response. This has been fixed.
28387497	BRM was not providing flexibility to set the transaction type for payments processed through Paymentech DM in the PCM_OP_PYMT_POL_PRE_COLLECT policy opcode. This has been fixed.
28444532	Oracle Data Manager was incorrectly logging an error message when insufficient back ends were configured. This has been fixed and now a warning message is displayed.
28466602	Indexes were rebuilt every time the audit tables were purged. This has been fixed. The purge_audit_tables.pl script has been modified and the indexes are not rebuilt if the $rebuild_indexentry in the BRM_home/sys/archive/oracle/purge_audit_tables.conf file is set to no, where BRM_home is the directory in which you installed BRM components. If this entry is not set or set to any other value, the indexes are rebuilt every time the audit tables are purged.
28490340	During the billing process, the end date in a cycle arrear event was set incorrectly when the product end date was the same as the actg_next_t value. This caused the resources to have incorrect validity dates. This has been fixed.
28521329	Paymentech DM now supports CIT and MIT for processing Mastercard, Japan Credit Bureau (JCB), and Diners Club credit cards. This has been fixed.
28543518	During subscription transfer, Adaptec AdvancedRAID Controller (AAC) details (for example, PIN_FLD_AAC_PROMO_CODE) of the service from the source account were not copied to the new service created at the destination account. This has been fixed.
28549500	The pin_recover utility was failing while searching for payments to be recovered. This has been fixed.
28552543	Web Services Manager was always sending the date-time stamp information in Universal Time Coordinated (UTC) as part of the response without considering the actual timezone. This has been fixed to send the date-time stamp as per the time zone configuration in the BRM_home/deploy/web_services/Infranet.properties file.
28556710	The rerate process did not update the original event. This has been fixed and some additional criteria has been added to identify and update the corresponding original event during rerating.
28588801	During the sequential discounting, non-applicable events were also considered while calculating the periods. This has been fixed.
28596194	The fm_pymt module was not sending transaction type to Paymentech DM. This has been fixed. Now, transaction type is used by Paymentech DM to identify the type of payment, for example, recurring, installment, and so on.
28603124	The scripts in BRM_home/bin was using two different versions of HTTPClient libraries, 4.4 and 4.5.3. This has been fixed to use only 4.5.3 version.
28607064	In a BRM deployment with Oracle Communications Elastic Charging Engine (ECE) as charging engine, when the BRM Oracle Data Manager commit failed, the BRM data was not in synchronization with the ECE cache data. This has been fixed by triggering a commit to ECE only after the BRM Oracle Data Manager commit is successful.
28631061	In the subscription opcode PCM_OP_SUBSCRIPTION_SET_PRODINFO, a memory leak was observed. This has been fixed.
28638444	In the subscription module, during the product cancellation, an incorrect scale for refund was used. This has been fixed.
28671913	The EVENT_POID_LIST required to store longer strings than it was allowed (4000 characters) in the database. This has been fixed.
28678759	A memory leak was observed in flist to string conversion routine. This has been fixed.
28689682	During rerating, the impact type for PIN_IMPACT_TYPE_TAX_RERATED was not being set to PIN_IMPACT_TYPE_TAX, and this was leading to incorrect tax amounts in the invoices. This has been fixed.
28700838	Backdated adjustments were not displayed in the corrective invoices. This has been fixed.
28774361	The PaymentDeallocation feature allows bill adjustment on a zero due bill or a partially paid bill. The same behavior has been now implemented for item and event-level adjustments. If BillPaymentDeallocation is enabled, do the following to allow the item and event-level adjustments: Unallocate the payment applied on the corresponding bill item. Do the item or event-level adjustment. Reallocate the payment back to the bill item. If the payment amount is more than the due amount after the adjustment is done, then some unallocated amount is stored in /item/payment. This unallocated amount is displayed in the Adjustment/Payments not applied tab of Customer Center.
28774366	If an error is thrown in ECE, the error was always set to PIN_ERR_BAD_VALUE. Hence, it was not possible to identify the actual error details. This has been fixed. In case the output flist of the PUBLISH_ECE_EVENT operation contains ERROR_DESCR set to Credit Ceiling Breached, the ebuf is set to PIN_ERR_CREDIT_LIMIT_BREACHED instead of PIN_ERR_BAD_VALUE.
28780635	There was an issue of wrong selection of item type when dealing with in-advance billing events. /item/adjustment was created instead of /ite/mcycle_forward_arrear for a cycle_forward_arrear event when billing in-advance was set. This has been fixed.
28786829	The PCM_OP_BILL_MAKE_BILL_NOW opcode was resetting the error buffer set by a policy customization in the workflow. This has been fixed.
28794484	In the subscription module, if END_T passed was earlier than the cycle/purchase/update end dates, then the cycle start and end dates were set incorrectly leading to validation error. This has been fixed.
28812794	The Conversion Manager failed to load data into uniqueness table due to the presence of double quotes. This has been fixed to parse and omit double quotes in the uniqueness-related functions.
28812798	The PCM_OP_AR_BILL_ADJUSTMENT opcode had memory leaks. This has been fixed.
28824835	The Connection Manager module had some memory leaks. This has been fixed.
28837038	In the subscription module, for a backdated purchase done on the billing day of the month, the end date for the event was incorrectly set and this was causing wrong validity periods for the resources both in BRM and Pipeline Manager. This has been fixed.
28843066	The Load Price List utility was failing with core dump while committing or retrieving price list. This has been fixed.
28848746	The Billing Care user interface was not displaying the details of a bill that was generated before the account was moved into a hierarchy. This has been fixed.
28848748	The transaction opening workflow was not returning an error, while trying to open a transaction on a non-existent object. This has been fixed with proper checks for existence of an object before the object is tried for a lock to open the transaction on it.
28871778	The file name format of the General Ledger (G/L) reports generated in XML were different. This has been fixed to restore the earlier naming format.
28873152	Any auditable updates to the account creates an entry in the audit table for au_account_t. In addition, for a transaction that requires data from the audit table, searching in au_account_t was taking considerable time. In such cases, the updates had to fetch effective_t from account_t if au_account_t returned null. This has been fixed.
28905266	When an account is deleted using a wrapper opcode that invokes PCM_OP_CUST_DELETE_ACCT opcode, an error in the workflow did not roll back the changes to /uniqueness object. This has been fixed.
28923379	The PCM_OP_BILL_MAKE_BILL opcode finalized the bill when the workflow was invoked by a process other than pin_bill_accts indicated by the program name field. This has been fixed to finalize the bill only through the pin_bill_accts utility.
28944041	For PCI compliance, it was required to mask the PIN_FLD_SECURITY_ID field in the card attributes structure for enhanced card security. See "Card Security Code Is Now Masked in Logs".
28944043	Paymentech DM has been enhanced to support Card Security Presence and to send Fraud Format Indicator (FR) record when this field is present. See "Additional Card Security Presence Values Supported for Card Validation or Authorization".
28944047	Paymentech returned duplicate CIT and MIT transaction IDs. This has been fixed and transaction IDs for CIT and MIT records are generated in a random manner.
28977386	Oracle Data Manager was not responding for a long time when PIN_ERR_NO_MEM was returned from the flist copying method. This has been fixed.
28997123	In the subscription module, when multiple discounts were purchased with different validity dates in the same deal, the discounts rules were not set correctly for the individual discounts. The discount validity dates of the first discount was used for all other discounts in the deal. This has been fixed.
29017375	The Connection Manager was dumping core when running pin_deferred_act and pin_bill_day utilities due to memory management issues. This has been fixed.
29023518	Due to the scope of the header file, the customer management module was throwing a symbol look up error. This has been fixed.
29036175	In the subscription module, during the product cancellation operation, the refund amount was calculated incorrectly if it includes in-advance charges. This was due to considering event end date instead of cycle end date for calculating the scale for refund. This has been fixed.
29042246	During the billing delay period for a deployment with the billing delay configuration, any discount cancellation operation was not applying refunds. Only during the delay period this inconsistency was observed as the accounting dates available in the bill unit would not be updated and still reflect the previous cycle information. This has been fixed with proper checks to handle such events in the delay period.
29042248	A memory leak was observed in the customer registration module. This has been fixed.
29042250	In some cases, PCM_OP_EXEC_PROC was not returning the correct response. This has been fixed.
29120662	A memory leak was observed in the Paymentech DM. This has been fixed.
29120695	When creating /payinfo/cc objects, any custom fields passing into the workflow were not dropped, which caused a schema error. This has been fixed.
29127140	In the subscription module, the PCM_OP_SUBSCRIPTION_CANCEL_DEAL opcode caused segmentation fault core dump while processing discounts. This has been fixed.
29141791	When rerating was done before billing, the invoice data received from ECE was not present in the rerated event. Instead, original invoice data was populated in the rerated event. This has been fixed.
29146203	The modify customer operation was not applying the cycle discount information passed in the input due to missing Portal object ID (POID) information in PIN_FLD_DEAL_INFO. This has been fixed.
29151194	In the subscription module, canceling a purchased product with the cycle start date in the future and the purchase and usage start dates in the past, updated the cycle, purchase, and usage start dates. This has been fixed to update only the cycle start date.
29151195	For a purchased product, if either purchase, usage, or cycle end date was changed, the end date for purchase, usage, and cycle were updated. This has been fixed to update only the date that is changed.
29174549	In Collections Manager, the PCM_OP_COLLECTIONS_GROUP_CREATE opcode had memory leaks. This has been fixed.
29178997	Event adjustment was not working as expected if the amount or percentage was not provided in the input. The expectation was to do 100% event adjustment if the amount or percentage value was not provided. This has been fixed.
29204382	In an Application Integration Architecture (AIA) deployed environment, during any transaction where the request is sent from BRM to ECE, if an error occurred in ECE, then AIA was not able to capture the error from BRM. This has been fixed.
29221143	The discount validity rules were not set for the discounts starting or ending in a future cycle as the accounting dates were prone to change. This has been fixed to identify the discounts during billing that have start or end dates in the next billing cycle and set the validity rules appropriately.
29265113	In case of a discount sharing scenario, when multiple reauthorization requests are created, the reservation quantity was not updated and it stayed at sum of the quantity of the first authorization and last reauthorization. In this case, it was possible to reauthorize sessions indefinitely and certain limits were also not enforced. This was leading to revenue leakage. This has been fixed.
29278528	In the subscription module, the plan transition opcode resulted in segmentation fault dumping core. This has been fixed.
29342746	While rating with sponsored product, the credit limit check was done both on the sponsored product and the user product. Due to this, a credit limit breach was reported when the user product sub-balance was positive. This has been fixed by removing the credit limit check on the user product while rating with the sponsored product.
29342749	CPU usage for the Connection Manager module reached and stayed at 100%. This has been fixed.
29370866	In the subscription module, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode failed for an account-level discount. This has been fixed.
29376633	In the Pipeline Manager Framework, a memory leak was reported while converting decimal to string. This has been fixed.
29395724	In a Service Lifecycle Management (SLM)-enabled deployment, when a deal was purchased with balance as zero, the service state was immediately set to recharge_only. This caused usage processing issues in ECE. This has been fixed. Now, status is not changed to recharge_only as soon as the purchase is completed.
29409245	In the subscription module, during the product cancellation operation, the validity end dates for noncurrency resources of an in-advance cycle was wrongly set. This has been fixed.
29428268	During the pin_collect process for payments, an error indicating PIN_ERR_PARTIAL was thrown, especially with CIT and MIT transactions. This has been fixed.
29441735	During the billing process, few items were incorrectly filtered during final billing, and it was due to item pruning in cases of billing suppression, suspension, or resume billing. This has been fixed.
29441740	When a back-dated account with a multi-month cycle was moved into a hierarchy, the child account's PIN_FLD_ACTG_NEXT_T did not align with that of the parent account. This has been fixed. Changes have been made to ensure that the dates are aligned.
29448150	Event adjustment was not working properly for tax-only adjustments. This has been fixed.
29448154	The PCM_OP_COLLECTIONS_GET_AGENTS_ACTIONS output flist did not return the PIN_FLD_COUNT field. As a result, the custom logic failed. This has been fixed.
29448156	In the subscription module, the product cancellation operation did not report missing validity information. This has been fixed.
29454752	Non-CIT and MIT were failing in an attempt to access the unavailable data. This has been fixed with appropriate null checks and error handling.
29460620	In the subscription module, incorrect discount amount was calculated when a discount was applied on a back-dated cycle forward monthly charge. This has been fixed.
29463336	In the subscription module, the pin_cycle_fees utility was not selecting the tailor made products when run in the Cancel mode. This has been fixed.
29480201	The AAA Services Framework, PCM_OP_TCF_AAA_AUTHORIZE opcode, had a memory leak. This has been fixed.
29496597	When a discount was purchased in deferred mode, and it was canceled subsequently before the actual start of the discount, the cycle, purchase, and usage start dates were not updated to align with the end dates. This has been fixed.
29514020	During billing, price-overridden products were not considered properly for rating. This has been fixed.
29514025	For a discount-sharing group, when balances were concurrently updated using the multithreaded application (MTA) framework, the balance updates were not made correctly obtaining necessary lock to the balance group. This has been fixed.
29526005	It was not possible to run multiple Rated Event (RE) Loader processes in parallel. When multiple RE Loader processes were run in parallel, the row lock contentions rendered the processes non-responsive. This has been fixed.
29533564	The PCM_OP_PYMT_COLLECT opcode was not working for transaction ID with a length more than 16 characters. This has been increased to 22 characters to be consistent with the Paymentech (fusa) specifications.
29533569	Wrong quantity for the event was picked up for rating. The event matching logic was considering the events based on the order in which they appeared. This has been changed to the longest match event and now that is considered first, overriding the order of events.
29533572	Tax percentage was not added even if the tax calculation was not using any third-party tax engines. This has been fixed. Changes are done to check tax_pkg_type for zero-tax amount cases.
29557884	In Oracle Communications Billing Care, it was not possible to track the user making any changes or updates in the News Feed section. This has been fixed. The external user data is persisted as PIN_FLD_EXTERNAL_USER in the /newsfeed storable class.
29557888	For an offer, if an usage event was rated that had 0 (zero) charge and then the offer was changed and rerating was 1 (one), there was no adjustment event created nor a new usage event was created with 0 charge. This has been fixed. Now, a new event with 0 charge is created and the general ledger ID (G/L ID) corresponding to the offer is impacted.
29584658	If the price of an one-time charge product is changed post billing and rerating and corrective invoicing is done, the rerated charge was not reflecting in the invoice. This has been fixed.
29590523	The RE Loader was failing with the error "too many open files" and required an update to handle maximum number of files. This has been fixed.
29596720	The pin_deferred_act utility was generating an error message in certain cases while dropping array elements, such as PIN_FLD_TELCO_FEATURES. This has been fixed.
29622932	A bill was not including the charges during service activation from deferred actions on the bill date. A new business parameter, BillDeferredActions, has been introduced in the Billing instance of the /config/business_params object. By default, the BillDeferredActions parameter is disabled and the charges are added to the next bill. If you set the BillDeferredActions parameter to enabled, the charges are included in the current month bill.
29634985	Even when a migration failed, the Conversion Manager was reporting it as success. This has been fixed.
29673013	It was not possible to synchronize the account data loaded into BRM with ECE by using the Conversion Manager. By default, the BRM data is published to ECE asynchronously, which could potentially lead to inconsistent data between BRM and ECE, if there are any synchronization failures. Also, it was not possible to migrate the hierarchical accounts into BRM if the parent and child accounts are in the same files and the parent accounts were not loaded first. This has been fixed. You can now perform the following: Loading the migrated account data in BRM into ECE synchronously (in real-time). Migrate parent and child accounts into BRM using the same input file.
29681830	In Billing Care, it took longer time to display the Account page. It was due to the PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode, delaying loading of accounts to the Account page. This has been fixed.
29714064	When a product was canceled, refund was not going through if the product was purchased on Day 28 through Day 31 of a month with 31-day billing enabled and the next billing date did not exist in the subsequent month. This has been fixed.
29795746	BRM triggered ECE_POST_COMMIT in ECE even when the transaction was cancelled. This has been fixed.
29808545	Any operation that included the PROFILE_SUBSCRIBER_PREFS_T table was causing a full table scan. This has been fixed by introducing an index on the table.
29820123	For the pin_mass_refund utility, performance issues were observed. This has been fixed.
29858023	In the plan transition flow, a new notification event /event/notification/plan/transition/post_deal_cancel was required to be sent soon after cancellation. This has been added.
29867410	During the cancellation of a cycle-forward event, the subscription module did not fetch all the related events for reversal of charges. This has been fixed.
29871639	In the discounting module of Pipeline Manager, after unloading existing configuration, a memory leak was observed while loading the new configuration, which was causing the growth of the used memory. This has been fixed.
29900322	In the adjustment workflows, the decimal rounding precision was different from the configured precision for usage events. This has been fixed.
29920007	In Conversion Manager, data errors were reported while migrating balances. These errors were due to unreleased database connections from the previous tasks. This has been fixed.
29937126	During the billing process, it was observed that the next item POID list of the service object was corrupted. This has been fixed.
29960514	While running the pin_del_closed_accts utility, NO_MEM error occurred. In such cases, memory was not cleared. This has been fixed.
29966023	There were memory management issues in the Oracle Data Manager when search operation was performed using the PCM_OP_BILL_ITEM_ADJUSTEMENT opcode. This was because the search returned a huge number of events crossing the high watermark for the Data Manager process. This search template has been fixed to retrieve the calculated sum from the database instead of retrieving huge number of records and calculating the sum.
29966026	The Paymentech DM was not supporting Zero Value Account Verification (ZVAV) for American Express cards. This has been fixed.
30031382	The RE Loader Daemon could not process certain files resulting in unprocessed files pending in the input directory. This has been fixed.
30095369	The RE Loader process witnessed an unaccounted growth in memory due to memory leak. This has been fixed.
30156863	The create_analytics_procedures_UTF8.plb is now included.
28653606 29428272	The Daylight Saving Time calculation was incorrect for Brazil. This has been fixed.
28923384 28975424	The RE Loader process was not gracefully shutdown, when it was still processing files. This has been fixed. Now, the RE Loader continues to process the pending files and then shuts down. A new configuration entry, batch.shutdown.interval, is introduced in the BRM_home/apps/pin_rel/Infranet.properties file to set the shutdown interval in seconds. By default, this entry is set to 2.

Customer-Reported Fixes in BRM 12.0 Patch Set 1

Table 1-8 lists the customer-reported issues that were resolved in BRM 12.0 Patch Set 1.

Table 1-8 Customer-Reported Fixes for BRM 12.0 Patch Set 1

Bug Number	Description
26810954	Web Services Manager was not fully compliant to SOAP 1.2 format. This has been fixed.
26810956 27241793	When the tiered taxation was applied, the tax information was consolidated instead of keeping it separate for each tier. This has been fixed.
26913721	After a service transfer from one account to another using the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode, the UNIQUENESS_T table was not updated with the correct account POID causing a mismatch with the correct account POID in the SERVICE_T table. This has been fixed.
26954698	For a quarterly billing cycle, the accounting dates were calculated incorrectly and this resulted in incorrect accounting periods. This has been fixed.
26961858	Refunding a fixed discount was incorrectly causing the refund of extra charges or other charges. This has been fixed.
26968649	Conversion Manager was throwing an error when the input XML contains a comma (,) in it. This has been fixed.
26980059	During product cancellation, while setting the product's charged period dates based on proration settings, the in-advance bill period was also being considered and this was causing inconsistencies. This has been fixed.
26990857 27577925	Authorization was incorrectly granting more than the available shared resource. This has been fixed.
27001622	In Collections Manager, when a scenario is replaced with another, the due date calculated for collection actions was incorrect. This has been fixed.
27001628	In Collections Manager, there was a deadlock situation during the collections process. This has been fixed.
27001631	When getting the aggregated information about a resource from BRM, the process was failing if the events for those resources were purged in the system. This has been fixed.
27016775	After the backdated modification of the discount end time (END_T), the charges were calculated incorrectly if sequential discounting was enabled. This has been fixed.
27023170	The PIN_ERR_LOG_FLIST function was generating core dump when any field in the flist logged was null. This has been fixed.
27049618	The 32-bit BRM client applications were not working properly with large files on Linux platforms. This has been fixed.
27060891	When the pin_collections_process utility was run, if the event POID was sent as null in the input flist while calling the PCM_OP_AR_RESOURCE_AGGREGATION opcode, it was dumping core instead of returning a proper error message.
27067419	When using Conversion Manager for loading data, the parent account and account receivable details could not be provided at bill-unit level. This was causing issues if the account had multiple bill units. This has been fixed.
27067422	The discount purchase was failing when the discount validity was set to full or none. This has been fixed.
27116849	The tax percentages were not properly getting accumulated in the balance impact of the rated event. This has been fixed.
27130470	There was an issue with state enumerations that was causing a core failure in BRM. This has been fixed.
27159336	The audit data retrieved from the database was not in the correct order. As a result, the rerating process was not creating charging events. This has been fixed.
27159380	When setting the discount validity dates on cycle boundaries, the discount validity rules were not considered for calculation and this resulted in incorrect discounts. This has been fixed.
27159381	There was a need to reassign the range for custom fields. This has been fixed.
27178506	Rerating was failing for usage events created on the billing day. This has been fixed.
27181445	For hierarchical accounts, bill-level adjustments were not getting synchronized with ECE properly. This has been fixed.
27199237	When applying cycle discounts, full discounts could not be applied due to incorrect discount start dates set by the set_discountinfo opcode. This has been fixed.
27202235	When accounts had hierarchical bill units, account deletion was failing. This has been fixed.
27213533	When the fetch size reached the maximum limit, the pin_bill_accts utility reported a performance issue. This has been fixed.
27219879	The pin_recover utility in the -rfr mode was not updating the result to zero in the charge event. This has been fixed.
27223026	The subscription transfer workflow was not allowing to use the custom logic to control the rerate requests through policy. This has been fixed.
27226303	In BRM, it was possible to allocate the same adjustment to a bill twice. This has been fixed.
27229728	While loading offer profiles into BRM, the "Double Free Or Corruption" error was displayed. This has been fixed.
27236217	Rated Event Loader Daemon did not process backlog files and went into sleep mode. This has been fixed.
27244352	There was no option to disable journal creation for zero (0) balance records. This has been fixed.
27263078	Duplicate events were created for the same period for cycle-forward products and the events did not have any balance impacts associated with them. This has been fixed.
27266272	When PDC was used for configuring pricing objects, there was some issue in the Item Type Selector configuration due to format mismatch. This has been fixed.
27269943	The host name was not validated properly during the BRM installation in silent mode. This has been fixed.
27274074	The discount purchase operation was not considering the appropriate rate plan resulting in incorrect calculation of the discount period. This has been fixed.
27274076	For time-based full discounts, BRM was incorrectly calculating the discount amount. This has been fixed.
27277544	When a service configured to have only discounts was terminated, an error was thrown. This has been fixed.
27288519	For accounts with multiple bill units, write off reversal was failing as the reversal items pointed to one bill unit. This has been fixed.
27304029	Even if the log level was set to ERROR, some debug messages were getting recorded in the log files. This has been fixed.
27304030	The value for the StopBillClosedAccounts business parameter was always getting set to 1 irrespective of the value specified. This has been fixed.
27309569	The input data for the payment policy opcode, PCM_OP_PYMT_POL_PRE_REFUND, did not contain all the required information for policy processing. This has been fixed.
27309573	The pin_deposit utility was not collecting pre-authorized charges. This has been fixed.
27337657	When making adjustments, if the adjustment amount was more than the actual due amount, an inconsistent behavior was observed. This has been fixed.
27362564	In Customer Center, when the permission to access account receivables (/accounttool/araccess) was set to read-only, the customer service representative (CSR) was not able to view the adjustment details from the Bill Details or Item Details page. This has been fixed.
27369059	System discounts for cycle arrear events were not applied properly. This has been fixed.
27389701	Web Services Manager was returning the Cannot initialize error when triggering the opcodes. This has been fixed.
27415116	Rerating events after changing the accounting cycle day of month (DOM) was incorrectly impacting the balances. This has been fixed.
27418546	The PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS opcode was not considering the latest or current hierarchy to calculate the amount due from aging buckets. This has been fixed.
27425461	When installing BRM in silent mode, the response file required the database system user password which was a potential security risk. This has been fixed.
27448146	When the billing delay was configured, auto-triggered billing from ECE was generating a final bill instead of a partial bill. This has been fixed.
27463239	Launching Suspense Center with Java WebStart had issues due to the version mismatch between the shipped version (4.5.3) and the version specified (4.4) in the orasoft.jnlp file. This has been fixed.
27463244	The General Ledger job was taking more time than expected and required a performance update. This has been fixed.
27507372	When a product configured with the cycle arrear event was canceled with a backdated date, the refund was not applied properly. This has been fixed.
27523584	Rerating after purchasing a discount was not working as expected. This has been fixed.
27523592	When a child account was moved under a parent account, the usage charges were not included in the correct bill. This has been fixed.
27539381	In some cases, while disconnecting a service, the PCM_OPCUST_SET_STATUS opcode was entering a deadlock. This has been fixed.
27539388	If sequential discounting was enabled, the subscription discounting was getting applied on top of the system-level discount. This was causing errors in some scenarios. This has been fixed.
27552474	During rerating, additional tax balance impacts were created. As a result, the adjustment calculated was incorrect. This has been fixed.
27584537	Conversion Manager was not handling migration of accounts with quarterly bill cycles properly. This has been fixed.
27591136 27738257	When event adjustment was done after tax-only adjustment, the tax jurisdiction information was not updated properly in the balance impact of the event adjustment. This has been fixed.
27613611 27613617 28149096	Rated Event Loader (pin_rel) was exiting due to the out of memory error. This has been fixed.
27613636	During cancellation of a product configured with in-advance billing, incorrect START_T and END_T were set in the events. This has been fixed.
27621461	In Collections Manager, when an account had two bill units, a paying bill unit and a non-paying bill unit, the aging due was calculated incorrectly. This has been fixed.
27667959	While recovering the failed payment, duplicate transaction IDs were observed and this was due to running two applications to recover the same failed payment, one was pin_recover and the other was a custom application, in parallel. This has been fixed.
27667961	The General Ledger job was taking more time than expected and required a performance update. This has been fixed.
27684532	In Collections Manager, if the PCM_OP_COLLECTIONS_GET_ACTION_HISTORY opcode was triggered with a transaction having a database number different from that of the collection event user, the opcode was failing. This has been fixed.
27691744	For an account with multiple bill units, a payment reversal for a backdated account level payment was having effective date as the current system date instead of the back date. This has been fixed.
27745481	The Oracle Data Manager process was failing with dumping core when processing the Account Receivables workflow. This has been fixed.
27745484	BRM was not providing options to control or customize workflow over rerate requests which were created as part of subscription transfer operation. This has been fixed.
27745489	When the EventAdjustmentDuringcancellation flag was enabled, the flist data corruption issue occurred intermittently, which was dumping core. This has been fixed.
27751025	The PCM_OP_AR_RESOURCE_AGGREGATION opcode was returning incorrect aggregated amount. This has been fixed.
27771916	The cancel discount operation was not setting the validity dates properly for discounts for which the end dates were in previous cycles. This has been fixed.
27795345	If sequential discounting was enabled, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was not working properly for in-advance billing periods. This has been fixed.
27816387	Even after paying the bill amount, the bill amount from the last bill was displayed as balance brought forward. This has been fixed.
27881741	When an event was rerated twice, the tax jurisdiction was not handled properly for adjustment events. This has been fixed.
27881743	When the same product was purchased twice, canceling one of the product deleted the provisioning tag from both the products. This has been fixed.
27881746	For billing cycles which spans across multiple months, newsfeed was getting created for the /event/notification/service_item/make_bill event for each accounting cycle. This has been fixed.
27891324	In a prepaid environment, when the subscriber's balance was lower than the required balance for a purchase and if a deal was purchased, BRM displayed the credit limit exceeded error. In addition, signal 11 was observed in Connection Manager. This has been fixed.
27894048	The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan. This has been fixed.
27894050	During item adjustment, the search operation got into a infinite loop. This has been fixed.
27938633	The dm_fusa front end was not receiving data after the connection manager established connection with it. This has been fixed.
27938637	It was not possible to locate the Secure Sockets Layer (SSL) client wallet file due to the use of back slash (\) in the resource path instead of a forward slash (/). This has been fixed.
27938640	The PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode was not allowing to add or modify the event data in its workflow through the PCM_OP_BILL_POL_GET_EVENT_SPECIFIC_DETAILS policy opcode. This has been fixed.
27956401	In Collections Manager, the collection write-off was failing for the bill unit in collection. This has been fixed.
27979521	The PCM_OP_SEARCH base opcode was failing when the template included a nested select query with the grouping by clause. This has been fixed.
27993358	During billing, the grantor information in the rollover bucket was incorrectly set to null. This has been fixed.
27993360	In LDAP Manager, the entry update operation was failing. This has been fixed.
28007850	When rating an event, sponsored products were ignored. This has been fixed.
28020470	If a service had two products and when one product was canceled, the EFFECTIVE_T value of the service was also updated. This was not allowing the processing of usage events for the other product. This has been fixed.
28089237	Quarterly cycles were getting merged which caused issues in applying charges. This has been fixed.
28089239	The date format in Web Services Manager could not be configured based on the Java's SimpleDateFormat specification. This has been fixed.
28119224	When in-advance billing was enabled, purchasing discount with a future date to become valid on ACTG_NEXT_T resulted in validation errors. This has been fixed.
28123147	Conversion Manager was not providing an option to capture bill_accounting_cycles_left and next_bill_t information for migration. This has been fixed.
28141241	The dm_ldap process was failing to start when SSL was enabled. This has been fixed.
28141243	After loading the rated events from Pipeline Manager, it was found that MOD_T of the corresponding items and journals were less than the CREATED_T. This has been fixed.
28159376	When an adjustment was applied in BRM, the revision number for the balance group was set incorrectly to zero causing data inconsistency between BRM and ECE. This has been fixed.
28200056	After purchasing the monthly cycle forward product, the newsfeed for the same did not include the bill unit information. This has been fixed.
28220691	When there were multiple bill adjustments, reallocation of the payment was done incorrectly. This has been fixed.
28247287	The bill generated using Bill Now was not including all items due for billing. This has been fixed.
28255178	Even if there was no amount left for adjustment, BRM was allowing adjustment up to the full adjustment amount. This has been fixed.
28259108	When an APN Map was reloaded using a semaphore, the rating functionality did not consider the new APN Map configuration. This has been fixed.
28261961	BRM was considering the regular monthly cycle forward event as backdated if the billing was run after the specified in-advance billing days in the same month. This has been fixed.
28261967	For cycle forward events, having discounts the newsfeed functionality was not working. This has been fixed.
28278327	Setting purchase start dates for first usage products was not allowed by using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode. This has been fixed.
28281697	When BRM was processing orders by using JCA Adapter, if the CM instance goes down, the JCA Adapter was unable to restore the transaction state. As a result, the subsequent orders could not be processed without restart. This has been fixed.
28334999	In case of sequential discounting, expired or ended discounts were also applied when new discounts were purchased. This has been fixed.
28342603	When an account was created, the ACCOUNT_NO value was not updated correctly in the UNIQUE_ACCT_NO_T table. This has been fixed.
28342608	The event adjustment for the product configured for deferred taxes was not updating the tax jurisdiction information in the balance impacts correctly. This has been fixed.
28366495	There were memory leaks observed in the PCM_OP_TCF_AAA_STOP_ACCOUNTING opcode workflow. This has been fixed.
28366497	There was a memory leaks observed in the op_tcf_aaa_search_session workflow. This has been fixed.
28379547	In a BRM system integrated with ECE, External Manager (EM) Gateway was causing errors which led to data inconsistency. This has been fixed.
28379549	When the updated pricing data was loaded using semaphore, the charges were calculated incorrectly. This has been fixed.
28379551	With in-advance billing, the scale was calculated incorrectly as zero for a valid purchased product having an end date set. This has been fixed.
28415082	The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan. This has been fixed.
28463456	The rerating flow was not updating the session_obj and rerated_obj information correctly. This has been fixed.
28466613	When doing a plan transition, it was not possible to override the resource balance granted or add any custom workflow. This has been fixed.
28359386 28359381	In Collections Manager, if schedule object was either completed or canceled, it was effective only for collection group owners, but not for members. This has been fixed.

Bug Number

Description

26810954

Web Services Manager was not fully compliant to SOAP 1.2 format.

This has been fixed.

26810956

27241793

When the tiered taxation was applied, the tax information was consolidated instead of keeping it separate for each tier.

This has been fixed.

26913721

After a service transfer from one account to another using the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode, the UNIQUENESS_T table was not updated with the correct account POID causing a mismatch with the correct account POID in the SERVICE_T table.

This has been fixed.

26954698

For a quarterly billing cycle, the accounting dates were calculated incorrectly and this resulted in incorrect accounting periods.

This has been fixed.

26961858

Refunding a fixed discount was incorrectly causing the refund of extra charges or other charges.

This has been fixed.

26968649

Conversion Manager was throwing an error when the input XML contains a comma (,) in it.

This has been fixed.

26980059

During product cancellation, while setting the product's charged period dates based on proration settings, the in-advance bill period was also being considered and this was causing inconsistencies.

This has been fixed.

26990857

27577925

Authorization was incorrectly granting more than the available shared resource.

This has been fixed.

27001622

In Collections Manager, when a scenario is replaced with another, the due date calculated for collection actions was incorrect.

This has been fixed.

27001628

In Collections Manager, there was a deadlock situation during the collections process.

This has been fixed.

27001631

When getting the aggregated information about a resource from BRM, the process was failing if the events for those resources were purged in the system.

This has been fixed.

27016775

After the backdated modification of the discount end time (END_T), the charges were calculated incorrectly if sequential discounting was enabled.

This has been fixed.

27023170

The PIN_ERR_LOG_FLIST function was generating core dump when any field in the flist logged was null.

This has been fixed.

27049618

The 32-bit BRM client applications were not working properly with large files on Linux platforms.

This has been fixed.

27060891

When the pin_collections_process utility was run, if the event POID was sent as null in the input flist while calling the PCM_OP_AR_RESOURCE_AGGREGATION opcode, it was dumping core instead of returning a proper error message.

27067419

When using Conversion Manager for loading data, the parent account and account receivable details could not be provided at bill-unit level. This was causing issues if the account had multiple bill units.

This has been fixed.

27067422

The discount purchase was failing when the discount validity was set to full or none.

This has been fixed.

27116849

The tax percentages were not properly getting accumulated in the balance impact of the rated event.

This has been fixed.

27130470

There was an issue with state enumerations that was causing a core failure in BRM.

This has been fixed.

27159336

The audit data retrieved from the database was not in the correct order. As a result, the rerating process was not creating charging events.

This has been fixed.

27159380

When setting the discount validity dates on cycle boundaries, the discount validity rules were not considered for calculation and this resulted in incorrect discounts.

This has been fixed.

27159381

There was a need to reassign the range for custom fields.

This has been fixed.

27178506

Rerating was failing for usage events created on the billing day.

This has been fixed.

27181445

For hierarchical accounts, bill-level adjustments were not getting synchronized with ECE properly.

This has been fixed.

27199237

When applying cycle discounts, full discounts could not be applied due to incorrect discount start dates set by the set_discountinfo opcode.

This has been fixed.

27202235

When accounts had hierarchical bill units, account deletion was failing.

This has been fixed.

27213533

When the fetch size reached the maximum limit, the pin_bill_accts utility reported a performance issue.

This has been fixed.

27219879

The pin_recover utility in the -rfr mode was not updating the result to zero in the charge event.

This has been fixed.

27223026

The subscription transfer workflow was not allowing to use the custom logic to control the rerate requests through policy.

This has been fixed.

27226303

In BRM, it was possible to allocate the same adjustment to a bill twice.

This has been fixed.

27229728

While loading offer profiles into BRM, the "Double Free Or Corruption" error was displayed.

This has been fixed.

27236217

Rated Event Loader Daemon did not process backlog files and went into sleep mode.

This has been fixed.

27244352

There was no option to disable journal creation for zero (0) balance records.

This has been fixed.

27263078

Duplicate events were created for the same period for cycle-forward products and the events did not have any balance impacts associated with them.

This has been fixed.

27266272

When PDC was used for configuring pricing objects, there was some issue in the Item Type Selector configuration due to format mismatch.

This has been fixed.

27269943

The host name was not validated properly during the BRM installation in silent mode.

This has been fixed.

27274074

The discount purchase operation was not considering the appropriate rate plan resulting in incorrect calculation of the discount period.

This has been fixed.

27274076

For time-based full discounts, BRM was incorrectly calculating the discount amount.

This has been fixed.

27277544

When a service configured to have only discounts was terminated, an error was thrown.

This has been fixed.

27288519

For accounts with multiple bill units, write off reversal was failing as the reversal items pointed to one bill unit.

This has been fixed.

27304029

Even if the log level was set to ERROR, some debug messages were getting recorded in the log files.

This has been fixed.

27304030

The value for the StopBillClosedAccounts business parameter was always getting set to 1 irrespective of the value specified.

This has been fixed.

27309569

The input data for the payment policy opcode, PCM_OP_PYMT_POL_PRE_REFUND, did not contain all the required information for policy processing.

This has been fixed.

27309573

The pin_deposit utility was not collecting pre-authorized charges.

This has been fixed.

27337657

When making adjustments, if the adjustment amount was more than the actual due amount, an inconsistent behavior was observed.

This has been fixed.

27362564

In Customer Center, when the permission to access account receivables (/accounttool/araccess) was set to read-only, the customer service representative (CSR) was not able to view the adjustment details from the Bill Details or Item Details page.

This has been fixed.

27369059

System discounts for cycle arrear events were not applied properly.

This has been fixed.

27389701

Web Services Manager was returning the Cannot initialize error when triggering the opcodes.

This has been fixed.

27415116

Rerating events after changing the accounting cycle day of month (DOM) was incorrectly impacting the balances.

This has been fixed.

27418546

The PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS opcode was not considering the latest or current hierarchy to calculate the amount due from aging buckets.

This has been fixed.

27425461

When installing BRM in silent mode, the response file required the database system user password which was a potential security risk.

This has been fixed.

27448146

When the billing delay was configured, auto-triggered billing from ECE was generating a final bill instead of a partial bill.

This has been fixed.

27463239

Launching Suspense Center with Java WebStart had issues due to the version mismatch between the shipped version (4.5.3) and the version specified (4.4) in the orasoft.jnlp file.

This has been fixed.

27463244

The General Ledger job was taking more time than expected and required a performance update.

This has been fixed.

27507372

When a product configured with the cycle arrear event was canceled with a backdated date, the refund was not applied properly.

This has been fixed.

27523584

Rerating after purchasing a discount was not working as expected.

This has been fixed.

27523592

When a child account was moved under a parent account, the usage charges were not included in the correct bill.

This has been fixed.

27539381

In some cases, while disconnecting a service, the PCM_OPCUST_SET_STATUS opcode was entering a deadlock.

This has been fixed.

27539388

If sequential discounting was enabled, the subscription discounting was getting applied on top of the system-level discount. This was causing errors in some scenarios.

This has been fixed.

27552474

During rerating, additional tax balance impacts were created. As a result, the adjustment calculated was incorrect.

This has been fixed.

27584537

Conversion Manager was not handling migration of accounts with quarterly bill cycles properly.

This has been fixed.

27591136

27738257

When event adjustment was done after tax-only adjustment, the tax jurisdiction information was not updated properly in the balance impact of the event adjustment.

This has been fixed.

27613611

27613617

28149096

Rated Event Loader (pin_rel) was exiting due to the out of memory error.

This has been fixed.

27613636

During cancellation of a product configured with in-advance billing, incorrect START_T and END_T were set in the events.

This has been fixed.

27621461

In Collections Manager, when an account had two bill units, a paying bill unit and a non-paying bill unit, the aging due was calculated incorrectly.

This has been fixed.

27667959

While recovering the failed payment, duplicate transaction IDs were observed and this was due to running two applications to recover the same failed payment, one was pin_recover and the other was a custom application, in parallel.

This has been fixed.

27667961

The General Ledger job was taking more time than expected and required a performance update.

This has been fixed.

27684532

In Collections Manager, if the PCM_OP_COLLECTIONS_GET_ACTION_HISTORY opcode was triggered with a transaction having a database number different from that of the collection event user, the opcode was failing.

This has been fixed.

27691744

For an account with multiple bill units, a payment reversal for a backdated account level payment was having effective date as the current system date instead of the back date.

This has been fixed.

27745481

The Oracle Data Manager process was failing with dumping core when processing the Account Receivables workflow.

This has been fixed.

27745484

BRM was not providing options to control or customize workflow over rerate requests which were created as part of subscription transfer operation.

This has been fixed.

27745489

When the EventAdjustmentDuringcancellation flag was enabled, the flist data corruption issue occurred intermittently, which was dumping core.

This has been fixed.

27751025

The PCM_OP_AR_RESOURCE_AGGREGATION opcode was returning incorrect aggregated amount.

This has been fixed.

27771916

The cancel discount operation was not setting the validity dates properly for discounts for which the end dates were in previous cycles.

This has been fixed.

27795345

If sequential discounting was enabled, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was not working properly for in-advance billing periods.

This has been fixed.

27816387

Even after paying the bill amount, the bill amount from the last bill was displayed as balance brought forward.

This has been fixed.

27881741

When an event was rerated twice, the tax jurisdiction was not handled properly for adjustment events.

This has been fixed.

27881743

When the same product was purchased twice, canceling one of the product deleted the provisioning tag from both the products.

This has been fixed.

27881746

For billing cycles which spans across multiple months, newsfeed was getting created for the /event/notification/service_item/make_bill event for each accounting cycle.

This has been fixed.

27891324

In a prepaid environment, when the subscriber's balance was lower than the required balance for a purchase and if a deal was purchased, BRM displayed the credit limit exceeded error. In addition, signal 11 was observed in Connection Manager.

This has been fixed.

27894048

The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan.

This has been fixed.

27894050

During item adjustment, the search operation got into a infinite loop.

This has been fixed.

27938633

The dm_fusa front end was not receiving data after the connection manager established connection with it.

This has been fixed.

27938637

It was not possible to locate the Secure Sockets Layer (SSL) client wallet file due to the use of back slash (\) in the resource path instead of a forward slash (/).

This has been fixed.

27938640

The PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode was not allowing to add or modify the event data in its workflow through the PCM_OP_BILL_POL_GET_EVENT_SPECIFIC_DETAILS policy opcode.

This has been fixed.

27956401

In Collections Manager, the collection write-off was failing for the bill unit in collection.

This has been fixed.

27979521

The PCM_OP_SEARCH base opcode was failing when the template included a nested select query with the grouping by clause.

This has been fixed.

27993358

During billing, the grantor information in the rollover bucket was incorrectly set to null.

This has been fixed.

27993360

In LDAP Manager, the entry update operation was failing.

This has been fixed.

28007850

When rating an event, sponsored products were ignored.

This has been fixed.

28020470

If a service had two products and when one product was canceled, the EFFECTIVE_T value of the service was also updated. This was not allowing the processing of usage events for the other product.

This has been fixed.

28089237

Quarterly cycles were getting merged which caused issues in applying charges.

This has been fixed.

28089239

The date format in Web Services Manager could not be configured based on the Java's SimpleDateFormat specification.

This has been fixed.

28119224

When in-advance billing was enabled, purchasing discount with a future date to become valid on ACTG_NEXT_T resulted in validation errors.

This has been fixed.

28123147

Conversion Manager was not providing an option to capture bill_accounting_cycles_left and next_bill_t information for migration.

This has been fixed.

28141241

The dm_ldap process was failing to start when SSL was enabled.

This has been fixed.

28141243

After loading the rated events from Pipeline Manager, it was found that MOD_T of the corresponding items and journals were less than the CREATED_T.

This has been fixed.

28159376

When an adjustment was applied in BRM, the revision number for the balance group was set incorrectly to zero causing data inconsistency between BRM and ECE.

This has been fixed.

28200056

After purchasing the monthly cycle forward product, the newsfeed for the same did not include the bill unit information.

This has been fixed.

28220691

When there were multiple bill adjustments, reallocation of the payment was done incorrectly.

This has been fixed.

28247287

The bill generated using Bill Now was not including all items due for billing.

This has been fixed.

28255178

Even if there was no amount left for adjustment, BRM was allowing adjustment up to the full adjustment amount.

This has been fixed.

28259108

When an APN Map was reloaded using a semaphore, the rating functionality did not consider the new APN Map configuration.

This has been fixed.

28261961

BRM was considering the regular monthly cycle forward event as backdated if the billing was run after the specified in-advance billing days in the same month.

This has been fixed.

28261967

For cycle forward events, having discounts the newsfeed functionality was not working.

This has been fixed.

28278327

Setting purchase start dates for first usage products was not allowed by using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode.

This has been fixed.

28281697

When BRM was processing orders by using JCA Adapter, if the CM instance goes down, the JCA Adapter was unable to restore the transaction state. As a result, the subsequent orders could not be processed without restart.

This has been fixed.

28334999

In case of sequential discounting, expired or ended discounts were also applied when new discounts were purchased.

This has been fixed.

28342603

When an account was created, the ACCOUNT_NO value was not updated correctly in the UNIQUE_ACCT_NO_T table.

This has been fixed.

28342608

The event adjustment for the product configured for deferred taxes was not updating the tax jurisdiction information in the balance impacts correctly.

This has been fixed.

28366495

There were memory leaks observed in the PCM_OP_TCF_AAA_STOP_ACCOUNTING opcode workflow.

This has been fixed.

28366497

There was a memory leaks observed in the op_tcf_aaa_search_session workflow.

This has been fixed.

28379547

In a BRM system integrated with ECE, External Manager (EM) Gateway was causing errors which led to data inconsistency.

This has been fixed.

28379549

When the updated pricing data was loaded using semaphore, the charges were calculated incorrectly.

This has been fixed.

28379551

With in-advance billing, the scale was calculated incorrectly as zero for a valid purchased product having an end date set.

This has been fixed.

28415082

The PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode was not canceling the deals from the existing plan while moving to the new plan.

This has been fixed.

28463456

The rerating flow was not updating the session_obj and rerated_obj information correctly.

This has been fixed.

28466613

When doing a plan transition, it was not possible to override the resource balance granted or add any custom workflow.

This has been fixed.

28359386

28359381

In Collections Manager, if schedule object was either completed or canceled, it was effective only for collection group owners, but not for members.

This has been fixed.

Customer-Reported Fixes in ECE

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

Customer-Reported Fixes in ECE 12.0 Patch Set 8

Table 1-9 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 8.

Table 1-9 Customer-Reported Fixes for ECE 12.0 Patch Set 8

Bug Number	Description
34141235 34258242	In previous releases, it was reported that additional, unnecessary SNRs were generated from ECE. This has been fixed. ECE generates the next SNR only after receiving an acknowledgment for the previous SNR with no connection loss.
34096234	In previous releases, the PARTITION_TIME column was not included in InvalidRatedEvent objects. This has been fixed.
33873681	In previous releases, the HTTP Gateway monitoring metrics did not include data for assessing the success or failure of charging requests. This has been fixed.
34136907	In the SLR flow, a NumberFormatException was reported for fields related to PendingPolicyCounter information. This has been fixed.
34017996	In previous releases, the 5G usage payload was failing when the time zone information included daylight saving time (DST) offset information in HTTP Gateway. This has been fixed.
34019605	The thread configuration for 5G unrated CDRs in the CDR Formatter required updates to improve performance. This has been fixed.
33941503	In previous releases, it was reported that some SNR notifications included expired balances. This has been fixed.
33997433	In previous releases, unrated CDR file names included only starting and ending timestamp information. This has been fixed. Unrated CDR file names now also include the cluster name and sequence number.
34058036 34312618	Automatic top-up functionality was enabled through non-counter grants during an on-going session. This is now similar to recurring bundle grants, so that it is available for all other parallel sessions immediately after the grant.
34073280	In previous releases, used service units rating was considering an additional 1 byte while processing the request. This has been fixed.
34021930	In previous releases, in a multi-RUM scenario, a TTC was generated incorrectly when just one of the RUMs was used. This has been fixed.
34012910	To improve CDR Formatter performance, the ECE 5G CDR session store has been enhanced with updated table definitions and additional index definitions.
34064745	In previous releases, performance issues were reported for 5G usage processing. This has been fixed with additional index definitions.
34121619	In previous releases, the realm and host information was not configurable for a multi-site deployment of ECE Diameter Gateway. This has been fixed.
34139881	In previous releases, breach notifications were not replicated to all members in a discount sharing group. This has been fixed.
34136087	In previous releases, the FINAL trigger was not supported at the rating group level. This has been fixed.
34145186	In previous releases, in some instances pending policy status calculation was done using incorrect balance information. This triggered unnecessary notifications. This has been fixed.
34090990	In previous releases, for 5G offline requests, it was required that the subscriber account be present in the BRM system. However, this is not true for an in-roaming subscriber. This has been fixed.
34103112	In previous releases, 5G offline requests were processing within the ECE charging grid, even if only unrated CDRs were to be generated for such requests. This has been fixed.
33878964	In previous releases, OCOMC ECE DC was not able to register or initialize due to missing monitor framework updates. This has been fixed.
34341927	In previous releases, when HTTP Gateway was processing 5G usage requests, it sometimes missed the generation of unrated CDRs or generated duplicate CDRs for concurrent requests. This has been fixed.
33062444	In previous releases, when the ECE persistence database was down, the usage charging flow involving conditional RUMs was delayed or there was no response in the charging flow back to the CTF. This has been fixed.
34400697	Thread leaks were reported in the purge rated events workflow. This has been fixed.
34380199	In previous releases, when creating new AVPs from the extensions API, the AVPs of type Enum were getting created as DiameterInteger32 instead of DiameterEnumerated. This has been fixed.
34000658	In previous releases, unrated CHF CDR generation was not supporting failover scenarios for a multi-site deployment. This has been fixed.
33972900 34746451	In previous releases, the validity time was not aligned with GSU for dynamic quota configuration. This has been fixed.
34401823	In previous releases, on multi-site active-active deployments, during customer loading from the BRM database to the ECE cache through Customer Loader or Customer Updater, the customers were not segregated into groups. This has been fixed.
34469111	In previous releases, in the charging flow, impacting for the consumed reservation was incorrectly done if the consumption was from a topped-up balance. This has been fixed.
34317216	In previous releases, for an ECE cloud native multi-site active-active deployment, both Pricing Updater and Customer Updater pods were started only in the primary site and not started in the remaining sites. This has been fixed.
34217563	In previous releases, when a session was in progress, balance updates were incorrect when a member was added or removed from a discount sharing group (DSG). This has been fixed.
34402458	In previous releases, some deployments of Coherence federation reported a destination error. This was due to thread leaks and fixed through Bug 34400697.
34211050	In previous releases, after a member was added to a discount sharing group, an SNR was not generated for any policy counter updates in member bundles. This has been fixed.
34205430	In previous releases, the same policy counter was being returned multiple times in an SLA. This has been fixed.
34262280	In previous releases, when multiple SNRs were sent for a policy counter during an ongoing session, IO timeout errors were reported. This has been fixed.
34310172	In previous releases, when a plan was about to expire, ECE was sending an incorrect validity time, without considering the end time of all applicable offers to evaluate the validity time for the request. This has been fixed.
34325037	In previous releases, 5G CHF (HTTP Gateway) was sending RARs using the Notify URI instead of the SCP URL configured in scpAuthorities. This has been fixed. Additionally, the notify URI is set in the header as "3gpp-Sbi-Target-apiRoot" and "user-agent" = "CHF".
34800211	In previous releases, the Tariff Time Change (TTC) was not reported in UTC. This has been fixed.
34777745	In previous releases, when a connectivity issue was experienced between 5G CHF (HTTP Gateway) and NRF, HTTP Gateway was retrying NRF Heartbeat for a preconfigured number of times. But, if the number of instances was just one, an option was required to retry until NRF was operational again. HTTP Gateway has been enhanced to support this now.
33909430	In previous releases, due to a mismatch in the currency balance element range between ECE and BRM, ECE was reporting a version mismatch. This has been fixed.
34698228	In previous releases, for an ECE active-active deployment, the Rated Event Formatter (REF) was failing on site 2 (secondary). This has been fixed.
34638932	In previous releases, 5G CHF (HTTP Gateway) was failing when the charging request included a null USU after the previous request included a closure trigger. This was also failing during the unrated CDR generation. This has been fixed.
34488077	In previous releases, in the rerating flow, impact category information was incorrectly populated as null. This has been fixed.
34049315	In previous releases, 5G unrated CDR generation did not have configuration for the Kafka topic name, number of partitions, SSL security, and compression methods. CDR generation has been enhanced to support this functionality. The configuration now also includes the wallet location and the TrustStore location.
34766318 34723470	In previous releases, for an active-active mode of ECE, the customer group list was not added during the deployment. This has been fixed.
34617995	In previous releases, during the charging flow, the UNIX epoch time-to-date conversion was incorrectly done for earliest-expiry-time. This has been fixed.
34693587	In previous releases, while processing charging requests, the routing data was set incorrectly and hence HTTP Gateway was unable to consume SNRs from ECS. This has been fixed.
34692273	In previous releases, first usage notifications were generated twice for the same subscriber. This has been fixed.
34483124	In previous releases, SNRs were not generated for parent accounts in a discount sharing group. This has been fixed.
34692304	In previous releases, the GSU calculation logic was incorrect. This has been fixed.
34627786	In previous releases, 5G CHF (HTTP Gateway) was not retrying NRF Heart Beat requests in case of any network exception. This has been fixed to retry for a configured number of times based on nrfHeartBeatRetryCount.
34542607	In previous releases, SNRs were not getting generated for a member of a discount sharing group when the member was deleted. This has been fixed.
34235570	In previous releases, the Tariff Time Change scenario was missing a reservation on the current bill cycle. This has been fixed.
34633958	In previous releases, 5G charging requests were failing with incorrect validation of volumeLimit trigger. This has been fixed.
34658482	In previous releases, 5G charging requests were failing at CDR Gateway for a Release request without Used Service Units information. This has been fixed.
34637428	In previous releases, it was observed that whenever a CCR-Update Request having USU=0 was received, ECE was adding an extra 10 bytes to the next Granted Service Units (GSU). This issue was observed in roaming zones, and when the rateZeroQuantity parameter was set to true in charging-settings.xml. This has been fixed.
34505169 34664433	In previous releases, the new automatic top-up bucket was not created when usage occurred during the last minute of the current bucket's validity. This has been fixed.
34247534	In previous releases, there was a discrepancy between the amount of reserved units and the Granted Service Units (GSU). This has been fixed.
34577587	In previous releases, for a multi-site active-active deployment of ECE, when a usage charging session was initiated in site 2, an SNR was generated and sent to the Kafka partition assigned to Diameter Gateway in site 2. However, it was observed that the SNR was picked up by Diameter Gateway in site 1. This has been fixed.
34527516	In previous releases, you started a session and triggered SLR through PCRF in Site1 to Diameter Gateway in site 1, and after some updates, you triggered STR through PCRF in Site 2 to Diameter Gateway in site 1. Then, Diameter Gateway in site 1 was responding with an STA to Site 1 instead of site 2, because Diameter Gateway was fetching the PCRF host from the session instead of the STR input. This has been fixed.
34569302	In previous releases, the Rated Event Formatter (REF) was not starting due to the incorrect mapping of the persisted_field and persisted_field_5g fields in the request specification. This has been fixed.
34589041	In previous releases, when nonlinear rating was configured, the Eval function defined in the pre-rating extension was not evaluated correctly. This was because any change due to the extension logic was not overriding the charging request's payload. This has been fixed.
34589097	In previous releases, when zeroRatedQty was enabled and incorrectly a midsession request for a termination came in, the request was failing. This is fixed now, with a check for not creating a mid session for terminate request.
34497871	In previous releases, when 5G CHF (HTTP Gateway) was processing multiple parallel charging requests, there was inconsistency in CDR generation. it was observed that multiple CDRs were of the same content. This has been fixed.
34614000	In previous releases, for a charging session with multiple rating groups, while generating a midsession CDR for a CCR update request with just one rating group, the midsession CDR was generated with just one rating group instead of all rating groups impacted by the session. This has been fixed.
34589076	In previous releases, while consuming data fully for a resource, reverse rating was failing with a null pointer exception. This has been fixed.
34567566	In previous releases, the consumed reservation calculation was incorrect for an update request due to rounding of used service units to the beat. This has been fixed.
34717616	In previous releases, for an ECE deployment with cache persistence configuration enabled, if the tax selectors were updated when the ECE database was down, usage processing was failing. This has been fixed.
34624902	In previous releases, Diameter Gateway was not consuming RAR notifications from Kafka topics. This has been fixed.
34697193	In previous releases, when ECE rated usage, subbalance impacts were created even for zero currency impacts for loan balances. This has been fixed.
34673867	ECE has been enhanced to provide an API to access the debit refund session list that can be used in the extension hooks for customizations.
34613541	The balance output map was having loan and current amounts as null. This has been fixed.
34602911	The balance query through Diameter Gateway was returning incorrect information when the balance item subtype was not set. This has been fixed.
34606521	For a CCR request with TTC enabled, the granted service units were incorrectly calculated. This has been fixed.
34652879	In previous releases, there was an issue with dynamic credit floors. This has been fixed to consider the sum of original granted balances at a given time as the dynamic floor.
34236341	In previous releases, there was no DSL support for lifecycle expiration dates. This has been fixed.
34700667	In previous releases, ECE was creating subbalance buckets with zero amounts. This has been fixed.
34760612	In a multischema deployment, when ECE was processing ProductInfoChange events through Customer Updater, the request was timing out in ECE. This has been fixed.
34810673	In previous releases, when processing a usage request, the used service units quantity was not getting rounded. This has been fixed.
34779306	It was observed that the error bit was not set in the Diameter CCA header for all protocol errors. This has been fixed.
34818739	In previous releases, for a tariff time change (TTC) scenario, the information for pre-TTC was not completely provided. This has been fixed.
34236998	In previous releases, when a Diameter client was sending a request for CER, the Diameter Gateway pod was not sending any response when an incorrect realm and origin host was used. This has been fixed. A message will now be logged when a correct realm and origin host are not used.
34796483	When processing delayed usage, the balance subtype set was incorrectly in rated events for loan balances. This has been fixed.
34711900	In ECE cloud native deployments, while processing incremental loading, the ece-preselect container was failing with an error as it could not process JDBC URL. This has been fixed.
34711877	In ECE cloud native deployments, loadCrossRefData logic was not included in the Customer Loader template. This has been fixed.
34862738	In previous releases, if the usage session arrived soon after the cycle boundary, and if the cycle fee processing was not complete in BRM, the charging workflow was not able to reserve from the correct balance bucket. This led to errors in resource quota management and consumption. This has been fixed by triggering the cycle fees from ECE and using the latest cycle grants for quota.
34397942	In previous releases, ECE did not cache the bundle/deal name and ID information, and then make it available to enrich rated events or notifications. This has been fixed. Now, the bundle/deal name and ID are accessible from the extension layer.
34184725	In previous releases, Diameter Peer Requests (DPRs) were not consistently answered by Diameter Gateway. This has been fixed.
34483649	In previous releases, the opcode call to PCM_OP_BAL_ECE_GET_BALANCES was not including loan balance information in the output. This has been fixed.
34543881	A null pointer exception was reported in IsBalanceUpdateRarGenerationQueryImpl, which was not handled. This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 7

Table 1-10 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 7.

Table 1-10 Customer-Reported Fixes for ECE 12.0 Patch Set 7

Bun Number	Description
33831830	In previous releases, you could not extend first-usage notifications in the post-charging workflow. ECE has been enhanced to support this.
33844645	CustomerPartitionSchemaMapping was updated even for single-schema deployments, which was not necessary. This has been fixed. A check for multischema has been added in the update flow for handling the CustomerPartitionSchemaMapping cache priming.
33629694	When there were multiple rating groups in a 5G online charging request, the quota reservation was not done correctly for granting units. This has been fixed.
33819713	When there were multiple used units in an offline-only charging request, HTTP Gateway was not mapping to the correct used units in ECE. This has been fixed.
33813619	In an active-active deployment, both primary and secondary instances of Rated Event Formatter were incorrectly configured to run on the same site. This has been fixed.
33769884	The 5G CHF CDRs generated by the CHF were missing certain attributes and the values of a few attributes were incorrect. This has been fixed.
33713970	Whenever the balance validity was updated in BRM, it was not synchronized correctly with ECE through EM Gateway. This has been fixed.
33773457	Diameter Gateway was not sending the URL redirection until a sufficient resource balance existed. This has been fixed.
33731809	The granted service units was incorrect when the reservation was from a single balance bucket. This has been fixed.
33770240	For 5G charging, multiple usage units were incorrectly considered mandatory. This has been fixed.
33745974	When a non-counter grant was done during discounting, the grant was not visible across sessions. This has been fixed.
33730620	For 5G charging, the policyCounterIds were kept incorrectly mandatory. This has been fixed.
33729723	For 5G charging, only one CHF instance was allowed to register with an NRF. Now, multiple CHFs can register with the same NRF.
33729402	For 5G charging, the multipleUnitUsage.usedUnitContainer.serviceId field was incorrectly considered mandatory. This has been fixed.
33704854	When a balance update was done on the BRM side for a customer, the balance was not synchronized to ECE and a Coherence error occurred. This has been fixed.
33697580	For 5G charging, the quotaManagementIndicator data type was incorrect. This has been fixed.
33606758	In an ECE active-active deployment, threshold breaches on an active site were not federated in decorative mode to the second site. This has been fixed.
33563419	During the charging process, ECE was not supporting and evaluating TotalC in Threshold_To expressions. This has been fixed.
33730943	In an ECE cloud native deployment, the PodHealthCheck process was creating orphan processes. This has been fixed.
33731972	In an ECE cloud native deployment, the cluster configuration was assuming a hard-coded name and was not allowing users to change it as required by the deployment. This has been fixed.
33734441	The ECE cloud native deployment was failing in interim patch 3 due to missing JAR files. This has been fixed.
33696433	The CHF was registering only for the Nchf_ConvergedCharging service with the NRF instance, and the Nchf_SpendingLimitControl service was omitted in the list of configured services. This has been fixed.
33814780	For 5G charging, ECE was not supporting tariff time change triggers in charging requests. This has been fixed.
33629355	For 5G charging, ECE was not using the quota management indicator to determine if a converged charging request contained online charging, offline charging, or both. This has been fixed.
33967432	HTTP Gateway was having issues in thread handling that was generating a huge number of threads. This has been fixed.
33892939	CHF CDRs generated by ECE had format-related issues specified by the 3GPP specifications. This has been fixed.
33646227 31338683	In ECE during usage processing, when a generic selector was not evaluating to any rule, a success was returned instead of a failure with the reason as NO_RATING_GRAPH_CONFIGURED. This has been fixed.
33969575	Automatic top-up grants were not handled correctly when there were tariff-time changes. This has been fixed.
33966053 33831757	Non-counter grants with an automatic top-up was not immediately recognized across all parallel on-going sessions. This has been fixed.
33902616	Threshold breach notifications were not replicated for child accounts in a discount sharing group. This has been fixed.
33963284	The PUID information was not properly updated in SNRs. This has been fixed.
33951010	Top-up bundle purchases were failing when the subscriber had both primary and secondary subscriptions. This has been fixed.
33873603	For 5G deployments, you could not register multiple HTTP Gateway instances with an NRF. This has been fixed.
33883486 33872083	HTTP Gateway was sending null-valued attributes for NRF registration, which caused a registration error. This has been fixed.
33935343	When a first-usage validity notification was generated, it was not replicated to all members in the subscription group. This has been fixed.
33764005	In ECE, the redirection DSL was not reading the correct data in case of an override in the payload. This has been fixed.
33267357	The RUM quantities were incorrectly updated when non-linear rating was enabled and when evaluating beat scenarios. This has been fixed.
33964143	The active session object cleanup parameter was missing from the cloud native deployment templates for ECE. This has been fixed.
33955909	ECE was allowed to generate custom SNRs in the usage flow extension points. This has been fixed.
33812526	In ECE, a NullPointerException was thrown when a tariff-time change was being processed with non-linear rating enabled. This has been fixed.
33929321	For a subscriber having a plan that was about to expire, any new session that was started or any update to an ongoing session just before the expiration, the validity time that was set in the response was later than the plan expiration time. This has been fixed.
33936076 32258304	Value maps were not accessible in pre-rating extensions, and DSL optimization was required during selector evaluation. This has been fixed.
34245333	In rated events, the sub-type values for loan balances and main balances were incorrect. This has been fixed.
33864314 33613568	ECE was generating RARs with Service ID and Rating Groups, which was having issues when there were active sessions with multiple different Rating Groups. This has been fixed. Now this has been fixed to generate an RAR without Service ID and Rating Groups so that it is honored by all active sessions for all Rating Groups.
34301863	Rated events were not including a customer's main balance and loan balance information. This has been fixed.
34185865	In ECE, bundles that expired out of billing cycles were not getting their grants replenished. With this release, ECE triggers cycle-forward fees calculation for grants through the offers that do not coincide with the billing cycle date.
34136283	The service expiration time was not synchronized from BRM to ECE through Customer Updater and EM Gateway. This has been fixed.
34185917	ECE was allowing the configuration of non-linear rating at the product-type level. This has been fixed.
34185968	The ECE customer cache was not including additional data, such as the deal ID, bundle ID, and name as part of purchased offerings. Due to this, it was not possible to include these details in rated events or notifications through extensions. This has been fixed.
34194932	In ECE, loan balances were not considered for consumption prior to main balance consumption. This has been fixed.
34174335	As part of balance synchronization with BRM, if the balance item type was not synchronized, the balance query and other balance-related operations were incorrect. This has been fixed. ECE now considers the balance item type as the main balance if it is not explicitly indicated with the balance type attribute.
33570517	The balance query operation was not returning life-cycle state information, such as the service expiration time. This has been fixed.
34323608	In ECE Patch Set 6, HTTP Gateway had a memory management issue. This has been fixed.
34141235	ECE was sending the next SNR before the response for the previous SNR was received from the network, which is contrary to 3GPP specifications. This has been fixed. ECE now waits for the previous SNR response before sending the next SNR.
34096234	The PARTITION_TIME column was not available in the InvalidRatedEvent table definition. This has been fixed.
33873681	In previous releases, ECE was not providing HTTP Gateway-related metrics. This has been fixed.
34136907	During the Sy SLR flow, ECE was generating a NumberFormatException for using an incorrect data type for an attribute. This has been fixed.
34017996	During 5G usage processing, a failure was reported when a request included a date field with a time zone having day light savings. This has been fixed.
34019605	5G CHF CDR Formatter was having some performance issues and required an optimized thread management. This has been fixed.
33941503	SNR notifications were generated based on available balances that incorrectly included expired balances. This has been fixed.
33997433	The 5G CHF CDR file naming syntax required an update. The file name syntax now includes the cluster name, starting time stamp, ending time stamp, and sequence number (ClusterName-StartTimeStamp-EndTimeStamp-SequenceNumber.Extension). For example: BRM-1654514133000-1654514134000-1.out.
34058036	Automatic top-up grants were not handled correctly for accounts configured with discount sharing group. This has been fixed.
34073280	While calculating the used and consumed units, a difference of one byte was encountered. This has been fixed.
34021930	Tariffs were evaluated to true even when the daily bundle charge rate plan was not applicable for a given usage request. This was also leading to creating multiple time points for TTC that were not actually applicable. This has been fixed.
34012910 34064745	The 5G CHF CDR Generator required performance improvements with database indexes.
34121619	In an active-active set up of Diameter Gateway, the realm and host configurations were incorrect. This has been fixed.
34139881	Threshold breach notifications were not triggered for all member accounts in a discount sharing group. This has been fixed.
34136087	For 5G usage rating requests that included multiple rating groups, the FINAL trigger was not supported. Instead, the granted service units was provided in the response. This has been fixed.
34145186	The pending policy counter was incorrect for SNRs that were triggered after purchasing certain bundles. This has been fixed.
34090990	In ECE, 5G offline charging was failing for usage requests for in-roaming subscribers, causing CDRs to not be generated. This has been fixed.
34103112	In ECE, every request was sent to charging irrespective of whether it required online or offline charging. This has been fixed. You can now configure whether to rate offline requests in ECE.
33878964	There was an initialization error for ECE Distribution Cartridge (DC) to work with ECE due to missing monitor framework dependency. This has been fixed.

Bun Number

Description

33831830

In previous releases, you could not extend first-usage notifications in the post-charging workflow.

ECE has been enhanced to support this.

33844645

CustomerPartitionSchemaMapping was updated even for single-schema deployments, which was not necessary.

This has been fixed. A check for multischema has been added in the update flow for handling the CustomerPartitionSchemaMapping cache priming.

33629694

When there were multiple rating groups in a 5G online charging request, the quota reservation was not done correctly for granting units.

This has been fixed.

33819713

When there were multiple used units in an offline-only charging request, HTTP Gateway was not mapping to the correct used units in ECE.

This has been fixed.

33813619

In an active-active deployment, both primary and secondary instances of Rated Event Formatter were incorrectly configured to run on the same site.

This has been fixed.

33769884

The 5G CHF CDRs generated by the CHF were missing certain attributes and the values of a few attributes were incorrect.

This has been fixed.

33713970

Whenever the balance validity was updated in BRM, it was not synchronized correctly with ECE through EM Gateway.

This has been fixed.

33773457

Diameter Gateway was not sending the URL redirection until a sufficient resource balance existed.

This has been fixed.

33731809

The granted service units was incorrect when the reservation was from a single balance bucket.

This has been fixed.

33770240

For 5G charging, multiple usage units were incorrectly considered mandatory.

This has been fixed.

33745974

When a non-counter grant was done during discounting, the grant was not visible across sessions.

This has been fixed.

33730620

For 5G charging, the policyCounterIds were kept incorrectly mandatory.

This has been fixed.

33729723

For 5G charging, only one CHF instance was allowed to register with an NRF.

Now, multiple CHFs can register with the same NRF.

33729402

For 5G charging, the multipleUnitUsage.usedUnitContainer.serviceId field was incorrectly considered mandatory.

This has been fixed.

33704854

When a balance update was done on the BRM side for a customer, the balance was not synchronized to ECE and a Coherence error occurred.

This has been fixed.

33697580

For 5G charging, the quotaManagementIndicator data type was incorrect.

This has been fixed.

33606758

In an ECE active-active deployment, threshold breaches on an active site were not federated in decorative mode to the second site.

This has been fixed.

33563419

During the charging process, ECE was not supporting and evaluating TotalC in Threshold_To expressions.

This has been fixed.

33730943

In an ECE cloud native deployment, the PodHealthCheck process was creating orphan processes.

This has been fixed.

33731972

In an ECE cloud native deployment, the cluster configuration was assuming a hard-coded name and was not allowing users to change it as required by the deployment.

This has been fixed.

33734441

The ECE cloud native deployment was failing in interim patch 3 due to missing JAR files.

This has been fixed.

33696433

The CHF was registering only for the Nchf_ConvergedCharging service with the NRF instance, and the Nchf_SpendingLimitControl service was omitted in the list of configured services.

This has been fixed.

33814780

For 5G charging, ECE was not supporting tariff time change triggers in charging requests.

This has been fixed.

33629355

For 5G charging, ECE was not using the quota management indicator to determine if a converged charging request contained online charging, offline charging, or both.

This has been fixed.

33967432

HTTP Gateway was having issues in thread handling that was generating a huge number of threads.

This has been fixed.

33892939

CHF CDRs generated by ECE had format-related issues specified by the 3GPP specifications.

This has been fixed.

33646227

31338683

In ECE during usage processing, when a generic selector was not evaluating to any rule, a success was returned instead of a failure with the reason as NO_RATING_GRAPH_CONFIGURED.

This has been fixed.

33969575

Automatic top-up grants were not handled correctly when there were tariff-time changes.

This has been fixed.

33966053

33831757

Non-counter grants with an automatic top-up was not immediately recognized across all parallel on-going sessions.

This has been fixed.

33902616

Threshold breach notifications were not replicated for child accounts in a discount sharing group.

This has been fixed.

33963284

The PUID information was not properly updated in SNRs.

This has been fixed.

33951010

Top-up bundle purchases were failing when the subscriber had both primary and secondary subscriptions.

This has been fixed.

33873603

For 5G deployments, you could not register multiple HTTP Gateway instances with an NRF.

This has been fixed.

33883486

33872083

HTTP Gateway was sending null-valued attributes for NRF registration, which caused a registration error.

This has been fixed.

33935343

When a first-usage validity notification was generated, it was not replicated to all members in the subscription group.

This has been fixed.

33764005

In ECE, the redirection DSL was not reading the correct data in case of an override in the payload.

This has been fixed.

33267357

The RUM quantities were incorrectly updated when non-linear rating was enabled and when evaluating beat scenarios.

This has been fixed.

33964143

The active session object cleanup parameter was missing from the cloud native deployment templates for ECE.

This has been fixed.

33955909

ECE was allowed to generate custom SNRs in the usage flow extension points.

This has been fixed.

33812526

In ECE, a NullPointerException was thrown when a tariff-time change was being processed with non-linear rating enabled.

This has been fixed.

33929321

For a subscriber having a plan that was about to expire, any new session that was started or any update to an ongoing session just before the expiration, the validity time that was set in the response was later than the plan expiration time.

This has been fixed.

33936076

32258304

Value maps were not accessible in pre-rating extensions, and DSL optimization was required during selector evaluation.

This has been fixed.

34245333

In rated events, the sub-type values for loan balances and main balances were incorrect.

This has been fixed.

33864314

33613568

ECE was generating RARs with Service ID and Rating Groups, which was having issues when there were active sessions with multiple different Rating Groups.

This has been fixed. Now this has been fixed to generate an RAR without Service ID and Rating Groups so that it is honored by all active sessions for all Rating Groups.

34301863

Rated events were not including a customer's main balance and loan balance information.

This has been fixed.

34185865

In ECE, bundles that expired out of billing cycles were not getting their grants replenished.

With this release, ECE triggers cycle-forward fees calculation for grants through the offers that do not coincide with the billing cycle date.

34136283

The service expiration time was not synchronized from BRM to ECE through Customer Updater and EM Gateway.

This has been fixed.

34185917

ECE was allowing the configuration of non-linear rating at the product-type level.

This has been fixed.

34185968

The ECE customer cache was not including additional data, such as the deal ID, bundle ID, and name as part of purchased offerings. Due to this, it was not possible to include these details in rated events or notifications through extensions.

This has been fixed.

34194932

In ECE, loan balances were not considered for consumption prior to main balance consumption.

This has been fixed.

34174335

As part of balance synchronization with BRM, if the balance item type was not synchronized, the balance query and other balance-related operations were incorrect.

This has been fixed. ECE now considers the balance item type as the main balance if it is not explicitly indicated with the balance type attribute.

33570517

The balance query operation was not returning life-cycle state information, such as the service expiration time.

This has been fixed.

34323608

In ECE Patch Set 6, HTTP Gateway had a memory management issue.

This has been fixed.

34141235

ECE was sending the next SNR before the response for the previous SNR was received from the network, which is contrary to 3GPP specifications.

This has been fixed. ECE now waits for the previous SNR response before sending the next SNR.

34096234

The PARTITION_TIME column was not available in the InvalidRatedEvent table definition.

This has been fixed.

33873681

In previous releases, ECE was not providing HTTP Gateway-related metrics.

This has been fixed.

34136907

During the Sy SLR flow, ECE was generating a NumberFormatException for using an incorrect data type for an attribute.

This has been fixed.

34017996

During 5G usage processing, a failure was reported when a request included a date field with a time zone having day light savings.

This has been fixed.

34019605

5G CHF CDR Formatter was having some performance issues and required an optimized thread management.

This has been fixed.

33941503

SNR notifications were generated based on available balances that incorrectly included expired balances.

This has been fixed.

33997433

The 5G CHF CDR file naming syntax required an update.

The file name syntax now includes the cluster name, starting time stamp, ending time stamp, and sequence number (ClusterName-StartTimeStamp-EndTimeStamp-SequenceNumber.Extension). For example: BRM-1654514133000-1654514134000-1.out.

34058036

Automatic top-up grants were not handled correctly for accounts configured with discount sharing group.

This has been fixed.

34073280

While calculating the used and consumed units, a difference of one byte was encountered.

This has been fixed.

34021930

Tariffs were evaluated to true even when the daily bundle charge rate plan was not applicable for a given usage request. This was also leading to creating multiple time points for TTC that were not actually applicable.

This has been fixed.

34012910

34064745

The 5G CHF CDR Generator required performance improvements with database indexes.

34121619

In an active-active set up of Diameter Gateway, the realm and host configurations were incorrect.

This has been fixed.

34139881

Threshold breach notifications were not triggered for all member accounts in a discount sharing group.

This has been fixed.

34136087

For 5G usage rating requests that included multiple rating groups, the FINAL trigger was not supported. Instead, the granted service units was provided in the response.

This has been fixed.

34145186

The pending policy counter was incorrect for SNRs that were triggered after purchasing certain bundles.

This has been fixed.

34090990

In ECE, 5G offline charging was failing for usage requests for in-roaming subscribers, causing CDRs to not be generated.

This has been fixed.

34103112

In ECE, every request was sent to charging irrespective of whether it required online or offline charging.

This has been fixed. You can now configure whether to rate offline requests in ECE.

33878964

There was an initialization error for ECE Distribution Cartridge (DC) to work with ECE due to missing monitor framework dependency.

This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 6

Table 1-11 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 6.

Table 1-11 Customer-Reported Fixes for ECE 12.0 Patch Set 6

Bug Number	Description
33829559	The following issues were reported while generating a CHF CDR: The Record Type and Rating Indicator tags were not populated. A negative duration was reported in the CHF CDR. The record sequence number and local sequence number values were incorrect in CHF CDRs. The totalVolume value was populated incorrectly. These have been fixed.
33985970	The following issues were reported while generating a CHF CDR: The sequence number fields (LocalRecordSequenceNumber, LocalSequenceNumber, and RecordSequenceNumber) were not incrementing correctly as defined in the 3GPP specifications. External trigger details for some CDRs were not populated even though causeOfRecordClosing was correctly mentioned. These have been fixed.
33809523	Reservations were made incorrectly when a 5G HTTP request for converged charging included multiple rating groups. This has been fixed.
33985962	When an account purchased a charge offer that included usage charges for which charging is based on a generic selector, Diameter Gateway usage processing returned an incorrect status. This has been fixed.
33834862	It was not possible to get a first usage notification service context in the post charging extension. This has been fixed.
33828497	Defunct processes from the ECE Pod health check were blocking worker nodes, because the parent process did not correctly handle child process termination. This has been fixed.
33794316	In an active-active DR setup, threshold breach and aggregated threshold breach events were not getting federated across sites. This has been fixed.
33880713	In an ECE setup with non-linear rating enabled, errors occurred while processing usage requests. When the period field in a balance item impact was NULL, ECE threw a NULL pointer exception. This has been fixed.
33724587	After deploying ECE in a cloud native environment, ECE was not connecting to JConsole. This has been fixed.
33828481	The installation of ECE 12.0 Patch Set 4 Interim Patch 3 in a cloud native environment was failing due to missing JAR files. This has been fixed.
33742497	When a balance update was published to ECE from BRM, ECE was returning a Coherence error. This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 5

Table 1-12 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 5.

Table 1-12 Customer-Reported Fixes for ECE 12.0 Patch Set 5

Bug Number	Description
33661199	The following issues were reported on 5G CHF HTTP Gateway functionality: The HTTP Gateway was checking if CHF was already registered before reregistering, which was an unnecessary step. The HTTP Gateway was not sending a correct header for the Nchf_ConvergedCharging_Create operation. If an attribute in the JSON payload had a NULL string, NRF did not process the request. The data type for pDUSessionChargingInformation.chargingId was incorrectly set to integer instead of unsigned integer. If a request had multiple rating groups, the HTTP Gateway was not reserving quota correctly. These issues have been fixed.
32311282	Performance issues occurred during the clean up of active session objects. This has been fixed. Also, a validation on the product ID was introduced.
33294593	There was no service to connect to JConsole from an ECE cloud native deployment. This has been fixed.
32665703	RADIUS Gateway was not handling access requests that required the PBKDF2 algorithm. This has been fixed.
32647547	While transferring a service from one account to another, the item POID for the service from the old account was also transferred to the new account. This caused the usage for the new account to be incorrectly recorded for the old account. This has been fixed.
33291753	After a service was transferred to a new billing account, usage charges were still rolling up to the old billing account. This has been fixed.
33189250	There were cluster timeouts in an active-active setup configuration followed by ConcurrentModificationException. This has been fixed.
33436905	The CustomerUpdater was crashing due to data inconsistencies even when the continueCustomerLoaderOnError flag was enabled. This has been fixed.
33249239	The subscriber tracing functionality was not working during usage processing even after enabling it. This has been fixed.
33249243	The group notifications feature was not working properly due to thread deadlocks. This has been fixed.
33249242	Readiness probes were not available for EM Gateway, RADIUS Gateway, and Diameter Gateway services. This has been fixed. Readiness probes have been added to these gateways. The probes indicate that a Pod is ready when its ports are open and ready to accept connections.
33189231	First usage validity was not working because the calculated validity was incorrect. This has been fixed.
33331310	For GPRS events, both INVOICE_DATA and RUM_NAME were populated incorrectly when it was set in the post rating extension hooks. This has been fixed.
33372715	During rerating, a rating error occurred for an account with grants and usages. This has been fixed.
33373301	While rating the last chunk of used units, Diameter Gateway generated a DIAMETER_CREDIT_LIMIT_REACHED error if there was no balance available to determine the requested units. This has been fixed.
33459324	When a SIM was changed, there was an issue fetching the product information that caused a DIAMETER_RATING_FAILED error. This has been fixed.
33114726	In ECE cloud native deployments, a SSL handshaking issue with BRM server occurred. This has been fixed.
33658703	When a balance was exhausted and a new usage request arrived, Diameter Gateway was generating a DIAMETER_CREDIT_LIMIT_REACHED (4012) error rather than generating a Final Unit Indicator (FUI). This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 4

Table 1-13 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 4.

Table 1-13 Customer-Reported Fixes for ECE 12.0 Patch Set 4

Bug Number	Description
31837847	When diameter gateways were shut down after a failure of an Elastic Charging Server, the gateways could not be restarted until the Elastic Charging Server and processes were started. This has been fixed.
32085459	After deploying ECE patch 11.3.0.8.10, duplicate usage requests were failing. This has been fixed.
31984386	After upgrading to ECE patch 11.3.0.9.10, invoice generation was failing. This was because the net_quantity field was not being updated when usage events were generated. This has been fixed.
31843322	While while synchronizing data from BRM to ECE for creating customers or billing and while members or a sharing group generated usage at the same time, transaction locks were resulting in 5012 errors, and services could not be used. This has been fixed. When an impacted account is in a transaction lock and then placed in the resubmit queue, a sleep is introduced. When the resubmit times out, a response with error code 4010 is returned.
32960759	Diameter gateway was timing out after 10 second when performing duplicate checks. This was because of Elastic Charging Server failures during the duplicate check. This has been fixed.
32647547	During usage rating, services that had been transferred from one account the another were still tagged with the old account. This was because IPL and NIPL were not fetched during the transfer, so charges were routed to the old items. This has been fixed.
32258295	When increase balance impacts were added to a counter with no credit limit or monetary balances changed, the SafetyNet based on the return value from getAvailableBalance method was not working. This has been fixed. A new getAvailableBalanceUpToCreditLimit method is now accessible through the getBalance() interface in PostRatingExtension.
33022624	For online usage UPDATE requests, when data bucket is completely consumed, QuotaHoldingTime (QHT) is being reported even though GrantedServiceUnit (GSU) is not set. This has been fixed.
32996820	When a new customer was created with a recycled MSISDN and a new family sharing plan was purchased in the same transaction, the sharing group creation and family sharing plan purchase was failing. This was because the AlterationSharingAgreement was updated in the old account and not the new account. This has been fixed
31571808	When requests to ECE from the Diameter Gateway timed out at the Diameter Gateway but continued to be processed in ECE, the Diameter Gateway was sending a response to the user or pricing gateway, even after the timeout, and the Diameter Gateway response was rejected because of the timeout. This has been fixed. If the transaction times out in the Diameter Gateway, the corresponding transaction in ECE is also cleared.
32470519	The HTTP gateway was not coming up. This was because of a the missing jackson-datatype-jsr310-2.11.2.jar file. This has been fixed.
32519770	The PCM_OP_CUST_DELETE_ACCT opcode was taking a long time to delete accounts. This was because of a slow flow, gateway latency spikes, and CPU usage spikes. This has been fixed.
32538295	In ECE UpdateExtension, calls to extensionContext.getExtensionsDataRepository() were returning nothing instead of the Extensions Data Repository View. This has been fixed.
31880868	When a terminate request was coming after session expiration, positive balances were being issue to prepaid subscribers. This was because ECE was sending a validity time of 0 for valid grant service units, and when validity time is 0, the network only sends CCR-U if the reservation is fully used or there is a CCR-T. This has been fixed.
31630743	When an SNA failed to process with an invalid AVP error, subsequent RAR/SNR notifications were getting stuck and the Diameter Gateway would stop processing RAR and SNR messages. This has been fixed.
31902139	For one time bundles, tariff time change (TTC) was not working when balance existed in the current month but not the next month balance and the system attempted to reserve a balance shortly before the balance expiry. This has been fixed.
31692737	The Diameter Gateway needed to be restarted because of increasing active sessions and heap size. This has been fixed. Stale sessions are now cleaned up.
32842304	When a product status was changed, active session cleanup was failing due to a no matching product error. This has been fixed.
31983454	Subscriber Preferences and Service Lifecycle were not included in CCA for EVENT_REQUEST (BALANCE_QUERY) even though they were enabled for use in extensions. This has been fixed.
31832442	ECE was failing to process RAR when there were multiple rating groups associated with the same session. This has been fixed.
32567193	The Diameter Gateway was not processing RAR notifications, which was increasing the pending RAR queue size. This has been fixed.
31559378	Restarting the Diameter Gateway during a rolling upgrade procedure was generating a `TransportsMessageBundle-0903:Unable to create session` error multiple times. This error occurs if durable subscription is being used with WebLogic Topic, and the same clientID and subscription name is in use. This has been fixed.
32007118	When a session has multiple updates, balance impacts were being applied for each CCR instead of treating it as a single event at the aggregate level. This has been fixed.
32013271	The CCA was returning incorrect GSUs and consumed reservations were not updated correctly because of how unratedNetQty was evaluated. This has been fixed.
31958554	Primary member data balances were not accessible for processing data usage CCR sessions that were dependent on the owner balance within a shared group. This has been fixed. Owner balances are now accessible in both post and prerating extensions.
32046630	Publishing customer updates requests to ECE was failing and ECE nodes were disjoining from the cluster and becoming inaccessible. This was because of improper initialization of the CQC key cache for public user identity (PUI). This has been fixed.
32002289	Subscriber tracing was not capturing SNR/RAR notification messages as expected. This has been fixed.
32003506	Incremental loading of customers was failing. This was because a SharingCustomerLock that existed when a customer was in a transaction was not removed automatically when the serving node went down. This has been fixed.
31897119	The replication of customer accounts between active and passive sites was showing a difference in relative account size between the primary and secondary ECE sites. This has been fixed.
31878546	The customerLoader process was running a query with a hard-coded value causing the generation of new SQL IDs and a new plan each time the query was run. This was impacting the customer migration process from legacy systems to BRM. This has been fixed. The query now uses bind variables instead of literals.
31630751	After changing a product's rate plan, ongoing data usage transactions were resulting in DIAMETER_UNABLE_TO_COMPLY messages instead of continuing with rating and committing the ongoing usage. This has been fixed.
31550821	When a recurring bundle was purchased or canceled during a session, ECE was rating the subsequent CCR as though the TTC condition were set to true, even if there was no real TTC. This has been fixed.
31535141	When Tariff-Time-Change AVP was enabled and triggered, Granted Service Units (GSU) of 0 was sent in response to UPDATE requests. This has been fixed.
31395496	In an ongoing sessions CCA was not being sent by ECE for a CCR-U request. This was causing the network to send a terminate request as a next request, abruptly ending the session that was in progress. This has been fixed.
31692727	The Diameter Gateway was not returning GSU in CCR-U replies, causing a mismatch of balances between the policy and charging rules function and ECE on the network side. This has been fixed.
31785258	The ActiveSession cache was not being replicated properly after switching the primary role from one ECE site to another. This has been fixed.
31769583	Changing the credit floor limit was not being updated in ECE correctly, which was impacting the subsequent rating and reservation behavior. This has been fixed.
31630756	ECE was failing to reserve remaining balance after CCR-I initial grant, affecting the processing of subsequent CCR requests. After receiving the first CCR-U, the USU was recorded correctly but the ActiveReservation in BalanceCache was incorrectly set to zero, which affected the filling of GSU in the CCA reply. This has been fixed.
31630747, 33108039	After a service transfer from one account to another, usage occurring after the transfer was incorrectly rolling up to the old account. This has been fixed.
31605626	Running the post_install.pl script after installing ECE 11.3 patch set 9 was giving the following error: `ORA-24006: cannot create QUEUE, PIN_2.ECE_SUSPENSE_QUEUE already exists`. This has been fixed.
31785256	An exception occurred during cache data federation. This has been fixed.
31666068	During the billing process, during diameter usage processing, the Diameter Gateway was throwing an `Unable to Comply` error. This has been fixed.
31824183	The ECE customer query had hard-coded literals instead of a bind variable, which caused issues while migrating customers into ECE. This has been fixed.
31501025	Reauthorization requests (RARs) were failing when there were multiple rating groups in the same session. This has been fixed.
31413905 31719731	The tariff time change was not working if the next month's balance was not available. This has been fixed.
31232536 31690795	Even after a billing account was changed for a non-paying child, usage charges were still being rolled up to the earlier billing account. This has been fixed.
31899413	With Final Unit Action as Final Unit Indicator (FUI)/REDIRECT, the Quota Holding Time (QHT) Attribute-Value Pair was missing in the CCA response. This has been fixed.
31296934 31782712	The selective subscriber tracing functionality was not capturing Sy SNR and Gy RAR messages. This has been fixed.
31872639	Conditional policy impacts were routed to the user balance instead of the sharer balance, even when the sharer balance was configured to be used. This has been fixed.
32092505	Account creation was failing because ECE was parsing the customer POID as an integer instead of a Long. This has been fixed.
32130386	Incremental synchronization of accounts was not working after an upgrade from ECE 11.3 Patch Set 9 Interim Patch 12 to ECE 12.0 Patch Set 3. This has been fixed. During incremental loading, you no longer have to provide -DpreDistributedWorkItems.
32184754	In ECE, the active session objects cleanup feature was causing performance degradation. This has been fixed.
32602507	When the database is down, ECE caches rated events in the Coherence cache, then pushes them to the database when it comes back up. Rated Event Formatter (REF) was skipping some cached events, which were eventually purged without being added to the BRM database. This has been fixed. Now, after the database comes back up, REF pauses processing for a new configurable time period, giving all of the cached events time to be pushed to the database. See "Configuring Rated Event Formatter" in ECE Implementing Charging for information about the parameter that controls this time period.
32551846	Active-active systems required a single REF instance on a single site that was used by all sites. This represented a potential single point of failure. This has been fixed. Now there is an REF instance at every site to format rated events locally, then disperse them to other sites. If an instance fails at one site, formatting fails over to a different REF site. See "Configuring an Active-Active System" in BRM System Administrator's Guide for information about active-active ECE systems.
N/A	Purchase or cycle prerated events passed from external systems into ECE for loading into BRM with Rated Even Loader (REL) include additional details like effective date-times and G/L data. Previously, only usage events were loaded by REL, so these details were ignored by ECE and not passed on to BRM. This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 3

Table 1-14 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 3.

Table 1-14 Customer-Reported Fixes for ECE 12.0 Patch Set 3

Bug Number	Description
29960660	The Final Unit Indicator (FUI) was not triggered for the successive update requests into Diameter Gateway, after the FUI was sent once in the response for an earlier request. This has been fixed.
29990703	The Pricing Updater was throwing an exception when processing offer profile information. This has been fixed.
30013014	When BRM Gateway and BRM reconnection was interrupted, the BRM Gateway suspense queue was blocked. This has been fixed.
30018071	The same Public User Identity (PUI) was appearing multiple times in notifications. The data structure has been updated to include the PUI only once in notifications.
30018075	ECE notifications did not include the event time stamp, which is required for BRM opcode calls. This has been included now.
30085070	When ECE evaluated an item selector, the results were incorrect. This has been fixed.
30120617	While creating accounts in BRM, there were error messages in EM Gateway. Post-commit validations were introduced in ECE to make sure of data integrity on both BRM and ECE systems.
30175643	It was noticed that both Validity Time and Granted Units were zero for some usage responses. This has been fixed.
30191582	In ECE, customer data map entries were not properly serialized, leading to a NullPointerException. This has been fixed.
30293167 30715647	ECE did not trigger SNR notifications when balances or counters were updated on the core BRM server for billing or product purchase. This has been fixed.
30293175	For a sharing hierarchy, AR actions (payments, adjustments) on payee accounts were not updating the balances correctly in ECE.
30293184	The time zone information in usage records was not considered in Diameter Gateway. This affected the time model evaluation during the rating phase in ECE, resulting in incorrect charging.
30378999	The consumption rules information was not handled in ECE. This has been fixed.
30560539	BRM Gateway requests from ECE to BRM were defaulted to BRM schema 1. This has been fixed to use the correct schema using account POID as the routing POID.
30577374	When a subscriber was having active sessions, the delete account operation was failing. This has been fixed.
30596817	In ECE, EM Gateway was throwing timeout error, during updates from BRM to ECE.
30599578	In ECE, when more than one discount was available for rating, reverse rating was not working properly. This has been fixed.
30681648	In Diameter Gateway, SLR messages were not retrieving the user identity based on the multiple options available in AVP. This has been fixed.
31007224	During rating, a new method to fetch the product details based on effective time of call from audit was not available. This has been fixed.

Customer-Reported Fixes in ECE 12.0 Patch Set 2

Table 1-15 lists the customer-reported issues that were resolved in ECE 12.0 Patch Set 2.

Table 1-15 Customer-Reported Fixes for ECE 12.0 Patch Set 2

Bug Number	Description
28499167	If there were multiple threshold events, then the custom data map was incorrect. This has been fixed.
29252596	With the discount sharing enabled in the system, the customer eviction was not working properly. This has been fixed.
29269723	The values stored for session initiate request of a session were not available during the update request. This has been fixed.
29297126	The latency information within External Manager (EM) Gateway were displayed incorrectly in the log files. This has been fixed.
29352741	For a long running session with split scenario, there were rounding issues with different scaling on charging and discounting. This has been fixed.
29352848	There were threading issues that were generating errors in the usage or update processing flows. This has been fixed.
29361881	The update processing flow was throwing a "no valid product" exception. This has been fixed.
29383215	Modifications to subbalance validity was not handled properly. This has been fixed.
29415796	Diameter Gateway was losing precision while processing integers that were big. This has been fixed.
29422243	If there was any change in the impact category, such as the user moving from one country to another in the same zone, the daily bundle was granted even if it was already granted. This has been fixed.
29428394	For usages of 1KB, the rounding was not proper due to precision and scaling issues. This has been fixed.
29479716	The threshold breach notification was not including all Public User Identities (PUI) from the service alias list. This has been fixed.
29531402	During the usage processing, reverse rating was not working correctly when multiple discounts were evaluated. This has been fixed.
29543203	During the usage processing, discount evaluation was incorrect when multiple discounts were involved. This has been fixed.
29634128	Data in ECE cache was lost due to the growth of memory with unnecessary replication of Subscribe-Notifications-Requests (SNR). This has been fixed.
29646046	When processing usage, if there were multiple threshold breaches in the same session, the aggregated information of those breaches were not populated properly in the notification. This has been fixed.
29647134	The closed user group (CUG) evaluation of a customer who was earlier in a CUG was incorrectly done. This has been fixed.
29669600	When processing update requests, the rating profile was corrupted. This has been fixed.
29674445	When service balance group transfer was done within the same account, the item portal object IDs (POID) list and the next item POID list were not syncrhonized properly. This has been fixed.
29763898	Diameter Gateway was expecting proxyable bit in the command flag in credit control requests and this was causing Diameter Gateway to respond with an error DIAMETER_INVALID_HDR_BITS (3008) when the command flags were simply 0x80 for the request. This has been fixed and now Diameter Gateway does not validate for the proxyable bit in the command flags when processing credit control requests.
29764019	When a balance impact was null for a rated event, the database was generating a unique constraint violation. This has been fixed by marking the rated event as invalid.
29782159	In an ECE deployment with beat configured, the reverse rating was not considering the splits. This has been fixed.
29808711	A balance update request was failing with an exception during Subscribe-Notifications-Request (SNR) generation. This has been fixed.
29823002	During the rolling upgrade, the tax code configuration data updated through Java Management Extensions (JMX) was lost. This was because only the charging-setting.xml was updated, but the updates were not reflected in the appconfiguration cache. This has been fixed.
29843327	The DiameterGy extension was throwing an exception on a top-up request. This has been fixed by adding sufficient checks.
29960659	During usage processing, a post File Update Information (FUI) update was trying to reserve further units causing DIAMETER_CREDIT_LIMIT_REACHED status to be returned to the network. This has been fixed.
30013017	Any updates to Oracle Communications Billing and Revenue Management (BRM) such as Life Cycle notifications from ECE to BRM were stuck in the Java Message Service (JMS) queue. The BRM Gateway was not able to send them to BRM due to connection pool issues. The BRM connections were not released back to the pool leading to non-availability of connections for any further requests. This has been fixed.
30175640	During usage processing, both validity time and granted service units were derived from adjusted rateable usage metric (RUM) quantity instead of the range-end. This has been fixed.
30177988	During usage processing, threshold notification was sent out based on reservation amount instead of actual consumed amount. This has been fixed.

Customer-Reported Fixes in PDC

See the following for a list of customer-reported issues that have been fixed in each Oracle Communications Pricing Design Center (PDC) patch set:

Customer-Reported Fixes in PDC 12.0 Patch Set 8

Table 1-16 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 8.

Table 1-16 Customer-Reported Fixes for PDC 12.0 Patch Set 8

Bug Number	Description
34787291	It was observed that when both the base and the derived event were modified in the same changeset, if a new field is added into the base event, the field is not being propagated into the supportedConfig object for the derived event. This has been fixed. When creating the supportedConfig object for a derived event, changes are now made to get the base event data from the same changeset before retrieving them from the PDC Server cache. The newly added field will be propagated to the derived event.
34740335	When a PDC user with a Pricing Reviewer role logged in to PDC, the user was able to view the Create Terms option. This has been fixed.
34700672	When upgrading to Patch Set 7, the customer-defined tax codes were not getting created in PDC, resulting in a missing data error when exporting the configuration data. Also, when deleting tax codes using the PDC UI, the default tax codes were removed from PDC but not from BRM. This has been fixed. Tax code configurations are mastered in PDC. Users need to create a BccTaxCode configuration for each customized tax code in the PDC system before exporting configuration data. In the RRE Transformation Engine, remove the deleted PDC tax code from the XREF table as well as the input tax code XML file used for loading into the BRM system.
34679033	During export using the -expRefAll option, if the number of child objects to be fetched is more than 1000, it was causing an ora-01795 exception. This has been fixed. During the export operation, if the number of child objects is more than 1000, the list is broken into batches of size 1000 and fetched from database so that the IN clause size is within the permitted range.

Customer-Reported Fixes in PDC 12.0 Patch Set 7

Table 1-17 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 7.

Table 1-17 Customer-Reported Fixes for PDC 12.0 Patch Set 7

Bug Number	Description
34352501	After upgrading PDC from 7.5 to 12.0 Patch Set 5, some charge offers could not be updated. This occurred because Patch Set 5 added a new configuration for the prorate cycle but the XREF database upgrade script was populating the wrong value as the default value. This has been fixed.
34278066	After upgrading PDC from 7.5 to 12.0, an issue occurred with discount quantity expressions because not all expressions were supported. This has been fixed. PDC validation now restricts quantity expression options only for the BRE pipeline. Restrictions were removed for ECE.
34124976	Some PDC scripts still referenced the transPLData.jar file even though it was removed from the code in a previous patch set. This has been fixed.

Bug Number

Description

34352501

After upgrading PDC from 7.5 to 12.0 Patch Set 5, some charge offers could not be updated. This occurred because Patch Set 5 added a new configuration for the prorate cycle but the XREF database upgrade script was populating the wrong value as the default value.

This has been fixed.

34278066

After upgrading PDC from 7.5 to 12.0, an issue occurred with discount quantity expressions because not all expressions were supported.

This has been fixed. PDC validation now restricts quantity expression options only for the BRE pipeline. Restrictions were removed for ECE.

34124976

Some PDC scripts still referenced the transPLData.jar file even though it was removed from the code in a previous patch set.

This has been fixed.

Customer-Reported Fixes in PDC 12.0 Patch Set 6

Table 1-18 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 6.

Table 1-18 Customer-Reported Fixes for PDC 12.0 Patch Set 6

Bug Number	Description
33733603	While creating a USC Selector, the Usage Type column was not displayed when the Convergent Usage profile was selected. This has been fixed.
33381695	When a plan transition entry was removed from PDC, it was not getting deleted from the TRANSITION_T table in BRM. This has been fixed.
33617669	Intermittently, objects were out of order in the payload, which resulted in the model selector not getting populated. This has been fixed.
33439274	Adjustment items created during rerating were not allocated to any bill even when the AllocateReratingAdjustments business parameter was enabled. This occurred because, in the PDC create charge offer page, the default value in the Stop Charging list was When Inactive and When Cancelled. This has been fixed. The default value in the Stop Charging list was changed to Never.
33921641	When a user logged in to PDC with the Pricing Reviewer role, a NullPointerException occurred when trying to open promoted Package objects. This occurred because there is no active changeset in Reviewer mode, but PDC was trying to access the active changeset while opening Package objects. This has been fixed. Accessing the active changeset when running in Reviewer Mode is now avoided.
33931861	If an impact category was deleted and then re-created, it could not be used in a zone model. This issue was caused by PDC not fetching the latest zone result items. This has been fixed.

Customer-Reported Fixes in PDC 12.0 Patch Set 5

Table 1-19 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 5.

Table 1-19 Customer-Reported Fixes for PDC 12.0 Patch Set 5

Bug Number	Description
33374664	PDC was not accepting monthly cycle forward and cycle arrears charges in the same charge offer. This has been fixed.
33171060	The BRE transformation engine was creating duplicate DiscountMaster for reusable PDC chargeSelectorSpec. This has been fixed.
33552021	When the CleanXrefDiscountMaster.sql script was run to clean up duplicate discountMasters in the BRE Transformation XREF table, it took 14 hours and still had not completed. This occurred because there were 120,000 discountMasters in the XREF table, and one of the discountMasters had 116,000 duplicated discountMasters. There was not enough memory in the original implementation to maintain this list of duplicated discountMasters for reporting. The script has been fixed.
33434673	BRM balance elements supported seven rounding modes, but PDC balance elements supported only four of them. PDC did not support the following rounding modes: ROUND_FLOOR ROUND_FLOOR_ALT ROUND_DOWN_ALT This has been fixed.
33185277	StepC and StepQ are the only valid options for a cascading discount. Validations to enforce these options have been implemented.
33205981	TotalC and TotalQ were not supported in QuantityRange expressions. This has been fixed.
33001081	In discount offers, a customer was able to configure only integer values and unable to configure decimal values to increment the step(beat) field. This has been fixed.
32968407	For a balance impact, it is possible to specify whether an impact applies to the Sharer's or Owner's balance groups. The request was for a similar ability when selecting balances for use in triggers and rules. For example, to permit the use of the following functors: Balance[Resource]: For a shared discount, get the Sharer balance of a resource. MemberBalance[Resource]: For a shared discount, get the Member balance of a resource. By permitting the expression to directly access a Member resource, it would no longer be necessary to create multiple discount rules for each resource that might be used. This could save hundreds of rules. To implement this, PDC has implemented the below features: Member Balance: A new Boolean flag has been added to balance expressions that can be used to indicate to ECE that a member balance needs to be considered while evaluating the expression rather than the owner balance. Max and Min Functors: Two new functors were added for finding the maximum and minimum of two different expressions.

Customer-Reported Fixes in PDC 12.0 Patch Set 4

Table 1-20 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 4.

Table 1-20 Customer-Reported Fixes for PDC 12.0 Patch Set 4

Bug Number	Description
32931796	The SyncPDC process was failing on the BRM side when there were multiple G/L segments involved. This has been fixed
32708512	Updating a bundle was failing. This was because validation rules expected a deliverable object. This has been fixed. The validation rules no longer expect a deliverable object if the existing charge offers in the bundle do not have one.
32645457	While doing package transitions in PDC, when a transition rule is deleted and saved, it was still appearing in the user interface, but when the changeset was submitted, the transition rule would disappear. This was because the content wasn't being refreshed after deleting the transition rule. This has been fixed. There is now a force refresh after a transition rule is deleted and the package is saved.
32172885	While creating pricing objects, the following errors occurred in the PDC server log file: `Error when in XmlValidationErrorHandler cos-nonambig: subscriptionTerms and subscriptionTerms (or elements from their substitution group) violate "Unique Particle Attribution".` Although this had no functional impact in creating or modifying pricing objects, the error occurred because the subscription terms definition was included twice in the PricingObjects.xsd. This has been fixed.
32164981	Importing a zone map was failing due to a mismatch between transformation and PDC. The map was being created in PDC but failing in Transformation, so the transaction was rolled back and the entries for the map were deleted. The next time the zone map was submitted, PDC sent it as a MODIFY object, and Transformation could not find the object in the database. This has been fixed. Transformation now does a lookup to search for the object. If the object isn't found, Transformation treats the MODIFY transaction as CREATE.
31955647	When running PDCBRMWalletUtil.sh to change the wallet password for BRM Integration pack, the script was failing with the following error: `Error: Could not find or load main class jvmopts`. This has been fixed . The script now uses the bin/bash UNIX shell instead of /bin/sh.
31583707	PDC did not support taxation at the balance impact level for charges. This has been fixed.
31583703	PDC did not support tax time in rating and billing at the balance impact level for charges. This has been fixed.
31511626	PDC migration was failing to migrate discount model configurations. This has been fixed.
31452654	PDC did not support tax codes at the balance impact level for discounts. This has been fixed.
31385700	PricingDesignCenter.sql was failing because of an issue with ProvisioningTagAttrSpecId.sql. This has been fixed.
31332903	It was not possible to update a zone model in PDC. This was because during PDC migration, multiple entries in the BRM zone model were created when multiple service codes were associated with a single BRM service. This has been fixed.
31257734	When adding a new GLID to BRM, SyncPDC reported a validation error for a GLID name change, stating that the name was already used by another GLID object in PDC. This is because PDC was using the description field for GLID, so if multiple GLIDs had same description, there would be duplicate GLID names. This has been fixed. Now migration/syncpdc uses the name that you enter for the GLID instead of copying it from the description.
31223178	Modifying charges for products with rate plan selectors was resulting in errors. This was because for migrated charge selectors, PDC prorate values (PRORATE_CHANGE, PRORATE_FULL, PRORATE_NONE) were set instead of BRM prorate values (prorate, full, none). This has been fixed.
31213200	During PDC migration, charge offer creation was failing. This was because required RUMs were missing, and the BRM RUM name was used instead of the PDC RUM name. This has been fixed. The migration scripts now check for required RUM names and PDC RUM names are used.
31124410	XML import for products was failing if the external ID in the XML doesn't exist in target system. This has been fixed. If external IDs are missing during XML import, they are created and added into the ExternalID table.
29770708	Filters were missing on the zone model screen of the PDC user interface. There was a long list of zone rules in the zone model and sorting the list timed out. This has been fixed.
31513293	When updating the pricing-price model code, PDC was overriding code with the internal ID of the migrated objects. This has been fixed.
31670528	PDC displays an `ADF_FACES-60097 Error` when trying to display some entries in the service-event map. To prevent this, click Save after adding or deleting each object in the Service-Event Map user interface.

Customer-Reported Fixes in PDC 12.0 Patch Set 3

Table 1-21 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 3.

Table 1-21 Customer-Reported Fixes for PDC 12.0 Patch Set 3

Bug Number	Description
30312020	When migrating batch rating events (BRE) to PDC, migration changed the SERVICE_CODE_USED and SERVICE_CLASS_USED BRE fields to the PDC SERVICE_CODE and SERVICE_CLASS fields. However, there was no mapping information being maintained in the PDC SupportedConfig. Because of this, the rating engines did not start. This has been fixed.
30920955	You could not sort zone models in the PDC GUI because, while sorting data, PDC always retrieved it from the database. This has been fixed. PDC now maintains data in memory on the first retrieval and then updates it during create/update.

Customer-Reported Fixes in PDC 12.0 Patch Set 2

Table 1-22 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 2.

Table 1-22 Customer-Reported Fixes for PDC 12.0 Patch Set 2

Bug Number	Description
29199299	If the startDate in the bundleProductOffering was immediate, the timestamp in the deal may be off by -1 hour. This caused failures while loading the deal into BRM. This has been fixed.
29526136	In Pricing Center, it was possible to configure pro-ration settings for each of the charges under a charge selector. This was missing in PDC. This has been fixed. Now, the Charge Selector Configuration menu is available with options for Proration Settings and Remove Charge Selector. To configure the proration details, click Proration Settings .
29590589	While using the function balance[Temporary Resource], an error was displayed in the PDC user interface. This has been fixed.
29635057	There were multiple issues while migrating real-time rating engine (RRE) and batch rating engine (BRE) data of BRM to PDC. BRE used multiple delayed events for the same service. Multiple PDC discount models created the discount model used by the discount selector and issues related to Plan and Deal transitions. This has been fixed.
29661212	User was not able to delete a ratable usage metric (RUM) because it was referenced in the older versions of the pricing and config objects. This has been fixed. Now, it is possible to delete the older versions of the referenced objects also, along with the RUM.
29825919	Pipeline rating was going wrong for the noncurrency resources. Earlier, PDC was transforming the balance element's numeric code as the resource name to the BRM system, which was not the correct implementation. This has been fixed in migration and transformation to transform the balance element's code as the resource name instead of numeric code. This fix is relevant to anyone using PDC migration and transformation.
29867480	While configuring roll over charge offers using the PDC user interface, errors were displayed. This has been fixed.
30150356	If a zone model is referenced in a pricing object, such as charge offer, and a new zone model is created, the user is unable to obsolete or delete any zone model either through the user interface or ImportExportPricing utility. This has been fixed.

Customer-Reported Fixes in PDC 12.0 Patch Set 1

Table 1-23 lists the customer-reported issues that were resolved in PDC 12.0 Patch Set 1.

Table 1-23 Customer-Reported Fixes for PDC 12.0 Patch Set 1

Bug Number	Description
20881534	When the Save as option was used to copy a component, it was not copying only the component instead it copied the internally referenced components along with the component. This has been fixed.
21575971	After importing setup components, there were no rows created in certain tables which was causing issues. This has been fixed. When you install BRM, its installation scripts populate the sample data, including setup and pricing components. When using PDC, this data should not be initiated in BRM, but it should be defined in PDC and published to the BRM database. To ensure that PDC and BRM are integrated properly, you must clean up the BRM sample data before you start using PDC. See the discussion about cleaning the sample data in PDC Installation Guide.
22488798	The ImportExportPricing utility with the -d (delete) parameter worked only for obsoleting a setup component and only if the component was not referenced by any other component. After the component was made obsolete, it could not be used by any other components. This has been fixed.
25091591	Import of metadata was failing with a constraint violation if PDC was integrated with ECE. Recreate the index without COMPRESS ADVANCE LOW to fix this issue.
25932012	SyncPDC was failing if /event/realtimeDiscount class existed in the BRM database. Delete this class from the BRM database to fix this issue.
27040318	Syncpdc was failing during the transformation of the event if the usage class length was more than 4K, the maximum size of the column. This has been fixed.
27756978	PDC Weblogic Server managed server was logging verbose Eclipse Link messages (up to the FINE level) in the Weblogic Server log (nohup.out). The FINE level was not appropriate for Production environments. This has been fixed.
27840554	The BRM Integration Pack installation was failing because of certain privilege issues. A SYSDBA user credential was required to proceed. This has been fixed. The PDC Installer now accepts any user with database privileges not restricting to the SYSDBA user in the System Database Credentials screen.
27881855	When a rateable usage metric (RUM) was disassociated from all services and events in the service-event map, importing the RUM into PDC caused NULL pointer exception in the real-time rating transform engine. This has been fixed.
27925018	For the same recurring charge product definition, the rate was generated as fixed amount in the case of pricing center but as scaled amount in PDC. PDC actually supports fixed amount for recurring charges. This has been fixed.
27963192	When SyncPDC was run after changing the length of a field in the storable class associated with a custom event in BRM, the change was not reflected in the event definition in the PDC database. This has been fixed.
28094045	The high-volume PDC tables were not getting purged which was leading to performance issues. This has been fixed.
28171359	For chargeshares, the General Ledger ID was migrated as Undefined instead of Not Set. This has been fixed.
28262068	The USC_MAP was case sensitive whereas the ZONE_RESULT was case insensitive. This has been fixed. The USC_MAP is also case insensitive

Customer-Reported Fixes in Billing Care

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

Customer-Reported Fixes in Billing Care 12.0 Patch Set 8

Table 1-24 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 8.

Table 1-24 Customer-Reported Fixes for Billing Care 12.0 Patch Set 8

Bug Number	Description
34921603	When accounts had multiple bill units, the Settled Dispute dialog box was displaying incorrectly in the Newsfeed. This issue has been fixed.
34836116	There was a requirement to validate the payment date before a payment reversal was performed. The PCM_OP_BILL_REVERSE opcode returns the result as success or fail. This has been fixed. The transaction is stopped when the opcode's result is Fail.
34815110	The Payment Details dialog box was not displaying the Move Payment to Suspense link when payments were re-allocated through Payment Suspense. This has been fixed.
34960177	Bills were incorrectly displaying A/R actions and applied payments. This has been fixed. Billing Care now identifies whether a refund is from a payment or an adjustment.
34782990	Opening an account resulted in a "Search template too big" error message due to a large search template being used in the Generate a Bill Unit Summary REST endpoint. This has been fixed.
34801290	Billing Care incorrectly displayed that some child accounts were paid by the partner and not the reseller. This has been fixed. It now shows the correct paid by account for child accounts in multilevel hierarchy flows.
34787371	CSRs with read-only permission were not able to view invoices in Billing Care. This has been fixed.
34658103	The Newsfeed displayed a blank page when you clicked Recurring Charges. This has been fixed.
34647372	The Billing Care events table was displaying time in the local timezone when the event object had no timezone offset value set. You can now configure the event table's display timezone by using the customConfiguration.xml file.
34608840	While viewing rate customizations, Billing Care displayed an "Invalid service information" error message. This occurred when PIN_FLD_RATE_TIER was present at ARRAY [1] instead of ARRAY [0] in the /rate_plan object of the purchased product. This has been fixed.
34537316	The Billing Care Unallocated Payments dialog box was displaying junk values. This has been fixed.
34594332	Accounts with a large number of children were not opening due to a "Search template too big" error while fetching bill units. This has been fixed. The search template and API calls that fetch bill unit data were optimized.
34574762	In the Bill Search results table, even when the balance due is 0, the days overdue is shown as 0. This has been fixed.
34543790	Refunds were shown as reverse payments in the Payment Details dialog box. This has been fixed. The Payment Details dialog box now shows the refunded amount and audit trails for refund actions.
34523780	When the service login details were updated, the details were not synchronizing with ECE even though it was synchronized to the database. The call to the PCM_OP_CUST_UPDATE_SERVICES opcode was modified to update any type of service that generates a login event, which helps the synchronization with ECE.
34658110	Attempting to click on a disabled negative balance was calling the Open Negative Transfer Balance dialog box. This has been fixed.
34417594	Batch payments were getting created with a payment channel ID of zero for each payment, regardless of what was passed in the PMT file. This has been fixed. A new Locale header has been added to the PMT file for fetching the payment channel ID from the correct locale. By default, it uses en_US. The channel name string should be passed under the Channel field for each payment so that it sets the corresponding channel ID while collecting payments.
34396022	A bill with zero balance was showing as overdue in the Newsfeed. This has been fixed. A new check verifies that only amounts greater than 0 are displayed as overdue in the Newsfeed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 7

Table 1-25 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 7.

Table 1-25 Customer-Reported Fixes for Billing Care 12.0 Patch Set 7

Bug Number	Release Notes
34175445	In a multischema BRM deployment, Billing Care was not displaying all bill units in an organization hierarchy. This has been fixed to show all bill units from all database schemas in an organizational hierarchy.
34131767	In the Billing Care Batch Payment interface, the Active tab did not display processed records correctly. This has been fixed.
34119136	For child accounts, the Billing Care Bills tab displayed the parent account POID rather than the parent's account number. The paid by parent account number was displayed correctly for bills in progress, but all previous bills displayed the parent account POID. This has been fixed.
34109642	Issues occurred when creating an inactive service in an account. This has been fixed.
34109640	When the Billing Care REST API was used to create a service profile, the effective date was set to the created date. This has been fixed. The Billing Care REST API now supports profile creation with a specific effective date passed in the request payload.
34095400	When using the search template to retrieve specified account numbers, the template was returning all accounts from the BRM database. This has been fixed.
33981515	When clicked twice, the Billing Care Newsfeed link was re-directing to the Balances page. This has been fixed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 6

Table 1-26 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 6.

Table 1-26 Customer-Reported Fixes for Billing Care 12.0 Patch Set 6

BUG Number	Description
33894625	The Billing Care REST API could not add or delete multiple aliases for a service. This has been fixed. The Billing Care REST API has been enhanced to support the addition and deletion of aliases.
33726114	In Billing Care, percentage adjustments were not working with bill amounts over 1,000. This has been fixed to show the proper value when the adjustment amount is more than 999.
33726113	The Pay screen in the Billing Care account creation wizard was blank after navigating back to the Configuring screen. This has been fixed.

BUG Number

Description

33894625

The Billing Care REST API could not add or delete multiple aliases for a service.

This has been fixed. The Billing Care REST API has been enhanced to support the addition and deletion of aliases.

33726114

In Billing Care, percentage adjustments were not working with bill amounts over 1,000.

This has been fixed to show the proper value when the adjustment amount is more than 999.

33726113

The Pay screen in the Billing Care account creation wizard was blank after navigating back to the Configuring screen.

This has been fixed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 5

Table 1-27 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 5.

Table 1-27 Customer-Reported Fixes for Billing Care 12.0 Patch Set 5

Bug Number	Description
33570044	A customer was not able to customize the account creation flow in Billing Care. This has been fixed. A customization hook was introduced to enable customizing the account creation flow in Billing Care, including an SDK sample.
33535652	The account creation REST API did not include an option for setting the account number in the input JSON. This has been fixed. A customization hook has been provided to enable customers to customize the account creation flow in Billing Care.
33512579	In batch payment cards, the View File link was navigating to a 401 error instead of displaying the file contents. This has been fixed.
33497816	Localized strings for custom labels defined under the `custom_extensions` group in custom XLF files were not being picked up by the Billing Care English resource bundle. This has been fixed.
33488572	The Billing Care bulk refund template was not fetching the events across child accounts. This has been fixed. The template now supports the POID type as input for search criteria and for creating a proper search template input flist when join is not specified in the filter criteria of XML.
33459924	Custom fields were not being displayed in the Billing Care Payment Details screen. This has been fixed.
33438993	In the Billing Care Make Payment dialog box, custom date fields for custom payment methods were being displayed in UNIX timestamp format. This has been fixed. The UNIX timestamp is now converted to the proper date format for display in the Billing Care UI.
33358070	When you selected View Invoice PDF for an account stored in a secondary schema, the invoice displayed only hard-coded strings. This has been fixed.
33139786	Billing Care was not able to fetch purchased products in the Subscription section for accounts in the secondary schema. This issue has been fixed. Billing Care now calls the PCM_OP_GLOBAL_SEARCH opcode rather than the PCM_OP_SEARCH opcode for multischema systems.
33105909	In Billing Care, purchasing a deal that had a two-month validity period was not working because PIN_FLD_END_T in /purchased_product and /purchased_discount was getting set to NULL. This has been fixed.
33655028	Hierarchies were not showing all child accounts in multischema systems. This has been fixed.
33560836	The Billing Care REST API was reporting errors when creating and updating service profiles. This has been fixed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 4

Table 1-28 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 4.

Table 1-28 Customer-Reported Fixes for Billing Care 12.0 Patch Set 4

Bug Number	Description
30528415	The DataModelGenerator was not generating the schema for a custom payment object for a custom batch template. This has been fixed. Billing Care now generates schemas for custom payment objects with standard /payinfo objects and events.
32434965	The Billing Care REST API returns the same generic error regardless of whether an internal server error or a business error occurred. This has been fixed. The Billing Care REST API now returns more descriptive error messages and response codes.
32434963	In the Billing Care user interface, the history page of batch payments displays multiple lines of duplicate results for the same processed file. This has been fixed.
32230733	The Billing Care user interface was loading the assets page and was getting services on large databases. This was because the query was retrieving all schedule objects. This has been fixed. The query now only retrieves selected schedule objects.
32078942	In the Billing Care user interface, when disputing an event with an amount greater than 1000, the dispute amount and reason codes were not displaying. This has been fixed.
32052513	In the Billing Care user interface, searching for a suspended payment, assigning the payment to an account, and adding comments were all slow when there were a large number of custom fields. This has been fixed.
32618809	In the Billing Care user interface, validity dates were incorrectly shown in the date pickers for noncurrency balances. Instead of displaying the actual valid-to end date, the current date was always shown as the default date. This has been fixed.
31452531	In the Billing Care user interface, searching by bill number and account number was not displaying the correct results or sometimes not displaying any results. This has been fixed.
31082441	Billing Care was not correctly displaying pages loaded in an iFrame using Chrome browser up to version 80. This has been fixed. Billing Care now supports adding additional attributes to application cookies in the SDK.
31037692	In the Billing Care user interface, when importing a payment file to perform a batch payment, the page was not refreshing automatically even when the batch payment file was processed successfully. The page had to be reloaded manually. This has been fixed.
31245611	In the Billing Care user interface, when trying to allocate a suspended payment to an account with multiple open bills, not all of the bills were displayed in the Allocate payment page. This has been fixed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 3

Table 1-29 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 3.

Table 1-29 Customer-Reported Fixes for Billing Care 12.0 Patch Set 3

Bug Number	Description
29351464	There was a requirement to switch between a summary and detailed view of account balances in the Billing Care Home tab. This is now supported through the Billing Care SDK.
29833415	Billing Care now supports timezones that automatically adjust for Daylight Saving Time (DST) changes. To do so, use the brmserver.timezone registry entry in the Billing Care SDK Configurations.xml file. By default, the entry is empty and Billing Care uses the WebLogic server's timezone.
29837457	In the Billing Care Bills tab, the hyperlink from a child account to its parent account was not working. This has been fixed.
30292975	In Billing Care, the account screen did not load when an account had more than 200 bill units attached to it. This occurred because the search template exceeded the maximum character range. This has been fixed by optimizing the search template.
30332380	The Billing Care REST API did not return the required security headers as part of the server response. This has been fixed.
30385889	The Account Profile dialog box in Billing Care displayed an account's country as Afghanistan even though the country was set to Sweden. This has been fixed.
30418719	In Billing Care, it is now possible to: Disable the backdated feature for the Account Creation, Purchase Package, and Purchase Bundle screens. Perform a backdated product purchase in the Purchase Bundle screen.
30541405	It was not possible to view a bill-level adjustment done through a custom opcode in the Billing Care GUI. This has been fixed. The Billing Care GUI has been enhanced to show bill-level adjustments done through custom opcodes.
30555807	The Notes section in the Billing Care Adjustments screen displayed an incorrect date. This has been fixed.
30761675	When attempting to set up a custom payment method in Billing Care, an exception occurred and the payment method was not displayed in the Billing Care GUI. This has been fixed.
30825689	When .pmt files were imported for processing batch payments, Billing Care kept processing the file until the page was reloaded. Thus, the page had to be reloaded every time you wanted to process a new batch payment. This has been fixed.
30829223	Billing Care displayed an incorrect net amount when you selected or deselected a negative amount. When a positive and negative amount was involved, Billing Care summed the two amounts rather than taking the difference. This has been fixed.
31012975	After a Chrome browser was updated to v80, the Billing Care screens did not load due to SameSite cookie enablement. Billing Care has been enhanced to support adding attributes to application cookies by using the Billing Care SDK. For example, a customer can use this new SDK capability to add the SameSite attribute to application-level cookies.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 2

Table 1-30 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 2.

Table 1-30 Customer-Reported Fixes for Billing Care 12.0 Patch Set 2

Bug Number	Description
27764510	In the Allocate Adjustment and Payment Details dialog boxes, the columns were not resizable for simple and advanced views. This has been fixed and the columns can now be resized.
28466526	In News Feed, when the Show Payment in Suspense link was clicked for a suspended payment, a payment suspense search page opened in a new browser tab. This has been fixed and clicking the link now opens the suspended payment record.
28543516	Terminating or Inactivating discounts for a service was throwing an error. This has been fixed.
28624766	In Billing Care Asset view, clicking Show Rate Customizaton was throwing an error, if the number of products purchased was more than 150. This has been fixed.
28664596	There was an issue with amount formatting and rounding for Singapore dollar currency. This has been fixed.
28671904	Billing Care is now enhanced to support account number and bill number instead of the corresponding Portal object IDs (POID) in the flows where Billing Care URLs are embedded in the external applications. See "Support for Account Number and Bill Number in Billing Care Embeddable URLs" for more information.
28671910 28853673	It was not possible to log in to Billing Care from a new browser tab using a bookmarked URL, if there was a browser tab already logged in with Billing Care. This has been fixed.
28707428	The Today date filter was not working in the payment suspense flow. This has been fixed and the payment suspense search template has been corrected.
28764136	Billing Care is now enhanced so that the JavaScript files changes are not required in the account number sorting during account search implemented through software development kit (SDK).
28768197	There was an issue while displaying the suspended payment details when the Move, and View in Payment Suspense link was clicked in the payment details page. This has been fixed.
28806804	Posting multiple comments (notes) was causing connection issues. This has been fixed and the connection is released to the free pool on completion of note update.
28806805	Some of the dependent classes for generating reports were not shipped as part of the REST WAR files package. This has been fixed and the missing dependencies are now included.
28837041	The connection to BRM was lost after timeout exception was thrown for the operations wrapped under a transaction. This has been fixed.
28854728	Transfers between billable credit and debit items were treated as accounts receivable. This resulted in incorrect breakup of charges under the Bills tab. This has been fixed.
28905269	While navigating to accounts receivable action details, after selecting a refund type accounts receivable action, the Back button was not working and its label was missing. This has been fixed.
28905272	It was not possible to install Billing Care REST in silent mode. This has been fixed.
28912852	Billing Care now displays a tool-tip in the Bill ID field of the following dialog boxes: Payment Details, Payment Details Item Affected, Account Adjustment, and Account Adjustment Details .
28912854	The Cancel link was not working for the notes in the Event Adjustment Details dialog box. This has been fixed.
29048170	When switching between bills, there was an issue with the Bills tab Show/Hide link. This has been fixed.
29161373	The Purchase Package and Purchase Deal flows are now supported as embeddable URLs. See "Embeddable URLs for Purchase Package and Purchase Bundle Screens" for more information.
29161376	Billing Care is now enhanced to display bills that were generated before the account was moved under a hierarchy. See "View Bills Generated Before Moving the Account to a Hierarchy" for more information.
29161377	It was not possible to enter special characters for the Billing Care Wallet Password field. This has been fixed.
29178999	For the bills in progress, wrong dates were displayed in the Item Adjustment dialog box. This has been fixed and the current billing cycle dates are displayed.
29272365	The Refund Bill dialog box was displaying an error that the amount was greater than 999.99. This has been fixed.
29272368	There were performance issues with the bill details view. It was taking more time to load particularly for the flows involving Billing Care URLs embedded in other applications. This has been fixed.
29290979	The collection actions scheduled dates were one day older than the actual due date. This has been fixed to show the correct scheduled dates.
29290981	If an account is created using customer center with a country, for example USA, and the same account was opened in Billing Care, a different country was displayed in the account profile details. This has been fixed.
29323429	There were alignment issues with the labels of the Tax Setup dialog box under Financial Setup. This has been fixed.
29349021	Discounts which were overridden as part of product purchase were not displayed in the breakup of the Original Charge or Discount or Net details in the Events dialog box. This has been fixed.
29376636	It is now possible to display custom error messages on the Billing Care user interface when purchasing a bundle.
29376640	It was not possible to link purchase reason and notes to a particular add-on purchase event. This has been fixed. A new method has been introduced, which retrieves the list of all the purchase events that can be used in the Billing Care SDK to assign to the notes.
29395718	To improve the performance of the Assets user interface, lazy loading of the assets has been implemented. By default, limited service information is retrieved and when the customer service representatives expand the particular service card, the additional service and offer details are retrieved.
29428269	The Bill in progress text was displayed twice in the Events page header. This has been fixed.
29435523	After installation, Business Operation Center was opening with a blank screen. This has been fixed.
29441732	Overdue days were shown incorrectly as the last configured period of the aging buckets. This has been fixed to show the actual overdue days. A new popup has been added to list the age of the overdue balances as per the aging bucket configuration.
29441738	Reason code was missing in the make payment flow. This has been fixed and the reason code is added now.
29493386	The Event Adjustment dialog box can now be customized to separate both Adjust the Amount field and Adjust the Percent field. Also, there was an issue with tax only adjustment. This has been fixed.
29511807	There was a performance issue while retrieving users who had access to the Payment Suspense screen because all the configured users were queried. This has been fixed and it is now possible to query only users associated with a specific role who has the required screen access.
29520395	The Billing Care SDK is now enhanced to support implementing the logic to restrict the deal list based on the role of the customer service representative. See Billing Care SDK Guide.
29629576	The Billing Care SDK is now enhanced to support implementing the logic for filtering deals list to display manual discount deals only. See Billing Care SDK Guide.
29629577	Object serialization error was logged in the Oracle Entitlements Server client weblogic logs. This has been fixed.
29645139	The future dated add on purchase were purchased with wrong dates. This has been fixed.
29649643	Billing Care is now enhanced to display the external user names (login user) in News Feed to clearly highlight who has made changes on the account or have performed any account receivables actions. See Billing Care SDK Guide.
29705003	It is now possible to customize Billing Care to include start date and end date based filtering for add on deal purchase.
29759310	In the Billing Care Item Adjustment dialog box, it is possible to see the total amount for which adjustment is done. But it does not display how much other amount was adjusted against specific item. This has been fixed.
29759312	To improve performance, Billing Care has been enhanced to disable direct click on the Assets view from the Home tab through customization. It is now possible to search through service ID to go to the Assets page which display only services associated with the search criteria.
29789695	The Oracle Entitlements Server obligation check was throwing an exception. A null value check on adjustment amount when percentage only adjustment is done using customization was not introduced to avoid this exception. This has been fixed.

Customer-Reported Fixes in Billing Care 12.0 Patch Set 1

Table 1-31 lists the customer-reported issues that were resolved in Billing Care 12.0 Patch Set 1.

Table 1-31 Customer-Reported Fixes for Billing Care 12.0 Patch Set 1

Bug Number	Description
27375507	In Billing Care, it was not possible to save the notes in the Payment Details dialog box when the amount was more than 999 and when the payment was added by using an opcode. This has been fixed.
27423362	When an attempt was made to open details using the account number hyperlink in the Payment Suspense Page Audit trail, it was opening the incorrect Suspense Account page. This has been fixed.
27500263	When a payment was made and then reversed, if a comment was added under reversal section, it was not visible unless the Payment Details dialog box was reopened. This has been fixed.
27698947	In Billing Care, a performance issue was reported while listing the deals during a product purchase operation. This has been fixed.
27722599	In Billing Care, in the Payment Details dialog box, the payment allocation table was not aligned properly. This has been fixed.
27771469	If a bill contains charges from subordinate bill units, the items were getting over allocated. This has been fixed.
27823059	The first column was Name in the Allocate Adjustment screen instead of Account. This has been fixed.
27828889	The Payment Allocation screen displayed the account POID instead of the account number. This has been fixed.
27874943	When a payment was first applied to an account and then moved to suspense and then again allocated to another account and then moved to suspense, the Audit Trail was not updated correctly. It was still showing the first account. This has been fixed.
27874945	While purchasing product/discount, the dates were not displaying correctly if there were timezone differences. This has been fixed.
27924915	Using the Billing Care SDK, it was not possible to customize the purchase deal screen and add a few custom fields. Also it was not possible to display the new fields in the asset display screen, changing the start /end date and change the overridden amount. This has been fixed. See Billing Care SDK Guide.
27931964	If a bundle was purchased with an override amount, the override amount was not accepted if it included ",". This has been fixed.
27938642	The date in the Payment Reversal page after posting a comment was not displayed correctly unless the page was refreshed. Also, the first comment was not visible. This has been fixed.
28206783	Whenever a customization was added to Billing Care, the cache was not getting refreshed automatically. The user had to clear the browser cache and relogin. This has been fixed.
28220688	The override amount was not being retained when the product status was changed to active. This has been fixed.
28261963	The search results in the Payment Suspense screen was not displaying all the records as per the set pagination limit. This has been fixed.
28431427	The Account Details page for an account with multiple bill units was taking more time to open which was leading to time out. This has been fixed.
28543514	When a credit adjustment was applied to a bill with no dues, the Event Adjustment column in the adjust event actions screen was showing only the tax part of the event adjustment instead of the full adjustment amount. This has been fixed.
28543965	The DataModelGenerator utility was not generating custom XSD for custom objects available in BRM. This has been fixed.
28543979	When Billing Care submitted the batch payments through Lockbox file, the entire file was rolled back if it included under payments. This has been fixed.
28543981	Account details were not being displayed in the Billing Care Collections Page after implementing custom collections scenario and customizing the policy opcode. This has been fixed.

Customer-Reported Fixes in Business Operations Center

Table 1-32 lists the customer-reported issues that were resolved in the Oracle Communications Business Operations Center 12.0 patch sets.

Note:

No customer-reported issues were resolved in Business Operations Center 12.0 Patch Set 5, Patch Set 6, and Patch Set 7.

Table 1-32 Customer-Reported Fixes for Business Operations Center

Bug Number	Patch Set	Description
34853383	8	It was possible for users to see all jobs in the Jobs page even when the required access was not granted. This has been fixed. Users can now see only allowed categories in the Jobs page, Job Timeline view, Job History page, and Home page.
34504354	8	The View failure report link was enabled for custom jobs when the /process_audit/billing object was populated in BRM for that job. In other cases, Business Operations Center doesn't show the link for custom jobs.
34504352	8	The Job History page was not loading when a /process_audit/export_gl object was created. This has been fixed.
32981684	4	The Business Operations Center installer now supports a pre-created Business Operations Center user. With this enhancement, you can create a Business Operations Center database user and tablespace, and then use these details in the installer to create the schema.
31954955	4	When installing Business Operations Center on an environment using RAC Database 19c, the silent installation was failing while running the boc_schema.sql script. This is fixed and the installer has been enhanced to use a pre-created database user and setup the Business Operations Center schema on the same. With this enhancement, you can now create the Business Operations Center database user and tablespace and use the same details in the installer to setup the BOC schema.
28602921	2	The SERVICE_HOST parameter in Business Operations Center configuration properties file restricted login with IP address when the parameter was set as hostname, and restricted login with hostname when the parameter was set as IP address. This has been fixed. Dependency on the SERVICE_HOST parameter has been removed to construct REST URL.
29033987	2	The Business Operations Center silent installer has been enhanced to update wallet with Secure Shell user and BRM connection keys.
29290982	2	During validation, the Business Operations Center installer was not accepting special character for passwords in the Wallet field. This has been fixed. Now, special characters in addition to numbers and characters are accepted.
29699403	2	The Business Operations Center failure report was showing Account Portal object ID (POID) instead of the account number. This has been fixed and the report now shows the account number.

Customer-Reported Fixes in BRM Thick Clients

Table 1-33 lists the issues reported by external sources for Oracle Communications Billing and Revenue Management (BRM) thick clients and provides a brief description of the resolution.

Note:

No customer-reported BRM thick client issues were resolved in 12.0 Patch Set 4, Patch Set 5, Patch Set 6, and Patch Set 7.

Table 1-33 Customer-Reported Fixes for BRM Thick Clients

Bug Number	Patch Set	Description
34629290	8	The Event Browser Custom Search template was not working. The extra fields RateTimezonId and TimezoneId were included in PCM_OP_GLOBAL_STEP_SEARCH for every search in Event Browser. Some custom template searches may not include these fields in the main class and thus the search was not working. This has been fixed. The two fields are included in search results only when a search is done on /event or /event/%.
34962905	8	Customer Center was displaying duplicate entries for disputes in the Unresolved Disputes page. The "wrong" entry did not contain details on the Dispute Details section. This has been fixed.
30439709	3	In the Customer Center Services tab, CSRs with read-only permission could not copy service IDs. This is now enabled through a customization option.
30727930	3	The Windows version of Payment Tool 12.0.0.2.0 threw an error message when users attempted to log in. This has been fixed.
30146959	3	In the Customer Center Payments tab, when searching for payments and selecting All in the Bill Unit list, Customer Center displayed only payments related to a specific bill unit. This has been fixed.
30562624	3	UEL templates could not be modified in Developer Center. This was caused by issues with the XML4J parser and was fixed by changing it to a JDK parser.