Discount Event Pointing to Current Month after Plan Change (Doc ID 3050754.1)

Last updated on OCTOBER 14, 2024

Applies to:

Symptoms

Issue is that during backdated account modification or plan changes, product level charges are showing correct mapping with correct bill object, but for discount it is mapping with current month bill_obj_id0 which is incorrect.

Scenario:

• created Charge Offer, cycle forward arrear event, impact is 100$, created bundle and package
• created Discount Offer, cycle forward arrear event, impact is 20% of charge, created bundle
• config_billing_delay = 27
• pin_virtual_time (PVT) 01-June-2024
• create backdated account with activation date 28-May-2024 along with purchase of the charge offer
• purchase the 20% discount backdated to 28-May-2024
• run pin_cycle_fees
  [pin_billd]$ pin_cycle_fees -regular_cycle_fees -verbose
• PVT: 20-June-2024
• cancel the purchased Charge Offer (purchased at account creation) backdated to 28-May-2024
• cancel discount backdated to 28-May-2024
• purchase deal (same Charge Offer) backdated to 28-May-2024 on same account
• See events generated:
   AMOUNT EVENT_TYPE
   100 /event/billing/product/fee/cycle/cycle_forward_arrear 
   12.9 /event/billing/product/fee/cycle/cycle_forward_arrear
  (one event is for 28May to 1June, another event for 1June to 1July)
• purchase the 20% discount backdated to 28-May-2024 on same account
• see event generated:
  -22.58 /event/billing/product/fee/cycle/cycle_forward_arrear
• see robj of above event poid, see that one long cycle is charged from May 28 to Jul 1, and the event is pointing to item 7413670 which is for June cycle:
  
  ...............

  0 PIN_FLD_CYCLE_INFO SUBSTRUCT [0] allocated 20, used 5
  1 PIN_FLD_CYCLE_END_T TSTAMP [0] (1719817200) Mon Jul 1 00:00:00 2024
  1 PIN_FLD_CYCLE_START_T TSTAMP [0] (1716879600) Tue May 28 00:00:00 2024
  1 PIN_FLD_FLAGS INT [0] 262152
  1 PIN_FLD_ORIGINAL_SCALE DECIMAL [0] 1
  1 PIN_FLD_SCALE DECIMAL [0] 1.1290322580645
  0 PIN_FLD_CYCLE_DISCOUNTS ARRAY [0] allocated 20, used 6
  1 PIN_FLD_CYCLE_END_T TSTAMP [0] (1719817200) Mon Jul 1 00:00:00 2024
  1 PIN_FLD_CYCLE_START_T TSTAMP [0] (1716879600) Tue May 28 00:00:00 2024
  1 PIN_FLD_DISCOUNT_OBJ POID [0] 0.0.0.1 /discount 2485041 1
  1 PIN_FLD_FLAGS INT [0] 9
  1 PIN_FLD_OFFERING_OBJ POID [0] 0.0.0.1 /purchased_discount 7407189 0
  1 PIN_FLD_SCALE DECIMAL [0] 1

• validate using below:
  select poid_id0,bill_obj_id0,due from item_t where account_obj_id0= 7410404;
  7413670 7412196 177.42
  7410660 7410148 0
  7412708 7412196 0
  7410708 7410148 25.8
• select poid_id0,start_t from bill_t where account_obj_id0= 7410404;
  7410148 28-MAY-24 12:30:00
  7412196 01-JUN-24 12:30:00
• Expected result: There should be two discount events, one for 28May to 1June, another for 1June to 1July, and they should point to corresponding items of may and june bill cycle

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.