IMPACT_CATEGORY Coming As Null For The Rerated Events
(Doc ID 2918947.1)
Last updated on JANUARY 03, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.0.0.4.0 version, Rating
ACTUAL BEHAVIOR
---------------
IMPACT_CATEGORY coming as null for the rerated events
It is observed that the backout event is having event_bal_impacts_t.impact_Category field populated whereas the rerated new charge event was having event_bal_impacts_t.impact_Category field populated as null.
The issue can be reproduced at will with the following steps:
We are in BRM-PDC-ECE setup and we have a invoice structure based on the impact category values for the usage data.
The usecase is as follows:
1) Create an account .
2) Create a service with /event/delayed/session/telco event.
3) Rate a usage in the account through OCOMC-ECE-BRM
4) Usage rated in BRM and event_bal_impacts_t.impact_Category field is populated with the specific impact_Category.
5) Rerate the account using pin_rerate -r -a <account_number>> -n event.txt -t 07/01/2022
6) The unbilled usage were rerated and event_bal_impacts_t table was populated with 2 entries - one for the backout of the existing usage event and other for the rerated charge.
It is observed that the backout event is having event_bal_impacts_t.impact_Category field populated whereas the rerated new charge event was having event_bal_impacts_t.impact_Category field populated as null.
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 |