My Oracle Support Banner

EPY: Mismatch Of Dept ID's & Business Units On PS_PAY_CHECK When Using The Single Check Option. (Doc ID 2190672.1)

Last updated on OCTOBER 15, 2018

Applies to:

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

Symptoms

Mismatch of Department ID's and Business units on PS_PAY_CHECK when using the Single Check option.

There some type of logic behind how the payroll calculation process determines what Department Id and what Business Unit to put on the PS_PAY_CHECK when an employee has multiple jobs that have different combinations of Business Units and Department IDs. It appears to be always putting the primary job's Dept_ID on the PS_PAY_CHECK record but it looks like it uses the BUSINESS_UNIT from the lowest EMPL_RCD event if it is not the person's primary job. It is causing issues with our GL interface because the BUSINESS_UNIT (which in most cases is the DEPT's SETID) in not valid for the DEPTID.

The issue can be reproduced at will with the following steps:
1. Create multiple jobs with different business unit and department id
2. Make the record one be the primary job and record zero be the secondary job
3. Create paysheet and run the payroll calculation to see what business unit and department id is reflected in PAY_CHECK.



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.