Last updated on JULY 25, 2011
Applies to:Oracle Communications Billing and Revenue Management - Version: 126.96.36.199.0
Information in this document applies to any platform.
Make RestrictResourceValidityToOffer = TRUE in the multi_bal instance of the /config/business_params object.
Steps to reproduce the issue:
- Create an account/service (say 12-May-2010) and purchase a product based on a purchase fees event containing a balance impact that starts on first usage and ends on relative one month after first usage.
When purchasing the first usage product in Customer Center you need to set end dates for purchase, cycle, usage to 14-June-2010.
- Rate a CDR on 17-May-2010 that will impact the bundle related to first usage resource. Check is the output notification file was generated.
- Load the previous notification file with UEL, for example:
uel -t FirstUsageResources -v notif_FU.out
Verify the resource valid_to date and see that it is wrongly set to 17-June instead of 14-June.
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