Oracle Fusion HCM: Diagnosing Missing Worker Records in Reports
Oracle Fusion HCM: Diagnosing Missing Worker Records in Reports
If a worker appears in one Oracle Fusion HCM page but not in a report, the cause may be the report’s effective date, filters, security context, or selected worker and assignment attributes. Validate each layer before changing the record.
1. Confirm the person and assignment context
Check whether the report is intended to return person records, work relationships, or assignments. These are related but not interchangeable reporting concepts.
2. Review effective dates
Effective-dated changes can make a record appear or disappear depending on the date used by the report. Verify the effective date and whether current, future, or historical records are included.
3. Inspect report filters
Check business unit, legal employer, department, worker type, assignment status, and other parameters. Confirm that the filters match the worker’s actual assignment values for the report date.
4. Check data security
Verify the reporting user’s roles and data access scope. If a report works for an authorized administrator but not another user, compare security context before assuming the data is missing.
5. Compare with source details
Use an approved worker inquiry to compare relevant fields and effective-dated rows. If the report is custom, review its joins, date conditions, and security-aware data source.
Document the result
Record the user context, report parameters, effective date, and a sanitized example. Avoid sharing unnecessary personal data when escalating the issue.
For structured learning, visit Oracle Fusion HCM / HR training.