Query employee details in Oracle Fusion HCM by resolving one worker first. The person number used by HR, the numeric person ID and the worker resource key serve different purposes. Copying a person number into an item URL can target an invalid resource even when the employee exists.
A scoped read is GET /hcmRestApi/resources/11.13.18.05/workers?q=PersonNumber='100123'&fields=PersonId,PersonNumber&limit=5. The person number is synthetic. Use a test employee and an account with the required HCM visibility. Confirm one matching worker before following its child resources.
Oracle's workers resource reference describes supported filters and returned properties. A name search can produce several people or name records. Use the documented finder or queryable fields, then resolve the result using the employee's confirmed person number. Do not choose the first name match silently.
Keep the returned resource links while resolving the worker key. The key used in a worker URL may be a composite hash rather than the numeric person ID. Follow the identified worker's same-origin link. Avoid constructing the key from assumptions about its format.
For names, request the resolved worker's names child collection. Check the name type and applicable dates before choosing the display value. For email addresses, read the emails child collection and select the appropriate work address using the documented type and dates. Returning every address is unnecessary for a work-contact question.
Specify the effective date when the business question concerns a past or future record. Oracle documents worker reads at a selected date. A current lookup cannot establish the employee's department or assignment at the time of an older transaction.
This SQL adapts the CLHAPI person-and-name lookup for synthetic person number 100123 on 31 October 2026. It omits the assignment join to keep the result at person level. Replace the person number and both dates together.
SELECT p.person_number,
p.person_id,
pnf.display_name
FROM per_all_people_f p
JOIN per_person_names_f pnf
ON pnf.person_id = p.person_id
AND DATE '2026-10-31' BETWEEN pnf.effective_start_date
AND pnf.effective_end_date
AND pnf.name_type = 'GLOBAL'
WHERE p.person_number = '100123'
AND DATE '2026-10-31' BETWEEN p.effective_start_date
AND p.effective_end_date
ORDER BY p.person_number;The query returns a global name rather than an email address or department. Use the child-resource reads above for those details. Confirm table visibility under your reporting account before treating an empty result as a missing employee.
In Fusion Toolkit, select the required test profile before making the read. The AI Administrator worker-search recipe supports a documented filter and selected fields. The worker-identity investigation can connect a resolved worker with its account when that is the actual question. Keep an account lookup separate from the assumption that every worker has an active user account.
Check collection completeness and retain only the fields needed for the task. An empty response can reflect access restrictions or the chosen date. Compare the same employee in Oracle under the same account before concluding that the worker is missing. The examples were reviewed on 8 November 2026.
You can use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Find employee 100123 and show their work email and current department." It can retrieve supported Oracle records in plain language without requiring you to write SQL or a REST query. Start with one employee in your test environment.