Results for “fnd_conc_release_classes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_CONC_RELEASE_CLASSES is a transactional configuration table in the Oracle E-Business Suite Application Object Library (FND) product, owned by the APPLSYS schema. It stores the definition of release classes, which are named groupings that control how concurrent programs, requests, and request sets are released for processing by the Concurrent Manager. A release class effectively governs the sequencing and dependency rules that determine when a submitted concurrent request becomes eligible to run, including conjunction-type relationships between requests in a class.

The table is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. In Data Vault modeling terms, the metadata classifies this object as satellite-leaning. This is a heuristic suggestion based on the foreign-key structure: the table carries descriptive attributes (name, class type, enablement flags, activity dates, and resubmission parameters) that are keyed by a composite of APPLICATION_ID and RELEASE_CLASS_ID, with audit columns tracking creation and modification. Practitioners modeling concurrent scheduler metadata in a warehouse should therefore treat this table as a satellite attached to the release-class business key, rather than as an independent hub.

Key Information Stored

The primary key FND_CONC_RELEASE_CLASSES_PK is the surrogate composite of APPLICATION_ID and RELEASE_CLASS_ID. Two unique indexes act as business-key candidates: FND_CONC_RELEASE_CLASSES_U1 (also APPLICATION_ID, RELEASE_CLASS_ID) and FND_CONC_RELEASE_CLASSES_U2 (APPLICATION_ID, RELEASE_CLASS_NAME). The second index enforces that a release class name is unique within an application.

• APPLICATION_ID and RELEASE_CLASS_ID — composite identifier of the release class.
• RELEASE_CLASS_NAME — the user-facing name enforced as unique per application.
• CLASS_TYPE — indicates the classification category of the release class.
• CLASS_INFO — ancillary configuration data associated with the class type.
• OWNER_REQ_ID — the concurrent request that owns the class, if applicable.
• OWNER_SCH_ID and OWNER_SCH_APP_ID — the owning schedule identity and its application.
• ENABLED_FLAG — controls whether the release class is active.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective dating window.
• RESUBMIT_INTERVAL, RESUBMIT_INTERVAL_UNIT_CODE, and RESUBMIT_INTERVAL_TYPE_CODE — the resubmission cadence and unit applied to the class.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS who-columns capturing user and login context.

Common Use Cases and Queries

The table is queried most often when diagnosing why concurrent requests are queued, delayed, or blocked. Release classes define the rules by which the Conflict Resolution Manager (CRM) and Concurrent Manager release requests, so support and DBA personnel inspect this table alongside FND_CONCURRENT_REQUESTS.

To list enabled release classes for an application:

SELECT release_class_id, release_class_name, class_type,
       enabled_flag, start_date_active, end_date_active
FROM   fnd_conc_release_classes
WHERE  application_id = :app_id
AND    enabled_flag = 'Y'
ORDER BY release_class_name;

To identify the release class assigned to a specific concurrent request:

SELECT r.request_id, r.release_class_app_id, c.release_class_name
FROM   fnd_concurrent_requests r,
       fnd_conc_release_classes c
WHERE  r.release_class_app_id = c.application_id
AND    r.release_class_id     = c.release_class_id
AND    r.request_id = :request_id;

Reporting use cases include listing active release-class windows for capacity planning, auditing resubmission schedules by RESUBMIT_INTERVAL_TYPE_CODE, and reconciling class membership through FND_CONC_REL_CONJ_MEMBERS to understand conjunction dependencies between requests.

Related Objects

• FND_CONCURRENT_REQUESTS — references this table via RELEASE_CLASS_APP_ID and RELEASE_CLASS_ID; the most common join target.
• FND_CONC_RELEASE_CLASSES_TL — the translation table keyed by APPLICATION_ID and RELEASE_CLASS_ID, holding language-specific class names.
• FND_CONC_REL_CONJ_MEMBERS — references this table via CLASS_APPLICATION_ID and RELEASE_CLASS_ID, defining conjunction membership.
• FND_USER — parent of CREATED_BY and LAST_UPDATED_BY audit references.
• FND_LOGINS — parent of LAST_UPDATE_LOGIN, providing the login audit trail.
• FND_CONCURRENT_PROGRAMS and FND_REQUEST_SETS — related FND concurrent objects commonly joined in release-class reporting.