Skip Headers
Oracle® Communications Billing and Revenue Management Maintenance Patch Set 2 Release Notes
Release 7.4

E35348-06
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

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

1 Summary of Customer-Reported Fixes

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

Customer-Reported Fixes

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

Table 1-1 Customer-Reported Fixes

SR Number Bug Number Description

3-2281844291

12403114

(Maintenance Patch Set 2) In Voucher Administration Center, when the response template did not contain an Order Id instance, the validation message was not being displayed if any order instance was opened in Voucher Administration Center and a response file was passed for parsing, or if no order instance was opened and no response file was passed for parsing.

This has been fixed. When the response template does not contain an Order Id instance, the Invalid Response Template.Order Id is required in the response template validation message is displayed.

3-4579959541

13064743

(Maintenance Patch Set 2) In the previous releases, the French version of Payment Tool was displaying an error when a batch submit was attempted.

This has been fixed.

3-5866997061

14457811

(Maintenance Patch Set 2) In the previous releases, when an event-level dispute was settled, the granted amount of unsettled event dispute was not correctly displayed in the Customer Center Settlement Details dialog box.

This has been fixed.

3-6151785241

15856107

(Maintenance Patch Set 2) After installing BRM 7.4 Patch Set 14, it was not possible to change the account or service status using Customer Center because the Account/service list was not getting populated.

This has been fixed.

3-6470507691

16097039

(Maintenance Patch Set 2) In the previous releases, for systems with locales - zh_SG or en_SG, searching with First Name, Last Name, or both was not working in Customer Center.

This has been fixed. With this release, support for zh_SG and en_SG locales has been added.

3-6793501601

16324496

(Maintenance Patch Set 2) 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-6661589111

16484488

(Maintenance Patch Set 2) In Suspense Management Center, when performing a bulk search or action, the values in the Status field were displayed in an incorrect order. This was resulting in an incorrect search result.

This has been fixed.

3-6507644791

16696706

(Maintenance Patch Set 2) In Business Operations Center, for the revenue assurance data, the invoice total was always displayed as zero in the out of the box setup.

This has been fixed. The invoice total is now removed from the invoice section of Business Operation Center.

3-7791124141

17707094

(Maintenance Patch Set 2) 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-7730960101

17834396

(Maintenance Patch Set 2) 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-7606314529

18060922

(Maintenance Patch Set 2) 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-6966124921

18060931

(Maintenance Patch Set 2) In the previous releases, Conversion Manager (CMT) was not able to populate the REC_ID field in the SERVICE_ALIAS_LIST_T table based on the ELEM Id passed in the Subscriber.xml file. Instead, it was populating the REC_ID starting with 0 and incremented it by 1.

This has been fixed. CMT now updates REC_ID in the SERVICE_ALIAS_LIST_T table with value in the ELEM attribute.

3-8447316831

18289228

(Maintenance Patch Set 2) In the previous releases, while configuring account-level products or discounts, though the account-level provisioning tags were loaded they were not available in Pricing Center. The Provisioning Tag field was disabled in Pricing Center.

This has been fixed.

3-8213387071

18425703

(Maintenance Patch Set 2) 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-8760328041

18481525

(Maintenance Patch Set 2) In the previous releases, Connection Manager was resulting in core dump when there were multiple accounts receivable action items for an item. This was because of a memory access violation.

This has been fixed.

3-7894706101

18569723

(Maintenance Patch Set 2) In the previous releases, Customer Center was throwing an error when attempting to transfer a negative bill balance even though the transfer was successful.

This has been fixed.

3-8754436561

18607790

(Maintenance Patch Set 2) After installing BRM 7.4 Patch Set 19, it was not possible to open accounts in the web version of Customer Center.

This has been fixed.

3-8213387071

18637846

(Maintenance Patch Set 2) 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. BRM now includes the required checks to ensure that after processing all the CustCreate requests, if the /profile/event_ordering object is present for the account, then it will be updated in the pipeline's account cache.

3-8099775021

18677872

(Maintenance Patch Set 2) In the previous releases, the cascade discount configuration was not working if it was preceded by a sequential or parallel discount. This was because the AvoidMatchfactorCalculation parameter was not correctly evaluated. When the parameter is set to TRUE, the match factor calculation was incorrect, resulting in the cascade discount being applied even after the complete charge was considered for the preceding discounting.

This has been fixed.

3-8749232001

18718419

(Maintenance Patch Set 2) In the previous releases, when a user was logging in to Developer Center, an UnknownProgramName error was logged in the Developer Center logs.

This has been fixed.

3-7617935901

18791571

(Maintenance Patch Set 2) If a product was configured that granted non-currency resource for a monthly cycle forward event, a discount was configured on the monthly cycle forward event to impact the non-currency resource, and another discount was configured to apply sequentially, the discount configured to apply sequentially was getting applied parallelly.

This has been fixed.

3-6793501601

18796527

(Maintenance Patch Set 2) In the previous releases, even when conventional path loading was selected by the customer, RE Loader waited for a lock on the EVENT_T table.

This has been fixed. With this release, if the conventional path loading is configured, multiple RE Loader instances can now run without waiting for other instances.

3-8763732361

18817039

(Maintenance Patch Set 2) In the previous releases, when orders were being processed and the related CM was terminated, JCA Adapter was incorrectly sending some events to the application server. This terminated the processing of the transaction state balancing, resulting in an ERR_STREAM_IO error.

This has been fixed.

3-8331542331

18895132

(Maintenance Patch Set 2) In the previous releases, when pipeline generated notifications, the notification XML file had the newest notification first. For example, if a 50% breach occurred first followed by an 80% breach, the notification for the 80% breach would appear first in the notification XML file.

This has been fixed. BRM ensures that the order in which the breach occurs is maintained at the time of writing into the notification XML file.

3-8674263601

18938585

(Maintenance Patch Set 2) 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. Changes were made in the profile selection criteria to ensure that the Pipeline Manager startup does not fail because of the large data.

3-8956489561

18957532

(Maintenance Patch Set 2) For a purchase event, Valid From for a granted resource was being rounded to midnight. This may not be the required behavior for all business scenarios.

With this release, a new timestamp_rounding_for_purchase_grant business parameter is introduced to configure timestamp rounding. If the value is set to 1 (the default value) the rounding is enabled.

3-9000971543

19052366

(Maintenance Patch Set 2) In the previous releases, an incorrect version number of the patch was being displayed in Payment Center.

This has been fixed.

3-9184208121

19159726

(Maintenance Patch Set 2) In the previous releases, for an account having more than 1000 services, the rollover correction was resulting in core dump.

This has been fixed.

3-9294034251

19164377

(Maintenance Patch Set 2) During BRM 7.4 Patch Set 21 installation, the upgrade scripts were failing because the script was trying to create a comment on the DueDate column of the COLL_ACTION_IF_VIEW view. The view did not exist because it was created only when Collections Manager was installed.

This has been fixed. BRM now includes the required checks to verify if the view exists before creating a comment on the column.

3-9044443971

19170124

(Maintenance Patch Set 2) 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-9591435811

19177330

(Maintenance Patch Set 2) In the previous releases, Payment Tool was not allowing any permissions to be set unless this was done via a role configured using Permissioning Center.

This has been fixed.

3-9219324731

19246394

(Maintenance Patch Set 2) 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-9352596531

19249357

(Maintenance Patch Set 2) In a Services Framework (TCF) enabled environment, when an account with a discount was created and the service was later activated, the end date of the discount was getting set to the date on which the service order was created. This was because the PIN_DISCOUNT_SET_INFO_FLAG field was passed and there was no check to find whether the discount had ended or not.

This has been fixed. The PIN_DISCOUNT_SET_INFO_CANCEL_FLAG field is now passed for cases where the discount end date is set.

3-9324679021

19284838

(Maintenance Patch Set 2) In the previous releases, the out of the box collection action close_billfinfo was not working and services in collection were not getting closed.

This has been fixed.

3-9389962401

19305845

(Maintenance Patch Set 2) In the previous releases, the tailormade product with cycle start date in the future was resulting in charges getting applied twice.

This has been fixed.

3-9248293521

19323345

(Maintenance Patch Set 2) 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-9138903801

19344828

(Maintenance Patch Set 2) 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-9345971301

19355143

(Maintenance Patch Set 2) During BRM 7.4 Patch Set 21 installation, the upgrade scripts were failing when executed in an environment where Revenue Assurance Manager was not installed.

This has been fixed. BRM now includes the required checks on the database tables before modifying the schema.

3-7051155361

19408406

(Maintenance Patch Set 2) In the previous releases, when the in-memory zone map is was updated, the zoning PCM_OP_ZONEMAP_POL_GET_LINEAGE policy opcode sometimes went into an infinite loop.

This has been fixed.

3-9416116906

19408410

(Maintenance Patch Set 2) In some scenarios, the tax totals from the write-off balance impacts were not matching the item total because the credit tax events were not being considered.

This has been fixed.

3-8628294001

19445803

(Maintenance Patch Set 2) In the previous releases, the rating pipeline processing was stopped with the ERR_THREAD_EXCEPTION error. This was because a local variable was being accessed simultaneously by two different transactions.

This has been fixed. The local variable is now locked using RWReadersWriterLock. Additionally, changes were made to remove the unnecessary outer joins while loading the deleted profiles.

3-9294386997

19569311

(Maintenance Patch Set 2) In the previous releases, Purify tests at customer site indicated that the subscription module read memory that was earlier freed.

This has been fixed.

3-9484122981

19616032

(Maintenance Patch Set 2) In the previous releases, tax-only disputes were not being populated with the details in Customer Center.

This has been fixed.

Not applicable

12792956

(Patch Set 21) When a discount was purchased or cancelled, events pertaining to non-relevant discounts (discounts that do not act together with the discount being purchased or cancelled) with a net 0 balance impact were generated during sequential discounting. These extra events were getting displayed in the invoice, which was not desirable.

This has been fixed. A new drop_extra_seq_disc_events invoicing business parameter is introduced to indicate whether to drop these unwanted events from the invoice or not. The business parameter takes the following values:

  • 1 to drop the non-relevant sequential discounting events.

  • 0 to not drop the non-relevant sequential discounting events. This is the default.

3-6508537831

16069567

(Patch Set 21) 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.

Not applicable

16679002

(Patch Set 21) In the previous releases, the billing time taxation was not considering rerated events, which led to less tax being computed.

This has been fixed.

3-7101481291

16786810

(Patch Set 21) In the previous releases, the Collections Center GUI was not displaying the Bill Unit ID correctly for the accounts that had been manually exempted from Collections. The GUI always displayed the Bill Unit ID of the last listed account.

This has been fixed.

3-7264288811

16983886

(Patch Set 21) If Vertex was used as the tax engine and a product was purchased while Vertex Data Manager (dm_vertex) is down, the transaction succeeded but no tax was applied, which led to revenue loss.

This has been fixed. If Vertex DM is down, the transaction will now be aborted.

3-7480137371

17067321

(Patch Set 21) The quality-of-service (QoS) statistics is collected at the end of the Connection Manager (CM) connection session for all the opcodes configured in the CM's pin.conf file and written to the CM log. This reporting is not useful.

With this release, the QoS statistics is collected for only the opcodes that are configured for QoS measurement in the CM's pin.conf file and are actually called in the current CM connection.

3-7547410071

17294660

(Patch Set 21) In the previous releases, if a Monthly Cycle Arrear product was cancelled after DOM and before billing had run for the account, the non-currency resource sub-balance valid_to date was set to the date of cancellation of this product through the configured discount, even though this was not the product that granted the resource.

This has been fixed.

3-7508765131

17322226

(Patch Set 21) In the previous releases, if a payment was suspended and the unallocated payment was removed from Payment Suspense Center, the next time a search was issued, the removed payment was not displayed.

This has been fixed. The unallocated payment is now displayed with a specific icon.

3-7560575581

17337948

(Patch Set 21) 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 - 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-7548257081

17367211

(Patch Set 21) In the previous releases, the customer service representatives (CSRs) accounts created using Permissioning Center were also considered for billing because of which unwanted data was generated.

This has been fixed. For the /billinfo objects of the CSR accounts created using Permissioning Center, the PIN_FLD_BILLING_STATUS is set to 1 making it a suspended account and as a result this is excluded from billing.

3-7575635931

17426330

(Patch Set 21) In the previous releases, for an account with write off items, reprocessing the suspended payments was not possible.

This has been fixed.

3-6945487611

17588607

(Patch Set 21) In the previous releases, when rerating was run for a second service after running rerating for a service, the adjustment event related to the first service was getting reapplied.

This has been fixed. The search query now picks up events relevant only to the second service.

3-7937393814

17604199

(Patch Set 21) In the previous releases, if a database connection attempt failed, the failure status was logged in the ERROR log level. However, the success status during a database reconnection attempt was logged in the DEBUG log level.

This has been fixed. The success and failure statuses are now logged in the same ERROR log level.

3-7982611221

17673178

(Patch Set 21) In the previous releases, running pin_rerate -g was throwing an error.

This has been fixed.

3-7882870641

17841888

(Patch Set 21) In the previous releases, during trial billing, the tax entries were being logged to the Vertex database, which was incorrect.

This has been fixed. In case of trial billing, the CALC_ONLY flag is passed to the Data Manager (DM) to skip recording the tax entries.

3-8164081675

17867771

(Patch Set 21) In the previous releases, when the pricing_admin.pl script was run with the -set option to grant administrative privileges to Pipeline Manager users, the script was failing.

This has been fixed.

3-7894706101

17903776

(Patch Set 21) In the previous releases, any attempt to transfer negative bill balance via Customer Center was resulting in an error.

This has been fixed. BRM now includes the required checks while transferring negative bill balance.

3-8193290131

17950188

(Patch Set 21) In the previous releases, if an account was in an inactive state and a deal or a product configured for monthly cycle_forward_arrear charging was purchased for the account and sometime later the account was reactivated, the charges for the inactive period were applied for newly purchased deal.

This has been fixed. In case of an account reactivation, when the change_start_time_on_activation parameter is set to 0, the cycle_beg will now be updated as the time of reactivation .

3-8101948141

17979798

(Patch Set 21) In the previous releases, invoking a custom opcode through BRM Web Service was failing. This was because the :customeFields package was not accessible due to invalid path to the Infranet.properties file.

This has been fixed.

3-8252791781

17979810

(Patch Set 21) In the previous releases, migration process was reporting errors after migrating 79,000 accounts due to a memory leak.

This has been fixed.

3-8129157061

17988213

(Patch Set 21) In the previous releases, if there were old cycle forward arrear events with no balance impacts (primarily for mid cycle discount purchase), the cancellation of deal was failing.

This has been fixed. The old cycle forward arrear events with no balance impacts are now ignored during deal cancellation.

3-8115209561

17989497

(Patch Set 21) In the previous releases, the pin_bill_accts utility process was resulting in core dump.

This has been fixed. Changes were made in the code to reset the cookie and to operate on a copy of the flist to avoid memory corruption during billing.

3-5392047531

18000149

(Patch Set 21) When a bill level adjustment is applied, BRM distributes and applies the bill level adjustment amount to the individual charge items under a given bill. In certain scenarios, while rounding the individual charges, the tax amount was over calculated and was left unallocated.

This has been fixed. When there is a difference between the rounded tax amounts and the calculated adjustment tax amount, a new tax_event with the difference amount is created.

3-8091699931

18000152

(Patch Set 21) In the previous releases, for a resource whose validity is set based on first usage, an attempt to update the validity of the Balance Group was resulting in an exception.

This has been fixed.

3-7967455551

18003073

(Patch Set 21) In the previous releases, cancelling a purchase product was failing if the underlying service was inactivated and reactivated. This was because, after service inactivation and reactivation, the cycle start date of the product was updated to the service reactivate date.

This has been fixed.

3-8298105494

18020802

(Patch Set 21) In the previous releases, the memory allocated in a function was not destroyed, resulting in a memory leak.

This has been fixed.

3-8225157841

18039442

(Patch Set 21) 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-8326842051

18065157

(Patch Set 21) In the previous releases, if there are more than one deferred purchase product with a different cycle_start_t per /billinfo object, the cycle forward charges were getting created with an incorrect end_t.

This has been fixed.

3-6422186321

18067597

(Patch Set 21) In the previous releases, if the rate plan of a product was changed from rate plan selector to a single rate plan, when you tried to perform a backdated cancellation of the product, BRM rating was throwing an error. This was because the details of the rate plan change was captured in the audit table which was not being checked.

This has been fixed.

3-7929514301

18123569

(Patch Set 21) In Customer Center, if a bill having an accounts receivable items with $0 amount was queried, an error was displayed instead of showing the bill details.

This has been fixed. The unnecessary checks are now removed.

3-8077624361

18127805

(Patch Set 21) In the previous releases, if the parent billing was suppressed, the effective_t of the child items were set during the next billing cycle of the child.

This has been fixed. The effective_t of the child will now be set only after parent comes out of suppression and the bill gets finalized.

3-7815391001

18130720

(Patch Set 21) In the previous releases, during billing, products with deferred purchase start were being considered for the wrong period.

This has been fixed. The condition to pick up products with deferred purchase start during billing has been modified to consider only ENDT.

3-8412754858

18135732

(Patch Set 21) In the previous releases, even after the configured idle time limit, the JCA connections that were above the "Minimum JCA connection limit" and idle were not getting removed.

With this patch, after the configured idle time limit, the idle connections are removed.

3-8372565791

18229697

(Patch Set 21) When a tailormade product was cancelled, the scale calculation was not correct, which resulted in an incorrect refund.

This has been fixed.

3-7967455551

18255626

(Patch Set 21) In the previous releases, when a product was reactivated after its cycle end date, the cycle start date of the product was being set to the current date. This resulted in the cycle start date to be set after the cycle end date leading to a negative scale calculation and incorrect rates.

This has been fixed. If the reactivation date is after cycle end date of the product, instead of setting the cycle start date to the current date, it is now set to cycle end date, so that the scale calculation is not negative.

3-8435611631

18260631

(Patch Set 21) In the previous releases, Customer Center was not displaying Resources, Amount, Allocated, and Unallocated for failed payments (soft decline). This was because the database query was not picking up events with resource ID.

This has been fixed.

3-8586941611

18285802

(Patch Set 21) In the previous releases, an account level Extended Rating Attribute (ERA) was created, followed by the creation of a profile sharing group at the account level, and addition of a member. When the member account was billed, it resulted in errors. This was because OP_RATE_GET_ERAS assumes that the sharing profile is of type /profile/serv_extrating.

This is now fixed. The account profile is now retrieved differently from service profile.

3-8648711551

18360128

(Patch Set 21) In the previous releases, CM went into an infinite loop when an error was returned from the PCM_OP_CUST_POL_PREP_BILLINFO opcode.

This has been fixed.

3-8621557868

18403908

(Patch Set 21) In the previous releases, a resource configured for initialization with first usage was not getting initialized when authorization was triggered for a usage event.

This has been fixed.

3-8688345841

18425708

(Patch Set 21) In the previous releases, the Cycle Arrear Product charges were getting refunded during backdated cancellation though prorate on purchase and cancel was set to charge for the full month.

This has been fixed.

3-8678625411

18445286

(Patch Set 21) In the previous releases, transactions were failing when subscriptions were added to the subscription group where ordered balance group was created or updated.

This has been fixed.

3-8695016731

18474464

(Patch Set 21) In the previous releases, if billing DOM of an account was changed after the account creation and the backdated purchase of a deal was done, an error was reported.

This has been fixed.

3-8727444791

18511969

(Patch Set 21) In the previous releases, when creating or modifying an account, if there was no service object present, instead of impacting the existing item from the item POID list of the account object, a new item was created for the events. This led to creation of an additional item.

This has been fixed.

3-8580826221

18545157

(Patch Set 21) After each successful login into BRM from a client application, the MOD_T date field in the /service/admin_client object or the /service/pcm_client object was updated. This update of the date value was not necessary and was impacting the performance.

This has been fixed. After a successful login, the number of login attempts is reset to 0 only if the previous value is more than 0.

3-8738918541

18550832

(Patch Set 21) In the previous releases, when the PCM_OP_PRICE_COMMIT_TRANSITION opcode was called directly, it was not recognized as a valid opcode.

This has been fixed.

3-8795168801

18607786

(Patch Set 21) In the previous releases, the rollover feature was not working correctly on February for customers with billing day of month (DOM) on February 29, February 30, and February 31. This was because the next accounting cycle was not being correctly calculated when the billing DOM was greater than February 28.

This has been fixed.

3-8748740281

18699627

(Patch Set 21) In the previous releases, purchasing an annual product on 29th, 30th or 31st day of month created events with incorrect amounts. This was caused by wrong proration calculations.

This has been fixed.

3-2115106501

10249355

(Patch Set 20) In the previous releases, an attempt to purchase a Purchase fee product configured with an On Demand feature and cycle tax within a delayed billing period, was resulting in error.

This has been fixed.

3-3040524771

11865808

(Patch Set 20) In Pricing Center, the Code field in Price Model was allowing only ten characters even though the database field supported 255 characters.

This has been fixed. The Pricing Center GUI now supports the same number of characters as the database field.

3-6440870677

15919859

(Patch Set 20) In Collections Configuration, if a user associated to a role had permission only to read data, it was possible for the user to write data.

This has been fixed.

3-6966124921

16629185

(Patch Set 20) Conversion Manager (CMT) now updates the REC_ID field in the SERVICE_ALIAS_LIST_T table with the value specified in the elem attribute of the Service Alias array. If a duplicate value exists in the elem attribute, the DUPLICATE_ELEM_SERVICEALIASLIST error message is displayed.

3-6866310181

16660458

(Patch Set 20) In the previous releases, a refund was always issued to the current payment method and not to the original payment method that was used during purchase time.

This has been fixed. With this patch, a refund will always be issued to the original payment method.

3-7134080981

17305663

(Patch Set 20) In AAA Gateway, the large unsigned integer values in Attribute Value Pair (AVP) were treated as negative integers by the Diameter grammar, which resulted in erroneous data.

This has been fixed. AVP now supports unsigned integers.

3-7606314529

17311875

(Patch Set 20) In the previous releases, CMT was not loading all the columns for the DEVICE_NUM_T table. Only CATEGORY_ID, CATEGORY_VERSION, and NETWORK_ELEMENT were being loaded from the XML file.

This has been fixed. CMT now loads additional columns like VANITY, PERMITTED, ORIG_NETWORK_ID, and RECENT_NETWORK_ID from the XML file.

3-6955426771

17316335

(Patch Set 20) In the previous releases, credit limit check was not performed in the PCM_OP_BILL_DEBIT opcode when the extra_rate_flags values was set to 0x02.

This has been fixed. A credit limit check is now performed to ensure that the credit limit is not crossed.

3-7529868431

17324536

(Patch Set 20) In the previous releases, the cycle fold balance impact was incorrect when the plan transition and account suspension occurs on the same day.

This has been fixed. The balance impacts are now calculated correctly.

3-7661401881

17332281

(Patch Set 20) In the previous releases, if a discount was purchased for a cycle event in the middle of a cycle, the discount was not reflected in the Invoice Policy.

This has been fixed. The discount is now correctly reflected in the policy.

3-7443116061

17334136

(Patch Set 20) When the PCM_OP_CUST_UPDATE_SERVICES opcode was called, the service order was not getting generated if the status flag value was changed without any change in status.

This has been fixed. The service order is now generated if the status flag is changed without any change in status.

3-6002812991

17356828, 17305659

(Patch Set 20) When a subscriber does not have a purchased product, rerating a usage event through the rerating pipeline will fail on the real time rating side because no rating product can be found. This will occur even when a system product is available.

This has been fixed. When no purchased product is found, rerating now retrieves the system product if available. Also, the rerating pipeline input mapping is changed because a few fields may be missing for a system product when compared to a normal purchased product.

3-7640890711

17358151

(Patch Set 20) For Linux, the memory monitoring module was shutting down after reporting that the memory utilization was more than 80% even when more than 80% memory was available. This was because the module was calculating the total available memory by looking at "free" memory. However, for Linux, the total available memory is the sum of free, buffer and cached memory.

The has been fixed. The memory monitoring module now calculates the total available memory using the /proc/meminfo system file.

3-7742915251

17426335

(Patch Set 20) When the PCM_OP_SUBSCRIPTION_PURCHASE_DEAL opcode is called in the calc-only mode and if the input flist includes the PIN_FLD_CYCLE_END_T field for proration calculation, the PIN_FLD_TOTAL block was not getting populated in the output flist.

This has been fixed.

3-7485956511

17475605, 17597768

(Patch Set 20) The PCM_OP_RATE_POL_GET_TAXCODE policy opcode was not returning the user-defined tax codes from the taxcode map file.

This has been fixed. PCM_OP_RATE_POL_GET_TAXCODE now returns all the tax codes specified in the taxcode map file. Additionally, the opcode accepts PIN_FLD_FLAGS as an optional input parameter to determine which set of taxcodes are returned:

  • 0: Return all taxcodes. This is the default.

  • 1: Return taxcodes that are associated with a tax package only.

  • 2: Return taxcodes that are user-defined only.

3-7458554491

17509039

(Patch Set 20) In the previous releases, the backdated payment reversals were not considered as backdated even though the correct back date was passed.

This has been fixed. The backdated payment reversals are now recorded correctly.

3-6867499371

17528908

(Patch Set 20) In Pricing Center, if a copy (P1) of a product (P) already existed, then an attempt to create another copy P2 from P resulted in overwriting P1.This has been fixed.

3-6972678311

17588614

(Patch Set 20) With the current code and the advance_bill_cycle entry in the pin.conf file, the account creation done on 28th of any month will have a cycle day of month (DOM) as the 2nd of the next month.

This has been fixed. Incrementing DOM twice in customer registration and billing opcodes is now avoided.

3-7884394191

17597682

(Patch Set 20) In the previous releases, the GetResourceBalance iScript was not considering the First Usage sub-balances at the time of returning the result to the caller.

This has been fixed. The GetResourceBalance iScript now considers the Fist Usage sub-balances as well if it exists in memory.

3-7704113271

17613921

(Patch Set 20) In the previous releases, when the rate plan list had large number of rate plans for different combination of event types, there was a degradation in the billing performance.

This has been fixed. The billing performance is improved for cases with a large number of rate plans.

3-7533451661

17640559

(Patch Set 20) In the previous releases, the pin_cycle_fees utility was not creating the /process_audit/billing object. This has been fixed.

3-7960600071

17650887

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

This has been fixed. The CUT mode (default) for sub-balances is now avoided if configured for ALIGN.

3-7785285591

17661529

(Patch Set 20) In the previous releases, if the keep_cancelled_products_or_discounts parameter was disabled and a discount was canceled, there was no reversal of discount applied.

This has been fixed. The applied discount is now reversed correctly.

3-8055649891

17770282

(Patch Set 20) In the previous releases, CMT was creating blank data files for the custom tables where classes other than service_telco_t were extended.

This has been fixed. CMT can now migrate data in the custom tables.

3-6544659031

17782268

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

This has been fixed.

3-7051155361

17789371

(Patch Set 20) The PCM_OP_POL_GET_LINEAGE policy opcode was going into an infinite loop resulting in very high CPU utilization.

This has been fixed.

3-8034642061

17841884

(Patch Set 20) In the previous releases, processing a service order for a member service was failing because the subscription service was in the CLOSED state.

This has been fixed. It is now possible to change the status of the member services if the existing status of a member service is due to provisioning and if its status is the same as that of the parent.

3-7899039371

17845536

(Patch Set 20) In the previous releases, refund was failing for accounts with multiple /billinfo objects having an open-item accounting type.

This has been fixed. The refund amount is now calculated from the items instead of the /billinfo object.

3-8206267411

17913376

(Patch Set 20) Vertex DM (dm_vertex) was experiencing random drop in connection to the Oracle CTQ schema.

This has been fixed. If the tax calculation fails due to a lost database connection, then an attempt is made to reestablish the connection and retry the tax calculation.

3-7859806331

17926541

(Patch Set 20) In the previous releases, the performance of the PCM_OP_READ_FLDS opcode was degrading when run for objects with an array and a subarray. The select query for each second-level array was being run multiple times.

This has been fixed. The select query for each second-level array is now run only once.

3-8204924731

17930421

(Patch Set 20) In the pipeline_upgrade.cfg file, for the MAIN DB, there was an instruction to specify the main "Portal Base database". This was confusing when separate databases were used for BRM and Pipeline Manager.

This has been fixed. The instructions in the pipeline_upgrade.cfg file are now updated to reflect the pipeline details.

3-8148129781

17935804

(Patch Set 20) In the previous releases, when purchasing a backdated deal with a date prior to the last bill run date and the end date is set to a future date, an extra credit event was getting generated.

This has been fixed.

3-8101948141

17953268

(Patch Set 20) In the previous releases, exposing custom opcodes was not possible through Web Services. This was because the CustomFields package was not accessible due to an incorrect path for the Infranet.properties file.

The file path is now corrected.

3-6083521571

14508999

(Patch Set 19) Vertex CTQ version 2.00.05 introduced three new tax authority (jurisdiction) codes: 6, 7 and 9. If the Vertex tax calculation returned any one of these codes, the Vertex DM (dm_vertex) ignored the code and the event would contain an incomplete jurisdiction level tax details.

This has been fixed.

3-6366951211

14810428

(Patch Set 19) In the previous releases, the online simulator "answer_s" was erroring out for the "online CC authorization" requests without the Address Verification System (AVS) records.

This has been fixed. The online simulator now works even if the AVS records are not present for authorization only requests.

3-6478450487

16375143

(Patch Set 19) The pin_sub_balance_cleanup utility was taking a long time to process if the number of accounts was very high.

With this patch, the performance has been improved by optimizing the SQL queries.

3-6829418291

16438179

(Patch Set 19) In the previous releases, while migrating accounts with CMT, the PENDING_RECV column of BILLINFO_T was not migrated.

This has been fixed. CMT now supports importing data for the PENDING_RECV column of BILLINFO_T from the input XML file.

3-6612054981

16464990

(Patch Set 19) In the previous releases, when a bulk update was run during call detail record (CDR) suspense management, the rollback function was not updating the modified time (mod_t) field of the usage records.

This has been fixed. The modified time (mod_t) field is now updated correctly.

3-6356222213

16561346

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

This has been fixed. CMT now throws the appropriate error message.

3-6946457174

16594167

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

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

3-6924162991

16686150

(Patch Set 19) Settling the same event dispute more than once was possible, which led to incorrect account balances and variance during account reconciliation.

With this patch, a check is in place to ensure that once an event dispute is settled, it cannot be settled again.

3-6739714431

16696695

(Patch Set 19) In the previous releases, if there was a need to implement a custom service type /service/partner_csr 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 can now be read from a properties file.

3-6708809741

16696699

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

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

3-6967270651

16722100

(Patch Set 19) In the previous releases, deleting a schedule created with status 3 was possible.

With this patch, the PCM_OP_ACT_SCHEDULE_DELETE opcode description has been modified to explain status 3 of the schedule object.

3-7099004551

16731013

(Patch Set 19) During product cancellation, the closed overridden products were also being considered for refund, which resulted in incorrect refunds.

This has been fixed.

3-7147494481

16797220

(Patch Set 19) In the previous releases, the purchased product, for which the purchase_start_t is in the future, was getting updated with a flag value 1 when you run pin_cycle_fee -purchase.

This has been fixed. A new check is added to skip the products for which the purchase_start_t is greater than the current time.

3-7081494701

16813497

(Patch Set 19) In the previous releases, event charges impacted the wrong item when there were account level and service level events with the same type.

This has been fixed. In item search, changes were made to match the service object with NULL POID.

3-6924316611

16817627

(Patch Set 19) An entry corresponding to the TIMEZONE_ID field is now introduced in the EventNotificationThreshold.xsd file to use for successful parsing while loading the notification through load_notification_event.

3-7214108601

16841108

(Patch Set 19) pin_recover 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-7086566771

16862103

(Patch Set 19) Invalid characters were being printed in the Data Manager (DM) pinlog file in case of a DM failover. The character array used to print messages did not have proper values assigned in case of a failover.

This has been fixed. The array is now properly initialized.

3-6894023281

16865210

(Patch Set 19) The refund amount during discount cancellation was not properly checked against the charged amount. This resulted in an incorrect refunding amount (more than the charged amount) even when the DiscountMoreThanCharge parameter was set to False.

This has been fixed.

3-6295751911

16872613

(Patch Set 19) The first usage validity has to be set for a free resource on START_ACCOUNTING without affecting the balances. A new PIN_APPLY_BAL_FU_VALIDITY_ONLY flag is introduced to set the validity for first usage resources without changing the balances. When the flag is set, it can be used in the other layers where the validity is required.

3-6648249946

16872616

(Patch Set 19) When a service order is raised for a change in field value configured in the IGNORE block of pin_telco_provisioning, the action was set to I.

With this patch, this action is now set to C.

3-7002247331

16885165

(Patch Set 19) If a discount was purchased in the middle of a billing cycle, an already existing discount was not getting applied.

This has been fixed.

3-6688784471

16931627

(Patch Set 19) 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 in PIN_FLD_RESULTS.

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

3-7250955071

16934722

(Patch Set 19) While loading the pind_beid file, the resource names containing numbers were being truncated with the numbers being omitted. Also, the resource validity was being set to 0.

This has been fixed. Changes were made in the code to modify the string operation to accommodate numbers in the resource names.

3-7184257601

16934757

(Patch Set 19) While migrating accounts using CMT, the balance groups were incorrectly created.

This has been fixed. A new skip_bal_grp_crt attribute is introduced with the following values:

  • When set to true in the service level and if the balance group is created at the billinfo level linked to this service, the balance group creation at the service level will be skipped even though bal_grp attribute is set to true.

  • When set to false in service level, the behavior of creation of the balance group at the service level will be as before and will be based on the bal_grp attribute.

3-7015326341

16934765

(Patch Set 19) Migrating a /billinfo object without having a /payinfo object reference was not possible.

This has been fixed. A new hasNoPayInfoRef attribute is introduced, which when set to true, the default /payinfo object will not be associated with the /billinfo object.

3-7229470961

16954175

(Patch Set 19) 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-7229403101

16954178

(Patch Set 19) While trying to reactivate an inactive account having no services using Customer Center, the Account/Service status in the Account Status link, Account Summary page was not showing any values.

This has been fixed.

3-7239765781

16961320

(Patch Set 19) In the previous releases, the zero value payment items were not created for all types of payments.

This has been fixed. Changes were made in the code to create zero value /item/payment only for successful payments. For failed payments, no items are created.

3-7244911551

16969572

(Patch Set 19) In the previous releases, if a rate plan has two products where one product has its priority higher than the other, the pipeline was selecting the product that was provisioned earlier even though the one provisioned later had higher priority.

This has been fixed. A new field has been introduced in the event detail record (EDR) container that keeps track of the correct purchased product to use for rating.

3-6973064601

16977277

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

This has been fixed.

3-6914734984

16990331

(Patch Set 19) During a service's database update, core dump was occurring intermittently during a check for initialization of the service.

This has been fixed. The initialization check is changed to use the service's validTo and validFrom fields.

3-7015019691

16996679

(Patch Set 19) In the Pricing Model Rule selector, any update was resulting in the creation of a new record leading to redundant records.

With this patch, LoadIfwConfig.xsd is modified to introduce a SELECTOR_RULE, SELECTOR_DETAIL key pair for the IFW_SELECTOR_RULE_LNK table. This code verifies the presence of a key and if present does an update rather than an insert, which prevents the creation of redundant records.

3-6677554101

16996682

(Patch Set 19) For an account, if the plan transition and suspension happens on the same day, then any cycle folds were incorrectly calculated.

This has been fixed.

3-7282839891

17010196

(Patch Set 19) When there was an account with two account-level discounts (for example, one that applied on purchase events and another on cycle forward events), the cycle forward event discount applied only on the first cycle and then the discount remained active but was not applied in the upcoming cycles. The account-level products and discounts were not cached properly, which was causing the issue.

This has been fixed.

3-7327211551

17016870

(Patch Set 19) When running the pin_cycle_fees utility with purchase option, when products were having the end date set in the future, an error was reported.

This has been fixed.

3-7316047581

17033119

(Patch Set 19) When an account adjustment was triggered using a failing PCM_OPFLG_CALC_ONLY flag, it was not returning the balances.

Changes were made in the code to return the balance impact when PCM_OP_AR_ACCOUNT_ADJUSTMENT is called using the PCM_OPFLG_CALC_ONLY flag.

3-7381130861

17043205

(Patch Set 19) In the previous releases, if the payment type is changed for the parent account, the billing cycle and accounting cycles were getting changed for the subordinate account.

This has been fixed. Changes were made in the code to ensure that the subordinate accounting cycles change only when there is a change in parent account's day of month (DOM) or billing frequency.

3-6837530731

17060308

(Patch Set 19) The item type products purchased without a deal were throwing errors during rerating.

This has been fixed. Rerating will now send the PACKAGE_ID for item type products as 0 to subscription when replaying the purchase fee event.

3-7469832438

17067039

(Patch Set 19) When the balance group creation was skipped for the parent service and when there were subscription services for this parent, then a NULL pointer exception was being triggered.

This has been fixed. The service balance group creation can be skipped for the parent service and the subscription services can now be configured for this parent service without any error.

3-7412207741

17159905

(Patch Set 19) In a single transaction, if there was 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

17159909

(Patch Set 19) Doing an adjustment against a non-currency resource beyond the credit floor setting was not possible. This was because the credit floor check was done all the time.

This has been fixed. An additional check is now introduced to perform the credit floor checking only if the extra_rate_flags flag is set to Credit Floor Check.

3-7442223611

17159912

(Patch Set 19) In the previous releases, when running load_localized_strings payment_channel.es, parsing of the input file failed for Spanish locales.

This has been fixed. With this patch, support for es_CO, es_ES, es_CR locales has been added.

3-7250351111

17168833

(Patch Set 19) When running pin_collection, pin_deferred_accts, and reversal of payments before running pin_bill_accts results in an error if the account had sharing groups.

This has been fixed.

3-7389622561

17176877

(Patch Set 19) An inactivation followed by reactivation of products on the same day should result in a net $0 charge or credit to the customer. But this was not the result for all cases and some of them resulted in a net charge for the customer.

This has been fixed.

3-5745234151

17190561

(Patch Set 19) In a parent child hierarchy, if a child account is moved from one parent to another parent in a different database, the information was not being synchronized to the pipeline, which resulted in rating errors.

This has been fixed. With this patch, the synchronization of the information occurs correctly.

3-7404688921

17212489

(Patch Set 19) When a product is canceled and purchased on the same day, followed by an account adjustment, the account write-off was failing. This was because when the bill due was negative and an adjustment was done, then the adjustment amount was also being considered while calculating the net amount for write-off.

This has been fixed.

3-7218665021

17219146

(Patch Set 19) In the previous releases, running the pin_crypt_upgrade utility resulted in a deadlock.

This has been fixed.

3-6295751911

17241783

(Patch Set 19) In BRM, the validity of a resource was set only during STOP ACCOUNTING and not during AUTHORIZATION or RE-AUTHORIZATION when configured for first usage. Hence, when a resource had a validity that was decided based on first usage, the subscriber was able to continue the session beyond the original intended validity period until the resource was depleted.

This has been fixed. A new set_first_usage_in_session business parameter is added under the activity group. This parameter decides if the first usage of balance validity will be triggered at the beginning or in the middle of a user session. If the value is set to 1 (enabled), the balance at First Usage can be set at the authorization or reauthorization time, as well as at the end of session. If the value is set to 0 (default value) the First Usage is set during stop_account time.

3-7461386911

17282791

(Patch Set 19) The non-currency bundles were not getting aligned to the monthly accounting cycle during backdated deal purchase.

This has been fixed.

3-7453190761

17324544

(Patch Set 19) If the BRM server is upgraded to version 7.3 from 7.0 without upgrading CMT, the Oracle DM (dm_oracle) was not starting.

This has been fixed.

3-7662444001

17324547

(Patch Set 19) The prerating policy output was not correctly passed for later processing and hence the updated balance impact details were not being used.

This has been fixed.

3-7605568281

17347040

(Patch Set 19) Rated Event Loader (RE Loader) was wasting memory in a shared pool because it was creating and parsing separate SQL statements.

With this patch, the issue is corrected by using bind variables.

3-7758018551

17416130

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

This has been fixed.

3-5687642121

14097100

(Patch Set 18) The BRM report templates were generating an error while fetching the report data. This was due to the UTF8 issue.

This has been fixed.

3-3848978661

14362828

(Patch Set 18) 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-5916852131

14538036

(Patch Set 18) The FTP or SFTP was not working in Oracle Business Intelligence Publisher (BI Publisher). The pin_inv_doc_gen utility was changed to not construct a delivery request when the delivery configurations in pin_inv_doc_gen's Infrnanet.properties is set to an empty value.

This has been fixed.

3-6056883991

14755552

(Patch Set 18) In the previous releases, when profile sharing is used for closed user group (CUG) promotion, the CUG flag was not being set.

This has been fixed.

3-6351718824

14793459

(Patch Set 18) In the previous releases, the cancel event was not being generated for tailormade products.

This has been fixed. The pin_cycle_fees utility in cancel mode will update the status of tailormade products when run after end date.

3-6166015201

15827569

(Patch Set 18) 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

15878486

(Patch Set 18) 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, has been added to the custom.properties file: when set to true, all times are displayed in the local time; when set to false, the previous behavior continues.

3-6256008521

15897283

(Patch Set 18) 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, the CMT application will use the rollover specified in the XML, otherwise CMT will compute its own rolldata value based on UOR and Frequency.

3-5967291991

15922534

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

3-7331902991

15943877

(Patch Set 18) In the previous releases, sometimes there is a mismatch between the count of EDRs sent for recycling and the actual number of EDRs recycled occurred.

This has been fixed.

3-6246774861

15959593

(Patch Set 18) In a parent-child account scenario, if the child account is transferred, such as from prepaid to post paid, its /ordered_balgrp can have a new instance. This results in more than one /au_parent objects for the child service in the /au_ordered_balgrp resulting in SQL exceptions.

This has been fixed.

3-6612054981

16059493

(Patch Set 18) Whenever a BRM object is added or modified, the MOD_T field is updated with the timestamp of the operation. This was not happening for the /bill object.

This has been fixed so that MOD_T is getting updated in the BILL_T and BILLINFO_T tables.

3-5398269781

16102995

(Patch Set 18) In the previous releases, the deferred taxation performance was poor when there are entries in the temporary table of events not yet processed by RE Loader.

This has been fixed.

3-6177090101

16191185

(Patch Set 18) In the previous releases, Account Migration Manager (AMM) was hanging at POST_MIGRATION_WAITING status when migrating accounts across schemas.

This has been fixed.

3-5363354871

16191191

(Patch Set 18) When a 30 day proration is enabled and the end date of a discount is changed, the balance impacts were incorrect.

This has been fixed.

3-6553157811

16191201

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

This has been fixed.

3-6625636981

16194470

(Patch Set 18) In the previous releases, the purge utility execution was failing when a huge volume of data was involved.

The queries are now modified to handle high volume data.

3-6670592051

16195976

(Patch Set 18) While creating an order in Voucher Administration Center, a deal is associated with the order. If it is a service level deal, then the deal details like Resource, Quantity, Amount, ValidFrom, ValidTo were not being displayed.

This has been fixed.

3-6688704381

16212990

(Patch Set 18) When the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode is called with flist having discount POID as NULL, it returned an error, but it did not close the transaction opened internally.

This has been fixed. If the discount POID in the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode flist is NULL, the transaction will be stopped.

3-5848566207

16216631

(Patch Set 18) In the previous releases, the PCM_OP_RATE_EVENT opcode was not returning the custom information structures that are passed in the rating input flist.

This has been fixed.

3-6430427641

16228416

(Patch Set 18) In the previous releases, while trying to do 100% bill-level adjustment from the Customer Center, an incorrect G/L ID was being assigned.

This has been fixed.

3-6746248491

16264023

(Patch Set 18) In the previous releases, Oracle DM (dm_oracle) reports an error while trying to create the /reservation_list object for newly created accounts where the value of POID_IDS2 sequence is greater than 2147483647.

This has been fixed.

3-6536108181

16273944

(Patch Set 18) While creating duplicated EDRs, the FCT_SUSPENSE plugin was not populating all the fields correctly. There were fields missing in the duplicate EDR.

This has been fixed.

3-6558232211

16290242

(Patch Set 18) In a multischema environment, when pinlog_open was concurrently accessed, the pin_inv_accts utility sometimes failed.

This has been fixed.

3-6496853051

16293978

(Patch Set 18) In the previous releases, sometimes billing was failing with a memory corruption error.

This has been fixed.

3-6794353871

16314151

(Patch Set 18) In the previous releases, when an account is suspended, the monthly cycle forward charges with Prorate set to Y was applying the whole amount instead of the prorated amount.

This has been fixed.

3-5937980521

16323157

(Patch Set 18) In the previous releases, when the rollover events generated were high, rerating was resulting in an out-of-memory error.

This has been fixed.

3-5316366321

16329172

(Patch Set 18) In the previous releases, if a product was configured with Prorate set to N with an in-advance billing, when canceling the product, the charges were not refunded correctly. For example, if the in-advance fee was collected for Jan and Feb on Jan 1 and the product was canceled on Jan 15, the charges from Jan 16 to Jan 31 were also refunded. This has been fixed.

3-6762112098

16343193

(Patch Set 18) When a database connection could not be established, the Oracle DM (dm_oracle) prints the database user name and password in clear text in the dm_oracle.pinlog file.

This has been fixed so that the passwords are not displayed in log files.

3-6770524071

16346426

(Patch Set 18) 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-6398560431

16360209

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

This has been fixed.

3-6802673491

16367070

(Patch Set 18) In the previous releases, if a product was purchased for an account (activated in the past) on the current date with the product start date in the future, the cycle fees applied was incorrect.

This has been fixed.

3-6612054981

16409851

(Patch Set 18) Whenever a BRM object is added or modified, the MOD_T field is updated with the timestamp of the operation. This was not being done by PIN_REL_UPDATER.SQL.

This has been fixed. After processing an EDR, MOD_T is getting updated in the bal_grp_t table.

3-6878694537

16425433

(Patch Set 18) In the FM_CUST_POL group of policy opcodes, Papua New Guinea was incorrectly spelled.

This has been fixed.

3-6808115451

16426583

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

This has been fixed.

3-6804436351

16426596

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

This has been fixed.

3-6731225751

16431350

(Patch Set 18) In the previous releases, purchasing dummy deals failed when the validate_deal_dependencies parameter was enabled. This has been fixed. When the dummy deals are purchased, they will not be validated if they do not have any restrictions configured.

3-5236524741

16452435

(Patch Set 18) 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-6840187551

16452442

(Patch Set 18) In the previous releases, when the timezone (TZ) is set to America/Sao_Paulo and billing delay is set, the account was not billed immediately after the delay period. In this case, the delay end time was not rounded to midnight.

This has been fixed.

3-6878694537

16473836

(Patch Set 18) In the FM_CUST_POL group of policy opcodes, country names and locales were missing.

This has been fixed.

3-6645466991

16477207

(Patch Set 18) In the previous releases, the pipeline was triggering business event processing even when it was not meeting any of the conditions in DAT_Listener required to start business event processing. The DAT_Listener's interleaving was not working as expected.

This has been fixed.

3-6661589111

16484487

(Patch Set 18) In the Suspense Management Center Spanish version, there was an error in the label of bulk search criteria for purge.

This has been fixed.

3-6204691689

16488470

(Patch Set 18) 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 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-6385736491

16488477

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

This has been fixed.

3-6825956161

16502362

(Patch Set 18) In the previous releases, the START_T value was incorrectly being set and was the same as END_T in the credit-threshold notification XML.

This has been fixed.

3-6743793501

16502368

(Patch Set 18) The ratable usage metric (RUM) quantity needs to be recalculated if the corresponding candidate product is not used. If the candidate product selected is the very first product, no recalculation is done.

This has been fixed. The RUM is recalculated regardless of the current product location in the product list, as long as the rated quantity is still zero.

3-6926130931

16539701

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

This has been fixed.

3-6559585011

16572106

(Patch Set 18) 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 are not calculated correctly.

This has been fixed.

3-6898960621

16589547

(Patch Set 18) If BRM is configured to generate a separate tax event for write-offs, in cases where the event has more than one tax balance impact (with the same PIN_FLD_QUANTITY and TAX_CODE), the amounts in journal_t.cr_ar_net_amt and journal_t.cr_ar_tax_amt for a write-off entry are incorrect.

This has been fixed. If the event has more than one tax balance impact (with the same PIN_FLD_QUANTITY and TAX_CODE); then these multiple tax balance impacts are combined into one tax balance impact.

3-6730679201

16600767

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

This has been fixed.

3-6521951561

16600771

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

3-6988827201

16607114

(Patch Set 18) In the previous releases, the pipeline was freezing when a semaphore was sent prior to the completion of the earlier one. This has been fixed.

3-6738918671

16612611

(Patch Set 18) 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-6900498371

16613143

(Patch Set 18) In the previous releases, an account-level adjustment with tax was failing.

This has been fixed.

3-5558210141

16621761

(Patch Set 18) In the previous releases, when rerating is run, the EARNED_START_T and EARNED_END_T values are set to the current time.

This has been fixed. Rerating now sets the earned period of the adjustment to match the cycle event for non-GL posted cycle events. If the G/L posting is already done for the event, the adjustment created from rerating will have EARNED_START_T and EARNED_END_T fields as the current time.

3-6904646871

16629292

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

This has been fixed.

3-6924316611

16656886

(Patch Set 18) In the previous releases, when the credit control notifications were generated by the pipeline, the timestamp of the call details were incorrect.

This has been fixed. A new field, TIMEZONE_ID, is added in the balance breach notification XML which has the UTC-offset value of the CDR. The XSD file is also updated accordingly with this new field.

3-2203320611

16660463

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

This has been fixed.

3-7042543211

16672127

(Patch Set 18) 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-6901848941

16686140

(Patch Set 18) Whenever a CDR was processed and the 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-6069999361

16715859

(Patch Set 18) For products with multiple /rate_plan objects, some of /rate_plan audit instances are not picked up by rating. As a result, the corresponding rates are not found during the cancellation process.

This has been fixed to retrieve audit /rate_plan from a given product by their unique name and currency combinations.

3-6967792101

16723614

(Patch Set 18) In the previous releases, when the pin_ledger_report utility is run with the export option, the transaction was taking a long time and the commit was occurring only at the end. The option was ignoring the pin.conf file's transaction_grouping parameter.

This has been fixed so that you can now specify the number of accounts to include in each transaction.

3-6688784471

16767269

(Patch Set 18) 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 the PIN_FLD_RESULTS.

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

3-6837530731

16832782

(Patch Set 18) In the previous releases, rerating failed for item type product rerating if PACKAGE_ID was not present in the purchase event. This occurred when a customer was created without a deal.

This has been fixed.

3-7250955071

16945583

(Patch Set 18) In the previous releases, the resource names containing numbers were being truncated due to which their validity was also being affected.

This has been fixed.

3-4095552281

12780619

(Patch Set 17) The PIN_FLD_TYPE field is removed from the input specifications of the PCM_OP_CUST_SET_PAYINFO, PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER, and PCM_OP_SUBSCRIPTION_TRANSFER_SUBSCRIPTION opcodes.

3-5092704051

13541847

(Patch Set 17) In the previous releases, when billing was skipped for events that arrived late, taxation for such events could be skipped when the final billing is calculated. This was caused by the partition pruning based on the START_T and END_T of the bill.

This has been fixed. If the actual billing time is later than the bill END_T, taxation will now consider the exact billing time when the bill is run.

3-4643501511

13564220

(Patch Set 17) In a hierarchy with a paying parent and a non-paying child, if there are differences between the rounded value of a pending item amount and the sum of rounded values of all the journal entries corresponding to that item for an item belonging to the child account, the journal entry is not created.

This has been fixed.

3-5489292551

13876761

(Patch Set 17) The description of PIN_FLD_ALIAS_LIST field in the PCM_OP_CUST_MODIFY_CUSTOMER opcode is now modified because during the creation of new services the deletion of an alias list is not supported.

3-5416164621

13881174

(Patch Set 17) If the Conversion Manager pin_cmt utility and Oracle Application Integration Architecture (Oracle AIA) are used alternatively to create accounts in BRM, then within the same schema there is a possibility of unique constraint violation.

This has been fixed. During legacy data migration, the Conversion Manager pin_cmt utility now uses mangled Portal Object IDs (POIDs) similar to the Oracle DM (dm_oracle) instead of normal POIDs for BRM objects. This ensures that the unique constraint exception does not occur in a multischema migration.

3-4374606661

13917078

(Patch Set 17) In the previous releases, raising a billed event level dispute or loading a usage CDRs including taxes (default tax_supplier) resulted in core dump.

This has been fixed.

3-5520738071

14010176

(Patch Set 17) The PIN_BILL_ACCOUNTING_ONLY field is removed from the input specifications of multiple opcodes.

3-5384515091

14031744

(Patch Set 17) An offer could have a product with purchase fee and cancel fee, and a discount is associated with the cancel fee. If this offer is attached to an account and then you attempt to cancel the offer, the operation fails.

This has been fixed.

3-5937980521

14309413

(Patch Set 17) If there are a high number or rollovers for a bill unit, it could result in overflow and rerating may generate an error.

This has been fixed.

3-5899243051

14326229

(Patch Set 17) In the previous releases, in a hierarchy, if the billing day of month (DOM) is 31, then for a month with 30 days, the billing was not called for some of the child accounts. Also, if the parent has already been billed on the 31st, the next billing date is set as 30, and the next month has only 30 days, the billing process for the child accounts went into infinite loop.

This has been fixed.

3-5969777971

14347584

(Patch Set 17) In the previous releases, when sequential discounting is enabled in combination with in-advance billing, the discount that is purchased in the middle of the cycle was getting applied twice for the in-advance period. This resulted in an incorrect calculation of the discount.

This has been fixed.

3-3848978661

14362828

(Patch Set 17) In the previous releases, the same refund amount was showing up twice in general ledger (G/L) reports: once in the Billed Earned report of one period and again in the Previous Billed Earned report of the subsequent period. This issue occurred when the refund was created during the first period and processed (for payment to customer) in the next period.

This has been fixed.

3-5848549741

14488679

(Patch Set 17) In the previous releases, at the time of billing, the PREVIOUS_TOTAL field of the bill object is populated with the due amount in open items for both balance forward and open item accounting types. This was creating performance issues.

A new configuration option is provided for skipping the calculation of PREVIOUS_TOTAL in the case of open item accounting (and setting its value to 0 instead), thus improving the performance of billing when a large number of open items are present for the account. When this option is enabled, the bill suppression logic will consider only the current bill's due amount for open item accounting type (as opposed to the sum of the current due and the previous due).

3-6263299341

14696343

(Patch Set 17) In the previous releases, for some cases, the accounting dates were incorrectly set, which resulted in billing not occurring for such accounts.

This has been fixed.

3-6272901201

14737965

(Patch Set 17) In the previous releases, when a Paymentech transaction was initiated, BRM was not processing the results of this transaction correctly and was creating a settlement success event. This was because Paymentech DM (dm_fusa) returned results in an order that was different from the order in which the input was sent.

This has been fixed. A hash table is now implemented to ensure that the results of Paymentech based on the trans_id and return results from Paymentech DM (dm_fusa) are in the same order as input.

3-6278455351

14785841

(Patch Set 17) In the previous releases, when the pin_bill_run_control.xml file was used to send the Due Date Adjustment parameter to billing and days were added to the due dates of bills, the due date adjustment was not read by the billing process.

This has been fixed.

3-5932993071

14788678

(Patch Set 17) In the previous releases, for monthly free bundles configured with no proration, when the product subscription ends, the bundles allocated one month in advance and purchased with an end date two months in the future were still prorated.

This has been fixed.

3-6070254761

14792494

(Patch Set 17) In a branded environment, search was failing when the search template did not contain a space between ( and F%.

This has been fixed.

3-5329788661

14798059

(Patch Set 17) In the previous releases, running rerating sometimes resulted in an account lock. This was due to some memory leaks.

This has been fixed.

3-6367380511

14813055

(Patch Set 17) When sending the transaction to Paymentech, Paymentech DM (dm_fusa) sets the merchant number as 0000000000 except for the first record in the first file of the batch in which it sets the correct merchant number. This results in failure of the transaction.

This has been fixed.

3-6256378481

15826932

(Patch Set 17) In the previous releases, taxes with 100% adjustment (credit) were not getting reflected correctly in the tax reports, which could lead to wrong tax payments.

This has been fixed. The tax balance impact is now created in the event.

3-5470820671

15884536

(Patch Set 17) In the previous releases, when a custom bill number sequence is used, the sequence was not called for suppressed accounts. Instead, the bill number sequence was used. Because of this, there was a possibility of duplicate bill numbers.

This has been fixed. The custom bill number sequence is called for suppressed accounts as well.

3-6409133581

15896844

(Patch Set 17) For a monthly cycle forward product with two resources, when a rollover event is generated, two sub-balances are present. However, when a rollover correction event is generated, there is only one sub-balance.

This has been fixed. The rollover correction occurs correctly when multiple resources are to be corrected.

3-5879088531

15897276

(Patch Set 17) In the previous releases, the pin_deferred_act utility did not process scheduled actions pertaining to one account in a single thread. Hence, the sequence of actions could not be guaranteed.

This has been fixed. You can now use the group_by_account multi-threaded application (MTA) configuration parameter to process the scheduled actions.

3-6312350661

15903407

(Patch Set 17) In a solution deployment involving Oracle AIA, whenever Oracle AIA calls the required functions to commit the products, discounts, or sponsorships into BRM, the return from the function did not contain the sponsorship details. It returned only the committed product and discount details. Hence, Oracle AIA was not able to make the correct updates for sponsorship at its end.

This has been fixed. The function now returns the sponsorship details as well.

3-5879088531

15903413

(Patch Set 17) In the previous releases, when a deferred action was scheduled, the specified schedule time was by default rounded to midnight.

This is fixed now. You can enable the new UseExactTimeForDeferredAction business parameter to ensure that the rounding does not happen and the deferred action is considered for running at the exact time specified.

3-6432547211

15925478

(Patch Set 17) The pin_crypt_upgrade utility was used to migrate data from MD5 (Message-Digest algorithm 5) to AES (Advanced Encryption Standard) encryption. The tool is enhanced to migrate unencrypted data to AES encryption.

3-5737193121

15934743

(Patch Set 17) In a discount sharing group, when the parent discount is end-dated in middle of a cycle, the corresponding refund was not applied for the member services.

This has been fixed.

3-6470507691

15938760

(Patch Set 17) If the system was set to the Singapore locale, searching with first name/last name in Customer Center was not working.

BRM now supports the Singapore locale while searching in the Customer Center.

3-6418758921

15953381

(Patch Set 17) PIN_FLD_EVENT_TYPE and PIN_FLD_DISCOUNT_MODEL are mandatory for the Sponsorship array. However, the PCM_OP_PRICE_SET_PRICE_LIST opcode was not returning an error when these mandatory fields were missing.

BRM now verifies for these mandatory fields. If the fields do not exist, an error is displayed.

3-5558022339

15972096

(Patch Set 17) While performing externally initiated payments, the Payment Tool was displaying only one bill if there are multiple bills with the same time (END_T). This was because the bills were segregated based only on END_T.

This has been fixed. You can now include the bill number in the search criteria to segregate the bills.

3-5981512651

15972104

(Patch Set 17) In the previous releases, the service-level products that were eligible for a discount were not getting the discount upon reactivation.

This has been fixed.

3-6480407791

15978942

(Patch Set 17) When a bill cycle coincided with daylight savings time change, BRM applied 01:00 as midnight time.

Changes were made in the code to ensure that the time is rounded to 00:00.

3-5966987241

16016846

(Patch Set 17) When a cycle fee cancellation is done after full-tax-only adjustment, the cancellation is expected to have $0 tax impact. However, in the previous releases, there was a $0.01 rounding difference.

This has been fixed.

3-6416781735

16016850

(Patch Set 17) In the previous releases, when a quarterly product was purchased with backdate, the cycle dates were not set correctly.

This has been fixed.

3-6100423051

16029367

(Patch Set 17) If an account has more than 1000 subscription accounts and has a sharing group at the account level, addition of a member to the sharing group takes more than 30 minutes to complete and caused blocking sessions in the database.

Changes were made in the code to improve the performance.

3-6557250571

16029517

(Patch Set 17) During a pin_deploy modify operation, when adding a new field, the PCM_OP_SET_DD opcode was setting the AUDITABLE field value to 1 for a sub-element in the audit class. Because of this, the PCM_OP_CREATE_OBJ opcode was failing.

This has been fixed.

3-6520197511

16045635

(Patch Set 17) In the previous releases, search was returning incomplete or incorrect results when the search criteria involved second-level or third-level array items.

This has been fixed.

3-6256378481

16048719

(Patch Set 17) In case of an adjustment with tax, the adjustment amount in the adjustment event was not rounded, leaving a small POSITIVE due in the adjustment item.

This has been fixed. Rounding is now applied on the amount field.

3-6336285001

16050297

(Patch Set 17) While processing CDRs, the pipeline encountered a critical error and the CDRs were being sent to suspense. This was caused by a database query to recreate the resource ID strings. The query was being incorrectly formed by concatenating null strings.

This has been fixed. The resource IDs are now retrieved and appropriately concatenated to form the string correctly for the database query.

3-6457220581

16050308

(Patch Set 17) In the previous releases, the input of the PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode could accept only 32-bit bill numbers. When larger bill numbers were passed, it resulted in an error.

This has been fixed. The PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode can now accept bill numbers up to 64-bit.

3-5622857181

16058137

(Patch Set 17) In the previous releases, when the product purchase was backdated to a time before discount CYCLE_END, rerating was not considering a canceled discount.

This has been fixed.

3-6600679521

16058690

(Patch Set 17) When a table is modified by calling the PCM_OP_INC_FLDS opcode, the MOD_T column was not getting updated.

This has been fixed.

3-6610954311

16079278

(Patch Set 17) In the pool of objects maintained at DAT_Account, when iterating over the elements of the pool, an incorrect condition was used to terminate the loop.

This has been fixed. The condition for terminating the loop is changed to take care of the possible error scenarios.

3-6565803381

16170815

(Patch Set 17) In the previous releases, the pipeline continued to rate CDRs even when the listener's connection to the database was lost. This lead to incorrect rating at times when there was a change in the account/service data while the pipeline continues to read from memory that was not updated because the listener's connection to the database was lost.

This has been fixed. The pipeline(s) is stopped whenever ERR_DEQUEUE_EVENT is encountered, thereby ensuring that the CDRs are not rated incorrectly.

3-4548239741

16188786

(Patch Set 17) When in-advance billing was enabled, best-pricing was not working for usage events. Whenever rerating was called in calc-only mode, the balance information was not updated in the database and needed to be fetched from cache. But for in-advance billing, the validity check was failing and the data was not fetched from cache, resulting in the issue.

This has been fixed. The validity check for calc-only rerating is now skipped.

3-6558950581

16191188

(Patch Set 17) When reversing a payment in different transactions, if the second transaction started before the first transaction was closed, the payment was reversed two times and the bill due was incremented twice.

This has been fixed. The account's default balance group is now locked to prevent concurrent transactions from reversing the same payment multiple times.

3-5735726051

16196556

(Patch Set 17) When sequential discounting is enabled and if the discount end date was set to the cycle end date, two additional events were getting generated with zero value.

This has been fixed.

3-6459392301

16227755

(Patch Set 17) If rerating is used to rerate events that have been provisioned retrospectively, it created new recurring charges without adjusting the old recurring charges.

This has been fixed. For backdated cycle forward events, except for in-advance billing cases, you now set the event. end_t as cycle_info.cycle_start_t.

3-6501795141

16228281

(Patch Set 17) When discount proration settings in discount cycle validity are different like Valid from the mid-cycle = no, Valid to mid-cycle = prorate, Valid partial cycle = prorate, purchasing the discount results in error.

This has been fixed.

3-6762112098

16278203

(Patch Set 17) When Oracle DM is not able to connect to the database, it was logging the user name and password to the log file in clear text.

This has been fixed. BRM now does not log passwords in the log file.

3-6688704381

16314840

(Patch Set 17) When the PCM_OP_SUBSCRIPTION_PURCHASE_DISCOUNT opcode is called with discount POID NULL, it returns an error, but it does not close the transaction opened internally.

This has been fixed. In case of such errors, the transaction is stopped.

3-6430427641

16320665

(Patch Set 17) While doing bill-level adjustments in Customer Center, incorrect G/L IDs were being assigned.

This has been fixed.

3-4208011871

13031820

(Patch Set 16) Customer Center Help now mentions that the usage discount configured on usage products is applicable only to the real-time rating engine and is not applicable to the batch rating engine.

3-5053628351

13507695

(Patch Set 16) In the previous releases, the check refund was possible only for the default bill unit.

You can now do a check refund for a bill unit, other than the default bill unit, if it has credit balance.

3-5248430451

13645405

(Patch Set 16) The DAT_Listener module of Pipeline Manager was throwing errors if the queue was empty.

This has been fixed.

3-5165728361

13962943

(Patch Set 16) Web Services Manager now supports Java Unified Logging (JUL) in addition to the WebLogic Server Administration console logging. You can now specify the appropriate logging mechanism by using the webservices.log.enabled entry in the Web Services Manager Infranet.properties file:

  • Set webservices.log.enabled to true to enable WebLogic Server Administration console logging.

  • Set webservices.log.enabled to false to enable JUL.

3-5393366906

13963996

(Patch Set 16) Multiple RUMs were not supported for VolumeUpload and VolumeDownload.

This has been fixed.

3-3737998431

13996317

(Patch Set 16) Payment reversal was not working for multiple bill units distributed payments.

This has been fixed.

3-5592970461

13997267

(Patch Set 16) In Pricing Center, editing a price model step generated an error and the operation was canceled.

This has been fixed.

3-5628232721

14025759

(Patch Set 16) When Conversion Manager was used to redeploy an account for which the deployment failed previously, it updated the AU_PARENT_OBJ_TYPE with the wrong value.

This has been fixed.

3-5638563461

14067637

(Patch Set 16) The prorate fee was not getting applied when the product end dates were changed.

This has been fixed.

3-5484768051

14093798

(Patch Set 16) In the previous releases, the following BRM-initiated payment utilities did not consider all the accounts with different statuses at one time:

  • pin_collect

  • pin_mass_refund

  • pin_refund

With this patch, a new -all parameter has been added to the syntax of these utilities that specifies to combine all the accounts with all statuses in a batch.

3-5654692401

14124063

(Patch Set 16) A database exception was thrown by the BRM BIPExtension package if NULL was passed as the date parameter.

This has been fixed.

3-5736332131

14163517

(Patch Set 16) When a discount was applied to a cycle fee, the earned date in the balance impact from the discount did not populate correctly.

This has been fixed.

3-5864173091

14226777

(Patch Set 16) When using Conversion Manager, the REC_ID field in the ACCOUNT_NAMEINFO_T table was populated from index 0. This is now corrected and the REC_ID field now starts from index 1.

3-5882536421

14246064

(Patch Set 16) In the previous releases, the Lightweight Directory Access Protocol (LDAP) Data Manager (DM) (dm_ldap) crashed with a core dump if left idle for a few hours and if an attempt was made to connect to the LDAP server.

This has been fixed.

3-5870415561

14268082

(Patch Set 16) In the previous releases, the pin_clean_rsvns utility picked up both active and closed objects from the BRM database.

With this patch, pin_clean_rsvns does not pick up reservations in released status for processing.

3-5658567701

14294686

(Patch Set 16) For an account with a subscription group, the closure of a bill unit no longer fails.

3-5693498421

14296533

(Patch Set 16) The event adjustment opcode in BRM could accept multiple input events. However, if any of the input events in the list did not have any balance impact, an error was generated and none of the events was updated.

This has been fixed.

3-5898090871

14300078

(Patch Set 16) When posting a failed payment batch for a cash payment, the reversal event that was created did not have the CASH_INFO. Due to this, Customer Center generated an exception and Payment Type/Trans ID did not display correctly.

This has been fixed.

3-5848394021

14317764

(Patch Set 16) When processing a capabilities exchange request (CER) from an external system, Pipeline Manager no longer crashes.

3-5856738491

14338912

(Patch Set 16) When a refund was made, it was not clearing the credit balances.

This has been fixed.

3-5981756665

14365457

(Patch Set 16) BRM opcodes were not returning the description attribute with the value Success in case of a partial adjustment. Due to this, the transactions were failing in the external system from which the opcode was called because the description was expected to be part of the response.

This has been fixed.

3-5993724121

14368388

(Patch Set 16) In Customer Center, if an account search was done using first name and Spanish (Costa Rica) was set in the Regional and Language Options dialog box in Windows, the search returned the "No search criterion specified" error.

This has been fixed.

3-5723088176

14410223

(Patch Set 16) In Payment Tool, any custom field defined with an integer data type generated a validation error.

This has been fixed.

3-5498062261

14457802

(Patch Set 16) When no purchase fee was defined for a product, the pin_cycle_fees utility picked the same set of records when run in purchase mode.

This has been fixed.

3-5898081191

14457805

(Patch Set 16) When an account was suspended and reactivated on the same day, cycle fees were not getting prorated correctly.

This has been fixed.

3-6040919101

14470058

(Patch Set 16) Successfully processing the sample input files supplied with a BRM installation was not possible using the sample.reg registry.

This has been fixed.

3-6075152331

14494396

(Patch Set 16) In a multischema environment, the pin_remittance_spec utility failed to load from the primary schema when the partner account was in the secondary schema.

This has been fixed.

3-5870415561

14514274

(Patch Set 16) The search criteria for the pin_clean_rsvns utility is now fixed to pick up objects only in the reserved (active) status.

3-6029183991

14519693

(Patch Set 16) After upgrading BRM 7.3.1 to BRM 7.4, if you canceled a product, BRM did not apply the refund correctly. If there were two cycle forward events after the product cancellation, the refund was applied only for one event.

This has been fixed.

3-5985912951

14544548

(Patch Set 16) Oracle DM (dm_oracle) no longer core dumps during Oracle Real Application Cluster failover.

3-5441829871

14592849

(Patch Set 16) In a customer hierarchy with a parent account having multiple bill units and a non-paying child account, if the status of any bill unit of the parent was changed to closed, the child account and its bill unit was also getting closed.

This has been fixed.

Not applicable

14622565

(Patch Set 16) The dm_mr_search_buf_sz in the pin.conf file of Oracle DM specifies the buffer size to store the results of the SQL query in the database. If there was any error in reading this buffer, the error message displayed "dm_mr_search_sz" instead of "dm_mr_search_buf_sz."

This error message is now corrected.

3-6132801731

14628970

(Patch Set 16) A function to clear the name from NAMED_TRANS_FLIST is now added.

3-6161982351

14631981

(Patch Set 16) When transaction mode was set to NO_TRANSACTION in JCA Resource Adapter and multiple opcodes were called from an external application, the transaction mode switched to LOCAL_TRANSACTION. Due to this, orders from the external application were failing in BRM.

This has been fixed.

3-6132801731

14632640

(Patch Set 16) Within a transaction, the purchase deal was failing because NAME_TRAN_FLIST was not cleared.

This has been fixed. The purchase deal now clears NAME_TRAN_FLIST before it finishes.

3-5752250061

14645649

(Patch Set 16) Refund proration was returning wrong values when discount end dates were modified.

This has been fixed.

3-5794412221

14666016

(Patch Set 16) In Customer Center, if the service.alias.display entry was set to false in the CCSDK_Home/CustCntr/custom/Customized.properties file, the Purchase dialog box displayed the service alias in the Service list. CCSDK_Home is the directory in which you installed the Customer Center software development kit (CCSDK).

This has been fixed.

3-6051270531

14672283

(Patch Set 16) If multiple product cancellations are triggered within the same transaction, BRM no longer core dumps.

3-6224016641

14684221

(Patch Set 16) An attempt to create a service object at the account level was going into infinite loop.

This has been fixed.

3-6228137331

14694807

(Patch Set 16) An application created by using MTA framework to parse a file and call the search opcode no longer hangs when passing the objects to the search opcode.

3-3775185661

14695351

(Patch Set 16) In the previous releases, suppressing bills with zero amount was not possible because the search returned all the bills irrespective of the bill amount.

With this patch, a policy hook has been added that enables you to add a search criteria to filter out the bills as required.

3-5872086781

14710999

(Patch Set 16) The pin_collect utility generated errors when Revenue Assurance was enabled.

This has been fixed.

3-6157490261

14732290

(Patch Set 16) In Conversion Manager, the following database fields were not mapped in the schema files:

  • BILL_INFO_ID, EXEMPT_FROM_COLLECTIONS, and BILLING_STATUS_FLAGS in the BILLINFO_T table

  • SERVICE_ID in the SERVICE_T table

  • NAME in the PAYINFO_T table

This has been fixed.

3-6272674811

14737976

(Patch Set 16) In the previous releases, when searching for tailor-made products, BRM searched for all the tailor-made products available in the databases. This slowed down the search process. This is now corrected to perform search only on the products that are sent in the input.

3-4770751921

13402228

(Patch Set 15) In Pricing Center, plans added under the Transition tab were being displayed incorrectly.

This has been fixed.

3-3632896541

13431786

(Patch Set 15) In a customer hierarchy, if Bill Now was run for a non-paying child, BRM did not do billing for the child and then create a bill at the parent level to show the subordinate bill charges. Instead, the subordinate charges were directly pulled into the newly created parent bill.

This has been fixed. If Bill Now is run at the parent level, it generates the bill for child and parent with same bill number; if Bill Now is run at the child level, a split is generated: one for the child and one for the parent.

3-4797945321

13506003

(Patch Set 15) For a plan with options or a plan with a subscription group, closing the required service was not possible using Customer Center.

This has been fixed.

3-5045093731

13655473

(Patch Set 15) If there were multiple instances of a same plan (for example, Plan1 was attached to an account) while trying to transition from Plan 1 to a new plan (for example, Plan2) only one instance of Plan1 was listed.

This has been fixed to list all instances of the same plan.

3-5045093731

13692676

(Patch Set 15) In Customer Center, closing the required or optional services of a plan with options and a plan with subscriptions was not possible.

This has been fixed.

3-5317941201

13824801

(Patch Set 15) When a large number of requests were timed out, in the case of running in the degraded mode, AAA Gateway crashed.

This has been fixed.

3-5339354711

13840237

(Patch Set 15) The Balance monitoring dialog box in Customer Center was not visible when there were no services associated with the account.

This has been fixed. For the accounts without any services, the Balance monitoring dialog box is now visible.

3-5789436181

13869376

(Patch Set 15) The pipeline startup was taking a long time trying to load deleted profiles.

A new registry parameter, LoadProfilesWithoutNameValue, has been introduced. If set to False, profiles without a name-value pair (deleted profiles) will not be loaded.

3-4797945321

13919646

(Patch Set 15) In a subscription group, there were inconsistencies in the service status changes when closing the services.

This has been fixed.

3-5108821411

13919660

(Patch Set 15) Closing an account having required services was not possible either through Customer Center or through an opcode with the flag set to PIN_BILL_CHANGE_ALL_SERVICES.

This has been fixed.

3-5535528651

13960395

(Patch Set 15) The cycle arrears charges were not applied if a cycle arrears product was purchased and canceled with a backdate or reactivated with a backdate.

This has been fixed.

3-5876323081

13962947

(Patch Set 15) If a new transfer event was created as a part of customization of the billing flow, and billing and invoicing happened in the same transaction (for example, in the trial billing or any other custom operation), invoicing failed with an error about the event not being found.

This has been fixed.

3-5022230471

13970581

(Patch Set 15) The wrong partition was picked up to load the custom delayed class when the class name did not start with /event/delayed.

This has been fixed. The condition is added to check if the class name contains /event/delayed.

3-5350155001

13975764

(Patch Set 15) In Payment Center, while searching for the suspended payments, all partitions were being searched with a batch size of 5, which was impacting the performance.

This has been fixed. The search is now made only in the required partition and the batch size is made configurable.

3-5464326741

13989080

(Patch Set 15) When the pin_collect utility is run, the report generated is expected to display both the account POID and the corresponding charge. In the previous releases, the report displayed only the account POID.

The report now displays the account POID and corresponding charges.

3-3481811891

13989948

(Patch Set 15) Renaming a deal in a plan with options was failing.

This has been fixed.

3-5305190811

13996309

(Patch Set 15) When searching for large hierarchical accounts with multiple child accounts, Customer Center is taking more than 30 minutes to display the account details.

The search is now optimized to return the results faster.

3-5595437531

14004368

(Patch Set 15) AAA Gateway now populates the failed AVP block for the mandatory fields in the CER/CEA flow.

3-5350155001

14015303

(Patch Set 15) The search in Payment Center was taking a long time.

The search is now optimized to return results faster.

3-5607297991

14031749

(Patch Set 15) In a customer hierarchy, the purchase of a product at child level triggered billing for the entire hierarchy if the billing was not already done.

This has been fixed.

3-5731373991

14035757

(Patch Set 15) The pipeline failed when the ProductInfoChange event with 1000 or more products was processed at one time.

This has been fixed.

3-5614429581

14040732

(Patch Set 15) The Account search dialog box in Customer Center did not allow you to open an account without selecting the same account after sorting the Search Results list.

This has been fixed.

3-5350155001

14053268

(Patch Set 15) The search query in the PCM_OP_BILL_REVERSE_PAYMENT opcode performed an entire table search, which was impacting the performance.

The query has been optimized to enable partition-based search to improve the performance.

3-5495899031

14053279

(Patch Set 15) The CREATEFROMSTRING() and CREATEFROMXML() class methods are now thread-safe.

3-5615374591

14053283

(Patch Set 15) The back-end process of Oracle DM (dm_oracle) was getting respawned when it was trying to reconnect to the database.

This has been fixed.

3-5556756071

14058413

(Patch Set 15) The update actions on the directory server was failing for the PIN_FLD_IN and PIN_FLD_DN_FLAGS fields in the WLFDS opcode.

This has been fixed.

3-5699506431

14067703

(Patch Set 15) The pipeline was crashing when a large number of critical error messages were logged simultaneously from different threads.

This has been fixed.

3-5701356512

14088529

(Patch Set 15) When a product was created (with the RATE_TIERS value set to RELATIVE) and exported as XML without committing anything to the database, and then imported into a new session of Pricing Center and committed, the RATE_TIERS value was set to 2 (Invalid Value).

This has been fixed.

3-5450227931

14089084

(Patch Set 15) In certain cases, during the deployment of the BRM J2EE Connector Architecture (JCA) Resource Adapter, a NullPointerException was displayed, halting the process.

This has been fixed.

3-5689937671

14089889

(Patch Set 15) When a full settlement was made for an event-level debit dispute through Customer Center, the balance was reduced.

In this scenario, the balance should not have been reduced because the original dispute request was a debit request to increase bill balance.

This has been fixed.

3-5670501551

14102074

(Patch Set 15) The pin_crypt_upgrade utility considered only the fields starting with PIN_FLD_ for upgrade from Message-Digest algorithm 5 (MD5) to Advanced Encryption Standard (AES).

The pin_crypt_upgrade utility now considers all the fields for upgrade.

3-5738668041

14109630

(Patch Set 15) Each sequencer had a database connection open throughout its lifetime. This was causing the pipeline to run out of database connections when a large number of sequencers were configured.

This has been fixed.

3-5590835511

14113269

(Patch Set 15) The Permissions Center dialog box in Collections Configuration Center was taking a long time to load if the number of customer service representatives (CSRs) were more.

This has been fixed.

3-5634882793

14113274

(Patch Set 15) Permissioning Center was taking a long time to find and display the CSRs in a role if the number of CSRs were more.

This has been fixed.

3-5665957951

14120958

(Patch Set 15) For an existing product in the database, a POID revision was created when loading a price list for the existing product without any changes.

The POID revision is now created only if there is a change.

3-5754924321

14121176

(Patch Set 15) The purchase of tailor-made products was failing because of not meeting the uniqueness constraint.

This has been fixed. The name created by the tailor-made product has the product name followed by the time in hex and the thread ID.

3-4978193941

14138139

(Patch Set 15) The password in the Infranet.properties file used by BI Publisher to connect to BRM was not encrypted.

This has been fixed to allow AES-encrypted passwords in the Infranet.properties file of the pin_inv_doc_gen utility.

3-5749016741

14157844

(Patch Set 15) Due to memory leaks, the BRM LDAP Data Manager was crashing after approximately 2000 operations.

This has been fixed.

3-5688917331

14166591

(Patch Set 15) If the /config/business_param EventAdjustmentsDuringCancellation entry was set to True, a product cancellation would cause an over-refund of the cycle fees. This happened in cases where a tax-only credit adjustment was previously done on the cycle fees.

This has been fixed.

3-5762909541

14187959

(Patch Set 15) In the account maintenance mode of Customer Center, the fields were not resized when the window was resized in the Product Details page.

This has been fixed.

3-5685959961

14191188

(Patch Set 15) In STOP Accounting Flow, a search was performed even for the correlation ID having null values.

An additional check is now included to avoid this search.

3-5715846851

14206244

(Patch Set 15) When a service-level product was canceled, the previously applied account-level discount was not getting refunded if sequential discounting was enabled.

This has been fixed.

3-5794523181

14206255

(Patch Set 15) Backdated purchase of a product aligned to a billing cycle was not creating charged events aligned to the cycle.

This has been fixed.

3-5595693481

14209774

(Patch Set 15) If the pin.conf parameter keep_cancelled_products_or_discounts was set to 0, a call to the PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS opcode in the same transaction as the product/discount cancellation sometimes caused the DM to log an error.

This has been fixed.

3-5791477121

14231560

(Patch Set 15) In Customer Center, service-level resource adjustments were changing the validity dates of all the records instead of only the selected record.

This has been fixed.

3-5189797981

14253367

(Patch Set 15) Balance breach Notification XML was generated even when an ongoing transaction was rolled back.

This has been fixed.

3-3252428421

14297864

(Patch Set 15) The FCT_DuplicateCheck module was internally using a deprecated API from a third-party library, which was causing high memory consumption in some cases.

This has been changed to use a new API.

3-5688917331

14320843

(Patch Set 15) If a refund was made on a cycle-forward fee through an accounts receivable action such as an adjustment or dispute, while canceling CYCLE_FEES, the cancellation refund did not consider the accounts receivable action and refunded more than what was charged.

This is now corrected to consider prorated account receivables action on the same scale as cancellation.

3-3141010911

11933586

(Patch Set 14) The startup time of the Connection Manager (CM) has been reduced.

3-4257191971

12881903

(Patch Set 14) In the previous releases, the TAP3.11 file was rejected due to an incorrect total charge. This happened because the global variables were not reset when a transaction rolled back.

This is now corrected by using the new resetGlobalVariables function in the ISC_TAP_0311_Validations iScript. This function resets the global variables when a transaction rolls back.

3-4672388311

13071996

(Patch Set 14) In the previous releases, there was no option to check the data type of the fields that were common between Pipeline Manager and BRM. This caused some of the common fields to get incorrect values assigned to them when there was a mismatch between Pipeline Manager and BRM data types.

A new entry, FieldTypeCheck, is now added to the EDR Factory section of the registry file that checks the data type defined in the fields that are common between Pipeline Manager and BRM. If the data types match, Pipeline Manager starts up as usual. If the data types do not match, a critical error is generated during Pipeline Manager startup.

3-4073294581

13347994

(Patch Set 14) The pin_inv_doc_gen utility now correctly works even if BRM virtual time is set by using the pin_virtual_time utility.

3-4932147421

13403060

(Patch Set 14) In the previous releases, if a deadlock occurred when running the pin_deferred_act utility, the PCM_OP_ACT_SCHEDULE_EXECUTE opcode opened a transaction, which was not committed or rolled back.

pin_deferred_act has been modified to ensure that the transaction is always closed even in case of a deadlock.

3-4981452981

13443418

(Patch Set 14) In the previous releases, when rating CDRs through a pipeline, the aggregation results file for an aggregation grouping scenario stored inconsistent data. This has been corrected.

3-4442452791

13461050

(Patch Set 14) The size of the Charge field in the TAP3.11 description file has been updated from 4 bytes to 8 bytes. The Charge field can now accommodate values up to 8 bytes.

3-4991121561

13468796

(Patch Set 14) 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-5115115411

13543305

(Patch Set 14) The Paymentech DM (dm_fusa) now sends the Paymentech files in the correct format for the Paymentech software to process.

3-5113094141

13550805

(Patch Set 14) The pin_bill_accts utility now correctly works with the -retry option under a brand.

3-5117857841

13580010

(Patch Set 14) In the previous releases, when an account was created for an Oracle In-Memory Database (IMDB) Cache DM system by using the PCM_OP_CUST_COMMIT_CUSTOMER opcode, BRM generated an error if the ACCOUNT_NO value in the input flist was not in the 0.0.0.1-123456 format.

This has been corrected.

3-4863380241

13581448

(Patch Set 14) The Paymentech DM now returns the correct response codes during refunds.

3-2784083551

13581458

(Patch Set 14) When retrieving the current bill during rerating, the first occurrence of the bill is now picked from the list of bills instead of picking the array index 0.

BRM now checks for a corresponding event before reapplying CYCLE_ROLLOVER to verify that the event is consistent with the original event's billed status.

3-5240562851

13599157

(Patch Set 14) BRM now supports rerating item type products and provides limited support for best pricing with item type products.

3-5056141341

13618468

(Patch Set 14) In the previous releases, the start date of the next monthly cycle (actg_next_t) was set incorrectly for the subordinate accounts that were created during the delay period.

Changes were made to check if the subordinate account is created in the delay period and to assign the correct value to actg_next_t.

3-5251157421

13642609

(Patch Set 14) The Paymentech DM now works as designed while processing transactions when the merchant descriptor flag (sd_descriptor_flag) is enabled.

3-5192527671

13644080

(Patch Set 14) In the DAT_ModelSelector module, the SQL statements that are used to load the configuration data from the Pipeline Manager database now contain bind variables instead of literals.

3-4798747791

13645429

(Patch Set 14) Changes were made to improve the performance of the PCM_OP_SUBSCRIPTION_CANCEL_DEAL and PCM_OP_SUBSCRIPTION_TRANSFER_SUBSCRIPTION opcodes when these opcodes are used for an account with multiple subscription groups.

3-5247955161

13649212

(Patch Set 14) In the previous releases, in Pricing Center, the login information, such as login name, host, and port, that you entered in the Login dialog box were always saved. The Login dialog box auto-filled the saved login information the next time you logged in. There was no option to disable the auto saving of login information.

With this patch, you can now disable the auto saving of the login information by adding the following entry in the PricingCenter_Home\lib\custom.properties file, where PricingCenter_Home is the directory in which you installed the Pricing Center:

login.connection.save.locally = false

3-5239170171

13651172

(Patch Set 14) In the previous releases, you could not stop Pipeline Manager by using the pin_ctl utility when the Event Handler block in the registry file contained wildcards, such as an asterisk ("*").

This issue has been fixed.

3-5247218131

13685061

(Patch Set 14) While loading multiple EDR files in the database, the SQL insert query now uses bind variables to save memory in the shared pool cache.

3-5279060591

13685928

(Patch Set 14) In Customer Center, you can now customize the maximum number of bills that are displayed in the Balance tab for any account. The default is 6.

3-4952140121

13692682

(Patch Set 14) BRM now correctly generates a rollover correction event when multiple resources require correction.

3-5309283921

13735577

(Patch Set 14) After changing the product end dates, when the discount end dates are changed using the PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO opcode, the discount is now correctly calculated.

3-5225267011

3-5595693481

13788950

(Patch Set 14) If the keep_cancelled_products_or_discounts entry in the CM pin.conf file is set to 0 and a product or discount is canceled, a subsequent call to the PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS opcode in the same transaction no longer generates an error.

3-5163911181

13814599

(Patch Set 14) The PIN_FLD_DESCR field in the input flist of the PCM_OP_CUST_SET_STATUS opcode now specifies whether the call to PCM_OP_CUST_SET_STATUS to update the status of an account or a service is intentional or inadvertent. PCM_OP_CUST_SET_STATUS now updates the status of an account or a service as follows.

  • If there is a change in the status of the account or the service, the opcode always updates the status, irrespective of whether PIN_FLD_DESCR is present or not.

  • If there is no change in the status of the account or the service, and PIN_FLD_DESCR is present, it means that the call to the opcode is intentional. The opcode compares the new value of PIN_FLD_DESCR with the present value. If the values are different, the opcode updates the related fields. If the values are the same, the opcode returns without modifying anything.

  • If there is no change in the status of the account or the service, and PIN_FLD_DESCR is not present, it means that the call to the opcode is inadvertent. The opcode returns without modifying anything.

3-5134046211

3-5464326741

13819766

(Patch Set 14) When there is more than one failed account, changes were made in the code to ensure that, while running the pin_collect utility, the account number is not repeated in the failed accounts array while creating the /process_audit/billing object.

3-5469723451

13858997

(Patch Set 14) In the previous releases, the DM generated an error when the transaction ID started with the letter V. This happened because the DM treated the V as a search argument rather than the absolute value.

This has been corrected.

3-5498155871

13927837

(Patch Set 14) In the following applications, the Preferences dialog box now correctly displays all the tabs:

  • Collections Center

  • IP Address Administration Center

  • Payment Center

  • Pricing Center

  • Revenue Assurance Center

  • Suspense Management Center

3-5322812501

13950520

(Patch Set 14) The PCM_OP_SEARCH opcode now correctly retrieves all the data when there is a condition on a field within an array of arrays.

3-5530772021

13962952

(Patch Set 14) In the previous releases, the loadpricelist utility generated an error when committing a price list to the database. The error occurred because the exported XML file contained the <plan_list_code> element for each plan list. This element was required only if BRM and Oracle Communications Pricing Design Center (PDC) integration was enabled.

With this patch, the <plan_list_code> element is added to the exported XML file only when it is required. By default, this element is not present.

3-5385832361

13964762

(Patch Set 14) In the previous releases, when there were multiple currencies defined for a product in a rate plan, the loadpricelist utility exported only the first currency to the XML file.

Changes were made in the code to ensure that loadpricelist exports all the currencies defined for a product in a rate plan.

3-3480449261

12414024

(Patch Set 13) In the previous releases, every time a new exchange rate is loaded, the CM needed to be restarted to use the new rate.

The exchange rate is now refreshed when the refresh interval duration specified in the new ExchangeRateRefreshInterval business parameter expires.

3-3387024141

12627294

(Patch Set 13) In case of multiple /billinfo objects, BRM now does not generate the refund event just based on the sign of the bill unit's due.

3-3539466021

12718253

(Patch Set 13) You can now account for event adjustments made on the cycle fees while calculating the refund during product inactivation or cancellation by using the new event_adjustments_during_cancellation business parameter in the subscription instance of the /config/business_params object.

When you set the event_adjustments_during_cancellation business parameter to 0 (the default value), subscription does not consider event adjustments on the cycle fees while calculating the refund.

When you set the event_adjustments_during_cancellation business parameter to 1, BRM searches for the event adjustments done on the product's cycle fees and passes the consolidated adjustment to rating. Rating manipulates the refund to ensure that rating is not more than the effective charge (original charge minus the refund).

3-3909577221

12779313

(Patch Set 13) After the account is created, when the /balance_group/monitor object is added and batch rating is performed, BRM now creates only a single entry for the /balance_group/monitor object in the outfile.

3-4154782851

12823026

(Patch Set 13) In the previous releases, the billing time taxation ignored any adjustment event that occurred at the billing boundary (the event end time of 00:00:00 hours) on the billing start date. This resulted in the adjustment amount not getting taxed.

This has been corrected.

3-3411898361

3-4142044581

12911961

(Patch Set 13) The pin_inv_doc_gen utility now supports ftp/sftp as the delivery option.

3-4211938221

3-4333530651

12936631

(Patch Set 13) When taxation is configured, the balance impacts due to the cycle taxes are now reflected in the monitored balance groups. Also, if an item-level adjustment is made on the cycle taxes, the balance impacts due to taxes on the adjustment amount are reflected in the monitored balance group.

3-3753364551

13017479

(Patch Set 13) BRM now returns multiple records with the same effective_t by using the new PIN_FLD_SELECT_RESULT field in the input flist of the PCM_OP_SUBSCRIPTION_GET_PURCHASED_OFFERINGS opcode.

Note: When you set the PIN_FLD_SELECT_RESULT field, all the records with the largest effective_t will be returned in the output flist, instead of returning the first one returned by the database search. If two or more records have the same effective_t, you still need to customize invoicing to sort the records and decide which record to display.

3-4538256361

13067421

(Patch Set 13) Improved performance for concurrent access, in case of logging, during billing or any other multithreaded applications.

3-4677525221

13068396

(Patch Set 13) Conversion Manager is now capable of migrating the /purchased_bundle class from the legacy database to the BRM database.

3-4553675131

3-4716726441

13077530

(Patch Set 13) When you call the PCM_OP_READ_OBJ opcode to read any /billinfo object using a Web service, you will get output of this opcode in XML format. While converting this XML flist to BRM flist format, BRM no longer throws any exceptions.

3-4501298011

13077543

(Patch Set 13) Web Services Manager will now parse the decimal separator based on the locale value.

3-4736506131

3-5187479141

13097312

(Patch Set 13) In Customer Center, during account creation, purchase, and maintenance, when a deal has a product and a discount with the same name, a discount icon is displayed for the product in the Plan page.

This issue has been corrected.

3-4744887151

13107449

(Patch Set 13) In Pricing Center, when you create a Plan With Options plan for a /service/telco service having two /service/telco deals, on database commit, the plan gets committed. When you restart Pricing Center, the service and its deals are not visible in the plan.

This issue has been corrected.

3-3590211441

13241152

(Patch Set 13) For a credit card account, after billing is done, when a plan with a higher value is canceled and a new plan with a lower value is purchased, the Refund Details page in Customer Center now displays the correct refund amount. The displayed refund amount is calculated after applying the prorated charges and the charges for the newly purchased plan.

3-3276584371

13246987

(Patch Set 13) In the previous releases, when a /billinfo object entered collections for a month, the collection action is run for that month, but for the next month onwards even though the bill is not paid, the collection actions are not run.

A policy hook has been provided to achieve the intended behavior.

3-3203134721

13344953

(Patch Set 13) In the previous releases, if the amount in an event was 0, BRM did not allow any adjustments on that event.

You can now control the event adjustment behavior when the event amount equals 0 by using the new event_over_adjust_enable business parameter.

3-4863380241

13347372

(Patch Set 13) During upgrade from BRM 7.3.1 to BRM 7.4, the payment opcode did not return the proper response codes. This occurs when you have the same merchant information for many charge packets.

Changes were made in the code to ensure that the correct response codes returned by Paymentech DM have the same response code as the charges array.

3-4716726441

13349937

(Patch Set 13) In the previous releases, while converting the flist to XML, when the flist contains extension fields (PIN_FLD_EXTENDED_INFO or PIN_FLD_INHERITED_INFO), the Web service code created XML tags depending on the brm_extension.xml file. But when no matching container was available and the flist contained direct extension fields (not wrapped inside any array), the conversion gave an error due to a NULL container.

Changes were made in the code to ensure that when the container is NULL, the customized tag generation is ignored and the default behavior (generating tags like <brm:INHERITED_INFO> or <brm:EXTENDED_INFO>) is used.

3-4882140921

13356326

(Patch Set 13) If the error buffer is set while performing settlement of a dispute, BRM no longer core dumps.

3-4897477591

13370501

(Patch Set 13) You can now enable the logging mechanism for the pin_purge utility.

3-4722741271

13386556

(Patch Set 13) When multiple pipelines perform an FSM search simultaneously for an event and service type combination, FSM now returns the correct search result.

3-4643501511

13386559

(Patch Set 13) The performance of the billing time taxation stored procedures is now improved by limiting the event search to a few specific database table partitions.

3-4694765491

13396848

(Patch Set 13) The discount sharing groups are now migrated properly and the default ordered_groups are created successfully.

3-4876708421

13422695

(Patch Set 13) For a canceled deal containing a cycle event, the G/L report now displays the correctly rounded EARNED_START_T/EARNED_END_T, if the timestamp_rounding configuration is enabled.

3-4872928851

13423836

(Patch Set 13) Products with future-dated purchase start dates (purchase_start) are now filtered out when PURCHASE_FEES is called.

3-3142233971

13426550

(Patch Set 13) The /schedule objects having status other than PIN_SCHEDULE_STATUS_DONE will now be transferred to the target account. All the /schedule objects corresponding to member services (including the parent service) will be transferred to the target account.

3-5011240881

13462826

(Patch Set 13) Changes were made to add the Parallel Enabled option to a database function. This ensures that the parallel hints added to the main billing select query during customizations now run properly.

3-4936699701

13475278

(Patch Set 13) In the previous releases, due to some changes in Business Application SDK (BAS), the dbLoader utility could not process the .ctl files. This is now corrected.

3-4932754181

13486002

(Patch Set 13) With the 31-day billing feature, you can now create accounts with billing segments having DOM set to 29 through 31.

3-5022365641

13494459

(Patch Set 13) BRM now logs the "DMfe #x: not accept token owner (x)" error message as a warning in the dm_oracle.pinlog file.

3-4941241011

13501312

(Patch Set 13) In the previous releases, when a product having both monthly cycle forward and annual cycle forward rate plans configured is inactivated and then reactivated, the cycle fees array pertaining to the annual cycle forward rate plan was set to the same dates as the monthly cycle forward rate plan, so the annual cycle forward event was charged again even though its cancel proration was Charge Full.

The CYCLE_FEES arrays are now updated correctly.

3-4885641211

13510469

(Patch Set 13) Changes were made in the device framework to ensure that the /device objects stay in the primary schema/database and the objects are updated correctly.

3-4315955271

13529011

(Patch Set 13) Pipeline Manager now charges calls correctly as per the configured price model for the premium SMS destinations.

3-4847341631

13532798

(Patch Set 13) In a multischema system, payment from an account residing in the primary schema to the account residing in the secondary schema is now allowed when the transaction cache is enabled.

3-4777533701

13534534

(Patch Set 13) A custom DM no longer crashes while opening the DM framework linking the Roguewave libraries and the third-party libraries, which are being loaded at run time.

3-4882635681

13534542

(Patch Set 13) The pin_cycle_fees utility no longer throws an error while trying to read the events that are not created.

3-5058889871

13536647

(Patch Set 13) The default ordered_groups is now created only once for one instance of ordered_balance_group.

3-4846513461

13562431

(Patch Set 13) In the previous releases, the PCM_OP_SEARCH opcode returned an incomplete list of objects.

Changes were made to clear the error buffer if the error code is set to PIN_ERR_NOT_FOUND.

3-4082777181

13568194

(Patch Set 13) If the balance group monitor is configured at service level, and an A/R item adjustment is done, the balance monitor object now properly reflects the monitor impacts.

3-5087331041

13569560

(Patch Set 13) In the previous releases, the write-off tax event was not generated when the tax flag was set in the PCM_OP_AR_ACCOUNT_WRITEOFF opcode.

Changes were made in the query to fetch all the tax events.

3-2029824721

10052332

(Patch Set 12) pin_ctl now redirects stdout and stderr to the process.log file.

3-2567145671

11654454

(Patch Set 12) In the previous releases, in the ISC_TAP_0311_Include.isc iScript, the CallTypeLevel 1 and CallTypeLevel 2 fields in the TAP3.11 file were mapped to the DETAIL.CONNECT_TYPE field with a comma separator. Due to this, the pin_rel utility was not able to load roaming GPRS events to the database.

This issue has been corrected, and the comma associated with the DETAIL.CONNECT_TYPE field has been removed.

3-2757549221

11811285

(Patch Set 12) BRM now sets the proper impact type after rerating for rollover and canceled products.

3-3141522481

11865376

(Patch Set 12) In the previous releases, the rollover_correction event and its balance impacts pointed to different item objects, and the service object pointer was missing on the rollover_correction event.

This issue has been corrected and the item object and the service object are now fetched from the original rollover event and populated on the rollover_correction event.

3-3142233971

11882192

(Patch Set 12) In the previous releases, the /schedule objects with status 3 were not transferred to the new account after the subscription transfer. In the services hierarchy, the /schedule objects of member services (except parent) were not transferred to the new account.

This issue has been corrected and the /schedule objects having status other than PIN_SCHEDULE_STATUS_DONE are transferred to the target account and all the /schedule objects corresponding to member services (including parent service) are transferred to the target account.

3-3288623191

12310372

(Patch Set 12) When running the pin_rel utility, in case the loading is retried, the exception thrown while creating the tables is now properly handled.

3-3429462261

12560280

(Patch Set 12) When you migrate a product that charges multi-month cycle fees having the cycle_start in the past, BRM now charges the cycle fees correctly.

3-3606729831

12586832

(Patch Set 12) The optional deal purchased on the account is now part of the subscription group defined in the pricing plan.

3-3999525282

12630895

(Patch Set 12) Account Migration Manager now updates uniqueness_t and au_uniqueness_t tables on the primary schema after the account migration. When the source and destination schemas for the migrating accounts are not the same as the primary schema, the job_batch_accounts_t table is updated with the job and batch details.

3-3654512481

12647465

(Patch Set 12) When the <SubsDis74BackDateValidations> subscription business parameter is enabled in the bus_params_subscription.xml file, a backdated cancellation of a product, whose PURCHASE_END is set to a time after the account is effective, is successful.

3-3301753601

12732225

(Patch Set 12) BRM now successfully generates the service orders for services configured for provisioning, even if some of the services in the plan are not configured for provisioning.

3-4040095551

12759452

(Patch Set 12) When sequential discounting is turned on and a discount is purchased with future start dates, BRM now generates the expected number of cycle events when the deal is purchased.

3-4023637801

12760535

(Patch Set 12) The pin_rel utility no longer throws an error while loading information into the service tables.

3-4040788161

12761978

(Patch Set 12) When the pin_sub_balance_cleanup utility is used to purge expired account sub-balances from the BRM database, an error occurs. This error is due to the following missing parameters in the BRM_Home/apps/pin_subscription/pin.conf file that are required for the utility:

  • pin_sub_balance_cleanup db_user pin_user

  • pin_sub_balance_cleanup db_password pin_user_password

  • pin_sub_balance_cleanup db_name db_alias

  • pin_sub_balance_cleanup db_accesslib ocilib

You must manually add these parameters in the BRM_Home/apps/pin_subscription/pin.conf file.

3-4019830701

12768443

(Patch Set 12) BRM now performs validation to ensure that the PIN_FLD_SERVICE_OBJ parameter is passed in the input flist at the 0th level during the creation or modification of the service level profile object.

3-3916218711

12774919

(Patch Set 12) When processing TAP files, the seq_gapnumbers field is not correctly populated in the ifw_seqcheck table, which causes the files that are not in the missing sequence to error. This no longer occurs.

3-4130093074

12794016

(Patch Set 12) The search type for the recycle_suspended_usage_t record in the amt_metadata_t table is changed from search type A to P.

3-4130092961

12794028

(Patch Set 12) The missing keyword DISTINCT is added to the query in the AMT_MV package.

3-4147313061

3-4398459401

12808550

(Patch Set 12) The device state ID is now loaded successfully into the BRM database based on the values for each device provided through the <StID> element in the input XML file.

3-4160488461

12823817

(Patch Set 12) A new log statement is introduced to print the recently run opcode name and its correlation ID in the JCA Resource Adapter log file that matches the correlation IDs in the CM log file. This log statement is printed after the opcode method is called.

3-4157008131

12850306

(Patch Set 12) The pin_amt_test utility now displays all the account POIDs that are migrated from one database or schema to another database or schema, irrespective of the length of the account POID.

3-4096700411

12881273

(Patch Set 12) Conversion Manager does not read the value specified for the <elem> element in the input XML file. The <elem> element is used only for reference.

3-4304561481

12905684

(Patch Set 12) In the previous releases, when you tried to update the credit limit from Customer Center, an ERR_NULL_PTR error was thrown. This no longer occurs.

3-4195503491

12914170

(Patch Set 12) The Paymentech DM now successfully sends the CVV value for Discover Diners card to Paymentech.

3-4087604261

3-4087604261

3-4423245683

12933347

(Patch Set 12) The PCM_OP_SET_STATUS opcode now returns without modifying the status when the new status and the new description of the account or service is the same as the present status and description of the account or service.

3-4343303361

12955630

(Patch Set 12) In the previous releases, after extracting the data with the -rall option (or retrieve_all), LoadIfwConifg crashed with a core dump. This no longer occurs.

3-4303129231

13050711

(Patch Set 12) In the previous releases, the end date entered without the time value was considered from start of the day, which means 00:00:00. With this patch, the end dates without the time values will be considered from end of the day (23:59:59). However, the start date will continue to work from start of the day (00:00:00).


Fixed Known Problems

Table 1-2 lists the previous known problems that are now fixed and provides a brief description of the resolution.

Table 1-2 Known Problems Fixed

SR Number Bug Number Fixed Resolution

Not applicable

14177870

BRM now compiles the files in the policy opcode directory without an error.