Search Results position_set_name




Overview
Explore in AI Chat

Overview

APPS.PSBFV_PARAMETER_POS_SET_LISTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered under the FND Design Data identifier PSB.PSBFV_PARAMETER_POS_SET_LISTS and carries a status of VALID in the documented ETRM metadata. The view presents information about worksheet parameters associated with positions, joining parameter definitions to the position sets that consume them. It is therefore a reporting and integration surface rather than a transactional table, existing to expose denormalized, human-readable parameter-to-position-set relationships.

Within the Oracle EBS 12.1.1 and 12.2.2 architecture, objects prefixed PSBFV follow the conventions of the Business Intelligence System views used by Oracle Advanced Benefits and related Position/Assignment/Compensation components. The view is read-only and is not referenced by any other database object, which confirms its role as a terminal reporting artifact exposed to end users, BI Publisher reports, and external extracts. Because the view resolves names and effective dates rather than exposing only numeric keys, it is well suited to ad hoc queries and downstream integration where a business user must understand which worksheet parameter applies to a given position set.

Underlying Base Objects

The documented dependencies for this view include the following APPS base objects:

  • PSB_ACCOUNT_POSITION_SETS — supplies position set definitions and their identifiers, including POSITION_SET_ID and the associated name.
  • PSB_ENTITY — provides the entity-level metadata from which parameter names and parameter identifiers are derived.
  • PSB_ENTITY_ASSIGNMENT — defines the assignment of an entity (parameter) to a position set, forming the core many-to-many relationship.
  • PSB_SET_RELATIONS — describes relationships among sets, used to resolve hierarchy or membership context for the position set.

Internally, the view joins these objects so that a parameter record is presented alongside the position set to which it is applied. The join keys revolve around PARAMETER_ID and POSITION_SET_ID. Because the view is a BIS view, it does not store data; the underlying tables remain the system of record, and the view is refreshed implicitly at query time. The ETRM metadata lists no objects that reference this view, indicating it is not a prerequisite for any dependent object and is safe to query without side effects.

Key Columns

The view exposes the following columns, each with its documented datatype and meaning:

  • PARAMETER_NAME (VARCHAR2, 30) — the descriptive name of the worksheet parameter.
  • POSITION_SET_NAME (VARCHAR2, 100) — the descriptive name of the position set consuming the parameter.
  • START_EFFECTIVE_DATE (DATE) — the date on which the parameter-to-position-set association becomes effective.
  • END_EFFECTIVE_DATE (DATE) — the date on which the association ceases to be effective.
  • PARAMETER_ID (NUMBER, 15) — the unique identifier for the parameter; the search term "position_set_id" maps to the sibling key used to link to the position set.
  • POSITION_SET_ID (NUMBER, 15) — the unique identifier of the position set; this is the primary join key when correlating to PSB_ACCOUNT_POSITION_SETS.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard Who columns that capture audit information.

Effective dating is central to interpretation: a row represents a valid association only when the query date falls between START_EFFECTIVE_DATE and END_EFFECTIVE_DATE, inclusive of the intended boundary conventions.

Common Use Cases and Queries

Typical scenarios include auditing which parameters apply to a position set, building BI Publisher extracts, and reconciling effective-dated associations. Because users frequently search on position_set_id, filtering on that column is the most common entry point.

Listing all parameters for a specific position set:

  • SELECT PARAMETER_NAME, POSITION_SET_NAME, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE FROM APPS.PSBFV_PARAMETER_POS_SET_LISTS WHERE POSITION_SET_ID = :p_position_set_id;

Retrieving only currently effective associations:

  • SELECT PARAMETER_NAME, POSITION_SET_NAME FROM APPS.PSBFV_PARAMETER_POS_SET_LISTS WHERE SYSDATE BETWEEN START_EFFECTIVE_DATE AND NVL(END_EFFECTIVE_DATE, SYSDATE + 1);

Joining to position set definitions for additional context:

  • SELECT v.PARAMETER_NAME, v.POSITION_SET_NAME, s.POSITION_SET_ID FROM APPS.PSBFV_PARAMETER_POS_SET_LISTS v, APPS.PSB_ACCOUNT_POSITION_SETS s WHERE v.POSITION_SET_ID = s.POSITION_SET_ID;

These queries should be issued with the APPS schema or an appropriately granted synonym, and results are read-only in all supported releases.