Search Results psb_position_definitions_kfv




Overview

PSB_POSITION_DEFINITIONS_KFV is a database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the PSB (Public Sector Budgeting) product family and is documented in ETRM with the shorthand description "10sc only," indicating that its applicability is limited to specific Public Sector Budgeting configurations rather than the general EBS footprint. The object carries VALID status in the data dictionary, meaning its definition compiles successfully against the underlying base object at the documented release level.

The suffix _KFV follows Oracle's established naming convention for "Key Flexfield View." These views are generated so that a descriptive flexfield or key flexfield structure can be reported on and integrated with in a denormalized form. In this case the view exposes the position definition key flexfield, presenting each segment as an individually addressable column alongside a concatenated representation of the same segments. This makes the view a convenient reporting and interface surface: rather than requiring callers to join the flexfield segment tables and resolve segment values manually, the view delivers IDs, the flexfield structure identifier, the enabled flag, and every segment position in a single row.

Because the view is thin — it is a projection over a single base table with no joins — it is inexpensive to query and is well suited to concurrent program extracts, BI Publisher data templates, and inbound or outbound interface staging. It is not, however, a transactional table; all reads reflect the current state of the position definition and its flexfield segments.

Underlying Base Objects

The view is defined over a single base table, PSB_POSITION_DEFINITIONS, in the APPS schema. The ETRM metadata lists no additional referenced base objects, and the view text confirms a straightforward SELECT from that one table with no WHERE clause, no join, and no aggregation. The projection includes the table's ROWID, aliased in the column list as ROW_ID, together with all key flexfield segment columns and the position definition attributes.

The concatenated segments column is produced by an inline expression that appends SEGMENT1 through SEGMENT3 using the double-pipe concatenation operator; segments beyond the third are exposed only as individual columns. This is consistent with the "10sc only" scope note, which suggests the flexfield structure in the supported configuration is a short, three-segment key. Sites that have configured a different number of segments should not assume the concatenated column reflects segments four and above. The ID_FLEX_NUM column ties the row to the flexfield definition registered in the application's flexfield metadata, allowing the structure and its segment qualifiers to be resolved when required.

Key Columns

  • ROW_ID — the base table ROWID, useful as a stable row locator in update-through-view scenarios and in diagnostics.
  • POSITION_DEFINITION_ID — the primary identifier for the position definition; the natural join key to related PSB position and budgeting tables.
  • ID_FLEX_NUM — the key flexfield structure number, enabling resolution of segment names, sizes, and validation rules from the flexfield definition tables.
  • ENABLED_FLAG — indicates whether the position definition is active; disabled definitions should generally be excluded from current reporting.
  • CONCATENATED_SEGMENTS — the display-form key built from SEGMENT1 through SEGMENT3, suitable for list-of-values and printed output.
  • SEGMENT1 … SEGMENT30 — each key flexfield segment as a discrete column, supporting segment-level filtering and grouping even where the concatenated form does not include the segment.

Common Use Cases and Queries

Typical uses include position definition validation extracts, reconciliation between PSB and downstream budgeting or HR systems, and list-of-values queries filtered on enabled definitions. Because the view is a single-table projection, queries are simple and index-friendly.

Listing active position definitions with their display key:

  • SELECT position_definition_id, concatenated_segments FROM apps.psb_position_definitions_kfv WHERE enabled_flag = 'Y' ORDER BY concatenated_segments;

Retrieving a specific definition and its individual segments for interface output:

  • SELECT position_definition_id, id_flex_num, segment1, segment2, segment3 FROM apps.psb_position_definitions_kfv WHERE position_definition_id = :p_id;

Grouping counts by the first segment to summarize position definitions across a reporting hierarchy:

  • SELECT segment1, COUNT(*) FROM apps.psb_position_definitions_kfv WHERE enabled_flag = 'Y' GROUP BY segment1;

Callers should always qualify the view with the APPS schema, filter on ENABLED_FLAG where currency of data matters, and avoid assuming that CONCATENATED_SEGMENTS includes more than the three documented segments.