Results for “psbfv_position_sets”

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

Overview

PSBFV_POSITION_SETS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the PSB (Public Sector Budgeting) product family. It exposes account position set definitions that are specifically typed as position sets, distinguished from account sets by the filter condition ACCOUNT_OR_POSITION_TYPE = 'P' applied against the PSB_ACCOUNT_POSITION_SETS base table. Because the view is created WITH READ ONLY, it is intended strictly for query, reporting, and integration purposes rather than for direct data manipulation; insertions, updates, and deletions must be performed against the underlying PSB tables.

The view joins each position set to its originating data extract, resolving the internal DATA_EXTRACT_ID foreign key into the human-readable DATA_EXTRACT_NAME. This is significant for the many users who search on the term "data_extract_name" when tracing where a position set originated, since the view presents the extract name alongside the set name without requiring the caller to perform an explicit join against PSB_DATA_EXTRACTS.

Underlying Base Objects

PSBFV_POSITION_SETS is defined over two documented base tables in the PSB schema:

• PSB_ACCOUNT_POSITION_SETS (aliased SETS) — the driving table, holding the position set definition, its type, sharing indicator, attribute selection type, and audit columns.
• PSB_DATA_EXTRACTS (aliased DTE) — the parent source of the data extract name.

The relationship is an outer join: DTE.DATA_EXTRACT_ID(+) = SETS.DATA_EXTRACT_ID. This ensures that position sets with no associated data extract are still returned, with DATA_EXTRACT_NAME appearing as NULL. The view is further restricted by the predicate on ACCOUNT_OR_POSITION_TYPE equal to 'P', so only position-type records are surfaced; account-type rows stored in the same base table are excluded.

Key Columns

• DATA_EXTRACT_NAME — the name of the associated data extract from PSB_DATA_EXTRACTS; NULL when no extract is linked.
• POSITION_SET_NAME — the user-facing name of the position set, sourced from SETS.NAME.
• POSITION_SET_SHAREABLE_FLAG — derived via DECODE(SETS.GLOBAL_OR_LOCAL_TYPE,'G','Y','N'); returns 'Y' for globally shared sets and 'N' for local ones.
• ATTRIBUTE_SELECTION_TYPE — indicates how attributes are selected for the set.
• POSITION_SET_ID — the primary identifier from SETS.ACCOUNT_POSITION_SET_ID.
• DATA_EXTRACT_ID — the foreign key linking to the data extract.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard Oracle audit columns inherited from PSB_ACCOUNT_POSITION_SETS.

Common Use Cases and Queries

Typical scenarios include auditing which data extracts populate each position set, identifying globally shared versus local sets, and feeding position set metadata into downstream reporting or integration extracts.

List all position sets with their extract names:

• SELECT position_set_id, position_set_name, data_extract_name, position_set_shareable_flag FROM apps.psbfv_position_sets ORDER BY position_set_name;

Find sets that are not linked to any data extract:

• SELECT position_set_name FROM apps.psbfv_position_sets WHERE data_extract_name IS NULL;

Isolate globally shared position sets:

• SELECT position_set_name, attribute_selection_type FROM apps.psbfv_position_sets WHERE position_set_shareable_flag = 'Y';

Because the view is read-only and joins only PSB tables, queries are lightweight and require no additional filtering to exclude account-type records; the position-type restriction is applied internally by the view definition.