Incorrect Behavior Of Discounts When It is Backdate Activated and Then Deactivated (Doc ID 2367207.1)

Last updated on AUGUST 31, 2023

Applies to:

Symptoms

Subscription Management shows incorrect behavior of discounts (dates) when one deactivates offer (which was backdate activated).

STEPS TO REPRODUCE:

1. create prod p1 = /service/ip , session event , 1$/min , create deal with name 'deal_prod'
2. create disc d1 = /service/ip , session event , 10% OFF for example ( not relevant ), d1->Detailed Discount Info->chose 'Full Discount' in all options
3. create deal deal_disc with d1.
4. PVT 2017-09-19, Create account (BDOM=21), create service , back dated 20 June. [PCM_OP_CUST_COMMIT_CUSTOMER + PCM_OP_CUST_MODIFY_CUSTOMER] [BDOM = Billing Day of Month]
5. PVT 2017-09-19, purchase  deal_prod (back dated activation from 2017-06-21 ). [PCM_OP_SUBSCRIPTION_PURCHASE_DEAL]
6. PVT 2017-09-19, Change BDOM from 21 to 24. [PCM_OP_CUST_SET_BILLINFO]
7. PVT 2017-09-22, Billing using pin_bill_accts
8. PVT 2017-09-22, Change BDOM from 24 to 26. [PCM_OP_CUST_SET_BILLINFO]
9. PVT 2017-09-22, Billing  using pin_bill_accts
10. PVT 2017-09-25, purchase deal_disc back dated activation from 2017-06-21 [PCM_OP_SUBSCRIPTION_PURCHASE_DEAL]
11. PVT 2017-09-25, deactivation of discount d1 back dated to 2017-07-21. [PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO]
    Here the problem is that the dates of discount , PIN_FLD_USAGE/CYCLE/PURCHASE_START_T, PIN_FLD_USAGE/CYCLE/PURCHASE_END_T
    (2017-05-24 to 2017-07-24) are different than the dates of activation and deactivation (2017-06-21 to 2017-07-21).

EXPECTED BEHAVIOR:

Dates of discount PIN_FLD_USAGE/CYCLE/PURCHASE_START_T, PIN_FLD_USAGE/CYCLE/PURCHASE_END_T (2017-05-24 TO 2017-07-24) should be same as dates of activation and deactivation (2017-06-21 TO 2017-07-21).

Changes

There are no recorded changes in the account, environment or product that could trigger the issue.

Cause

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