Fusionintermediate
Fusion HCM Core Concepts: Global HR and Work Structures
Understand the foundational work structures that underpin Oracle Fusion HCM implementations
Fusion HCM models an organisation through work structures, and one global instance can serve many countries.
Fusion's work structures are like a multinational franchise's org chart: the parent brand (Enterprise) sets overall standards, each country's franchise (Legal Employer/LDG) follows local laws, and within each location, some franchises tightly define exact staffed positions (Position-based, like 'Shift Manager - Store 42') while others just hire flexibly into general roles (Job-based, like 'Barista').
Key Concepts
1
Enterprise the whole organisation
Legal Employer the legal entity that employs people
Business Unit a processing and security boundary
Division / Department
Job or Position2
Legislative Data Groups handle country differences. Payroll rules, statutory reporting and legislative
requirements differ per country, and an LDG is the boundary that holds them.
3
So one instance supports India, the UK and the US with their own rules, rather than the separate business
groups per country that EBS HR effectively required.
4
Job or position is the design decision every implementation makes.
Job-based "Software Engineer" exists as a concept.
Hire someone into it. No seat required.
Position-based "Software Engineer, Team 4, Bengaluru, seat 2"
exists. Somebody occupies it or it is vacant.5
Job-based suits organisations where roles move around — technology and services companies, where teams
are reshaped often and headcount is managed in aggregate.
6
Position-based controls headcount structurally. A vacancy exists as an object, a hire fills it, and you
cannot exceed budgeted headcount because there is no seat. Public sector and heavily unionised
organisations use this, because the establishment is the control.
7
The trade is administrative: position-based means maintaining positions, and every reorganisation is a
position change before it is a people change.
8
The person model is genuinely more flexible than EBS's.
Person
Work Relationship (with a legal employer)
Assignment
Assignment <- two at once
Work Relationship <- a second employer9
One person can hold two part-time assignments, or an employee relationship and a contingent worker
relationship, or a global assignment alongside a home one.
10
EBS HR could not express that cleanly, and implementations worked around it with duplicate person records —
which then broke reporting and payroll.
11
Flexfields still exist under the same name, configured through a different interface, doing the same job:
extending the delivered data model without altering it.
12
What the interviewer is probing.1. "What are the core work structures?" Probing: the vocabulary. Stalls: "Departments."
Moves up: legal entities, business units, departments, locations, jobs, positions and grades — the
frame every worker record hangs from.
13
2. "What is the difference between a job and a position?" Probing: the key distinction.
Stalls: "Nothing." Moves up: a job is a generic role definition; a position is a specific seat
in a specific department, which position management requires.
14
3. "Why is effective dating central?" Probing: the model. Stalls: "History." Moves up:
nearly everything is date-tracked, so a change is recorded from a date rather than overwriting —
which is what makes retroactive processing possible.
15
4. "What is the person versus worker distinction?" Probing: the detail. Stalls: "The same."
Moves up: a person can hold several work relationships over time or at once, so the person record
outlives any single assignment.