Timecards Interfaced to Projects Without Costings, How to do Retro? (Doc ID 1365382.1)

Last updated on OCTOBER 11, 2017

Applies to:

Oracle Time and Labor - Version 11.5.10.2 and later
Information in this document applies to any platform.

Goal

A Batch of Timecards has been interfaced to Projects from OTL without costings.

We would like to re-process the Timecards as Adjustments using the following SQL to set the Timecard entries to be handled as Retro entries:

UPDATE hxt_det_hours_worked_x
SET pa_status = 'R' -- Rollback = 'C'
WHERE tim_id in (
SELECT distinct tim.id
FROM hxt_timecards_x tim,
per_time_periods ptp,
per_time_period_types ptpt,
pay_batch_headers ppbh,
per_people_f ppf
WHERE tim.payroll_id = 61
AND ptp.time_period_id BETWEEN NVL(150,1) AND NVL(151,999999999)
AND tim.time_period_id = ptp.time_period_id
AND ptp.period_type = ptpt.period_type
AND tim.batch_id = ppbh.batch_id
AND ppbh.batch_status <> 'U'
AND ppbh.batch_id = 791709
AND ppf.person_id = tim.for_person_id
AND ppf.effective_start_date =
(select MAX (ppf2.effective_start_date) -- to handle mid pay period changes
from per_people_f ppf2
where ppf2.person_id = tim.for_person_id
and ppf2.effective_end_date >= ptp.START_date
and ppf2.effective_start_date <= ptp.END_date)
)
AND pa_status = 'C'
;

Then run "Transfer to Proj Act (Retro)"

And Import the Transactions to Projects as Adjustments.

Do you foresee any problems with this?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms