In-Session Threshold Notifications Are Not Triggered For Shared Resource
(Doc ID 2183292.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version
In-session PIGGYBACK NOTIFICATIONS are not being generated for Threshold breach of Shared resource during PCM_OP_TCF_AAA_AUTHORIZE and PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE.
We have a Payee account and subscription Account structure. The payee account is Discount sharing owner and Subscription account is member of it. For example, a "5GB" plan was purchased at payee account under /service/telco which grants 5GB of Data and also contains discount object "Shared Data Discount" (Owner). We have set the Fixed thresholds at 80% and 100% i.e -1024 MB and 0.
Example: Current Bucket value is - 1387 MB, Subscription unit has requested the authorization for 512 MB which breaches the -1024 MB threshold limit. Authorization was successful and 512 MB was reserved for the resource but PIGGYBACK notifications are not generated.
Pass the Stop accounting request for the same reserved amount that is 512 MB , and Notification was generated.
Expectation: In session Piggyback Notifications should be generated for the share resource.
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