First Usage Restrictresourcevaliditytooffer Not Working

(Doc ID 1328838.1)

Last updated on JULY 25, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0 and later   [Release: 7.3.0 and later ]
Information in this document applies to any platform.

Symptoms

Regarding First Usage resource validity feature, configured BRM to automatically restrict the validity period of granted resources to end no later than the end time of the product or discount that grants the resource. Restricting the resource end time to the product end time ensures that the resource cannot continue to be consumed after the first usage option validity expires. This is useful when the call that activates first usage option arrives closed to the end of validity period.

Make RestrictResourceValidityToOffer = TRUE in the multi_bal instance of the /config/business_params object.

Steps to reproduce the issue:
  1. 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.

  2. 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.

  3. 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.


Cause

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