Selective Rerating by Event Does Not Produce Correct Results (Doc ID 3062383.1)

Last updated on JANUARY 22, 2025

Applies to:

Symptoms

Rerating results are not ok in the selective rerating (by events) scenario explained below:

1. Created account on 01.Jun.2024, purchased charge offer with rating setup and charge offer with some free resources.
2. On 24.Jul.2024, rated usage at '24.Jul.2024 12:11:50' for duration 1200 seconds, with start_time '24.Jun.2024 17:00:00'. Rating is ok and free resources  are consumed ok which is expected for June.
3. Rated usage at '24.Jul.2024 12:14:28', with start_time '02.Jul.2024 12:00:00' for 2000 seconds duration (actual quantity rated is 2040, because rounding unit was 60 seconds). This triggered cycle forward which is ok, not consuming free resources.
4. Rated usage at '24.Jul.2024 12:14:40', with start_time '05.Jul.2024 13:00:00' for 16000 seconds duration (actual quantity rated is 16020), rating is ok and free resources consumed ok.
5. Rated usage at '24.Jul.2024 12:14:46', with start_time '06.Jul.2024 14:00:00' for 18000 seconds duration, rating is ok and free resources consumed ok.
6. Rated usage at '24.Jul.2024 12:14:52', with start_time '08.Jul.2024 12:30:00' for 14000 seconds duration, (rounding unit 60 seconds, so quantity rated is 14040), rating is ok and free resources consumed ok, and part of the duration is charged – this is also as expected.
7. Run selective rerating by event as follows:
   pin_rerate -r -n event.txt -t 07/01/2024
           (Note: event.txt contains just one event "/event/delayed/session/telco/gsm")
   pin_rerate -process jobs
   pin_rerate -process queue
   pin_rerate -rerate
   pin_rerate -process queue
   pin_rerate -process recycle
8. Actual result:
   • After the above rerating steps, on checking the balances and consumed/charged resources below observations/discrepancies were captured
   • The usage that was processed at 24.Jul.2024 12:14:28 is rerated and it has 2040 free resources consumed. This is OK. New adjustment is created which did backout the charged amount and adjustment that consumed free resources -2040 seconds.
   • The usage that was run at 24.Jul.2024 12:14:40, is impacted also by filer (the same event poid type), but here instead of consuming all resources (all 16020), free resources are consumed worth 2040 seconds and the rest is charged (13980 seconds). Why rerating did not consume all resources form this usage?
   • Usage at 24.Jul.2024 12:14:46, is impacted also by filer (the same event poid type), but here instead of consuming all resources (all 18000), free resources are consumed worth 4080 seconds and the rest is charged (13920 seconds). Why rerating did not consume all resources from this usage?
   • The last usage processed at 24.Jul.2024 12:14:52, was part charged and part consumed free resources before rerating. After rerating, the amount and free resources did backout, so this part was OK, but new resources used and calculated are not OK like the previous two usages. Here it is seen that free resources was consumed worth 8160 seconds, and the rest is charged (5880 seconds).
9. Expected:
   After rerating, free resources consumed should be worth seconds 2040 + 16020 + 18000 + 14040 = 50100, (and from this we minus 48000 available free resources), remaining 2100 seconds should be charged.

Cause

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