An HR Specialist adds a new action "Reclassification" under the predefined Action Type "Promotion." What is true about this configuration?
-
A
It will replace all existing promotion actions.
-
B
It becomes available for selection in employment transactions.
-
C
It requires an associated Action Reason to be valid.
-
D
It is visible only to administrators.
Reveal answer details
Close answer details
Correct answerB
ExplanationUser-defined actions linked to predefined action types appear as selectable values in related transactions, such as Change Assignment.
Action Reasons are optional.
References:
Actions and Action Types - Managing Workforce Records.
Question 2
Multiple choice
What are four benefits of Enterprise Structure Configurator (ESC)?
-
A
Cannot roll back an enterprise that is created through ESC
-
B
Can create multiple configurations to test multiple scenarios
-
C
Can roll back an enterprise configuration after loading it
-
D
Can review the enterprise configuration before loading it
-
E
Can create all organizational structures at once
Reveal answer details
Close answer details
Correct answersB, C, D, E
ExplanationThe Enterprise Structure Configurator (ESC) offers several benefits: B: Allows creation of multiple configurations for testing different scenarios, enhancing flexibility.
C: Supports rollback of configurations post-loading if adjustments are needed, ensuring reversibility.
D: Enables review of the configuration before final loading, reducing errors.
E: Facilitates simultaneous creation of all organizational structures, streamlining setup.
References:
Oracle HCM Cloud: Implementing Global Human Resources, "ESC Benefits".
You are an HR specialist and want to add new values to a lookup. You have access to the specific work area, but are unable to perform the activity. Identify the correct statement about this.
-
A
You cannot add new lookup codes and meanings to the existing lookup types.
-
B
Oracle applications contain certain predefined system lookups that are locked for editing.
-
C
You can access the task for profile options from the Setup and Maintenance menu.
-
D
You can create new lookup types but cannot modify the existing ones.
-
E
The system administrator must enable the lookup before it is modified in the work area.
Reveal answer details
Close answer details
Correct answerB
ExplanationIn Oracle Global Human Resources Cloud, lookups are managed via the "Manage Common Lookups" or "Manage Standard Lookups" tasks in the Setup and Maintenance work area. Lookupsprovide drop-down values (codes and meanings) for fields, and their editability depends on their type and configuration.
Option A: Incorrect. You can add new lookup codes and meanings to many existing lookup types, provided they are not system-locked or restricted by security.
Option B: Correct. Oracle includes predefined system lookups (e.g., seeded values for core fields like Action Types or Employment Status) that are locked for editing to maintain application integrity. If the lookup you're trying to modify is one of these, you'll be unable to add values, even with access to the work area, due to system restrictions.
Option C: Incorrect. Profile options are unrelated to lookups; they control application behavior, not value lists, and don't explain the inability to edit.
Option D: Incorrect. You can modify existing lookup types (if not system-locked) and create new ones, depending on permissions and lookup status.
Option E: Incorrect. There's no specific "enable" step by a system administrator for lookups; editability is determined by the lookup's system status and user privileges.
The correct answer isB, as per "Implementing Global Human Resources" on lookup management, where system lookups are noted as non-editable. References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 5:
Lookups and Value Sets.
A worker in an organization will be holding a new position because the worker holding the position has gone on maternity leave. When the second worker returns from maternity leave, the former will be moved back to his or her old position. His or her payroll and legal reporting will be the same even after the position changes. Which transfer method should be used for the first movement of the said worker?
-
A
-
B
-
C
-
D
Global Temporary Assignment
Reveal answer details
Close answer details
Correct answerB
ExplanationOracle Global Human Resources Cloud provides various transfer actions to manage worker movements.
The scenario involves a temporary position change with a return to the original position, and payroll/legal reporting remaining unchanged.
Option A: A Transfer is a permanent move to a new assignment or position, not suitable for a temporary scenario with a planned return.
Option B: Correct. A Temporary Assignment allows a worker to take on a new position or assignment for a fixed period, with the system retaining the original assignment for automatic reversion. Payroll and legal reporting can remain tied to the primary assignment, fitting the requirement.
Option C: Global Transfer is for permanent moves across legal employers or countries, not applicable here.
Option D: Global Temporary Assignment is for temporary international moves, not relevant for a same-
entity, same-reporting scenario.
The correct answer isB, as per "Using Global Human Resources" on temporary assignments. References:
Oracle Global Human Resources Cloud - Using Global Human Resources, Chapter 7:
Employment Transactions.
Which is a new feature available on the Redwood Cancel Work Relationship page?
-
A
Ability to track employee attendance and absences
-
B
Capability to record additional information during work relationship cancellation
-
C
Option to generate automated performance reports
Reveal answer details
Close answer details
Correct answerB
ExplanationThe Redwood Cancel Work Relationship page in Oracle Global Human Resources Cloud introduces enhancements designed to improve user experience and streamline the process of terminating work relationships. According to Oracle's 24C and subsequent release notes, one of the key new features is the ability to record additional information during the cancellation of a work relationship. This includes selecting actions and action reasons for the cancellation and utilizing the action occurrence extensible flexfield (EFF) to store extra details in an "Additional Info" section, which is displayed only when configured for the action occurrence EFF. This feature enhances flexibility and allows organizations to capture enterprise-specific data during the termination process.
Option A: Ability to track employee attendance and absencesTracking employee attendance and absences is not a feature associated with the Redwood Cancel Work Relationship page. Attendance and absence management are handled through separate modules, such as Oracle Absence Management or Time and Labor, and are not integrated into the work relationship cancellation process. Oracle documentation does not mention attendance or absence tracking as part of this page's functionality, making this option incorrect.
Option B: Capability to record additional information during work relationship cancellationThis is the correct answer. Oracle's 24C release notes specify that the Redwood Cancel Work Relationship page allows users to configure multiple actions for the cancellation process and includes an action occurrence EFF in the Additional Info section. This enables the storage of extra information, such as specific reasons or contextual details, during the cancellation.
The feature is supported by configuration in the Business Rules to show the Additional Info section and is available only on the Redwood page, not the responsive version, enhancing the user experience with greater customization. Option C: Option to generate automated performance reportsGenerating automated performance reports is not a feature of the Redwood Cancel Work Relationship page. Performance reports are typically managed through Oracle Performance Management or Talent Management modules, and no
Oracle documentation indicates that the Cancel Work Relationship page includes this capability. This option is unrelated to the termination process and is therefore incorrect. References:
Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published:
2024-08-27
Section:
Redwood Experience for Cancel Work Relationship Page: "Ability to record extra info while canceling a work relationship - You can now select the action and action reason for canceling the work relationship.
You can now configure multiple actions as a part of the Cancel Work Relationship action type. Additionally, the action occurrence extensible flexfield (EFF) is added in the Additional info section so that you can store extra information while canceling a work relationship." Section: Cancel Work Relationships: "Describes the process to cancel work relationships, including configuration of actions and reasons."
Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle. com,
Published: 2024-07-02 Oracle Global Human Resources Cloud: Implementing Global Human Resources,
Document ID: docs. oracle.com, Published: 2023-12-12
Section: Extensible Flexfields: "Explains how EFFs can be configured to capture additional attributes for
actions like work relationship cancellation
An HR Specialist attempts to update a person's marital status but receives an error indicating missing required LOV values. What is the likely cause?
-
A
The lookup type associated with marital status is end-dated.
-
B
The user lacks Maintain Marital Status privilege.
-
C
The Person Search Keywords process failed.
-
D
The person record is locked by another user.
Reveal answer details
Close answer details
Correct answerA
ExplanationMarital Status uses a lookup type. If the lookup is end-dated, values disappear from LOVs, causing validation errors.
User privilege issues would prevent access entirely.
Search keywords do not affect data entry.
References:
Managing Lookups - Lookup Validity Dates.
You are required to set geography validation for country-specific address style. You have configured the application correctly, but users are still entering addresses in the wrong address format.
Whatcan be done to change this?
-
A
Set the geography validation level to Error instead of No Validation.
-
B
Educate users to use the country-specific address format only.
-
C
Effective End Date for geography validation is end of time.
-
D
Create a new geography validation.
Reveal answer details
Close answer details
Correct answerA
ExplanationGeography validation in Oracle HCM Cloud ensures addresses conform to country-specific formats (e.g., postal code rules). If users are entering incorrect formats despite correct configuration, the validation
enforcement level needs adjustment.
Option A ("Set the geography validation level to Error instead of No Validation") is correct. Oracle allows configuration of geography validation levels in the "Manage Geographies" task: No Validation (no checks), Warning (alerts but allows saving), and Error (prevents saving invalid formats). If set to No Validation or Warning, users can bypass the country-specific format. Changing it to Error enforces compliance by rejecting incorrect entries, as detailed in the "Implementing Global Human Resources" guide.
Option B ("Educate users to use the country-specific address format only") is a workaround, not a system solution, and does not enforce compliance. Option C ("Effective End Date for geography validation is end of time") is irrelevant, as end-dating applies to data validity, not validation enforcement.
Option D ("Create a new geography validation") is unnecessary if the existing configuration is correct; the issue lies in the enforcement level. References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Chapter on Geographies, section on validation levels.
"Oracle Human Resources Cloud: Using Global Human Resources" - Address setup and validation.
What work area within HCM Cloud provides implementers with end-to-end access to all configuration objects needed to successfully implement HCM Cloud: Core HR?
-
A
Person Management work area
-
B
Enterprise Structures work area
-
C
Workforce Structures work area
-
D
Setup and Maintenance work area
Reveal answer details
Close answer details
Correct answerD
ExplanationTheSetup and Maintenance work area(FSM) in Oracle HCM Cloud is the central hub for implementers, providing comprehensive access to all configuration tasks required for implementing Core HR. This includes defining enterprise structures, workforce structures, geographies, and other foundational elements. While the Person Management (A), Enterprise Structures (B), and Workforce Structures (C) work areas support specific functions, they are operational or subset areas, not the end-to-end configuration hub. The Oracle "Implementing Global Human Resources" guide confirms that FSM is the primary work area for Core HR setup, makingDthe correct answer.
References:
Oracle HCM Cloud: Implementing Global Human Resources, "Setup and Maintenance
Overview".
What type of people within our system are assigned Person IDs?
-
A
Employees, Contingent Workers, Non-Workers
-
B
Employees, Contingent Workers, Non-Workers, Pending Workers, Worker Contacts
-
C
Employees, Contingent Workers, Non-Workers, Pending Workers
Reveal answer details
Close answer details
Correct answerB
ExplanationIn Oracle HCM Cloud, aPerson IDis a unique identifier assigned to individuals within the system who have a person record. The types of people assigned Person IDs include: Employees: Full-time or part-time workers with an employment relationship.
Contingent Workers: Temporary or contract workers.
Non-Workers: Individuals like retirees or external contacts with a person record but no active work relationship.
Pending Workers: Individuals hired but not yet started (e.g., future-dated hires).
Worker Contacts: Emergency contacts or dependents linked to a worker's record, who also receive a Person ID for tracking purposes.
Option A omits Pending Workers and Worker Contacts, which are included in the system's person model.
Option C misses Worker Contacts, who are explicitly assigned Person IDs to manage relationships. Option
B is the most comprehensive, aligning with Oracle's definition of person records in the "Person Management" guide, makingBthe correct answer. References:
Oracle HCM Cloud: Implementing Global Human Resources, "Person ID Assignment".
Question 10
Single choice
When initiating the Change Manager transaction for employees, the first-level approval is assigned to the HR Specialist Sales application role. In the approval rule configuration for Change Manager, the option to Enable Auto Claim is not selected. What happens in this case?
-
A
The transaction goes for approval to all the workers who inherit the HR Specialist Sales role and one of the HR Specialist Sales representatives needs to "Claim" the transaction for it to be assigned for approval
-
B
The transaction has to be approved by all HR Specialist Sales representatives for it to be approved; if
one of the HR Specialist Sales representatives rejects the transaction, others can still approve it
-
C
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 Salesrole
-
D
The transaction goes into error because it was not auto-claimed and if one of the HR Specialist Sales representatives rejects the transaction, others can still approve it
Reveal answer details
Close answer details
Correct answerA
ExplanationIn 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. References:
Oracle Docs - "Using Global Human Resources" (docs.oracle.com, published 2023-10-03),
Approval Rules section.
Question 11
Single choice
You have a business requirement to default the Business Title of a worker when a user updates a worker's assignment by using one of the worker employment responsive flows. How can you enable this feature and which options are available for defaulting?
-
A
Enable the Default Business Title field on the Legal Entity HCM Information task, and select Retain User Changes, Automatically Update Based on Position Change, or Allow Override if Position Data is Overridden.
-
B
Enable the Default Business Title field on the Enterprise HCM Information task, and select Retain User Changes, Automatically Update Based on Job Change, or Automatically Update Based on Position Change.
-
C
Enable the ORA_PER_EMPL_DEFAULT_BUSINESS_TITLE_FROM profile option, and select Retain
User Changes, Automatically Update Based on Job Change, Automatically Update Based on Position Change, or Allow Override if Position Data is Overridden.
-
D
Enable the ORA_PER_EMPL_DEFAULT_BUSINESS_TITLE_FROM profile option, and select Retain
User Changes, Automatically Update Based on Job Change, or Automatically Update Based on Position Change.
Reveal answer details
Close answer details
Correct answerD
ExplanationDefaulting the Business Title in Oracle HCM Cloud during assignment updates is controlled by a profile option, not HCM Information tasks.
Option D ("Enable the ORA_PER_EMPL_DEFAULT_BUSINESS_TITLE_FROM profile option, and select Retain User Changes, Automatically Update Based on Job Change, or Automatically Update Based on Position Change") is correct. The profile option "ORA_PER_EMPL_DEFAULT_BUSINESS_TITLE_FROM" determines how the Business Title is populated in responsive flows (e.g., Change Assignment). Available settings are: Retain User Changes: Keeps manual edits.
Automatically Update Based on Job Change: Updates from the job title.
Automatically Update Based on Position Change: Updates from the position title. This is detailed in the "Implementing Global Human Resources" guide under profile options.
Option A and B reference HCM Information tasks, which don't control this feature.
Option C adds "Allow Override if Position Data is Overridden," which is not a valid setting for this profile option. References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Profile options for employment flows.
"Oracle Human Resources Cloud: Using Global Human Resources" - Assignment updates.
Question 12
Multiple choice
A Human Resource Representative is in the process of transferring an employee from France Subsidiary to US Subsidiary and exercises the option of Global Transfer. Identify the three options for the Global Transfer process. (Choose three.)
-
A
A new work relationship in the destination legal employer is not created automatically.
-
B
The Human Resources Representative cannot override the default changes.
-
C
The Human Resources Representative can override the default by deselecting the assignments that
are not required to be terminated; these assignments retain their original status and the work
relationship is not terminated.
-
D
The existing set of employment terms and assignments in the source work relationship are terminated and their status is set to Inactive - Payroll Eligible by default.
-
E
A new work relationship in the destination legal employer is created automatically.
Reveal answer details
Close answer details
Correct answersC, D, E
ExplanationThe Global Transfer feature in Oracle HCM Cloud facilitates moving an employee between legal employers within the same enterprise, such as from France Subsidiary to US Subsidiary.
Option C ("The Human Resources Representative can override the default by deselecting the assignments that are not required to be terminated; these assignments retain their original status and the work
relationship is not terminated"): True. During a Global Transfer, the HR representative can choose which assignments to terminate or retain, overriding defaults, as explained in the "Using Global Human Resources" guide. Option D ("The existing set of employment terms and assignments in the source work relationship are terminated and their status is set to Inactive - Payroll Eligible by default"): True. By default, the source work relationship's assignments are terminated and marked Inactive - Payroll Eligible, preserving payroll history, per standard Oracle behavior.
Option E ("A new work relationship in the destination legal employer is created automatically"): True. A Global Transfer automatically creates a new work relationship in the destination legal employer, effective from the transfer date.
Option A ("A new work relationship in the destination legal employer is not created automatically"): False.
This contradicts the automated nature of Global Transfer.
Option B ("The Human Resources Representative cannot override the default changes"): False. Overrides are allowed, as noted in
Option C. References:
"Oracle Human Resources Cloud: Using Global Human Resources" - Global Transfer process details.
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Employment model
changes.
Question 13
Multiple choice
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?
-
A
The transaction goes into error because it was not auto-claimed
-
B
The transaction has to be approved by all HR Specialist Sales representatives for it to be approved
-
C
The transaction goes for approval to all the workers who inherit the HR Specialist Sales role
-
D
One of the HR Specialist Sales representatives should "Claim" the transaction for it to be assigned for approval
Reveal answer details
Close answer details
Correct answersC, D
ExplanationIn Oracle Global Human Resources Cloud, approval rules for the Change Manager transaction are configured per the "Securing HCM" guide: With "Enable Auto Claim" deselected, the transaction isn't automatically assigned to one approver; it goes to all users with the HR Specialist Sales role (Option C).
References:
Oracle Global Human Resources Cloud - Securing HCM, "Approval Rules Configuration" topic.
Question 14
Single choice
Which option represents the basis on which approval routing policies can be defined?
-
A
Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups
-
B
Employee Supervisor Hierarchy, Position Hierarchy, Grades, Approval Groups, Organization Hierarchy
-
C
Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups, Organization
Hierarchy
-
D
Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Department Manager
Reveal answer details
Close answer details
Correct answerA
ExplanationApproval routing policies in Oracle HCM Cloud, configured via Transaction Console or BPM Worklist, use specific bases to define approver chains. The documentation lists these as:Employee Supervisor Hierarchy (management chain),Position Hierarchy(position-based reporting),Job Levels(relative to the requester's job level), andApproval Groups(static or dynamic groups). These options provide flexibility to route approvals based on organizational structure or predefined lists, covering most use cases.
Option B includes "Grades," which influence salary, not approvals, and "Organization Hierarchy," which isn't a direct routing basis.
Option C adds "Organization Hierarchy," which is redundant with Supervisor Hierarchy.
Option D's "Department Manager" isn't a distinct basis-it's part of Supervisor Hierarchy. Option A accurately reflects Oracle's supported routing bases. References:
Oracle Docs - "Using Global Human Resources" (docs.oracle.com, published 2023-10-03),
Approval Policies section.
Question 15
Single choice
Which Approval Types are supported while configuring the Managing Approval Rules: Promote transaction?
-
A
Application Role, Approval Groups, Management Hierarchy, Parent Position, Representative,User, Self
Auto Approve
-
B
Application Role, Approval Groups, Management Hierarchy, Position Hierarchy, Representative, Self
Auto Approve, User
-
C
Data Role, Application Role, Approval Groups, Management Hierarchy, Position Hierarchy, Self Auto
Approve, User
-
D
Enterprise Role, Application Role, Approval Groups, Parent Position, Representative, User, Self Auto
Approve
Reveal answer details
Close answer details
Correct answerB
ExplanationIn Oracle Global Human Resources Cloud, approval rules for transactions like Promote are configured in BPM Worklist with supported approval types.
Option A: "Parent Position" is not a standard approval type; "Position Hierarchy" is correct.
Option B: Correct. Supported types include:
Application Role (e.g., HR Specialist), Approval Groups (static user lists),
Management Hierarchy (line managers),
Position Hierarchy (position-based),
Representative (e.g., delegate), Self Auto Approve (initiator approves), User (specific individual).
Option C: "Data Role" is a security concept, not an approval type.
Option D: "Enterprise Role" is not an approval type; "Parent Position" is incorrect.
The correct answer is B, per "Using Global Human Resources" on approval configuration. References:
Oracle Global Human Resources Cloud - Using Global Human Resources, Chapter 3:
Approvals and Notifications.
Question 16
Single choice
An employee's job title was "Recruiter" as of January 01, 2024. However, on February 01, 2024, the job title was updated to "Consultant" in the system. The latest effective-dated employment record in the system is the one from February 01, 2024. On March 01, 2024, an HR specialist tries to search for the previous employment details of this employee using Global Search. The HR specialist enters the search keyword "Recruiter" and the Effective Date value of January 31, 2024, since the employee's job title was Recruiter on that day. The search returns no rows. What is the reason?
-
A
The process has successfully updated the most recent effective-dated job attribute in the keyword record.
-
B
The process failed on January 31, 2024 but it ran successfully the following day.
-
C
The process failed on March 1st, 2024, but it ran successfully the day before.
Reveal answer details
Close answer details
Question 17
Single choice
A static approval group named "Trio" comprises three members-Jacob, Susan, and Dia (in the mentioned order). For all the Manage Employment transactions, the approval should be routed to the "Trio" approval group. When the assignment change transaction is submitted, what is the order in which these three members receive the assignment change approval notification?
-
A
System decides the approval route by randomly selecting approvers who are a part of the approval group.
-
B
First Approver Jacob, Second Approver-Susan, Third Approver-Dia
-
C
First Approver Dia, Second Approver-Susan, Third Approver Jacob; the approval is routed
alphabetically.
-
D
All three get the notification at the same time.
Reveal answer details
Close answer details
Correct answerB
ExplanationIn Oracle HCM Cloud, a static approval group (e.g., "Trio") routes approvals sequentially based on the order members are listed in the group definition, unless configured otherwise (e.g., parallel routing). For "Trio" (Jacob, Susan, Dia), the documentation states that approval notifications follow this sequence: Jacob (first), Susan (second), Dia (third), with each approving in turn before the task progresses.
Option A (random) contradicts the fixed order of static groups.
Option C (alphabetical) is incorrect-order is based on definition, not names.
Option D (simultaneous) applies to parallel groups, not sequential static ones.
Option B matches Oracle's default behavior for static approval groups. References:
Oracle Docs - "Using Global Human Resources" (docs.oracle.com, published 2023-10-03),
Approval Groups section.
Question 18
Single choice
As an implementation consultant, you have configured several rules in Transaction Design Studio within the test environment. How do you migrate these changes to your production environment?
-
A
Use the Configuration Package capabilities within the Configuration > Migration work area
-
B
Use the Configuration Package capabilities of Functional Setup Manager to export the configurations
-
C
Transaction Design Studio changes can't be migrated from one instance to another. You will need to reconfigure the transactions within your production environment
-
D
Use the Configuration Set Migration tool within the Configuration > Migration work area
Reveal answer details
Close answer details
Correct answerD
ExplanationTransaction Design Studio (TDS) customizations, such as rules for transactions, are migrated using the Configuration Set Migration tool, as per the "Implementing Global Human Resources" guide. Located in the Configuration > Migration work area, this tool allows export and import of TDS configurations between
environments (e.g., test to production).
Option A refers to a broader migration capability, not specific to TDS.
Option B (Functional Setup Manager) is for setup data, not TDS rules.
Option C is incorrect, as migration is supported. Thus, Option D is correct.
References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, "Migrating
Transaction Design Studio Configurations" topic.
Question 19
Single choice
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.
-
A
Person Number at the Enterprise Level is set to Automatic before submission.
-
B
Worker Number at the Enterprise Level is set to Manual.
-
C
Person Number at the Enterprise Level is set to Automatic after final save.
-
D
Person Number at the Enterprise Level is set to Manual.
Reveal answer details
Close answer details
Correct answerC
ExplanationIn Oracle Global Human Resources Cloud, the Person Number generation method is configured via "Manage Enterprise HCM Information." Options include Manual, Automatic before submission, or Automatic after final save. The behavior described-showing "Generated Automatically" with no number on the Review page-indicates the number is assigned post-submission.
Option A: "Automatic before submission" generates the person number immediately upon initiating the hire process, visible before review. This doesn't match the scenario.
Option B: "Worker Number" is distinct from Person Number and irrelevant here. Manual setting would require user input, not "Generated Automatically."
Option C: Correct. "Automatic after final save" delays person number generation until the transaction is fully submitted and saved, explaining why it's not visible on the Review page but marked as automatic.
Option D: Manual requires the user to enter a number, contradicting the "Generated Automatically" indication.
The correct answer isC, as detailed in "Implementing Global Human Resources" under Person Number setup. References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 8:
Person Records.
Question 20
Single choice
A manager initiates a global transfer for a worker but notices the proposed new assignment does not inherit the expected job and location defaults. What is the reason?
-
A
Job and location defaults must be manually selected during global transfer.
-
B
Position synchronization overrides all defaults.
-
C
Global Transfer only copies person-level data.
-
D
The legal employer transfer disables inheritance of assignment attributes.
Reveal answer details
Close answer details
Correct answerA
ExplanationGlobal Transfer does not automatically inherit job or location defaults; the HR user must explicitly select values when configuring the destination assignment.
Position synchronization applies only if a position is selected.
References:
Using Global Human Resources - Global Transfer.
Question 21
Single choice
During implementation, a two-tier employment model with multiple assignments has been set up. Now the client wants to store contract information. Which statement is true about changing the employment model setting after implementation?
-
A
The client can change from any two-tier option to another at any point in time, irrespective of the existence of work relationships.
-
B
The client cannot move from a two-tier multiple assignment to a two-tier single contract and single assignment after implementation.
-
C
The client can have both: a two-tier multiple assignment employment model can remain for its existing employees, and a two-tier multiple contracts single assignment can be created to hire new employees within the same legal employer.
-
D
If employees exist within the enterprise and legal employer, the person model setting cannot be changed as there are no contract options that support a contract with multiple assignments.
Reveal answer details
Close answer details
Correct answerA
ExplanationOracle Global Human Resources Cloud supports two-tier employment models: single assignment (SA) or multiple assignments (MA), with or without contracts (SC or MC). The employment model is set at the enterprise or legal employer level via "Manage Enterprise HCM Information" or "Manage Legal Entity HCM Information." Changing this model post-implementation is possible under certain conditions. Option A: Correct. Oracle allows flexibility to change the employment model (e.g., from two-tier MA to two-tier MC SA) at any time, even with existing work relationships, as long as data migration and configuration adjustments (e.g., contract setup) are handled. The system does not lock the model once set.
Option B: Incorrect. The client can transition from two-tier MA to two-tier SC SA post-implementation, though it requires updating existing records and ensuring compliance with new contract rules.
Option C: Incorrect. Within the same legal employer, only one employment model can be active at a time.
Mixing MA for existing employees and MC SA for new hires in the same legal employer is not supported without separate legal employers or a model change.
Option D: Incorrect. Contracts can coexist with multiple assignments if configured as multiple contracts (MC), so the model can be changed even with existing employees, contradicting this statement.
The correct answer isA, as per "Implementing Global Human Resources" on employment model flexibility. References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 8:
Employment Model Configuration.
Question 22
Single choice
An organization is running a fitness program. They want to identify a Fitness Representative who will be responsible for a group of people in the organization. How should you set this up?
-
A
Deploy a Key Flexfield to capture the information.
-
B
Deploy a Descriptive Flexfield to capture the information.
-
C
Create a new job Fitness Representative and associate that to the person.
-
D
Define the person's area of responsibility to reflect Fitness Representative.
Reveal answer details
Close answer details
Correct answerD
ExplanationOracle HCM Cloud allows assigning responsibilities to individuals for specific tasks or groups, such as a Fitness Representative for a fitness program. The setup should leverage existing functionality efficiently.
Option D ("Define the person's area of responsibility to reflect Fitness Representative") is correct. In Oracle HCM, "Areas of Responsibility" (AOR) can be defined via the "Manage Areas of Responsibility" task to assign specific duties (e.g., Fitness Representative) to a person for a group of workers. This is a standard feature for designating responsibilities without requiring new jobs or flexfields, as outlined in the "Implementing Global Human Resources" guide.
Option A ("Deploy a Key Flexfield to capture the information") is incorrect. Key Flexfields (KFFs) are used for structured data (e.g., job codes), not responsibilities.
Option B ("Deploy a Descriptive Flexfield to capture the information") could work for custom attributes but is overkill when AOR is available.
Option C ("Create a new job Fitness Representative and associate that to the person") is unnecessary; a job defines a role, not a specific responsibility for a program. References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Section
on Areas of Responsibility."Oracle Human Resources Cloud: Using Global Human Resources" - Managing responsibilities.
Question 23
Single choice
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?
-
A
When a user tries to use the Promote transaction, the page will error when loading.
-
B
If modifications were made in both tools and the changes conflict, the result will be inconsistentbehavior.
-
C
Transaction Design Studio configurations always override Page Composer configurations.
-
D
Page Composer configurations always override Transaction Design Studio configurations.
-
E
If modifications were made in both tools and the changes conflict, the last change created in either tool will be applied.
Reveal answer details
Close answer details
Correct answerE
ExplanationOracle 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 it for 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. References:
Oracle Docs - "Using Global Human Resources" (docs.oracle.com, published 2023-10-03), UI
Customization section.
Question 24
Single choice
When a parent position becomes vacant, you need the incumbents in the child positions to be assigned to a delegate position rather than the second-level parent position.
To achieve this, what steps must be followed?
-
A
A value is specified for the Delegate Position attribute, the line manager synchronization needs to be based on the HCM Position Hierarchy, and the Synchronize Person Assignments from Position ESS process must be run.
-
B
The parent position is vacant, a value is specified for the Delegate Position attribute, the line manager synchronization needs to be based on Position Trees, and the Synchronize Person Assignments from Position ESS process must be run.
-
C
The parent position is vacant, a value is specified for the Delegate Position attribute, the line manager synchronization needs to be based on the HCM Position Hierarchy, and the Synchronize Person Assignments from Position ESS process must be run.
-
D
A value is specified for the Delegate Position attribute, the line manager synchronization needs to be based on Position Trees, and the Synchronize Person Assignments from Position ESS process must be run.
Reveal answer details
Close answer details
Correct answerC
ExplanationIn Oracle Global Human Resources Cloud, position hierarchies define reporting structures, and the Delegate Position attribute allows redirection of reporting lines when a parent position is vacant. The synchronization process ensures these changes reflect in person assignments.
Option A: This omits the condition that the parent position must be vacant, which is critical to trigger the delegate reassignment. It's incomplete.
Option B: Using "Position Trees" is incorrect; Oracle uses the "HCM Position Hierarchy" for line manager synchronization, not generic position trees, which are not a standard synchronization mechanism in this context.
Option C: This is correct: The parent position is vacant (trigger condition).
A Delegate Position attribute is specified (e.g., via the Manage Positions task) to redirect child position incumbents.
Line manager synchronization is based on the HCM Position Hierarchy (configured in Manage Enterprise
HCM Information).
The "Synchronize Person Assignments from Position" ESS process updates assignments to reflect the delegate position.This aligns with Oracle's position management functionality.
Option D: Like B, it incorrectly references "Position Trees" instead of the HCM Position Hierarchy, making it invalid.
The correct answer isC, as detailed in "Implementing Global Human Resources" under Position Management. References:
Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 9:
Position Structures.
Question 25
Single choice
Which statement is true regarding Payroll Statutory Units (PSUs)?
-
A
A legal employer must have only one PSU.
-
B
A PSU can support multiple legislative data groups.
-
C
A PSU is used to group legal employers for payroll reporting.
-
D
PSUs cannot be shared across business units.
Reveal answer details
Close answer details
Correct answerC
ExplanationPayroll Statutory Units consolidate legal employers for statutory payroll reporting.
A single PSU belongs to a single LDG, not multiple.
Multiple PSUs may exist in one enterprise.
References:
Implementing Global Human Resources - Payroll Statutory Units.
Question 26
Lab simulation
Simulation Manage Business Unit Scenario An additional business unit is required for the newly acquired company to reflect the business rules and policies that must be enforced within the organization. Task Create a Business Unit for the technician group, where: 1. The Code is x Tech Business Unit
2. The Default set is COMMON
Reveal model answer
Close model answer
This task requires creating a business unit in Oracle Global Human Resources Cloud for the technician group of a newly acquired company. The business unit must have a Code of x Tech Business Unit and a Default Set of COMMON. 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 as Application Implementation Consultant or HCM 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 business units. The user must have permissions to access the Workforce Structures functional area and the Manage Business Unit task. Roles like Application Implementation Consultant include the
necessary privileges (e.g., Manage Business Unit duty role).
Verification: Oracle documentation confirms that setup tasks require specific security roles, and the Manage Business Unit task is restricted to authorized users. Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section: Security for Setup Tasks. Step 2: Navigate to Setup and Maintenance Action: From the Oracle Fusion Applications home page, click the Navigator icon (hamburger menu) in the top-left corner.
Under the Tools section, select Setup and Maintenance.
Explanation: The Setup and Maintenance work area provides access to all implementation and configuration tasks, organized by functional areas. This is the entry point for accessing the Manage Business Unit task.
Verification: Oracle's user interface consistently places Setup and Maintenance under the Navigator's
Tools section, as confirmed in both Redwood and responsive interfaces.
References:
Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:
Setup and Maintenance Overview.
Step 3: Select the Workforce Structures Functional Area and Locate the Task Action: In the Setup and Maintenance work area, click the Functional Area dropdown and select Workforce Structures.
In the task list, locate Manage Business Unit by scrolling or using the search bar (type "Manage Business Unit").
Click the Go to Task icon (typically a play button or arrow) next to Manage Business Unit to open the task.
Explanation: The Workforce Structures functional area includes tasks related to organizations, including
business units. The Manage Business Unit task is designed to create and manage business units, which enforce business rules and policies. Using the search bar ensures quick access if the task list is extensive.
Verification: Oracle documentation lists Manage Business Unit under Workforce Structures, accessible via the Setup and Maintenance UI in both Redwood and responsive interfaces.
Reference: Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Manage
Business Unit.
Step 4: Initiate Creation of a New Business Unit Action: On the Manage Business Unit page, click the Create button (typically a plus sign (+) or labeled "Create" in the Redwood interface).
This opens the Create Business Unit page for entering the business unit details.
Explanation: The Manage Business Unit page displays a searchable list of existing business units. The
Create action starts the process of adding a new business unit, opening a form where the code, name, and default set can be specified.
Verification: Oracle's UI for managing business units includes a Create button, as confirmed in documentation and Redwood interface updates (24C and later).
Reference: Oracle Global Human Resources Cloud: Implementing Global Human Resources,
Section:Creating Business Units.
Step 5: Enter the Business Unit Details Action: On the Create Business Unit page, enter the following details as provided in the scenario: Name: Enter x Tech Business Unit.
Code: Enter x Tech Business Unit.
Default Set: Search for and select COMMON.
Click the Search icon (magnifying glass) in the Default Set field.
Enter COMMON in the search criteria and click Search.
Select COMMON and click OK.
Status: Ensure Active is selected (default setting).
Effective Start Date: Enter 04/15/2025 (current date, unless a specific date is required for the technician group).
Description (optional): Enter a description, e.g., "Business unit for x Cloud Vision technician group".
Country: Select United States (based on the company's location in Michigan, as per prior tasks).
Explanation: Name and Code: In Oracle HCM Cloud, the Name and Code for a business unit are often the
same forclarity, and the scenario specifies x Tech Business Unit for the code, which is used as the name as well. The code is a unique identifier in the system. Default Set: The COMMON set is a predefined reference data set used to share jobs, departments, locations, and grades across multiple business units.
Selecting COMMON ensures the technician group's workforce structures are accessible broadly unless restricted later.
Status: Active ensures the business unit is immediately usable for transactions and policies.
Effective Start Date: Oracle uses effective dating for business units to track validity. The current date
(04/15/2025) is appropriate unless otherwise specified.
Description: While optional, a description aids in identifying the business unit's purpose, especially for the technician group.
Country: United States aligns with the company's Michigan location, ensuring compliance with regional settings.
Verification: Oracle documentation specifies mandatory fields (Name, Code, Default Set, Country) and optional fields (Description) for business unit creation. The COMMON set is a standard option, and the details align with US-based configurations.
Reference: Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Business
Unit Fields.
Step 6: Configure Additional Settings (if prompted)
Action:
Reporting Establishment: If prompted, leave blank or select an existing establishment tied to the legal entity, but this is not required by the scenario.
Manager: If a manager field appears, leave blank, as no manager is specified.
Payroll Statutory Unit: If prompted, leave blank, as the PSU is handled by the legal entity (x Cloud Vision)
Explanation: Reporting Establishment: Business units may link to establishments for reporting, but the
scenario does not require this.
Manager: Assigning a manager is optional and not specified here.
Payroll Statutory Unit: The PSU is already set at the legal entity level, so no additional PSU configuration is needed for the business unit.
Verification: Oracle documentation confirms that fields like Reporting Establishment are optional, and PSU settings are typically managed at the legal entity level.
Reference: Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:
Business Unit Configurations.
Step 7: Save the Business Unit Action: After entering all details, click Save and Close (or Save if further edits are needed).
If prompted, confirm the creation of the business unit.
Explanation: Saving creates the business unit in the system, making it available for enforcing business
rules and policies for the technician group. The Save and Close button finalizes the task, while Save allows additional configurations if needed. Oracle validates mandatory fields before saving.
Verification: Oracle's UI includes Save and Save and Close options for business unit creation, as confirmed in documentation for both responsive and Redwood interfaces.
Reference: Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:
Saving Business Units.
Step 8: Verify the Business Unit Creation Action: Return to the Manage Business Unit page.
In the search criteria, enter x Tech Business Unit and click Search.
Confirm that the new business unit appears with the details: Name: x Tech Business Unit Code: x Tech Business Unit Default Set: COMMON Status: Active Effective Start Date: 04/15/2025
Country: United States
Description (if entered): Business unit for x Cloud Vision technician group
Explanation: Verification ensures the business unit was created correctly and is ready to enforce rules for
the technician group. Searching by name or code confirms the record's accuracy and checks for errors in data entry.
Verification: Oracle documentation emphasizes verifying setup tasks by searching created records, and the Manage Business Unit page supports detailed searches.
Reference: Oracle Global Human Resources Cloud: Using Global Human Resources, Section: Searching
Business Units.
Step 9: Prepare for Business Rules and Policies (Optional)
Action:
Note that the x Tech Business Unit can now be used in tasks like Manage HCM Role Provisioning Rules, Manage Approval Policies, or Manage Data Access to define specific rules and policies for the technician group.
For example, assign the business unit to specific departments or jobs in the Manage Departments or Manage Jobs tasks to align with the technician group's scope.
Explanation: The scenario mentions enforcing business rules and policies, which occurs after business
unit creation in separate tasks. The x Tech Business Unit is now available for these configurations, ensuring the technician group operates under tailored settings (e.g., approval workflows, data access).
This step is optional, as the task focuses on creation, but it highlights the business unit's purpose.
Verification: Oracle documentation confirms that business units are used to scope rules and policies, and the created unit will appear in relevant setup tasks.
Reference: Oracle Global Human Resources Cloud: Implementing Global Human Resources, Section:
Using Business Units.
Detailed Explanation
Purpose of Business Units: Business units organize business functions (e.g., HR, payroll, approvals) and enforce rules and policies. The x Tech Business Unit ensures the technician group operates under specific settings, supporting the acquired company's integration. Default Set (COMMON): The COMMON set allows the business unit to share jobs, departments, locations, and grades across the enterprise, reducing setup complexity unless isolation is needed (e.g., via xTECH from). This aligns with broad accessibility for the technician group.
Code and Name: The Code (x Tech Business Unit) is a unique system identifier, and the Name matches for consistency, as is common in Oracle HCM configurations.
Country Context: United States ties the business unit to the company's Michigan operations, ensuring compliance with regional settings.
Redwood Interface: In the Redwood interface (24C and later), the Manage Business Unit page may feature enhanced UI elements (e.g., streamlined forms, inline validation), but the fields and steps remain consistent with the responsive interface.
Effective Dating: The effective start date ensures the business unit is active, supporting future changes if the technician group's scope evolves.
Key Considerations
Accuracy: The Code and Name (x Tech Business Unit) and Default Set (COMMON) must be entered exactly as specified to ensure system recognition and alignment with the scenario.
Uniqueness: The Code must be unique. If x Tech Business Unit exists, an error occurs, requiring a unique
code.
Default Set Availability: The COMMON set is a standard Oracle set. If not found, it indicates a configuration issue, as COMMON is always available.
Security: Only users with the Manage Business Unit privilege can perform this task. Role mismatches require administrative intervention.
Policy Setup: The business unit is ready for rule enforcement, but additional tasks (e.g., approval policies) are needed to fully implement the scenario's intent.
Potential Challenges and Solutions Access Denied: If the user lacks the Manage Business Unit privilege, an error occurs.
Solution: Assign the Application Implementation Consultant role via Security Console.
Duplicate Code: If x Tech Business Unit already exists, the system prevents saving. Solution: Search for
the code first
if it exists, coordinate with the implementation team to resolve conflicts or use a different
code.
Redwood UI Variations: The Redwood interface may use different button labels (e.g., Add instead of Create) or layouts. Solution: Follow field prompts and ensure Code and Default Set are completed.
COMMON Set Not Found: If COMMON is missing, it may indicate a corrupted setup. Solution: Verify set availability in Manage Reference Data Sets or contact Oracle Support.
Country Selection: If United States is not selected, regional settings may misalign. Solution: Confirm United States to match the Michigan context.
References
Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
Section: Manage Business Unit: "Steps to create business units, including code, name, and default set."
Section: Business Units in Workforce Structures: "Explains how business units enforce rules and policies."
Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com,
Published: 2024-07-02
Section: Creating Business Units: "Details on configuring business units for organizational functions."
Section: Reference Data Sets: "Use of COMMON set for shared data access."
Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com,
Published:2024-08-27
Section: Redwood Experience for Workforce Structures: "Improved UI for business unit management."
Oracle Fusion Cloud Human Resources 25A What's New, Document ID: docs.oracle.com, Published:2025-03-20
Section: Workforce Structures: "Enhanced support for business unit configurations.
Question 27
Single choice
By default, any user who has access to Checklist Templates can create Task Groups to create a group of common tasks. How can we restrict the creation by Role?
-
A
Configure Role in Category Security.
-
B
Configure Exclude Rules from Workforce Structures.
-
C
Configure Person Security Profile.
Reveal answer details
Close answer details
Correct answerA
ExplanationPosition Synchronization in Oracle Global Human Resources Cloud allows assignments to inherit values from associated positions, streamlining workforce management by ensuring consistency between position definitions and employee assignments. The question asks for three advantages of using Position Synchronization, given that the customer has chosen Position Management for this functionality. The provided web results offer detailed insights into how Position Synchronization operates, which are leveraged here to validate the answer. Option A: The customer can configure which assignment attributes to synchronize from the position.This is a correct answer. Position Synchronization allows customers to select specific attributes (e.g., job, department, location, manager) to synchronize from the position to the assignment. This configurability is set at the enterprise or legal entity level using tasks like Manage Enterprise HCM Information or Manage Legal Entity HCM Information. For example, a customer might choose to synchronize the job and manager but not the location, tailoring the synchronization to their needs. Oracle documentation confirms that users can specify which attributes are inherited, providing flexibility in workforce management.
Option B: For synchronized attributes, any position update will automatically be pushed to the incumbents' assignments.This is a correct answer. When Position Synchronization is enabled, changes to synchronized attributes in a position (e.g., updating a position's department) are automatically reflected in all active assignments linked to that position. This automation reduces manual updates and ensures consistency across incumbents' assignments. The Synchronize Person Assignments from Position process may be required for retroactive changes, but for active assignments, updates are typically automatic for synchronized attributes. Oracle documentation highlights that synchronized attributes inherit changes, streamlining maintenance.
Option C: Synchronized attributes will be displayed as read-only in the assignment to ensure the position as the only source of truth.This is a correct answer. To maintain data integrity, synchronized attributes in an assignment are displayed as read-only, preventing manual edits at the assignment level unless override is explicitly allowed. For instance, if the manager attribute is synchronized, the assignment's manager field cannot be changed directly, ensuring the position remains the single source of truth. Oracle documentation notes that this read-only behavior enforces consistency, though overrides can be configured if needed.
Option D: If you use Position Synchronization, Manager Self Service cannot be used.This option is incorrect. There is no restriction in Oracle HCM Cloud preventing the use of Manager Self Service when Position Synchronization is enabled. Manager Self Service allows managers to perform actions like viewing team details or initiating transactions, and these functions are compatible with Position Synchronization. Oracle documentation does not mention any such limitation, and Position Synchronization operates independently of self-service capabilities, making this option invalid.
Why these three advantages?The advantages in , , and C directly align with the benefits of AB Position Synchronization: configurability (choosing attributes), automation (automatic updates), and data integrity (read-only attributes). These features reduce administrative effort, ensure consistency, and maintain a single source of truth, which are critical for effective workforce management. Option D is a false statement, as Position Synchronization does not restrict Manager Self Service. References:
Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
Section: Position Synchronization: "You can select attributes to synchronize, and synchronized attributes are inherited automatically by assignments. Synchronized fields are read-only unless overrides are allowed."
Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs. oracle.com,
Published: 2024-07-02
Section: Position Management: "Changes to positions are reflected in assignments for synchronized attributes, ensuring consistency."
Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published:
2024-08-27
Section: Workforce Structures Enhancements: "Position Synchronization improvements for attribute management."
Question 28
Single choice
In order for a worker to complete a checklist item before their hire date, the following must be done?
-
A
The worker must have been added as an applicant in Recruiting Cloud
-
B
The worker needs to be added as an Employee with a future hire date
-
C
The worker must be added as a Pending Worker with an effective date equal to or less than the system date and a future hire date
Reveal answer details
Close answer details
Correct answerC
ExplanationChecklists in Oracle Global Human Resources Cloud can be assigned to workers before their official hire date, typically during onboarding. The "Using Global Human Resources" guide under "Checklists and Onboarding" explains that for a worker to access and complete checklist tasks prior to their hire date, they must be added as a Pending Worker. A Pending Worker record requires an effective date (start date of the record) that is equal to or earlier than the current system date, allowing system access, and a future hire date (when they transition to an Employee). This setup enables pre-hire tasks, such as completing forms, to be actioned.
Option A (applicant in Recruiting Cloud) doesn't grant HCM access, and Option B (Employee with future hire date) doesn't allow pre-hire task completion before the hire date is effective.
Option C is precise and correct.
References:
Oracle Global Human Resources Cloud - Using Global Human Resources, "Pending Workers
and Checklists" section.
Question 29
Single choice
When creating your THEN condition, which Approver Types enable you to configure the Automatic Approval Action type?
-
A
Representative, Management Hierarchy, Position Hierarchy
-
B
Users, Representative, Management Hierarchy, Job Level Based Line Manager Hierarchy, Position
Hierarchy
-
C
Application Role, Users, Representative, Approval Groups
-
D
Management Hierarchy, Job Level Based Line Manager Hierarchy, Position Hierarchy
-
E
Approval Groups, Representative, Management Hierarchy, Position Hierarchy
Reveal answer details
Close answer details
Correct answerE
ExplanationIn 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. References:
Oracle Docs - "Implementing Global Human Resources" (docs.oracle.com, published 2023-
12-12), Approval Rules Configuration.
|