If Real-Time Rerating Fails, The New Job Rerate Object Can Not Be Customized (Doc ID 1383701.1)

Last updated on JULY 27, 2017

Applies to:

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

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.3.0.0.0 version, if real-time rerating fails, the new job rerate object can not be customized.

Steps to reproduce:

  1. Create a rerate job by OOD (out-of-order rating).
    You need to customize op_subscription_pol_generate_rerate (PCM_OP_SUBSCRIPTION_POL_GENERATE_RERATE) to add a filter. This opcode is notified by /event/notification/activity/out_of_order event.

  2. Check a rerate object /job_batch/rerate is created

  3. Stop Realtime Pipeline
    The idea is to make rerating fails. This ways a new rerate object is created.

  4. Run rerate:
       pin_rerate -process jobs
       pin_rerate -process queue
       pin_rerate -rerate

  5. Check the new rerate job
    As rerate fails, a new rerate job is created. But this rerate job does not contain the same filters as the original one. The reason is that rerate does not call op_subscription_pol_generate_rerate.

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