Introduction
In Oracle Fusion HCM, HR Help Desk categories are configured for use in the Agent and Employee experiences. Sometimes, a category that has been configured does not appear in the category drop-down list. In other cases, the list may appear empty. In this article, I’ll walk through the checks we used during implementation to investigate these issues.
Business Use Case
An HR Help Desk category is missing from the drop-down list for an agent or employee, or no category values appear in the field.
Common Reasons
There can be several reasons for this behaviour. The checks below are based on issues we encountered during implementation; the exact cause may vary depending on how your environment is configured.
- Category configuration
- User access and role synchronization
- SQL syntax in the
SVC_CATEGORIESdatabase resource condition - A missing or misspelled category code in the SQL query
- Data security policies
- Browser cache
Step 1: Verify Category Configuration
Navigate to Manage Categories for HR Help Desk Requests. Search for the category by name or code and confirm that it is active. If the category is inactive, it may not be available for selection.
Step 2: Verify User Access
Confirm that the agent or employee has the roles required to access the relevant HR Help Desk experience. During implementation, we also found cases where the role had been assigned but the relevant LDAP processes had not yet been completed. If the role was recently assigned, check that the required process has run.
Step 3: Check the SVC_CATEGORIES Condition
In the Security Console, navigate to Manage Database Resources and search for SVC_CATEGORIES in the Object Name field. Open the condition tab and review the SQL condition configured for the resource.
Check the query carefully for syntax issues, such as a missing opening or closing bracket. In our experience, a condition could be saved even when the query contained a syntax issue, so do not rely only on whether the configuration saved successfully.
Also verify that each category code referenced in the query is spelled correctly and has not been omitted. A misspelled or missing code can cause the expected category values not to appear.
For more details, see our guide on:
How to Restrict HR Help Desk Categories in Oracle Fusion HCM
Step 4: Verify Data Security Policies
Find the custom role used for the agent or employee experience and review the associated data security policies. Confirm that the required policy is present and configured for your implementation. If a required policy is missing, the expected category values may not appear.
If you add or update a policy, complete any required role or LDAP synchronization steps for your environment, then test again.
You can also refer to our step-by-step guide on:
How to Configure HR Help Desk Data Security Policy in Oracle Fusion HCM
Step 5: Clear the Browser Cache
Clear the browser cache, or try the page in a fresh browser session. We have seen cases where the category values appeared after the browser cache was cleared. This is a quick check to try after confirming the configuration and access.
Step 6: Test and Validate
Sign in with the appropriate agent or employee account and reopen the relevant HR Help Desk page. Confirm that the expected categories appear in the drop-down list. If the issue remains, revisit the checks above and compare the results between the Agent and Employee experiences, where applicable.
Related Articles
You may also find these Tecolabs articles useful:
- How to Restrict HR Help Desk Categories in Oracle Fusion HCM
- How to Configure HR Help Desk Data Security Policy in Oracle Fusion HCM
Conclusion
These are the checks we followed when investigating HR Help Desk category visibility issues during implementation. If your setup uses Business Unit functionality to control category visibility, the troubleshooting steps may differ from an implementation that uses a data security policy and a SQL condition in the SVC_CATEGORIES database resource.
I hope these steps help you narrow down the cause more quickly. If you have encountered a similar issue or found another check useful, feel free to share your experience in the comments. I’ll continue sharing practical Oracle HCM solutions and lessons learned from implementation work.


1 Comment