In Oracle Global Human Resources Cloud, work structures include organizations like Legal Entities, Business Units, and Departments, each serving distinct purposes. The question asks which organization type allows capturing work timings, standard working hours, organization manager, and cost center during Core HR setup.
* Option A: Legal EntityThis option is incorrect. ALegal Entityrepresents a legal employer or registered organization for compliance and reporting (e.g., tax, payroll). While it captures attributes like name, address, and jurisdiction, it does not maintain fields forwork timings,standard working hours, organization manager, orcost centerdirectly. Legal Entities are higher-level structures focused on regulatory requirements, not operational details like schedules or managers, making this option unsuitable.
* Option B: Business UnitThis option is incorrect. ABusiness Unitorganizes business functions for transaction processing (e.g., payroll, requisition approvals) and defines scope for data access. Itcaptures attributes like default working hours for payroll purposes, but it does not directly maintainwork timings
,organization manager, orcost centeras part of its setup. Business Units are broader constructs and lack the granularity to manage department-specific operational details, ruling out this option.
* Option C: DepartmentThis is the correct answer. ADepartmentin Oracle HCM Cloud is an organization type used to represent operational units (e.g., Sales, IT). During setup via theManage Organizationtask, Departments allow capturing:
* Work timings: Configured via work schedules or shift details associated with the department.
* Standard working hours: Defined to specify default hours for employees in the department (e.
g., 40 hours/week).
* Organization manager: Assigned to designate the department's manager or supervisor.
* Cost center: Linked to track financial accountability for department activities. Oracle documentation confirms that Departments support these fields to manage workforce operations, making them the ideal organization type for this requirement.
* Why this answer?Departments are designed to handle operational and workforce-related details, unlike Legal Entities (compliance-focused) or Business Units (transaction-focused). The ability to configure work timings, standard hours, managers, and cost centers aligns with the Department's role in Core HR setup, makingCthe correct choice.
References
* Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
* Section: Manage Organizations: "Departments can include details like work schedules, standard hours, managers, and cost centers."
* Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.
oracle.com, Published: 2024-07-02
* Section: Department Setup: "Configure operational attributes such as work timings, hours, and cost centers for departments."
* Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published: 2024-08-27
* Section: Workforce Structures: "Enhanced department configurations for operational management."

Full Detailed In-Depth Explanation:
The Enterprise Structures Configurator (ESC) in Oracle Global Human Resources Cloud is detailed in the
"Implementing Global Human Resources" guide:
Option A: True. ESC allows review, modification, and load/rollback of the enterprise and job/position structures.
Option B: False. ESC doesn't limit to divisions; it includes broader structures.
Option C: False. Departments are not a primary output; reference data sets are included instead.
Option D: True. ESC creates divisions, legal entities, business units, and reference data sets.

Full Detailed In-Depth Explanation:
In Oracle HCM Cloud, Position Management settings are defined at the Enterprise level (via Manage Enterprise HCM Information) and can be overridden at the Legal Entity level (via Manage Legal Entity HCM Information). The documentation specifies thatPosition Synchronization Configurationsettings (e.g., enabling synchronization, allowing overrides) are configurable at both levels, with Legal Entity settings taking precedence if specified. This allows tailored synchronization behavior per legal entity while maintaining an enterprise default.
Position Incumbent Validation (e.g., validating position assignments) and Position Hierarchy Configuration (e.
g., hierarchy rules) are managed separately and not explicitly noted as overrideable at the Legal Entity level in the same way. Options B, C, and D include additionalsettings that lack evidence of Legal Entity override capability in the documentation. Option A correctly identifies Position Synchronization Configuration as the overrideable setting.

Full Detailed in Depth Explanation:
In Oracle HCM Cloud, statuses control various aspects of a worker's record, and the ability to create additional values depends on the status type:
* A (Payroll Status): This refers to payroll-specific statuses (e.g., Processed, Paid), which are system- defined and tied to payroll processes. These are fixed and cannot be extended with additional values.
* B (Assignment Status): This governs the status of a worker's assignment (e.g., Active, Suspended).
Oracle allows you to create additionalUser-Defined Assignment Statusesvia the "Manage Assignment Status" task, enabling customization (e.g., "On Leave - Special Circumstance") while preserving system statuses like Active or Inactive.
* C (HR Status): This is a broad term, but in context, it typically refers to the Person-level status (e.g., Active, Terminated), which is system-defined and not extensible with additional values.
The Oracle documentation highlights that Assignment Status is unique in allowing user-defined values to meet specific business needs, while Payroll and HR Statuses remain locked to maintain consistency. Thus,Bis the correct answer.

Full Detailed in Depth Explanation:
Actions and Action Reasons in Oracle HCM Cloud categorize and explain employment events (e.g., hires, terminations), supporting tracking and analytics.
* Option A ("Terminations predictive analytics uses Actions and Reasons data to identify whether a termination is voluntary or involuntary"): True. Oracle Workforce Predictions leverages Actions (e.g., Termination) and Action Reasons (e.g., Resignation vs. Layoff) to classify terminations, as detailed in the "Using Workforce Predictions" guide.
* Option B ("The history of effective date changes can be tracked well by using the Actions framework"):
True. The Actions framework logs changes (e.g., promotions, transfers) with effective dates, providing a clear audit trail, per the "Implementing Global Human Resources" guide.
* Option C ("It is mandatory to associate Actions with Action Reasons"): False. Action Reasons are optional; an Action (e.g., Termination) can be recorded without a reason.
* Option D ("There is always a one-to-one relationship between Action Type and Action"): False. Action Types (e.g., Termination) can have multiple Actions (e.g., Voluntary Termination, Involuntary Termination).