Realtime Rerating Is Not Creating A New Job With The Status New For Failed Jobs.

(Doc ID 1300290.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: to - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.


According to the documentation: "When rerating fails for one or more accounts in a rerate job, pin_rerate sets the status of the accounts in the rerate job batch to FAILED. When rerating process is complete for the rerate job, pin_rerate creates a new rerate job consisting of only the accounts that failed. The new rerate job is processed the next time pin_rerate is run."

But when the rerate job, having multiple accounts, is rerated, the job status (/job/rerate) is not changed to completed (4) and there is no NEW rerate job created (only with the failed accounts). It is also observed that status in PIN_FLD_RERATE_ACCOUNTS of job_batch (/job_batch/rerate) is not changed to failed/Rerated.


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