Search Results psbbv_position_costs

Overview

PSBBV_POSITION_COSTS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the PSB (Public Sector Budgeting) product family, now part of the Oracle E-Business Suite Human Capital Management and budgeting footprint. The view presents position cost information on an element-by-element basis, decomposing the aggregate cost of a budgeted position into its constituent payroll or budget elements. Its primary role is to expose this data in a stable, security-friendly form suitable for reporting, concurrent program extraction, and integration interfaces that require position-level cost visibility without directly accessing the transactional base table. Because it is defined with a WITH READ ONLY clause, the view cannot be used for DML operations, ensuring that cost data integrity is preserved. The view carries status VALID in the data dictionary and is documented in the ETRM reference as providing details about Position Costs elementwise.

Underlying Base Objects

The view is defined over a single underlying base table, PSB_POSITION_COSTS, which resides in the same APPS application schema. The view text is a straightforward projection of nine columns with no joins, filters, aggregation, or function-based derivations, and is restricted by a WITH READ ONLY directive. The ETRM metadata records no additional referenced base objects beyond this source table, confirming that PSBBV_POSITION_COSTS exists as a thin logical layer over the position cost staging data. This simplicity is intentional: it provides a stable public interface decoupled from underlying table changes, while preserving row-level column names and data types identical to those of the source table. Administrators should note that granting privileges on this view rather than on the base table reduces the risk of unintended modifications to the cost records, since the read-only clause enforces that restriction at the object level.

Key Columns

• POSITION_ELEMENT_LINE_ID — Primary identifier for each element line within a position cost record. Uniquely distinguishes individual element lines.
• POSITION_ID — Foreign key identifying the budgeted position to which the cost element line belongs.
• PAY_ELEMENT_ID — Identifies the payroll or budget element (such as salary, fringe, or allowance) whose cost is captured on this line.
• BUDGET_REVISION_ID — Identifies the budget revision context in which the position cost was defined.
• BASE_LINE_VERSION — Indicates the version of the base line, supporting multiple iterations of a position cost record.
• CURRENCY_CODE — The currency in which the element cost is expressed.
• START_DATE and END_DATE — The effective date range during which the element cost applies.
• ELEMENT_COST — The monetary cost amount attributed to the element for the position over the stated date range.

Common Use Cases and Queries

Typical reporting scenarios include reconciling position budgets to element detail, feeding downstream costing or position control processes, and extracting costs for a specific budget revision or currency. A representative query retrieving all element costs for a given position is:

SELECT POSITION_ELEMENT_LINE_ID, POSITION_ID, PAY_ELEMENT_ID, ELEMENT_COST, CURRENCY_CODE FROM APPS.PSBBV_POSITION_COSTS WHERE POSITION_ID = :p_position_id;

A second common pattern totals element costs by budget revision:

SELECT BUDGET_REVISION_ID, CURRENCY_CODE, SUM(ELEMENT_COST) FROM APPS.PSBBV_POSITION_COSTS WHERE START_DATE BETWEEN :p_start AND :p_end GROUP BY BUDGET_REVISION_ID, CURRENCY_CODE;

Because the view is read-only and exposes no derived logic, its output aligns exactly with the underlying PSB_POSITION_COSTS records, making it well suited to audit-style reconciliations and interface extracts where consistency between reported and stored values is essential.