PIN_BILL_ACCTS -retry Doesn't Clear the Error Status on /billinfo object (Doc ID 2955097.1)

Last updated on JUNE 13, 2023

Applies to:

Symptoms

In the current scenario, customer is running pin_bill_accts on a list of accounts. For some of them, it ends with error and the /billinfo status is set to ERROR (billinfo.billing_status = 4).
Next, a report is made after the partial billing was run. Those bills with ERROR are analysed and once the problems are solved (it's customer's job), they call pin_bill_accts with -retry parameter.
Once it is finished, it was observed that despite the fact "partial" billing ends with no error, the ERROR status is not cleared for affected /billinfo objects.


DESIRED BEHAVIOR:
------------------
When "pin_bill_accts -retry" ends successfully, /billinfo.billing_status should be set to 0.


Steps to reproduce:
-----------------------
1. Set config_billing_delay = 1;
2. (2023-01-31) Existing /account with BDOM = 1
3. (2023-01-31) "break" the system, make it unable to bill the account correctly (one option is to stop the dm_ifw_sync);
4. (2023-02-01) perform:
        $ pin_bill_accts -verbose -file tmp_config_13272.xml

            output:
            Thread (4129786688) begins ...
            Rows(elements) read from file:6 (2)
            Thread (4138179392) begins ...
            Fetched (2) units in Total.
            Thread (4138179392) exits ...
            Thread (4129786688) exits ...
            Total number of records processed = 2.
            Number of data errors encountered = 0.
            Total number of errors encountered = 1.

            /billinfo.billing_status = 4  <- We want this status to be 4 for testing purposes.

5. (2023-02-01) "Repair" the system;

6. (2023-02-01) perform:
        $ pin_bill_accts -verbose -retry -file tmp_config_13272.xml

            output:
            Thread (4129524544) begins ...
            Rows(elements) read from file:6 (2)
            Thread (4137917248) begins ...
            Fetched (2) units in Total.
            Thread (4137917248) exits ...
            Thread (4129524544) exits ...
            Total number of records processed = 2.
            Number of data errors encountered = 0.
            Total number of errors encountered = 0.

            PROBLEM: /billinfo.billing_status is still 4   <- NOT OK. It should be 0.

IMPORTANT NOTE:
----------------------
If "pin_bill_accts -verbose -retry" is run on 2023-02-02 (note that customer has config_billing_delay = 1), then everything is OK.
But, this is not the current scenario.
Expectation is billing_status to be changed from 4 to 0 after successful retry on 2023-02-01.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.