My Oracle Support Banner

Updating Position With Datetrack to SYSDATE+1 Sets Expiration_date to SYSDATE (Doc ID 1443612.1)

Last updated on SEPTEMBER 30, 2019

Applies to:

Oracle Human Resources - Version 12.1.2 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
If a date track change exists on a position with effective start date =
system date +1, PQH_POS_ROLES.expiration_date is set to SYSDATE.

then for any transaction submitted on system date requiring approval from
that position, then AME is not able to find the that position.

EXPECTED BEHAVIOR
-----------------------
If there is a future dated change for the position,
PQH_POS_ROLES.expiration_date should not be set to SYSDATE.

STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Navigate to 'US HRMS Manager' -> Work Structures -> Position ->
Description
2. Find a Active Position.
3. DateTrack to SYSDATE+1
4. Make a change to the position (Example: Increase the Headcount under
Hiring Information Tab).
5. Save.
6. Check PQH_POS_ROLES.Expiration_date shows SYSDATE NOT '31-Dec-2047'
7. Also as WF_LOCAL_ROLES depends on PQH_POS_ROLES table,
WF_LOCAL_ROLES.Expiration_date shows SYSDATE making the same position
record unavailable in wf_roles view.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, When there is future dated change exits for a position,
the same position is not available in wf_roles table making AME unable to
find the position hierarchy. The expense claims are not going to the
managers.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

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