Rerating Applying Charges Exceeding Credit Limit Set in Subscriber Resources
(Doc ID 1991903.1)
Last updated on APRIL 08, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
The fm_rate_and_discount_event.c source code has specifically set the PIN_FLD_CHECK_CREDIT_LIMIT field to 0 during rerating before passing the event to the real-time Discounting Pipeline; thus, it is indicating not to check for credit limits. This causes rerating to apply charges that exceed the credit limits set in the subscriber's resources.
As a workaround, the user has implemented a custom iScript in the real-time Discounting Pipeline in order to force the credit limit check by setting the DETAIL.CREDIT_LIMIT_CHECK field to 1.
Is there a specific reason to set this PIN_FLD_CHECK_CREDIT_LIMIT field to 0 and not to check for credit limits during rerating?
Is this a behavior that can be modified through simple configuration?
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