Future Cycle Purchases with PCM_OP_SUBSCRIPTION_PURCHASE_FEES Did Not Have A Balance Impact (Doc ID 1263002.1)

Last updated on JULY 14, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.
*** Checked for relevance on 29-Mar-2013 ***

Symptoms

Consider this scenario:

  1. Create account on 1st June.
  2. Purchase a deal (event type /event/billing/product/fee/purchase) with pcm_op_subscription_purchase_deal opcode by setting the value 2nd July to cycle_start_t, purchase_start_t, usage_start_t (input flist as below).

    op_subscription_purchase_deal input flist
    # number of field entries allocated 20, used 5
    0 PIN_FLD_DEAL_INFO SUBSTRUCT [0] allocated 20, used 13
    1        PIN_FLD_POID POID [0] 0.0.0.1 /deal 25334564493 0
    1        PIN_FLD_CREATED_T TSTAMP [0] (1190295136) Thu Sep 20 15:32:16 2007
    1        PIN_FLD_MOD_T TSTAMP [0] (1190295136) Thu Sep 20 15:32:16 2007
    1        PIN_FLD_READ_ACCESS STR [0] "B"
    1        PIN_FLD_WRITE_ACCESS STR [0] "S"
    1        PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 1 0
    1        PIN_FLD_DESCR STR [0] "Test"
    1        PIN_FLD_END_T TSTAMP [0] (0) <null>
    1        PIN_FLD_FLAGS INT [0] 0
    1        PIN_FLD_NAME STR [0] "Test"
    1        PIN_FLD_PERMITTED STR [0] "/account"
    1        PIN_FLD_START_T TSTAMP [0] (0) <null>
    1        PIN_FLD_PRODUCTS ARRAY [0] allocated 20, used 20
    2               PIN_FLD_CYCLE_DISCOUNT DECIMAL [0] 0
    2               PIN_FLD_CYCLE_END_DETAILS INT [0] 1
    2               PIN_FLD_CYCLE_END_T TSTAMP [0] (0) <null>
    2               PIN_FLD_CYCLE_START_DETAILS INT [0] 1
    2               PIN_FLD_CYCLE_START_T TSTAMP [0] (87001) Fri Jan 02 01:10:01 1970
    2               PIN_FLD_PRODUCT_OBJ POID [0] 0.0.0.1 /product 25334564649 0
    2               PIN_FLD_PURCHASE_DISCOUNT DECIMAL [0] 0
    2               PIN_FLD_PURCHASE_END_DETAILS INT [0] 1
    2               PIN_FLD_PURCHASE_END_T TSTAMP [0] (0) <null>
    2               PIN_FLD_PURCHASE_START_DETAILS INT [0] 1
    2               PIN_FLD_PURCHASE_START_T TSTAMP [0] (87001) Fri Jan 02 01:10:01 1970
    2               PIN_FLD_QUANTITY DECIMAL [0] 1
    2               PIN_FLD_STATUS ENUM [0] 1
    2               PIN_FLD_STATUS_FLAGS INT [0] 16777216
    2               PIN_FLD_USAGE_DISCOUNT DECIMAL [0] 0
    2               PIN_FLD_USAGE_END_DETAILS INT [0] 1
    2               PIN_FLD_USAGE_END_T TSTAMP [0] (0) <null>
    2               PIN_FLD_USAGE_START_DETAILS INT [0] 1
    2               PIN_FLD_USAGE_START_T TSTAMP [0] (87001) Fri Jan 02 01:10:01 1970
    2               PIN_FLD_PURCHASE_FEE_AMT DECIMAL [0] 11
    0 PIN_FLD_POID POID [0] 0.0.0.1 /account 39335324536 14
    0 PIN_FLD_DESCR STR [0] "Test Cancel OCC"
    0 PIN_FLD_END_T TSTAMP [0] (1246399199) Tue Jun 30 23:59:59 2009
    0 PIN_FLD_PROGRAM_NAME STR [0] "Test" 

  3. The output of this opcode does not generate the balance impact. See output flist as below :

    op_subscription_purchase_deal return flist
    # number of field entries allocated 20, used 4
    0 PIN_FLD_POID POID [0] 0.0.0.1 /account 39335324536 14
    0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 3
    1        PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.0 0 0
    1        PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 39335324536 14
    1        PIN_FLD_POID POID [0] 0.0.0.1 /event/billing/product/action/purchase 253257149630735108 0
    0 PIN_FLD_PRODUCTS ARRAY [0] allocated 20, used 3
    1        PIN_FLD_PRODUCT_OBJ POID [0] 0.0.0.1 /product 25334564649 0
    1        PIN_FLD_OFFERING_OBJ POID [0] 0.0.0.1 /purchased_product 39335324932 0
    1        PIN_FLD_PACKAGE_ID INT [0] 16
    0 PIN_FLD_RESULTS ARRAY [1] allocated 20, used 2
    1        PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 39335324536 14
    1        PIN_FLD_POID POID [0] 0.0.0.1 /event/billing/deal/purchase 253257149630737156 0

  4. Call the pcm_op_subscription_purchase_fee opcode with start_t and end_t with July 2nd to generate the charge for the previous purchase. See below input flist :

    op_subscription_purchase_fees input flist
    # number of field entries allocated 20, used 4
    0 PIN_FLD_POID POID [0] 0.0.0.1 /account 39335324536 14
    0 PIN_FLD_PROGRAM_NAME STR [0] "Test"
    0 PIN_FLD_START_T TSTAMP [0] (1246486200) Thu Jul 02 00:10:00 2009
    0 PIN_FLD_END_T TSTAMP [0] (1246486200) Thu Jul 02 00:10:00 2009

  5. After the purchase_fee opcode call, it does not generate the bal_impact as expected. See below output flist; it does not have the event for the balance impact :

    op_subscription_purchase_fees return flist
    # number of field entries allocated 20, used 1
    0 PIN_FLD_POID POID [0] 0.0.0.1 /account 39335324536 14





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