Folds in BRM 12 PS3 Not Applied in the Same Order as Before in 7.5 PS22
(Doc ID 2836243.1)
Last updated on JANUARY 27, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The fold behavior changed from Billing and Revenue Management (BRM) 7.5 to 12. In 7.5, the fold is applied first and then the grant happens. But in 12, the grant is happening first and then the fold is applying which is causing the grant to be zeroed out.
With Pricing configuration
1. fold to empty resource counter
2. cycle fee to grant resource got next cycle (e.g 500)
After upgrade to BRM 12PS03, the bucket is zero after running billing.
Like in 7.5, the bucket should be folded into 0 and the cycle fee should be granted 500 after billing.
The issue is because of default behavior of config_billing_delay parameter changed.
In 7.5, it is only as a cm pin.conf entry and it is disabled by default:
# By default, this configuration parameter is disabled, so the autobilling
# trigger is enabled. This is a system-wide parameter only.
#- fm_bill config_billing_delay 10
In 12, its available as a business parameter and it is enabled by default:
PARAM_NAME, PARAM_TYPE, PARAM_VALUE
config_billing_delay, 5, 0
The scenario is working with this parameter disabled. However, the user already have events been rated for a couple of months on the production system.
How to disable the parameter?
Or, is the warning only during rating of events, i.e. do not reset the parameter during rating?
Configuring Delayed Billing
By default, delayed billing is enabled. You can configure delayed billing by setting the ConfigBillingDelay parameter using the pin_bus_params utility. For information on this utility, see BRM Developer's Guide.
To use delayed billing, set ConfigBillingDelay to a value ranging from 1 to 27. The length of the billing delay interval must be shorter than one accounting cycle.
If you do not want use delayed billing, set ConfigBillingDelay to 0.
To disable delayed billing, set this parameter to -1. This is supported for backward compatibility.
You can change the value of ConfigBillingDelay at any time. However, after you begin rating events in a production database, do not reset this parameter. Doing so might cause database errors
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