Search Results lookup_value




Overview
Explore in AI Chat

Overview

The FND_CONC_STATE_LOOKUPS_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Residing in the APPLSYS schema, its primary function is to store translated, language-specific descriptions for concurrent program state lookup codes. It serves as the multilingual counterpart to the base table FND_CONC_STATE_LOOKUPS, enabling the EBS user interface to display statuses like "Pending," "Running," or "Completed" in the language of the end-user's session. This table is integral to the global deployment of EBS, ensuring that concurrent manager statuses and related messages are presented correctly across all supported languages.

Key Information Stored

The table's structure is designed to support multilingual data with standard EBS audit columns. Its composite primary key uniquely identifies each translation record. The most critical columns include:

  • LOOKUP_TYPE_ID and LOOKUP_VALUE: Together with LANGUAGE, these form the primary key. They link the translation to a specific lookup type and code (e.g., 'CP_STATUS_CODE', 'R') from the base FND_CONC_STATE_LOOKUPS table.
  • LANGUAGE: The ISO code (e.g., 'US', 'KO', 'JA') for which the translation is stored.
  • MEANING and DESCRIPTION: The core translated text. MEANING typically holds the short, displayable name (e.g., "Running"), while DESCRIPTION may contain a longer explanation.
  • SOURCE_LANG: Indicates the language code of the original record from which the translation was created, facilitating synchronization during translation updates.
  • Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track record history.

Common Use Cases and Queries

This table is primarily accessed indirectly by the EBS application's internal logic to resolve display values. Direct queries are most common for data validation, support diagnostics, and custom reporting where translated statuses are required. A typical pattern is to join this table with the base lookup table and filter by the user's session language.

Sample Query: Retrieving all translated concurrent program statuses for a specific language.

SELECT b.lookup_type,
       b.lookup_code,
       t.meaning,
       t.description
FROM   fnd_conc_state_lookups b,
       fnd_conc_state_lookups_tl t
WHERE  b.lookup_type_id = t.lookup_type_id
AND    b.lookup_code    = t.lookup_value
AND    t.language       = USERENV('LANG')
ORDER BY b.lookup_type, b.lookup_code;

Another critical use case is verifying translation completeness for a new language installation or troubleshooting missing translations, which often manifest as untranslated codes appearing in the user interface.

Related Objects

FND_CONC_STATE_LOOKUPS_TL maintains defined foreign key relationships with several fundamental EBS tables, as documented in the provided metadata:

  • FND_CONC_STATE_LOOKUPS: The primary relationship. The columns LOOKUP_TYPE_ID and LOOKUP_VALUE in the TL table reference the base lookup definitions.
  • FND_LANGUAGES: Referenced twice. The LANGUAGE column ensures the value is a valid installed language, and SOURCE_LANG references the same table to validate the source language code.
  • FND_USER: Referenced by the CREATED_BY and LAST_UPDATED_BY audit columns to link to the user who created or last modified the translation record.
  • FND_LOGINS: Referenced by the LAST_UPDATE_LOGIN audit column to track the session from which the last update was made.

This network of relationships ensures data integrity, enforcing that all translations correspond to valid base lookup codes, languages, and application users.