Search Results psb_employees_u1

Overview

The PSB.PSB_EMPLOYEES table is a core data repository within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Public Sector Budgeting (PSB) module. It functions as a read-only staging table for employee demographic information. Its primary role is to store a synchronized extract of employee master data sourced from Oracle Human Resource Management Systems (HRMS). This design ensures that budgeting processes within PSB operate on a consistent and controlled snapshot of HR data, preventing direct modifications from the budgeting application and maintaining data integrity across the integrated EBS landscape.

Key Information Stored

The table stores fundamental employee identifiers and personal details. The key columns include:

• EMPLOYEE_ID: The primary key and unique identifier for the employee record within the PSB module.
• HR_EMPLOYEE_ID: A critical foreign key that links the PSB record to the originating employee record in the source HRMS system (e.g., PER_ALL_PEOPLE_F). This is the column referenced in the user's search.
• DATA_EXTRACT_ID: Identifies the specific data extraction batch, allowing for versioning and tracking of HR data loads into PSB.
• EMPLOYEE_NUMBER: The business-facing employee identifier or badge number from HRMS.
• Demographic Data: Columns such as FIRST_NAME, LAST_NAME, FULL_NAME, DATE_OF_BIRTH, EMAIL_ADDRESS, and SEX store personal information.
• Standard Who Columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit trails.

Common Use Cases and Queries

This table is central to any PSB reporting or process requiring employee context, such as budgeting by personnel cost, assigning budget preparers, or generating employee-based reports. A common use case is validating or troubleshooting the HR data extract by comparing PSB records with the source HRMS system. The non-unique index on HR_EMPLOYEE_ID and DATA_EXTRACT_ID (PSB_EMPLOYEES_N1) is optimized for such joins.

Sample Query: Find PSB employee details for a specific HR employee identifier.

SELECT pe.full_name, pe.employee_number, pe.email_address, pe.hr_employee_id
FROM psb.psb_employees pe
WHERE pe.hr_employee_id = <input_value>;

Sample Query: List all employees imported in a specific data extract.

SELECT pe.employee_number, pe.full_name, pe.business_group_id
FROM psb.psb_employees pe
WHERE pe.data_extract_id = <extract_id>
ORDER BY pe.last_name, pe.first_name;

Related Objects

The table's primary integration is through the HR_EMPLOYEE_ID column, which serves as the logical link to the HRMS source. While explicit foreign key constraints are not detailed in the provided metadata, the documented relationship data indicates the following key dependency:

• Primary Key: The table is governed by the PSB_EMPLOYEES_PK primary key constraint on the EMPLOYEE_ID column. This unique identifier is referenced by other PSB module tables (such as budget assignment or salary detail tables) to associate financial data with an employee. The PSB_EMPLOYEES_U1 index enforces this uniqueness.
• HRMS Source: The HR_EMPLOYEE_ID column is a foreign key pointing to the corresponding surrogate key (typically PERSON_ID) in the HRMS person tables, most notably PER_ALL_PEOPLE_F. This is the definitive relationship for data lineage.
• Data Extract Context: The DATA_EXTRACT_ID column relates to the PSB data extraction control tables, which manage the batch process of pulling HR data into the PSB schema.