Search Results base_line_revision




Overview
Explore in AI Chat

Overview

PSBFV_POSITION_COSTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PSB (Public Sector Budgeting) product family. It presents the costed position lines generated during budgetary position costing, joining position cost records to their parent position definition, pay element, and budget revision context. The view serves as the reporting and integration layer between the PSB costing engine and downstream consumers such as budget worksheets, position control reports, and custom extracts. It is defined WITH READ ONLY, so it cannot be used for DML; it exists purely for query and reporting purposes.

The user search term "budget_revision_justification" corresponds to the view column BUDGET_REVISION_JUSTIFICATION, which is populated from PSB_BUDGET_REVISIONS.JUSTIFICATION. This is the narrative text entered by budget analysts when a revision is created, explaining why the revision was made. The view exposes this justification alongside the costed lines that belong to the revision, which is why it surfaces so often in revision audit and reconciliation queries.

Underlying Base Objects

Per the documented view text, PSBFV_POSITION_COSTS is defined over five base objects:

The literal '_KF:PSB:BPS:PKFV:_CO' in the SELECT list is a flexfield token instructing the Key Flexfield View mechanism to resolve the position name from PKFV.

Key Columns

  • POSITION_ELEMENT_LINE_ID — primary key of the costed line in PSB_POSITION_COSTS.
  • POSITION_ID — foreign key to the position header.
  • _KF:POSITION_NAME — the descriptive position name derived from the position key flexfield.
  • PAY_ELEMENT_ID / PAY_ELEMENT_NAME — the pay element being costed (for example, base salary, fringe, or allowance) and its display name.
  • BUDGET_REVISION_ID / BUDGET_REVISION_JUSTIFICATION — the revision identifier and its free-text justification, the latter being the column most frequently queried.
  • BASE_LINE_REVISION — the version of the base line against which the cost was calculated.
  • CURRENCY_CODE, START_DATE, END_DATE — currency context and the effective period of the costed amount.
  • ELEMENT_COST — the computed monetary amount for the position element line.

Common Use Cases and Queries

Typical scenarios include auditing position costs against their revisions, extracting justifications for budget review packs, and feeding reconciliations between PSB and GL or HR. A representative query filtering on revision justification:

  • SELECT position_id, "_KF:POSITION_NAME", pay_element_name, budget_revision_id, budget_revision_justification, element_cost FROM apps.psbfv_position_costs WHERE budget_revision_justification IS NOT NULL ORDER BY budget_revision_id, position_id;
  • SELECT budget_revision_id, budget_revision_justification, SUM(element_cost) FROM apps.psbfv_position_costs GROUP BY budget_revision_id, budget_revision_justification;
  • SELECT p.position_id, p."_KF:POSITION_NAME", p.pay_element_name, p.element_cost, p.start_date, p.end_date FROM apps.psbfv_position_costs p WHERE p.start_date >= :from_date AND p.end_date <= :to_date;

Because the view is read-only and inherits the PSB security model, queries run with the privileges of the executing user. Confirm the flexfield name column quoting in SQL*Plus, as the "_KF:" prefix requires double quotation marks.