Oracle HCM Cloud’s BPM Worklist allows users to setVacation Rules(also called delegation rules) under the Preferences section of their worklist notifications. The line manager can configure a rule to reroute all approval tasks to his supervisor during a specified period (e.g., vacation dates). This is user-driven, requires no administrator intervention, and doesn’t alter underlying approval policies.

Option B (admin reassignment) is manual and unnecessary. Option C (automatic delegation) isn’t triggered by leave requests—it requires explicit setup. Option D (new policies) is overkill for a temporary absence. Option A correctly identifies the Vacation Rule as the solution, per Oracle’s workflow features.

In Oracle Global Human Resources Cloud, educational establishments (schools, universities) are maintained as part of the talent profile to support qualification tracking.

Option A: " Manage Profile Content Items " defines specific content (e.g., skills), not educational institutions.

Option B: " Manage Content Subscribers " controls access to content, not the list itself.

Option C: " Manage Profile Types " defines profile structures, not specific data likeinstitutions.

Option D: Correct. " Manage Educational Establishments " under Define Talent Profile Content allows setup of a selectable list of schools, colleges, and universities for qualifications.

The correct answer isD, per " Implementing Global Human Resources " on workforce profiles.

Guided Journeys in Oracle Global Human Resources Cloud are interactive processes designed to assist users in completing tasks or milestones. The " Using Journeys " guide specifies that Guided Journeys are primarily accessed and displayed via the " Journeys " tile on the employee’s home page or navigation menu. This tile serves as the entry point for users to view and interact with assigned or available journeys, such as onboarding or career development tasks. Option A (page/section headers) relates more to Contextual Journeys, not Guided ones. Option B (72pt. flashing font) is fictional and not a feature of Oracle HCM. Option C (Quick Action) is a separate feature for initiating transactions, not specifically tied to Guided Journeys. Therefore, Option D is the correct answer.

Full Detailed in Depth Explanation:

The Enterprise Structure Configurator (ESC) in Oracle HCM Cloud is a tool for efficiently creating and managing enterprise structures. It supports the creation of:

Divisions (A): Organizational units for segmenting the business.

Legal Entities (C): Entities with legal standing for employment and payroll.

Business Units (D): Operational units for managing transactions.

Reference Data Sets (E): Sets for sharing data across business units.

Comprehensive and Detailed Explanation From Exact Extract:

In Oracle Global Human Resources Cloud, checklist templates are used to automate tasks, such as offboarding journeys, for employees based on specific events like termination. The scenario describes a situation where an HR specialist created a checklist template categorized as " Offboarding " with the action " Termination, " but no offboarding journey or checklist is assigned to a retired employee after their work relationship is terminated. The Manage Allocated Checklist section, accessible via the Journeys or Checklist Tasks work areas, displays checklists assigned to employees. The absence of the checklist indicates a mismatch or configuration issue in the template’s setup.

Option A: Action Type was not defined for the checklist.

This option is incorrect. In Oracle HCM Cloud, the Action Type is a higher-level classification (e.g., Hire, Termination) that groups actions, but checklist templates are associated with specific Actions (e.g., Termination, Retirement) rather than requiring a separate Action Type definition. The scenario specifies that the checklist includes the action " Termination, " implying the action is defined. Oracle documentation does not mandate a distinct Action Type field for checklist templates to trigger allocation, making this option irrelevant.

Extract: “When you create a checklist template, you associate it with an action, such as Hire or Terminate, to trigger the checklist for specific events.” (OracleOracle Global Human Resources Cloud: Using Global Human Resources, Section: Checklist Templates).

Option B: Action Reasons were not defined in the checklist.

This option is incorrect. Action Reasons (e.g., Retirement, Resignation) provide additional context for an action and can be used to filter checklist allocation, but they are not mandatory for checklist assignment. If no action reasons are specified in the checklist template, the checklist should still be allocated based on the action (e.g., Termination) unless specific reasons are configured to restrict it. The scenario does not indicate that the checklist requires specific action reasons, and the lack of an assigned checklist suggests a broader issue with the action itself, not the absence of reasons.

Extract: “You can optionally specify action reasons to filter when a checklist is allocated, but this is not required for the checklist to trigger.” (Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Configuring Checklists).

Option C: The Action associated with the checklist does not match the Action selected during the termination process.

This is the correct answer. In Oracle HCM Cloud, checklist templates are triggered based on the Action selected during an employee’s transaction, such as termination. The scenario states the checklist is associated with the action " Termination, " but the employee’s work relationship is terminated due to retirement. In Oracle, Retirement is a distinct action (with a lookup code like RETIREMENT) separate from Termination (e.g., VOLUNTARY_TERMINATION). If the HR specialist selected Retirement as the action during the termination process, but the checklist is configured for Termination, the checklist will not be allocated, as the actions do not match. This explains why no offboarding journey or checklist appears in the Manage Allocated Checklist section for the retired employee.

Extract: “The checklist is allocated to a person when the action specified in the checklist template matches the action performed in the transaction. For example, a checklist for Termination won’t trigger if the action is Retirement.” (Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Checklist Allocation).

Additionally, the 24C What’s New documentation clarifies: “Ensure the checklist action aligns with the transaction action to avoid allocation issues.” (Oracle Fusion Cloud Human Resources 24C What’s New, Section: Journeys and Checklists).

Option D: The checklist template is not enabled for automatic allocation.

This option is incorrect. Checklist templates in Oracle HCM Cloud are enabled for allocation by default when created, provided they are Active and associated with an action. The scenario does not indicate that the template is inactive or disabled for allocation, and the issue is specifically tied to the retirement event not triggering the checklist. If automatic allocation were disabled, the template would not function for any termination actions, but the question focuses on the retirement case, pointing to an action mismatch.

Extract: “Checklist templates are active for allocation unless explicitly disabled or set to inactive status.” (Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Checklist Template Setup).

Why this answer?

The key issue is that the employee’s termination was processed with the Retirement action, which does not match the Termination action configured in the checklist template. Oracle’s checklist allocation logic requires an exact match between the transaction action and the checklist’s action, as documented. This mismatch prevents the offboarding journey from being assigned, making C the correct answer. The other options either misalign with Oracle’s functionality or do not directly address the retirement-specific issue.

References

Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com, Published: 2024-07-02

Section: Checklist Templates: Details on associating actions with checklists.

Section: Checklist Allocation: Explains how actions trigger checklist assignments.

Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-12

Section: Configuring Checklists: Describes action and action reason configurations.

Oracle Fusion Cloud Human Resources 24C What’s New, Document ID: docs.oracle.com, Published: 2024-08-27

Section: Journeys and Checklists: Notes on action alignment for checklist triggers.

Full Detailed in Depth Explanation:

Note: This appears to be a " choose two " question based on the original phrasing, though only one " Correct selection " was marked. I’ve interpreted it as requiring two correct answers based on Oracle functionality.

Option B ( " You can provide a role access to either of ' Specific categories ' or ' Allcategories ' options " ): True. Role-based security in Oracle HCM Cloud allows assigning access to all checklist categories or specific ones via custom roles, configured in " Manage Roles, " as per the " Implementing Global Human Resources " guide.

Option C ( " You can use Category Security to control what categories users see when creating templates on the Create Checklist Template page and when creating a personal journey in the Journeys app " ): True. Category Security restricts visibility and creation rights by category (e.g., Compensation), applied to templates and journeys, detailed in the " Using Checklists " guide.

Option A ( " This is not currently an option in the application " ): False. Oracle supports category-level access control.

In Oracle HCM Cloud’s BPM Worklist, when an approval task (e.g., Change Manager) is assigned to an application role like " HR Specialist Sales " with multiple inheritors, the " Enable Auto Claim " setting determines assignment behavior. If Auto Claim is disabled (not selected), the task is sent to all users with the role as a shared notification. One of these users must manually " Claim " the task in the worklist to take ownership and proceed with approval or rejection. Until claimed, the task remains unassigned to a specific individual, ensuring only one approver acts after claiming.

Option B (all must approve) misrepresents the process—only one approval is needed post-claim. Option C (auto-claimed randomly) contradicts the disabled Auto Claim setting. Option D (error) is incorrect—disabling Auto Claim doesn’t cause errors; it just requires manual claiming. Option A accurately describes the behavior: the task goes to all HR Specialist Sales role holders, and one must claim it, per Oracle’s approval framework.

To create a legal address for a legal entity in Oracle Global Human Resources Cloud, you need to use the Manage Legal Addresses task within the Setup and Maintenance work area. The task involves entering the provided address details (900 Main St, Dearborn Heights, Wayne, Michigan 48127) and ensuring the address is validated and associated with the legal entity. Below is a step-by-step solution, including detailed explanations and references to Oracle documentation, to accomplish this task.

Step-by-Step Solution

Step 1: Log in to Oracle Fusion Applications

Action : Log in to Oracle Fusion Applications with a user account that has the necessary privileges, such as the HCM Application Administrator or Setup User role. These roles typically include permissions to access the Setup and Maintenance work area.

Explanation : The Setup and Maintenance work area is where configuration tasks, including managing legal addresses, are performed. Proper access ensures you can navigate to the required tasks without restrictions.

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 Entity This option is incorrect. A Legal Entity represents 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 for work timings , standard working hours , organization manager , or cost center directly. Legal Entities are higher-level structures focused on regulatory requirements, not operat ional details like schedules or managers, making this option unsuitable.

Option B: Business Unit This option is incorrect. A Business Unit organizes business functions for transaction processing (e.g., payroll, requisition approvals) and defines scope for data access. It captures attributes like default working hours for payroll purposes, but it does not directly maintain work timings , organization manager , or cost center as part of its setup. Business Units are broader constructs and lack the granularity t o manage department-specific operational details, ruling out this option.

Option C: Department This is the correct answer. A Department in Oracle HCM Cloud is an organization type used to represent operational units (e.g., Sales, IT). During setup via the Manage Organization task, 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-foc used). The ability to configure work timings, standard hours, managers, and cost centers aligns with the Department’s role in Core HR setup, making C the correct choice.

References

Oracle Global Human Resources Cloud: Implementing Global Human Resources , D ocument 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 , Documen t 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.”

Reference data partitioning in Oracle Global Human Resources Cloud separates data sets to control visibility and usage across the organization. Enabled objects for partitioning are typically workforce structures shared across business units.

Option A: Enterprise and legal entity are structural, not reference data objects; position is not typically partitioned.

Option B: Correct. Department, location, jobs, and grades are reference data objects that can be partitioned using reference data sets (e.g., via Manage Reference Data Sets) to restrict access by business unit or other criteria.

Option C: Salary plans and rates are not standard partitioned objects; jobs and grades are, but the set is incomplete.

Option D: Division is not a standard partitioning object; legal entity is structural, not reference data.

The correct answer isB, as per " Implementing Global Human Resources " on reference data management.