Results for “psb_budget_positions”

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

Overview

PSB_BUDGET_POSITIONS is a table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. The module is documented as obsolete in the ETRM metadata for releases 12.1.1 and 12.2.2, and the table itself is marked "Not implemented in this database" in the implementation/DBA data. Its documented role is to hold an expanded list of positions that belong to a position set, acting as the bridge between a defined account position set and the individual positions that constitute it.

From a modeling perspective, the metadata's heuristic Data Vault classification identifies this object as a link. This is a suggestion only: the table resolves a many-to-many relationship between position sets and positions, and the presence of a composite primary key over two foreign key columns, together with a surrogate DATA_EXTRACT_ID foreign key, is consistent with a link construct that associates multiple hubs.

Key Information Stored

The documented physical schema for PSB_BUDGET_POSITIONS contains nine columns owned by the PSB schema. The most significant of these are described below.

• ACCOUNT_POSITION_SET_ID — Identifies the account position set to which the expanded entry belongs. This column forms part of the composite primary key and carries a foreign key to PSB_ACCOUNT_POSITION_SETS.
• POSITION_ID — Identifies the individual position included in the set. It also participates in the composite primary key and carries a foreign key to PSB_POSITIONS.
• DATA_EXTRACT_ID — Foreign key to PSB_DATA_EXTRACTS, linking each expanded row back to the data extract process that populated it.
• BUSINESS_GROUP_ID — The operating unit or business group context under which the row was created, supporting multi-organization data segregation.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — The application user who last modified the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for audit tracking.
• CREATED_BY — The application user who created the row.
• CREATION_DATE — Timestamp of row creation.

The primary key is defined as PSB_BUDGET_POSITIONS_PK over (ACCOUNT_POSITION_SET_ID, POSITION_ID). A separate unique index, PSB_BUDGET_POSITIONS_U1, is documented over (POSITION_ID, ACCOUNT_POSITION_SET_ID) and can be considered a business-key candidate, since it enforces the same logical uniqueness from the reverse column order. The three foreign keys — ACCOUNT_POSITION_SET_ID, DATA_EXTRACT_ID, and POSITION_ID — define the table's referential dependencies.

Common Use Cases and Queries

In environments where the PSB module was in use, this table supported budget position expansion, reporting on which positions were included in a given position set, and audit reconciliation of extract-driven position data. Typical access patterns include joining to PSB_POSITIONS for descriptive attributes and to PSB_ACCOUNT_POSITION_SETS for set-level context.

• Identify all positions in a given set: SELECT position_id FROM psb_budget_positions WHERE account_position_set_id = :set_id;
• Find all sets that contain a specific position: SELECT account_position_set_id FROM psb_budget_positions WHERE position_id = :position_id;
• Trace rows back to their extract: join to PSB_DATA_EXTRACTS on data_extract_id.
• Audit changes by filtering on last_update_date, last_updated_by, or creation_date.

Because the module is obsolete and the table is documented as not implemented, these queries are primarily relevant to legacy migrations, historical reconciliation, or archival analysis.

Related Objects

The following objects are directly related through the documented foreign keys and key structure.

• PSB_ACCOUNT_POSITION_SETS — referenced via PSB_BUDGET_POSITIONS.ACCOUNT_POSITION_SET_ID; the parent set definition.
• PSB_POSITIONS — referenced via PSB_BUDGET_POSITIONS.POSITION_ID; the position master.
• PSB_DATA_EXTRACTS — referenced via PSB_BUDGET_POSITIONS.DATA_EXTRACT_ID; the extract that generated the expansion.

These three parent tables form the complete documented dependency set. Any dependent views, concurrent programs, or APIs that consumed PSB_BUDGET_POSITIONS would logically traverse these same foreign keys, but no additional child objects are documented in the provided metadata.