Balance Bucket Validity Is Rounding to Midnight for Recurring Products
(Doc ID 3026762.1)
Last updated on JUNE 14, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Goal
While trying to create 4-hour validity products in an upgraded BRM (BRM 12 PS 8) environment, the balance validity start time is rounding to 00:00:00 hours.
The following configuration works fine for one-time purchase products but does not work for cycle-forward products.
Cycle product configuration (which does not need rounding):
It is known that the parameter "timestamp_rounding_for_purchase_grant" is applicable only for purchase_fee events ("/event/billing/product/fee/purchase").
Hence, as per design with the above configuration, the timestamps will be rounded for recurring events and add-on products.
If the need is to round the timestamp for a specific product, customization has to be done in the pol_post_rating policy opcode to set the valid_from to event end_t.
How do you achieve not rounding the balance validity timestamps for cycle-forward products by using flexible proration options?
Solution
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
Goal |
Solution |
References |