Oracle HCM Cloud Global HR —
100 Interview Questions & Answers

Oracle HCM Cloud Global HR (also called Core HR or Workforce Management) is the foundational module of Oracle HCM Cloud that stores and manages the entire employee and contingent worker lifecycle — from hire to retire — across all countries and legal entities in a single unified system.

• Single Source of Truth: Maintains all person, employment, and workforce structure data shared across Payroll, Talent, Recruiting, Absence, and Benefits modules
• Global Scalability: Supports multiple countries, legal entities, currencies, languages, and legislative requirements in one instance
• Key Functional Areas: Person Management, Employment Records, Workforce Structures (Enterprise → Position), Actions & Action Reasons, Position Management, Absence, and Document Records
• Cloud Native: Delivered as SaaS; Oracle handles quarterly updates, infrastructure, and compliance packs for 200+ countries
• Self-Service: Employee Self-Service (ESS) and Manager Self-Service (MSS) empower workers and managers to manage HR transactions without HR intervention

The Enterprise Structure is a hierarchical framework that represents the legal, financial, and operational organisation of a company in Oracle HCM Cloud.

• Enterprise: The top-level entity representing the entire company — there is only one enterprise per HCM instance
• Legislative Data Groups (LDG): Groups legal entities by country/legislation to drive payroll and compliance rules
• Legal Entities / Legal Employers: Represent the legal companies that employ workers, issue payslips, and file statutory returns
• Business Units: Represent the operational divisions for financial reporting, purchasing, and HR management purposes
• Departments: Organisational units within a Business Unit where workers are assigned; used for reporting and cost allocation
• Locations: Physical addresses where workers are based; used for tax purposes and site-level reporting

Legal Entities and Business Units serve distinct purposes and operate at different levels of the enterprise structure:

• Legal Entity: Represents a legally registered company. It is used for statutory compliance — issuing contracts, processing payroll, filing taxes. A worker's assignment is linked to a Legal Employer (a type of Legal Entity)
• Business Unit: Represents an operational division used for financial management, purchasing, and HR processing. It does not have legal standing but is used for subledger accounting and business reporting
• HR Perspective: From a Core HR point of view, a worker's assignment is linked to a Legal Employer and a Business Unit. The Legal Employer drives statutory compliance while the Business Unit drives financial and HR operational processes
• Multiple BUs per Legal Entity: A single Legal Entity can have multiple Business Units (e.g., Sales BU and IT BU under one legal company)

A Legislative Data Group (LDG) is a partition in Oracle HCM Cloud that groups legal entities sharing the same legislation/country. It is primarily a payroll concept but impacts Core HR configuration.

• Each LDG is associated with a single country's legislation — e.g., one LDG for India, one for the UK
• Payroll definitions, elements, balances, and legislative rules are defined at the LDG level
• A Legal Employer must be linked to an LDG before payroll can be processed for workers in that legal entity
• HR configuration like Grade Ladders, Salary Bases, and some absence plans can also be tied to an LDG
• If a company operates in multiple countries, multiple LDGs are created — one per country's legislation

Reference Data Sets (Set IDs) are a partitioning mechanism that allows the same type of reference data (e.g., Departments, Locations, Jobs, Grades) to be shared across or restricted to specific Business Units.

• Common Set: A special set visible to all Business Units — used for truly global reference data like shared job definitions
• BU-specific Sets: Created for reference data that should only be visible within a particular Business Unit or group of BUs
• Set Assignment: Each Business Unit is assigned a Set ID for each reference object type (e.g., BU1 uses Set A for Departments, Set B for Locations)
• Impact: When a user creates a worker assignment in BU1, they can only see Departments and Locations that belong to BU1's assigned set or the Common Set
• Configuration: Managed via Setup and Maintenance → Manage Reference Data Sets and Manage Business Unit Set Assignment

Jobs and Positions are two complementary ways to classify work in Oracle HCM Cloud, and understanding their difference is a critical interview topic:

• Job: A generic role definition not tied to a specific organisational unit. For example, "Software Engineer" is a job — it can exist in any department. Jobs are reusable across the enterprise and have a Job Family and Job Function classification
• Position: A specific occurrence of a job within a specific department/organisation. For example, "Software Engineer – Bangalore – Team A" is a position. Positions carry headcount, FTE, and budget information
• Job-based model: Simpler; workers are assigned to jobs. Used when headcount control at position level is not needed
• Position-based model: More controlled; workers are assigned to positions. Positions can be vacant, filled, or frozen — enabling precise headcount management
• Hybrid: Many organisations use both — positions for controlled roles (finance, compliance) and jobs for others

Grades represent the level or seniority of a role and are used for salary banding, progression, and workforce analytics.

• Grade: A classification of work level (e.g., Grade 1, Grade 2, Band A, Band B). Grades can have associated salary ranges (minimum, midpoint, maximum) called Grade Rate Steps
• Grade Ladder: An ordered sequence of grades representing a career progression path. For example, a "Software Engineering Ladder" might contain Junior → Senior → Lead → Principal grades
• Grade Steps: Within a grade, steps define specific pay points (e.g., Step 1 = ₹500,000, Step 2 = ₹550,000). Used in public sector and union environments
• Assignment: Workers are assigned a Grade on their employment record, which drives compensation eligibility and salary range validation
• Configuration: Managed in Setup and Maintenance → Manage Grades and Manage Grade Ladders

Departments are organisational units that group workers for HR, financial, and reporting purposes.

• Department Attributes: Department Name, Description, Status (Active/Inactive), Business Unit, Cost Center (optional link to GL), Location, and Manager
• Department Tree (Org Chart): Departments can be arranged in a parent-child hierarchy using the Oracle Tree structure. This creates an organisation chart that drives manager reporting relationships and HR security
• Creating a Tree: In Setup and Maintenance → Manage Department Trees, administrators define the parent-child relationships between departments. Trees are versioned and can be activated/deactivated
• Tree Flattening: Oracle uses tree flattening to improve performance for reporting queries that traverse the hierarchy
• Reporting: Department hierarchies drive headcount roll-up reports and HR dashboards in OTBI and HCM Extracts

Locations represent physical sites or addresses where workers are based. They serve multiple purposes across HR, Payroll, and Facilities.

• Address Details: Locations store address, country, state/province, postal code — driving tax jurisdiction for payroll
• Primary Work Location: Workers are assigned a primary work location on their employment record, impacting tax withholding and statutory reporting
• Usage: Locations are used on Positions, Requisitions (for job posting), and Absence Plans (for public holidays)
• Set Assignment: Locations belong to Reference Data Sets and are visible to Business Units based on their set assignment
• Legal Address vs Work Location: A Legal Entity has a registered address; a Location is the operational work site — these can differ (e.g., registered in Mumbai, office in Pune)

Job Families and Job Functions are classification attributes that group jobs for reporting, benchmarking, and talent matching.

• Job Function: The broadest classification — e.g., Finance, Technology, Operations, Human Resources. Oracle provides a standard list that maps to industry benchmarks
• Job Family: A more specific grouping within a function — e.g., within Technology: Software Engineering, Data Engineering, IT Support
• Usage in Recruiting: Oracle Recruiting Cloud uses Job Family and Function to match candidates to requisitions and drive career site search filters
• Compensation Benchmarking: External salary surveys are often mapped to Job Family/Function codes for compensation analysis
• Talent Profiles: Talent Management uses Job Family to group similar roles for succession planning and career development paths

These three layers form the core data model of Oracle Global HR and represent different aspects of a worker's information:

• Person Record: Stores personal biographical information — name, date of birth, national ID, contact details, addresses, and disability/ethnicity data. It is shared across all roles a person may hold (employee, contingent worker, ex-employee)
• Employment Record (Work Relationship): Links a person to a legal employer with a specific worker type and start date. A person can have multiple work relationships (e.g., primary employee + part-time contingent worker at the same time)
• Assignment: The most detailed record — captures the specific work context: Job, Position, Department, Location, Grade, Hours, Salary, Manager. A work relationship can have multiple assignments (e.g., an employee with two jobs in the same legal employer)

Oracle HCM Cloud supports multiple worker types to represent different employment arrangements:

• Employee: A person on the company payroll with an employment contract. Sub-types include Full-Time, Part-Time, and Fixed-Term
• Contingent Worker: A contractor or consultant not on payroll but tracked in HCM for system access, project management, or compliance. They are placed by suppliers and have a Placement (not a payroll record)
• Non-Worker: A person with no employment relationship but requiring system access or HR tracking — e.g., a board member, retiree, or intern awaiting onboarding
• Pending Worker: A pre-hire record created after a job offer is accepted but before the actual start date. Enables early system access provisioning (IT setup, background checks)

The Hire process creates a new Person record and Work Relationship for a new employee. In Oracle HCM Cloud, this is initiated via the New Person or Hire an Employee transaction.

• Step 1 – Identify Person: Search for an existing person to avoid duplicates (using national ID, name, DOB). If found, a new work relationship is added to the existing person
• Step 2 – Personal Information: Enter name, DOB, national identifier, gender, nationality
• Step 3 – Employment Information: Legal Employer, Start Date, Worker Type, Payroll, and HR Representative
• Step 4 – Assignment: Job/Position, Department, Location, Grade, Manager, Work Schedule, Hours
• Step 5 – Compensation: Salary basis, salary amount, and grade rate validation
• Step 6 – Additional Info: Document Records, Benefits Enrollment, Bank Account, Tax Withholding
• Approval Flow: Hire transactions can be routed through approval workflows before the employee record is active

Date-Effective tracking (also called temporal data management) is Oracle HCM Cloud's mechanism for maintaining a full history of all changes to a worker's record over time.

• How it works: Every update to an assignment creates a new effective-dated row with a start and end date — the previous row is not deleted but becomes a historical record with an end date
• Example: A promotion on 01-Apr-2024 creates a new row. The system maintains the previous record (e.g., Senior Analyst from 01-Jan-2022 to 31-Mar-2024) and adds the new row (Manager from 01-Apr-2024 to end of time)
• Correction vs Update: A Correction changes an existing effective-dated row (fixing an error). An Update creates a new row going forward (a genuine change)
• Future Dating: Changes can be entered in advance — e.g., a salary increase effective next month is entered today and automatically activates on the effective date
• Impact on Reporting: All OTBI and HCM Extracts support AS OF date parameters to view the state of a workforce at any past, present, or future point in time

Global and Local Transfers are HR actions that move workers between different parts of the organisation, but they operate differently depending on whether a legal employer change is involved.

• Local Transfer: Moves a worker within the same legal employer. Department, Location, Job, Manager, or Grade changes. No change to work relationship — a new assignment record is created. Payroll continues without interruption
• Global Transfer: Moves a worker from one legal employer to another (crossing legal entities, often crossing countries). This terminates the existing work relationship and creates a new one under the new legal employer. Payroll in the origin country is finalised; a new payroll in the destination country begins
• Global Transfer Data Copy: Oracle provides options to copy personal information, salary, assignment details, and benefits to the new work relationship, avoiding re-entry
• Impact on Person Number: The Person record and Person Number remain the same for both transfer types — the person is not rehired as a new person
• Cross-Legislation Complexity: Global transfers between countries with different LDGs require careful handling of payroll finalisation, tax settlement, shadow payroll, and benefit plan transitions

Actions are the pre-defined HR transactions available in Oracle HCM Cloud that create an effective-dated change on a worker's record. Action Reasons provide a more granular explanation for why the action was taken.

• Action Examples: Hire, Transfer, Promotion, Salary Change, Change Working Hours, Termination, Rehire, Data Change, Suspension
• Action Reasons: Each action can have multiple reasons. For example, the Termination action might have reasons: Resignation, Redundancy, Retirement, End of Contract, Dismissal
• Reporting Impact: Actions and Reasons are captured on every effective-dated record change, enabling detailed workforce movement analytics (turnover by reason, promotion rates, etc.)
• Configuration: Managed in Setup and Maintenance → Manage Actions and Manage Action Reasons. Custom actions and reasons can be added
• Flow Configuration: Each action can be associated with a specific UI flow (which pages and fields are shown) and an approval rule set

Termination in Oracle HCM Cloud ends a worker's active work relationship with a legal employer. It is a critical process that impacts Payroll, Benefits, IT Access, and Absence.

• Key Fields: Action (Termination), Action Reason (Resignation / Redundancy etc.), Termination Date (Last Working Day), Notified Date, Projected Termination Date
• Last Day vs Termination Date: The Termination Date is the last day the employee is active. Payroll processes up to and including this date. Access is revoked the next day (unless configured differently)
• Multiple Assignments: If a worker has multiple assignments, each must be terminated individually unless a global termination option is used
• Checklist/Offboarding: Termination can trigger an offboarding checklist — tasks for HR, IT, Finance, and the manager (e.g., collect laptop, revoke access, final payroll)
• Rehire Eligibility: A flag can be set at termination indicating whether the person is eligible for rehire. This is checked when the person's record appears in future hiring processes
• Reversing a Termination: Oracle allows reversal of a termination if processed in error — the work relationship is reinstated without creating a new hire record

Both Promotion and Transfer create a new effective-dated assignment record, but they represent different business events:

• Promotion: An upward career move — typically involves a Grade or Job change to a higher level and usually triggers a salary increase. The action type is "Promotion" and drives specific approval flows (often requiring compensation review)
• Transfer: A lateral or location move — changing Department, Location, Manager, or Business Unit without necessarily changing Grade or salary. Can be local (same legal employer) or global (different legal employer)
• Configuration Difference: Different Action types can be configured with different UI flows — a Promotion might show compensation fields prominently, while a Transfer might emphasise location and department fields
• Combined Actions: A worker can receive a Promotion-Transfer — a simultaneous grade increase AND department/location change. This is handled as a single transaction with both action/reason selected

Assignment Status Types represent the current state of a worker's assignment and drive downstream processing in Payroll, Benefits, and Absence.

• System-Defined Statuses: Active – Payroll Eligible, Active – No Payroll, Suspended – Payroll Eligible, Suspended – No Payroll, Inactive
• Custom Statuses: Organisations can create custom assignment status types mapped to a system status. For example, "On Maternity Leave" mapped to "Suspended – Payroll Eligible" or "Long-Term Sick" mapped to "Suspended – No Payroll"
• Payroll Impact: Only assignments with a status mapped to "Active – Payroll Eligible" or "Suspended – Payroll Eligible" are picked up by the payroll run. Changing status to "Suspended – No Payroll" stops payroll without terminating the record
• Benefits Impact: Benefits eligibility rules can reference assignment status — e.g., workers on unpaid leave may lose certain benefit entitlements
• Configuration: Setup and Maintenance → Manage Assignment Status Types

• Employee Self-Service (ESS): Allows employees to view and update their own information without HR involvement — e.g., update personal address, emergency contacts, bank account details, request name change, view payslips and tax documents
• Manager Self-Service (MSS): Allows line managers to manage their team directly — initiate transfers, promotions, salary changes, terminations, approve absence requests, and view team analytics
• HR Efficiency: ESS and MSS reduce HR's administrative burden by distributing routine transactions to the people who initiate them
• Approval Integration: MSS-initiated transactions can be routed through approval workflows before the change is committed, ensuring governance without removing manager autonomy
• Mobile Support: Oracle HCM Cloud's responsive UI supports ESS and MSS on mobile devices through the HCM Cloud mobile app

• Position Name and Code: Unique identifier and display name
• Job: The job that this position is a specific instance of
• Business Unit and Department: Workforce structure to which the position belongs
• Location: Physical work location associated with the position
• Grade: Expected grade/pay band for the position — drives salary offer validation
• Full-Time Equivalent (FTE): The FTE allocation (e.g., 1.0 for full-time, 0.5 for part-time)
• Headcount: The approved number of workers allowed in the position
• Position Type: Single Incumbent (only one person), Shared, or Pooled
• Hiring Status: Active (accepting new hires), Frozen (no new hires), Eliminated
• Reports-To Position: The parent position in the position hierarchy

Position Synchronisation is an Oracle HCM feature that automatically updates a worker's assignment attributes whenever the associated position is updated.

• How it works: When enabled, changes made to a position (e.g., department change, grade change, location change) are automatically propagated to all workers assigned to that position
• Configuration: Enabled via Setup and Maintenance → Manage Position Synchronisation. Administrators select which position attributes to synchronise (Job, Department, Location, Grade, FTE)
• Effective Dating: Synchronisation is effective-dated — position changes propagate to assignments with the same effective date, maintaining full audit history
• Override Option: Certain attributes can be overridden at the assignment level even when position synchronisation is enabled — useful for exceptions
• Use Case: Most useful in organisations with strict position-based models where the position definition drives all assignment attributes, reducing manual data entry

Oracle provides position-based headcount control to prevent over-hiring beyond approved budgets.

• Maximum Headcount: Each position has a maximum number of incumbents. When the current headcount reaches the maximum, the system warns or blocks new assignments to that position
• Hiring Allowed Flag: Positions can be set to "Hiring Frozen" to stop new hires without changing the position structure
• Recruiting Integration: Oracle Recruiting Cloud checks position headcount before allowing a requisition to be created — if a position is at capacity, the recruiter is notified
• Workforce Budgeting Integration: Oracle Workforce Compensation and Position Budgeting modules can enforce budget control at position level — blocking new hires if budget is exhausted
• Reporting: Vacancy reporting shows positions with approved headcount greater than current incumbents — useful for talent acquisition prioritisation

Position and Supervisor hierarchies represent different perspectives of the reporting structure in Oracle HCM Cloud.

• Position Hierarchy: Defined at the position level using the "Reports-To Position" field. It represents the role-based reporting structure — independent of who currently holds the positions. Useful for succession planning and org design
• Supervisor Hierarchy: Defined on each worker's assignment by assigning a Line Manager. It represents the person-based reporting structure — who each worker's actual manager is today
• Difference: In a position hierarchy, the CEO position always reports to the Board regardless of who holds the CEO role. In a supervisor hierarchy, the current CEO person is the manager of their direct reports — if the CEO changes, all direct reports must be updated
• Approval Routing: Both hierarchies can be used to route approvals in Oracle BPM workflow — position hierarchy is more stable for approval routing since it doesn't change when people leave
• Security: HCM Data Roles can use either hierarchy to define which workers a manager can view/update — supervisor hierarchy is more commonly used for operational access

• Headcount: A simple count of the number of people (worker records). One person = 1 headcount, regardless of whether they work full-time or part-time
• FTE (Full-Time Equivalent): A measure of working capacity normalised to full-time hours. A full-time employee = 1.0 FTE. A part-time employee working 50% of full-time hours = 0.5 FTE
• Position FTE: Each position carries an FTE allocation. A position with 2.0 FTE can accommodate two full-time workers or four part-time workers at 0.5 FTE each
• Reporting: Workforce analytics often show both metrics separately — headcount shows people, FTE shows capacity. A large part-time workforce will have high headcount but lower FTE
• Workforce Planning: FTE is more meaningful for budgeting and capacity planning; headcount is more meaningful for benefits administration (e.g., some benefits are per-head regardless of FTE)

Oracle Absence Management (part of Oracle Global HR) manages all types of worker absence — planned, unplanned, statutory, and accrued leave.

• Absence Types: Define the category of leave — Annual Leave, Sick Leave, Maternity Leave, Unpaid Leave, Public Holiday. Each absence type maps to an Absence Category
• Absence Plans: Define accrual rules, entitlement amounts, balance carry-forward rules, and eligibility criteria. Plans can be accrual-based (balance builds over time) or entitlement-based (fixed allocation per year)
• Absence Reasons: Further classification within an absence type — e.g., Sick Leave reasons: Medical, Family Care, Mental Health
• Work Schedules: The work schedule assigned to an employee determines how absence days/hours are calculated (a 4-day worker has a different absence count than a 5-day worker)
• Payroll Integration: Absence entries generate payroll inputs — e.g., approved annual leave triggers a payment; unpaid leave generates a deduction

An Accrual Plan is the rule set that defines how a worker's absence balance accumulates over time.

• Accrual Rate: Defines how much leave accrues per period — e.g., 1.25 days per month = 15 days per year
• Accrual Frequency: How often the balance is credited — Monthly, Bi-weekly, Annual (lump sum at start of year)
• Ceiling: Maximum balance a worker can accumulate. If balance reaches the ceiling, no further accrual occurs until leave is taken
• Carry-Over Rules: At year-end, unused balance can be carried forward (with or without a cap), lapsed (lost), or paid out as a cash allowance
• Eligibility Criteria: Plans can have eligibility rules — e.g., an enhanced accrual rate for employees with >5 years of service, or a higher entitlement for senior grades
• Balance Disbursement: When an absence is entered, Oracle deducts from the accrual plan balance and validates that sufficient balance exists (warning or blocking if insufficient)

Work Schedules define the days and hours a worker is expected to work. They are critical for accurately calculating absence duration.

• Schedule Types: Standard (Mon–Fri, 8 hrs/day), Compressed (Mon–Thu, 10 hrs/day), Shift-based, Part-Time, Flexible
• Absence Duration Calculation: When an employee records an absence from Monday to Wednesday, the system uses their work schedule to determine that this is 3 working days (not calendar days), avoiding incorrect deductions
• Public Holidays: Work schedules can be linked to a Work Schedule Holiday Calendar. If a public holiday falls during an absence period, it is excluded from the absence duration
• Time and Labour: Work schedules are also used in Oracle Time and Labour for scheduled vs. actual hours comparison
• Eligibility: Some absence plans restrict eligibility based on work schedule (e.g., a flex-time leave plan only applies to workers on a flexible schedule)

Absence Management and Payroll are tightly integrated in Oracle HCM Cloud, with absence events automatically generating payroll inputs.

• Payroll Absence Element: Each Absence Type is linked to a Payroll Element. When an absence is approved, Oracle automatically creates an element entry on the worker's assignment for the payroll period
• Paid vs Unpaid: Annual leave generates a "Paid Leave" element that ensures the worker receives normal pay. Unpaid leave generates a "Unpaid Leave Deduction" element that reduces gross pay accordingly
• SSP/SMP (UK) / Sick Pay Schemes: Country-specific statutory schemes (Statutory Sick Pay, Maternity Pay) use Absence Management to track qualifying days, then generate the correct statutory payment elements in Payroll
• Retrospective Absence: If an absence is entered or updated after payroll has run, a retrospective payroll calculation adjusts the next pay period for any underpayment or overpayment
• Absence and Costing: Absence types can be configured to re-cost the worker's salary to a different cost centre (e.g., maternity leave cost posted to an HR overhead account rather than the department)

• Absence Category: The broadest grouping of leave at the system level — e.g., Illness, Personal, Family. Used for high-level reporting and legislative classification
• Absence Type: A specific leave type within a category — e.g., within Personal: Annual Leave, Floating Holiday. The Absence Type is what employees select when submitting a leave request
• Absence Plan: The rule engine behind an Absence Type — it defines accrual rates, entitlement amounts, eligibility rules, carry-forward, and ceiling. One Absence Type can link to one or multiple Plans (e.g., different accrual rates by years of service)
• Summary: Category → Type → Plan is the configuration hierarchy. Employees see Types; Plans are the underlying rules governing balance accumulation and consumption

Oracle HCM Cloud uses a Role-Based Access Control (RBAC) model with the following role types:

• Abstract Roles: High-level roles that represent a class of users — Employee, Manager, HR Specialist, Line Manager. These are assigned to all people in that category and grant access to self-service functions
• Job Roles: Represent a specific job function in the organisation — e.g., Human Resource Analyst, Payroll Manager, Benefits Administrator. They aggregate Duty Roles to grant functional access
• Duty Roles: Represent a specific task or set of tasks — e.g., "Manage Worker Assignment" or "View Employment Details." They are the building blocks aggregated into Job Roles
• Data Roles: Combine a Job Role with a Data Security Profile (Person Security Profile, Organisation Security Profile) to define WHAT data a user can see. A user might have the "Human Resource Analyst" job role restricted to employees in India only via a data role
• Role Assignment: Users are assigned Abstract Roles automatically (based on worker type) and Job/Data Roles manually or via auto-provisioning rules

A Person Security Profile defines which worker records a user can access. It is one of three HCM Security Profiles (Person, Organisation, Legislative Data Group).

• Access Types: View All Workers, View Own Record, View Workers in Reporting Hierarchy, View Workers in Department, View Workers by Organisation Security Profile
• Manager Self-Service: Managers are typically assigned a Person Security Profile that gives them access to their direct and indirect reports (via the supervisor hierarchy). This means a manager can see, edit, and transact on their team's records only
• HR Specialist: An HR specialist might have a Person Security Profile scoped to a specific country or business unit — e.g., "India HR Analyst" sees only Indian employees
• Configuration: Created in Setup and Maintenance → Manage Person Security Profiles then combined with a Job Role to form a Data Role in Manage HCM Data Roles
• Custom Criteria: Person Security Profiles can include custom SQL-based criteria for complex filtering (e.g., view only workers with a specific assignment attribute)

HCM Data Roles and LDAP roles serve different purposes in the Oracle security model:

• HCM Data Roles: Defined within Oracle HCM Cloud and combine a Job Role with an HCM Security Profile. They restrict which records a user can access and what actions they can take on those records
• LDAP/Identity Roles (OIM roles): Defined in Oracle Identity Management or the Fusion Security Console and control which application functions (pages, tasks, workflows) a user can access
• Together: A complete access configuration requires both — the LDAP role grants access to the HR Analyst function pages, and the HCM Data Role restricts which employee records are visible within those pages
• Role Provisioning: Roles can be auto-provisioned based on worker attributes (e.g., all workers with Job = "HR Analyst" automatically get the HR Data Role for their Business Unit)
• Role Assignments in HCM: Managed via My Roles on the worker's record or via bulk provisioning in Manage Role Provisioning Rules

Aggregate Privileges are a type of role in Oracle Fusion that group a set of Function Security Privileges (permissions to run specific tasks or view specific pages) into a reusable package.

• Purpose: They simplify role design by bundling related privileges — e.g., "Manage Employment" aggregate privilege includes "Create Assignment", "Edit Assignment", "Terminate Employment" privileges
• Hierarchy: Privilege → Aggregate Privilege → Duty Role → Job Role → Data Role → User
• Customisation: Oracle recommends not modifying Oracle-delivered Aggregate Privileges directly. Instead, create a custom Duty Role that includes the required Aggregate Privileges and add it to a custom Job Role
• Security Console: Managed in Tools → Security Console → Roles. The role hierarchy visualisation shows all inherited privileges
• Audit Impact: Aggregate Privileges are tracked in the Audit Report — changes to them affect all Job Roles that inherit them, so change management is important

Role Auto-Provisioning automatically assigns roles to workers based on their HR attributes — eliminating the need for manual role assignment in most cases.

• Provisioning Rules: Configured in Setup and Maintenance → Manage Role Provisioning Rules. Rules are condition-action pairs: IF worker has Job = "HR Manager" THEN assign role "Human Resource Manager"
• Trigger Events: Auto-provisioning fires on hire, transfer, promotion, and termination — ensuring roles are always aligned with the current employment record
• De-provisioning: When a worker transfers out of a role that triggered provisioning, the role is automatically removed. This prevents stale access
• Manual Roles: Some roles require manual assignment (e.g., system administrator roles). These are not subject to auto-provisioning rules and persist through transfers
• Role Request Workflow: Users can also request additional roles through a self-service request, which routes through an approval workflow before provisioning

Oracle Business Process Management (BPM) is the workflow engine embedded in Oracle HCM Cloud that routes HR transactions through approval chains before they are committed to the database.

• How it works: When a manager submits a promotion, BPM evaluates approval rules and sends the transaction to the appropriate approver(s) via worklist notifications and email
• Approval Types: Sequential (one approver at a time), Parallel (all approvers simultaneously), First-Responder-Wins (first to approve commits the transaction)
• Worklist: Pending approvals appear in the approver's BPM Worklist (Navigator → Worklist) and as bell notifications in HCM Cloud
• Rule Configuration: BPM rules are managed via Setup and Maintenance → Manage Approval Rules for Human Capital Management
• Actions Available: Approve, Reject, Request Information (suspends the workflow), Reassign, Withdraw (by initiator)

Approval rules for salary changes can be configured with conditions based on the transaction attributes — allowing different approval chains based on the magnitude or type of change.

• Path: Setup and Maintenance → Manage Approval Rules for Human Capital Management → Salary
• Rule Conditions: Conditions can reference attributes like Salary Change %, New Salary Amount, Grade, Business Unit, Legal Employer, Worker Type
• Example Rule: IF Salary Change % > 10% THEN route to Line Manager AND HR Director sequentially; ELSE route to Line Manager only
• Approver Types: Supervisory Hierarchy Level (e.g., 1 level above), Named User, Job Role (anyone with HR Director role), Position Hierarchy Level
• Deadlines and Escalations: Rules can include a time limit — if not actioned within X days, the workflow escalates to the next level or auto-approves

HCM Notifications alert workers, managers, and HR about HR events — approval requests, process completions, data changes, and reminders.

• Notification Types: Action Required (approval pending), Informational (process completed), Alert (threshold exceeded — e.g., contract expiry)
• Delivery Channels: In-app bell notifications, Email (via SMTP server), Mobile push (via HCM mobile app)
• Transaction Design Studio: My Client Groups → HCM Experience Design Studio → Transaction Design Studio — allows configuring which notifications are sent for each HR transaction
• Alert Rules: Configured in Tools → Alerts Composer. Custom alerts can be created based on HCM data conditions — e.g., alert HR when a fixed-term contract expiry is within 60 days
• Templates: Email notification templates are managed in Oracle BI Publisher — HTML email templates with HCM data merge fields

Transaction Design Studio (TDS) is a no-code configuration tool in Oracle HCM Cloud that allows HR to customise the appearance and behaviour of HR transactions without developer involvement.

• Capabilities: Show/hide fields, make fields required or read-only, configure default values, change field labels, reorder sections on transaction pages
• Context-Sensitive Rules: TDS rules can be conditional — e.g., show the "Visa Expiry Date" field only for non-citizen workers; make "End Date" mandatory for contract workers but optional for permanent employees
• Scope: Works across Hire, Add Assignment, Transfer, Promotion, Salary Change, Termination, and other HR transactions
• No Personalisation vs TDS: Page Composer/Personalisation operates at page UI level; TDS operates at transaction flow level — TDS changes apply across all users by condition, not per-user personalisation
• Path: My Client Groups → HCM Experience Design Studio → Transaction Design Studio → select Action → configure rules

• Definition: An HR Checklist is a structured to-do list assigned to a worker, HR, or manager during key HR events — onboarding (new hire), offboarding (termination), or role change
• Tasks: Each checklist contains tasks with owners (Employee, Manager, HR, IT), due dates, and completion tracking. Tasks can be manual (checklist items) or automated (trigger a system action)
• Onboarding Use: A new hire checklist might include: "Complete Personal Details," "Upload Photo ID," "Attend Orientation," "Set Up Laptop" — distributed across HR, IT, and the employee
• Offboarding Use: Termination checklist: "Collect Laptop," "Revoke System Access," "Process Final Pay," "Exit Interview Scheduled"
• Configuration: Setup and Maintenance → Manage Checklists → Manage Checklist Templates. Templates define the tasks; instances are created when the triggering event occurs

Oracle HCM Cloud offers multiple reporting tools, each suited to different use cases and user skill levels:

• OTBI (Oracle Transactional Business Intelligence): Self-service ad-hoc reporting tool using pre-built Subject Areas. Drag-and-drop interface for HR users. Reports are based on real-time transactional data
• Oracle Analytics Cloud (OAC) / OBIA: Enterprise analytics platform for complex dashboards, predictive analytics, and cross-pillar reporting (HR + Finance + ERP)
• HCM Extracts: A structured, configurable extract framework for extracting HR data in various formats (XML, CSV, delimited) for integration with external systems
• BI Publisher (BIP): Pixel-perfect report generation — used for pay slips, letters, contracts, and statutory reports. Reports can be output to PDF, Excel, Word, HTML
• Workforce Management Analytics: Pre-built Oracle dashboards for headcount, turnover, absence, and diversity analytics embedded in the HCM Cloud UI

HCM Extracts are a specialised reporting tool in Oracle HCM Cloud designed to extract worker and HR data in structured, configurable formats for downstream systems and regulatory reporting.

• Use Cases: Payroll-to-benefits integration, employee data files for pension providers, regulatory reporting (EEO, GDPR, statutory filings), data migration validation
• Components: Extract Definition (what data to extract), Extract Criteria (filtering conditions), Extract Delivery (output format and delivery location — SFTP, UCM, email)
• Data Groups: Extracts are structured in hierarchical Data Groups — Root Group (Persons), Child Groups (Assignments, Salaries, Addresses). This mirrors the HCM data model
• Fast Formula Integration: Extracts support Oracle Fast Formula for derived or calculated fields — e.g., calculate age from DOB, determine pension eligibility, format national ID
• Scheduling: Extracts can be scheduled via Scheduled Processes to run automatically at defined intervals (daily, weekly, monthly)

Oracle Fast Formula is Oracle's proprietary formula language for writing custom business logic within Oracle HCM Cloud without requiring traditional programming.

• Syntax: A simple, English-like scripting language supporting variables, conditions (IF/THEN/ELSE), loops, and calls to database functions
• Use Cases in Global HR: Eligibility rules for absence plans, accrual calculation rules, validation rules for custom fields, HCM Extract derived fields, payroll element formulas, grade rate calculations
• Formula Types: Each formula is associated with a Formula Type — e.g., Accrual Formula Type, Extract Formula Type, Payroll Element Formula Type — each type has different context variables available
• Configuration: Created and tested in My Client Groups → Fast Formulas. Formulas can be compiled and tested with sample data before deployment
• Common Functions: GET_VALUE_SET(), GET_TABLE_VALUE(), ADD_MONTHS(), ROUND(), CONVERT_PERIOD()

OTBI Subject Areas are pre-built analytical schemas that expose HCM transactional data in a business-friendly, dimensional model for self-service reporting.

• Key HR Subject Areas: Workforce Management - Worker Assignment Real Time, Absence Management - Absence Transaction Real Time, Compensation - Salary Real Time, Talent Management - Performance Rating Real Time
• Dimensions and Facts: Subject Areas contain Dimension folders (Worker, Assignment, Department, Location, Time) and Fact folders (FTE, Headcount, Salary Amount)
• As-Of Date: Most HR subject areas support an "Effective Date" prompt — allowing reports to show the state of the workforce at any specific date (e.g., headcount on 31-Dec-2023)
• Security: OTBI respects HCM Data Security — a manager running an OTBI report only sees data for their own workers based on their Person Security Profile
• Combination Reports: Multiple Subject Areas can be joined in a single analysis if they share common dimensions (e.g., combining headcount with salary data using the Worker dimension as the join key)

• Scheduled Process: A background program that performs a processing action — e.g., Run Payroll, Process Accruals, Import HR Data, Calculate Workforce Forecasts. It changes data or performs calculations. Managed via Tools → Scheduled Processes
• Report: A read-only output that presents existing data in a formatted view — OTBI analysis, BI Publisher report, HCM Extract. Reports do not change data; they present it
• Relationship: Some Scheduled Processes generate report outputs (e.g., the "Run HCM Extract" process runs a data extract process and delivers a file). The distinction is: does it change data or only read it?
• Scheduling: Both can be scheduled via Scheduled Processes. Reports can also be scheduled via Oracle BI Catalog for automatic email delivery

HCM Data Loader (HDL) and HCM Spreadsheet Data Loader (HSDL) are the two primary tools for bulk-loading HR data into Oracle HCM Cloud.

• HDL (HCM Data Loader): A file-based bulk loading tool using .dat files (pipe-delimited). Designed for large-scale data migration and integration — tens of thousands of records. Used by technical consultants and integration developers. Supports all HCM objects (Person, Employment, Salary, Absence, Benefits, etc.)
• HSDL (HCM Spreadsheet Data Loader): Excel-based loading tool for HR users and smaller data sets (hundreds to a few thousand records). Less technical — HR admins can use it without developer involvement. Ideal for ongoing data maintenance tasks (e.g., bulk grade updates, location changes)
• When to use HDL: Initial data migration, large-scale integrations, complex object loading (nested data like assignments + salaries in one load), automated nightly integration feeds
• When to use HSDL: Ad-hoc bulk updates, HR admin corrections, small-scale periodic loads where business users manage the process
• Error Handling: Both tools provide error reports. HDL generates a process log and error file; HSDL highlights errors in the Excel sheet for easy correction

HDL files use a specific pipe-delimited format with METADATA and DATA records for each business object.

METADATA|Worker|PersonId|PersonNumber|StartDate|LegislationCode
DATA|Worker||EMP001|2024-01-15|IN

METADATA|PersonName|PersonId|PersonNumber|LegislationCode|FirstName|LastName|NameType|StartDate
DATA|PersonName||EMP001|IN|Ravi|Kumar|GLOBAL|2024-01-15

METADATA|WorkRelationship|PersonId|PersonNumber|LegislationCode|LegalEntityId|StartDate|WorkerType
DATA|WorkRelationship||EMP001|IN|300000001234567|2024-01-15|E

• METADATA row: Defines which attributes (columns) are being loaded for that business object
• DATA row: Contains the actual values for each record
• Object Order: Parent objects must precede child objects in the file — Worker before PersonName, before WorkRelationship, before Assignment
• Source System Keys: Use SourceSystemOwner and SourceSystemId for cross-referencing records from legacy systems
• Submission: Files are zipped and submitted via Tools → Import and Load Data → Load HCM Data

Flexfields are Oracle's mechanism for extending the data model without modifying base application code — a cornerstone of Oracle cloud customisation strategy.

• Descriptive Flexfields (DFF): Add additional attributes to an existing form/page. For example, adding a "Cost Centre Override" field to the Assignment page. DFFs are context-sensitive — different sets of fields can appear based on a context value (e.g., different fields for Permanent vs Contract workers)
• Extensible Flexfields (EFF): More powerful than DFFs — allow creating multiple context categories, each with its own set of attributes. Used for complex extensions like adding a "Visa Information" section with multiple fields to the Person record, or "Vehicle Details" to the Assignment. EFFs support multiple rows per context
• Key DFF Examples in HR: Person DFF, Assignment DFF, Location DFF — each appears on the respective HR page as an "Additional Information" section
• Key EFF Examples: Person Extensible Flexfield (for passport, visa, professional licence data), Assignment Extensible Flexfield (for union data, remote work details)
• Configuration: Setup and Maintenance → Manage Descriptive Flexfields or Manage Extensible Flexfields — requires deployment after configuration to make changes visible in the UI

Oracle HCM Cloud provides a comprehensive REST API for real-time integration — enabling external systems to read, create, update, and delete HR data programmatically.

• Key HR REST Resources: /hcmRestApi/resources/11.13.18.05/workers, /emps, /assignments, /persons, /absences, /positions
• Use Cases: Real-time new hire notification to IT systems, Active Directory synchronisation, mobile app HR self-service, third-party time & attendance integration, chatbot HR queries
• Authentication: OAuth 2.0 or Basic Authentication. For system-to-system integration, OAuth 2.0 with a dedicated integration user is recommended
• Query Parameters: Supports OData-style filtering — e.g., ?q=PersonNumber=EMP001, ?fields=PersonId,DisplayName,AssignmentStatus, ?expand=assignments
• Rate Limits: Oracle applies throttling on REST API calls — integrations must implement retry logic and respect HTTP 429 responses

ATOM Feeds (also called HCM Cloud Change Detection feeds) are a publish-subscribe mechanism that notifies external systems of changes to HCM data in near-real-time.

• How it works: When an HR event occurs (new hire, transfer, termination, salary change), Oracle HCM publishes an ATOM entry for that change. Subscribing systems poll the ATOM feed endpoint to retrieve only the records that changed since their last poll
• Efficiency: Instead of a full daily extract, ATOM Feeds deliver only delta changes — significantly reducing data volume and improving integration latency
• Objects Supported: Worker, Assignment, Salary, Absence, Benefits Enrolment, Position, Department — most core HR objects have ATOM feeds
• Use Cases: LDAP/AD synchronisation (trigger user provisioning on hire), Payroll middleware (catch salary changes for payroll system), Security tool feeds (revoke access on termination)
• Configuration: ATOM feeds are accessed via a URL with authentication. Oracle Integration Cloud (OIC) has native connectors for polling HCM ATOM feeds

A Pending Worker is a pre-hire record created for a candidate who has accepted a job offer but has not yet started. It enables pre-onboarding activities before the first working day.

• Timing: Created when an offer is accepted in Oracle Recruiting Cloud — the candidate is automatically converted to a Pending Worker record in Core HR
• Use Cases: IT equipment provisioning (laptop ordered before day 1), system access setup (accounts created ready for first day), background check tracking, pre-hire document collection (tax forms, bank details), compliance training
• Conversion to Employee: On the actual start date, the Pending Worker record is converted to an active Employee record — no re-entry needed. All data captured in pre-hire is carried over
• Person Number: The Pending Worker receives a Person Number at creation — ensuring a stable identifier from offer acceptance through the full employment lifecycle
• Security: Pending Workers can be granted limited system access (e.g., intranet, benefits enrolment portal) via role provisioning rules that apply to the Pending Worker abstract role

Document Records is the Oracle HCM Cloud functionality for managing employee documents — certificates, contracts, visas, licenses, and compliance records — associated with a worker's profile.

• Document Types: Configured document categories like Visa, Passport, Professional Licence, Educational Certificate, Employment Contract, Performance Review
• Expiry Tracking: Each document type can have an expiry date. Oracle HCM Cloud provides expiry alerts — notifying HR and the worker when a document (e.g., work visa) is approaching expiry
• Attachments: Actual files (PDF, images) can be attached to a document record for a paperless document store
• Visibility: Document visibility can be restricted — some documents are visible only to HR, others are visible to the employee, and some to both
• Configuration: Setup and Maintenance → Manage Document Types — define categories, required attributes, expiry rules, and visibility settings

A Salary Basis defines how a worker's salary is expressed — the frequency and unit of the stated salary amount.

• Salary Basis Types: Annual Salary (expressed as annual total), Monthly Salary (expressed per month), Hourly Rate (expressed per hour), Daily Rate
• Annualisation Factor: The salary basis includes an annualisation factor to convert the stated amount to an annual figure for comparison and budgeting. Monthly × 12 = Annual; Hourly × 52 weeks × contracted hours = Annual
• Grade Rate Link: A salary basis is linked to a Grade Rate — when a worker's salary is saved, Oracle validates it against the minimum and maximum of the grade rate for their grade
• Payroll Element: Each salary basis is linked to a payroll element that carries the salary amount into the payroll run
• Configuration: My Client Groups → Compensation → Salary Bases. Different salary bases can exist per Legislative Data Group to handle different country pay norms

Oracle HCM Cloud Global HR implementations follow a structured approach using Oracle's AIM/OUM methodology or the Agile-based Oracle Implementation Methodology (OIM).

• Phase 1 – Discovery & Analysis: Gather business requirements, document As-Is HR processes, identify gaps between Oracle standard and client requirements
• Phase 2 – Design: Design Enterprise Structure (Legal Entities, BUs, LDGs), Workforce Structures (Jobs, Grades, Departments), Security Model, Integration Architecture, and Data Migration Strategy
• Phase 3 – Build & Configuration: Configure Oracle HCM in the development environment — Enterprise Setup, Lookups, Flexfields, Absence Plans, Security Profiles, BPM Approval Rules, TDS configuration
• Phase 4 – Data Migration: Design HDL templates, extract data from legacy systems, cleanse data, perform test loads, validate data quality
• Phase 5 – Testing: SIT (System Integration Testing), UAT (User Acceptance Testing), payroll parallel runs, regression testing after updates
• Phase 6 – Training & Change Management: Train HR admins, managers, and employees on new processes; create training materials and job aids
• Phase 7 – Go-Live & Hypercare: Production cutover, final data migration, go-live support, hypercare period monitoring

Oracle HCM Cloud supports multiple concurrent work relationships for a single person, enabling scenarios where someone is employed by more than one legal entity simultaneously.

• Multiple Work Relationships: A person can have two active work relationships — one as an employee with Legal Employer A and another as a part-time employee or contingent worker with Legal Employer B
• Primary vs Secondary: One work relationship is designated as Primary (driving the person's primary HR record, payslip, and benefits). Others are Secondary
• Payroll: Each legal employer runs its own payroll separately. The two payrolls do not automatically consolidate — statutory tax calculations may need manual coordination (P45/P46 in UK, Form 16 in India)
• Security: HR administrators in Legal Employer A see only that work relationship; HR in Legal Employer B sees their own. Only a super-user with cross-entity access sees both
• Person Number: The Person Number remains unique across the enterprise — the same person is not duplicated. Both work relationships hang off the same Person record

Lookups are configurable value lists (drop-downs) used throughout Oracle HCM Cloud. They control the available options for fields like Marital Status, Ethnicity, Nationality, Action Reason, and many others.

• Lookup Types: Each drop-down field is driven by a Lookup Type — e.g., MARITAL_STATUS lookup type contains values: Single, Married, Divorced, Widowed
• Extensibility: Oracle marks lookups as "User" (fully customisable), "Extensible" (add new values but cannot delete Oracle-delivered ones), or "System" (read-only — cannot be modified)
• Configuration: Setup and Maintenance → Manage Common Lookups or Manage HCM Lookups. Lookup values can be enabled/disabled and assigned start/end dates
• Translation: Lookup values support multi-language — the same code can display different labels in English, French, Arabic, etc. based on the user's language preference
• Reporting: OTBI and HCM Extracts expose lookup codes (e.g., M, S, D) and lookup meanings (e.g., Married, Single, Divorced) — consultants should always report on meanings, not codes

Oracle HCM Cloud includes a Workforce Modeling and Predictions feature (part of Oracle Analytics for Cloud HCM) that uses AI/ML to model workforce scenarios and predict future HR outcomes.

• Org Chart Modeling: HR can create "what-if" scenarios — model restructuring options, mergers, headcount reductions — without affecting live data. Multiple versions can be saved and compared
• Attrition Prediction: Oracle's embedded AI engine predicts which employees are at risk of leaving based on engagement, tenure, compensation, manager rating, and promotion history
• Workforce Forecasting: Projects future headcount, cost, and skill requirements based on current trends and business growth assumptions
• Diversity Analytics: Tracks gender, ethnicity, and age distribution across levels and functions — highlighting pay equity gaps and representation trends
• Access: Available via My Client Groups → Workforce Modeling and Oracle Analytics for HCM dashboards

The Oracle HCM Cloud Audit Framework tracks who changed what data, when, and from what value to what value — providing a complete audit trail for compliance and governance.

• Audit Objects: Administrators select which business objects and attributes to audit — e.g., Salary Amount, Assignment Status, Grade, Legal Employer. Over-auditing impacts performance, so targeted auditing is recommended
• Configuration: Setup and Maintenance → Manage Audit Policies → Oracle Fusion Applications → Human Capital Management
• Audit Report: Accessible via Navigator → Audit Reports. Reports can be filtered by user, object, date range, and attribute. Shows old value, new value, timestamp, and username
• Compliance Use Cases: SOX compliance (salary changes), GDPR (personal data access and modification), internal audit (HR data integrity checks)
• Data Retention: Oracle retains audit data according to the configured retention period. Long retention periods increase storage costs — balance compliance requirements against storage budgets

• Payroll Relationship: The link between a worker and a payroll. It is created automatically when a worker is assigned a payroll definition on their employment record
• Relationship to Work Relationship: A single Work Relationship (Legal Employer) can have one Payroll Relationship. The payroll processes all assignments under that work relationship in a single payroll run
• Payroll Definition: Specifies the pay frequency (Monthly, Weekly, Bi-weekly), the processing currency, and the legislative data group for payroll rules
• Impact of Termination: Terminating the work relationship ends the payroll relationship — the final payroll period is determined by the termination date. Payroll processes the final payment and balance finalisation
• Global Transfer: A global transfer creates a new payroll relationship under the new legal employer — old payroll relationship is closed and finalised

• Holiday Calendars: Oracle provides a Work Schedule Holiday Calendar to define public holidays for specific countries/regions and years
• Assignment: Holiday calendars are linked to Work Schedules. Workers on a particular schedule observe the holidays in the calendar attached to that schedule
• Country-Specific: Different countries have different public holidays. A UK worker's schedule references the UK holiday calendar; an India-based worker references the India calendar
• Absence Impact: When a public holiday falls within an employee's approved absence period, the holiday is excluded from the absence duration (e.g., 5 days of annual leave over a week with a public holiday = 4 days of leave consumed)
• Configuration Path: My Client Groups → Workforce Management → Work Schedules → Manage Holiday Schedules

Profile Options are configurable parameters that control default system behaviour and feature enablement across Oracle HCM Cloud.

• Definition: Key-value pairs that switch on/off features or set default values — e.g., whether position is mandatory on assignment, whether salary range validation blocks or warns, or the default currency for a business unit
• Profile Levels: Site (applies to all users), Product (applies to a specific module), User (applies to a specific user). Site-level settings are overridden by Product, then User levels
• HR-Specific Examples: PER_PERSON_NUMBER_GENERATION_METHOD (manual vs automatic person numbers), ORA_PER_POSITIONS_REQUIRED (force position on assignment), ORA_PER_GRADE_LADDER (enable grade ladders globally)
• Configuration: Setup and Maintenance → Manage Profile Options and Manage Administrator Profile Values
• Testing: Profile option changes should always be tested in a non-production environment as they can have broad systemic impacts

• Value Set: A validation set for flexfield attributes. It defines the allowed values and their format for a custom flexfield segment. Value Sets can be Independent (a fixed list), Table-validated (SQL-based dynamic list from any database table), Format-only (data type/format validation without a fixed list), or Dependent (child list filtered based on a parent segment value)
• Lookup: A simpler, UI-managed list of values for standard application fields. Lookups are managed by functional users in the Setup workbench without SQL knowledge
• Key Difference: Value Sets are primarily used with flexfields for custom attributes; Lookups are used for standard Oracle-delivered fields. Value Sets are more powerful (table-validated) but more technically complex to set up
• Where to use which: For a custom dropdown on a DFF or EFF, use a Value Set. For customising the values in a standard Oracle field (e.g., Action Reason), use a Lookup

Oracle Integration Cloud (OIC) is Oracle's cloud-based iPaaS (Integration Platform as a Service) for connecting Oracle and non-Oracle applications.

• HCM Integration: OIC has pre-built Oracle HCM Cloud adapters that connect to HCM REST APIs, ATOM Feeds, and File-based integrations (HDL/HCM Extracts) with low-code configuration
• Common Use Cases: HCM → Active Directory/LDAP sync on hire/termination, HCM ↔ Benefits carrier file exchange, HCM → ERP (for costing), HCM → Background Check vendors, HCM → Learning Management Systems
• Prebuilt Recipes: Oracle provides pre-built integration templates (recipes) for common HCM integrations — significantly accelerating implementation time
• Process Automation: OIC includes Process Cloud (BPM) for orchestrating complex multi-step workflows that span multiple systems — e.g., new hire triggering IT provisioning, badge creation, and benefits enrolment across three systems simultaneously
• Monitoring: OIC provides a dashboard for monitoring integration run status, errors, and retry management — essential for production support

• Definition: The Contract record in Oracle HCM Cloud holds the formal employment contract terms associated with a worker's employment — separate from the assignment but linked to the work relationship
• Key Fields: Contract Type (Permanent, Fixed-Term, Agency, Zero-Hours), Contract Start/End Date, Contract Document Reference, Notice Period, Probation End Date
• Fixed-Term Contracts: For fixed-term employees, the contract end date drives automated notifications (approaching expiry alerts) and enables the HR team to decide on renewal or termination before the end date
• Probation Period: The probation end date on the contract record can trigger a notification to the manager to conduct a probation review before the period ends
• Document Storage: The signed contract document can be uploaded as an attachment to the Contract record or stored in Document Records linked to the worker

The Workforce Structures Workbench is the guided setup area in Oracle HCM Cloud's Setup and Maintenance for configuring the enterprise and workforce structure hierarchy.

• Tasks Covered: Create Enterprise, Create Reference Data Sets, Create Legislative Data Groups, Create Legal Addresses, Create Legal Entities, Create Business Units, Create Set Assignments, Create Locations, Create Departments, Create Jobs, Create Grades
• Configuration Sequence: The workbench enforces a logical sequence — Enterprise must be created first, then LDGs, then Legal Entities (which depend on LDGs), then Business Units. This prevents configuration errors from incomplete setups
• One-Time Setup: Most Enterprise Structure components are set up once and rarely changed post go-live. Changes (especially to LDGs and Legal Entities) can have significant downstream impacts on Payroll and HR data
• Testing: Always validate the enterprise structure design in CRP (Conference Room Pilot) sessions with the client's Finance and HR stakeholders before building in production
• Access Path: Setup and Maintenance → Workforce Structures Workbench (in the Functional Setup Manager)

Eligibility Profiles are reusable rule sets that determine which workers are eligible for a specific HR programme — absence plan, benefits plan, compensation plan, or training programme.

• Criteria Types: Employment (Worker Type, Assignment Status, Legal Employer, Business Unit), Derived Factors (Length of Service, Age, Compensation), Personal (Gender, Nationality), Job (Grade, Job Family, Position), Collective Agreement
• Usage in Absence: An annual leave plan using an eligibility profile might restrict access to permanent employees only (excluding contractors). Another plan for enhanced leave might require ≥3 years of service
• Usage in Benefits: Health insurance eligibility profile might include: Worker Type = Employee, Assignment Status = Active, Hours ≥ 20 per week
• Reusability: The same eligibility profile can be attached to multiple plans — e.g., "Full-Time Permanent Employee" profile used across Annual Leave, Health Insurance, and Bonus eligibility
• Configuration: My Client Groups → Benefits → Eligibility Profiles or Absence Management → Eligibility Profiles

Oracle HCM Cloud provides several built-in features to support GDPR compliance requirements for organisations operating in the EU/UK.

• Data Anonymisation: The Person Information Removal process (PIR) anonymises a terminated worker's personal data after the defined retention period — replacing name, DOB, national IDs with pseudonyms while retaining statistical HR data
• Purpose-Based Data Access: HCM Security Profiles limit access to personal data — ensuring only authorised HR users can view sensitive personal information
• Consent Management: Oracle supports recording consent for specific data processing purposes on the person record — e.g., consent to share data with third-party benefit providers
• Audit Trail: The Audit Framework tracks every access and modification to personal data — supporting the GDPR requirement to demonstrate who accessed personal data and when
• Data Portability: HCM Extracts and REST APIs can generate structured data exports of a worker's personal information to support Subject Access Requests (SAR)
• Breach Notification: Oracle's security infrastructure (penetration testing, SOC2 compliance, encryption at rest and in transit) supports breach prevention and detection obligations

• Definition: A Collective Agreement is a negotiated agreement between an employer and a trade union/employee representative body defining employment terms — pay scales, working hours, holiday entitlement, overtime rules
• Oracle HCM Use: Collective Agreements are configured in Oracle Global HR and attached to eligible worker assignments. Once attached, the agreement's terms (grade, salary, working hours) override default HR configurations for those workers
• Eligibility: Collective Agreements have eligibility criteria — typically specifying the bargaining unit, job grades, or locations covered by the agreement
• Entitlement Items: The agreement specifies entitlements that map to Oracle HR attributes — e.g., Grade Ladder assignments, Salary Band, specific Absence Plan entitlements
• Configuration: My Client Groups → Workforce Structures → Collective Agreements. Once created, the agreement is linked to assignments through eligibility profiles

• Definition: The Navigator is the main menu in Oracle HCM Cloud that provides access to all functional areas — My Workforce, My Client Groups, Tools, Benefits, Payroll, Absence, Setup and Maintenance
• Role-Based Display: The Navigator only shows menu items that a user has access to based on their assigned roles — an employee sees ESS options; an HR admin sees HR management tools; a payroll specialist sees payroll processing tasks
• Quick Actions: The home page also provides Quick Actions — frequently used shortcuts like "Add Person," "Hire an Employee," "Manage Absence," and "Run Payroll" — configurable per role
• Home Page Customisation: Administrators can configure which Quick Actions and info tiles appear for each role using Page Composer
• Deep Links: Oracle HCM Cloud supports deep links — direct URLs to specific pages or transactions — useful for embedding HR actions in email notifications or intranet portals