Rerated Taxes Are Incorrect
(Doc ID 2862089.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.22.0 and laterInformation in this document applies to any platform.
Symptoms
The issue can be reproduced at will with the following steps:
Create account on 01/01/21 with commitment Charge Offer(amount 200) and paygo on shipto1 (owner) and paygo on shipto2(member)
Process Billing on 2nd Feb
Process Billing on 2nd March
Process Usage (10 march) (Overage is seen(Paygo usage more than commitment amount))
Process Billing on 2nd April
Process Change Order and update commitment amount to 400(true up should be generated after rerating)
Generate Bill
Run Rerating in two steps:
pin_rerate -t 04/01/2022 -a (member poid)
pin_rerate -process jobs
pin_rerate -process queue
pin_rerate -rerate
pin_rerate -process queue
pin_rerate -t 04/01/2022 -a (owner poid)
pin_rerate -process jobs
pin_rerate -process queue
pin_rerate -rerate
pin_rerate -process queue
ACTUAL BEHAVIOR
---------------
While executing the below scenario, it is observed that corrective bill dis not consider "/event/billing/cycle/tax" generated after re-rating. so corrective bill amount is not correct.
EXPECTED BEHAVIOR
-----------------------
/event/billing/cycle/tax event with item_poid_type as /item/adjustment should be included while generating corrective bill.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |