Oracle 1Z0-1046-24 Exam Questions

Full Detailed In-Depth

In Oracle Global Human Resources Cloud, tracking external training in the talent profile (Skills and Qualifications page) requires configuring content types and items via 'Manage Content Types' and 'Manage Content Items.'

Option A: Incorrect. The sequence is off; content types must precede content items, and 'person profile' linking is vague.

Option B: Correct:

Create a new content type (e.g., 'External Training') via Manage Content Types.

Create content items (e.g., specific training courses) under that type.

Link the content type to the person profile (via Manage Profile Types, associating it with the Skills and Qualifications section).

This ensures display on the page.

Option C: Incorrect. Linking to a 'model profile' (e.g., job/role profile) doesn't target individual worker records.

Option D: Incorrect. Content items come after content types, and model profile linking is irrelevant.

The correct answer is B, per 'Implementing Global Human Resources' on talent profiles.

Full Detailed In-Depth

In 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.

Full Detailed In-Depth

In Oracle Global Human Resources Cloud, the Public Info/Spotlight page in the Directory allows employees to update certain fields visible to others, managed via the 'Edit My Public Info' action.

Option A: 'HR representative information' is not editable by employees; it's system-managed.

Option B: Not a valid answer option.

Option C: 'Peer information' is not a standard editable field on the public profile.

Option D: 'Home address' is private and not part of the public profile; it's restricted.

Option E: Correct. Employees can update:

About me (bio),

Contact information (e.g., work phone),

Profile photo,

Public message (status),

Favorites (e.g., interests),

Background photo (header image).

The correct answer is E, per 'Using Global Human Resources' on Directory features.

Full Detailed In-Depth

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

In 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.