Search Results fnd_conc_release_classes_tl




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_CLASSES_TL table is a core Application Object Library (FND) table within the Oracle E-Business Suite (EBS) architecture, specifically for versions 12.1.1 and 12.2.2. As indicated by the "_TL" suffix, it is a translation table. Its primary function is to store the translated, language-specific descriptions and names for Concurrent Release Classes. A Concurrent Release Class is a logical grouping mechanism for concurrent managers, allowing administrators to define and manage sets of managers that process requests for specific application modules or functional areas. This table enables the EBS system to present these class names and descriptions in the language of the user's session, supporting the application's global, multi-language capabilities.

Key Information Stored

The table stores the translated attributes for each Concurrent Release Class record. Its structure is anchored by a composite primary key consisting of APPLICATION_ID, RELEASE_CLASS_ID, and LANGUAGE. This ensures a unique translated entry for each class per installed application and language. Key columns include RELEASE_CLASS_ID, which links to the base table FND_CONC_RELEASE_CLASSES; LANGUAGE and SOURCE_LANG, which are foreign keys to FND_LANGUAGES and denote the translation language and the original language of the data, respectively; USER_RELEASE_CLASS_NAME, which holds the translated name visible to users; and DESCRIPTION for the translated descriptive text. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track changes, with the latter two being foreign keys to FND_USER and FND_LOGINS.

Common Use Cases and Queries

This table is primarily accessed by the EBS application runtime to display localized manager class information in forms and reports. Common administrative and reporting use cases involve auditing translations or troubleshooting display issues. A typical query retrieves all translations for a specific release class to verify completeness across installed languages:

  • SELECT frct.language, frct.user_release_class_name, frct.description FROM fnd_conc_release_classes_tl frct WHERE frct.release_class_id = :class_id AND frct.application_id = :app_id ORDER BY language;

Another common pattern is to join with the base table to get a comprehensive list of classes with their base and translated details for a specific language, which is useful for support scripts or data fixes:

  • SELECT frc.release_class_id, frc.release_class_name, frct.user_release_class_name, frct.description FROM fnd_conc_release_classes frc, fnd_conc_release_classes_tl frct WHERE frc.release_class_id = frct.release_class_id AND frc.application_id = frct.application_id AND frct.language = USERENV('LANG');

Related Objects

FND_CONC_RELEASE_CLASSES_TL has integral relationships with several other FND tables. Its existence is dependent on the base table FND_CONC_RELEASE_CLASSES, with which it shares the APPLICATION_ID and RELEASE_CLASS_ID foreign key relationship. It relies on FND_LANGUAGES for valid LANGUAGE and SOURCE_LANG code values. 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. In practice, application developers and system administrators interact with these entities through defined APIs and the front-end Concurrent Manager administration forms, rather than directly manipulating these tables.