Search Results pv_attribute_codes_tl_u1

Overview

PV.PV_ATTRIBUTE_CODES_TL is the translation (TL) table within the Oracle EBS Product Lifecycle Management / Product Development schema (PV, historically "Product Vision"). It stores the multilingual name and description of attribute codes that are defined in the base table PV_ATTRIBUTE_CODES_B. In Oracle EBS Release 12.1.1 and 12.2.2, the TL architectural pattern separates language-independent business data from language-dependent descriptive text, allowing the same attribute code definition to be presented in each installed language without duplicating the underlying record.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its unique index PV_ATTRIBUTE_CODES_TL_U1 resides in APPS_TS_TX_IDX. The object holds a VALID status and carries an Oracle FND design data registration under PV.PV_ATTRIBUTE_CODES_TL. From a Data Vault modeling perspective, the metadata suggests a satellite-leaning classification: it extends the base entity PV_ATTRIBUTE_CODES_B with descriptive, language-scoped attributes rather than introducing new business relationships. Each row depends on a parent attribute code and adds translated text, which is characteristic satellite behavior.

Key Information Stored

The table contains twelve documented columns. The most important are listed below.

• ATTR_CODE_ID (NUMBER 15) — the attribute code identifier and the foreign key to PV_ATTRIBUTE_CODES_B. It forms the leading column of the primary key.
• LANGUAGE (VARCHAR2) — the language into which the record is translated. It completes the primary key with ATTR_CODE_ID.
• SOURCE_LANG (VARCHAR2) — records the language of the original (source) text, supporting the EBS translation workflow.
• DESCRIPTION (VARCHAR2 240) — the translated description of the attribute code, the primary user-facing payload of this table.
• SECURITY_GROUP_ID (NUMBER 15) — the security group identifier, with a documented foreign key to FND_SECURITY_GROUPS for multi-org/security-group isolation.
• OBJECT_VERSION_NUMBER (NUMBER) — used for optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns capturing audit and user context.
• ZD_EDITION_NAME (VARCHAR2 30) — the editioning column introduced in the 12.2 online patching architecture, enabling Edition-Based Redefinition.

The surrogate/business primary key is PV_ATTRIBUTE_CODES_TL_PK on (ATTR_CODE_ID, LANGUAGE). The documented unique index PV_ATTRIBUTE_CODES_TL_U1 extends this to (ATTR_CODE_ID, LANGUAGE, ZD_EDITION_NAME), which is the business-key candidate that guarantees one translation row per attribute code, language, and edition.

Common Use Cases and Queries

Typical usage centers on presenting attribute code descriptions in the user's session language, verifying that translations exist for all required languages, and reconciling translations against the base table. A common join is:

• SELECT tl.attr_code_id, tl.language, tl.description FROM pv_attribute_codes_tl tl WHERE tl.language = USERENV('LANG') AND tl.attr_code_id = :attr_code_id;
• Joining to the base table: SELECT b.attr_code_id, b.attribute_code, tl.description FROM pv_attribute_codes_b b, pv_attribute_codes_tl tl WHERE b.attr_code_id = tl.attr_code_id AND tl.language = 'US';
• Completeness reporting: identify base records lacking a translation for a given language.
• Filtering by security group using SECURITY_GROUP_ID for multi-org environments.

Related Objects

The following objects are most significant in relation to this table.

• PV.PV_ATTRIBUTE_CODES_B — the base table holding language-independent attribute code definitions; joined on ATTR_CODE_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• PV.PV_ATTRIBUTE_CODES_TL# — the underlying editioning/trigger-related object recorded as dependent on the table.
• Attribute code setup, validation, and description lookup forms that read translated text for display.