ERS 9.2: Open Assignments Created Under EMPL_RCD 0 Being Wrongfully Canceled By WORKFORCE_SYNC When Terminating EMPL_RCD 1 (Doc ID 2043832.1)

Last updated on MARCH 16, 2016

Applies to:

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

Symptoms

ISSUE:

For those Employees established as Resources in FSCM Resource Management module, who have multiple Job Instances, if any of them get Terminated in HRMS systems, the WORKFORCE_SYNC Service Operations delivered codeline will not only bring the latest data into Records PS_JOB and PS_EMPLOYMENT, but it will also automatically CANCEL any open and outstanding Assignments these Resources have, even if the Employee Job Instance used to create them differs than the one that has been Terminated. As a result:

  - The Assignment Status changes from ASSIGN to CANCEL
  - The Assignment's End Date gets updated to the Termination Date of the Job Instance that has been terminated
  - If the Assignment got created from a Service Order Line, the Service Order gets automatically re-opened for the Staffing Coordinators to find a suitable replacement

When a Resource in FSCM has multiple Job Instances (EMPL_RCD 0, 1, 2, etc...), the Resource Management module makes it compulsory to Select a Default Job Instance to be used in all Searches generated, and Assignments created. It does not make any sense that an unused Job Instance in FSCM Resource Management module has the potential effect of automatically closing all outstanding Assignments of the affected Resource.

REPLICATION STEPS:

 - Integrate a PeopleSoft Enterprise HRMS environment with a PeopleSoft Enterprise FSCM instance for PERSON_BASIC_SYNC and WORKFORCE_SYNC
 - In HRMS, create a new Employee ID GCS0001 with Effective Date January 1st 2010, and EMPL_RCD = 0
 - In FSCM, establish the new Employee ID GCS0001 as a Resource, with Job Record 0 as the default in Resource Management (RS) module
 - Create a new Project ID GCS_PROJECT, spanning from January 1st 2015, through December 31st 2015
 - Proceed to create a brand new Assignment for this Resource GCS0001, with Start Date of Today (as the Employee got established as a Resource from today onwards), and End Date of December 31st 2015
 - Back in HRMS, create a new Job Instance for the Employee, with EMPL_RCD = 1, on a different Department ID and Job Code, with an Effective Date of January 1st 2015
 - Still in HRMS systems, proceed to Terminate the new EMPL_RCD 1 Job Instance with an Effective Date of Today
 - Check in FSCM systems, and confirm how the Assignment ID created for the Employee ID GCS0001 using default Job Instance EMPL_RCD = 0 has been CANCELED with an End Date of Today

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:

The affected Assignment IDs are Canceled, and as such, cannot be re-opened again. The Staffing Coordinators will have to create brand new Assignments for each one wrongfully closed. This is affecting Billing revenues, adding extra unnecessary work to Staffing Coordinators, creating confusion among Resources who see their Assignments canceled for no apparent reason, and creating duplicate transactions when a new Assignment is to be created.

EXPECTED BEHAVIOR:

The WORKFORCE_SYNC Service Operations delivered codeline should know which EMPL_RCD Job Instance got Terminated, and affect only those open/ongoing Assignment IDs whose EMPL_RCD used when creating them has the same value (Record Field PS_ASSIGNMENT.EMPL_RCD_NUM). Therefore, leaving untouched those Assignment IDs created with a Job Instance that is not the one being Terminated.

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