OTL Process overview

Oracle Time & Labor meets your time entry needs for employees and contractors for the entire e-business suite. Workers enter their
own time which you can subject to an approval process according to your business rules. The time entries are then made
available for retrieval by any of the applications that require this person’s data. So there is a single point of time entry for use by
multiple applications

Methods for integrating OTL to Payroll Cloud.

Option
Use the Payroll Batch Loader
Submit the Load Time Card Batches Process
Call the Time Card Web Service
Action
Submit the Create Batch process from the Payroll
Administration work area to load time card entries
Create an XML file as an attachment using the file
format for transferring a batch of time cards. Submit
the Load Time Card Batches process from the Payroll
Administration or Payroll Checklist work areas to
load an XML file.
Pass the time entries to payroll using the time web
service
OTL Process Flow
Absence Integration

Enterprises use Oracle Time and Labor to capture time worked for their workers and the Absence Module in Oracle Human Resources to
record planned and unplanned absences. Workers need to have the ability to record time off and time worked from one interface rather
than navigating between multiple Interfaces. Hence these two modules have to be integrated to ensure avoidance of double entry of
absences and maintain data integrity. When workers use both the modules, absences recorded in HR Absences should be reflected on the
time cards. Worker should also be allowed to modify the time card to reflect any changes and synchronized back to the absence module.
This is required to avoid conflicting and duplicate entries in these two modules. This would help organizations to ensure accuracy of pay
calculations.

HR absence and OTL integrated business process

Process flow in Oracle Time and Labor

The following diagram illustrates the typical flow in Oracle Time and Labor module with Absences integration enabled.
Historical Edits/Updates

In Oracle Time and Labor, Updating the history data is done using following methods.

1. Using Retro functionality in OTL

2. Timekeeper

1. Using Retro functionality in OTL

If we set “status allowing edits” functionality in OTL as Retro then,

Workers can edit all timecards, including submitted, approved and processed timecards.
Adjustments made at this point would create a Retro Time Adjustment. We can also set past number of days that allows edit
and future number of days where a user can enter a timecard in advance.

OTL also allows users to edit their timecard based on status and data.

 Submitted - Workers can edit submitted, new, working, and rejected timecards.
 Approvals Initiated - Workers can edit, delete, and resubmit new, working, rejected, and submitted timecards, plus
those for which an approval process has been initiated.

Note: Workers can edit timecards in this status only if the recipient application has not retrieved them.

2. Timekeeper

It is a PUI form based interface and provides a mechanism for fast mass timecard entry and edit functionality
A person in the role of a Timekeeper can:

1. Enter time for other employees from a paper-based system filled out by the employee

2. Review and make changes to timecards that are already submitted by employees.
Schedules

Shifts define work schedules. An Employee might have several work shifts during his business day or week.
For instance, some operations have an early, a middle, and a late shift; some operations have a weekend shift.
Off shifts define the times when employees are not working, such as weekends.

In OTL from the implementation point of view, we define shifts first, then use them in work plans, which, in turn, use in rotation
plans, finally we can assign people to a rotation plan.