Results for “data_extract_name”

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

Overview

PSBFV_POSITION_SET_LISTS is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the Public Sector Budgeting (PSB) product family. The ETRM metadata identifies the object as a VIEW with VALID status and annotates its description simply as "10sc only," indicating that the view was originally introduced or scoped for a specific ten-character/ten-column configuration, historically associated with the Public Sector Budgeting release lineage. In EBS 12.1.1 and 12.2.2 the view remains present as a legacy compatibility object rather than a primary data-entry construct.

The view presents a denormalized, human-readable listing of position set lists — that is, the association between budget positions, their parent position definitions, data extracts, and account position sets. Its role is primarily reporting and integration: it allows forms, concurrent programs, or external extracts to resolve internal numeric identifiers into meaningful names without requiring the caller to perform the multi-table joins manually. Because the view is defined WITH READ ONLY, it cannot be used for DML and is intended strictly for query access.

Underlying Base Objects

The view text joins four PSB base tables:

• PSB_BUDGET_POSITIONS (alias PO) — the driving table, holding the linkage between an account position set and a position, including the data extract identifier.
• PSB_POSITIONS (alias PS) — the position definition, keyed by POSITION_ID and carrying the DATA_EXTRACT_ID.
• PSB_DATA_EXTRACTS (alias DT) — the data extract master, supplying DATA_EXTRACT_NAME.
• PSB_ACCOUNT_POSITION_SETS (alias ST) — the account position set master, supplying the position set NAME and ACCOUNT_POSITION_SET_ID.

The join predicates are: PO.POSITION_ID = PS.POSITION_ID, DT.DATA_EXTRACT_ID = PS.DATA_EXTRACT_ID, and ST.ACCOUNT_POSITION_SET_ID = PO.ACCOUNT_POSITION_SET_ID. The ETRM 12.2.2 metadata records no separately documented base objects, so the authoritative relationship set is derived directly from the embedded view text. Each row therefore represents one position's membership within a specific account position set for a given data extract.

Key Columns

• POSITION_SET_NAME — the descriptive name of the account position set (from ST.NAME).
• DATA_EXTRACT_NAME — the name of the associated data extract (from DT.DATA_EXTRACT_NAME).
• POSITION_NAME — the descriptive name of the position (from PS.NAME).
• POSITION_SET_ID — the account position set identifier (PO.ACCOUNT_POSITION_SET_ID).
• DATA_EXTRACT_ID — the data extract identifier (PO.DATA_EXTRACT_ID).
• POSITION_ID — the position identifier (PO.POSITION_ID).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS audit columns inherited from PSB_BUDGET_POSITIONS.

Common Use Cases and Queries

Typical applications include validating position set membership, populating reports or interfaces that require descriptive names rather than surrogate keys, and troubleshooting budget position setup during implementation or support. A representative query retrieving all positions for a given set is:

• SELECT position_set_name, data_extract_name, position_name FROM apps.psbfv_position_set_lists WHERE position_set_id = :set_id ORDER BY position_name;

To list all sets and their extract context:

• SELECT DISTINCT position_set_name, data_extract_name FROM apps.psbfv_position_set_lists ORDER BY 1, 2;

Because the view is read-only and joins four tables, queries should filter on indexed identifiers such as POSITION_SET_ID or DATA_EXTRACT_ID to avoid full scans on large PSB datasets. Any modification to the underlying position set membership must be performed through the PSB forms or via the base tables directly, not through this view.