My Oracle Support Banner

EPY: Employee-specific Expense Mapping doesn't work if EMPL_RCD > 0 (Doc ID 657727.1)

Last updated on NOVEMBER 26, 2021

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 8.9 and later
Information in this document applies to any platform.

Information in this document applies to any platform.

SPECIFIC TO:  Enterprise, North America Payroll, Version 8.9

This document was previously published as Customer Connection Solution 201053064


 Have found that the GL Interface process (PAYGL01) contains defect where the employee-specific expense mapping will not work if the employee's EMPL_RCD on the expense mapping is non-zero.  The following are the details of the code where the defect exists:
In the Procedure "Define-Search-Values", the following code contains the defect
       let #_Srch_Empl_Rcd     = #_Empl_Rcd
The global variable "#Empl_Rcd" referenced above is incorrect.  The correct global variable is "#EmplRcd".  The variable "#Empl_Rcd" is actually used as a local variable in several other procedures.  The value of the global variable "#Empl_Rcd" always remains zero because it is never set to the correct EMPL_RCD value of the employee. Hence, the expense mapping will fail.
A similar defect, although minor, shows up in the following code in the procedures "Get-Ern-ChartFields", "Get-Ded-ChartFields", "Get-Tax-ChartFields", and "Get-Ctx-ChartFields":
   let $DispEmplRcd = #Empl_Rcd
The variable should be "#EmplRcd" instead of "#Empl_Rcd".


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

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