My Oracle Support Banner

EEX: Problem With WORKFORCE_SYNC Not Properly Updating Record Field PS_JOB.SUPERVISOR_ID For Reporting Employees After HRMS Change In Position Number From Manager (Doc ID 2620297.1)

Last updated on APRIL 21, 2020

Applies to:

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

Symptoms


In HRMS systems, the company is using Position Numbering functionality as organizational structure. As such, PS_JOB Record in FSCM systems gets updated in the following values when WORKFORCE_SYNC is triggered (among others):

  - PS_JOB.POSITION_NBR = Value of the Employees Position Number they hold in HRMS
  - PS_JOB.REPORTS_TO = Position Number value from the Manager of the Employee
  - PS_JOB.SUPERVISOR_ID = Employee ID value of the Manager holder the Position Number from REPORTS_TO

A problem has been detected though, when in HRMS, the Employee holder the Manager Position Number gets changed to another Position, and someone new gets assigned to the Manager's Position Number. While for the 2 affected Employees the changes are correctly brought into FSCM systems, for the Employee reporting to that Manager Position Number, nothing is changed, which should be OK, except for PS_JOB.SUPERVISOR_ID field, as the value of EMPLID has indeed changed.

Ensure that in FSCM systems, at least one of the below listed modules are selected/active (no need to have all of them):

  - Resource Management
  - Program Management
  - Maintenance Management
  - Staffing Front Office
  - Services Procurement

REPLICATION STEPS:

  1.- Enable Position Numbering in HRMS systems as the way to organize the structure of the Company
  2.- Define Position Numbers 111, 222, and 333. Each with a Job Code and valid settings
  3.- State that Position Number 111 reports directly to Position Number 222
  4.- Create Employee ID BBB in HRMS, and link it to Position Number 222
  5.- Create Employee ID AAA in HRMS, and link it to Position Number 111
  6.- Confirm that WORKFORCE_SYNC integration has brought all data into FSCM systems
  7.- In FSCM, ensure that for Employee ID AAA, the below is correct:
  - PS_JOB.POSITION_NBR = '111'
  - PS_JOB.REPORTS_TO = '222'
  - PS_JOB.SUPERVISOR_ID = 'BBB'
  8.- Now, in HRMS, perform a change, so that Employee ID BBB is now allocated to Position Number 333
  9.- Create new Employee ID CCC in HRMS, and link it to Position Number 222
  10.- Confirm that WORKFORCE_SYNC integration has brought all data into FSCM systems
  11.- In FSCM, ensure that for Employee ID BBB, the Record Field PS_JOB.POSITION_NBR = '333'
  12.- In FSCM, ensure that for Employee ID CCC is properly created in PS_JOB table, with Record Field PS_JOB.POSITION_NBR = '222'
  13.- In FSCM, confirm that nothing has changed in PS_JOB Record for Employee ID AAA, which means PS_JOB.SUPERVISOR_ID = 'BBB' while it should now be 'CCC' instead


The Record Field PS_JOB.SUPERVISOR_ID in FSCM systems is incorrect for the Employees whose Position Number reports to the Position Number that in HRMS systems has changed Employees. This can cause issues in numerous FSCM modules that make use of this field value.

At all times, in FSCM systems, the PS_JOB.SUPERVISOR_ID and PS_JOB.REPORTS_TO Record Fields of an Employee should be insync with the Employee that holds the Manager Position Number in HRMS side, especially after changes take place in HRMS systems.

Changes

 

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
Changes
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.