![]() ![]() This process only applies to timecards that have been transferred from the professional forms Timecard window to Batch Element Entry or Element Entries. The overall process for managing the creation, validation, and transfer of timecard retro adjustments is as follows. ![]() You will receive an error when you try to submit the retro adjusted timecard. If you made any changes to the original timecard data within Oracle Projects, you cannot edit the timecard within Oracle Time & Labor. If you use Oracle Payroll, you can run the Retro Notification process within Oracle Payroll to identify the changes, and then run RetroPay to correct payments. This process create a retro batch automatically so you are ready to run the Validate for BEE (retro) process. Timecards belonging to workers with the OTL Rules Evaluation preference set to Yes are transferred to the professional forms Timecard window, not straight to BEE. You run the Transfer Time from OTL to BEE process for the retro-adjusted timecards. So, if you adjust a June timecard in August, the transferred entries will be effective in June. The time and labor data is transferred to element entries as of the date of the timecard, not the date on which the adjustment is made. Retro adjusted timecards are approved and transferred to other applications in the usual way. What Happens To Retro Adjusted Timecards? So, a worker can retro adjust a timecard if the worker's Timecard Status Allowing Edits preference is set to Retro and the timecard is for a period that falls within the limit set by the Past Number of Days field of this preference. Note: A timecard is only editable if it has a status that allows edits AND it is for a timecard period that falls within the date limits set by this preference. For example, if you enter 28, a worker can enter timecards for all periods up to and including the period that contains the 28th day. Timecards for the period in which this day falls will be editable.įuture Number of Days, which holds the number of days in advance a worker can enter a timecard. Past Number of Days, which holds the age, in days, of the oldest timecard a worker can edit. Adjustments made at this point would create a Retro Time Adjustment. Retro-Workers can edit all timecards, including those that have been submitted, approved, and processed. Submitted-Workers can edit new, working, and rejected timecards, plus those that have been submitted.Īpprovals Initiated-Workers can edit new, working, rejected, and submitted timecards, plus those for which an approval process has been initiated. New_Working_Rejected -Workers can only edit timecards that have not been submitted, or are in a working or rejected status. Status Allowing Edits, which can have one of the following values: This preference determines whether the worker can edit a timecard by the timecard status and date. Who Can Make Retro Adjustments?Ī worker's ability to make retro adjustments in the self service timecard is controlled by the Timecard Status Allowing Edits preference. Retro Adjustments Retro AdjustmentsĪ retro adjustment is a change made to a timecard after it has been transferred to other applications. When you have made retro adjustments to a timecard using the Timecard window, use the Submit Requests window to run the Validate for BEE (retro) process before transferring timecards to Batch Element Entry. ![]() Can you validate the retro adjustments made to a timecard? Who can make retro adjustments?Ī worker's ability to make retro adjustments in the self-service timecard is controlled by the Timecard Status Allowing Edits preference. Retro Adjustment Procedures Retro Adjustment ProceduresĪ retro adjustment is a change made to a timecard after it has been transferred to other applications. Oracle Time and Labor Implementation and User Guide Retro Adjustment Procedures Browser version script Skip Headers
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |