My Oracle Support Banner

EEX 9.2: EX_EE_UPDATE Application Engine Program Not Flagging Proper Employee Job Record As Expenses Default Profile If Current One Is Terminated (Doc ID 2339991.1)

Last updated on DECEMBER 15, 2017

Applies to:

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

Symptoms

ISSUE:

The delivered Employee Data Load Application Engine Program (EX_EE_UPDATE) is not flagging the proper Expenses Profile as default should an Employee have multiple Job Records coming from HRMS systems. If a Job Record is Terminated, the remaining one should be set as Default.

REPLICATION STEPS:

     1.- Perform the necessary system configuration from HRMS to FSCM for PERSON_BASIC_SYNC and WORKFORCE_SYNC
     2.- In HRMS systems, create a new Person, and define him as an Employee, with Job Record 0, and Effective Date January 1st 2010 (This would be marked as Primary Job)
     3.- In FSCM systems, launch the Load Employee Data AE Program (EX_EE_UPDATE)
     4.- Confirm that the Expenses Profile of the new Employee has been created successfully, and Job Record 0 is flagged as Default Profile
     5.- In HRMS systems, create a new Job Record 1 for the Employee, with different Department ID, and with an Effective Date January 1st 2015 (This would be marked as Secondary Job)
     6.- In FSCM systems, launch the Load Employee Data AE Program (EX_EE_UPDATE)
     7.- Confirm that the Expenses Profile of the new Employee has now two Job Records, and that Job Record 0 is flagged as Default Profile
     8.- In HRMS systems, proceed to Terminate Job Record 0 with an Effective Date of December 31st 2016
     9.- In FSCM systems, launch the Load Employee Data AE Program (EX_EE_UPDATE)
     10.- Confirm that the Expenses Profile of the new Employee has now set Job Record 0 as Terminated
     11.- However, Job Record 1 is not being flagged as Default Profile, so there is no default

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.

ACTUAL RESULT:

User needs to manually select as Default Profile Job Record 1, otherwise no Expense transactions can be entered for that Employee.

EXPECTED BEHAVIOR:

The EX_EE_UPDATE AE Program should always be able to update the proper Employee Job Record as the Default Profile in Expenses.

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.