Core HR
Worker, Assignment, Work Relationship: The Three Records and Their Rules
Three records answer three different questions about a person, and the one learners confuse is the pair that can disagree: a nonprimary work relationship whose assignment is still primary. Plus the two date fields that change nothing.
Learning objectives
- 1.State what each of the three records holds and decides
- 2.Explain who can access whose assignment, and under what rule
- 3.Explain the primary work relationship and primary assignment rules, including where they disagree
- 4.State what the two projected date fields are for, and what they do not do
Why this matters
Almost every "this worker looks wrong" ticket is a confusion between three records. The person is who they are. The work relationship binds them to one legal employer under one worker type. The assignment carries the role: job or position, pay, manager, hours, location. Ask "which of the three are we talking about" and most of these tickets answer themselves.
If you skip this: A fix applied to the assignment when the problem is the work relationship — or the reverse — either fails silently or undoes a second thing nobody asked it to touch.
What it is, why it exists, what breaks
What it is
The work relationship binds a person to a legal employer and must have at least one assignment; the legal employer may allow several. The assignment carries the role — job, position, pay, compensation, managers, working hours, location — and its status decides whether it is eligible for payroll processing.
Why it exists
Two records because two different things are true at once: who employs the person, and what the person does. The work relationship cannot change employer or type after creation; the assignment changes all the time, by design.
What breaks without it
The two primary rules are the confusion engine. A person has one primary work relationship, and each work relationship must have one primary assignment — but pending worker and offer work relationships are created nonprimary while the assignments inside them are still created primary. "Is this primary" therefore has a different answer per record, and a query that joins them naively reports a contradiction that is not one.
Source: COREHR-WR-013, COREHR-ASG-009, COREHR-ASG-031
Three records, and security stops at the assignment
Containment, not equivalence: the person holds work relationships, the work relationships hold assignments, and the primary rules differ per record. Listed in order: Person, then Work relationship, then Assignment, then Primary flags, then Assignment-level security, then Projected dates.
Three records answer three questions about one person. The person is who they are. The work relationship binds them to one legal employer under one worker type, fixed from creation, and must hold at least one assignment. The assignment carries the role — job or position, pay, compensation, managers, working hours, location — and its status decides payroll eligibility. Two primary rules govern the pair and can disagree: a person has one primary work relationship, and each work relationship holds one primary assignment — including inside pending worker and offer relationships, which are created nonprimary while the assignments within them are still created primary. Security stops at the assignment, not the person: worker assignments are secured by assignment-level security, so a line manager reaches only the assignments of workers reporting to them and an HR specialist only within their area of responsibility. One worker with two assignments can therefore be correctly visible to two different managers, and a missing assignment in one manager’s view is not evidence it was deleted. Two projected date fields complete the picture and do nothing: the projected termination date on the work relationship table and the projected assignment end date on the assignment table are for information purposes only and have no effect on application processing.
What to take from this: Read the diagram top to bottom as containment, not equivalence: the person holds work relationships, the work relationships hold assignments, and security stops at the assignment. That is the second teaching point — a line manager’s reach is defined per assignment, not per person, so a manager can see one of a worker’s two assignments and be correct.
Source: COREHR-ASG-009, COREHR-ASG-012, COREHR-ASG-029
The manager who could see the worker but not the worker’s second assignment
A worker holds two assignments under one legal employer — a main role and a project role. Their line manager opens the worker’s record and sees only the main role. A support ticket is raised claiming the second assignment was deleted.
- 1.The manager’s view is checked against the person record, and the second assignment is still there.
- 2.Worker assignments are secured by assignment-level security: the manager can reach only the assignments of workers reporting to them — and reporting is a property of the assignment, not of the person.
- 3.The second assignment reports to a different manager, so the first manager’s view is correct and complete.
- 4.The ticket closes as "working as designed", which is true, and would have been answerable before it was opened.
Takeaway: Assignment-level security means the unit of visibility is the assignment. Before concluding a record is missing, ask who the record reports to — not who the person is.
Source: COREHR-ASG-029
Configuration model
Navigation paths
My Client Groups tab > employment-related quick actions — for HR specialistsCOREHR-ASG-030My Team tab > employment-related quick actions — for line managersCOREHR-ASG-030
Objects
Person record
Who somebody is. Survives every work relationship it outlives, including a termination and rehire.
Risk if wrong: Treated as the record that holds employment facts, which it does not — those live one level down.
Work relationship
The binding to one legal employer under one worker type, fixed from creation until cancelled.
Risk if wrong: A wrong worker type or legal employer cannot be edited; the relationship is cancelled and re-created.
Assignment
The role record: job or position, pay, compensation, managers, working hours and location, with a status that decides payroll eligibility.
Risk if wrong: The assignment is also the unit of security and the unit of manager reporting, which is why a person can be visible twice or half-visible.
Projected dates
The projected termination date and projected assignment end date, stored on the work relationship and assignment tables.
Risk if wrong: Assumed to drive processing. They are for information only and have no effect on what the application does.
Constraints
- A work relationship must have at least one assignment, and your legal employer may allow multiple assignments in one work relationship.
- You must identify one assignment as the primary assignment in each work relationship, and where a person has several work relationships the overall primary assignment is the primary assignment in the primary work relationship.
- Pending worker work relationships and offer work relationships are created as nonprimary, but the assignments within them are still created as primary.
- Worker assignments are secured by assignment-level security: a line manager sees only the assignments of workers reporting to them, and an HR specialist only within their area of responsibility.
- HR specialists create and manage assignments with the employment-related quick actions on the My Client Groups tab; line managers with those on the My Team tab.
- The projected termination date and the projected assignment end date are for information purposes only and have no effect on application processing.
Source: COREHR-ASG-009, COREHR-ASG-012, COREHR-ASG-029, COREHR-ASG-030, COREHR-ASG-031, COREHR-ASG-034
Common mistakes
Wrong: Reading a nonprimary work relationship as proof the assignment inside it is nonprimary too.
Symptom: A data-quality report flags a pending worker as having "two primaries" or no primary at all.
Fix: Pending worker and offer work relationships are created nonprimary, while the assignments inside them are still created primary. The two records answer the question differently by design.
Wrong: Concluding an assignment was deleted because a manager cannot see it.
Symptom: A second role is missing from a manager’s view of a worker who demonstrably holds it.
Fix: Assignments are secured per assignment. The unit of a manager’s reach is what reports to them, so a worker’s assignments can be split across managers correctly.
Wrong: Setting the projected termination date and expecting processing to respect it.
Symptom: A global temporary assignment or fixed contract ends with no automatic action, and the date is blamed for failing to act.
Fix: Both projected date fields are for information only and have no effect on application processing. Whatever ends the assignment, a process or a person ends it.
Wrong: Building single-assignment reporting off whichever assignment is convenient.
Symptom: A government-style report that must use one assignment per person produces a different answer per run.
Fix: When you need one assignment for a person, use the overall primary assignment — the primary assignment in the primary work relationship. That is what it exists for.
Diagnosing it
Symptom: A worker’s assignment is invisible to somebody, or a primary flag looks contradictory in the data.
Category: security
- 1.
Does the person accessing the record hold access to that specific assignment?
If no: Assignment-level security is the answer: a line manager reaches only assignments reporting to them, an HR specialist only their area of responsibility.
Evidence to capture: The assignment’s manager and the accessing user’s area of responsibility
- 2.
Is the contradiction between the work relationship’s primary flag and the assignment’s?
If no: A pending worker or offer relationship is nonprimary while its assignments are primary. Both flags are correct; only the record being asked about differs.
Evidence to capture: The primary flags on both records, with the work relationship type named
- 3.
Is the report expecting one assignment for a person with several?
If no: Single-assignment reporting has a documented answer: the overall primary assignment. Anything else is a report defect.
Evidence to capture: The report’s assignment selection rule
Confirm: Confirm which of the three records the question is about, then whether the answer differs per record — person, work relationship, assignment — before changing any of them.
Recall
Name the three records and what each holds, state the assignment-level security rule, and say what the two projected date fields do.
Answer shape: The person is who somebody is. The work relationship binds them to one legal employer under one worker type, fixed from creation. The assignment carries the role — job or position, pay, managers, hours, location — and its status decides payroll eligibility. Assignments are secured per assignment: a line manager sees only those reporting to them, an HR specialist only within their area of responsibility. The projected termination date and projected assignment end date are for information only and have no effect on application processing.
Memory hook: Person, employer, role — three records, three questions. Security stops at the assignment. Projected dates project nothing.
Source evidence
The assignment contents, the primary assignment rules including the pending worker and offer exception, assignment-level security, the creation quick actions, and the projected date fields were read from the Assignments page on 2026-10-09, alongside the Work Relationships page read the same day for the work relationship’s own rules.
Release scope: FA Latest
Recorded gaps
- The assignments page references Implementing Assignment-Level Security in HCM (Doc ID 2700661.1) on My Oracle Support. That is a document ID, not content: it has not been read, so this lesson states the security rule the page states and does not describe how to configure it.
- The page states that assignments can include contract details and describes the collective agreement linking rules by bargaining unit, country and legal employer. The linking rules are claimed; what the link then does is not stated on the page and is not asserted here.
- Whether an assignment created primary inside a nonprimary work relationship changes when the pending worker is converted is not stated on either page read, and this lesson does not claim it.
Related concepts
- Assignmentteaches
The assignment is the record most of this lesson’s rules hang off: security, primary designation, status and the projected dates.
- Work relationshipdepends on
The assignment lives inside the work relationship, and the two primary rules are what make the pair confusing.
- The security modelextends
Assignment-level security is the data half of the security model applied at the finest grain the product has — the assignment rather than the person.
Self-check
An auto-graded assessment is attached to this lesson: assessment-core-hr-worker-assignment
Lesson progress
Checking your progress…