Search Results aso_sup_component_tl_pk




Overview
Explore in AI Chat

Overview

ASO_SUP_COMPONENT_TL is the translation (TL) table for the Oracle E-Business Suite Order Capture module (ASO) in releases 12.1.1 and 12.2.2. It stores the language-specific name and description attributes associated with the records held in the base ASO_SUP_COMPONENT table. In Oracle EBS, the multilingual architecture separates language-independent data from translatable attributes: the base table retains the identifiers and structural relationships, while the corresponding _TL table carries one row per installed language for each translatable column. This table specifically provides the translated COMPONENT_NAME, DESCRIPTION, and INSTRUCTION values used to present component information to users in their session language.

From a dimensional modeling perspective, the mined metadata classifies this object as a standalone entity (heuristic Data Vault classification), meaning no foreign-key-derived hub or link role is asserted beyond its own primary key. It functions as a language-keyed satellite of the base component entity, capturing descriptive, non-key attributes. The owner schema is ASO, and the object status is VALID as documented in ETRM for 12.2.2.

Key Information Stored

The table is keyed by the composite primary key ASO_SUP_COMPONENT_TL_PK (COMPONENT_ID, LANGUAGE), which uniquely identifies the translated record for a given component and language. COMPONENT_ID is the surrogate primary-key reference back to the base component, while LANGUAGE determines which linguistic row is returned.

  • COMPONENT_ID — joins to the base component record.
  • LANGUAGE — the language code of the translated content.
  • SOURCE_LANG — the language from which the translation originated, used by the Multi-Language Support (MLS) framework.
  • COMPONENT_NAME — the displayed name of the component in the target language.
  • DESCRIPTION — the descriptive text for the component.
  • INSTRUCTION — user-facing instructions associated with the component.
  • ZD_EDITION_NAME — editioning column supporting Online Patching in 12.2.x; part of the unique index ASO_SUP_COMPONENT_TL_U1 (COMPONENT_ID, LANGUAGE, ZD_EDITION_NAME), a documented business-key candidate.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns.
  • CREATION_DATE, CREATED_BY — record creation audit columns.
  • SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, restricting data visibility.

Common Use Cases and Queries

Because the base table holds only untranslated identifiers, reporting on component names must join across the _TL and _B/_base tables while restricting to the appropriate language. A typical query uses the USERENV('LANG') or an explicit language value to retrieve the correct row:

  • SELECT b.component_id, t.component_name, t.description FROM aso_sup_component_tl t WHERE t.language = USERENV('LANG')
  • Joining the _TL table to the base component table on COMPONENT_ID for a full component listing.
  • Reporting translation coverage by comparing rows per LANGUAGE against the count of base components.
  • Extracting ZD_EDITION_NAME for Edition-Based Redefinition (EBR) analysis in 12.2.2.
  • Filtering by SECURITY_GROUP_ID to enforce responsibility-level data access.

These patterns support component maintenance, multilingual audit, and localization verification reporting.

Related Objects

  • ASO_SUP_COMPONENT — the base table joined on COMPONENT_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
  • ASO_SUP_COMPONENT_TL_PK — the primary key constraint.
  • ASO_SUP_COMPONENT_TL_U1 — the unique index including ZD_EDITION_NAME.
  • The Order Capture (ASO) component maintenance APIs and concurrent programs that read and update translated component values.