Oracle Cloud HCM cheat sheet

Oracle Cloud HCM Business Process Foundations

• Enterprise structure hierarchy: Enterprise > Legal Entity > Business Unit > Department > Location > Position. A legal entity is the level that owns payroll statutory reporting; a business unit is the level that owns transactional data such as requisitions, jobs, and grades.

• Business Unit is the primary partitioning key for most HCM transactional data: workers, assignments, jobs, grades, and salary bases are business-unit specific; reference data sets (enterprise-level) can be shared across business units.

• Legal Entity and Business Unit are decoupled: one legal entity can be associated with multiple business units and one business unit can pay workers from multiple legal entities via payroll relationship and payroll statutory unit assignments.

• Date-tracked (effective-dated) records: every core object change is stored as a row with Effective Start Date/End Date. Correcting history requires DateTrack correction mode; future changes use Update mode. The latest effective date on or before the current date is the active row.

• Worker model: a person can hold multiple work relationships (employee, contingent worker, non-worker). Each work relationship has one or more assignments; the primary assignment drives most downstream processes.

• Core workforce structures: Job (generic role), Position (specific authorized slot, optional), Grade (seniority/pay band), Location (physical or logical address), Department (organization tree with a tree version).

• Enterprise structures use Trees with Tree Versions and Tree Nodes; department, organization, and geography hierarchies are published tree versions, and a date-effective tree node controls when a department rolls up to its parent.

• HCM Data Loader (HDL) loads business objects via .dat files with METADATA and MERGE lines; spreadsheet loaders (HCM Spreadsheet Data Loader) are generated from the same business object definitions and enforce the same validation rules.