Rerating Applying Charges Exceeding The Credit Limit Set On The Subscriber's Resources
Last updated on MARCH 15, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
Observed in the CM logs that the fm_rate_and_discount_event.c source code is specifically setting 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. It causes rerating to apply charges that exceed the credit limits set on 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 check for credit limits during rerating? Is this a behavior that can be modified through simple configuration?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms