Search Results ego_mtl_sy_items_ext_tl_pk

Overview

The EGO_MTL_SY_ITEMS_EXT_TL table is a core data object within the Oracle E-Business Suite (EBS) Advanced Product Catalog (EGO) module. It functions as a translation (TL) table designed to store multilingual user-defined attribute (UDA) data for catalog items. Its primary role is to extend the standard item master (MTL_SYSTEM_ITEMS_B) by holding descriptive, language-specific values for attributes defined through the EGO extensibility framework. This enables organizations to maintain a centralized product catalog with rich, locale-specific descriptive content, which is critical for global operations and multi-language user interfaces in releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores translated values for extensible attributes associated with catalog items. While the full column list is not detailed in the provided metadata, the structure of a standard TL table and its documented primary key imply critical columns. The primary key, EGO_MTL_SY_ITEMS_EXT_TL_PK, is based on the EXTENSION_ID column, which uniquely identifies each attribute value record. Standard TL table conventions dictate it will also include a LANGUAGE column (e.g., NLS_LANGUAGE) to store the language code (e.g., 'US', 'FR') and a SOURCE_LANG column. The table will contain one or more attribute columns (often named ATTRIBUTE_n through ATTRIBUTE_n) that hold the actual translated text values for the user-defined attributes. A CREATION_DATE and LAST_UPDATE_DATE are also typically present for auditing.

Common Use Cases and Queries

This table is primarily accessed for reporting and data extraction scenarios requiring item information with its extended, language-specific attributes. A common use case is generating localized product catalogs or data feeds for downstream systems like eCommerce platforms. Sample queries often involve joining this table to its base table (EGO_MTL_SY_ITEMS_EXT_B) and the core item master. For example, to retrieve item numbers and a specific UDA in French, a query might resemble:

• SELECT msib.segment1 Item_Number, ext_tl.attribute_1 French_Description
• FROM mtl_system_items_b msib, ego_mtl_sy_items_ext_b ext_b, ego_mtl_sy_items_ext_tl ext_tl
• WHERE msib.inventory_item_id = ext_b.inventory_item_id
• AND ext_b.extension_id = ext_tl.extension_id
• AND ext_tl.language = 'F'
• AND msib.organization_id = <org_id>;

Data maintenance is typically performed via the EGO application interfaces, not via direct SQL updates.

Related Objects

EGO_MTL_SY_ITEMS_EXT_TL has a direct and essential relationship with its base table, EGO_MTL_SY_ITEMS_EXT_B. The TL table's EXTENSION_ID column is a foreign key referencing the primary key of the base table. This base table, in turn, is linked to the core inventory item definition via the INVENTORY_ITEM_ID column, joining to MTL_SYSTEM_ITEMS_B. The primary integration flow is: MTL_SYSTEM_ITEMS_B -> EGO_MTL_SY_ITEMS_EXT_B -> EGO_MTL_SY_ITEMS_EXT_TL. This hierarchy ensures that every translated extensible attribute is tied to a specific base attribute record and, ultimately, to a specific inventory item. The table is also referenced by various EGO catalog APIs and user interface forms that render item details.