Certain Impact Categories Were Incorrectly Rated By Pipeline
(Doc ID 1429254.1)
Last updated on MARCH 07, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]Information in this document applies to any platform.
Symptoms
DESCRIPTION
-----------------
Pipeline rated calls for few of the premium SMS destinations strangely (Not as per the PriceModel Configured) with a different charge than the one configured in the pricemodel for a certain period(between two restarts).Customer got to know after the revenue assurance team reported the discrepancies. Later verified the issue from billing and have the following observations.
1. The product used for rating was the same but the usage was rated with 1$ rather than the configured rates(3$).
2. Though the rate was incorrect, the GL was matching as provided in the pricemodel.
3. This happened system wide and not just for certain accounts.
4. These pricemodels were not modified during that period.
5. For the product/rateplan, there is only one version which has configuration for this impact_category.
6. This incorrect rating started happening after a pipeline restart which subsequently stopped after the next restart.
ACTUAL BEHAVIOR
--------------------
Pipeline rated calls for few of the premium SMS destinations strangely with a different charge than the one configured in the pricemodel for a certain period(between two restarts).
EXPECTED BEHAVIOR
-----------------------
Calls should be charged as per the PriceModel configured.
BUSINESS IMPACT
-----------------------
Due to this issue, The events were wrongly charged.
-----------------------
Due to this issue, The events were wrongly charged.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |