Search Results pv_attribute_codes_tl_pk

Overview

PV_ATTRIBUTE_CODES_TL is the translation (language) table for Partner Attribute Codes within the Oracle E-Business Suite Partner Management (PV) module. It stores the translatable name and description text associated with each attribute code defined for trading partners. In Oracle EBS Release 12.1.1 and 12.2.2, this table follows the standard multilingual "TL" pattern, in which language-independent attributes reside in a companion base table (PV_ATTRIBUTE_CODES_B) and the language-dependent descriptive text resides in the _TL table, keyed by both the entity identifier and the LANGUAGE code.

The object carries a Data Vault classification, mined heuristically from its foreign key structure, of satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a descriptive satellite attached to the attribute code hub represented by the base table, holding context and text that may change over time and by language.

Key Information Stored

The table holds 12 documented columns. The most significant are:

• ATTR_CODE_ID — The surrogate identifier for the attribute code. It is part of the composite primary key and the foreign key to the base table.
• LANGUAGE — The NLS language code for the translated text; the second component of the primary key.
• SOURCE_LANG — Indicates the source language of the translated row, used in the standard EBS multilingual translation framework.
• DESCRIPTION — The translated name and/or description text for the attribute code, which is the principal payload of this table.
• ZD_EDITION_NAME — The edition identifier used by the EBS Edition-Based Redefinition (EBR) infrastructure in Release 12.2, supporting online patching.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-tenant or data-segregated deployments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns capturing audit and concurrency information.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.

The surrogate primary key is PV_ATTRIBUTE_CODES_TL_PK, defined over (ATTR_CODE_ID, LANGUAGE). A unique index, PV_ATTRIBUTE_CODES_TL_U1, is defined over (ATTR_CODE_ID, LANGUAGE, ZD_EDITION_NAME), which acts as the business-key candidate incorporating the edition dimension.

Common Use Cases and Queries

This table is typically queried to return the translated display name of a partner attribute code for a given session language, often joined to its base table. A representative query pattern joins the translation table to the base table on ATTR_CODE_ID and filters by the session language:

• Retrieve attribute code descriptions for reports or LOVs: SELECT b.attr_code_id, t.description FROM pv_attribute_codes_b b, pv_attribute_codes_tl t WHERE b.attr_code_id = t.attr_code_id AND t.language = USERENV('LANG');
• Validate multilingual coverage by counting rows per ATTR_CODE_ID across languages.
• Extract translated attribute metadata for data-warehouse or integration feeds, respecting SOURCE_LANG.
• Audit translation changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The most significant related objects are:

• PV_ATTRIBUTE_CODES_B — The base table holding language-independent columns; joined on ATTR_CODE_ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for data segregation.
• Standard EBS language and audit infrastructure tables (for example, FND_LANGUAGES) that support the LANGUAGE and who-columns.

Because PV_ATTRIBUTE_CODES_TL is the translation store, any UI, concurrent program, or API that displays translated attribute code names depends on it indirectly through the base and translation table pair.