Pin_discount_cleanup Sets End Times Of /purchased_discount To Sysdate

(Doc ID 1488455.1)

Last updated on AUGUST 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.1 [Release 7.3.0]
Information in this document applies to any platform.

Symptoms

On : 7.3.0.0.0 version, Purging

ACTUAL BEHAVIOR
---------------
pin_discount_cleanup utility sets purchase_end_t, cycle_end_t, usage_end_t values to sysdate.

EXPECTED BEHAVIOR
-----------------------
pin_discount_cleanup utility should not change purchase_end_t, cycle_end_t, usage_end_t values to current sysdate.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:

Example of Business scenario being impacted -

Customer had purchase_discount instance which have purchase_end_t (cycle_end_t, usage_end_t) set to 15. april 2011 and status was set to 0.

After execution of pin_discount_cleanup utility status was set to 3, but also purchase_end_t (cycle_end_t, usage_end_t) have been shifted to 20. july 2012.

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