Incorrect Handling Of Discount Version
(Doc ID 2110533.1)
Last updated on NOVEMBER 15, 2022
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.5.0.10.0 version, Pipeline Manager
Actual Behavior:
Pipeline doesn’t consider the timestamp in Discount version.
Expected Behavior:
Pipeline should consider the timestamp also while applying discounts.
Scenario:
1. Load discount model ‘TestSysDisc’ using LoadIfwConfig
LoadIfwConfig -v -u -c –I TestSysDisc.xml
2. Restart discounting pipeline
Note: The discount model has 3 versions
o Version#1 valid from ‘2015-01-01T00:00:00’ gives 10% discount
o Version#2 valid from ‘2015-02-01T10:00:00’ gives 20% discount
o Version#3 valid from ‘2015-03-01T00:00:00’ gives 30% discount
3. Load discount object ‘TestSysDisc’ system discount on /account
loadpricelist -v -f -c TestSysDiscObj.xml
Steps:
1. pvt -m1 020100002015
2. create account with any plan
3. check the discount bal impact
• Expected result version#1 (10% discount) should be applied
• Actual result version#2 got applied
0 PIN_FLD_BAL_IMPACTS ARRAY [0] allocated 20, used 16
1 PIN_FLD_IMPACT_CATEGORY STR [0] "20_off_Disc"
1 PIN_FLD_AMOUNT DECIMAL [0] -2
1 PIN_FLD_QUANTITY DECIMAL [0] 10
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 |