Search Results fnd_conc_state_lookup_types_tl




Overview
Explore in AI Chat

Overview

The table FND_CONC_STATE_LOOKUP_TYPES_TL is a core Application Object Library (FND) object within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Residing in the APPLSYS schema, it functions as a translation table. Its primary role is to store the translated, language-specific descriptions for concurrent program state lookup types. This table enables the EBS user interface to display these lookup type descriptions in the language of the user's session, supporting the application's global, multi-language capabilities. It is a child table to the base table FND_CONC_STATE_LOOKUP_TYPES, which holds the language-independent seed data.

Key Information Stored

The table's structure is typical of EBS translation tables. The primary key is a composite of LOOKUP_TYPE_ID and LANGUAGE, ensuring a unique translation record per language for each lookup type. The LOOKUP_TYPE_ID is a foreign key that links back to the corresponding record in FND_CONC_STATE_LOOKUP_TYPES. The LANGUAGE column stores the language code (e.g., 'US', 'F') and is a foreign key to FND_LANGUAGES. The core translated content is held in the USER_LOOKUP_TYPE_NAME column, which contains the descriptive name of the concurrent program state lookup type in the specified language. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track record history. The SOURCE_LANG column indicates the original language in which the data was created, which is critical for the translation synchronization process.

Common Use Cases and Queries

This table is primarily accessed by the EBS application runtime to render translated text. Common technical and reporting use cases include auditing translation completeness and debugging user interface display issues. A typical query retrieves the translated description for a specific lookup type in the current session language, often joining with the base table. For example:

  • SELECT t.USER_LOOKUP_TYPE_NAME FROM fnd_conc_state_lookup_types b, fnd_conc_state_lookup_types_tl t WHERE b.lookup_type_id = t.lookup_type_id AND t.language = USERENV('LANG') AND b.lookup_type = 'CONC_PROGRAM_STATUS';

Another common pattern is to identify all available translations for a given lookup type to assess localization coverage:

  • SELECT l.language_code, t.user_lookup_type_name FROM fnd_conc_state_lookup_types_tl t, fnd_languages l WHERE t.language = l.language_code AND t.lookup_type_id = 12345 ORDER BY l.language_code;

Related Objects

The table maintains defined foreign key relationships with several core FND tables, as documented in the ETRM metadata. Its primary relationship is with the base table FND_CONC_STATE_LOOKUP_TYPES via the LOOKUP_TYPE_ID column. For language reference, it joins to FND_LANGUAGES twice: once for the LANGUAGE column and once for the SOURCE_LANG column. For audit trail integrity, it references FND_USER for the CREATED_BY and LAST_UPDATED_BY columns, and FND_LOGINS for the LAST_UPDATE_LOGIN column. These relationships ensure data consistency and integrate the translation layer with the application's security and language frameworks.