Core HR
Configuration order, and the failures it prevents
Seven setup steps in dependency order, two of them decisions that can fail. Get the order wrong and the application rejects children without saying which parent it wanted.
Learning objectives
- 1.State the seven configuration steps in dependency order
- 2.Explain why a child object cannot be saved without a valid parent
- 3.Predict the failure signature when the payroll relationship names the wrong legal entity
- 4.Explain why an unfixed structure defect surfaces in payroll rather than in Core HR
Why this matters
Every other HCM module attaches to a structure you configure first. Time and Labor routes time through the payroll relationship on an assignment, which belongs to a business unit inside a legal entity. Payroll pays the legal employer. Get the structure wrong and every module downstream inherits the error somewhere harder to diagnose than the original mistake.
If you skip this: The cost is not a failed save. It is a save that succeeds, a worker who accrues entitlement, and a payslip that is quietly empty for two months.
What it is, why it exists, what breaks
What it is
The setup runs in dependency order: legal entity, then business unit, then department, then location, then worker time entry profile, then assignment. Each step needs its parent to exist first, so the order is a constraint rather than a convention.
Why it exists
Configuration done top-down means every child has somewhere valid to attach. Configuration done bottom-up means the application rejects children and, critically, does not always say which parent it expected — so the implementer guesses.
What breaks without it
A department created before its business unit, or an assignment whose payroll relationship names a legal entity that does not employ in that country. The second case produces time that validates, transfers and arrives at payroll, and then cannot be paid.
Source: COREHR-ORDER-001, COREHR-ORDER-002
Core HR configuration order
Read top to bottom. A dashed arrow means the step failed and the flow goes back to the parent step.
Reported time reaches payroll only if seven configuration steps were performed in dependency order: legal entity, business unit, department, location, worker time entry profile, assignment. Two of those steps are decisions rather than actions, and both can fail. A business unit whose legal entity does not exist loops back to the entity step rather than continuing. A department with no valid business unit loops back to the business unit. The final decision is the expensive one: it asks whether the payroll relationship names a legal entity that employs in the worker country, and a no returns all the way to the legal entity, because the assignment is correct and the entity it names is not. That case produces a worker who exists, accrues entitlement, enters time, has it validated, transferred and received by payroll, and is never paid — with no error reported anywhere in the chain.
What to take from this: The two dashed arrows are the lesson. A business unit with no legal entity returns to the entity step, and a payroll relationship pointing at the wrong legal entity returns all the way back to the entity — not forward to the assignment, which is already correct. Reading the recovery paths is more instructive than reading the happy path.
Source: COREHR-ORDER-001
The payslip that is empty for two months
A worker in the Netherlands is set up correctly: legal entity, business unit, department, location and an assignment all exist. Time is entered weekly and validates. The transfer to the consumer set completes and is recorded as successful. Two months later the worker queries their payslip and finds nothing for the period.
- 1.Payroll support opens the payroll input and finds no time element. Correct — nothing arrived that payroll can use.
- 2.Time and Labor reports the transfer completed. Also correct, and this is the clue: the chain worked.
- 3.The analyst checks the assignment the time belonged to and finds a payroll relationship is defined.
- 4.The payroll relationship names a legal entity that does not employ in the Netherlands and is not designated as the legal employer there.
- 5.The payroll relationship is corrected to the employing legal entity and the time is reprocessed.
Takeaway: When every stage inside one application reports success, the defect is almost never inside that application. Walk the boundaries outward before auditing the stages.
Source: COREHR-ORDER-003
Who owns each step
Time flows left to right. An empty lane means that actor does nothing at that stage, and the empty lanes are the content.
Four lanes, four phases, time running left to right. The HCM administrator lane is busy for the first two phases and then idle: it creates the legal entity, business unit, department and location, then the worker time entry profile and assignment, and it does nothing during time entry or pay. The worker lane acts once, entering time. The system lane validates, calculates and transfers during the time phase, then performs the single most dangerous action in the whole process — delivering time across the bridge to payroll. The payroll lane is empty for three of the four phases and acts only at the end, producing the payslip line from whatever arrived. This is the diagnostic lesson of the picture: every step before the last column is inside a system the administrator controls and can inspect, and the last column is the only boundary where a defect can occur without anything reporting an error. A learner who internalises the shape of this diagram will start their investigation at the boundary rather than in payroll.
What to take from this: Payroll acts in exactly one column. Everything before it is inside systems the administrator configured and can inspect; the last column is the only boundary where a defect can occur without anything reporting an error. The empty lanes are the content, not an omission — three actors do nothing for three of the four phases.
Source: COREHR-ORDER-003
Configuration model
Navigation paths
Setup and Maintenance > Legal Structures > Manage Legal EntitiesCOREHR-ORDER-001Setup and Maintenance > Organization Structures > Manage Business UnitsCOREHR-ORDER-001Workforce Structures > Manage DepartmentsCOREHR-ORDER-002
Objects
Legal Entity
The organisation recognised in law. It is where the legal employer and payroll statutory unit designations live, which is what makes payroll able to pay anybody.
Risk if wrong: Payroll reports no legal employer for the worker. Time still validates and still transfers, so nothing upstream announces the problem.
Business Unit
The unit with a manager, profit and loss responsibility and a level of autonomy. It is the level at which financial transactions roll up.
Risk if wrong: A business unit that belongs to no legal entity cannot carry transactions. An assignment pointing at one will not cost or route.
Department
The organisation with operational objectives or responsibilities that exist independently of its manager, and the target of headcount and cost reporting.
Risk if wrong: A department with no valid business unit is rejected at save time, and the error may not name the parent it expected.
Location
The physical place a worker works. It carries the work relationship, the default legal employer and payroll defaults.
Risk if wrong: A location with no employing legal entity defaults the worker to the wrong employer for tax and statutory purposes.
Worker Time Entry Profile
Binds a worker to a time processing profile, which is what makes their time entry rules apply.
Risk if wrong: Time entry works and nothing ever processes. The worker reports time into a void and no error is raised.
Assignment
The dated link between a person and a job or position. It carries the payroll relationship and the reporting line.
Risk if wrong: The signature failure of Core HR: the worker exists, accrues entitlement, has time validated and transferred, and is never paid.
Constraints
- A child object cannot be saved without a valid parent, and the rejection does not reliably name which parent it expected.
- Payroll pays the legal employer and payroll statutory unit. Those designations live on the legal entity and are not implied by business unit membership.
- The payroll relationship is an attribute of the assignment, not of the worker, because a worker may hold several assignments.
Source: COREHR-ORDER-001, COREHR-ORDER-002
Common mistakes
Wrong: Creating a department before the business unit it belongs to exists.
Symptom: The save is rejected, or the department saves and then reports as invalid the moment a worker is assigned to it.
Fix: Build in dependency order: legal entity, business unit, department, location. When the message does not name the parent, check the parent rather than re-trying the child.
Wrong: Assuming the business unit determines who employs the worker.
Symptom: Payroll reports no legal employer even though the business unit is valid, populated and correctly assigned.
Fix: The legal employer is designated on the legal entity. Business unit membership does not imply it, and payroll does not infer it.
Wrong: Setting the payroll relationship on the worker record.
Symptom: A worker with two roles is paid from only one payroll, and payroll cannot tell which assignment a time entry belonged to.
Fix: Move the payroll relationship to each assignment. One worker can hold several assignments, each with its own payroll relationship.
Diagnosing it
Symptom: A worker is set up, enters time, and the time validates and transfers, but no pay ever appears.
Category: configuration
- 1.
Does the assignment carrying the time have a payroll relationship defined for the period in question?
If no: The time has no route to a payroll. Define the relationship on the assignment rather than the worker, because a worker can hold several.
Evidence to capture: Payroll relationship on the assignment, with effective dates
- 2.
Does the legal entity named by that relationship carry the legal employer designation for the worker country?
If no: This is the answer in most cases. It is the hardest to see because nothing in Time and Labor reports an error — the chain genuinely succeeded.
Evidence to capture: Legal employer and payroll statutory unit on the named legal entity
- 3.
Does the worker time entry profile exist and bind the worker to a time processing profile?
If no: A distinct failure with a distinct signature: time entry works but nothing ever processes, and the time never reaches the transfer stage at all.
Evidence to capture: Worker time entry profile and the time processing profile it references
Confirm: Confirm by reprocessing the affected period and verifying that the payslip line now appears. A configuration change that has not been verified has not been completed.
Recall
State the Core HR configuration order from memory, and say which two steps are decisions rather than actions.
Answer shape: 1. Legal entity. 2. Business unit. 3. Department. 4. Location. 5. Worker time entry profile. 6. Assignment. The decisions are: whether the business unit belongs to an existing legal entity, and whether the payroll relationship names a legal entity that employs in the worker country. Everything after the legal entity fails back to it, because the entity is the root of the structure.
Memory hook: Entity, Unit, Department, Location, Entry profile, Assignment. Read the initials: E U D L E A. The payroll relationship is on the last one.
Source evidence
The legal entity, business unit and department definitions and the separation of the legal, management and functional structures were read directly from Oracle documentation on 2026-10-05 and are linked rather than reproduced. The seven-step dependency order is assembled by this academy from those pages plus the Workforce Structures work area, and the diagnostic sequence in the troubleshooting block is this academy’s reasoning rather than an Oracle support procedure.
Release scope: 26D
Recorded gaps
- No single Oracle page states the six-step dependency order in this form. It is assembled from the Manage Legal Entities, Manage Business Units and Manage Departments pages, each of which documents its own task in isolation.
- The claim that a rejected child save does not always name the expected parent is the academy’s observation from implementation practice. It has not been confirmed against an Oracle statement, and is recorded as such rather than presented as documented behaviour.
Related concepts
- The enterpriseprerequisite
The enterprise is the root boundary every other object in this lesson is defined within.
- Legal entity and legal employerteaches
Step one of the order, and the object every failure in this lesson loops back to.
- Business unitteaches
Step two, and the level at which financial transactions roll up.
- Departmentteaches
Step three, and the first object in the order where a missing parent produces a rejected save.
- Payroll relationshiptroubleshoots
The attribute the final diagnostic check looks for, and the boundary this lesson teaches you to walk outward.
Self-check
An auto-graded assessment is attached to this lesson: assessment-core-hr-configuration-order
Lesson progress
Checking your progress…