Results for “psb_position_fte”

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

Overview

PSB_POSITION_FTE is a Public Sector Budgeting (PSB) table that stores position control Full-Time Equivalent (FTE) information. In Oracle EBS 12.1.1 and 12.2.2, PSB supported budgetary position management for public sector and government organizations, allowing them to track authorized positions, their FTE allocations, and their linkage to budget revisions across budgeting cycles. The table records the FTE value associated with a given position over a defined date range and ties that value to a specific budget revision, enabling historical and versioned position control reporting.

The ETRM metadata notes that the PSB product is marked obsolete and that this table is "Not implemented in this database" in the referenced environment. Practitioners should therefore validate existence in their specific instance before relying on it. Using the heuristic Data Vault classification mined from the FK structure, PSB_POSITION_FTE is best modeled as a link table, since it resolves relationships between positions, budget revisions, and HR position/assignment entities rather than acting as a standalone hub of business keys or a descriptive satellite.

Key Information Stored

The table contains 15 documented columns. The most significant include:

• POSITION_FTE_LINE_ID — the surrogate primary key (PSB_POSITION_FTE_PK) that uniquely identifies each FTE line record. A unique index, PSB_POSITION_FTE_U1, is also defined on this column, making it the primary business-key candidate.
• POSITION_ID — foreign key to PSB_POSITIONS, identifying the position whose FTE is being controlled.
• BUDGET_REVISION_ID — foreign key to PSB_BUDGET_REVISIONS, tying the FTE value to a specific budget revision or version.
• HR_POSITION_ID — foreign key referencing PSB_EMPLOYEE_ASSIGNMENTS_I, linking the budgetary position to the underlying HR assignment.
• HR_BUDGET_ID — associates the line with an HR budget context.
• FTE — the numeric full-time equivalent value allocated to the position for the period.
• START_DATE / END_DATE — the effective date range during which the FTE value applies.
• BASE_LINE_VERSION — indicates the baseline version of the budget against which the FTE is measured.
• TRANSFER_TO_PC_FLAG — a flag indicating whether the FTE line is transferred to position control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS WHO columns for audit and concurrency tracking.

Common Use Cases and Queries

Typical scenarios include reporting authorized versus actual FTE by position, reconciling position control against budget revisions, and auditing FTE changes over time. A common query joins the FTE table to positions and budget revisions:

• SELECT p.position_id, f.fte, f.start_date, f.end_date FROM psb_position_fte f, psb_positions p WHERE f.position_id = p.position_id AND f.budget_revision_id = :rev_id;
• Trend analysis of FTE by budget revision using GROUP BY on BUDGET_REVISION_ID and SUM(FTE).
• Reconciliation to HR using HR_POSITION_ID against PSB_EMPLOYEE_ASSIGNMENTS_I.
• Filtering by date range (START_DATE/END_DATE) to retrieve the FTE in effect for a given period.

Related Objects

• PSB_POSITIONS — parent to POSITION_ID; defines the positions being controlled.
• PSB_BUDGET_REVISIONS — parent to BUDGET_REVISION_ID; defines the budget version.
• PSB_EMPLOYEE_ASSIGNMENTS_I — referenced via HR_POSITION_ID, connecting budgetary FTE to HR assignments.
• PSB_POSITION_FTE_PK — primary key constraint on POSITION_FTE_LINE_ID.
• PSB_POSITION_FTE_U1 — unique index supporting the business-key candidate.

Because PSB is obsolete, organizations migrating to later budgeting solutions should extract PSB_POSITION_FTE data early and map FTE allocations to their replacement position control structures.