Search Results pv_attribute_codes_vl




Overview
Explore in AI Chat

Overview

PV_ATTRIBUTE_CODES_VL is a seeded, read-only Oracle EBS view owned by the APPS schema within the Partner Management (PV) product family. Its suffix, "_VL", follows standard Oracle Applications naming conventions for views that join a _B (base) table to its corresponding _TL (translation) table and restrict the translation rows to the session's current language. In this case, the view exposes attribute codes along with their language-dependent descriptions from a single, denormalized result set. Because it layers language resolution on top of the base table, PV_ATTRIBUTE_CODES_VL is the appropriate entry point for any query, concurrent program, form, or integration that needs attribute code information presented in the user's language rather than in every installed language simultaneously.

Underlying Base Objects

The view references two documented base objects, both exposed through synonyms in the APPS schema: PV_ATTRIBUTE_CODES_B and PV_ATTRIBUTE_CODES_TL. The _B table holds language-independent columns, including the primary key, code values, flags, and date-effective ranges. The _TL table holds the translated DESCRIPTION column keyed by ATTR_CODE_ID and LANGUAGE. The view text performs an inner join between the two:

  • B.ATTR_CODE_ID = T.ATTR_CODE_ID equates the base and translation records.
  • T.LANGUAGE = USERENV('LANG') filters translations to the current session language.

The view's ROW_ID derives from the base table's ROWID (B.ROWID), and the join is not restricted by an OUTER JOIN operator, so a base record without a matching translation row for the active language is not returned.

Key Columns

Common Use Cases and Queries

Typical uses include validation lists (LOVs) on Partner Management forms, concurrent program parameter validation, and inbound/outbound integration extracts requiring localized descriptions. A representative query filtering to currently enabled codes and their active children is:

SELECT attr_code_id, attr_code, description, attribute_id, enabled_flag FROM apps.pv_attribute_codes_vl WHERE enabled_flag = 'Y' AND attribute_id = :p_attribute_id ORDER BY attr_code;

To list codes effective as of today:

SELECT attr_code, description FROM apps.pv_attribute_codes_vl WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

For reporting that must display the AUTO_ASSIGN_FLAG or audit information, the same view supports direct projection of those columns. Because the view is defined with an inner join to the translation table, custom queries should confirm that a translation exists for the runtime language; otherwise the base row will be omitted from results.