One Second Discount/Product Got Set with a Wrong Validity End Date (Doc ID 2938633.1)

Last updated on APRIL 12, 2024

Applies to:

Goal

 After upgrade from Billing and Revenue Management (BRM) 7.5 to 12.0 Patch Set 5, the product and discount configurations are also migrated.

The user encounters a case in which a discount/product with one second validity has a wrong purchase_end_t and usage_end_t after the bundle which contains these discounts/products is activated.

--------------------------------correct dates----------------------------------------------------
0 PIN_FLD_USAGE_END_T TSTAMP [0] (1677167373) Thu Feb 23 17:49:33 2023
0 PIN_FLD_USAGE_START_T TSTAMP [0] (1677167372) Thu Feb 23 17:49:32 2023
------------------------------------------------------------------------------------------

timestamp_rounding seems to round the date, but it should not because is on 0.

The user does not set flag prorateCycle to PRORATE, but it can be seen that from the exported bundle that <prorateCycle>PRORATE_CHARGE</prorateCycle> is set. In PDC for BRM 7.5, this is not present.
Usage Purchase discount is also set to FULLDISCOUNT.

-------------------------------------------wrong dates--------------------------------------------------
discount_validity_dates write input flist
0 PIN_FLD_PURCHASE_START_T TSTAMP [0] (1677103200) Thu Feb 23 00:00:00 2023
0 PIN_FLD_PURCHASE_END_T TSTAMP [0] (1679522400) Thu Mar 23 00:00:00 2023

The expectation is that the purchase_end_t - purchase_start_t = 1 sec. Why is the purchase_end_t set to a month out?

Solution

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