Hiring an employee is the first transaction anyone learns in Oracle Fusion HCM, and the one every later HR task builds on. Promotions, transfers, salary changes and terminations all act on records the hire creates. Interviewers for Core HR roles ask about it because explaining a hire well shows you understand how Fusion models a worker.
This guide walks through the hire flow, explains what each part of it creates, and lists what to practise once your first employee exists.
What a hire creates
Before clicking anything, it helps to know the four records behind one employee:
- Person: the human being, with a name, date of birth, national identifier, addresses and contacts. Each person gets a person number.
- Work relationship: the link between the person and a legal employer, starting on the hire date. One person can have work relationships with more than one legal employer over time.
- Employment terms: an optional layer some enterprises use to hold terms shared by several assignments.
- Assignment: the job itself, with business unit, department, job or position, location, grade, manager and working hours. Most day-to-day changes happen here.
The hire flow collects data for all of these on one set of pages, so it can feel like a long form. Knowing which record each field lands on makes it much easier to follow.
What you need first
- A login with an HR role, such as Human Resource Specialist, with data access to the legal employer and business unit you will hire into.
- The enterprise structures already set up: a legal employer, a business unit, departments, jobs, locations and, if used, grades and positions. On a practice instance with demo data these exist already.
Fusion pages change between releases, and the newer Redwood pages lay this out differently from the classic ones. The section names below may not match your screen word for word, but the information asked for is the same.
Step 1: Start the hire
From the home page, open My Client Groups and, under Quick Actions, choose Hire an Employee.
If you do not see it, your role does not include the hire privilege, or you have no data access to any legal employer. Ask whoever manages your roles, or check them in the Security Console if your plan includes it.
Step 2: When, why and where
The first section sets the frame for everything else:
- Hire Date: the date the work relationship and the assignment start. Every record the hire creates is effective from this date.
- Hire Action and Action Reason: normally Hire, with an optional reason. Reasons are useful later in reports.
- Legal Employer: the company that employs the person. It decides which legislation applies, and which national identifier types and other fields you see later.
Step 3: Personal details
Next comes the person record:
- Name: the name format depends on the legal employer's country.
- Date of birth, gender and national identifier: the identifier type list depends on the legislation.
- Address, phone and email: the work email matters on a real project, because it is usually what the user account and notifications use.
- Marital status, citizenship and other legislative details where the country requires them.
When you enter a name and date of birth, Fusion can check for an existing person who matches and warn you. On a real project that check prevents duplicate person records; on a practice instance it is a good moment to see it work.
Step 4: Employment information
This is the assignment, and it carries most of the fields people talk about:
- Business Unit: decides which departments, jobs and positions you can pick.
- Person Type: Employee for an ordinary hire.
- Assignment Status: usually Active - Payroll Eligible, or the active status your enterprise uses.
- Position, if your enterprise is position-based. Choosing a position brings in its job, department, location and grade as defaults.
- Job, Department, Location and Grade if you are not using positions, or to override defaults.
- Manager: the line manager. This drives approvals and what the manager sees in their own team pages.
- Working Hours and Frequency, and whether the job is full time or part time.
The difference between a job and a position is a classic interview question. A job is a generic role, such as Accountant, that many people can hold. A position is a specific seat in a specific department, with its own headcount, that inherits a job. Enterprises that control headcount tightly tend to hire into positions.
Step 5: Salary and other information
If the enterprise uses compensation in Fusion, enter:
- Salary Basis: defines how salary is expressed, for example annual or hourly, and in which currency.
- Salary Amount: the amount on that basis.
Depending on the setup, you may also see a payroll to attach the assignment to, documents to upload such as an offer letter, and extra information fields the enterprise added.
Step 6: Review and submit
Review the summary and click Submit. Two things can happen next:
- If no approval rules apply, the hire completes straight away.
- If approvals are configured, the transaction goes to the approver first, and the person record is created when it is approved.
Depending on the enterprise's user provisioning settings, a user account may be created for the new worker automatically, with roles assigned through role provisioning rules. Whether that happens on your instance is a setup choice, so check it rather than assume it.
Step 7: Check the new worker
Search for the person from My Client Groups, by name or person number, and open their record. Look at:
- the person number that was assigned,
- the work relationship, with its start date and legal employer,
- the assignment, with its department, job, manager and status,
- the salary, if you entered one.
Then open the employment details and look at the history. There is one row, starting on the hire date. That row is the first piece of effective dating, the idea behind nearly everything else in Fusion HCM.
Effective dating in one paragraph
Fusion HCM keeps history by date. When you later promote this employee from 1 January, Fusion does not overwrite the assignment; it ends the current row on 31 December and starts a new one on 1 January. Searching "as of" a date shows the record as it was then. Corrections fix a row in place, while updates add a new one. Most confusing results in HCM, such as a change that "did not save", turn out to be a change made with an effective date in the future or the past.
What to practise
Once one employee exists, these make good exercises and good interview stories:
- Promote the employee with a new job and grade from a future date, then look at the assignment history and the "as of" view either side of that date.
- Transfer the employee to another department and change their manager.
- Make a salary change and see how it appears against the salary basis.
- Terminate the work relationship, then rehire the same person and see that they keep their person number.
- Hire a second person with the same name and date of birth as the first, and watch the duplicate check.
- Add a pending worker, then convert them to an employee from their record, which is how many enterprises handle new joiners.
Practise on a Fusion instance
The hire only makes sense once you have done it a few times and then changed the record you created. Our Fusion plans come in refresh and non-refresh versions, with or without Security Console.
Questions people ask
Where is Hire an Employee in Oracle Fusion?
Open **My Client Groups** from the home page and look under **Quick Actions**. If it is missing, your role does not include the hire privilege or you have no data access to a legal employer.
What is the difference between a job and a position in Fusion HCM?
A job is a generic role that many people can hold, such as Accountant. A position is a specific seat in a department, with its own headcount, and it is linked to a job. Position-based enterprises hire people into positions.
What is a work relationship?
It is the link between a person and a legal employer, starting on the hire date and ending on termination. Assignments sit under it. A person who is terminated and later rehired gets a new work relationship but keeps the same person number.
What is the difference between an employee and a pending worker?
A pending worker is someone who has accepted an offer but not yet started. Their record exists so that onboarding can begin. Conversion to an employee or contingent worker does not happen by itself: an HR user converts the record, or the enterprise schedules the process that converts pending workers automatically.
Why does my change not show on the employee's record?
Check the effective date. Fusion HCM keeps history by date, so a change dated in the future does not show when you view the record as of today.