Search Results pv_attributes_vl




Overview
Explore in AI Chat

Overview

PV_ATTRIBUTES_VL is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the PV product family, Partner Management, and functions as a linguistic (MLS) view that presents attribute definitions used within partner and channel management functionality. The "_VL" suffix identifies it as a view that joins a base table to its translation table, returning descriptive columns in the session language and non-translated columns from the base entity. The view merges the operational columns of PV_ATTRIBUTES_B with the translatable NAME, DESCRIPTION, and SHORT_NAME columns of PV_ATTRIBUTES_TL, filtered by the current runtime language.

In reporting and integration contexts, PV_ATTRIBUTES_VL is the preferred access point for querying attribute metadata because it automatically resolves language-dependent descriptive text without requiring the report or interface to join the translation table explicitly. It is typically used by concurrent programs, OAF-based partner pages, and custom extracts that need to enumerate attribute definitions, their data types, validation rules, and display characteristics.

Underlying Base Objects

The documented view text defines PV_ATTRIBUTES_VL over two synonyms: PV_ATTRIBUTES_B and PV_ATTRIBUTES_TL. PV_ATTRIBUTES_B is the base table holding non-translatable attribute metadata, including keys, audit columns, object version, flags, and type information. PV_ATTRIBUTES_TL is the translation table storing language-specific NAME, DESCRIPTION, and SHORT_NAME values.

The two objects are equated on ATTRIBUTE_ID. Because PV_ATTRIBUTES_TL is a translation table, it carries additional language columns not exposed by the view; the view restricts rows with LANGUAGE = USERENV('LANG') so that only the current session language is returned. This join pattern is standard for MLS views and explains why the view is read-only for practical purposes and does not surface ROWID-based DML against multiple tables.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating attribute setup, building LOV-driven partner configuration extracts, and reporting on exposed partner attributes. A simple listing query follows:

SELECT attribute_id, name, short_name, attribute_type, enabled_flag
FROM apps.pv_attributes_vl
WHERE enabled_flag = 'Y'
ORDER BY sequence_number;

Filtering exposed attributes for a partner integration would add AND expose_to_partner_flag = 'Y'. Because the view applies USERENV('LANG'), results reflect the connected user's language; multilingual extracts must connect with the appropriate NLS_LANG or query PV_ATTRIBUTES_TL directly to obtain all translations.