Realtime Rating Get Problem When A Service Is Set To Backdate Close (Doc ID 865923.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

The rerating result of a CDR event is not correct. The rerating result is the same as the original event.

Steps To Reproduce:

1. Pin_virtual_time is set to May 16.
2. Create an account with the OOB pricing plan "Standard GSM". There will be one cycle forward event and its balance is Euro=45, free seconds=3600
3. Adjust pin_virtual_time to May 21
4. Send the CDR1(start_t is on May 18) and use pin_rel load to BRM. The balance impact of CDR1 is:
Duration: 7200 seconds
Euro=7.2, free seconds=-3600
5. The current account balance is :
euro=52.2, free seconds=0
6. Adjust pin_virtual_time to May 23
7. Send CDR2 on May 22(start_t in on May 22) and use pin_rel load to BRM. The balance impact of CDR2 is:
Duration:=3600 seconds ; Euro=7.2
8. The current account balance is:
euro=59.4, free seconds=0
9. Do a back date close of the above service (backdate on May 20 00:00:00).
10. There will be the second cycle forward event created. Its balance impact is:
Euro=-45, free seconds=3600
11. Use pin_rerate to create an job which rerate all the event_t from May 20 00:00:00

pin_rerate -t 05/20/2011 -a 4448894
pin_rerate -process jobs
pin_rerate -process queue
pin_rerate -rerate
pin_rerate -process queue
pin_rerate -process recycle

Actual Result The rerating result is same as the original.

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