An HR representative enters employee details in the application as part of the hiring process. On the Review page, the HR representative notices that Person Number does not show any number, but indicates "Generated Automatically." Identify the option that relates to this intended behavior.
Person Number at the Enterprise Level is set to Manual.
Person Number at the Enterprise Level is set to Automatic before submission.
Person Number at the Enterprise Level is set to Automatic after final save.
Worker Number at the Enterprise level is set to Manual.
The Answer Is:
CExplanation:
Full Detailed in Depth Explanation:
Person Number in Oracle HCM Cloud is a unique identifier for individuals, and its generation method is configured at the enterprise level via the "Manage Enterprise HCM Information" task. The behavior described—showing "Generated Automatically" with no number until the final save—indicates a specific setting.
Option C ("Person Number at the Enterprise Level is set to Automatic after final save") is correct. When configured this way, the Person Number is not assigned during data entry or review but is generated only after the transaction is fully saved. This ensures the number is allocated only when the record is committed, avoiding unused numbers if the process is abandoned. The "Implementing Global Human Resources" guide explains this option under Person Number generation settings.
Option A ("Person Number at the Enterprise Level is set to Manual") would require manual entry, not automatic generation.
Option B ("Person Number at the Enterprise Level is set to Automatic before submission") would assign the number earlier, visible during review, contradicting the scenario.
Option D ("Worker Number at the Enterprise level is set to Manual") is irrelevant, as "Worker Number" is not a standard term here; it’s Person Number.
The Promote transaction was configured by using Page Composer to require the location field. Another change was made to the transaction by using Transaction Design Studio, which indicated that the location field must be hidden when a manager uses the Promote transaction. How does the system determine how the user interface will render?
When a user tries to use the Promote transaction, the page will error when loading.
If modifications were made in both tools and the changes conflict, the result will be inconsistent behavior.
Transaction Design Studio configurations always override Page Composer configurations.
Page Composer configurations always override Transaction Design Studio configurations.
If modifications were made in both tools and the changes conflict, the last change created in either tool will be applied.
The Answer Is:
EExplanation:
Full Detailed In-Depth Explanation:
Oracle HCM Cloud allows UI customizations via Page Composer (for page-level changes) and Transaction Design Studio (for transaction-specific rules). When conflicting changes occur—e.g., Page Composer making the location field required and Transaction Design Studio hiding itfor managers—the system resolves this based on the timestamp of the last modification. The documentation states that if modifications from both tools conflict, the most recent change (based on creation or update date) takes precedence, regardless of the tool used. This ensures predictable behavior without requiring a strict hierarchy between the tools.
Option A (page error) is incorrect as the system doesn’t crash—it resolves conflicts silently. Option B (inconsistent behavior) is misleading because Oracle provides a clear resolution mechanism. Option C (TDS always overrides) and Option D (Page Composer always overrides) are incorrect because precedence isn’t tool-specific but time-based. Option E accurately reflects Oracle’s behavior: the last change applied in either tool wins, aligning with the customer’s observed UI rendering.
A consultant is trying to modify an existing lookup type to add a lookup code. But, they are not able to add lookup code.
What could be the possible reason?
The lookup type has been defined as Read Only.
The configuration level of lookup type is set as System.
The configuration level of lookup type is set as User.
The Answer Is:
BExplanation:
In Oracle Global Human Resources Cloud, lookup types are used to define lists of values (lookup codes) for fields, such as drop-down menus or selection lists. The question indicates that a consultant cannot add a lookup code to an existing lookup type, and we need to identify the reason. Lookup types have a configuration level that determines their modifiability:System,Extensible, orUser.
Option A: The lookup type has been defined as Read Only.This option is incorrect because Oracle HCM Cloud does not use aRead Onlydesignation for lookup types. Instead, modifiability is controlled by theConfiguration Level(System, Extensible, or User). ASystemlookup type is non-editable, anExtensiblelookup type allows adding new codes but not modifying predefined ones, and aUserlookup type is fully editable. The termRead Onlymay be confused withSystemlookup types, but it is not a standard term in Oracle documentation for this context, making this option invalid.
Option B: The configuration level of lookup type is set as System.This is the correct answer. Lookup types with aSystemconfiguration level are predefined by Oracle and cannot be modified by users, including adding, editing, or deleting lookup codes. For example, a lookup type likePER_PERSON_TYPE(for person types) is set asSystem, preventing consultants from adding new codes to maintain system integrity. If the consultant is trying to modify such a lookup type, they will be unable to add a lookup code, as the system restricts changes. Oracle documentation confirms thatSystemlookup types are locked for modifications, making this the most likely reason.
Option C: The configuration level of lookup type is set as User.This option is incorrect. A lookup type with aUserconfiguration level is fully editable, allowing users to add, edit, or delete lookup codes as needed. For instance, a custom lookup type created for department categories would typically beUserlevel, enabling the consultant to add new codes freely. Since the consultant cannot add a lookup code, aUserconfiguration level does not explain the issue.
Why this reason?The inability to add a lookup code points to a restriction on the lookup type’s modifiability. TheSystemconfiguration level explicitly prevents changes to ensure consistency across the application, aligning with Oracle’s design for predefined lookup types. NeitherRead OnlynorUseraccurately describes the restriction, asRead Onlyis not a valid term, andUserallows modifications.
References
Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-12
Section: Lookups: “System lookup types are predefined and can’t be modified. Extensible lookup types let you add new lookup codes, but you can’t modify predefined codes. User lookup types are fully editable.”
Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com, Published: 2024-07-02
Section: Manage Lookups: “You manage lookups using the Manage Common Lookups task. The configuration level determines whether you can add or modify lookup codes.”
Oracle Fusion Cloud Human Resources 24C What’s New, Document ID: docs.oracle.com, Published: 2024-08-27
Section: Configuration Enhancements: “Clarifications on lookup type management and restrictions.”
Challenge 1
Manage Legal Addresses
Scenario
An organization has just acquired a company, that manufactures spring hinges for spectacles in Michigain. You need to create a legal address for this company.
Task Create a legal address for the legal entity using the following details.
900 Main st, Dearborn Heights, Wayne, Michigan 48127.
The Answer Is:
See the solution in Explanation below.
Explanation:
This task requires creating a legal address for a legal entity in Oracle Global Human Resources Cloud using theManage Legal Addressestask. The address provided is900 Main St, Dearborn Heights, Wayne, Michigan 48127, for a company recently acquired by the organization. Below is a verified, step-by-step solution based on Oracle’s official documentation, ensuring accuracy and compliance with the system’s functionality as of the latest releases
Step-by-Step Solution
Step 1: Log in to Oracle Fusion Applications
Action: Log in to Oracle Fusion Applications using a user account with privileges such asApplication Implementation ConsultantorHCM Application Administrator. These roles grant access to the Setup and Maintenance work area.
Explanation: The Setup and Maintenance work area is the central hub for configuration tasks, including managing legal addresses. The user must have permissions to access theWorkforce Structuresfunctional area and theManage Legal Addressestask. Roles likeApplication Implementation Consultantinclude the necessary privileges (e.g.,Manage Legal Addressduty role).
Verification: Oracle documentation specifies that setup tasks require specific security roles, and theManage Legal Addressestask is restricted to authorized users.
An employee accesses the application, adds a self-requestable role, and saves the transaction. However, the line manager does not receive any notification to either approve or reject it. Which option describes the cause of this issue?
The security profile associated with the data role assigned to the line manager prevents any notification flowing to him.
The line manager does not have the privilege to receive notifications.
The role provisioning user interface and objects are not workflow-enabled. They are not currently designed to send notifications for any provisioning type.
Approvals in Oracle Global Human Resources Cloud go to two levels by default. Approvals should be modified to go to the line manager.
The Answer Is:
AExplanation:
Full Detailed in Depth Explanation:
In Oracle HCM Cloud, self-requestable roles trigger approval workflows if configured, typically notifying the line manager. If no notification is received, the issue likely relates to security or workflow setup.
Option A ("The security profile associated with the data role assigned to the line manager prevents any notification flowing to him") is correct. Notifications depend on the line manager’s data role and security profile. If the profile lacks access to the employee’s data or the transaction type, notifications are blocked. This is a common issue addressed in the "Implementing Global Human Resources" guide under security troubleshooting.
Option B ("The line manager does not have the privilege to receive notifications") is vague and less specific than A; privileges are part of the security profile.
Option C ("The role provisioning user interface and objects are not workflow-enabled") is incorrect; self-requestable roles are workflow-enabled by default in Oracle.
Option D ("Approvals in Oracle Global Human Resources Cloud go to two levels by default") is incorrect; approval levels are configurable, not fixed at two, and this doesn’t explain the lack of notification.
Availability (work time) can be defined in HCM Cloud in different ways. In which order does the application search for an employee's schedule, before applying it to an assignment?
Published schedules, Primary work schedule, Employment work week, Standard working hours
Standard working hours, Primary work schedule, Employment work week, Published schedules
Employment work week, Published schedules, Primary work schedule, Standard working hours
Published schedules, Employment work week, Primary work schedule, Standard working hours
The Answer Is:
AExplanation:
Full Detailed In-Depth Explanation:
In Oracle HCM Cloud, an employee’s work schedule for an assignment is determined by a hierarchical search order, as outlined in the documentation. The system prioritizes the most specific schedule first, falling back to broader defaults if none is found:
Published Schedules: These are worker-specific schedules published via Time and Labor, taking top priority.
Primary Work Schedule: Defined at the assignment level in Manage Employment, this is the next check.
Employment Work Week: Set at the work relationship level, it applies if no specific schedule exists.
Standard Working Hours: Defined at the legal employer or enterprise level, this is the final fallback.
Option A (Published schedules, Primary work schedule, Employment work week, Standard working hours) matches this exact order. Option B starts with Standard working hours (the last resort), which is incorrect. Option C prioritizes Employment work week over Published schedules, reversing the hierarchy. Option D swaps Primary work schedule and Employment work week, also incorrect. Option A is the verified sequence per Oracle’s logic.
Challenge 5
Manage Business Unit Set Assignment
Scenario
The new reference set needs to be mapped to the business unit that was created for departments, jobs, locations, and grades.
Task
Map your X Tech Business Unit Business Unit to the XTECH reference set for departments, jobs, locations, and grades.
The Answer Is:
See the solution in Explanation below.
Explanation:
To create a legal address for a legal entity in Oracle Global Human Resources Cloud, you need to use theManage Legal Addressestask 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 theHCM Application AdministratororSetup Userrole. 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.
As an employee of an organization, you can access your Public Information/Spotlight page within the Directory. What updates are employees allowed to directly make on their own My Public Info page that all users with access to view their Public Spotlight can see?
About me, contact information, profile photo, public message, favorites, and background photo
About me, area of expertise, area of interest, contact information, profile photo, public message, and peer information
Area of expertise, area of interest, contact information, profile photo, public message, and HR representative information
Home address, area of interest, contact information, profile photo, public message, and background photo
The Answer Is:
CExplanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, the Public Information/Spotlight page within the Directory allows employees to share information visible to others with appropriate access. The "Using Global Human Resources" guide under "Directory" specifies that employees can directly update: Area of Expertise (skills or specialties), Area of Interest (professional interests), Contact Information (e.g., work phone, email), Profile Photo, Public Message (a personal note), and HRRepresentative Information (contact details of their HR rep). Option C lists these accurately. Option A includes "about me" and "favorites," which are not standard editable fields here. Option B adds "peer information," which isn’t employee-editable. Option D includes "home address," which is private and not part of the public profile. Thus, Option C is correct.
When creating your THEN condition, which Approver Types enable you to configure the Automatic Approval Action type?
Representative, Management Hierarchy, Position Hierarchy
Users, Representative, Management Hierarchy, Job Level Based Line Manager Hierarchy, Position Hierarchy
Application Role, Users, Representative, Approval Groups
Management Hierarchy, Job Level Based Line Manager Hierarchy, Position Hierarchy
Approval Groups, Representative, Management Hierarchy, Position Hierarchy
The Answer Is:
EExplanation:
Full Detailed In-Depth Explanation:
In Oracle HCM Cloud’s Transaction Console, approval rules are defined with "IF" and "THEN" conditions. The "THEN" condition specifies the action, such as "Automatic Approval," and the approver type determines who or what approves the transaction. The Automatic Approval Action type allows a transaction to be approved without human intervention based on predefined rules. According to Oracle documentation, the approver types that support configuring Automatic Approval include Approval Groups (static or dynamic groups of approvers), Representative (e.g., HR or Payroll Representative), Management Hierarchy (based on supervisor hierarchy), and Position Hierarchy (based on position structure). These types can be configured to automatically approve under specific conditions.
Option A omits Approval Groups, which is a valid type for automatic approval. Option B includes "Users" and "Job Level Based Line Manager Hierarchy," but "Users" (individual named users) and "Job Level" are not typically used for automatic approval—they are more suited for manual routing. Option C includes "Application Role," which is used for role-based access, not automatic approval in workflows. Option D misses Approval Groups and Representative, both critical for this feature. Option E correctly lists Approval Groups, Representative, Management Hierarchy, and Position Hierarchy, aligning with Oracle’s supported approver types for automatic approval.
For the Change Manager transaction, the first-level approval is set to the Application Role type. The name of the application role is HR Specialist Sales. In the Change Manager approval rule configuration, the Enable Auto Claim option is deselected. Which two actions take place when the transaction for manager change is initiated for employees?
The transaction goes into error because it was not auto-claimed.
The transaction goes for approval to all the workers who inherit the HR Specialist Sales role.
The transaction will be auto-claimed and assigned randomly to anyone who has the HR Specialist Sales role.
If one of the HR Specialist Sales representatives rejects the transaction, others can still approve it.
One of the HR Specialist Sales representatives should "Claim" the transaction for it to be assigned for approval.
The Answer Is:
B, EExplanation:
Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, approval rules for transactions like Change Manager are managed via BPM Worklist. The "Application Role" approval type routes tasks to all users with that role (e.g., HR Specialist Sales), and the "Enable Auto Claim" setting determines assignment behavior.
Option A: Incorrect. Disabling auto-claim does not cause an error; it simply requires manual claiming before approval can proceed.
Option B: Correct. When auto-claim is disabled, the transaction is sent to all users with the HR Specialist Sales role, appearing in their worklist for claiming.
Option C: Incorrect. Without auto-claim, the transaction is not automatically assigned; it requires manual intervention.
Option D: Incorrect. In a parallel approval to multiple role holders, one rejection typically stops the process unless configured otherwise (e.g., consensus or first responder), which is not specified here.
Option E: Correct. With auto-claim disabled, an HR Specialist Sales representative must manually claim the transaction from the worklist to proceed with approval.
The correct answers areBandE, as detailed in "Using Global Human Resources" under Approval Configuration.
