Time reporting channels
ConceptfoundationThe four doors reported time arrives through — time cards, a calendar, Web Clock and third-party devices — and the three actors with different reach over other people’s time.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That a device channel reports time on its own. Its events arrive by an import, and the events the import rejects become exceptions that time and labor managers must resolve, or the time simply never exists.
- That line managers and time and labor managers have the same powers. Only time and labor managers can run the processes that generate mass time.
Recall it
Name the four reporting channels, say which arrive by import and who resolves their exceptions, and name the two prerequisite functional areas.
Time cards, calendar, Web Clock and third-party time collection devices. Web Clock and device events arrive by an import that validates the event data and creates or completes time entries, with the rejected events becoming badge and time entry exceptions resolved by time and labor managers. Oracle Global Human Resources Cloud is required for Time and Labor, and the Elements and Formulas functional area is also required if you pay worked time according to time card entries.
Memory hook: Cards, calendar, clock, devices. The personless two arrive by import, and the import names its own exception owner. No Global HR, no Time and Labor; pay on cards, add elements and formulas.
Rests on OTL-CHANNEL-003, OTL-CHANNEL-004, OTL-CHANNEL-007, OTL-CHANNEL-008.
Taught in
Related
- Terminology glossary — what a term means, and what people get wrong when they use it