Querying an Oracle Fusion username and account status starts with the user-account record. Employment status and account status are different facts. An active employee can have a suspended account, and a worker search alone cannot establish whether sign-in is enabled.
Use a scoped request such as GET /hcmRestApi/resources/11.13.18.05/userAccounts?q=PersonNumber='100123'&limit=5. Alternatively, filter by the documented username attribute. The person number is synthetic. Confirm the selected account belongs to the intended employee before retrieving its details.
Retain the returned GUID. Oracle uses that identifier in the account item route, GET /hcmRestApi/resources/11.13.18.05/userAccounts/{GUID}. The numeric person ID and displayed username should not be substituted for the GUID. Oracle's user-account reference describes the account response.
Read SuspendedFlag according to the documented representation returned by the user-account service. Preserve the returned value when troubleshooting a consumer that expects a boolean or text. If activation evidence is needed, inspect the documented identity resource separately. The account response does not expose a universal active-status field.
Compare the account's person reference with the resolved worker record. If the person-number query finds no account, verify visibility and the business identifier before treating the result as a provisioning failure. A missing result and an HTTP authorization error need different investigations.
This SQL adapts CLHAPI's person/account matching into a lookup for synthetic person number 100123. Oracle's user-query examples document the suspension and termination fields. The person row is current; the returned account dates are not filtered away.
SELECT p.person_number,
u.person_id,
u.username,
u.start_date,
u.end_date,
u.hr_terminated,
u.suspended
FROM per_all_people_f p
JOIN per_users u
ON u.person_id = p.person_id
WHERE p.person_number = '100123'
AND TRUNC(SYSDATE) BETWEEN p.effective_start_date
AND p.effective_end_date
ORDER BY u.username;Read SUSPENDED with the account dates and identity-service evidence. HR_TERMINATED concerns the HR relationship and does not prove whether authentication will succeed. Reporting-table access can differ from REST visibility.
If the account exists but data is inaccessible, inspect its role assignments separately. Oracle documents the account's role child resource. Roles and Financials data-security assignments answer different access questions. The data-access comparison guide covers the latter.
Fusion Toolkit's worker-identity investigation combines scoped worker and account lookups with a supported SCIM identity read. SCIM is an identity-management API. Access to that resource remains subject to Oracle permissions; failure there does not invalidate a separately successful user-account lookup.
Keep this investigation read-only until the responsible administrator approves a specific correction. Account activation or role changes affect access and need their own verification. The examples were reviewed on 8 November 2026.
You can also use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Find employee 100123's username and tell me whether the Oracle account is active or suspended." It can perform the supported lookups without requiring you to write the query. Ask for the account evidence before requesting any change.