Search Results fnd_conc_release_disjs




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_DISJS table is a core repository table within the Oracle E-Business Suite Application Object Library (FND) module. It stores the definition of disjunctions, which are logical OR conditions used to construct Advanced Schedules for concurrent program submission. In the context of Oracle EBS Release 12.1.1 and 12.2.2, Advanced Schedules provide a sophisticated mechanism to define complex, conditional release criteria for concurrent requests, moving beyond simple time-based scheduling. This table acts as the master definition for these disjunction rules, enabling the system to evaluate whether a request should be released to run based on a flexible combination of application-defined conditions.

Key Information Stored

The table's structure centers on uniquely identifying and describing each disjunction rule. The primary key is a composite of APPLICATION_ID and DISJUNCTION_ID, ensuring uniqueness within the application. The DISJUNCTION_NAME provides a unique, human-readable identifier within the same application. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track changes. The table's relationship with its Translation table (FND_CONC_RELEASE_DISJS_TL) indicates that the USER_DISJUNCTION_NAME column likely stores a user-facing description that can be localized. The data defines the rule's container, while the specific logical members (conditions) that make up the disjunction are stored in related detail tables.

Common Use Cases and Queries

Primary interactions with this table occur during the setup and analysis of Advanced Schedules. System administrators or developers may query it to audit existing schedule logic or troubleshoot request release issues. A common reporting need is to list all disjunction definitions within a specific application module.

Sample Query: List Disjunctions for an Application

  • SELECT disj.application_id,
           disj.disjunction_id,
           disj.disjunction_name,
           disj.user_disjunction_name,
           disj.creation_date
    FROM apps.fnd_conc_release_disjs disj
    WHERE disj.application_id = 275 -- Example: HRMS Application
    ORDER BY disj.disjunction_name;

Another critical use case involves joining to member tables to understand the full logical construct of a schedule before modifying it, ensuring changes do not inadvertently affect dependent request submissions.

Related Objects

FND_CONC_RELEASE_DISJS is central to a network of objects that manage Advanced Schedule logic. As per the documented relationships:

  • Referenced by Foreign Keys (Child Tables):
    • FND_CONC_REL_CONJ_MEMBERS: Links disjunctions to conjunctions (logical AND groups) via DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID, forming complex nested logic.
    • FND_CONC_REL_DISJ_MEMBERS: Links disjunctions to their constituent condition members (e.g., specific program statuses, completion events) via DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID.
    • FND_CONC_RELEASE_DISJS_TL: The Translation table, joined on APPLICATION_ID and DISJUNCTION_ID, stores language-specific names for the disjunction.
  • References via Foreign Keys (Parent Tables):
    • FND_USER (for CREATED_BY, LAST_UPDATED_BY): Identifies the users who created and last modified the record.
    • FND_LOGINS (for LAST_UPDATE_LOGIN): Captures the session login ID for the last update.

This relational structure allows a single disjunction rule to be reused within multiple, intricate schedule definitions managed by the Concurrent Processing architecture.