Cycle, Purchase, Usage End Dates Of 'purchased_discount' Are Changing During Suspension (Doc ID 1589372.1)

Last updated on OCTOBER 28, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On :  BRM 7.5.0.4.0 version, Subscription Management

It is seen that the Cycle, Purchase, Usage end dates of /purchased_discount object are changing during suspension, for purchased discount having a set validity.


Scenario:

  1. Create an account on Jun 1st, 2014
  2. Create the service on Jun 1st, 2014 with product and discount by giving relative start and end dates for Cycle, Purchase, Usage dates fields using OFFSET and UNIT fields . After creating the service, below are the start and end dates for /purchased_discount:

    PIN_FLD_PURCHASE_START_T TSTAMP [0] (1401548400) Sun Jun 1 00:00:00 2014
    PIN_FLD_CYCLE_START_T TSTAMP [0] (1401894000) Thu Jun 5 00:00:00 2014
    PIN_FLD_USAGE_START_T TSTAMP [0] (1401548400) Sun Jun 1 00:00:00 2014

    PIN_FLD_PURCHASE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014
    PIN_FLD_CYCLE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014
    PIN_FLD_USAGE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014

  3. On Jun 1st, 2014, that is, inactivate the product and discount using  PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS and PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS
  4. PIN_FLD_PURCHASE_END_T, PIN_FLD_CYCLE_END_T and PIN_FLD_USAGE_END_T of /purchased_discount are changing incorrectly as shown below:

    PIN_FLD_PURCHASE_END_T TSTAMP [0] (1401548400) Sun Jun 1 00:00:00 2014
    PIN_FLD_CYCLE_END_T TSTAMP [0] (1401548400) Sun Jun 1 00:00:00 2014
    PIN_FLD_USAGE_END_T TSTAMP [0] (1401548400) Sun Jun 1 00:00:00 2014

  5. Also note that these values are not modified ( as expected ) for purrchased_product


Expected behavior:

The expectation is that in the step 4, the timestamps should be:

PIN_FLD_PURCHASE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014
PIN_FLD_CYCLE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014
PIN_FLD_USAGE_END_T TSTAMP [0] (1404140400) Tue Jul 1 00:00:00 2014

That is, the end dates should not change from 1 July to 1 June. This issue is for PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS and it is working ok for PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS.

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