Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, Page Composer and Transaction Design Studio (TDS) are tools for customizing UI behavior. Page Composer modifies page layouts globally or by role, while TDS applies transaction-specific rules, often by role or context. When configurations conflict, precedence is determined by the system's conflict resolution logic.
Option A: Incorrect. Page Composer does not universally override TDS; precedence depends on timing and context.
Option B: Correct. When conflicting changes exist (e.g., Page Composer making location required, TDS hiding it for managers), Oracle applies thelast changemade in either tool. The system uses a timestamp-based approach to resolve conflicts, ensuring the most recent configuration takes effect.
Option C: Incorrect. Conflicting configurations do not cause page errors; the system resolves them silently.
Option D: Incorrect. TDS does not universally override Page Composer; it depends on the order of changes.
The correct answer isB, per "Using Global Human Resources" on UI customization tools.

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.

Full Detailed In-Depth Explanation:
In Oracle Global Human Resources Cloud, the compa-ratio (comparison ratio) measures an employee's salary against the midpoint of a grade rate range. It's displayed in the employment or salary details section when entering a base salary, provided all components are correctly aligned.
* Option A: Incorrect. Grade rates and salary basis don't need to share the same legislative data group (LDG) for compa-ratio calculation; LDGs partition data but don't directly affect this display unless misconfigured at a higher level.
* Option B: Incorrect. The grade itself isn't tied to an LDG; it's the grade rate that matters. This option misattributes the relationship.
* Option C: Incorrect. While frequency (e.g., monthly vs. annual) must align for accurate salary calculations, compa-ratio is normalized and should still display if the grade rate and salary basis are linked, even with frequency differences (assuming conversion is handled).
* Option D: Correct. The compa-ratio requires a grade rate (defining min, mid, max values) to be associated with the salary basis used in the employee's record. If the grade rate isn't linked to the salary basis (via "Manage Salary Basis" or "Manage Grade Rates"), the system lacks the reference range to compute and display the compa-ratio. This is a common setup oversight during implementation.
The correct answer isD, as detailed in "Using Global Human Resources" on salary management and grade rate integration.

Full Detailed in Depth Explanation:
The Global Human Resources (HR) Business Process in Oracle HCM Cloud encompasses core capabilities that manage workforce data, structures, and planning at a global level. According to Oracle documentation:
* Workforce Directory (A): Provides a centralized view of the workforce, including organizational hierarchies and worker details, which is integral to Global HR.
* Workforce Modeling (D): Enables scenario planning and organizational modeling, a key feature of Global HR for strategic workforce management.
* Core Human Resources (E): Covers essential HR functions like person management,employment records, and organizational structures, forming the backbone of Global HR.

See the solution in Explanation below.
Explanation:
This task requires creating a reference data set in Oracle Global Human Resources Cloud to associate departments, jobs, locations, and grades for a newly acquired company's technology group. The reference data set must have aCodeofXTECHand aSet NameofX Tech. 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: TheSetup and Maintenancework area is the central hub for configuration tasks, including managing reference data sets. The user must havepermissions to access theWorkforce StructuresorReference Data Setsfunctional area and theManage Reference Data Setstask. Roles like Application Implementation Consultantinclude the necessary privileges (e.g.,Manage Reference Data Setduty role).
* Verification: Oracle documentation confirms that setup tasks require specific security roles, and the Manage Reference Data Setstask is restricted to authorized users.