Results for “psb_employees_i”

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

Overview

PSB_EMPLOYEES_I is a table in the PSB (Public Sector Budgeting) schema of Oracle E-Business Suite, documented as the interface table for PSB_EMPLOYEES. In Oracle EBS 12.1.1 and 12.2.2, PSB supports position and employee budgeting across public sector organizations, and interface tables of this type serve as the staging area where HR-sourced employee records are loaded, validated, and then transferred into the corresponding base table. PSB_EMPLOYEES_I therefore acts as the inbound integration point between Oracle HRMS and PSB budgeting structures, carrying employee, assignment, grade, pay, and personal details that budgeting workflows require.

Under the heuristic Data Vault classification derived from its foreign key structure, the object is satellite-leaning. That is a modeling suggestion: PSB_EMPLOYEES_I behaves less like an independent hub and more like a descriptive satellite attached to parent entities such as the data extract batch, position, and assignment records it references. Practitioners designing warehouse or reporting extracts should treat its attributes as descriptive payload rather than as durable business keys in their own right.

Key Information Stored

The table is documented with 33 columns in the 12.1.1 physical schema. The primary key is HR_EMPLOYEE_ID, which is also the business-key candidate that uniquely identifies each employee record within the table. Key columns include:

• HR_EMPLOYEE_ID — primary key and the principal business-key candidate for the employee record; this is the column most frequently referenced by related tables.
• DATA_EXTRACT_ID — identifies the PSB_DATA_EXTRACTS batch that produced the interface row, enabling traceability back to the source extract run.
• HR_POSITION_ID — links the employee to the position used in budgeting.
• EMPLOYEE_NUMBER — the HRMS-visible employee identifier.
• ASSIGNMENT_ID — the assignment record associated with the employee.
• GRADE_ID and GRADE_STEP — grade and step used for salary and FTE budgeting.
• PAY_BASIS and RATE_ID — pay basis indicator and the rate reference.
• FIRST_NAME, MIDDLE_NAMES, LAST_NAME, KNOWN_AS, FULL_NAME, TITLE — descriptive employee identity fields.
• SALARY_TYPE, RATE_OR_PAYSCALE_ID, ELEMENT_VALUE, PROPOSED_SALARY — salary and payscale detail used for costing.
• BUSINESS_GROUP_ID, SET_OF_BOOKS_ID — the HR business group and ledger context for the record.
• EFFECTIVE_START_DATE, CHANGE_DATE — date-effective control for the interface row.

Standard EBS audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE — are present for WHO-column tracking.

Common Use Cases and Queries

The most common use case is verifying that an employee extract loaded correctly before it is pushed downstream into PSB_EMPLOYEES. A typical validation query joins the interface table to its extract batch:

SELECT i.hr_employee_id, i.employee_number, i.full_name, i.data_extract_id FROM psb.psb_employees_i i WHERE i.data_extract_id = :extract_id;

Budget analysts use the grade, payscale, and proposed salary columns to reconcile position-level costing before commitment. A query matching positions to employees via HR_EMPLOYEE_ID supports FTE and salary rollups:

SELECT p.hr_position_id, e.hr_employee_id, e.grade_id, e.grade_step, e.proposed_salary FROM psb.psb_positions_i p, psb.psb_employees_i e WHERE p.hr_employee_id = e.hr_employee_id;

Integration troubleshooting focuses on orphan interface rows — records with no matching extract or assignment — and on duplicate HR_EMPLOYEE_ID values that would violate the primary key.

Related Objects

The following objects are the most significant dependencies, all grounded in the documented FK relationships:

• PSB_DATA_EXTRACTS — referenced by PSB_EMPLOYEES_I.DATA_EXTRACT_ID; the parent batch record for each extract run.
• PSB_EMPLOYEE_ASSIGNMENTS_I — referenced via HR_POSITION_ID; also itself references PSB_EMPLOYEES_I through HR_EMPLOYEE_ID, forming a bidirectional relationship between employee and assignment interface rows.
• PSB_EMPLOYEES — the base table; references PSB_EMPLOYEES_I.HR_EMPLOYEE_ID, and is the destination for validated interface rows.
• PSB_POSITIONS_I — references PSB_EMPLOYEES_I.HR_EMPLOYEE_ID; position interface data tied to the employee.
• PSB_POSITIONS — references PSB_EMPLOYEES_I.HR_EMPLOYEE_ID; the base position table linked to the employee record.

Because PSB_EMPLOYEES_I sits between Oracle HRMS and PSB budgeting, extract and load processes that populate PSB_EMPLOYEES and PSB_POSITIONS depend directly on the integrity of this interface table.