Multiple SNRs Are Generated For Parallel Usage With Primary And Secondary MSISDN
(Doc ID 2934803.1)
Last updated on MARCH 15, 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
ACTUAL BEHAVIOR
-----------------------
Multiple (duplicate) Spending-Status-Notification-Request (SNRs) are generated for parallel usage with primary and secondary login during sub-operation type "UPDATE". That is, in a scenario when when using both logins simultaneously for rating, multiple SNRs are generated after all data has been depleted.
EXPECTED BEHAVIOR
-----------------------
Only one SNR notification each for primary and secondary login should be generated when they are in parallel active sessions.
STEPS
-----------------------
- Create account with a primary service
- Add secondary service
- Start usage with primary and secondary numbers in parallel
- After consuming all the data multiple SNRs are generated for primary and secondary service
- That is, two SNR notifications each for primary and secondary login numbers are generated
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 |