Time and Labor
Time Consumer Sets
How Time and Labor decides which downstream systems receive time, which validations they contribute, and why the set locks once a profile uses it.
Learning objectives
- 1.Name the products that consume Time and Labor data
- 2.Explain what a time consumer set holds and how it links to people
- 3.Explain why a consumer set becomes uneditable after a profile is associated with it
- 4.Explain where the Payroll-to-Project-Costing attribute mapping actually lives
Why this matters
Every Time and Labor incident that ends in "payroll is wrong" or "project cost is wrong" passes through a consumer set. If you do not know which consumers are attached to a population, you cannot tell whether the data was never transferred or was transformed in transit.
If you skip this: Treating consumer validation as Time and Labor configuration is a category error. Those rules are delivered by the consumer.
What it is, why it exists, what breaks
What it is
A time consumer set identifies which consumers consume time data for specific groups of people, and is where the consumer validation rules, approval periods and transfer rules are configured.
Why it exists
Grouping the consumer decision in one object means the answer to "who receives this time" is a configuration lookup rather than an inference from several screens.
What breaks without it
Once a set is associated with a worker time processing profile, adding or removing consumers from it is no longer possible. Design it before attaching it.
Source: OTL-CONSUMER-051, OTL-CONSUMER-052
Time consumers and the transfer
Three consumers receive the same validated time, and which of them receive it for a given population is decided by the time consumer set.
Three products consume Time and Labor data: Global Payroll, Project Costing, and the Project Execution Management offering of Project Portfolio Management. Which of them receive time for a given population is decided by the time consumer set attached to the worker time processing profile, so the same submitted time can go to payroll but not to project costing. The set also holds each consumer's validation rules, its approval period, and its transfer rules. The approval period matters most in practice: it determines when transferred time actually reaches the consumer. A consumer whose source is not healthy is demoted in search ranking, and a claim citing a broken source stops being retrievable as support until it is re-verified.
What to take from this: The same submitted time can reach payroll but not project costing, because the consumer set decides who receives what for which population. The approval period decides when transferred time actually arrives, so a correct card with no pay is usually a missing transfer rather than a rejected one.
Source: OTL-CONSUMER-050, OTL-CONSUMER-051
Project cost is missing hours that Time and Labor says were transferred
A project manager is confident their time card transferred, because they can see the project allocation in Time and Labor. Project Costing shows nothing for the same period.
- 1.Check which consumers are on the time consumer set for that population. If Project Costing is absent, nothing was ever sent.
- 2.If Project Costing is present, check whether its consumer validation rejected the entries — a closed project is the usual cause.
- 3.Check whether the Validate on Time Card Actions setting includes save for this consumer. By default the delivered project and payroll validations do not run on save.
- 4.Confirm the transfer completed for the approval period covering those dates.
Takeaway: Oracle recommends selecting submit and save for Project Costing precisely so people know immediately if they are saving time against a closed project. The default hides that failure until transfer.
Source: OTL-ACTION-061, OTL-ACTION-062
Configuration model
Objects
Time consumer set
Names consumers for a population and holds their validation, approval period and transfer rules.
Risk if wrong: A consumer receives nothing, or receives data it cannot accept.
Consumer validation rules
Delivered by each consumer. Absence validations check eligibility; project and payroll validations check their own preconditions.
Risk if wrong: These are not editable here. A failing consumer validation must be resolved against the consumer's own rules.
Approval period
A repeating time period that bounds when approvers can approve a submitted card.
Risk if wrong: Approval windows open or close at the wrong times for a whole population.
Constraints
- A time consumer set associated with a worker time processing profile cannot be edited.
- After saving a new set, new time consumers cannot be added to it and existing ones cannot be removed.
- By default the delivered absence validations start on save, while the delivered project and payroll validations do not.
Source: OTL-CONSUMER-050, OTL-ACTION-061, OTL-CONSUMER-052
Common mistakes
Wrong: Adding a consumer to a set that is already attached to a profile.
Symptom: The change is silently impossible, or the edit is refused outright.
Fix: Confirm whether the set is already associated with a worker time processing profile before designing it.
Wrong: Assuming a save on the time card triggers project or payroll validation.
Symptom: An entry against a closed project saves cleanly and only fails much later at transfer.
Fix: By default those validations do not run on save. Configure the validation-on-action setting for the consumer.
Wrong: Looking for Oracle documentation of the time-entry-to-payroll-element mapping.
Symptom: Frustration, and a temptation to trust a blog post.
Fix: That mapping is not published on the consumer sets page. It is defined by your own payroll elements and cost segments, so treat any mapping you read as tenant-specific.
Diagnosing it
Symptom: A downstream consumer is not receiving time it should receive.
Category: integration
- 1.
Is the consumer named on the time consumer set for this population?
If no: Nothing was ever intended to be sent. This is a design gap, not a bug.
Evidence to capture: Time consumer set configuration for the profile
- 2.
Did consumer validation pass for that specific consumer?
If no: The consumer rejected the data. Read its message; the rule belongs to the consumer, not to Time and Labor.
Evidence to capture: Consumer-specific validation messages on the entries
- 3.
Did the transfer complete for the approval period covering these dates?
If no: The approval period has not closed, or a transfer is due. Check the period, not the rules.
Evidence to capture: Transfer status and the approval period on the set
- 4.
Does the consumer require a field the entries do not carry?
If no: The attribute mapping in your tenant does not supply what this consumer needs. This is a mapping gap you must close in your own configuration.
Evidence to capture: The consumer's required attributes against your element and cost segment definitions
Confirm: Once the transfer succeeds, re-query the consumer. If it is still absent there, the investigation has moved into the consumer's own integration.
Recall
Name the three products that consume Time and Labor data, then say what a time consumer set holds.
Answer shape: Global Payroll, Project Costing, and the Project Execution Management offering of Project Portfolio Management. A time consumer set holds the consumers, their validation rules, their approval period and their transfer rules, for a specific group of people.
Memory hook: Pay, Cost, Staff. The set holds Consumers, Validation, Approval and Transfer — CVAT.
Source evidence
The consumer list and the immutability constraint were read directly from Oracle's Time Consumer Sets page on 2026-10-05. The default validation behaviour and Oracle's Project Costing recommendation come from the validation-by-action page.
Release scope: FA Latest
Recorded gaps
- Oracle publishes no attribute-level mapping between time entries and payroll or project costing fields on these pages. Any mapping is tenant-specific and must be established from your own element and cost segment definitions.
- Whether the delivered absence validation runs on Save alone or on both Save and Save and Close is ambiguous in the retrieved documentation and is recorded as unverified.
Related concepts
- Worker Time Processing Profiledepends on
The profile is what associates a consumer set with a population, which is what locks it.
- OTL to Payroll bridgeteaches
This is the OTL half of the Payroll bridge.
- OTL to Project Costing bridgeteaches
This is the OTL half of the Project Costing bridge.
Self-check
An auto-graded assessment is attached to this lesson: assessment-otl-consumer-sets
Lesson progress
Checking your progress…