Search Results attribute_values

Overview

APPS.PSB_POSITION_SET_LINE_VALUES_V is a supplementary database view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment. It resides in the APPS schema and carries the FND Design Data reference PSB.PSB_POSITION_SET_LINE_VALUES_V, placing it within the Public Sector Budgeting (PSB) product family. Position sets are a core construct in PSB, used to organize and group position lines that drive budget formulation and salary costing. This view flattens and denormalizes the attribute value data attached to those position set lines, exposing both the stored attribute value and the attribute definition in a single, form-friendly structure.

Per the ETRM documentation, the view is explicitly described as "a supplementary view used to simplify forms coding." Oracle warns that the view is not intended for direct query or data manipulation and that its definition "may change dramatically in subsequent minor or major releases." Consequently, the view should be treated as an internal Forms-support artifact rather than a stable public interface. Reporting and integration developers should recognize it as a convenience layer and validate any dependency against the underlying base tables before relying on it in custom code or extracts.

Underlying Base Objects

The view is defined over four documented base objects in the APPS schema:

• PSB_POSITION_SET_LINE_VALUES — the principal table storing the attribute values assigned to each position set line.
• PSB_ATTRIBUTE_VALUES — the value definitions or master value records referenced by the line values.
• PSB_ATTRIBUTES — the attribute metadata, supplying attribute names and flags.
• PSB_ACCOUNT_POSITION_SET_LINES — the account-specific position set line records that provide the contextual header and line linkage.

The view joins these objects to resolve an attribute value against its attribute definition and its parent position set line. It is in turn referenced by the PL/SQL package APPS.PSB_ACCOUNT_POSITION_SET_PVT, which confirms its role as a supporting component of the position set maintenance forms and their associated business logic. Note that the documented metadata does not enumerate a full column-to-table mapping; the dependency list above is the authoritative statement of the view's lineage.

Key Columns

The view exposes fourteen columns. The most significant are:

• VALUE_SEQUENCE_ID, LINE_SEQUENCE_ID — numeric keys linking each value row to its parent value set and position set line.
• ATTRIBUTE_VALUE_ID — identifier for the specific attribute value record.
• ATTRIBUTE_VALUE (VARCHAR2, 240) — the stored value of the attribute for the line.
• ATTRIBUTE_ID and ATTRIBUTE_NAME (VARCHAR2, 30) — the identifier and human-readable name of the attribute.
• ATTRIBUTE_VALUE_TABLE_FLAG — a flag indicating the source mode of the value.
• ATTRIBUTE_TABLE_VALUE (VARCHAR2, 240) — the table-derived or looked-up value, which is the column most closely associated with the attribute_table_value term used in the originating search.
• ROW_ID (ROWID) — the underlying row identifier.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Together, ATTRIBUTE_VALUE and ATTRIBUTE_TABLE_VALUE allow the forms layer to present either a directly entered value or one resolved from a validated value table, governed by ATTRIBUTE_VALUE_TABLE_FLAG.

Common Use Cases and Queries

Because Oracle discourages direct queries against supplementary views, the safest pattern is to query the view read-only for diagnostics and reporting, then confirm results against the base tables. Typical scenarios include auditing which attributes are populated on position set lines, reconciling direct values against table-validated values, and troubleshooting forms behavior in the Account Position Set maintenance flow.

A representative query retrieves all values for a given line:

• SELECT line_sequence_id, attribute_name, attribute_value, attribute_table_value, attribute_value_table_flag, last_update_date FROM apps.psb_position_set_line_values_v WHERE line_sequence_id = :p_line_seq ORDER BY attribute_name;

To isolate records whose value is sourced from a value table:

• SELECT attribute_id, attribute_name, attribute_table_value FROM apps.psb_position_set_line_values_v WHERE attribute_value_table_flag IS NOT NULL;

For audit purposes, filtering on the standard date columns (for example, WHERE last_update_date >= :cutoff) yields recently modified attribute values. In all cases, developers should prefer joining PSB_POSITION_SET_LINE_VALUES, PSB_ATTRIBUTE_VALUES, and PSB_ATTRIBUTES directly when long-term stability is required, reserving the view for exploratory or form-aligned use.