PSFT T&L - Issue Encountered On App Engine GP_TLCOST When Setting The LBR_DIST_AMT In TL_PAYABLE_TIME
(Doc ID 2350651.1)
Last updated on FEBRUARY 04, 2019
Applies to:PeopleSoft Enterprise HCM Global Payroll Core - Version 9.1 and later
Information in this document applies to any platform.
Recovery of a prior time entry is not being passed to T & L correctly via the Send Cost to TL process (GP_TL_COST)
Bug encoutered in Time and Labour / Global Payroll when running the Send Cost to TL process (GP_TL_COST). Scenario: Staffing Client, and there are occasions where processed Timesheet transactions have to be reversed out in a subsequent Payroll run due to incorrect Payments or incorrect selection of TRCs. This is a necessary business process to ensure that all data which flows into Financials produces accurate Invoices in Billing.
There are issues when "Additional" Sessions are being created in T+L with Negative Amounts to "offset" the original timesheet transaction. The transactions process through to Payroll correctly. However when running the Send Cost to TL process, the TL_PAYABLE_TIME.LBR_DIST_AMT has the wrong value being stored and as such the wrong LBR_DIST_AMT value is being sent across to Financials.
With regards to T+L, Business Processes requires to always create "Additional" Sessions.
The source of the bug appears to start in GP_TLCOST.EA000.Step20. The SQL section criteria is incorrect and the wrong records are being selected in this step and as such the LBR_DIST_AMT is being calculated from transactions processed in the previous week.
Some further information for the Technical Resource. The original entry was and always is distributed. The TL_PAYABLE_TIME for the original entries always have a final PAYABLE_STATUS of 'PD' after the 'Send Costs to T+L' process is run. In addition, the PUBLISH_SW also changes to 'Y'. However when subsequent offsets are processed, this can update the PAYABLE_STATUS values on the original entry from 'PD' to 'IG'.
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