Fixing the Oracle Element Results Register

If you have ever tried to create a custom report and modify or even filter the Oracle Cloud HCM elements entries results register you may have found some of the parameters do not work.

One of the most common ones is to try and filter using Person Number.

If you preview the parameters available for filtering Person Number exists as one of them, however when using this field you would have found that you get no results returned.

Looking into the Oracle BI data model for this report we can see the issue.

As part of the seeded report it has been built with the Person Number field being joined up to the Person ID field, which are 2 different numbers.

In Oracle Cloud HCM, understanding the distinction between Person Number and Person ID is essential for effective system management and configuration.

Person Number:

The Person Number is a configurable identifier that is assigned to each individual when they are entered into the system. This number can be generated automatically or manually assigned based on your organization’s specific requirements. Its format is flexible—allowing the use of prefixes, suffixes, or entirely custom sequences—making it adaptable to your business rules and processes.

This identifier is primarily user-facing, meaning it’s the one HR professionals, managers, and other users will commonly interact with during day-to-day operations. It’s designed to be memorable and easily referenced in reports, employee records, and searches within the system.

Person ID:

On the other hand, the Person ID is a system-generated, unique numeric identifier assigned automatically by Oracle HCM. This ID is integral to the system’s internal operations, ensuring data consistency and integrity across various tables and modules. Unlike the Person Number, the Person ID is not something you would customize or even regularly see, as it is intended for backend use and is crucial for developers and technical teams working on integrations, data migrations, or troubleshooting within the system.

Key Differences:

• Visibility: Person Number is prominently visible to end-users and is used across the application’s interface, while the Person ID operates behind the scenes, critical to the system’s internal workings.
• Customization: You have the flexibility to define the format and generation rules for Person Number to align with your organization’s needs, whereas the Person ID is automatically generated by the system and remains immutable.
• Purpose: Person Number serves as a practical, user-friendly reference for day-to-day HR tasks, while the Person ID is fundamental for maintaining data integrity and supporting system functionality.

As someone who has worked extensively with Oracle HCM for over two decades, I can’t stress enough the importance of configuring these identifiers correctly from the start. Doing so ensures that your HR processes run smoothly and that your data remains consistent and reliable throughout the system.

If you need help with your seeded reports or custom reports, reach out to the Oracle Cloud HCM Experts @MKSK Consulting!