Pin_state_change Utility is Not Setting State_Expiration Timestamp to 00:00 Hours (Doc ID 2687697.1)

Last updated on MAY 29, 2024

Applies to:

Symptoms

While testing on 12.0.0.2.0 version, it has been observed that when pin_state_change utility is run for changing life cycle from one state to another as per configurations, STATE_EXPIRATION_T of service_t is calculated from the current timestamp and set but not rounded to the date. So when pin_state_change is run at 01-Jan 0400 Hour for example and default configuration to next state is set as 30 days, then state expiration is getting set as 30-Jan 0400 Hours instead of 30-JAN 0000 Hours.

STEPS
-----------------------
Execute the pin_state_change utility for the targeted accounts and observe that time is not around for the validity of state change.

ACTUAL BEHAVIOR
-----------------------
Pin_state_change utility is not setting state_expiration timestamp to 00:00 HR and it is picking the utility execution time stamp.

EXPECTED BEHAVIOR
-----------------------
Pin_state_change utility should set the state_expiration timestamp to 0:00 HR irrespective of the utility run time.


BUSINESS IMPACT
-----------------------
Due to this issue, system is providing additional hours/day for the customer to stay in a particular state and this would impact the business logic across systems. Technically, it is an overhead to run the pin_state_change utility daily multiple times and also dates are not aligned as per other dates like purchase, billing etc. It might also impact regulatory requirements in the country.

Changes

Cause

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