Results for “psb_employees”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PSB_EMPLOYEES table is owned by the PSB schema and forms part of the Public Sector Budgeting (PSB) module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It holds employee information used by Public Sector Budgeting to associate personnel with budgeting positions, worksheets, and line balances. Because PSB supports position-based budgeting in government and public sector organizations, the employee record serves as the master reference for individuals whose salaries, assignments, and distribution costs are projected through the budgeting cycle.

The table contains 20 documented columns and carries the primary key constraint PSB_EMPLOYEES_PK on EMPLOYEE_ID, supported by the unique index PSB_EMPLOYEES_U1. From a Data Vault modeling perspective, the mined foreign key structure classifies this object as standalone, which suggests it behaves primarily as a hub or reference dimension rather than a dependent link or satellite. In practice it acts as a hub-like reference of employee identities, enriched by descriptive attributes residing directly on the same table.

Key Information Stored

The following columns represent the most significant data held on the table:

• EMPLOYEE_ID — The surrogate primary key, uniquely identifying each row in PSB_EMPLOYEES and serving as the foreign key target for a large number of dependent tables across EBS.
• HR_EMPLOYEE_ID — The link back to the Oracle HR employee record (PSB_EMPLOYEES_I, per the documented foreign key). This column is the critical bridge between PSB budgeting data and the HRMS repository.
• DATA_EXTRACT_ID — References PSB_DATA_EXTRACTS, identifying the extract batch through which the employee record entered PSB.
• BUSINESS_GROUP_ID — The business group (HR organization) to which the employee belongs, enabling multi-organization filtering.
• EMPLOYEE_NUMBER — The business-facing employee number assigned in HR, a business-key candidate often used in user-facing reports.
• FIRST_NAME, MIDDLE_NAMES, LAST_NAME, FULL_NAME — Name attributes used for display, sorting, and reporting.
• KNOWN_AS — The preferred or familiar name used in user interfaces and reports.
• TITLE — The employee's job title as extracted for budgeting purposes.
• EMAIL_ADDRESS — Contact information for notification and workflow purposes.
• DATE_OF_BIRTH, SEX, MARITAL_STATUS — Demographic attributes inherited from the HR extract.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns supporting audit and concurrency tracking.

Common Use Cases and Queries

PSB_EMPLOYEES is typically queried when joining budgeted position and line-balance data to employee identity and HR information. A common pattern resolves the PSB employee to the HR record:

• Joining PSB_EMPLOYEES to PSB_POSITION_ASSIGNMENTS on EMPLOYEE_ID to list employees assigned to budgeted positions.
• Joining to PSB_WS_LINE_BALANCES_I on EMPLOYEE_ID to attribute worksheet line balances to individuals.
• Filtering by BUSINESS_GROUP_ID and DATA_EXTRACT_ID to report on a specific extract or organization.
• Lookups by EMPLOYEE_NUMBER or FULL_NAME for ad hoc employee searches.

A representative query pattern is: SELECT e.EMPLOYEE_NUMBER, e.FULL_NAME, e.TITLE FROM PSB.PSB_EMPLOYEES e WHERE e.BUSINESS_GROUP_ID = :p_bg_id ORDER BY e.LAST_NAME, e.FIRST_NAME;

Related Objects

The FK relationships documented for PSB_EMPLOYEES reveal a wide dependency graph. The most significant related objects include:

• PSB_EMPLOYEES_I — Referenced through HR_EMPLOYEE_ID; the HR-side employee interface record.
• PSB_DATA_EXTRACTS — Referenced through DATA_EXTRACT_ID; the extract batch that populated the row.
• PSB_POSITION_ASSIGNMENTS — References PSB_EMPLOYEES.EMPLOYEE_ID; ties employees to budgeted positions.
• PSB_WS_LINE_BALANCES_I — References EMPLOYEE_ID; worksheet line balances attributed to the employee.
• FND_USER — References EMPLOYEE_ID; links the employee to the EBS application user account.
• AP_EXPENSE_REPORT_HEADERS_ALL — References EMPLOYEE_ID for expense-reporting integration.
• PO_ACCEPTANCES and PO_ACTION_HISTORY — Reference EMPLOYEE_ID for purchasing action attribution.
• RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — Reference EMPLOYEE_ID for receiving activity.
• WIP_TRANSACTIONS and WIP_RESOURCE_ACTUAL_TIMES — Reference EMPLOYEE_ID for manufacturing labor accounting.

The breadth of referencing tables indicates that PSB_EMPLOYEES.EMPLOYEE_ID is reused as a shared employee identifier across many EBS modules, underscoring the importance of maintaining referential integrity when PSB extracts are refreshed.