Search Results fa_lookups_tl




Overview
Explore in AI Chat

Overview

FA_LOOKUPS_TL is the translated (Multi-Lingual Support, MLS) child table of the Oracle Assets QuickCode lookup framework, owned by the FA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific text — the meaning and description — associated with seeded and user-defined Oracle Assets lookup values. Where the base table FA_LOOKUPS_B holds language-independent attributes for each QuickCode, FA_LOOKUPS_TL holds one row per lookup value per installed language, exposing the translated display text used throughout the Assets forms, concurrent programs, and reports.

QuickCodes in Oracle Assets drive enumerated fields such as asset categories, depreciation methods, prorate conventions, retirement types, and transaction source types. The translated layer ensures these values render correctly for users operating in non-English languages while retaining a single canonical lookup structure. The table is documented as a standalone object with a heuristic Data Vault classification of standalone; from a modeling perspective, this suggests treating it as a reference or satellite-style structure rather than a hub or link, since it carries descriptive attributes (MEANING, DESCRIPTION) tied to a business key of lookup type and code.

Key Information Stored

The table is defined with 12 documented columns. The most operationally significant are:

  • LOOKUP_TYPE — The QuickCode category (for example, a category or method lookup type). Part of the composite primary key and the principal filter in most queries.
  • LOOKUP_CODE — The internal, language-independent code for the lookup value. Part of the composite primary key.
  • LANGUAGE — The NLS language code identifying which translation this row provides. Part of the composite primary key.
  • MEANING — The translated display text for the QuickCode, shown to users in the corresponding language.
  • DESCRIPTION — The translated longer description of the lookup value.
  • SOURCE_LANG — The language from which the translation was derived, used by the MLS translation tools.
  • ZD_EDITION_NAME — The editioning column supporting Online Patching and Edition-Based Redefinition in 12.2.x.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle audit columns tracking who created and last modified each translated row.

The surrogate/composite primary key is documented as FA_LOOKUPS_TL_PK on (LOOKUP_TYPE, LOOKUP_CODE, LANGUAGE). A separate unique index, FA_LOOKUPS_TL_U1, extends the business key to include ZD_EDITION_NAME, reflecting the editioning model in 12.2.x.

Common Use Cases and Queries

Typical uses include resolving the display text for an enumerated Assets field, verifying that a translation exists for a given language, and joining translated meanings to transactional data that stores only lookup codes. A representative query retrieves the English meaning of all values for a lookup type:

  • SELECT lookup_code, meaning FROM fa_lookups_tl WHERE lookup_type = :p_type AND language = 'US';
  • Join translated text to the base table: SELECT b.lookup_code, tl.meaning FROM fa_lookups_b b, fa_lookups_tl tl WHERE b.lookup_type = tl.lookup_type AND b.lookup_code = tl.lookup_code AND tl.language = USERENV('LANG');
  • Detect missing translations for a target language by comparing against expected codes.

Reporting scenarios include audit reports on customized QuickCodes, validation of terminology consistency across languages, and data extraction for interfaces that require descriptive labels rather than codes.

Related Objects

  • FA_LOOKUPS_B — The base (language-independent) lookup table; join on LOOKUP_TYPE and LOOKUP_CODE.
  • FA_LOOKUPS — The public synonym/view exposing the lookup and translated text together.
  • FND_LOOKUP_TYPES_TL — The shared Application Object Library translated lookup types that parallel the same MLS pattern.
  • FND_LOOKUP_VALUES_VL — The AOL view that provides the translated lookup values reused across modules, including Assets QuickCodes.
  • Assets transactional tables that store lookup codes (for example, asset category and depreciation method references) depend on FA_LOOKUPS_TL for display text.

Because the table is documented as standalone, dependency is driven by matching lookup_type and lookup_code values rather than by enforced foreign keys.