Pin_ledger_report In Export Mode To Support Intermediate Commits (Doc ID 1552967.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.

Symptoms

pin_ledger_report is run daily in "export" mode. With the existing data, pin_ledger_report populates around 1.5 million records in 'ledger_report_accts_t' table out of which around 1million records relate to Prev-billed-earned type which takes around 1:30 hours.

 

It is observed that the application commits the transaction at the end. As a result, the transaction duration is more than an hour.

It is highly helpful to have intermediate commits that minimizes the duration of transaction and the number of records to replicate.

Using "transaction_grouping" parameter in test environment, identified the following behaviour:


1. Without setting "transaction_group" in pin.conf, and run the pin_ledger_report in "export" mode
  Input flist to PCM_OP_GL_LEDGER_REPORT opcode has 0 PIN_FLD_ACCTS_NUM_FOR_GROUP INT [0] 0


2. Setting "transaction_group" in pin.conf, and run the pin_ledger_report in "export" mode
  Input flist to PCM_OP_GL_LEDGER_REPORT opcode does not have PIN_FLD_ACCTS_NUM_FOR_GROUP field set.

Seems like the transaction_grouping parameter is not being used in "export" mode.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms