Time and Labor
Time Reporting Channels and Who May Act on Whose Time
Four channels bring time in, three roles can act on somebody else’s, and two prerequisite functional areas decide whether any of it reaches payroll.
Learning objectives
- 1.Name the four channels an individual can report time through
- 2.State what the device and Web Clock import does, and who resolves what it rejects
- 3.Distinguish what line managers may do for their people from what time and labor managers may do
- 4.Name the two prerequisite functional areas and when each is required
Why this matters
Reported time is the raw material of everything downstream in Time and Labor, and it arrives through four different doors with different failure shapes. A typed time card can be corrected by the person who typed it; a badge swipe cannot be corrected at all, only re-imported or overridden. Choosing a channel is therefore an operational decision — it decides who fixes a bad record, and when.
If you skip this: A workforce put on devices without anybody assigned to resolve badge exceptions produces validated-looking data with silent holes, because the exceptions have an owner on paper and nobody at the desk.
What it is, why it exists, what breaks
What it is
Individuals can report time using time cards, a calendar and Web Clock, and can also use third-party time collection devices such as badge and biometric readers. For Web Clock and devices, an import process validates the event data and creates or completes time entries, and time and labor managers resolve the badge and time entry exceptions it identifies.
Why it exists
One validated stream, four entry doors. Everything downstream — entry rules, calculation rules, consumer validation, transfer — only ever sees the time entries the channels produced, so the channel choice is the last point at which the shape of the data is a human decision.
What breaks without it
The two personless channels are the dangerous ones. A typed card has an author who can be asked what they meant; a device event has only an import and an exception queue, and if nobody works the queue the entry simply never exists.
Source: OTL-CHANNEL-003, OTL-CHANNEL-004
Four channels, one validated stream
Four parallel doors into the same stream of time entries — peers, not a sequence — with the device path carrying an exception queue the typed paths do not have. Listed in order: Time cards, then Calendar, then Web Clock, then Third-party devices, then The exception queue, then Mass time generation, then Prerequisites.
Four channels bring reported time into the application, and they are not equivalent. Time cards, a calendar and Web Clock are used directly by an individual, who can see and correct their own record. Web Clock events and third-party time collection devices — badge and biometric readers — arrive differently: an import process validates the event-related time data and creates or completes time entries from it, and the events it rejects become badge and time entry exceptions that time and labor managers resolve. That queue is the operational difference between the typed and the personless channels: a typed card has an author who can be asked what they meant, while a rejected badge event has only an exception with an owner and no deadline. Three actors have different reach. A worker reports their own time. A line manager can report, review and submit time cards for their people, including delegates. A time and labor manager can do the same for their people and additionally run the processes that generate mass time — the only actor who can create time that nobody individually recorded. Beneath the channels sit the prerequisites that decide whether any of it works: the setup tasks live in Setup and Maintenance under the Workforce Deployment offering, Time, and Labor functional area, in three groups — Time entry, Time processing, and File processing for time collection devices; Oracle Global Human Resources Cloud is required for Time and Labor processing; and if you pay worked time according to time card entries, the Elements and Formulas functional area is needed as well.
What to take from this: The interesting split is not the four channels but the three actors. A worker reports their own time. A line manager can report, review and submit for their people, including delegates. A time and labor manager can do the same for their people, and additionally run the processes that generate mass time — the only actor who can create time nobody individually recorded.
Source: OTL-CHANNEL-003, OTL-CHANNEL-005, OTL-CHANNEL-006
The badge reader that produced half a workforce’s time
A distribution centre moves its hourly staff from paper to badge readers. The devices are installed, events flow nightly into the import, and after the first week several workers’ time cards show fewer hours than the shift rosters say they worked.
- 1.The import validates the event data and creates or completes time entries for the events it can read.
- 2.Unreadable or conflicting events become badge and time entry exceptions, owned by time and labor managers.
- 3.Nobody has been assigned to work the exception queue, so the rejected events sit as exceptions and no entries exist for them.
- 4.The missing hours are investigated as a calculation problem, furthest from the queue that holds them.
Takeaway: A device channel without a staffed exception queue is not a reporting channel; it is a filter that drops a shift and files the evidence where nobody is looking. The import names its own owner — time and labor managers — and that assignment is part of choosing the channel.
Source: OTL-CHANNEL-004
Configuration model
Navigation paths
Setup and Maintenance > Workforce Deployment offering > Time, and Labor functional areaOTL-CHANNEL-007
Objects
Time cards, calendar, Web Clock
The three channels an individual uses directly, each producing entries the person can see and correct.
Risk if wrong: A workforce that cannot correct its own record moves every small error into a manager’s day.
Third-party time collection devices
Badge and biometric readers whose events arrive by import, which validates them and creates or completes time entries.
Risk if wrong: Rejected events become badge and time entry exceptions, and unworked exceptions are silent missing time.
Mass time generation
Processes that generate time for a population, available to time and labor managers for their people.
Risk if wrong: Generated time that disagrees with device events surfaces as exceptions rather than as a headline, because generation is also just a producer of entries.
Task list groups
All Time and Labor setup tasks, shown by three groups: Time entry, Time processing, and File processing for time collection devices.
Risk if wrong: A device implementation that configures entry and processing but not file processing has a channel with no importer.
Constraints
- Individuals can report time using time cards, a calendar and Web Clock, and can also use third-party time collection devices such as badge and biometric readers.
- For Web Clock and third-party devices, the import process validates event-related time data and creates or completes time entries, and time and labor managers resolve the badge and time entry exceptions identified during this validation.
- Line managers can report, review, and submit time cards for their people, including delegates.
- Time and labor managers can report, review, and submit time for their people using time cards and processes that generate mass time.
- Time and Labor setup tasks are part of the Workforce Deployment offering, Time, and Labor functional area, and Oracle Global Human Resources Cloud is required for Time and Labor processing.
- If you pay worked time according to time card entries, you also need to complete tasks in the Elements and Formulas functional area.
Source: OTL-CHANNEL-003, OTL-CHANNEL-004, OTL-CHANNEL-005, OTL-CHANNEL-006, OTL-CHANNEL-007, OTL-CHANNEL-008, OTL-CHANNEL-009
Common mistakes
Wrong: Installing devices without assigning exception resolution to anybody.
Symptom: Hours quietly missing for exactly the workers whose badges misread, with no error anywhere on a time card.
Fix: The import’s rejected events become badge and time entry exceptions that time and labor managers resolve. Staffing that queue is part of enabling the channel.
Wrong: Treating all three manager powers as the same permission.
Symptom: A line manager is expected to generate time for a whole population, and cannot.
Fix: Line managers report, review and submit for their people, including delegates. Mass time generation belongs to time and labor managers.
Wrong: Starting Time and Labor setup without Global Human Resources.
Symptom: Prerequisite tasks are missing from the task lists, and the implementation stalls on objects that are not its own.
Fix: Oracle Global Human Resources Cloud is required for Time and Labor processing, and having implemented it already completes many prerequisite tasks.
Wrong: Skipping the Elements and Formulas functional area when pay depends on time cards.
Symptom: Time is validated, calculated and transferred, and payroll has nothing to pay the hours with.
Fix: If you pay worked time according to time card entries, complete the Elements and Formulas tasks too — the bridge to payroll is a functional area, not an automatic consequence.
Diagnosing it
Symptom: A worker’s time card shows fewer hours than the roster says they worked, and nobody reported a problem.
Category: integration
- 1.
Does this population report through devices or Web Clock?
If no: The typed channels produce what the worker typed, so the gap is between the worker and the card rather than in a pipeline.
Evidence to capture: The reporting channel configured for this population
- 2.
Are there badge or time entry exceptions for this worker’s events, and are they assigned and being worked?
If no: The import rejected the events and created exceptions. Unworked exceptions are missing hours with an owner and no deadline.
Evidence to capture: The exception queue for the import period
- 3.
Was file processing for time collection devices configured as part of setup?
If no: The devices produce events and no importer consumes them, so nothing reaches a time card at all.
Evidence to capture: The three task list groups in Time and Labor setup
Confirm: Confirm the channel, then the exception queue, then the importer configuration — in that order, because each depends on the one before it existing at all.
Recall
Name the four reporting channels, say which of them arrive by import and who resolves their exceptions, and state which two functional areas Time and Labor depends on.
Answer shape: Time cards, calendar, Web Clock, and third-party time collection devices such as badge and biometric readers. Web Clock and device events arrive by an import that validates the event data and creates or completes time entries, with badge and time entry exceptions resolved by time and labor managers. Time and Labor is part of the Workforce Deployment offering’s Time, and Labor functional area, requires Oracle Global Human Resources Cloud, and needs the Elements and Formulas functional area as well if you pay worked time according to time card entries.
Memory hook: Cards, calendar, clock, devices. Devices arrive by import; the import names its own exception owner. No Global HR, no Time and Labor; pay on cards, need elements and formulas.
Source evidence
The four channels, the manager powers including delegates and mass time, the device import behaviour, and the task-list and prerequisite facts were read from the Overview of Implementing Time and Labor page on 2026-10-09.
Release scope: FA Latest
Recorded gaps
- The page states that the application addresses simple to complex time reporting for permanent and contingent employees, and names no other worker populations. Whether other populations may report is not asserted here.
- The page names File processing for time collection devices as a setup task group but does not describe the import schedule or its configuration, so this lesson states that the group exists and no more.
Related concepts
- The five-stage processing chaindepends on
Everything the channels produce enters the five-stage chain at its first stage, and the chain’s later stages never see which door the time came from.
- Time card actionsteaches
The typed channels act through the four card actions, and which actions run validation is decided by the consumer-set field that lesson covers.
- HCM groupreferenced by
Who "their people" are for a line manager or a time and labor manager is resolved by the same group machinery the profiles use.
Self-check
An auto-graded assessment is attached to this lesson: assessment-otl-reporting-channels
Lesson progress
Checking your progress…