Oracle Cloud HCM Business Process Foundations
What this domain tests
Oracle Cloud HCM Business Process Foundations tests the shared objects and transaction mechanics behind every HCM module: enterprise structures, the person/work-relationship model, action-based approvals, and configurable processes such as Journeys and Checklists. Questions typically ask which object to configure, why a transaction is pending, or how a change propagates.
Enterprise structure
- Legal Entity (LE): registered organization for statutory and tax reporting; not the daily transaction boundary.
- Business Unit (BU): day-to-day transaction and security container; reference data sets determine which reference data it sees.
- Department belongs to a BU; Location is a physical address; Job is a reusable set of duties; Position is a specific budgeted instance of a job; Grade defines compensation levels.
- Payroll Statutory Unit (PSU) and Tax Reporting Unit (TRU) sit under the LE.
- Configure via tasks such as Manage Legal Entity, Manage Business Unit, Manage Departments, Manage Jobs, and Manage Positions. Most are date-tracked.
Person model
A person can hold multiple work relationships (employee, contingent worker, nonworker). Each work relationship contains assignments and terms. Security and approvals often act at assignment or work-relationship level, not person level.
Actions and approvals
Transactions are actions-hire, promote, transfer, terminate-that trigger approval rules. HCM approvals can use supervisory hierarchy, position hierarchy, or job/grade rules. The Transaction Console shows pending, errored, or stuck approvals. Journeys and Checklists orchestrate tasks but do not approve transactions.
Worked example
A firm opens a sales office in a new state, using its existing LE and BU. Create a Location for the address; create or reuse a Department under the BU; reuse the Job "Sales Representative"; create Positions only if headcount control is required; attach a Grade. If the state requires separate tax registration, add a TRU (and possibly PSU) under the same LE. A new LE or BU is unnecessary without a statutory or processing reason.
Traps
Confusing LE with BU; creating a BU per department; assuming positions are mandatory; ignoring date-effective start dates; expecting Journeys to approve; mixing person and assignment security.