Search Results psb_employees




Overview
Explore in AI Chat

Overview

The PSB_EMPLOYEES table is a core data object within the Oracle E-Business Suite Public Sector Budgeting (PSB) module. It serves as the central repository for storing employee information that is critical for budget planning and analysis in a government or public sector context. Its primary role is to provide a master list of employees, identified by a unique EMPLOYEE_ID, which can be linked to various budgeting components such as position funding, salary forecasts, and personnel cost allocations. The table's existence is fundamental to enabling the integration of human resource data with the financial budgeting processes that the PSB module automates.

Key Information Stored

While the provided ETRM metadata does not list all columns, the documented structure confirms the EMPLOYEE_ID column as the primary key, uniquely identifying each employee record. Based on standard PSB data models and the table's purpose, it typically stores attributes essential for budgetary calculations. This commonly includes employee names, assignment details, job codes, salary grades, and effective dates. The table likely contains columns linking to foundational EBS entities, such as PERSON_ID from the HR schema, to ensure data consistency across the application. The primary key constraint, PSB_EMPLOYEES_PK, enforces the uniqueness of the EMPLOYEE_ID, guaranteeing data integrity for all related budgeting transactions.

Common Use Cases and Queries

This table is primarily accessed during budget formulation to associate personnel costs with specific budget lines and organizational units. A common reporting use case involves generating a list of all employees included in a fiscal year's budget plan. Sample SQL patterns often involve joining PSB_EMPLOYEES to budget-specific tables, such as those holding salary proposals or position budgets. For instance, a query to validate employee data in the budgeting system might follow this pattern:

  • SELECT e.employee_id, e.full_name FROM psb.psb_employees e WHERE EXISTS (SELECT 1 FROM psb_budget_lines bl WHERE bl.employee_id = e.employee_id);

Another critical use case is during data validation and migration, where scripts check for the existence of an employee in PSB_EMPLOYEES before inserting related budget detail records, thereby preventing foreign key constraint violations.

Related Objects

The documented primary key relationship indicates that PSB_EMPLOYEES is a parent table. Other tables within the PSB schema will hold foreign key references to PSB_EMPLOYEES.EMPLOYEE_ID to maintain referential integrity. While specific child tables are not named in the provided excerpt, typical related objects in the PSB module include budget detail tables (e.g., PSB_BUDGET_LINES), position budget tables, and salary forecast tables. These child tables would use EMPLOYEE_ID as a foreign key column to link transactional budgeting data back to the master employee record. The constraint name PSB_EMPLOYEES_PK is explicitly referenced by these foreign key constraints in the dependent objects.