Full Detailed in Depth Explanation:
Oracle HCM Cloud uses a matching algorithm to identify duplicate person records during processes like hiring or candidate application, even across different legal employers within the same enterprise. This is critical to avoid creating duplicate records when a person reapplies with a changed national identifier.
Option B ("The application identifies a match if the first name, the first character of the last name, and date of birth are the same; or if the last name, the first character of the first name, and date of birth are the same") is correct. The system employs a configurable person-matching rule that typically uses a combination of key attributes-first name, last name (or initial), and date of birth-to determine if a record already exists. This rule is designed to handle cases where the national identifier changes, as it does not rely solely on that field.
The "Implementing Global Human Resources" guide confirms this matching logic, noting that the system checks these attributes to prevent duplication.
Option A ("Because the national identifier has changed, the system cannot identify the matching record") is incorrect because the matching process does not depend solely on the national identifier.
Option C ("The application searches for the availability of date of birth and middle name to identify the matching record") is incorrect because middle name is not a standard required attribute in the default matching rule.
Option D ("The application cannot identify the matching record and there will be two person records available for further processing") is incorrect because the system is designed to detect matches and avoid duplicate records when possible.
References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Section on Person Matching and Duplicate Prevention.
"Oracle Recruiting Cloud: Implementation Guide" - Candidate matching rules.

In Oracle Global Human Resources Cloud, Action Types categorize business processes (e.g., Hire, Terminate), while Actions are specific instances within those types (e.g., Voluntary Termination under Terminate). Understanding their relationship is key.
Option A: Correct. An Action Type (e.g., Termination) can have multiple Actions (e.g., Voluntary Termination, Involuntary Termination), allowing flexibility within a process category.
Option B: Correct. Oracle provides seeded Action Types (e.g., Hire, Transfer, Termination) as part of the base application, which can be used out-of-the-box or extended.
Option C: Incorrect. User-defined Actions can be created and linked to both seeded and custom Action Types, offering customization flexibility.
Option D: Incorrect. While you can create custom Actions, Action Types are seeded and cannot be created anew by users; they can only be extended via Actions.
Option E: Incorrect. "Termination" is an Action Type, and "Normal Termination" would be an Action under it, not the other way around.
The correct answers areAandB, as per "Implementing Global Human Resources" under Action Configuration.
References: Oracle Global Human Resources Cloud - Implementing Global Human Resources, Chapter 6:
Actions and Action Types.

The Alerts Composer in Oracle HCM Cloud is a tool for configuring informational notifications sent via email or worklist, based on predefined events. Event Alerts are triggered by specific application events, such as a new hire or promotion. The question asks about the behavior of these alerts, particularly regarding the modification of triggering criteria.
* Option A: Event Alerts are triggered when a specific event occurs in the application. You cannot modify the triggering criteria for notifications.This is the correct answer. Event Alerts in Alerts Composer are based on filters delivered by Oracle, tied to specific events (e.g., employee termination, assignment change). Oracle documentation states that the triggering criteria for these alerts are predefined and cannot be modified by users, as they are linked to system events controlled by Oracle's seeded configurations. Users can customize notification content (e.g., message text) or recipients, but the event conditions themselves are fixed to ensure system stability and consistency.
* Option B: Event Alerts are triggered when a specific event occurs in the application. You can modify the frequency in which the alert is triggered by using the Run Options tab within the alert.
This option is incorrect. Alerts Composer does not provide a Run Options tab for Event Alerts, nor does it allow modification of the frequency of event-based triggers. Event Alerts are triggered immediately when the associated event occurs (e.g., a new hire record is saved). While Scheduled Alerts allow frequency settings (e.g., daily or weekly runs), Event Alerts are event-driven, and their triggering is not controlled by a frequency setting, making this option invalid.
* Option C: Event Alerts are triggered when a specific event occurs in the application. You can modify the triggering criteria for notifications by modifying the Groovy script within the specific alert.This option is incorrect. Event Alerts in Alerts Composer do not allow modification of triggering criteria via Groovy scripts. Oracle restricts customization of event triggers to maintain system integrity, and Groovy scripts are used in other contexts (e.g., for validations or calculations), not for altering Event Alert conditions. Documentation confirms that triggering criteria are Oracle-delivered and non- editable.
* Why this answer?The fixed nature of Event Alert triggers ensures standardized behavior across HCM Cloud implementations. Users can configure aspects like notification templates or recipients, but the core event conditions (e.g., "trigger when an employee is hired") are locked, aligning with Oracle's design and making A the correct statement.
References
* Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.
oracle.com, Published: 2024-07-02
* Section: Alerts Composer: "Event Alerts are based on Oracle-delivered filters and trigger when specific events occur. You can't modify the triggering criteria."
* Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID:
docs.oracle.com, Published: 2023-12-12
* Section: Configuring Alerts: "Event Alerts use predefined conditions; customization is limited to content and delivery options."
* Oracle Fusion Cloud Human Resources 24C What's New, Document ID: docs.oracle.com, Published: 2024-08-27
* Section: Alerts Enhancements: "Clarifications on Event Alerts and their fixed triggering mechanisms."

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.
References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Security profiles and notifications.
"Oracle Human Resources Cloud: Using Approvals" - Workflow configuration.

Full Detailed in Depth Explanation:
In Oracle Global Human Resources Cloud, approval routing policies determine how transactions (e.g., promotions, transfers) are routed for approval. These policies are configured using the "Manage Approval Transactions" task and rely on specific hierarchies and groups.
Option B ("Employee Supervisor Hierarchy, Position Hierarchy, Job Levels, Approval Groups") is correct.
Oracle HCM Cloud supports the following bases for defining approval rules:
Employee Supervisor Hierarchy: Routes approvals through the employee's reporting structure.
Position Hierarchy: Uses the position hierarchy if positions are implemented.
Job Levels: Routes based on job level differences (e.g., requiring higher-level approval for significant changes).
Approval Groups: Predefined groups of approvers for specific transactions.
The "Implementing Global Human Resources" guide confirms these as the standard components.Grades and Organization Hierarchy (e.g., Department or Division) are not directly used in approval routing policies, making other options incorrect.
Option A includes "Grades" and "Organization Hierarchy," which are not standard bases.
Option C omits "Approval Groups," which is a key component.
Option D adds "Organization Hierarchy," which is not supported for approval routing.
References:
"Oracle Global Human Resources Cloud: Implementing Global Human Resources" - Chapter on Approvals, section on configuring approval policies.
"Oracle Human Resources Cloud: Using Approvals" - Approval routing options.