Search Results account_or_position_type




Overview
Explore in AI Chat

Overview

APPS.PSBBV_POSITION_SETS is a read-only Oracle EBS view belonging to the Public Sector / Advanced Procurement (PSB) schema family. It exposes a filtered, denormalized projection of account and position set definitions managed by the ETRM (Enterprise Tax, Reporting and Management, historically the Public Sector Budgeting / Position Control module) subsystem. Specifically, the view restricts its result set to rows where ACCOUNT_OR_POSITION_TYPE = 'P', meaning it presents only position sets and excludes account set records sharing the same parent table.

The view's role in EBS reporting and integration is to provide downstream reports, concurrent programs, and interface extracts with a clean list of position sets joined (outer) to their associated data extract definitions. Because the view is declared WITH READ ONLY, it cannot be used for DML; it serves purely as a query surface.

Underlying Base Objects

The view is defined over two base tables:

  • PSB_ACCOUNT_POSITION_SETS (aliased SETS) — the driving table, holding both account sets and position sets, discriminated by the ACCOUNT_OR_POSITION_TYPE column. The view filters this table to 'P' to isolate position sets.
  • PSB_DATA_EXTRACTS (aliased DTE) — joined via an outer join (DTE.DATA_EXTRACT_ID(+) = SETS.DATA_EXTRACT_ID) so that position sets without an assigned data extract still appear in the output, with NULL extract attributes.

The ETRM metadata lists "none documented" for referenced base objects, but the embedded view text unambiguously identifies these two PSB tables as the source objects.

Key Columns

The view exposes the following projected columns, several of which are renamed relative to their base columns:

  • NAME — from SETS.NAME; the user-defined position set name.
  • DATA_EXTRACT_NAME — from DTE.DATA_EXTRACT_NAME; the name of the linked data extract, or NULL when no extract is assigned.
  • GLOBAL_OR_LOCAL (decoded) — DECODE(SETS.GLOBAL_OR_LOCAL_TYPE,'G','Y','N'); yields 'Y' for global position sets and 'N' for local ones. Note the alias is not explicitly supplied in the view text, so the column inherits an expression-derived name.
  • ACCOUNT_POSITION_SET_ID — primary identifier of the position set.
  • DATA_EXTRACT_ID — foreign key to PSB_DATA_EXTRACTS; NULL if unassigned.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS audit columns (WHO columns) for the set record.

The inclusion of the ACCOUNT_OR_POSITION_TYPE predicate directly addresses the user's search term: this column is the discriminator that the view internally consumes (fixed at 'P') but does not itself expose in the SELECT list.

Common Use Cases and Queries

Typical scenarios include auditing which position sets are wired to data extracts, validating global vs. local scope, and feeding external interfaces. Sample query:

  • SELECT name, data_extract_name FROM apps.psbbv_position_sets WHERE data_extract_id IS NULL; — identify position sets lacking an extract.
  • SELECT name, account_position_set_id FROM apps.psbbv_position_sets ORDER BY name; — enumerate all position sets.

Because the view already isolates type 'P' and enforces read-only semantics, it is the preferred, safe access path for reporting on position sets without re-implementing the base-table filter logic.