Search Results psb_position_costs_u1

Overview

The PSB.PSB_POSITION_COSTS table is an interface and staging object within the Oracle E-Business Suite Position Control module. It stores position costs segmented by pay element, capturing the baseline values derived from budget revisions before those costs are posted to a downstream Position Control system. In this capacity the table functions as a bridge between budget preparation data and operational Position Control processing, holding cost records at the granularity of an individual position, pay element, and effective date range.

Under a heuristic Data Vault classification, PSB_POSITION_COSTS models most naturally as a link entity. It resolves the many-to-many relationship between positions and pay elements while carrying descriptive cost measures and dates, and it references several surrounding hubs such as PSB_POSITIONS, PSB_PAY_ELEMENTS, and PSB_BUDGET_REVISIONS. This classification is a modeling suggestion rather than a formally declared designation.

Key Information Stored

The table is keyed by a surrogate primary key, with a unique index serving as the principal business-key candidate.

• POSITION_ELEMENT_LINE_ID — Surrogate primary key (also indexed uniquely as PSB_POSITION_COSTS_U1) uniquely identifying each position element cost line.
• POSITION_ID — Foreign key to PSB_POSITIONS; the position to which the cost applies (indexed by PSB_POSITION_COSTS_N1).
• PAY_ELEMENT_ID — Foreign key to PSB_PAY_ELEMENTS; the pay element being costed.
• BUDGET_REVISION_ID — Foreign key to PSB_BUDGET_REVISIONS; the budget revision supplying the baseline (indexed by PSB_POSITION_COSTS_N2).
• START_DATE / END_DATE — Effective date range for which the element cost is maintained.
• CURRENCY_CODE — Currency in which the element cost is expressed.
• ELEMENT_COST — The monetary cost of the Position Control element.
• BASE_LINE_VERSION — Indicates whether values are Original (from Budget Preparation) or Current (from Position Control).
• TRANSFER_TO_PC_FLAG — The control flag governing whether the record is transferred to the Position Control system; central to the interface posting process.
• HR_POSITION_ID, HR_BUDGET_SET_ID, HR_BUDGET_ID — Cross-references to the source HRMS position and budget identifiers.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) — Audit trail fields.

Common Use Cases and Queries

Because TRANSFER_TO_PC_FLAG controls the movement of staged costs into Position Control, a primary use case is identifying pending interface records:

• Selecting cost lines awaiting transfer, filtering by the transfer flag and budget revision.
• Reporting position costs by pay element for a given effective date range.
• Reconciling budget preparation baselines against current Position Control values via BASE_LINE_VERSION.

A representative query joins the interface table to its parent position, element, and revision tables, using the documented foreign-key columns:

• SELECT pc.POSITION_ELEMENT_LINE_ID, pc.ELEMENT_COST, pc.CURRENCY_CODE
• FROM PSB.PSB_POSITION_COSTS pc
• JOIN PSB.PSB_POSITIONS p ON p.POSITION_ID = pc.POSITION_ID
• JOIN PSB.PSB_PAY_ELEMENTS e ON e.PAY_ELEMENT_ID = pc.PAY_ELEMENT_ID
• WHERE pc.TRANSFER_TO_PC_FLAG = 'Y'

Related Objects

The table participates in a defined foreign-key network with the following significant objects, joined on the columns noted:

• PSB.PSB_POSITIONS — joined via POSITION_ID; the defining position record.
• PSB.PSB_PAY_ELEMENTS — joined via PAY_ELEMENT_ID; defines the costed element.
• PSB.PSB_BUDGET_REVISIONS — joined via BUDGET_REVISION_ID; supplies baseline revision context.
• PSB.PSB_EMPLOYEE_ASSIGNMENTS_I — referenced through HR_POSITION_ID, linking to source HRMS position/assignment data.

Together these relationships position PSB_POSITION_COSTS as the cost-bearing link at the intersection of positions, pay elements, and budget revisions within the Position Control interface flow.