Search Results fnd_conc_release_classes




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_CLASSES table is a core data object within the Application Object Library (FND) of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the master definition table for concurrent program schedules, which are also known as release classes. A release class is a logical grouping mechanism that allows system administrators to schedule and control the execution of batches of concurrent requests. This table stores the fundamental metadata for each schedule, enabling the Concurrent Manager to process requests based on predefined time-based or dependency-based rules rather than immediate submission. Its role is central to automating and streamlining batch processing workflows within the EBS environment.

Key Information Stored

The table's structure is designed to uniquely identify and describe each schedule within a specific application. The primary key is a composite of APPLICATION_ID and RELEASE_CLASS_ID, ensuring uniqueness within the EBS instance. A unique key on APPLICATION_ID and RELEASE_CLASS_NAME enforces naming conventions. Key columns include RELEASE_CLASS_NAME for the schedule's identifier and RELEASE_CLASS_ID as the system-generated unique numeric identifier. Standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track changes. The table's relationships, as defined by its foreign keys, are critical to its function, linking it to user tables (FND_USER, FND_LOGINS) and to the concurrent request execution engine.

Common Use Cases and Queries

This table is primarily referenced for administrative reporting, troubleshooting, and integration tasks. Common scenarios include identifying all defined schedules within the system, investigating the schedule associated with a specific concurrent request, or diagnosing issues with scheduled job batches. A typical query joins FND_CONC_RELEASE_CLASSES with the concurrent requests table and the application metadata table for a comprehensive report:

  • SELECT fcrc.release_class_name,
           fcr.request_id,
           fat.application_name
    FROM apps.fnd_conc_release_classes fcrc,
         apps.fnd_concurrent_requests fcr,
         apps.fnd_application_tl fat
    WHERE fcrc.application_id = fcr.release_class_app_id
    AND fcrc.release_class_id = fcr.release_class_id
    AND fcrc.application_id = fat.application_id
    AND fat.language = USERENV('LANG');

Direct manipulation of data in this table via DML is strongly discouraged; schedule creation and maintenance should be performed through the standard EBS administrator interface or dedicated APIs.

Related Objects

As indicated by the foreign key metadata, FND_CONC_RELEASE_CLASSES is integral to several key concurrent processing tables. The FND_CONCURRENT_REQUESTS table references it to associate individual requests with a specific schedule. The FND_CONC_RELEASE_CLASSES_TL table provides translated descriptions for the schedules. The FND_CONC_REL_CONJ_MEMBERS table defines the membership of concurrent programs within a specific release class, detailing the components of the schedule. Furthermore, it maintains referential integrity with the standard EBS audit tables FND_USER and FND_LOGINS. These relationships collectively form the backbone of the EBS concurrent scheduling subsystem.