Discounting Discrepancies due to PIN_FLD_STR_VAL Value in Purchased Discount (Doc ID 2533640.1)

Last updated on AUGUST 27, 2023

Applies to:

Symptoms

Even though purchase discount has proper usage_start_t/purchase_start_t/cycle_start_t values, discounting module is checking the value in PIN_FLD_STR_VAL field, and it is calculating discount based on timestamp present in PIN_FLD_STR_VAL value.

What is the purpose of this field and why it is being referred in discounting?

The purchase discount robj:
=====================
0 PIN_FLD_POID POID [0] 0.0.0.1 /purchased_discount 214725609 4
0 PIN_FLD_CREATED_T TSTAMP [0] (1521027642) Wed Mar 14 13:40:42 2018
0 PIN_FLD_MOD_T TSTAMP [0] (1523633212) Fri Apr 13 17:26:52 2018
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 25468535 0
0 PIN_FLD_CYCLE_END_DETAILS INT [0] 2
0 PIN_FLD_CYCLE_END_T TSTAMP [0] (0)
0 PIN_FLD_CYCLE_START_DETAILS INT [0] -2142105084
0 PIN_FLD_CYCLE_START_T TSTAMP [0] (1523570400) Fri Apr 13 00:00:00 2018
0 PIN_FLD_DESCR STR [0] "In RSA"
0 PIN_FLD_DISCOUNT_OBJ POID [0] 0.0.0.1 /discount 843864 0
0 PIN_FLD_EFFECTIVE_T TSTAMP [0] (1523633206) Fri Apr 13 17:26:46 2018
0 PIN_FLD_FLAGS INT [0] 0
0 PIN_FLD_INSTANTIATED_T TSTAMP [0] (1520978400) Wed Mar 14 00:00:00 2018
0 PIN_FLD_PLAN_OBJ POID [0] 0.0.0.1 /purchased_bundle 214728681 0
0 PIN_FLD_PURCHASE_END_DETAILS INT [0] 2
0 PIN_FLD_PURCHASE_END_T TSTAMP [0] (0)
0 PIN_FLD_PURCHASE_START_DETAILS INT [0] 516
0 PIN_FLD_PURCHASE_START_T TSTAMP [0] (1520978400) Wed Mar 14 00:00:00 2018
0 PIN_FLD_QUANTITY DECIMAL [0] 1
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/DedicatedInternetAccess 25573615 0
0 PIN_FLD_STATUS ENUM [0] 1
0 PIN_FLD_STATUS_FLAGS INT [0] 0
0 PIN_FLD_STR_VAL STR [0] "1#1552514400"
0 PIN_FLD_USAGE_END_DETAILS INT [0] 2

Here, str_val field has timestamp 1552514400, i.e. Mar 14 00:00:00 SAT 2019, and the discount has also being applied from Mar 14 - Mar25 instead Feb 25 - Mar 25.

STEPS
-----------------------
1. Whenever a discount is purchased, the system will add one year to cycle_start_t since implementation team will take some time not more than a year to activate service on the network.
    So, the event cycle_start_t set as 16-Apr-2019. Also same value present in PIN_FLD_STR_VAL.

2. Now whenever services activated on the network, then Implementation team will enter a billing start date in the system then cycle_start_t will be updated.
    In this scenario, it is 11-Jul-2018. Refer PIN_FLD_ACTION_INFO array 1 of above event.

3. The value in PIN_FLD_STR_VAL is "1#1555365600", Remove 1# it is 1555365600 i.e Tue Apr 16 00:00:00 SAT 2019.
    So, in April 2019, bill cycle While discounting even though cycle_start_t is from 11-Jul-2018 for this month, it is considering cycle from 16-Apr-2019 which is not expected.

Cause

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