Search Results system_attribute_type

Overview

APPS.PSB_ATTRIBUTES_VL is a multilingual (language-resolved) view in the Oracle E-Business Suite Applications schema. It exposes descriptive information about attribute definitions used by the Public Sector Budgeting (PSB) product family, and it is the language-resolved layer over the intersection of the PSB_ATTRIBUTES and PSB_ATTRIBUTES_TL tables. The view is registered in FND Design Data under the form/view identifier PSB.PSB_ATTRIBUTES_VL and carries a VALID status in both 12.1.1 and 12.2.2, indicating it is a supported and queryable object rather than an obsolete internal artifact.

The view is a component of the PSB attribute framework that governs how budget position attributes behave: whether they are permitted in a position set, whether they draw values from a value table, how they are displayed in worksheets, and which underlying definition structure, table, and column they are bound to. Because it resolves translated display prompts and names through a multilingual view construct, it is the appropriate source for any report or integration that must present attribute definitions to end users in their session language.

Underlying Base Objects

The documented dependencies for APPS.PSB_ATTRIBUTES_VL are:

• PSB_ATTRIBUTES — the base attribute definition table (primary data source).
• PSB_ATTRIBUTES_TL — the translation table supplying language-specific NAME and DISPLAY_PROMPT values.
• PER_BUSINESS_GROUPS — joined to resolve BUSINESS_GROUP_NAME from the numeric business group identifier.

The view is therefore defined over three objects and is not an independent entity. The "_VL" suffix denotes a language-resolved view: Oracle joins the base table to its translation table on the standard language columns and returns one row per attribute for the current session language. Consumers should be aware that the row count and text columns depend on the language context in which the query executes; results for a non-base language may differ from the base-language rows.

APPS.PSB_ATTRIBUTES_VL is referenced by other application objects, including PSB_ACCOUNT_POSITION_SET_PVT, which indicates the view participates in the Public Sector Budgeting account/position set processing path rather than serving purely as a reporting convenience. Documented inverse dependencies should be reviewed before altering or wrapping this view.

Key Columns

The view exposes twenty-five columns spanning identifiers, flags, definition metadata, and display attributes. The columns most relevant to the "definition_column" interest are:

• DEFINITION_COLUMN (VARCHAR2, 30) — names the physical column on the underlying definition table to which the attribute maps. This is the binding between an abstract attribute definition and its storage location.
• DEFINITION_TABLE (VARCHAR2, 30) — the table or structure that holds the attribute's value.
• DEFINITION_STRUCTURE (VARCHAR2, 30) — the broader definition container or structure type.
• DEFINITION_TYPE (VARCHAR2, 10) — classifies the nature of the attribute definition.
• ATTRIBUTE_ID and ATTRIBUTE_TYPE_ID — the primary key of the definition and its type reference.
• DATA_TYPE and SYSTEM_ATTRIBUTE_TYPE — the value's datatype and, for seeded attributes, the system-assigned type that identifies Oracle-maintained vs. user-defined behavior.
• BUSINESS_GROUP_ID / BUSINESS_GROUP_NAME — the business group ownership context, resolved via PER_BUSINESS_GROUPS.
• Flags controlling behavior: ALLOW_IN_POSITION_SET_FLAG, VALUE_TABLE_FLAG, REQUIRED_FOR_POSITIONS_FLAG, REQUIRED_FOR_IMPORT_FLAG, PROTECTED_FLAG, and DISPLAY_IN_WORKSHEET.
• Presentation columns: NAME, DISPLAY_PROMPT, and DISPLAY_SEQUENCE.
• Standard audit columns: ROW_ID, APPLICATION_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical scenarios include auditing which physical column backs a given PSB attribute, verifying business-group scoping, and generating reference listings of attribute prompts for a reporting front end. Because DEFINITION_COLUMN and DEFINITION_TABLE are exposed together, the view is a convenient starting point for metadata-driven integrations that need to build dynamic SQL against PSB definition structures.

To locate the definition column for a specific attribute:

• SELECT attribute_id, name, display_prompt, definition_structure, definition_table, definition_column FROM apps.psb_attributes_vl WHERE business_group_id = :p_bg_id AND name = :p_name ORDER BY display_sequence;

To audit all user-defined (non-system) attributes and their storage bindings:

• SELECT attribute_id, name, definition_table, definition_column, data_type FROM apps.psb_attributes_vl WHERE system_attribute_type IS NULL ORDER BY application_id, display_sequence;

To review attributes that participate in position sets and worksheets:

• SELECT name, display_prompt, allow_in_position_set_flag, required_for_positions_flag, display_in_worksheet FROM apps.psb_attributes_vl WHERE allow_in_position_set_flag = 'Y' ORDER BY display_sequence;

Queries against this view should account for multilingual resolution: the NAME and DISPLAY_PROMPT values returned reflect the language environment of the session, and joins to other PSB objects should use ATTRIBUTE_ID rather than the translated text columns.