ERS 9.1+: Modifying Employee Leave Of Absence Job Data Effective Date Not Recalculating PS_RS_MEMBER_DATES.START_DATE For Unassigned Pool (Doc ID 1673418.1)

Last updated on MARCH 16, 2016

Applies to:

PeopleSoft Enterprise FIN Resource Management - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

Whenever an Employee that has been established as a Resource is being set from Active Status to a non-Active status, such as Leave Of Absence, using an effective date value in the past, the system calculates the End Date from the Resource's current Pool ID (PS_RS_MEMBER_DATES.END_DATE), and automatically transfers the Employee to the Unassigned Pool ID (0000000001), where it stores the Resource with a Start Date equal to the previous Pool ID End Date + 1 day. The issue that Defect # 14323063  reported has been fixed in PeopleSoft Enterprise FSCM 9.1 ESA Bundle #24.

However, upon further testing, a new sub-scenario has been found to still be faulty. This involves if by means of the Correction History Mode, a user modifies the Effective Date value from the Employee's Job Data row where it got set to a value other than 'Active', such as 'Leave Of Absence'. While the original Pool ID PS_RS_MEMBER_DATES.END_DATE Record Field gets properly updated with the newly modified Effective Date value, the target Unassigned Pool ID does not get its PS_RS_MEMBER_DATES.START_DATE Field value corrected to match the End Date + 1 day. As a result, the system creates an inconsistency in the data stored for that Resource.

REPLICATION STEPS:

    - Log with User ID VP1 into a PeopleSoft Enterprise FSCM 9.1 Online Application patched at least up to ESA Bundle #24
    - Navigate to: Resource Management > Manage Resource Pools > Pool Resources.
    - Open Resource Pool ID 0000000009 (Global Info Technology).
    - Find Employee ID RS00000003 (Armand Falkner) listed with no End Date value.
    - Navigate to: Resource Management > Establish Resources > Update Employee Data.
    - Open Employee ID RS00000003.
    - Go to the Employee Job tab, and create a new effective dated row dating from December 31st 2013 (a date in the past).
    - Set the Employee Status to 'Leave Of Absence' and save the changes.
    - Navigate to: Resource Management > Manage Resource Pools > Pool Resources.
    - Open Resource Pool ID 0000000009 (Global Info Technology).
    - Click on the Pool History link.
    - See listed the Employee ID RS00000003 (Armand Falkner) listed with an End Date value of December 30th 2013.
    - Query the table PS_RS_POOL_MEMBERS for EMPLID = 'RS00000003', and see how it has 2 entries, one for the initial Pool the Employee was until now working on (0000000009 Global Info Technology), and the new one that has been transferred since the change of Employee Status (Pool ID 0000000001 Unassigned).
    - Query also PS_RS_MEMBER_DATES record, for POOL_ID = '0000000001' (Unassigned), and find the Member ID 48, corresponding to Employee ID RS00000003 (Armand Falkner), and see a Start Date of December 31st 2013, and an End Date of Null.
    - Navigate to: Resource Management > Establish Resources > Update Employee Data.
    - Open Employee ID RS00000003.
    - Go to the Employee Job tab, and in Correct History Mode, change the Effective Date field value of the new row we created from December 31st 2013 to December 29th 2013 instead.
    - Leave all the rest as it is, and proceed to save the changes.
    - Query PS_RS_MEMBER_DATES record, for POOL_ID = '0000000009' (Global Info Technology), and find the Member ID 9, corresponding to Employee ID RS00000003 (Armand Falkner), and see an End Date of December 28th 2013, where before we had December 30th 2013. This is correct.
    - Query again PS_RS_MEMBER_DATES record, for POOL_ID = '0000000001' (Unassigned), and find the Member ID 48, corresponding to Employee ID RS00000003 (Armand Falkner), and see a Start Date of still December 31st 2013, while it should now be December 29th 2013. There is now an inconsistency of data, which is wrong.

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

BUSINESS IMPACT:

In the system, the affected Resource is not pertaining to any Resource Pool for the period of time that lies in between the original Effective Date value of the Employee's 'Leave Of Absence', and the newly Effective Date value that was corrected. This is inconsistent with the delivered design of the intended functionality. Any Resource Search performed between that affected period would not show the Resource as potential candidate.

EXPECTED BEHAVIOR:

If the Resource has to be automatically transferred to the Unassigned Resource Pool upon setting it Inactive or In-Eligible For Staffing, then at least the Start and End Dates should be consistent at all times, no matter if the Employee Job Data got modified once, or it got later on corrected by modifying existing history rows.

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