Nonprorated Full Charge Rerated With Zero Amount
(Doc ID 2148011.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.13.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On : 7.5.0.12.0 version, Rerating/Rebilling
Actual Behavior:
On rerating, nonprorated full charge is backed out and zero amount appears.
Expected Behavior:
Full charge should be applied for each product.
Steps to reproduce:
1. pvt=01.08.2015 00:00:00
create Account
2. create Offer1 (package of products/discounts - not relevant for the scenario)
3. pvt=13.08.2015 02:00:00
create Offer2 (package of products/discounts - relevant for the scenario)
configuration detail for products:
rate_t.prorate_first = 701
rate_t.prorate_last = 701
rate_bal_impacts_t.flags = 0 or 1 or 8 i.e. non-proratable
Offer purchase relevant details (details are further propagated in /purchased_product objects)
start_t = 13.08.2015 00:00:00 (could be any day except of 01.08.2015 00:00:00 - i.e. the start of current period. otherwise the issue does not occur)
end_t = 01.09.2015 00:00:00 (the end of current period. in case this date is not set and default 0 is used, the issue does not occur)
Results: full charge is applied for each product with the above mentioned configuration wrapped within offer => CORRECT
4. Insert rerate request for the US with start_t = 31.07.2015 11:59:59
5. pvt=13.08.2015 03:00:00
execute pin_rerate -rerate
Results: charges generated in step 3 are backed-out and re-charged with 0 amount => INCORRECT
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 |