If Real-Time Rerating Fails, The New Job Rerate Object Can Not Be Customized
Last updated on JULY 27, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0]
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 18.104.22.168.0 version, if real-time rerating fails, the new job rerate object can not be customized.
Steps to reproduce:
- 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.
- Check a rerate object /job_batch/rerate is created
- Stop Realtime Pipeline
The idea is to make rerating fails. This ways a new rerate object is created.
- Run rerate:
pin_rerate -process jobs
pin_rerate -process queue
- 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.
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