Incorrect Char Value Used While Billing
(Doc ID 2379535.1)
Last updated on SEPTEMBER 20, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.4.0.3.0 to 2.4.0.3.0 [Release 2.4]Information in this document applies to any platform.
Symptoms
On : 2.4.0.3.0 version, BI - Billing
Incorrect char value used while billing
Char Type used at Calc. rule, is not considering the char value, which is effective from Bill segment start date.
Steps to reproduce:
1. While billing, system considers the effective Char value at SP for the bill segment start date.
Char value used at Bill factor: MSNPU
Char value used at calculation rule: TRNFU
Rate:
2. Bill segment period: 09-11-2017 - 10-11-2017
Start date: 09-12-2017
Scenario 1:
Both SP chars effective from 09-11-2017
3. Calculations:
MSNPU char value – 2 => $28.70
28.70*2 = $57.40
Passed
4. Scenario 2:
MSNPU (Bill Factor char) effective from 09-12-2017
TRNFU (Calc. Rule char) effective from 09-11-2017
5. Bill segment period: 09-11-2017 - 10-11-2017
Start date: 09-12-2017
Calculations:
MSNPU char value – 2 => $28.70
28.70*2 = $57.40
Passed
6. Scenario 3:
MSNPU (Bill Factor char) effective from 09-11-2017
TRNFU (Calc. Rule char) effective from 09-12-2017
7. Bill segment period: 09-11-2017 - 10-11-2017
Start date: 09-12-2017
Calculations:
MSNPU char value – 2 => $28.70
28.70*2 = $57.40
Failed
Issue:
Char used at Calc. rule (TRNFU char) is not considering the char value, which is effective from Bill segment start date (09-12-2017), which is incorrect. Whereas char used at Bill factor (MSNPU char) is considering the char value, which is effective from Bill segment start date (09-12-2017), which is correct.
8. Scenario 4:
MSNPU (Bill Factor char) effective from 09-12-2017
TRNFU (Calc. Rule char) effective from 09-12-2017
9. Bill segment period: 09-11-2017 - 10-11-2017
Start date: 09-12-2017
Calculations:
MSNPU char value – 2 => $28.70
28.70*2 = $57.40
Failed
Issue:
Char used at Calc. rule (TRNFU char) is not considering the char value, which is effective from Bill segment start date (09-12-2017), which is incorrect. Whereas char used at Bill factor (MSNPU char) is considering the char value, which is effective from Bill segment start date (09-12-2017), which is correct.
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 |