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 Maintenance Patch Set 1.
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-10261348621 |
20543454 |
(Maintenance Patch Set 1) In the previous releases, during rerating with the AllocateReratingAdjustments business parameter enabled, if an original item was not found for an adjustment, the rerating process was failing with an error message instead of just a warning. This has been fixed. |
|
3-10282666271 |
20580074 |
(Maintenance Patch Set 1) In the previous releases, when an event did not have a service reference, recording each prerated event was creating a new item at the account level in the system. This has been fixed. |
|
3-10238714961 |
20584864 |
(Maintenance Patch Set 1) In the previous releases, the POID sequences were getting exhausted quickly and after exhausting the allowed sequence, the pin_rel utility was rejecting the files because the POID sequence was out of bounds. This has been fixed. |
|
3-10293093941 |
20601260 20616928 |
(Maintenance Patch Set 1) In the previous releases, after a plan transition, if a comprehensive rerating was performed for a period earlier than the plan transition, the items were not properly allocated for the rerated events. This has been fixed. |
|
3-10373813551 |
20670369 |
(Maintenance Patch Set 1) In the previous releases, after a subscription transfer, when rerating was performed, the validity dates set for the non-currency resources were incorrect. This has been fixed. |
|
3-10285773521 |
20707738 |
(Maintenance Patch Set 1) Conversion Manager was not populating the record IDs or element IDs for the service-level promotion object correctly based on the input data. This has been fixed. |
|
3-10430483161 |
20728521 |
(Maintenance Patch Set 1) In the previous releases, after a line service transfer, when rerating was done for the source account from which the line was transferred, the validity of the cycle grant was not updated correctly to the time at which the transfer took place, but instead it was set to the billing date of the account to which the line was transferred. This has been fixed. |
|
3-8254002681 |
20748847 |
(Maintenance Patch Set 1) The USC_MAP iScript required optimizations for using complex regular expressions. This has been fixed. |
|
3-10226840141 |
20753835 |
(Maintenance Patch Set 1) The upgrade script for BRM 7.5 Patch Set 9 was not backing up the files and also the updates made to some configuration or script files were having an incorrect path. This has been fixed. |
|
3-10426548251 |
20762874 |
(Maintenance Patch Set 1) In the previous releases, when purchasing a deal, an error indicating exceeding the credit limit was thrown incorrectly. This has been fixed. |
|
3-10445099231 |
20770712 |
(Maintenance Patch Set 1) In the previous releases, the PCM_OP_SEARCH base opcode was not working with the Group By clause. This has been fixed. |
|
3-10450127891 |
20789186 20803791 |
(Maintenance Patch Set 1) In the previous releases, when a product was purchased and canceled on the same day with proration set to Charge for the entire cycle, and later if rerating was done, the rerating flow was calculating charges differently compared to the rating. Also, the resource sub-balance validity was not getting set to the cancellation time during the rerating. This has been fixed. |
|
3-10468216051 |
20813075 |
(Maintenance Patch Set 1) In Conversion Manager, when importing some tables, MOD_T was set to NULL instead of a proper value. This has been fixed. |
|
3-10504790741 |
20827660 |
(Maintenance Patch Set 1) In the previous releases, during rerating, discounts associated with a discount sharing group were not considered, resulting in incorrect balance impacts. This has been fixed. |
|
3-10238213241 |
20865577 |
(Maintenance Patch Set 1) In the previous releases, when cycle end_t discount was moved from a future cycle to the current cycle and then moved from the current cycle to the future cycle, the discount calculations were incorrect. This has been fixed. |
|
3-10479032591 |
20865590 21367571 |
(Maintenance Patch Set 1) In the previous releases, when Customer Center event browser was used to browse events pertaining to an account in collections, the event descriptions for /event/schedule/modify and /event/activity/collections/promise_to_pay were blank. This has been fixed. |
|
3-10131283021 |
20869650 |
(Maintenance Patch Set 1) In the previous releases, inactivating and reactivating long cycle products was resulting in reactivation charging as a series of month-long charges instead of a single long cycle charge. This has been fixed. |
|
3-10490996091 |
20908660 |
(Maintenance Patch Set 1) In the previous releases, when running the pin_monitor_balance utility to update the balance monitors, deadlocks were observed due to the balance group locking the account while updating the status in the /monitor_queue objects. This has been fixed. |
|
3-10572022381 |
20909982 |
(Maintenance Patch Set 1) In the previous releases, when rerating was run on a closed account, the monthly cycle fees were not reapplied. This has been fixed. |
|
3-10401734041 |
20921774 |
(Maintenance Patch Set 1) In the previous releases, when a discount was purchased backdated to a date which was earlier than the product purchase date, the discount was not applied correctly. This has been fixed. |
|
3-10571864541 |
20929227 |
(Maintenance Patch Set 1) If an event has a mix of balance impacts and the last one in that is a non-currency balance impact, the pin_rel utility was not inserting journals into the database. This has been fixed. |
|
3-10573768511 |
20948696 |
(Maintenance Patch Set 1) In the previous releases, rerating was not completing due to nonexistence of sub-balances. This has been fixed. |
|
3-10246738261 |
20988724 |
(Maintenance Patch Set 1) In the previous releases, for an auto-triggered billing of a subordinate account, if the parent account's billing was skipped, the status of the items was not updated from pending to open. This has been fixed. |
|
3-10119628461 |
21033499 |
(Maintenance Patch Set 1) In the previous releases, for corrective bills, the due dates were updated incorrectly instead of maintaining the actual due dates that were computed during the normal billing. This has been fixed. |
|
3-10439611661 |
21048743 |
(Maintenance Patch Set 1) In the previous releases, the PCM_OP_COLLECTIONS_GET_ACTION_HISTORY opcode was throwing an error in Oracle Data Manager (DM). This has been fixed. |
|
3-10385944441 |
21048748 |
(Maintenance Patch Set 1) In the previous releases, the PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode was throwing the PIN_ERR_NOT_FOUND error. This has been fixed. |
|
3-10295629441 |
21060570 |
(Maintenance Patch Set 1) In the previous releases, when processing credit card payments, if there were any failed payments in the response file, those failed payments were also getting processed as successful payments. This has been fixed. |
|
3-10713112001 |
21067601 |
(Maintenance Patch Set 1) In the previous releases, comprehensive rerating was failing on some accounts. After receiving an error in rerating, the transaction was not rolled back. This has been fixed. |
|
3-10718604951 |
21073288 |
(Maintenance Patch Set 1) In the previous releases, when Provisioning DM was starting up, it was opening an incorrect number of sockets. This has been fixed. |
|
3-9923242751 |
21097643 |
(Maintenance Patch Set 1) In the previous releases, for a non-currency resource with credit limit set to zero (0), it was possible to have the current balance with a value greater than zero (0). This has been fixed. |
|
3-10577232581 |
21105739 |
(Maintenance Patch Set 1) In the previous releases, when a negative discount with a cycle forward event was purchased in a previous billing cycle and the billing was run and later if the discount was canceled in the current billing cycle, the balance impacts were dropped. This has been fixed. |
|
3-10708774291 |
21105744 |
(Maintenance Patch Set 1) In the previous releases, the partition_utils utility was showing a deprecation message with the Perl version 5.18.2. This has been fixed. |
|
3-10245158971 |
21113987 |
(Maintenance Patch Set 1) In the previous releases, when the tax code configured for adjustment action was having more than one different percentage value for different validity periods, and when an adjustment is performed, an invalid tax code percentage (not belonging to the current valid period) was fetched for tax calculation, resulting in an incorrect tax. This has been fixed. |
|
3-10790592468 |
21138111 |
(Maintenance Patch Set 1) In the previous releases, when starting or stopping any BRM service (CM) with the pin_ctl utility, even though the pin_ctl process had successfully completed, it was displaying an error message. This has been fixed. |
|
3-10643615171 |
21147654 |
(Maintenance Patch Set 1) Using Account Migration Manager, when the UNIQUE_ACCT_NO_T table was migrated from one schema to another, the account object ID column was not getting updated with the target database number. This has been fixed. |
|
3-10728919061 |
21155231 |
(Maintenance Patch Set 1) In the previous releases, when a new user created with read-only permissions in Permissions Center is used to log in to Customer Center, the Problem constructing the contact information panel error was displayed. This has been fixed. |
|
3-10788686351 |
21160864 |
(Maintenance Patch Set 1) In the previous releases, the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode was crashing when no information was passed in the BAL_INFO array in the input to the opcode. This has been fixed. |
|
3-6305986021 |
21177291 |
(Maintenance Patch Set 1) In the previous releases, when trying to PRINTDATALOGIN in the pipeline router mode, Pipeline Manager was dumping core. This has been fixed. |
|
3-9636994891 |
21178749 |
(Maintenance Patch Set 1) In the previous releases, on a bill having two items, one associated with a tax and the other without any tax, if a bill-level debit adjustment with tax was performed, the tax was not calculated on the adjustment amount. This has been fixed. |
|
3-10768253411 |
21207832 |
(Maintenance Patch Set 1) In the previous releases, when multiple concurrent operations were carried out on the service-level balance groups of the same account, deadlocks were observed. This has been fixed. |
|
3-10660659161 |
21207836 |
(Maintenance Patch Set 1) In the previous releases, when the service status update functionality is invoked, it was not picking up the correct services for an update, resulting in an incorrect status update to some services. This has been fixed. |
|
3-10853477701 |
21209857 |
(Maintenance Patch Set 1) In the previous releases, the path to the Perl software was hardcoded in all the Perl files in the software package. This has been fixed. |
|
3-10749230211 |
21211511 |
(Maintenance Patch Set 1) In the previous releases, when an account having a subscription that included a product having both monthly and annual cycle forward events configured was trying to transfer its subscription to another account, the subscription transfer was failing. This has been fixed. |
|
3-10766603697 |
21211517 |
(Maintenance Patch Set 1) In the previous releases, cycle charges were applied twice for a product having both annual and monthly cycle forward events configured. This has been fixed. |
|
3-10835117301 |
21224175 |
(Maintenance Patch Set 1) In the previous releases, in the PCM_OP_CUST_MODIFY_BAL_GRP opcode, the PIN_FLD_PROGRAM_NAME input field was mandatory. This has been fixed. The PIN_FLD_PROGRAM_NAME input field is now optional. |
|
3-10563895651 |
21231573 |
(Maintenance Patch Set 1) In the previous releases, for an account with a cycle skipped for billing, the next bill run was not calculating taxes on the cycle forward fees for the subordinate accounts from the previous cycles. This has been fixed. |
|
3-10889929861 |
21245048 |
(Maintenance Patch Set 1) In the previous releases, for payments from BRM, the select status values of MANUAL_ALLOC or ALLOCATION_DEFERRED were not stopping the auto-allocation of payments. This has been fixed. |
|
3-10655923781 |
21255926 |
(Maintenance Patch Set 1) In the previous releases, when a new non-payee child account was created and added to an existing payee account/hierarchy, an existing child account was overwritten in the GROUP_BILLING_MEMBERS_T table. This has been fixed. |
|
3-10538158611 |
21263431 |
(Maintenance Patch Set 1) In the previous releases, searching for deal objects on the secondary schema using In-Memory Database (IMDB) Cache Data Manager was throwing errors. This has been fixed. |
|
3-10837700311 |
21280144 |
(Maintenance Patch Set 1) Customer Center was not displaying the Direct Debit payment method. This has been fixed. |
|
3-10305930231 |
21291935 |
(Maintenance Patch Set 1) Account Migration Manager was running for a long duration and was then rolling back displaying a Java exception. This has been fixed. |
|
3-10750433691 |
21293094 |
(Maintenance Patch Set 1) Conversion Manager was not populating some fields in the AU_ACCOUNT_T and AU_PURCHASED_BUNDLE_T audit tables. This has been fixed. |
|
3-10860918611 |
21312155 |
(Maintenance Patch Set 1) In the previous releases, in the Customer Center Plans tab, the Product Detail and Discount Detail fields were having alignment issues. This has been fixed. |
|
3-10855121661 |
21356302 |
(Maintenance Patch Set 1) In the previous releases, an item type that was configured to pre-create for a specific service type (for example, /service/telco/gsm,) was getting created even for a subclass of the configured service (for example, /service/telco/gsm/telephony). This has been fixed. |
|
3-10979682507 |
21356309 |
(Maintenance Patch Set 1) In the previous releases, in a multischema environment, the create_procedure.plb script was failing to load into the secondary schema. This has been fixed. |
|
3-10427229851 |
21363713 |
(Maintenance Patch Set 1) In the previous releases, an item type that was configured to pre-create for a specific service type, was continuing to create items even after the service was disconnected. This has been fixed. |
|
3-10911712171 |
21376738 |
(Maintenance Patch Set 1) In the previous releases, the loadpricelist utility was restricting the timezone offsets within the range -12 to +12 and the exported file was including an invalid timestamp, and hence the file could not be imported using the loadpricelist utility. This has been fixed. |
|
3-10966666201 |
21391750 |
(Maintenance Patch Set 1) On Windows 8, Payment Tool was crashing when the arrow keys were used to move between controls and when some data was pasted into any text box field. This has been fixed. |
|
3-10733800551 |
21391756 |
(Maintenance Patch Set 1) In the previous releases, when the PCM_OP_ACT_FIND opcode was called in a deployment with IMDB Cache DM, a memory leak was identified within the Connection Manager (CM) module. This has been fixed. |
|
3-10904843431 |
21435526 |
(Maintenance Patch Set 1) In the previous releases, for a product with prorate_first and prorate_last set to a value, the charge was prorated. This has been fixed. |
|
3-10931353761 |
21443073 |
(Maintenance Patch Set 1) In the previous releases, when the PIN_FLD_QUANTITY field was not equal to zero, the bill_item_assign function was returning a segmentation fault. This has been fixed. |
|
3-10935513451 |
21457586 |
(Maintenance Patch Set 1) In the previous releases, when a subscription with an annual cycle fee was transferred from account A to account B and rerating was run on account A from the last billing cycle, the rerating was failing. This has been fixed. |
|
3-10542624811 |
21464320 |
(Maintenance Patch Set 1) In the previous releases, during a service transfer with backdating, the source service was getting closed on the specified date, but the destination service was getting created with the current date, resulting in incorrect prorated balance impacts on the destination account. This has been fixed. |
|
3-11010667451 |
21566190 |
(Maintenance Patch Set 1) In the previous releases, the bill time discounting at the member service level was not triggering for discount sharing. This has been fixed. |
|
3-5896168931 |
14498154 |
(Patch Set 12) In the previous releases, when cleaning up the completed rerate jobs with the pin_rerate utility, the process was returning an error and the purging was not successfully completed. This has been fixed. |
|
3-7755663121 |
17422610 |
(Patch Set 12) In the previous releases, when accounts were migrated using Conversion Manager, the billinfo POID was populated with the type as /billinfo% instead of /billinfo and the ID was incorrect. This has been fixed. |
|
3-7705325011 |
17666544 17736769 |
(Patch Set 12) Conversion Manager, when migrating accounts, bad files were getting generated for purchased products and purchased discounts. This has been fixed. |
|
3-7930330891 |
17766399 |
(Patch Set 12) In the previous releases, Conversion Manager was not:
This has been fixed. |
|
3-8235143371 |
18511981 |
(Patch Set 12) In Conversion Manager, during the migration of accounts with profiles related to extended rating attributes, the reference count value in profile_serv_extrating_t was always set to 1, instead of the actual value. This has been fixed. |
|
3-8855539641 |
18673846 |
(Patch Set 12) In the previous releases, when generating an invoice for an account with sponsored charges rolled up, the events from /config/invoice_events were not considered and hence the invoice event types were not filtered for the sponsored charges. This has been fixed. |
|
3-7596524091 |
19140671 20558999 |
(Patch Set 12) In the previous releases, the Rated Event (RE) Loader was failing with the POID range issue. This has been fixed. |
|
3-9424735361 |
19488357 |
(Patch Set 12) The PCM_OP_SUBSCRIPTION_SET_BUNDLE opcode was resulting in balance group locking, due to an unnecessary rating call for the /event/billing/suppression, /event/billing/bundle, /event/billing/bundle/create, and /event/billing/bundle/modify events for which the RUM information was not properly configured in the /config/rum object. This has been fixed. |
|
3-9513800701 |
19688970 20564179 |
(Patch Set 12) When a terminate request (AAA) in Direct Debit mode was processed for an unbilled account, intermittent timeouts were observed. This has been fixed. |
|
3-9500867391 |
19896391 |
(Patch Set 12) In the previous releases, the duplicate check functionality was not working as expected in Pipeline Manager and was resulting in a unique constraint violation error when trying to persist the data in the database. This has been fixed. |
|
3-8254002681 |
19911447 |
(Patch Set 12) In the previous releases, loading the USC Map DAT module was taking a lot of memory, when .* was used as a regular expression. This has been fixed. |
|
3-9765366348 |
19919863 |
(Patch Set 12) In the previous releases, when the pin_ledger_report utility was run in export mode it was failing. This has been fixed. |
|
3-9984434411 |
20187975 |
(Patch Set 12) In the previous releases, the watermark on a duplicate invoice generated through BIP was constant and there was no provision to configure a different watermark. With this release, you can now configure the watermark using the entries in Infranet.properties file. |
|
3-9753446251 |
20197522 |
(Patch Set 12) In the previous releases, the start time of an active session was being incorrectly modified during reauthorization. This was impacting the incorrect balance buckets. This has been fixed. |
|
3-9495753081 |
20220828 |
(Patch Set 12) When the collections process was trying to add a configuration scenario data to its cache, a message was incorrectly logged as an error into the log file. This has been fixed. |
|
3-9829284161 |
20229069 |
(Patch Set 12) When a monthly cycle forward non-currency resource deal, which was providing resources one month in advance and without proration, was canceled, valid_to of respective sub balance in bal_grp_sub_bals_t was not updated based on the cancellation date. This has been fixed. |
|
3-9951038171 |
20229074 |
(Patch Set 12) The pin_ledger_report utility in detailed mode was not returning the correct report due to incomplete calculations without account number and item number information. This has been fixed. |
|
3-9484526921 |
20236481 20462699 |
(Patch Set 12) The best pricing calculation was incorrectly calculating the alternative price during rerating. This has been fixed. |
|
3-10000421741 |
20262918 |
(Patch Set 12) For an account with multiple balance groups, with an active session in progress, the subsequent authorization or re-authorization flows involving discounting were reporting a credit check failure. This has been fixed. |
|
3-7427949411 |
20301369 |
(Patch Set 12) In the previous releases, due to the lack of synchronization of threads for logging, for higher log levels the threads were waiting longer times affecting performance. This has been fixed. |
|
3-10031473161 |
20310218 |
(Patch Set 12) When a product was canceled, the applicable credits were not applied. This has been fixed. |
|
3-10023359921 |
20318012 |
(Patch Set 12) With Number Administration Center, the device.useglobalsearch = true configuration parameter was not actually resulting in a global search. This has been fixed. |
|
3-9885466281 |
20331918 |
(Patch Set 12) With Collections Manager, the PCM_OP_COLLECTIONS_TAKE_ACTION opcode was failing when run through the PCM_OP_ACT_SCHEDULE opcode without the required DUE_T information. This has been fixed. |
|
3-10003034921 |
20331920 |
(Patch Set 12) For an account with tax exemptions, the tax calculation flow was incorrectly dropping the data related to exemptions and subsequently causing the account to be taxed. This has been fixed. |
|
3-9704723441 |
20345113 |
(Patch Set 12) Whenever a rollover product end date coincides with the billing date for the account, the rollover was not happening properly. This has been fixed. |
|
3-10117682977 |
20371184 |
(Patch Set 12) A discount configured with scale of zero (0) was causing the discount to be applied twice. This has been fixed. |
|
3-9712476101 |
20375902 |
(Patch Set 12) In Customer Center, an error message was displayed when viewing a plan detail containing an offering that was deleted from the system. This has been fixed. |
|
3-10010476311 |
20375906 |
(Patch Set 12) While rating an event, the rating cache was returning invalid information resulting in incorrect balance impacts. This has been fixed. |
|
3-10019459157 |
20386251 |
(Patch Set 12) When billing day of the month was updated with the offset of more than two cycles, the valid_to field was incorrectly populated based on next_t instead of future_t. This has been fixed. |
|
3-9985167281 |
20393441 |
(Patch Set 12) When an account closure is scheduled using Customer Center for a future date creating a scheduler object, it was observed that the last_status and laststat_cmnt fields were updated even before the actual status change. This has been fixed. |
|
3-10037858781 |
20401985 |
(Patch Set 12) When a product with the Charge for the entire cycle proration setting was purchased for an account and canceled before the cycle ended, the entire charges for the product was incorrectly refunded. This has been fixed. |
|
3-10144245101 |
20416284 |
(Patch Set 12) When an account was created with a long cycle, the sub-balances with non-currency resources were having an incorrect valid_to value. This has been fixed. |
|
3-9953216281 |
20422775 |
(Patch Set 12) While discounting, rounding was done incorrectly if the precision was more than 15 digits after the decimal point. This has been fixed. |
|
3-10176053261 |
20432187 |
(Patch Set 12) With Automated Monitor Setup (AMS) configuration for Balance Monitoring, for every rerating request, an extra rerating job was created causing an accumulation of rerating jobs. This has been fixed. |
|
3-10187518331 |
20436888 |
(Patch Set 12) When calling PCM_OP_SUBSCRIPTION_SET_PRODINFO to set cycle_end_t to 0, the values for charged_from_t were incorrectly aligning with charged_to_t, and cycle_fee_start_t was incorrectly aligning with cycle_fee_end_t. This has been fixed. |
|
3-10105991631 |
20450292 |
(Patch Set 12) During trial billing, for a purchased product starting from billing DOM, charge_from was incorrectly calculated. This has been fixed. |
|
3-10128809191 |
20452428 |
(Patch Set 12) In a multidatabase system, the offer profile tables were not replicated. This has been fixed. |
|
3-10117542611 |
20462695 |
(Patch Set 12) While purchasing a deal, the purchased product's purchase or cycle or usage end date was set one day prior to the expected date. This has been fixed. |
|
3-10180364211 |
20471105 |
(Patch Set 12) In a multischema environment, the payment reversals could be done multiple times from each schema, because the lookup for an already executed payment reversal was not processed globally across all the schema, for a particular payment. This has been fixed. |
|
3-10051409151 |
20479692 |
(Patch Set 12) The plan transition was failing for member services when it required a status update to those member services. This has been fixed. |
|
3-8959105771 |
20527047 |
(Patch Set 12) When Login Exclusion was configured, the system was still performing a login search first instead of just the aliases search for that login. This has been fixed. |
|
3-8892430511 |
20534430 |
(Patch Set 12) The PCM_OP_SUBSCRIPTION_READ_ACCT_PRODUCTS opcode was generating core due to an uninitialized cookie after each iteration. This has been fixed. |
|
3-10000209801 |
20583621 |
(Patch Set 12) The PCM_OP_SUBSCRIPTION_CANCEL_DISCOUNT opcode was not saving the value passed in for PIN_FLD_DESCR into the generated cancel event. This has been fixed. |
|
3-10353697641 |
20645464 |
(Patch Set 12) During the subscription transfer operation, a rerate job was created with an incorrect start date. This has been fixed. |
|
3-10334546841 |
20654250 |
(Patch Set 12) The rerating operation was failing when trying to back out monitor update events belonging to a previous bill cycle. This has been fixed. |
|
3-10301779691 |
20677976 |
(Patch Set 12) When a subscriber who had entered into a promise-to-pay agreement, even after fulfilling the agreement by paying an amount more than actually promised, the subscriber was not coming out of the promise-to-pay agreement. This has been fixed. |
|
3-10375299561 |
20720288 |
(Patch Set 12) With a billing DOM of first of a month, ACTG_NEXT_T set to 1 and advance_bill_cycle also set to 1, for the month of March the value of ACTG_FUTURE_T was incorrectly set. This has been fixed. |
|
3-10286852131 |
20733490 |
(Patch Set 12) The PCM_OP_BULK_DELETE_OBJ opcode was failing to delete when called from within a transaction on an object type without specifying any objects to delete. This has been fixed. |
|
3-10249511381 |
20736200 20802638 20816269 |
(Patch Set 12) The performance of pin_ledger_report was degraded due to the introduction of the get_gl_bill_t stored function. This has been fixed. |
|
3-9529076071 |
20785075 |
(Patch Set 12) MTA's search feature was not working. This has been fixed. |
|
3-10179553901 |
20785078 |
(Patch Set 12) In Suspense Manager, while reprocessing a suspended call details record (CDR), there was an error when querying for the event data record (EDR) version information and when parsing the recycled CDR for rating. This has been fixed. |
|
3-10450819691 |
20785084 |
(Patch Set 12) The charged amount values against individual RUMs were incorrect in the Charge Packets for fixed charge calls when such calls overlapped multiple time zones. This has been fixed. |
|
3-10341449171 |
20805907 |
(Patch Set 12) During the step search, when an error condition was met, step_end was not explicitly called resulting in further errors. This has been fixed. |
|
3-10434604941 |
20827663 |
(Patch Set 12) In Collections Manager, the Next Payment Due field name was changed to Payment Due because it was not correctly representing the field. |
|
3-10438654581 |
20832904 |
(Patch Set 12) In Collections Manager, the promise-to-pay actions agent information was not updated. This has been fixed. |
|
3-9771430971 |
20839673 |
(Patch Set 12) When the pin_inv_accts utility was run with PIN_BILL_FLG_SKIPPED_BILL, the utility was not adding information on failed bill objects into failed accounts' audit objects. This left incomplete failed accounts audit objects. This has been fixed. |
|
3-10018355111 |
20843636 |
(Patch Set 12) The data manager for IMDB Cache (TimesTen) was generating core. This has been fixed. |
|
3-10127021691 |
20854256 |
(Patch Set 12) Row lock contentions were observed during transactions opened when pin_deferred_act was run. This has been fixed. |
|
3-5566352891 |
13996314 |
(Patch Set 11) In the previous releases, Pricing Center was not displaying the correct transition plans under the allowable plan list. This has been fixed. |
|
3-5695750521 |
14091039 |
(Patch Set 11) In the previous releases, when you restarted Pricing Center after creating a plan with options having a subscription group and deals, the subscription group service and deals associated under that plan were not displayed. This has been fixed. |
|
3-6507644791 |
16696707 |
(Patch Set 11) In Revenue Assurance Center, for the revenue assurance data, the invoice total was always displayed as 0 (zero) in the default setup. This has been fixed. The invoice total is now removed from the invoice section of Revenue Assurance Center. |
|
3-7483002591 |
17071366 |
(Patch Set 11) In the previous releases, a customer service representative (CSR) with read-only access could update the validity of resources using Customer Center. This has been fixed. |
|
3-6867499371 |
17528910 |
(Patch Set 11) In Pricing Center, if a copy (P1) of a product (P) already existed, creating a copy P2 from P resulted in overwriting P1. This has been fixed. |
|
3-6508537831 |
18589292 |
(Patch Set 11) In Pricing Center, the Transition tab for a deal was not displaying all the possible transitions because the transitions for the deals were not retrieved properly from the database. This has been fixed. |
|
3-9232635917 |
19384069 |
(Patch Set 11) In Customer Center, accounts and services were displayed multiple times in the list for the Account Status link in the Summary tab. This has been fixed. |
|
3-9447740581 |
19386804 |
(Patch Set 11) In the previous releases, even though Vertex Quantum Manager was only for Sales Tax Q (STQ), it was throwing errors if Communications Tax Q (CTQ) was not installed and configured. This has been fixed. |
|
3-9225436091 |
19408414 |
(Patch Set 11) In the previous releases, when generating an invoice with debug mode on, a core dump was generated when searching items with the Group By clause. This has been fixed. |
|
3-9506658234 |
19561377 |
(Patch Set 11) In the previous releases, the Oracle Data Manager (DM) was dumping core when reading NULL-terminated Character Large Object (CLOB) data.This has been fixed. |
|
3-9578603551 |
19595644 |
(Patch Set 11) In the previous releases, EAI Manager (dm_eai) was throwing a getaddrinfo failed error while publishing messages. This has been fixed. |
|
3-9479605561 |
19595654 |
(Patch Set 11) In the previous releases, when purchasing a deal or modifying a customer, when purchasing a discount and an invalid discount object was passed to the operation, core dump was generated during service creation. This has been fixed. |
|
3-8807271531 |
19603741 |
(Patch Set 11) In the previous releases, when a charging group was created with an existing account as owner, having multiple services with some in open and some in closed status, the created sharing group was showing closed status. This has been fixed. |
|
3-9372408131 |
19603744 |
(Patch Set 11) In the previous releases, the Event Details window of Event Browser was not displaying the correct time information based on the timezone. This has been fixed. |
|
3-9597886941 |
19623442 |
(Patch Set 11) In the previous releases, Customer Center was allowing CSRs to do adjustments greater than the event adjustment limit set in Permissioning Center. This has been fixed. |
|
3-9561429431 |
19627250 |
(Patch Set 11) In the previous releases, for a failed payment, Customer Center was displaying the corresponding event with an incorrect payment type. This has been fixed. |
|
3-9384144601 |
19628977 |
(Patch Set 11) In the previous releases, Pipeline Manager was throwing a compilation error during the promotion of data types used in the parameter list for any function called from an iScript. This has been fixed. |
|
3-9523337291 |
19637922 |
(Patch Set 11) In the previous releases, the threshold breach calculation was incorrectly performed for in-session notifications. This has been fixed. |
|
3-9345733151 |
19644047 |
(Patch Set 11) In the previous releases, when a product was purchased with a large (a day or more) offset for the start time, because of which the product effective date was earlier than the product created date, the purchase and cycle fees were not applied. This has been fixed. |
|
3-6793501601 |
19644052 19649816 |
(Patch Set 11) In the previous releases, there was a restriction that pin_event_extract and pin_rel could not be run in parallel. This has been fixed. Changes were made in the event selection criteria in pin_event_extract so that events that are not completely processed by Rated Event Loader (RE Loader) cannot be extracted. This ensures that the integrity of the events to be rerated is not disturbed while extracting events using pin_event_extract. |
|
3-7941628591 |
19651427 |
(Patch Set 11) In the previous releases, when writing off an account, the tax part of the amount being written off was incorrectly calculated. This has been fixed. |
|
3-9567425201 |
19651433 |
(Patch Set 11) In the previous releases, after migrating an account using Conversion Manager, the values of offering_obj fields in the AU_GROUP_SHARING_DISCOUNTS_T table were not correctly populated. This has been fixed. |
|
3-9531426771 |
19655833 |
(Patch Set 11) In the previous releases, with billing delay and proration settings configured to calculate charges based on usage for both purchase and cancel operations, when a cycle forward product was canceled, after inactivating and reactivating the product, the prorated cycle forward charges due to cancellation were not refunded. This has been fixed. |
|
3-9600184221 |
19669597 |
(Patch Set 11) In the previous releases, with propagate_discount set to 1 in the Connection Manager's (CM's) pin.conf file to enable the discount sharing startup from the beginning of the next billing cycle to the time of creating the discount sharing group or adding a member, when a member was added, BRM was throwing an error during the reevaluation of discounts in the discount sharing group. This has been fixed. |
|
3-9649089721 |
19699063 |
(Patch Set 11) In the previous releases, the discount was calculated for a time period that was outside of the validity period. This has been fixed. |
|
3-9533882771 |
19699070 |
(Patch Set 11) In the previous releases, when an account had multiple bill units, the Collection Manager's pin_collections_process utility was entering into a deadlock, and Collection Manager was hanging.This has been fixed. |
|
3-9653218061 |
19704712 |
(Patch Set 11) In the previous releases, when 30 days proration was enabled, sequential discounting was applying a discount greater than 100%. This has been fixed. |
|
3-9589343971 |
19712308 |
(Patch Set 11) In the previous releases, when an account was migrated using Conversion Manager, the item_t.ar_billinfo_obj_id0 was incorrectly populated with the service-level bill unit instead of the account-level bill unit. This has been fixed. |
|
3-9591167041 |
19734105 |
(Patch Set 11) In the previous releases, moving a subordinate account from one account to another resulted in a validation failure. This has been fixed. |
|
3-9627117591 |
19780375 |
(Patch Set 11) In the previous releases, the PCM_OP_SUBSCRIPTION_READ_ACCT_PRODUCTS opcode was dumping core. This has been fixed. |
|
3-9673843028 |
19787832 |
(Patch Set 11) In the previous releases, after a bill unit name is updated, refreshing the Balance tab in Customer Center was throwing the Error Communicating with BRM error. This has been fixed. |
|
3-9613131901 |
19801369 |
(Patch Set 11) In the previous releases, the loadpricelist utility was failing while loading pricing objects when a large result set was returned from a /config/glid search. This has been fixed. |
|
3-9539885621 |
19805696 |
(Patch Set 11) In the previous releases, when the db2irules.pl script was run with the -u parameter, the generated output file was not matching the ST_CIBER_VAL.xml file that was loaded in the database. Additionally, when the script was run with the -d parameter, CIBER validation rules were not deleted from the database. This has been fixed. |
|
3-9658464901 |
19822362 |
(Patch Set 11) In Collections Manager, the collection rescheduling was failing for the current or any future date. This has been fixed. |
|
3-9379625544 |
19831218 |
(Patch Set 11) In the previous releases, if all members and the parent of the subscription group are members of a discount sharing group, the recurring charges were not reflected in balance monitoring for the newly added member service into the subscription group. This has been fixed. |
|
3-9692801681 |
19851513 |
(Patch Set 11) In Collections Center, the Number of Bill Units field data was not correctly aligned. Additionally, the Assigned Bill Units and Agent fields were blank. This has been fixed. |
|
3-9768695701 |
19866783 |
(Patch Set 11) In Roaming Manager, the CIBER records were rejected with a validation error for the SPECIAL_FEATURES_USED field. This has been fixed. |
|
3-9624210961 |
19875341 |
(Patch Set 11) In Collections Manager, when an account entered collections, the collections due date field was being omitted by the PCM_OP_COLLECTIONS_POL_CALC_DUE_DATE policy opcode. This has been fixed. |
|
3-9658332011 |
19881465 |
(Patch Set 11) In Roaming Manager, the CIBER records were rejected with a validation error for the ORIG_BATCH_SEQ_NO field. This has been fixed. |
|
3-9709832411 |
19911438 |
(Patch Set 11) In Conversion Manager, during the migration of non-currency balances, loading the XML file was very slow, irrespective of the size of the file. Additionally, the following occurred:
This has been fixed. |
|
3-9698602741 |
19911455 |
(Patch Set 11) In the previous releases, when a subordinate account was created with the account creation time greater than ACTG_NEXT_T of the parent, the ACTG_NEXT_T of the subordinate was aligning to ACTG_FUTURE_T, instead of to ACTG_NEXT_T, of the parent bill unit. This has been fixed. |
|
3-9455198081 |
19931091 |
(Patch Set 11) In Conversion Manager, for account-level products, purchased_product_t.plan_obj_id0 was incorrectly populated. This has been fixed. |
|
3-9800104001 |
19948636 |
(Patch Set 11) In Collections Manager, when a payment was made to a written-off account, the tax events were not created correctly. This has been fixed. |
|
3-9619119681 |
19957521 |
(Patch Set 11) In the previous releases, in the rerating workflow, item adjustments were created by RE Loader not just for billed events but also for the unbilled events, which was incorrect. This has been fixed. |
|
3-9685906951 |
20001526 |
(Patch Set 11) In the previous releases, BRM was incorrectly allowing the application of recurring cycle forward fees for a canceled product period. This has been fixed. |
|
3-9740493385 |
20017115 |
(Patch Set 11) In the previous releases, when a charge was applied for a future cycle, the scale was incorrectly calculated as 0. This has been fixed. |
|
3-9382785971 |
20017119 |
(Patch Set 11) With Conversion Manager, during migration, if partial rollover data (for example, not containing ValidFromDetails and ValidToDetails) was provided in the input XML file, the corresponding sub-balance creation was incorrect. Additionally, while importing balances with infranet.cmt.billingdelay set to true, the due amount was sometimes overwritten. This has been fixed. |
|
3-9761054791 |
20032761 |
(Patch Set 11) In the previous releases, when an annual cycle forward product was purchased with backdating, the cycle end time was incorrectly calculated and was resulting in incorrect charging of the account. This has been fixed. |
|
3-9811088441 |
20060558 |
(Patch Set 11) In a multischema environment, when a payment was posted to an account in a secondary schema with Payment Tool, by a user other than an administrator user, the payment was going through, but the payment event was containing incorrect user information. This has been fixed. |
|
3-9309436241 |
20068404 |
(Patch Set 11) In the previous releases, when a deal was purchased with an extended rating attribute (ERA), the effective time of the ERA profile was not properly set and was not matching the purchased product for which the effective time was correctly set. This has been fixed. |
|
3-9763470341 |
20076840 |
(Patch Set 11) In the previous releases, when corrective billing was run, the PIN_FLD_NAME field was containing invalid data. So, identifying a corrective bill for the due date calculation using PIN_FLD_NAME was not possible. This has been fixed. |
|
3-9887999451 |
20081079 |
(Patch Set 11) In the previous releases, if the purchase of a tailor-made plan was beyond the current product cycle, it was incorrectly refunding and reapplying the base product cycle fees. This has been fixed. |
|
3-9889133741 |
20102108 |
(Patch Set 11) In the previous releases, for a monthly recurring charges product with multiple rate tiers for rate change purchased with backdating in such a way that the purchase effective date was prior to the rate change date and charges were applied for the rate change period, the backdated cancellation with effective date prior to the rate change was incorrectly calculating the refund. This has been fixed. |
|
3-9901763406 |
20102113 |
(Patch Set 11) In the previous releases, the Customer Center AR Adjustment dialog box was not closing when the OK button was clicked after entering the required information for adjustment, even though the adjustment went through successfully. This has been fixed. |
|
3-9828162251 |
20102120 |
(Patch Set 11) In the previous releases, the PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL policy opcode was not being called when a cycle arrears product was canceled, which was restricting any possible customizations to arrive at the cycle fees interval during cancellation. This has been fixed. |
|
3-9685949901 |
20114129 |
(Patch Set 11) In the previous releases, the future-dated service disconnections were generating incorrect refunds. This has been fixed. |
|
3-9755304631 |
20136958 |
(Patch Set 11) In the previous releases, corrective billing was not calling the PCM_OP_BILL_POL_SPEC_BILLNO policy opcode in its workflow to enable the bill-number-related format customizations. This has been fixed. |
|
3-8534671511 |
20166721 |
(Patch Set 11) In the previous releases, the event browser in Customer Center was not displaying the event time information based on the timezone. This has been fixed. |
|
3-9926769431 |
20181649 |
(Patch Set 11) In the previous releases, when a product with a rate plan selector was used, the PIN_FLD_SCOPE information (whether cycle forward or cycle arrears) was missing in the input of the PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL policy opcode. This has been fixed. |
|
3-9980011471 |
20208772 |
(Patch Set 11) In Customer Center, the phone number was not correctly displayed on the Balance tab. This has been fixed. |
|
3-9874595211 |
20241294 |
(Patch Set 11) In the previous releases, Pricing Center was not opening due to memory-full issue due to large G/L ID objects. This has been fixed. |
|
3-9464578441 |
20025156 20032766 |
(Patch Set 11) In the previous releases, in a multischema environment, duplicate POIDs were getting generated while creating new POIDs through Pipeline Manager. This has been fixed. |
|
3-7153450471 |
16965406 19352822 |
(Patch Set 10) In the previous releases, Payment Tool was not honoring access with the permissions defined in /service/admin_client. The only way to access was to define permissions in Permissioning Center. This has been fixed. |
|
3-7730960101 |
17834397 17928712 19368177 |
(Patch Set 10) In the previous releases, the pin_trial_bill_accts utility was taking a very long time to process accounts for trial billing. This was observed for large account hierarchies. This has been fixed. |
|
3-7752886781 |
17970904 |
(Patch Set 10) In the previous releases, for an account when a proration-enabled product was purchased or canceled on cycle boundaries, the proration was getting into effect, but it was not necessary to do the proration when the dates were aligned to the cycle dates. This has been fixed. |
|
3-8546674701 |
18389662 19143314 |
(Patch Set 10) In the previous releases, in Customer Center, when modifying products that had a relative offset period set to an absolute date, the date was defaulting to 31-Dec-1969 rather than the absolute date corresponding to the relative offset that was defined earlier. This has been fixed. |
|
3-8657352981 |
18425860 |
(Patch Set 10) In the previous releases, real-time pipelines for rerating and discounting were not supporting the EDRTrace feature. This has been fixed. |
|
3-8668009771 |
18433221 |
(Patch Set 10) In the previous releases, in Customer Center, the units in the Products - Product Details tab were disappearing when choosing between Relative and Date options. This has been fixed. |
|
3-8389236441 |
18475426 |
(Patch Set 10) From BRM 7.5 Patch Set 7, the link edit between libportal.so and Oracle 11g client libclntsh.so was failing while building custom applications. This has been fixed. |
|
3-8781616941 |
18508380 |
(Patch Set 10) In the previous releases, the pin_mass_refund utility was not working for bill units with open item accounting. This has been fixed. |
|
3-8380836155 |
18511978 |
(Patch Set 10) In the previous releases, when Connection Manager Master Process (CMMP) was used as a load balancer, switching transaction state, even for non-transactional opcodes, was then resulting in an ERR_TRANS_ALREADY_OPEN error. This has been fixed. |
|
3-8331979191 |
18519249 |
(Patch Set 10) In the previous releases, when using Conversion Manager, the actual values provided for deal_obj_db and plan_obj_db were disregarded and these parameters were always incorrectly set to 1. This has been fixed. |
|
3-8834248071 |
18546684 19207928 |
(Patch Set 10) In the previous releases, the subscription-level balance monitor was correctly updated with subscription-level adjustments when the subscription service POID was passed in the input flist of the PCM_OP_AR_ACCOUNT_ADJUSTMENT opcode. This information was not correctly documented in the opcode specification. This has been fixed. |
|
3-8835796891 |
18546903 |
(Patch Set 10) In the previous releases, the Customer Center SDK method was setting the date incorrectly in the PAIDateField class. This has been fixed. |
|
3-8826336531 |
18614306 |
(Patch Set 10) In the previous releases, in Event browser, the Connection Manager (CM) connection was not released even after closing the window. This has been fixed. |
|
3-8902318711 |
18665392 |
(Patch Set 10) In the previous releases, multiple warning messages were displayed when launching Customer Center from a web browser. This has been fixed. |
|
3-8674415121 |
18699624 |
(Patch Set 10) In the previous releases, the timestamp fields of the uniqueness table were populated based on the system date. This has been fixed. The timestamp value is now set to the value stored in the database. |
|
3-7560575581 |
18739065 |
(Patch Set 10) In the previous releases, the BRM general ledger reports considered revenue to be billed based on the end time of the corresponding bill period. For example, if the bill period is Jan 1 through Feb 1, but the actual bill run is on Feb 3, the revenue is considered billed on Feb 1. With this release, you can now set the new UseActualBilledTimeForGLReport billing business parameter to consider the revenue billed to be on the actual bill run date. |
|
3-8640746111 |
18752383 |
(Patch Set 10) In the previous releases, when using Conversion Manager, if pin_cmt_deploy was run multiple times for same stage ID, it was resulting in inconsistent data in the au_profile_t and au_service_t audit tables. This has been fixed. |
|
3-7617935901 |
18791573 |
(Patch Set 10) In the previous releases, when the discount was applied to the same non-currency resource as the charge, the base amount for a sequential discount was incorrectly calculated. This has been fixed. |
|
3-8735434341 |
18826015 19569009 |
(Patch Set 10) In the previous releases, when submitting duplicate payments for the same account in a single batch of Payment Tool, both payments were being applied on the account without any check for overallocation to items. This was resulting in a negative account balance. With this release, a new business parameter, ItemOverAllocation, is added to determine whether any item can be allocated beyond its due. By default, the value of the business parameter is enabled. |
|
3-8926475921 |
18903914 |
(Patch Set 10) In the previous releases, when publishing events from eai_js, the format of the timestamps sent out was incorrect. This has been fixed. |
|
3-8777861598 |
18948667 |
(Patch Set 10) In the previous releases, during migration with Conversion Manager, while trying to update bal_grp_t as first day of previous month, the effective date in bal_grp_t was incorrectly set to created_t. This has been fixed. The value is now set to effective_t. |
|
3-8951132071 |
18957536 |
(Patch Set 10) In the previous releases, Conversion Manager was hanging with java.lang.NullPointerException in the Java stack trace. This has been fixed. |
|
3-9074661021 |
19021970 19341890 19342928 |
(Patch Set 10) In the previous releases, BRM was not supporting querying the latest real-time-balance information from Elastic Charging Engine (ECE). This has been fixed. |
|
3-8956489561 |
19031334 |
(Patch Set 10) In the previous releases, when timestamp rounding is enabled for all the non-currency resource grants due to the cycle forward event, bal_grp_sub_bals_t.valid_from in the granted sub-balance was rounded to midnight. Controlling this rounding for purchase grants was not possible. With this release, a new business parameter, TimestampRoundingForPurchaseGrant, is added for rating. This business parameter works along with the timestamp_rounding parameter in the pin.conf file. When the business parameter is enabled and the timestamp_rounding parameter in the pin.conf file is also enabled, the purchase grant will be rounded to midnight. By default, the value of the business parameter is enabled (set to 1). |
|
3-9000971543 |
19052369 |
(Patch Set 10) In the previous releases, the client patch did not specify a build number. This has been fixed. |
|
3-9107610731 |
19055312 |
(Patch Set 10) In the previous releases, when multiple transactions were active, FCT_ApplyBalance was not properly renaming the notification files to have .xml extension. It was picking up only the latest stream for verifying and renaming only the corresponding notification file. This has been fixed. |
|
3-9084752364 |
19062931 |
(Patch Set 10) In the previous releases, when in maintenance mode, updating the cycle end date was not working. It was always defaulting to the next cycle end date. This has been fixed. |
|
3-9097643431 |
19067183 |
(Patch Set 10) In the previous releases, it was not possible to configure an RSC_Map using a rateplan code, even though using a rateplan code was more intuitive than using a rateplan identifier. With this release, you can now set the optional Boolean UserRatePlanCode registry parameter to use rateplan code. The default is false. To use rateplan code, set the parameter to true. |
|
3-9065871071 |
19078159 19259074 |
(Patch Set 10) In the previous releases, the pin_rel utility was not updating the /journal objects with events corresponding to zero event balances. With this release, you can now set the ZeroEventBalances business parameter to update the /journal objects with events corresponding to zero event balances. By default, the value of the business parameter is 0, which is to not include the zero event journal balances. To include zero event journal balances, set the business parameter to 1. |
|
3-8900925751 |
19128368 |
(Patch Set 10) In the previous releases, while migrating non-currency resources using Conversion Manager, the realtime_cntr and rec_id fields of the existing sub-balances were not properly updated. This has been fixed. |
|
3-9277903901 |
19158265 19329665 |
(Patch Set 10) In the previous releases, the PIN_FLD_GEOCODE and PIN_FLD_TAXPKG_TYPE fields were missing from PCM_OP_BAL_GET_ACCT_BILLINFO JCA XSD file, due to which the information in these fields were not passed to the opcode for proper opcode functionality. This has been fixed. |
|
3-9267909481 |
19164918 |
(Patch Set 10) In the previous releases, in multischema account migration using Conversion Manager, when other accounts were created using standard account creation opcodes, the POID_ID0 field of the /uniqueness object was not mangled, resulting in an unique constraint violation error. This has been fixed. |
|
3-9044443971 |
19170129 |
(Patch Set 10) In the previous releases, when a service for an account having purchased discounts was inactivated first and later the service was reactivated and the discount was repurchased, the discounts were not getting applied. This has been fixed. |
|
3-8841891961 |
19172383 |
(Patch Set 10) In the previous releases, when purchasing a one-time deal to an existing service, the Customer Center Plans tab was showing the correct product name, but the deal name was incorrect. This has been fixed. |
|
3-8894533131 |
19194696 |
(Patch Set 10) In the previous releases, while calculating payment incentives, the TOTAL_DUE (that included the previous dues) was incorrectly mapped instead of just the current month due. Due to this, the payment incentive calculation was incorrect. This has been fixed. |
|
3-8963911221 |
19194698 |
(Patch Set 10) In the previous releases, during migration using Conversion Manager, the group object ID values were not properly populated, and this was causing operations like PCM_OP_BILL_DEBIT to fail, which in turn was accessing the group sharing objects. This has been fixed. |
|
3-9311090061 |
19202345 |
(Patch Set 10) In the previous releases, the pin_discount_cleanup utility was crashing. This has been fixed. |
|
3-9294585111 |
19217389 |
(Patch Set 10) In the previous releases, when more than one discount was present with sequential discounting enabled, the discount calculation was incorrect and impacted the balances. This has been fixed. |
|
3-9347295804 |
19219139 |
(Patch Set 10) In the previous releases, when trying to start Customer Center with Java Webstart, the JAR resources in JNLP file are not signed by same certificate error message appeared. This has been fixed. |
|
3-9527135271 |
19227016 |
(Patch Set 10) In the previous releases, every time the BufferLimit or StoreLimit parameters was updated, the index was getting recreated for FCT_DuplicateCheck in Pipeline Manager. This was taking a long time to complete and there was no control to make it optional. This has been fixed. |
|
3-9121968561 |
19227161 |
(Patch Set 10) In the previous releases, when a group of accounts was migrated in bulk using Conversion Manager, the timestamps for created_t, effective_t, and mod_t were inconsistent in the UNIQUENESS_T and AU_UNIQUENESS_T tables. This has been fixed. |
|
3-9028194391 |
19236913 |
(Patch Set 10) In the previous releases, when using Conversion Manager with multithreading, an ArrayIndexOutOfBoundsException exception was thrown. This has been fixed. |
|
3-9028022821 |
19246390 |
(Patch Set 10) In the previous releases, when data was migrated from older releases like Portal 7.2.1 to BRM 7.5, FCT_DuplicateCheck was failing due to the way the search key was derived. Prior to BRM 7.5, the search key was directly inserted into the database, whereas in BRM 7.5 a hashed value was being inserted. So on a migrated instance, FCT_DuplicateCheck failed because it was expecting a hashed key rather than the actual key. This has been fixed. |
|
3-9219324731 |
19246395 |
(Patch Set 10) In the previous releases, when unit was DAYS, daylight saving time (DST) was not considered for calculating the relative time, which resulted in incorrect values for the product cycle timestamps. This has been fixed. |
|
3-9309315781 |
19246403 |
(Patch Set 10) In the previous releases, during the delay period, a backdated cancellation was pushing the discount refund to the next bill cycle. This has been fixed. |
|
3-9348642551 |
19254938 |
(Patch Set 10) In the previous releases, the extended rating attribute (ERA) Extension APIs used the local time rather than the UTC time. This was resulting in inconsistent behavior. This has been fixed. |
|
3-9302735771 |
19276557 |
(Patch Set 10) In the previous releases, during the inactivation of a subscription, an incorrect end_t was calculated and was being used. This has been fixed. |
|
3-9309315781 |
19276560 |
(Patch Set 10) In the previous releases, when two discounts were configured with sequential discounting enabled, canceling one discount was causing the other discount to be applied during the next cycle instead of during the current cycle. This has been fixed. |
|
3-9320949131 |
19284834 |
(Patch Set 10) In the previous releases, when the product end date was changed within the cycle, the cycle forward charges were getting unnecessarily applied even though the charges were already applied. This has been fixed. |
|
3-9375886241 |
19295129 |
(Patch Set 10) In the previous releases, open billing was failing because of locking of balance groups. This has been fixed. |
|
2-5816784 |
19304275 |
(Patch Set 10) In the previous releases, during plan transition, there was an issue with credit limit exceeding for prepaid scenarios. This has been fixed. |
|
3-9389962401 |
19305846 |
(Patch Set 10) In the previous releases, a tailor-made product that had a future cycle_start in the current cycle was getting skipped. This has been fixed. |
|
3-9248293521 |
19323346 |
(Patch Set 10) In the previous releases, in Customer Center, it was not possible to transfer balance if it had a negative decimal amount. This has been fixed. |
|
3-9198088431 |
19323348 |
(Patch Set 10) In the previous releases, during plan transition, if there were any common services, the service orders were created only for deactivation and the rest of the activities through the provisioning flow were not considered. This has been fixed. |
|
3-9362428291 |
19334711 |
(Patch Set 10) In the previous releases, if you were not using tailor-made products, the locks on the derived rateplans were not getting released. This was increasing the number of locks in the system, eventually shutting down the pipeline process. With this release, the locks on the rateplans are released properly. Additionally, you can set the TailormadeProductsSearch business parameter to disabled to skip locking the rateplans. |
|
3-9373391501 |
19336565 |
(Patch Set 10) During the BRM 7.5 Patch Set 8 installation, pin_setup was failing. This was due to the installation scripts pointing to Perl 5.8.0 instead of newly packaged Perl 5.18.2. This has been fixed. |
|
3-8855926111 |
19344824 |
(Patch Set 10) In the previous releases, in Pricing Center, whenever a rate description was modified for a product, a new rate object was created, without deleting the old rate object. This has been fixed. |
|
3-9138903801 |
19344829 |
(Patch Set 10) In the previous releases, in Pipeline Manager, even after reloading APN Map by passing a semaphore, it was still referring to old data. This has been fixed. |
|
3-7051155361 |
19408407 |
(Patch Set 10) In the previous releases, when a zone map was updated while the zoning PCM_OP_ZONEMAP_POL_GET_LINEAGE policy opcode was being run, sometimes it went into an infinite loop, and the process was hanging. This has been fixed. |
|
3-9416116906 |
19408411 |
(Patch Set 10) In the previous releases, in some scenarios the total tax from the written-off balance impacts was not matching the total tax of the actual item totals. This has been fixed. |
|
3-9469185811 |
19445384 |
(Patch Set 10) In the previous releases, when the input data for collections did not contain the POID values, the process was dumping core. This has been fixed. |
|
3-8628294001 |
19445804 |
(Patch Set 10) In the previous releases, the rating pipeline stops and was erroring out with ERR_THREAD_EXCEPTION and invalid state change errors due to a local variable being accessed simultaneously across two different transactions in the FCT_EventOrder module. This has been fixed. |
|
3-9352596531 |
19466104 |
(Patch Set 10) In the previous releases, in a Services Framework enabled environment, when an account with a discount was first created and later the service was activated, the end date of the discount was getting set during the activation. This has been fixed. |
|
3-9508509961 |
19487669 |
(Patch Set 10) In the previous releases, when processing a CIBER record type 22 for Mobile Terminating Call with an Initial Cell Site field value 11 spaces (blank), the CIBER InProcessing pipeline rejected the call record with an error. This has been fixed. |
|
3-9436828911 |
19508032 |
(Patch Set 10) In the previous releases, the PCM_OP_BILL_ITEM_REFUND opcode was throwing a TRANS_ALREADY_OPEN error. This has been fixed. |
|
3-8612866981 |
19523820 |
(Patch Set 10) In the previous releases, when a system product was configured to give incentives to customers who paid their bills before the due date, the incentives were not applied to customers who came out of collections making an overpayment. This has been fixed. |
|
3-9383592677 |
19533783 |
(Patch Set 10) In the previous releases, when a product was purchased with a future cycle start date, the existing discounts, if any, were not applied properly. This has been fixed. |
|
3-7791124141 |
19561370 |
(Patch Set 10) In the previous releases, when fetching data from database in double format, rounding issues were identified in the Rogue Wave library. This has been fixed. |
|
3-9445909211 |
19561375 |
(Patch Set 10) In the previous releases, pin_dd_schema was not working due to the updated version of Perl. This has been fixed. |
|
3-9294386997 |
19569312 |
(Patch Set 10) In the previous releases, Purify tests at customer sites indicated that the subscription module read memory that was earlier freed. This has been fixed. |
|
3-9513444631 |
19587204 |
(Patch Set 10) In the previous releases, when updating a discount's purchase, cycle, and usage dates information, the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode was throwing an error. This has been fixed. |
|
NA |
19616033 |
(Patch Set 10) In the previous releases, the PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode was not returning tax-only disputes information to be displayed in Customer Center. This has been fixed. |
|
3-6967792101 |
16723615 |
(Patch Set 9) In the previous releases, the pin_ledger_report -export command was ignoring the transaction_grouping parameter setting in the pin.conf file. This has been fixed. |
|
3-7404740751 |
17248392 |
(Patch Set 9) In the previous releases, when a collections task was inserted into the workflow by a CSR and then subsequently updated, it was never scheduled. Also, the /schedule object was NULL and it was not showing in the list of deferred actions for the account in Customer Center. This has been fixed. |
|
3-7250627677 |
17282786 |
(Patch Set 9) In the previous releases, the RE Loader daemon was not processing files that were staged on a file system other than the one on which the BRM instance existed. This has been fixed. |
|
3-7511849521 |
17287756 |
(Patch Set 9) In the previous releases, there was no link between the refund object and the original event for which the refund was granted, making it difficult to track. This has been fixed. |
|
3-6945487611 |
17588608 |
(Patch Set 9) In the previous releases, when rerating for a particular service S2 after rerating for another service S1, the adjustment event related to S1 was getting reapplied, resulting in incorrect balance impacts. This has been fixed. |
|
3-8014826971 |
17705577 |
(Patch Set 9) In the previous releases, a taxation-related SQL query was degrading the performance of billing. This has been fixed. |
|
3-8237233401 |
17974361 |
(Patch Set 9) In the previous releases, the pin_bus_params utility was not working. This has been fixed. |
|
3-8261620171 |
18062835 |
(Patch Set 9) In the previous releases, when an account was charged a usage with a discount, upon billing the account, the general ledger (G/L) report incorrectly displayed both gross credit and gross debit amounts instead of displaying only the gross credit amount. This has been fixed. |
|
3-8107252761 |
18077057 |
(Patch Set 9) In Customer Center, canceled products were displayed multiple times when you selected Cancelled Products on the Plans/Products tab, Customize Plan table. This has been fixed. |
|
3-8417183481 |
18174307 |
(Patch Set 9) In the previous releases, FCT_EventOrder was generating files out of order without a .xml extension. This has been fixed. |
|
3-7335940201 |
18202671 |
(Patch Set 9) In the previous releases, if a credit limit check failed in the real-time pipeline and a discount was involved, there was no appropriate error set in the error buffer and the event was incorrectly allowed to be rated and recorded. This has been fixed. |
|
3-8542691131 |
18233807 |
(Patch Set 9) In the previous releases, the start time was not being set for duration-based-charging resulting in a NULL_PTR error in the PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE opcode flow. This has been fixed. |
|
3-8197785961 |
18255638 18229692 |
(Patch Set 9) In the previous releases, BRM did not take into account the event quantity rounding rules configured at the product level in the price list during authorization when the credit limit was exceeded. With this patch, in both CRE and the real-time discount pipeline, when the credit limit is exceeded during authorization or reauthorization, the last incremental quantity can be rounded based on a new business parameter configuration. |
|
3-9021829121 |
18289230 |
(Patch Set 9) In the previous releases, account-level provisioning tags were disabled in Pricing Center. This has been fixed. |
|
3-8591368871 |
18359129 |
(Patch Set 9) In the previous releases, inactivating an account or a service, when pin_cycle_fees was not run between purchase and inactivation, resulted in charges for the deferred purchased products, if any, being not applied. This has been fixed. |
|
3-8475279591 |
18360125 |
(Patch Set 9) In the previous releases, the Vertex DM was not reconnecting after it accidentally lost the connection to the CTQ database due to a communication error. This has been fixed. |
|
3-7508765131 |
18371432 |
(Patch Set 9) The Payment Center search for payments was not displaying removed payments. The documentation mentioned that the removed payments would be shown with an icon, which is no longer available. This has been fixed. |
|
3-8621557868 |
18403909 |
(Patch Set 9) In the previous releases, the first usage validity was not being set during the authorization. This has been fixed. |
|
3-8553106291 |
18413331 |
(Patch Set 9) In the previous releases, the batch rating pipeline was not starting. This has been fixed. |
|
3-8622307441 |
18416747 18416749 |
(Patch Set 9) In the previous releases, when there were no events in the Account Sync queue, ORA-04043 errors were being reported continuously in the truss output. This has been fixed. |
|
3-8712240501 |
18423624 |
(Patch Set 9) In the previous releases, with EventAdjustmentsDuringCancellation for an account set to 1, after an adjustment to an event an error was being thrown while trying to close that account. This has been fixed. |
|
3-8213387071 |
18425704 18637848 |
(Patch Set 9) In the previous releases, during account creation, the /profile/event_ordering object was not synchronized with Pipeline Manager, causing the Pipeline Manager to crash. This has been fixed. |
|
3-8688345841 |
18425710 |
(Patch Set 9) In the previous releases, during backdated cancellation, the cycle arrears charges were getting refunded. This has been fixed. |
|
3-8583691721 |
18425712 |
(Patch Set 9) In the previous releases, the pin_recover utility was failing when resubmitting a failed batch. This has been fixed. |
|
3-8707362221 |
18426258 |
(Patch Set 9) In a multischema environment, the Oracle DM was not starting due to non-availability of required views. This has been fixed. |
|
3-6422186321 |
18433223 |
(Patch Set 9) In the previous releases, the backdated cancellation of a product that was updated to have a rate plan in place of a rate plan selector, was failing. This has been fixed. |
|
3-8678625411 |
18445287 |
(Patch Set 9) In the previous releases, the transactions related to group management operations were failing. This has been fixed. |
|
3-8695016731 |
18474465 |
(Patch Set 9) In the previous releases, a backdated purchase of a product was causing cycle_fee_t and charge_to_t to have incorrect timestamps. This has been fixed. |
|
3-8544120811 |
18474467 |
(Patch Set 9) In the previous releases, when a cycle forward arrears event was rerated, even though the event was unbilled, it was incorrectly flagged as billed, resulting in the creation of an adjustment item. This has been fixed. |
|
3-8472342851 |
18497159 |
(Patch Set 9) In the previous releases, in the PCM_OP_CUST_UPDATE_CUSTOMER opcode workflow, the /billinfo information was not updated properly in /profile/colletions_params. This has been fixed. |
|
3-7925391041 |
18497164 |
(Patch Set 9) In the previous releases, the Oracle DM was crashing when running the PCM_OP_BULK_DELETE_OBJ opcode to delete event objects. This has been fixed. |
|
3-8743735041 |
18504193 |
(Patch Set 9) In the previous releases, if a monthly cycle arrears deal was purchased, and if the end date was set to a future date twice within the same cycle, the charges corresponding to the deal for the first month were not applied. This has been fixed. |
|
3-8727444791 |
18511970 |
(Patch Set 9) In the previous releases, when an event did not have service information, for such events, a new /item/misc object was created for each instance, resulting in the creation of multiple /item/misc objects. This has been fixed. |
|
3-8665711001 |
18511972 |
(Patch Set 9) In the previous releases, an account created with a short billing cycle (creation date is January 27 and the billing DOM January 29 and cycle length is SHORT), was incorrectly having a long accounting cycle. This has been fixed. |
|
3-7480137371 |
18511976 |
(Patch Set 9) In the previous releases, with the configuration of opcode statistics logging, BRM was logging unnecessary opcode information even when an opcode was not run. This has been fixed. |
|
3-8707682611 |
18519242 |
(Patch Set 9) In the previous releases, the LoadIfwConfig process was failing with a segmentation fault error. This has been fixed. |
|
3-8819613341 |
18536832 |
(Patch Set 9) In the previous releases, when loading BEID information into BRM, the load_pin_beid utility was truncating the resource name and was updating the PIN_FLD_VALIDITY_IN_DAYS field with an invalid value when the resource name ended with digits. This has been fixed. |
|
3-8738918541 |
18550833 |
(Patch Set 9) In the previous releases, the PCM_OP_PRICE_COMMIT_TRANSITION opcode was not recognized as a valid opcode when called directly, even though it was a recommended opcode. With this patch, you can directly call the PCM_OP_PRICE_COMMIT_TRANSITION opcode. |
|
3-8065938551 |
18597350 |
(Patch Set 9) In the previous releases, with partitioning enabled, the PCM_OP_SEARCH opcode was not returning objects from the PARTITION_MIGRATE partition. This has been fixed. |
|
3-8838587351 |
18599070 |
(Patch Set 9) In the previous releases, in some cases, the trial billing workflow was finalizing the pending bill. This has been fixed. |
|
3-8516133441 |
18600210 |
(Patch Set 9) In the previous releases, the PCM_OP_SEARCH opcode was throwing an error in the DM log, indicating respawning of a backend child. This has been fixed. |
|
3-8795168801 |
18607787 |
(Patch Set 9) In the previous releases, the rollover functionality was not working correctly in the month of February for accounts with the billing DOM set to 29, 30, or 31. This has been fixed. |
|
3-8754436561 |
18607791 |
(Patch Set 9) In the Customer Center Payment tab, a NULL pointer exception was thrown when custom.jnlp was uncommented in CustomerCenter_en_jnlp.This has been fixed. |
|
3-8729438171 |
18607793 |
(Patch Set 9) In Customer Center, the number of decimal digits in the quantity fields was hardcoded to 2. With this patch, you can configure the number of decimal digits in the preferences section. |
|
3-8750007371 |
18607797 |
(Patch Set 9) In the previous releases, with 30-day proration enabled, the cycle fees were incorrectly calculated for a product that ended within a cycle. This has been fixed. |
|
3-8860097101 |
18610275 |
(Patch Set 9) During TAP3 validation in Roaming Manager, a warning message was being generated on the Recording Entity Code field. This has been fixed. |
|
3-8710825661 |
18645100 |
(Patch Set 9) In the previous releases, Pipeline Manager was considering incorrect or invalid sub-balances to consume from, when the usage timestamp was at the boundary of the correct or valid sub-balance. This has been fixed. |
|
3-8698446761 |
18645102 |
(Patch Set 9) In the previous releases, the Service Order update was failing for the service closure order when the transaction included service closure and deal cancel orders. This has been fixed. |
|
3-8381104581 |
18671002 |
(Patch Set 9) In the previous releases, Conversion Manager was not updating the data for a few columns in the BILL_T table. This has been fixed. |
|
3-8593446251 |
18677858 |
(Patch Set 9) In the previous releases, any backdated purchase of a product was charging the account twice for that product. This has been fixed. |
|
3-8099775021 |
18677873 |
(Patch Set 9) In a bill cycle, purchasing and cancelling a cascade cycle arrears discount along with a sequential cycle arrears discount was not working properly. This has been fixed. |
|
3-8603079881 |
18684106 |
(Patch Set 9) In the previous releases, there was no failure code to notify duplicate rate descriptions in price plans. With this patch, the new PIN_PRICE_ERR_DUPLICATE_RATE_DESC failure code has been added. |
|
3-8782137751 |
18695752 18704226 |
(Patch Set 9) In the previous releases, the balance impacts in the adjustment items generated during event rerating were not rounded and were shown unrounded in the invoice. This has been fixed. |
|
3-8748740281 |
18699628 |
(Patch Set 9) In the previous releases, purchasing of an annual product on the 29th, 30th, or 31st day of a month was charging the customer incorrectly. This has been fixed. |
|
3-8952197881 |
18710796 |
(Patch Set 9) In the previous releases, a debug log message was being logged in cm.pinlog even when the Connection Manager (CM) log level was set to log error messages only. This has been fixed. |
|
3-8749232001 |
18718420 |
(Patch Set 9) In the previous releases, Developer Center was sending an UnknownProgramName error when a user was logging in. This has been fixed. |
|
3-8925838164 |
18725429 |
(Patch Set 9) In Customer Center, after the password expiry, the Change Password dialog box was not appearing. This has been fixed. |
|
3-8586941611 |
18740144 |
(Patch Set 9) In the previous releases, if the current balance was below the threshold, the same threshold notification was sent to the subscriber repeatedly until a new threshold was crossed. With this patch, the threshold notification is sent only for the first session request across the threshold. |
|
3-8846734881 |
18747414 |
(Patch Set 9) In the previous releases, the in-session threshold notification was generated even when the reservation had not breached any configured threshold points. This has been fixed. |
|
3-8970377371 |
18749612 |
(Patch Set 9) In a multischema environment, when Payment Tool was opened on one schema and the reversal batch was for another schema, the application was throwing a currency conversion error during validation. This has been fixed. |
|
3-8773202601 |
18752381 |
(Patch Set 9) In the previous releases, the pin_rerate utility was not recycling EDRs that were suspended during rerating. This has been fixed. |
|
3-8902318711 |
18754591 |
(Patch Set 9) In the previous releases, Customer Center was launching with a warning about missing classes. This has been fixed. |
|
N/A |
18795043 |
(Patch Set 9) In the previous releases, any positive balance impact due to a discount was considered to be a discount in the Billing Record module and would continue to reflect as a discount in the /journal object, instead of as a charge. This has been fixed. |
|
3-8769392381 |
18817035 |
(Patch Set 9) In the previous releases, the tax calculations were incorrect during billing. This has been fixed. |
|
N/A |
18826005 |
(Patch Set 9) In the previous releases, if a cycle arrears discount was purchased before the inactivation or reactivation feature was introduced, after upgrade to BRM 7.5, those discounts did not have all the new fields. Because these fields were required in BRM 7.5, when the discount was applied during billing, the cycle arrears discounts were not applied properly. This has been fixed. |
|
3-9021271001 |
18826382 |
(Patch Set 9) In the previous releases, the item number was being updated by the system based on the bill number. With this patch, you can now control updating the item number with the perf_advanced_tuning_settings business parameter, which allows you to set a custom item number that is not updated by the billing process. |
|
3-8762099671 |
18831341 |
(Patch Set 9) In the previous releases, when a recycle payment was made from a regular account to a suspense account, the description for the payment was missing. This has been fixed. |
|
3-8935719631 |
18831343 |
(Patch Set 9) In the previous releases, when a service owned by a parent account was transferred to its non-paying child account using the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode, the pay_type of the child account's /billinfo was getting corrupted. This has been fixed. |
|
3-8893050931 |
18864043 |
(Patch Set 9) In the previous releases, even when incorrect account_poid and /billinfo were passed to the PCM_OP_CUST_SET_PAYINFO opcode, despite throwing an error the opcode was creating a /payinfo object. This has been fixed. |
|
3-8826242781 |
18879621 |
(Patch Set 9) In a multischema setup, the POID database of the product object was always getting set to the default value of 1, instead of basing the database information from the account object. This has been fixed. |
|
3-8961751531 |
18886374 |
(Patch Set 9) In the previous releases, during a failed job creation, the rerating request data such as EVENTS/SERVICES/PRODUCTS/DISCOUNTS/DEALS/OVERRIDE_PRODUCTS/OVERRIDE_DISCOUNTS were not carried onto the new job. This has been fixed. |
|
3-8331542331 |
18895133 |
(Patch Set 9) In the previous releases, the notification sequence generated in Pipeline Manager was incorrect. If an account's balance was configured for 75%, to be breached at 80%, and with a usage event impacting the balance beyond 80%, Pipeline Manager was generating the 80% balance first and then the 75% balance, instead of the other way. This has been fixed. |
|
3-8698446761 |
18914088 18914083 |
(Patch Set 9) In the previous releases, during a plan transition, the service orders were not generated properly, resulting in inconsistent results cancelling only a portion of the earlier purchased plan. This has been fixed. |
|
3-8979975258 |
18922448 |
(Patch Set 9) In the previous releases, the pin_collect utility was not processing the batch when the per_batch parameter was set to 1. This has been fixed. |
|
3-8674263601 |
18938586 |
(Patch Set 9) In the previous releases, Pipeline Manager was not starting when the profile selection criteria included a large number of profiles to be loaded. This has been fixed. |
|
3-8980965901 |
18938589 |
(Patch Set 9) In the previous releases, when a non-paying child account was added to an existing hierarchy, the non-paying account's billing cycle did not get synchronized with the billing cycle of the parent account in the hierarchy. This has been fixed. |
|
3-8986813581 |
18938592 |
(Patch Set 9) In the previous releases, the sequential discounts were not calculated correctly, resulting in generation of invalid invoices. This has been fixed. |
|
3-8956489561 |
18957533 |
(Patch Set 9) In the previous releases, there was no option to control the rounding of valid_from separately from timestamp rounding. This has been fixed. |
|
3-8949337811 |
18966929 |
(Patch Set 9) In the previous releases, during subscription transfer there was no validity check on the deal object, which resulted in updating the deal object with the passed value even if the deal object had NULL POID ID. This has been fixed. |
|
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, the flexible cycles feature was not available for cycle arrears events. This has been fixed. |
|
3-7575635931 |
17426332 |
(Patch Set 8) In the previous releases, reprocessing suspended payments was not possible. This has been fixed. |
|
3-7883532671 |
17547351 |
(Patch Set 8) When a device is disassociated from a service, the telco features and the service status were set to inactive. This has been fixed. |
|
3-7795922241 |
17554381 |
(Patch Set 8) In the previous releases, running pin_collections_process -billinfo was not considering custom pay types. 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 an Oracle Business Intelligence Publisher (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 canceled, 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 BRM multischema systems, data errors caused by conflicting storable class IDs sometimes occurred during the following operations:
This has been fixed. |
|
3-6544659031 |
17782269 |
(Patch Set 8) When Customer Center was used to modify accounts, after modifying 10 accounts (canceling a deal or a product, or modifying an account or a service status), when the 11th 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 chargeshare 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, reading an event related to a charge packet or a tax packet not having general ledger information by using testnap or applications was not possible. 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 a 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 /config/business_params was configured to do so. 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 a cycle end date later than the purchase end date, and the error message thrown was also incorrectly referring to the cycle start date rather than the 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 was 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, canceling a deal that had any old cycle events having zero balance impact was not possible. 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, running pin_collections_process -billinfo failed when a 64-bit POID was passed in. This has been fixed. |
|
3-7967455551 |
18003074 |
(Patch Set 8) In the previous releases, running pin_cycle_fees -cancel failed 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 arrears product was performed for the previous accounting cycle, with the cycle start date in the current accounting cycle, the cycle arrears 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, updating the customer-specific values for ERAs was not allowed in Customer Center. 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 JCA Resource Adapter, which resulted in JCA Resource Adapter waiting indefinitely. This has been fixed. |
|
3-8039516251 |
18045562 |
(Patch Set 8) In the previous releases, account creation through JCA Resource Adapter failed because of an 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 resulted 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, when an external transaction errored out, the uniqueness entries for the relevant account were getting removed. This has been fixed. |
|
3-8107252761 |
18077057 |
(Patch Set 8) In Customer Center, canceled 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, events prior 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, the Oracle DM was crashing intermittently during the billing process. This has been fixed. |
|
3-8218411461 |
18089343 |
(Patch Set 8) In the previous releases, the 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), setting the cycle fee end date using the PCM_OP_SUBSCRIPTION_SET_PRODINFO opcode for a product purchased before the upgrade did not generate the cycle forward event. 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 a multischema environment, attempting to perform a service transfer within a schema other than the primary schema resulted 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 took longer than expected and caused system performance issues. This has been fixed. |
|
3-8234687951 |
18105071 |
(Patch Set 8) In the previous releases, the cycle_fees dates were not correctly computed in a short cycle. This has been fixed. |
|
3-7929514301 |
18123572 |
(Patch Set 8) In the previous releases, viewing the bill details of a bill with zero item_total and due caused Customer Center to error out without displaying the bill details. This has been fixed. |
|
3-7815391001 |
18130721 |
(Patch Set 8) In the previous releases, products with a 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, an 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 arrears 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, running deferred actions was throwing errors. This has been fixed. |
|
3-8447740781 |
18181447 |
(Patch Set 8) In the previous releases, when migrating existing balances and sub-balances using Conversion Manager, bal_grp_bals_t was not populated by the pin_cmt utility. 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 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, sending a file as an input to the pricing_admin.pl script was not possible. 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, the Paymentech DM 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 incorrect error message was displayed. This has been fixed. |
|
3-8372565791 |
18229698 |
(Patch Set 8) In the previous releases, when a tailor-made product was canceled, refunds were incorrectly calculated. This has been fixed. |
|
3-7967455551 |
18255628 |
(Patch Set 8) In the previous releases, running pin_cycle_fees -cancel failed 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 was 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, unnecessary updates occurred 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 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 because the IN clause of the search template exceeded the limitation of the Oracle DM buffer. This has been fixed. |
|
3-8580263821 |
18313822 |
(Patch Set 8) The pin_cycle_fees utility was accessing more than the normal number of records for processing and was taking an 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, the 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 Vertex DM was not reconnecting after losing connection to the 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 Vertex DM were 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 BI Publisher 10g reports were deployed on a port other than 9704, reports failed to run 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, the Vertex DM 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 to shut down. 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 arrears 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_UNIQUENESS_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 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 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 an 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 combinations 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. This has been fixed. |
|
3-7939096121 |
17641286 |
(Patch Set 7) The PCM_OP_COLLECTIONS_GROUP_GET_BILLINFO opcode was failing when the 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) Running pin_rerate -a -n was throwing an error. 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 underpayment 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 underpayment 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 was not possible to track the payment using the item number, and this payment was not shown 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 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 non-currency 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) The PCM_OP_CUST_CREATE_CUSTOMER opcode 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 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 multithreaded 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 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 file, 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 the PCM_OP_SUBSCRIPTION_PURCHASE_DEAL opcode 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 the Vertex DM 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, the Oracle DM was throwing the PIN_ERR_NO_MEM error. This has been fixed. Oracle DM 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 14678171 |
(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-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 Oracle DM 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 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 the previous releases, the 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 nonpartitioned 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 the 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 DM 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 Vertex DM (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 preprocessor was changing all virtual-column POID type strings in the 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, restarting the Oracle DM failed 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 impacts. 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. |
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 the CM. |
|
Not applicable |
19226805 |
You must install the BRM-BI Publisher invoicing integration package on the system on which BRM Reports is installed. See the discussion about installing BRM-BI Publisher invoicing integration package in BRM Designing and Generating Invoices for more information. |
|
Not applicable |
18497218 |
Documentation about the -v schema_file parameter with pin_wsdl_generator utility was removed because the parameter is obsolete. |
|
Not applicable |
18645165 |
Documentation about setting the environment variables before generating the base64 encoded hash in a Solaris environment is added in the BRM 7.5 patch set installation guide. See the discussion about setting the environment variables before generating the base64 encoded hash in a Solaris environment in BRM Patch Set Installation Guide for more information. |
|
Not applicable |
16868738 |
You can now install the BRM optional managers with any supported version of Java installed on the system on which the BRM server is installed. See the discussion about BRM software compatibility in BRM Installation Guide for the supported JRE version. |
|
Not applicable |
19214339 |
After you run pin_multidb.pl -R all, run the create_procedures_character_set.plb script and the grant_permissions_oracle.plb script, which sets up the schema qualifications for payment processing, where character_set specifies the database character set of either UTF8 or AL32UTF8. |
|
Not applicable |
16519890 |
You can now install Customer Center SDK on Windows when JDK 1.7 is installed and the JAVA_HOME environment variable is set to the directory in which JDK 1.7 is installed. |