Credential holds processing and changes in query

posted Nov 3, 2017, 4:37 PM by Barbara Thiss   [ updated Nov 6, 2017, 11:21 AM by Peyri Herrera ]
NEW

M_HR_CRED_HOLD_BY_DIST query change
The M_HR_CRED_HOLD_BY_DIST query to see credential holds has been modified so you can also use it to identify hidden holds.

Credential Holds processing
When credential department places a hold on a job data position for pay to be held, a hold flag is visible on the credential holds screen. The District transfers the employee from the position being held into another position number using the same empl record number (a transfer is used when an employee is going from one position to another but the empl class is staying the same). The hold is associated with the position number so when the transfer occurs, it hides the hold_flag on the credential holds screen. Districts can use the M_HR_CRED_HOLD_BY_DIST query to see these hidden holds along with the other holds.

Be advised that the Paycheck will still be held even though the flag is not visible by the district or credentials. The only way to release the hold is to delete the transfer row using correct history. When the transfer row is deleted and the old position number is again visible, the hold will be visible as well. The hold can then be unchecked and saved (this will require communication with the Credentials department once the transfer is removed in order for them to stop the pay hold). Once this happens the district will need to reenter the transfer ASAP. This step is critical because the hold will then need to be applied to the new position by credentials if the employee is not to be paid. A request has been submitted to the PeopleSoft technical team requesting a long term solution which will not require the use of correct history. Until development can be completed, we will need to follow the above business process.