Skip Headers
Oracle® Communications Billing and Revenue Management Patch Set 8 Release Notes
Release 7.5

E28199-08
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Summary of Customer-Reported Fixes

This chapter provides an overview of the customer-reported bug fixes that were introduced in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 1 through BRM 7.5 Patch Set 8.

Customer-Reported Fixes

Table 1-1 lists the service request (SR) issues reported by external sources and provides a brief description of the resolution. The SRs are grouped by the respective patch sets.

Table 1-1 Customer-Reported Fixes

SR Number Bug Number Description

3-1829300141

16712903

(Patch Set 8) In the previous releases, Billing Time taxation was not considering rerated events.

This has been fixed.

3-7264844381

16934735

(Patch Set 8) In Collection Center, the password update functionality was not working correctly.

This has been fixed.

3-6942999391

17374482

(Patch Set 8) In the previous releases, flexible cycles feature was not available for cycle-arrear type of events.

This has been fixed.

3-7575635931

17426332

(Patch Set 8) In the previous releases, it was not possible to reprocess suspended payments.

This has been fixed.

3-7883532671

17547351

(Patch Set 8) When a device is disassociated from a service, the tlco features and the service status was set to inactive.

This has been fixed.

3-7795922241

17554381

(Patch Set 8) In the previous releases, the pin_collections_process utility was not considering custom pay types when used with -billinfo option.

This has been fixed.

3-3203134721

17558049

(Patch Set 8) In the previous releases, when an event is adjusted to a zero amount, BRM was not allowing further adjustments to the same event.

This has been fixed.

3-7761178911

17613917

(Patch Set 8) In the previous releases, when a BI Publisher job fails, the pin_inv_doc_gen application was not responding.

This has been fixed.

3-3224766561

17649746

(Patch Set 8) In the previous releases, when a discount was purchased or cancelled, events corresponding to the non-relevant discounts with a net zero balance impact were generated during sequential discounting.

This has been fixed.

3-8024405931

17737580

(Patch Set 8) While prorating cycle fees for the first cycle, the proration was incorrectly done due to rounding errors.

This has been fixed.

3-7916589241

17758446

(Patch Set 8) In a multi-schema deployment, there was an inconsistency in the data dictionaries across primary and secondary schemas with respect to the Class ID information for some storable classes. This was causing an issue when events were migrated across schemas using AMM or while using global transactions.

This has been fixed.

3-6544659031

17782269

(Patch Set 8) When Customer Center was used to modify accounts, after modifying ten accounts (canceling a deal or a product, or modifying an account or a service status), when the eleventh account is opened for editing by closing the previously opened accounts, Customer Center was hanging.

This has been fixed.

3-7983376211

17782272

(Patch Set 8) In Pricing Center, the charge share model search functionality was not refreshing the results for display.

This has been fixed.

-

17834402

(Patch Set 8) In the previous releases, non-currency resources were being incorrectly included in the tax calculation.

This has been fixed.

3-8068729561

17841880

(Patch Set 8) In the previous releases, updating the /profile/collection_params object with the billinfo_obj object was not supported with the PCM_OP_CUST_UPDATE_CUSTOMER and PCM_OP_CUST_CREATE_CUSTOMER opcodes.

This has been fixed.

3-7737814231

17845539

(Patch Set 8) In the previous releases, it was not possible to read an event related to a charge packet or a tax packet not having general ledger information using the testnap utility or applications.

This has been fixed.

3-8064376913

17889096

(Patch Set 8) In the previous releases, the HUR summary report was throwing an error when used with multiple time zones.

This has been fixed.

3-7894667251

17896043

(Patch Set 8) In the previous releases, Web Services Manager was not able to call custom opcodes.

This has been fixed.

3-8196304884

17900751

(Patch Set 8) In the previous releases, Connection Manager was signaling that the transaction was already open, even when it was not open.

This has been fixed.

3-7894706101

17903777

(Patch Set 8) In the previous releases, Customer Center was throwing an error when attempting to transfer negative bill balance.

This has been fixed.

3-6440870677

17935807

(Patch Set 8) In Collection Center, a user with read-only permissions could create and modify collections scenarios.

This has been fixed.

3-7960600071

17950186

(Patch Set 8) In certain scenarios, all non-currency resource buckets were not following the ALIGN mode for sub-balances, even though the /config/business_params was configured for the same.

This has been fixed.

3-8193290131

17950189

(Patch Set 8) When reactivating an account, even though the account was configured for not charging (change_start_time_on_activation set to 0), all the deals purchased during the inactive period were charged.

This has been fixed.

3-8035728931

17953892

(Patch Set 8) In the previous releases, Account Migration Manager was incorrectly updating the POID data of the migrated objects.

This has been fixed.

3-8236511011

17960952

(Patch Set 8) In the previous releases, a deal could not be purchased with cycle end date later than purchase end date and the error message thrown was also incorrectly referring to cycle start date rather than cycle end date.

This has been fixed.

3-8227147931

17969941

(Patch Set 8) In the previous releases, the answer-b simulator was not handling files containing more than 15000 records.

This has been fixed and the limit has been removed.

3-8146998271

17979806

(Patch Set 8) In the previous releases, Account Migration Manager was not considering au_bal_grp_bals_t and au_bal_grp_sub_bals_t for migration.

This has been fixed.

3-8252791781

17979811

(Patch Set 8) In the previous releases, while processing a large amount of subscription operations during migration, there was a memory leak in the subscription module resulting in a PIN_ERR_NO_MEM error.

This has been fixed.

3-8077624361

17986166

(Patch Set 8) In the previous releases, even though the parent billing was suppressed, the effective_t for child items were set during the billing.

This has been fixed.

3-8029971471

17987706

(Patch Set 8) In the previous releases, there were memory leaks during the invoice generation.

This has been fixed.

3-8129157061

17988212

(Patch Set 8) In the previous releases, if there were any old cycle events having zero balance impact, it was not possible to cancel that deal.

This has been fixed.

3-8225910261

17989494

(Patch Set 8) In the previous releases, for child accounts in a hierarchy with an annual cycle plan, cycle_end_t was not set correctly after billing.

This has been fixed.

3-8115209561

17989498

(Patch Set 8) In the previous releases, the pin_bill_accts utility was dumping core due to memory corruption.

This has been fixed.

3-8187852561

17989500

(Patch Set 8) In the previous releases, the rejection percentage calculation was incorrect in Pipeline Manager and Pipeline Manager was not honoring the actual MaxErrorRates.INF_EDR_REJECTED setting due to this error.

This has been fixed.

3-5392047531

18000150

(Patch Set 8) In the previous releases, there was an issue with rounding in the bill adjustment functionality.

This has been fixed.

3-8091699931

18000153

(Patch Set 8) In the previous releases, setting new validities for a balance group was not working.

This has been fixed.

3-8262672901

18000156

(Patch Set 8) In the previous releases, the pin_collections_process utility was failing when a 64-bit POID was passed in using the -billinfo option.

This has been fixed.

3-7967455551

18003074

(Patch Set 8) In the previous releases, when the pin_cycle_fees utility was used with -cancel option, it was failing to cancel expired products.

This has been fixed.

3-8066512611

18009156

(Patch Set 8) In the previous releases, Customer Center was not considering non-ASCII characters for status change note.

This has been fixed.

3-8234687951

18011724

(Patch Set 8) In the previous releases, when a deferred purchase of a Cycle Arrear product was performed for the last accounting cycle, with the cycle start date in the current accounting cycle, the cycle arrear charges were applied during the purchase for the previous accounting cycle.

This has been fixed.

3-8235356971

18018966

(Patch Set 8) In Payment Center, the Undo Allocation dialog box was not displaying any information.

This has been fixed to show the relevant information.

3-8298105494

18020803

(Patch Set 8) In the previous releases, there were memory leaks in subscription module affecting the get_offerings functionality.

This has been fixed.

3-8302820211

18021949

(Patch Set 8) In the previous releases, Customer Center was not allowing to update the customer specific values for Extended Rating Attributes (ERAs).

This has been fixed.

3-8241871651

18028894

(Patch Set 8) While rerating, the rerated events were created with event types different from the actual or original event types.

This has been fixed.

3-7680101571

18035886

(Patch Set 8) In the previous releases, deferred taxes for adjusted events were incorrectly taken into account twice, once when calculated and then again during billing.

This has been fixed.

3-8225157841

18039440

(Patch Set 8) In the previous releases, core dump was encountered while fetching item level products using the PCM_OP_SUBSCRIPTION_READ_ACCT_PRODUCTS opcode.

This has been fixed.

3-8147489964

18045426

(Patch Set 8) In the previous releases, there was no transaction timeout set in BRM JCA Adapter, which was resulting in the JCA Adapter to wait indefinitely.

This has been fixed.

3-8039516251

18045562

(Patch Set 8) In the previous releases, account creation through JCA Adapter was failing due to incorrect PIN_FLD_TXN_FLAGS value (2).

This has been fixed.

3-8195716611

18048135

(Patch Set 8) In the previous releases, when different parameters for PIN_FLD_STATUS were sent, the PCM_OP_AR_GET_DISPUTES opcode was not working as per the documentation.

This has been fixed.

3-7547410071

18058584

(Patch Set 8) In the previous releases, cancellation of one product was resulting in an update to the validity of another product.

This has been fixed.

3-8326842051

18065158

(Patch Set 8) In the previous releases, when a deferred purchase of a tailor-made plan was done, creation of cycle events was inconsistent for the tailor-made product.

This has been fixed.

3-7785161621

18075534

(Patch Set 8) In the previous releases, in case of an external transaction errorring out, the uniqueness entries for the relevant account were getting removed.

This has been fixed.

3-8107252761

18077057

(Patch Set 8) In Customer Center, cancelled products were displayed multiple times.

This has been fixed.

3-8253376711

18082392

(Patch Set 8) In the previous releases, when a balance group is transferred from one bill unit to another, any events earlier to the transfer were referring to the latter bill unit for rounding.

This has been fixed.

3-8268530121

18089341

(Patch Set 8) In the previous releases, dm_oracle was crashing intermittently during the billing process.

This has been fixed.

3-8218411461

18089343

(Patch Set 8) In the previous releases, refunded discount amount was different from what was actually charged.

This has been fixed.

3-8360703251

18089346

(Patch Set 8) In an upgraded system; for example, from 7.2.1 to 7.5, when setting the cycle fee end date using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode for a product purchased before the upgrade, the cycle forward event was not generated. This was not the case for the products purchased after the upgrade.

This has been fixed.

3-8171715051

18097559

(Patch Set 8) In Customer Center, when canceling a deal, the dialog box was not sized properly and the contents of the dialog box were off the viewing area.

This has been fixed.

3-8114388951

18105060

(Patch Set 8) In multischema environment, other than primary schema, attempting to perform a service transfer within the same schema was resulting in a duplicate login error.

3-8236030981

18105062

(Patch Set 8) In the previous releases, for the PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode, the amount (MINIMUM, MAXIMUM fields) and the resource_ID were not working as documented and as expected.

This has been fixed.

3-8255438523

18105066

(Patch Set 8) In Account Migration Manager, migration of the POID data inside BLOB value of the invoice_formats_but_t table was incorrect.

This has been fixed.

3-8224919131

18105068

(Patch Set 8) In the previous releases, the PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode was taking longer time and causing system performance issues.

This has been fixed.

3-8234687951

18105071

(Patch Set 8) In the previous releases, in case of a short cycle, the cycle_fees dates were not correctly computed.

This has been fixed.

3-7929514301

18123572

(Patch Set 8) In the previous releases, while viewing the bill details of a bill with zero item_total and due, Customer Center errors out without displaying the bill details.

This has been fixed.

3-7815391001

18130721

(Patch Set 8) In the previous releases, products with deferred purchase start date were being considered for an incorrect period during billing.

This has been fixed.

3-8167352561

18130728

(Patch Set 8) In the previous releases, incorrect value was reported in special drawing rights (SDR) in the Detail section, which resulted in an incorrect value for the PARAM_THRESHOLD_VALUE field of HUR reports.

This has been fixed.

3-8156854901

18137014

(Patch Set 8) In the previous releases, an incorrect discount was being applied with the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode.

This has been fixed.

3-8390593051

18143076

(Patch Set 8) In the previous releases, the pin_flist_to_xml macro was not supporting special character codes.

This has been fixed.

3-8148669581

18145951

(Patch Set 8) In the previous releases, the flexible cycles feature was not available for cycle arrear type of events.

This has been fixed.

3-8434449451

18148830

(Patch Set 8) In the previous releases, the behavior of the pin_deferred_act utility with exit code was inconsistent compared to other utilities.

This has been fixed.

3-8021529961

18153415

(Patch Set 8) In the previous releases, existing discounts were not getting applied after purchasing a new discount.

This has been fixed.

3-8189645221

18160124

(Patch Set 8) In Customer Center, executing deferred actions was throwing errors.

This has been fixed.

3-8447740781

18181447

(Patch Set 8) In the previous releases, when migrating balances and sub balances using Conversion Manager, bal_grp_bals_t was not populated by the pin_cmt utility in case of an existing balance.

This has been fixed.

3-8511819171

18189283

(Patch Set 8) In the previous releases, Conversion Manager was not recognizing the AAC_ACCESS, AAC_PACKAGE, AAC_PROMO_CODE, AAC_SERIAL_NUM, AAC_SOURCE, and AAC_VENDOR out-of-the-box fields.

This has been fixed.

3-8255438426

18195447

(Patch Set 8) In the previous releases, the AMM Monitor module was not able to process certain event types.

This has been fixed.

3-8164081675

18200941

(Patch Set 8) In the previous releases, it was not possible to send a file as an input to the pricing_admin.pl script.

This has been fixed.

3-8138316801

18202674

(Patch Set 8) In the previous releases, an account level bill time discount was applied to only one bill unit, even though the account had multiple bill units.

This has been fixed.

3-8518620561

18205040

(Patch Set 8) In the previous releases, dm_fusa was logging unnecessary errors in its pinlog file.

This has been fixed.

3-8064029011

18207660

(Patch Set 8) In Customer Center, when an adjustment failed, an improper error message was displayed.

This has been fixed.

3-8372565791

18229698

(Patch Set 8) In the previous releases, when a tailor-made product was cancelled, refunds were incorrectly calculated.

This has been fixed.

3-7967455551

18255628

(Patch Set 8) In the previous releases, the pin_cycle_fees utility with -cancel option was failing to cancel expired products.

This has been fixed.

3-8161921671

18255630

(Patch Set 8) In a short cycle, the proration was incorrectly performed without considering the actual number of days.

This has been fixed.

3-8243499441

18255632

(Patch Set 8) In Pipeline Manager, the PLAN_LIST block was not getting reset after each time a CDR is processed.

This has been fixed.

3-8435611631

18260632

(Patch Set 8) In Customer Center, for soft decline cases, the resource ID and amount were not displayed in the payment details section.

This has been fixed.

3-8580826221

18277424

(Patch Set 8) In the previous releases, after each successful login, there were unnecessary updates in the /service/admin_client object and the /service/pcm_client object.

This has been fixed.

3-8411543901

18292808

(Patch Set 8) In the previous releases, the loadpricelist utility was not checking for the existence of price plans and the rate plans in the source file; instead it was throwing a NullPointerException exception while trying to load from an xml file.

This has been fixed.

3-2578237711

18293638

(Patch Set 8) In the previous releases, the PCM_OP_AR_BILL_ADJUSTMENT opcode was erroring out as the IN clause of the search template was exceeding the limitation of the dm_oracle buffer.

This has been fixed.

3-8580263821

18313822

(Patch Set 8) The pin_cycle_fees utility was accessing more number of records for processing and was taking unusually long time to compute cycle fees.

This has been fixed.

3-8501473801

18344997

(Patch Set 8) In the previous releases, the subscription transfer operation was not working and was throwing errors.

This has been fixed.

3-8648711551

18360130

(Patch Set 8) In the previous releases, Connection Manager (CM) was looping infinitely when an error was thrown from the PCM_OP_CUST_POL_PREP_BILLINFO policy opcode.

This has been fixed.

3-8161921671

18380888

(Patch Set 8) In the previous releases, during a short cycle, the proration was incorrectly performed.

This has been fixed.

3-8475279591

18435484

(Patch Set 8) In the previous releases, the dm_vertex was not reconnecting after losing connection to CTQ database.

This has been fixed.

3-6455148891

15887303

(Patch Set 7) In the previous releases, during the trial billing operation, BRM rolled back only the charges and not the taxes.

This has been fixed.

3-6648900291

16221298

(Patch Set 7) When you are launching Web-based Pricing Center, the "Could not load suite definition file. Exiting application" error was thrown.

This has been fixed.

3-6866310181

16660459

(Patch Set 7) In the previous releases, after a pay_type was modified, any refund requests made against the payment amounts were refunded to the new or modified pay_type, instead of refunding to the pay_type that was used to make the payment.

This has been fixed.

3-6739714431

16696696

(Patch Set 7) In the previous releases, if there was a need to implement the /service/partner_csr custom service type similar to /service/admin_client, the Change Password dialog box defaulted to /service/admin_client.

This has been fixed. The Change Password dialog box no longer defaults to /service/admin_client and the custom service is now read from a properties file.

3-7277349381

16921531

(Patch Set 7) In the previous releases, there was a memory leak in the PCM_OP_SUBSCRIPTION_CANCEL_DISCOUNT opcode.

This has been fixed.

3-7229470961

16954176

(Patch Set 7) In the previous releases, an account that had several products associated to different deals was showing the same deal name for all the deals in Customer Center.

This has been fixed.

3-7264288811

16983887

(Patch Set 7) In the previous releases, even when the tax engines such as dm_vertex was down, instead of throwing an error and aborting the transaction, the tax calculation was succeeding incorrectly, showing 0 taxes.

With this patch, an error is thrown when the tax engine is down.

3-7484824561

17183808

(Patch Set 7) When Business Intelligence Publisher (BI Publisher) 10g reports were deployed on a port other than 9704, reports failed to execute because the location of the sub-templates was hardcoded into the reports.

With this patch, the customer intervention is now reduced to only changing the port in a property file, which updates a variable and all the reports with sub-templates are updated with this variable.

3-7517206641

17289102

(Patch Set 7) In the previous releases, dm_vertex was not working for Canadian addresses.

This has been fixed.

3-7443116061

17334137

(Patch Set 7) In the previous releases, service orders were not being generated for a change in the status_flags parameter.

This has been fixed.

3-7391444541

17338355

(Patch Set 7) In the previous releases, when billing was run by passing a control file, such as PinBillRunControl.xml, the default due date was not considered for billing.

This has been fixed.

3-7640890711

17356834

(Patch Set 7) The memory monitoring module in the router pipeline was generating a false alarm on the available memory and was causing the pipeline shutdown.

This has been fixed.

3-7548257081

17367213

(Patch Set 7) In the previous releases, the CSR accounts created using Permissioning Center were incorrectly picked up for billing.

This has been fixed.

3-7721921861

17386134

(Patch Set 7) In the previous releases, tax was not applied on late fee or finance charges because the tax details sent through the policy opcodes were not honored.

This has been fixed.

3-7742042501

17388514, 17388516

(Patch Set 7) In the previous releases, balance threshold notification was not including the record ID information.

With this patch, the record ID is now included as the <INFO> element within the notification XML file.

3-7702402441

17392322

(Patch Set 7) In the previous releases, the parent bill unit of the collections group was incorrectly entering into collections, even when the bill unit was exempted from collections.

This has been fixed.

3-7076809871

17392324, 17392333

(Patch Set 7) In the previous releases, the PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS opcode was not supporting inactivation and reactivation of a cycle arrear discount.

This has been fixed.

3-7659413561

17415780

(Patch Set 7) When loading rated events using PIN_REL, if there was a failure, PIN_REL was incorrectly moving the file to the archive directory instead of to the reject directory.

This has been fixed. In case of a failure, the file is now moved to the reject directory.

3-7743065831

17422613

(Patch Set 7) In the previous releases, rating was failing for accounts migrated through Conversion Manager because the CREATED_T, MOD_T, and EFFECTIVE_T entries in the UNIQUENESS_T, AU_UNIQUNESS_T, and UNIQUE_ACCT_NO_T tables were not populated with the value in CREATED_T of ACCOUNT_T.

This has been fixed.

3-7725919111

17442229

(Patch Set 7) In the previous releases, there was no configuration that governs whether to keep or delete the existing balances when new balances were migrated using Conversion Manager.

This has been fixed.

3-7782875571

17448898

(Patch Set 7) Conversion Manager was not populating the REC_ID of SERVICE_ALIAS_LIST_T based on the ELEM ID passed in the Subscriber.xml file.

This has been fixed.

3-7615827681

17455607

(Patch Set 7) In the previous releases, an incorrect discount Portal ID (POID) in the input to the PCM_OP_SUBSCRIPTION_PURCHASE_DEAL opcode was causing the Connection Manager (CM) to crash without returning an appropriate error.

This has been fixed.

3-7644617461

17481884

(Patch Set 7) The PCM_OP_BILL_MAKE_INVOICE opcode was not picking up events generated by trial bill. This was due to the incorrect event search criteria used in the opcode.

This has been fixed.

3-7725634881

17488108

(Patch Set 7) In the previous releases, rerating was throwing a unique constraint error on ITEM_NO.

This has been fixed.

3-7562871791

17495576

(Patch Set 7) When Oracle Communication Pricing Design Center was enabled, the transition code was getting incorrectly copied to the transition name.

This has been fixed.

3-7740495438

17502487

(Patch Set 7) In the previous releases, during billing, a product was rated with an incorrect scale after the charged_from and charged_to dates were updated.

This has been fixed.

3-7792071021

17502491

(Patch Set 7) The purchase fees for the products whose deferred time coincides with the billing time were not being considered in the ongoing cycle, even though the purchase_fees_backcharge entry in the pin.conf file was enabled.

This has been fixed.

3-7458554491

17509041

(Patch Set 7) In the previous releases, reversals were not recognized as backdated even after passing END_T in the input of the PCM_OP_BILL_REVERSE opcode.

This has been fixed.

3-7504743251

17509050, 17646849

(Patch Set 7) In the previous releases, when processing the usages for a service, there were validation failures for which the payer was updated during the delay period.

This has been fixed.

3-7605568281

17509052

(Patch Set 7) Rated Event Loader (RE Loader) was not using bind variables in some SQL queries, which was resulting in unwanted memory use of the shared pool.

This has been fixed.

3-7861651681

17511460

(Patch Set 7) In the previous releases, one-time credit card topup was failing because of a mismatch in the data type used to store the port number.

This has been fixed.

3-7788938941

17540679

(Patch Set 7) In spite of specifying a custom /config/config/payment object in the CM's pin.conf file, it was not being referred.

This has been fixed.

3-7545970761

17564123

(Patch Set 7) The PCM_OP_AR_GET_ACTION_ITEMS opcode was returning PIN_ERR_MISSING_ARG when called with the default input data for the opcode.

This has been fixed.

3-7761024621

17564132

(Patch Set 7) The PCM_OP_COLLECTIONS_PROCESS_BILLINFO opcode was erroring out when the disable_pcm_mempool entry was set in the CM's pin.conf file.

This has been fixed.

3-7773678861

17564134

(Patch Set 7) While using the PCM_OP_ACT_SCHEDULE_CREATE opcode for deferred purchases, a value of 0 for the IP address was causing error.

This has been fixed.

3-7758018551

17581601

(Patch Set 7) In the previous releases, attempting to purchase a product under the root service of account (/service) was throwing errors.

This has been fixed.

3-6972678311

17588615

(Patch Set 7) With advance_bill_cycle set to 1 in the CM's pin.conf file, the cycle day of month (DOM) was incorrectly set to 2 for accounts created on the 29th, 30th, or 31st of a month.

This has been fixed.

3-7725919111

17595091, 17713807

(Patch Set 7) When migrating balances through Conversion Manager, the existing items were overwritten.

This has been fixed.

3-7892680211

17613909

(Patch Set 7) The PCM_OP_SUBSCRIPTION_GET_ACTG_DATES opcode was throwing a warning about the unsupported flag (0x2000) and subsequently throwing a PIN_STREAM_EOF error.

This has been fixed.

3-7704113271

17613922

(Patch Set 7) In the previous releases, billing performance was degraded and required improvement for cases where a large number of rate plans existed for different combination of event types causing flist manipulation in the subscription module to take more time.

This has been fixed.

3-7850053441

17634054

(Patch Set 7) When a backdated purchase of an annual product was made to an account, the dates in the cycle_fees array were incorrectly set, leading to an incorrect rating.

This has been fixed.

3-7533451661

17640560

(Patch Set 7) The pin_cycle_fees utility was failing to create the /process_audit/billing object.

3-7939096121

17641286

(Patch Set 7) The PCM_OP_COLLECTIONS_GROUP_GET_BILLINFO opcode was failing when collections group included the owner but not the members.

This has been fixed.

3-4556934401

17646959

(Patch Set 7) Web Services Manager was waiting until the response was received from BRM, without timing out and it seemed like it was hanging.

This has been fixed. Web Services Manager now considers the timeout parameter from the properties file.

3-7449246051

17647842

(Patch Set 7) In the previous releases, the ORA-00445 message was frequently detected because a background process could not be started after a specific interval.

This has been fixed.

3-7785285591

17661531

(Patch Set 7) When a discount was canceled, the balances were not impacted even if the keep_cancelled_products_or_discounts parameter was disabled.

This has been fixed.

3-7809032181

17661535

(Patch Set 7) For an account with a service having discounts and products, when the service was closed, discounts were applied twice.

This has been fixed.

3-7999475501

17662775

(Patch Set 7) In the previous releases, the pin_inv_send utility was not honoring the pay_type parameter in its command line.

This has been fixed.

3-7993447171

17732221

(Patch Set 7) The PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE opcode was throwing a null pointer error in prep input helper opcode for some cases.

This has been fixed.

3-7826832831

17732223

(Patch Set 7) During reauthorization flow, even when the threshold points were breached, the in-session notifications for threshold breach were not generated.

This has been fixed.

3-7952251921

17766402

(Patch Set 7) In the previous releases, there were some memory leaks in the fm_subs_utils_handle_system_events function during service creation flow.

This has been fixed.

Not applicable

17768658

(Patch Set 7) In the previous releases, with an account in collections, when you tried to schedule payments through Collections Center, it was throwing the "Unable to Invoke Promise to Pay" error.

This has been fixed.

3-7965032891

17770280

(Patch Set 7) An incorrect product POID in the input to the PCM_OP_RATE_GET_PRODUCT opcode was causing the CM to crash without returning an appropriate error.

This has been fixed.

3-8055649891

17770283

(Patch Set 7) Conversion Manager was creating empty data files for the custom tables where classes other than service_telco_t were extended using mySubstruct.

This has been fixed.

3-7859806331

17789366

(Patch Set 7) The performance of PCM_OP_READ_FLDS with two levels of sub-arrays has now been improved.

3-7051155361

17789372

(Patch Set 7) With cm_vas running, the CPU utilization was observed to be very high, affecting performance.

This has been fixed.

3-7680101571

17807491

(Patch Set 7) During rerating, deferred taxation was not computed for the resulting delta amount.

With this patch, deferred taxation is now enabled with the ApplyDeferredTaxDuringRerating business parameter.

3-7964127861

17807493

(Patch Set 7) The deferred taxation was not replayed during the rerating workflow and was only taken care of during the next billing operation.

With this patch, deferred taxation is calculated and applied during the rerating workflow.

3-7884394191

17819271

(Patch Set 7) The GetResourceBalance interface was not considering first usage sub-balances at the time of returning the result to the caller.

This has been fixed.

3-8034642061

17841885

(Patch Set 7) When a subscription service was already deactivated or closed, it was not possible to process the service orders for the member services.

This has been fixed.

3-7899039371

17845537

(Patch Set 7) Refund was failing for accounts with multiple bill units and the open item accounting type.

This has been fixed.

3-7369981281

3-8101561327

17891994

(Patch Set 7) The connection to the Communications Tax Q (CTQ) schema was being dropped randomly and the tax calculation was failing. In the case of a lost database connection, there were no retries to reconnect and recalculate taxes.

This has been fixed.

3-7985294091

17896045

(Patch Set 7) The pin_rerate utility was throwing an error when used with the -a and -n command-line options.

This has been fixed.

3-7511410011

17932580

(Patch Set 7) While inserting lower or upper functions in the WHERE clause of an SQL statement, the results were not according to those functions.

This has been fixed.

3-8148129781

17935805

(Patch Set 7) When a deal was purchased backdated to a date prior to the last bill run date with the end date set in the future, rating was incorrectly performed, creating an extra credit event.

This has been fixed.

3-8204924731

17966447

(Patch Set 7) During the pipeline upgrade, it was incorrectly prompting for Portal base database value.

This has been fixed.

3-6807250701

16355012

(Patch Set 6) In the previous releases, for a duplicate authorization or re-authorization request the response did not carry adequate information including appropriate quantity and correct expiration_t.

This has been fixed.

3-6829418291

16438180

(Patch Set 6) In the previous releases, Conversion Manager was not supporting the import of data for the PENDING_RECV column of the BILLINFO_T table.

This has been fixed.

3-6878209768

16470594

(Patch Set 6) In the previous releases, the PCM_OP_COLLECTIONS_PROCESS_BILLINFO opcode was not considering the overdue amount and the overdue date sent from the PCM_OP_COLLECTIONS_POL_PROCESS_BILLINFO policy opcode during scenario selection.

This has been fixed.

3-6356222213

16561347

(Patch Set 6) In the previous releases, Conversion Manager was returning success even though it failed to run sqlldr for the .dat files.

This has been fixed. Conversion Manager now throws the appropriate error message.

3-6946457174

16594168

(Patch Set 6) In the previous releases, Conversion Manager was able to import data for the PENDING_RECV column of the BILLINFO_T table from the input XML file only for integer values.

This has been fixed. Conversion Manager can now import data for decimal values.

3-6708809741

16696700

(Patch Set 6) In the Customer Center Payments tab, there was an option to specify "undefined" as the payment method.

With this patch, customization hooks are provided to customize the payment types, so you can remove unwanted payment types.

3-6947731501

16731016

(Patch Set 6) In the previous releases, Java PCM was not recognizing octal encoded data in the flist.

This has been fixed.

3-6854269511

16748630, 16836145

(Patch Set 6) When no specific value for END_T was passed to the PCM_OP_CUST_SET_TAXINFO opcode, it was by default considering the current time as END_T for the EXEMPTIONS array. When the opcode was run, the exemption was being dropped during billing because the exemption was showing as ended.

This has been fixed.

3-6430427641

16780255

(Patch Set 6) When performing a 100% bill level adjustment in Customer Center, an incorrect G/L ID was being picked up.

This has been fixed.

3-7183314521

16816316

(Patch Set 6) When the product end date was the same as the charged to end date, there was an unnecessary refund given to the customer for the last cycle.

This has been fixed.

3-7093022241

16827083

(Patch Set 6) In the previous releases, the sequencer in Roaming Manager was not releasing or reusing database connections. As a result, Roaming Manager was running out of database connections in cases where large numbers of sequencers were configured.

This has been fixed.

3-7214108601

16841109

(Patch Set 6) The pin_recover utility in the rfr mode was failing due to the absence of an amount in the input, though the rfr mode did not require the amount as input.

This has been fixed.

3-6961723971

16841113

(Patch Set 6) The PCM_OP_TCF_AAA_REFUND opcode was not working on a discounted non-currency resource balance impact.

This has been fixed.

3-7086566771

16862104

(Patch Set 6) In the previous releases, during a RAC failover, the messages logged in the dm.pinlog file contained invalid characters.

This has been fixed.

3-7072669711

16865207

(Patch Set 6) In the previous releases, when an under payment is processed with the PCM_OP_PYMT_COLLECT opcode, the opcode was not working properly when the payment amount was passed in the BILLINFO array. The under payment was recorded as full payment.

This has been fixed.

3-6894023281

16865211

(Patch Set 6) In the previous releases, the discount cancellation was not checking the exact discount amount. It was refunding an amount that was originally requested as the discount amount instead of the applied discount amount.

This has been fixed.

3-6648249946

16872618

(Patch Set 6) In the previous releases, the service order was being generated with an IGNORE action while changing the password.

This has been fixed. The action is now CHANGE instead of IGNORE.

3-7002247331

16885166

(Patch Set 6) In the previous releases, when a discount is purchased in the middle of a billing cycle, the existing discount was not getting applied. This was due to the incorrect value of flags set in the purchased_discount block by the discount_analysis plug-in.

This has been fixed.

3-6961723971

16895605

(Patch Set 6) The PCM_OP_TCF_AAA_REFUND opcode was not working correctly for resources that were impacted with discounts.

This has been fixed.

3-7283335571

16898744

(Patch Set 6) When a delayed billing is configured, while billing the parent account in a hierarchy, an object-locking error was thrown by the BRM server.

This has been fixed.

3-7220058897

16906745

(Patch Set 6) In the previous releases, The PCM_OP_GROUP_DELETE_MEMBER opcode was not deleting all the specified members. The opcode was being called multiple times to delete all the members in the group.

This has been fixed.

3-6930943241

16913433

(Patch Set 6) The execute permissions were not granted for procedures to run in a multischema environment.

This has been fixed.

3-7272791181

16933466

(Patch Set 6) When the purchase proration for cycle forward fees was set to do not apply charge for the entire cycle, the subsequent billing triggered through pin_cycle_fees was not charging cycle fees.

This has been fixed.

3-7250955071

16934725

(Patch Set 6) If the resource names defined in the pin_beid file contained numeric values, they were not parsed properly by the load_pin_beid utility. This affected the validity for the resources.

This has been fixed.

3-7076809871

16934728, 16966893

(Patch Set 6) In the previous releases, if the discount is inactivated using the PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS opcode, the discounts were not being applied.

This has been fixed.

3-7184257601

16934758

(Patch Set 6) When accounts were migrated using Conversion Manager, the actual number of balance groups created was not correct.

This has been fixed.

3-7015326341

16934767

(Patch Set 6) Conversion Manager was not migrating the /billinfo objects that do not reference the /payinfo objects.

This has been fixed.

3-7342201341

16946351, 17181678

(Patch Set 6) In the previous releases, the customer registration opcodes were throwing an error if password information was not passed in for a service. The passwords may not be present in all cases.

This has been fixed.

3-7239765781

16961321

(Patch Set 6) In the previous releases, a payment of zero currency units was only creating a payment event, but this event was not being linked to an item. Because of this it is not possible to track the payment using the item number and this payment will not show in Customer Center.

This has been fixed.

3-7290599911

16961325

(Patch Set 6) When invoking the real time pipeline charging functionality, the custom fields populated in the pre_rating policy were getting dropped even before the pipeline functionality is called for rating.

This has been fixed

3-7319414481

16966896

(Patch Set 6) In the previous releases, the pin_state_change utility was picking accounts whose service expiration time was on the same day (that is, the end of the day), even when the expiration time was not actually reached.

This has been fixed.

3-7478053428

16977278

(Patch Set 6) In the previous releases, discounts with cycle validity flags set to No discount were being considered for discount calculation during the current period.

This has been fixed.

3-7320020581

16990087

(Patch Set 6) In the previous releases, semaphore was not updating the parameter value in the iScript plug-in's in-memory.

This has been fixed.

3-6914734984

16990333

(Patch Set 6) When a dbUpdate was being done for a service, an intermittent crash was observed during the check for initialization of the service.

This has been fixed.

3-6677554101

16996683

(Patch Set 6) The cycle fold balance impact was incorrectly calculated when plan transition and account suspension were carried out on the same day.

This has been fixed.

3-7389622561

16997854

(Patch Set 6) In the previous releases, a simple inactivation followed by reactivation of products on the same day was not resulting in net zero currency units of charge or credit to the customer.

This has been fixed.

3-7231970841

17000499

(Patch Set 6) In Collections Manager, it was not possible to update the payment details of the promise-to-pay action if that action was in waiting for dependent status.

This has been fixed.

3-7313814311

17000502

(Patch Set 6) In Collections Manager, with collection dependency enabled, it was not possible to add an action when a canceled or completed action exists.

This has been fixed.

3-7257949001

17000504

(Patch Set 6) In the previous releases, it was not possible to control milestone action status in the PCM_OP_COLLECTIONS_POL_HANDLE_BREACH_PROMISE_TO_PAY policy opcode. Also, the total payment calculation was not correct during the running of the promise-to-pay action for collections group cases.

This has been fixed.

3-7282839891

17010199

(Patch Set 6) In the previous releases, the cycle forward impacts associated with the account level products and discounts were being applied only for the first cycle; there was no impact from the second cycle onwards.

This has been fixed.

3-7418540881

17010871

(Patch Set 6) In the previous releases, Conversion Manager was not allowing migration of accounts with service of /service type.

This has been fixed.

3-7327211551

17016872

(Patch Set 6) In the previous releases, running pin_cycle_fees with a purchase option and products having future end dates was returning an error.

This has been fixed.

3-7048441791

17023458

(Patch Set 6) In the previous releases, Suspense Manager was not able to recycle suspended call details records (CDRs) in a multischema environment.

This has been fixed.

3-7283727351

17029887

(Patch Set 6) In the previous releases, Bill Now was failing for a bill unit when a service under the bill unit is in an hierarchy.

This has been fixed.

3-7316047581

17033120

(Patch Set 6) In the previous releases, the account adjustment opcodes called with the PCM_OPFLG_CALC_ONLY flag were failing to return balances.

This has been fixed.

3-7381130861

17043206

(Patch Set 6) A change in the pay type for the parent account was resulting in a change in the billing cycle and accounting cycles left for the subordinate account.

This has been fixed.

3-7261992151

17043210

(Patch Set 6) In the previous releases, when Bill Now is run during a delayed billing period, the cycle charges were not calculated correctly.

This has been fixed.

3-7375919621

17055806

(Patch Set 6) When using PCM_OP_SUBSCRIPTION_SET_PRODINFO to set cycle_end_t in the future, cycle charges were not applied correctly.

This has been fixed.

3-7426660313

17060629

(Patch Set 6) In the previous releases, Conversion Manager was not properly migrating multiple instances of the purchased bundle.

This has been fixed.

3-7407640961

17060634

(Patch Set 6) In the previous releases, Conversion Manager was not properly populating mod_t and effective_t of the /billinfo object.

This has been fixed.

3-7469832438

17067041

(Patch Set 6) In the previous releases, Conversion Manager was throwing a NULL pointer exception while creating a balance group for a parent service that has subscription services.

This has been fixed.

3-7483386371

17072719

(Patch Set 6) In the previous releases, pin_ctl clear was not working.

This has been fixed.

3-7321977301

17079747

(Patch Set 6) In Collections Manager, with the collections_action_dependency parameter enabled, action status was not correctly handled while rescheduling an action.

This has been fixed.

3-7340647231

17079750

(Patch Set 6) In Collections Manager, after canceling the waiting for a dependent action, the next action was made pending.

This has been fixed.

3-7475044051

17086282

(Patch Set 6) In the previous releases, converting the epoch time to a human-readable date was done incorrectly and was causing errors in the collection dates.

This has been fixed.

3-7316813971

17156585

(Patch Set 6) In the case of multi-ratable user metric (RUM) configuration, the rating was encountering an "array out of bounds" error resulting in memory corruption and core dump.

This has been fixed.

3-7237739311

17156588, 17372813, 17372844

(Patch Set 6) In the previous releases, the load_config utility was not supporting load configurations for collection scenarios and collection actions. The load_config utility could not be used for deploying custom configuration objects.

This has been fixed.

3-7412207741

17159906

(Patch Set 6) In the previous releases, in a single transaction that had more than one financial transaction with different backdated dates, billing was not getting triggered for all the backdated dates.

This has been fixed.

3-6955426771

17159910

(Patch Set 6) In the previous releases, the PCM_OP_BILL_DEBIT opcode was not able to do an adjustment to a non-currency resource beyond the configured credit_floor value, because the credit floor check was done irrespective of the extra_rate_flags set to "no check".

This has been fixed.

3-7442223611

17159913

(Patch Set 6) When attempting to run load_localized_strings payment_channel.es, parsing of the input file was failing for Spanish locales.

This has been fixed.

3-7452643191

17170371

(Patch Set 6) The transaction was not rolled back when the PCM_OP_COLLECTIONS_EXEMPT_BILLINFO opcode exited the transaction while attempting to remove exemptions from collections for an account that was not exempted and was already in collections with active scenarios.

This has been fixed.

3-6898960621

17175838

(Patch Set 6) The write-off operation was failing when the event had more than one tax balance impact with the same PIN_FLD_QUANTITY and TAX_CODE entries.

This has been fixed.

3-7439243501

17183805

(Patch Set 6) PCM_OP_CUST_CREATE_CUSTOMER was throwing an error when a transaction was closed because the service password was not available.

This has been fixed.

3-7434135691

17183813

(Patch Set 6) In Conversion Manager, it was not possible to link multiple bill units of the same account.

This has been fixed.

3-5745234151

17190562

(Patch Set 6) When multiple Data Manager (DM) contexts were used with transaction handling opcodes, the generated events were not published.

This has been fixed.

3-7404688921

17212487

(Patch Set 6) The account write-off was failing when a product was canceled and purchased on the same day, followed by an account adjustment.

This has been fixed.

3-7218665021

17219147

(Patch Set 6) When multiple threads were trying to lock the same balance group object, there was a deadlock in pin_crypt_upgrade (which is a multi-threaded application.)

This has been fixed.

3-7465451901

17219149

(Patch Set 6) The performance of Account Migration Manager while purging is now improved.

3-6295751911

17241784

(Patch Set 6) In the previous releases, the first usage validity was not being set during the authorization and the subsequent reauthorizations were not getting the resources reserved from the correct sub-balances for a resource in the balance group, in case the first usage validity sub-balances exist.

This has been fixed.

3-7579664611

17255486

(Patch Set 6) In Collections Manager, while performing rescheduling with slip days specified, the action's statuses were not correctly set.

This has been fixed.

3-7543019681

17262278, 17266954

(Patch Set 6) When billing a hierarchy of accounts, subordinates were locked for updating the bill objects, affecting the billing performance when the number of subordinates was very large. This was a performance concern because subordinates were getting locked for an extended period of time.

This has been fixed.

3-7461386911

17282792

(Patch Set 6) When a non-currency bundle was purchased with a backdated start date, the bundle was not aligned to the monthly accounting cycle.

This has been fixed.

3-7529765281

17293232

(Patch Set 6) The load_price_list utility write operation was failing because PIN_FLD_CODE was not handled properly in case of an event rating map in products.

This has been fixed.

3-7606314529

17311877

(Patch Set 6) Conversion Manager was not populating data into VANITY, PERMITTED, ORIG_NETWORK_ID, and RECENT_NETWORK_ID columns in the DEVICE_NUM_T table.

This has been fixed.

3-7504743251

17316333

(Patch Set 6) In the previous releases, it was not possible to pay charges for a service belonging to an account by another account in a different hierarchy.

This has been fixed.

3-6955426771

17316336

(Patch Set 6) The PCM_OP_BILL_DEBIT opcode was allowing credit_limit to be exceeded.

This has been fixed.

3-7529868431

17324537

(Patch Set 6) For scenarios where a plan transition and account suspension were run on the same day, the cycle fold balance impact was incorrectly calculated.

This has been fixed.

3-7635299721

17352544

(Patch Set 6) The EVAL function was not identifying the discount model and hence it was not possible to gather any information about the discount being processed.

This has been fixed.

3-7583896271

17353851

(Patch Set 6) When there were two or more purchased products of the same rateplan with different priorities, even though rating was done correctly using the highest priority product, the lower priority product of the same rateplan was incorrectly termed to be used for rating in the event data record (EDR) container.

This has been fixed.

3-6978588193

17360596

(Patch Set 6) Due to daylight saving time (DST) changes, the difference between cycle start and cycle end may not result in whole days, resulting in an incorrect scale recalculation.

This has been fixed.

3-7761024621

17411295

(Patch Set 6) When the PCM_OP_COLLECTIONS_PROCESS_BILLINFO opcode was called with disable_pcm_mempool set to 1 in the CM's pin.conf, the opcode was returning PIN_ERR_TRANS_ALREADY_OPEN.

This has been fixed.

3-7745151311

17416239

(Patch Set 6) Setting cycle_end_t to 0 using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode did not trigger cycling.

This has been fixed.

3-7740495438

17418405

(Patch Set 6) The CYCLE_FEE_START and CYCLE_FEE_END values updated within the PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL policy opcode were not being honored by rating.

This has been fixed.

3-7742915251

17426336

(Patch Set 6) When PCM_OP_SUBSCRIPTION_PURCHASE_DEAL is called in calc-only mode specifying PIN_FLD_CYCLE_END_T in the input, the response omitted the PIN_FLD_TOTAL block.

This has been fixed.

3-7792071021

17444822

(Patch Set 6) The purchase fees for products whose deferred time coincides with the billing time were not considered in the current cycle, even though the pin.conf file's purchase_fees_backcharge parameter was enabled.

This has been fixed.

3-7264288811

17484683

(Patch Set 6) When a tax engine such as dm_vertex was down, the tax calculation succeeded with zero tax instead of throwing an error and aborting the transaction.

This has been fixed.

3-7644617461

17544947

(Patch Set 6) The PCM_OP_BILL_MAKE_INVOICE opcode was not picking up events generated by trial billing.

This has been fixed.

3-3681399471

13513732

(Patch Set 5) In a few database errors, dm_oracle was throwing the PIN_ERR_NO_MEM error.

This has been fixed. dm_oracle now throws the PIN_ERR_STORAGE error instead of the PIN_ERR_NO_MEM error.

3-4991121561

13897894

(Patch Set 5) The ISC_GetResourceBalance.isc iScript was not available in the Pipeline_Home/iScriptLib/iScriptLib_Standard directory.

This has been fixed. Also, the updated signature of the getResourceBal() function is used in the ISC_GetResourceBalance.isc iScript.

3-5464675459

13962948

(Patch Set 5) When billing and invoicing were run in the same transaction, invoicing does not pick up the events created by billing.

This has been fixed.

3-3848978661

14362830

(Patch Set 5) In the previous releases, the same refund amount was being shown twice: once in the billed-earned report and again in the previous-billed-earned report.

This has been fixed.

3-7360443161

14550448

(Patch Set 5) The credit control notifications were not working for grants.

This has been fixed.

3-6107699411

14575290

(Patch Set 5) The current_bal information was missing the notification; for a grant, the threshold notification was not generated.

These issues have been fixed.

3-6107699411

14575293

(Patch Set 5) The current_bal information is now positioned appropriately so that the load_notification_event utility does not fail.

3-6161449871

14601829

(Patch Set 5) In the previous releases, for non-currency resources, the pipeline was not updating the credit profile changes from BRM into pipeline.

This has been fixed.

3-5586566201

14678167

(Patch Set 5) In the previous releases, the fixed threshold data was not supporting a value of more than 2 GB for Pipeline Manager.

A new optional field, PIN_FLD_AMOUNT, has been introduced to accept a value larger than 2 GB to indicate a fixed threshold in the input for the PCM_OP_BILL_SET_LIMIT_AND_CR opcode.

3-5586566201

14678171

(Patch Set 5) In the previous releases, the fixed threshold data was not supporting a value of more than 2 GB.

A new optional field, PIN_FLD_AMOUNT, has been introduced to accept a value larger than 2 GB to indicate a fixed threshold in the input for the PCM_OP_BILL_SET_LIMIT_AND_CR opcode.

3-6056883991

14755553

(Patch Set 5) In the previous releases, when the CUG profile was shared, there was an issue where the member usage records were not properly tagged.

This has been fixed. The CUG profile sharing now works properly.

3-6166015201

15827570

(Patch Set 5) In the previous releases, BRM was not always honoring the order in which item tags were specified in the config_item_tags.xml configuration file.

This has been fixed.

Note: This fix may result in an undesired item tag being used if the incorrect order was producing the correct results. In this case, check the order and realign.

3-5578174271

15878487

(Patch Set 5) In the previous releases, Suspense Manager was not displaying the recycle time in the local timezone.

This has been fixed. A new entry, display.local.timezone, is introduced in the custom.properties file. When set to true, it will display all times in the local timezone; when set to false, the earlier behavior continues.

3-6256008521

15897284

(Patch Set 5) In the previous releases, CMT was not managing rollovers correctly.

This has been fixed. A new element, RollData, is added in the Sub balances array in the CMT_Balances.xsd file. If RollData is populated in the XML, CMT will use the rollover specified in the XML, otherwise CMT will compute its own rolldata value based on UOR and Frequency.

3-5879088531

15903415

(Patch Set 5) In the previous releases, there was an issue of rounding of WHEN_T when a deferred action was scheduled. The schedule time was always rounded to midnight by default.

This has been fixed. A new business parameter, UseExactTimeForDeferredAction, is added to prevent the rounding so that the deferred action is considered for running at the specified time.

3-5967291991

15922535

(Patch Set 5) A new billing business parameter, SkipCheckForSubordinatesBilled, has been added that allows you to enable/disable checking that all the children are billed before billing the parent. The default is false, enabling the check.

3-5966987241

16016847

(Patch Set 5) In the previous releases, there was an issue with rounding of tax on the cycle fees when canceled after full-tax-only adjustment.

This has been fixed.

3-6100423051

16029368

(Patch Set 5) With this patch, you can see an improved performance while adding a new member into the discount sharing group having a large number of members using the SHARING_GROUP_MODIFY opcode.

3-5398269781

16102996

(Patch Set 5) With this patch, you can see an improved performance of Rated Event (RE) Loader loading events rated by the batch rating pipeline.

3-6553157811

16191203

(Patch Set 5) In the case of a discount sharing group, when a product is canceled, the shared discount was not refunded.

This has been fixed.

3-5363354871

16191192

(Patch Set 5) With this patch, the 30 days proration calculation is correctly applied when the number of days in a month is 28, 29, or 31 days.

3-6557250571

16194478

(Patch Set 5) In the previous releases, while creating an object with subelements in it and an auditable flag is set for the object, the "au_au_* table not found” error may appear.

This has been fixed.

3-6706144278

16216595

(Patch Set 5) The upgrade framework now works with encrypted passwords in the pin-setup.values file.

3-5848566207

16216632

(Patch Set 5) With this patch, if custom information is passed into the PCM_OP_RATE_EVENT opcode through the PIN_FLD_CUSTOM_INFO structure, the opcode will retain this structure in the output.

3-5969777971

16226684

(Patch Set 5) When sequential discounting is enabled in combination with in-advance billing, the discount that was purchased in mid-cycle was getting incorrectly applied.

This has been fixed.

3-3744892821

16233670

(Patch Set 5) In the previous releases, the best pricing deal was not considered for taxation.

This has been fixed.

3-6536108181

16273957

(Patch Set 5) In the previous releases, the EDR buffer was not correctly populated for duplicate EDRs by FCT_Suspense.

This has been fixed.

3-6558232211

16290243

(Patch Set 5) The pin_inv_accts utility is now thread safe with mutexes to avoid crashes.

3-6597485341

16296942

16481299

(Patch Set 5) You can now perform validations in the PCM_OP_SIM_POL_ORDER_CREATE policy opcode before the order creation opcode is called.

3-6688704381

16308412

(Patch Set 5) If a discount POID is set as NULL to the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode, it was returning an error, without closing the transaction.

With this patch, in such cases, the transaction exits.

3-6758615281

16314143

(Patch Set 5) You can now commit a product with multiple events in rate_plan_selector to the database.

3-5937980521

16323158

(Patch Set 5) In the previous releases, there were memory overflow issues in the rerating flow.

This has been fixed.

3-6333796831

16323161

(Patch Set 5) In Pricing Center, you can now include a hyphen (-) character in the plan list name.

3-5316366321

16329173

(Patch Set 5) When canceling a product having in-advance billing configured for the cycle fees without proration, the charge was not correctly returned.

This has been fixed.

3-6762112098

16343194

(Patch Set 5) With this patch, the password in the dm_oracle logs is masked.

3-6398560431

16346424

(Patch Set 5) In the previous releases, the item assignment was not correct after subscription transfer.

This has been fixed.

3-6770524071

16346427

(Patch Set 5) In a multischema setup, after terminating a transaction if you tried to open a new transaction on the same object type, it was throwing a TRANS_ALREADY_OPEN error.

This has been fixed.

3-6736622891

16361907

(Patch Set 5) The PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS opcode was dumping core.

This has been fixed.

3-6744523841

16361909

(Patch Set 5) In the previous releases, the cycle fees were not applied correctly (both cycle forward and cycle arrears events), when a service is suspended and reconnected on the same day as the service creation date.

This has been fixed.

3-6453274901

16361913

(Patch Set 5) With this patch, the audit search for au_rate_plan and au_rate has been modified to improve cancellation and backdating performance.

3-6385736491

16374600

(Patch Set 5) In the previous releases, the batch controller was logging errors after successfully processing a rerate request file.

This has been fixed.

3-6825841441

16382143

(Patch Set 5) In the previous releases, adjustment was not happening on the custom delayed events in a pipeline.

This has been fixed.

3-6808115451

16426585

(Patch Set 5) In the previous releases, Collections Center was dropping characters while writing them to the database.

This has been fixed.

3-6808115451

16426588

(Patch Set 5) In the previous releases, Collections Center was dropping characters while writing them to the database.

This has been fixed.

3-6804436351

16426597

(Patch Set 5) In the previous releases, the suspended payments were under the customer account instead of the suspense account.

This has been fixed.

3-6731225751

16431351

(Patch Set 5) In the previous releases, the dummy deal purchase was generating errors when the validate_deal_dependencies parameter is enabled.

This has been fixed.

3-6432547211

16446334

(Patch Set 5) With this patch, the pin_crypt_upgrade utility is enhanced to encrypt the unencrypted data when migrating from MD5 to AES encryption.

3-6612054981

16464991

(Patch Set 5) In the previous releases, in rollback_susp_pre_updater_sp, while updating the suspended_usage_t record, the mod_t was not updated.

This has been fixed.

3-5236524741

16469872

(Patch Set 5) In discount sharing group scenarios, where sequential discounting is enabled, updating the discount with an end date was not resulting in a refund for member services.

This has been fixed.

3-6715397251

16477213

(Patch Set 5) In previous releases, the Data Manager (DM) stopped when the transaction timed out.

This has been fixed.

3-6835556761

16477215

(Patch Set 5) In the previous releases, when migration occurred from a non-partitioned class to a partitioned class, the pruning condition was not considering PARTITION_MIGRATE.

This has been fixed.

3-6204691689

16488502

(Patch Set 5) In Pipeline Manager, while validating the number of fields in the input file, if the number of fields is one less than that defined in the stream description, an incorrect error message was thrown.

This has been fixed. A check on the number of fields in the input file has been added, and now the appropriate error message is displayed.

3-6825956161

16502363

(Patch Set 5) In the previous releases, the notification XML from Pipeline Manager was showing an incorrect END_T.

This has been fixed.

3-6612054981

16514056

(Patch Set 5) In the previous releases, after billing, mod_t was not getting updated in bill_t and BILLINFO_T tables.

This has been fixed.

3-6688784471

16521353

(Patch Set 5) In the previous releases, the PCM_OP_SEARCH opcode was not returning all the second-level arrays and it was only returning the first second-level array mentioned in PIN_FLD_RESULTS.

This has been fixed. The PCM_OP_SEARCH opcode now returns all second-level arrays mentioned in PIN_FLD_RESULTS.

3-6843191961

16528734

(Patch Set 5) In the previous releases, payment was failing with the PCM_OP_PYMT_COLLECT opcode, if the PIN_FLD_BILLINFO array is specified in the input flist without PIN_FLD_AMOUNT under it.

This has been fixed.

3-6926130931

16539702

(Patch Set 5) In the previous releases, multiple devices swapping in one request were generating an incorrect service order.

This has been fixed.

3-6837530731

16539705

(Patch Set 5) In the previous releases, any item type products purchased without a deal was throwing an error during rerating.

This has been fixed.

3-2488529721

16551628

(Patch Set 5) In the previous releases, the cmt_mta_cycle_fees utility was creating balances with valid_to set to the migration date.

This has been fixed.

3-6738918671

16565849

(Patch Set 5) In the previous releases, during inactivation or cancellation on the same day as the billing date, fold was considering invalid buckets and was generating incorrect balances.

This has been fixed.

3-6559585011

16572104

(Patch Set 5) During the delayed billing period, if a monthly cycle arrears deal backdated to the previous month is purchased and then the end date of the same deal is updated to the end of the current month, the monthly charges were not calculated correctly.

This has been fixed.

3-6802673491

16577401

(Patch Set 5) In the previous releases, when a backdated cycle product is purchased, the cycle charges were not calculated correctly.

This has been fixed.

3-6746248491

16577406

(Patch Set 5) In the previous releases, the data manager was not allowing creation of the /reservation_list objects with POID_ID greater than 2147483647 (2^32-1).

This has been fixed.

3-6878694537

16579282

16579284

(Patch Set 5) In the previous releases, fm_cust_pol was missing the names of some countries, as defined in ISO 3166.

With this patch, the fm_cust_pol is now up to date with all country names.

3-4539937001

16579311

(Patch Set 5) In the previous releases, for bill time discounting, the correct sub-balances were not being considered for impact.

This has been fixed.

3-6730679201

16600769

(Patch Set 5) When moving accounts under a hierarchy from paying to non-paying type, an error occurred if the paying account being moved is closed.

This has been fixed.

3-6521951561

16600772

(Patch Set 5) With this patch, the pin_bill_day utility was optimized to improve the performance of calculating cycle forward fees.

3-6988827201

16607116

(Patch Set 5) In the previous releases, pipeline was freezing when a semaphore was sent prior to the completion of the earlier one.

This has been fixed.

3-6780016671

16607120

(Patch Set 5) In the previous releases, when running multiple RE Loader processes, deadlock errors were seen.

This has been fixed.

3-6807023828

16626084

(Patch Set 5) The loadpricelist utility supports retrieval of zone maps separately into a file by the parameter -z. But the loadpricelist Help did not mention this option. The Help is now updated to address the missing parameter.

3-6904646871

16629294

(Patch Set 5) In a multischema setup, when calling the PCM_OP_PRICE_COMMIT_PRODUCT opcode to delete a product, it was deleting that product even if the product was purchased by an active account.

This has been fixed.

3-2203320611

16660464

(Patch Set 5) In the previous releases, Pipeline Manager had intermittent issues with closing intermediate files.

This has been fixed.

3-7034481951

16661232

(Patch Set 5) In the previous releases, the breakup of tax amounts returned by dm_vertex (Vertex Communications Tax Q Series) was not matching the total tax amount in the event's tax balance impact, due to rounding.

This has been fixed.

3-7042543211

16672129

(Patch Set 5) In the previous releases, the pin_cycle_fees utility with purchase option was hanging when there were products with no purchase fee event defined.

This has been fixed.

3-6845973891

16672136

(Patch Set 5) In the previous releases, the real time discounting was invoked irrespective of the availability of resources for discounting.

With this patch, the discount data is made available to the prerating policy opcode, so that a decision can be made in the policy opcode to invoke real-time discounting.

3-7007112741

16678351

(Patch Set 5) The usage of entries like 'AND', '!', 'OR' in the ifw_sync_queuenames file was not clear by the inline comments.

A new inline comment section is added in the ifw_sync_queuenames file elaborating the usage so as to filter events based on customer's criteria.

3-6901848941

16686142

(Patch Set 5) Whenever a CDR was processed and filter set rule did not match, the "EDR index creation failed: illegal blocktype" error was logged. This error was being reported because of memory corruption.

This has been fixed. The filter set data is now extracted from the global memory pool, thus avoiding any possible memory corruption.

3-7045253131

16686148

(Patch Set 5) In the previous releases, the PCM_OP_PRICE_SET_PRICE_LIST.xml file and the PCM_OP_PRICE_GET_PRICE_LIST.xml file were not published as part of JCA Resource Adapter installation.

With this patch, these two files are now published.

3-6924162991

16686152

(Patch Set 5) In the previous releases, you could settle the same event dispute more than once, which is incorrect.

With this patch, a check is placed to make sure that once an event dispute is settled, it cannot be resettled.

3-7103041971

16715852

(Patch Set 5) In the previous releases, during the cancellation of products initiated from pin_cycle_fees, the products that were not supposed to be canceled were also being canceled.

This has been fixed.

3-6977890801

16715869

(Patch Set 5) In the previous releases, the RE Loader's pre-updater procedure was generating run-time errors while updating rerated events with the virtual column feature enabled.

This has been fixed.

3-6902693201

16715873

(Patch Set 5) In the previous releases, in a multischema environment, it was not possible to remove a suspended payment from a suspense account in schemas other than the primary.

This has been fixed.

3-6408914974

16723612

(Patch Set 5) In the previous releases, the multithreaded application (MTA) was crashing with double free corruption error.

This has been fixed in the MTA framework.

3-7023360601

16731009

(Patch Set 5) With the virtual column feature enabled, the RE Loader's preprocessor was changing all virtual column POID type strings in CDR to their corresponding virtual numbers, affecting the user customizations in non-virtual column strings.

With this patch, the virtual column POID type string substitution is restricted to the data corresponding to the virtual column types.

3-7099004551

16731014

(Patch Set 5) In the previous releases, the scale calculation was incorrectly applied while canceling tailor-made products.

This has been fixed.

3-6942065541

16748628

(Patch Set 5) In the previous releases, with a large discount amount and quantity during computation resulted in throwing an exception.

This has been fixed.

3-6780016671

16768098

(Patch Set 5) In the previous releases, RE Loader was failing due to deadlock, as data in tmp_unprocessed_events_t was not being deleted.

This has been fixed.

3-4199671371

16777978

(Patch Set 5) In the previous releases, when a product with multiple rate plans is purchased in the middle of the cycle and canceled in the same cycle, an error was thrown indicating non-availability of a valid product to rate the event.

This has been fixed.

3-7147494481

16797221

(Patch Set 5) In the previous releases, when pin_cycle_fees with purchase option was run, even purchased products for which purchase_start_t is in the future were also being considered.

This has been fixed.

3-6967270651

16813503

(Patch Set 5) The opcode input specification for the PCM_OP_ACT_SCHEDULE_DELETE opcode has been updated. The input specification now says that the schedule object will always be deleted even if the status is non-deletable(3) except for the PCM_OP_CUST_SET_STATUS opcode and the PCM_OP_CUST_UPDATE_SERVICES opcode.

3-6924316611

16817660

(Patch Set 5) A new field, TIMEZONE_ID, is introduced in the balance breach notification XML. The XSD file is accordingly updated with this new field.

3-7220058897

16832343

(Patch Set 5) In the previous releases, the PCM_OP_GROUP_DELETE_MEMBER opcode was not deleting all the members in the /group/sponsor object.

This has been fixed.

3-7072669711

16936803

(Patch Set 5) In the previous releases, if there was no PIN_FLD_AMOUNT under the billinfo array in the input for the PCM_OP_PYMT_COLLECT opcode, the payment was considered to be in full, irrespective of CHARGES specified in the input.

This has been fixed. The amount specified in CHARGES will now be used as the payment amount.

3-6430427641

16937930

(Patch Set 5) In the previous releases, an incorrect G/L ID was being assigned when doing 100% bill level adjustment.

This has been fixed.

3-7317345921

16940416

(Patch Set 5) In the previous releases, the restart of DM Oracle was failing due to socket issues.

This has been fixed.

3-6930943241

16941765

(Patch Set 5) In the previous releases, if the virtual columns were generated using pin_virtual_gen, modifying the event or any subclasses of event was throwing an error.

This has been fixed.

3-6961723971

16944676

(Patch Set 5) The PCM_OP_TCF_AAA_REFUND opcode was not working on discounted non-currency balance impact.

This has been fixed.

3-5577069681

13959245

(Patch Set 4) The missing C++ header files are now included in the Pipeline PDK.

3-6280850831

14730135

(Patch Set 4) During installation, all the required load utilities are generated to ensure that the installation of optional managers is successful.

3-6484200311

15934302

(Patch Set 4) To improve database schema upgrade performance, the upgrade process queries user_tab_columns to check whether a new column has been added to a table.

3-6597485341

16051864

(Patch Set 4) While creating Subscriber Identity Module (SIM) orders, you can now add custom validations through the PCM_OP_SIM_POL_ORDER_CREATE policy opcode.

3-6608970641

16077034

(Patch Set 4) You can now include a wild card '?' in the Number Administrator search string; for example, if you have created a block A7, you can search for the block using A?.

3-6665458741

16207517

(Patch Set 4) The tax information was not available for the PCM_OP_BILL_POL_BILL_PRE_COMMIT policy opcode in the Bill Now workflow in the delayed period.

Changes were made to call the PCM_OP_BILL_POL_BILL_PRE_COMMIT policy opcode after tax computation, so that the tax information is available in the PCM_OP_BILL_POL_BILL_PRE_COMMIT policy opcode.

3-5844217331

14232013

(Patch Set 3) After building the fm_bill_pol_custom library, when you start the CM, the custom library is now loaded successfully.

3-6108849061

14550665

(Patch Set 3) Fixed issues found during BRM upgrade.

3-6314208771

14757302

(Patch Set 3) Pricing Center can now correctly export products with multiple currencies.


Fixed Known Problems

Table 1-2 lists known problems in previous patch sets that are now fixed.

Table 1-2 Known Problems Fixed

SR Number Bug Number Resolution

Not applicable

13960159

You can now run RE Loader on an AIX system that contains IMDB Cache Manager.

Not applicable

14526282

You can now use the PCM_OP_COLLECTIONS_GROUP_GET_BILLINFO opcode to retrieve pending receivables for an account that contains multiple bill units.

Not applicable

17644766

You can now use the loadpricelist utility when SSL is enabled in CM.