Search Results disjunction_application_id




Overview
Explore in AI Chat

Overview

The FND_CONC_REL_CONJ_MEMBERS table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a junction table that defines the membership of individual concurrent program release classes within logical disjunctions. This structure is integral to the EBS Concurrent Processing engine's release rule functionality, which governs the conditional execution of concurrent requests based on system state or other program dependencies. The table, owned by the APPLSYS schema, stores the relationships that form the building blocks of complex release logic, enabling administrators to create sophisticated scheduling and dependency rules.

Key Information Stored

The table's primary key uniquely identifies each membership record through a composite of four columns. The CLASS_APPLICATION_ID and RELEASE_CLASS_ID columns together reference a specific concurrent program release class defined in FND_CONC_RELEASE_CLASSES. The DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID columns together reference a specific logical disjunction group defined in FND_CONC_RELEASE_DISJS. This establishes a many-to-many relationship where a single disjunction can contain multiple release classes, and a release class can belong to multiple disjunctions. Standard audit columns, such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, track the creation and modification history of each record.

Common Use Cases and Queries

This table is primarily accessed for administrative reporting, troubleshooting release rules, and programmatic setup. A common use case involves diagnosing why a specific concurrent request is held or identifying all dependencies for a program. For example, to list all release classes that are members of a specific disjunction, one would query:

  • SELECT rc.user_release_class_name, rc.description FROM fnd_conc_rel_conj_members cm, fnd_conc_release_classes rc WHERE cm.class_application_id = rc.application_id AND cm.release_class_id = rc.release_class_id AND cm.disjunction_application_id = &disj_app_id AND cm.disjunction_id = &disj_id;

Conversely, to find all disjunctions a particular release class belongs to, the join would be reversed to reference FND_CONC_RELEASE_DISJS. Direct data manipulation (DML) on this table is typically performed through dedicated administrative interfaces or APIs rather than manual SQL, to maintain data integrity with related objects.

Related Objects

FND_CONC_REL_CONJ_MEMBERS is centrally connected to several key FND tables via foreign key constraints, as documented in the ETRM metadata. The primary relationships are:

  • FND_CONC_RELEASE_CLASSES: Links via (CLASS_APPLICATION_ID, RELEASE_CLASS_ID). This defines the specific program release class that is a member.
  • FND_CONC_RELEASE_DISJS: Links via (DISJUNCTION_APPLICATION_ID, DISJUNCTION_ID). This defines the logical disjunction group containing the member.
  • FND_USER (twice): Links CREATED_BY and LAST_UPDATED_BY to the user ID, recording who created and last modified the record.
  • FND_LOGINS: Links LAST_UPDATE_LOGIN to track the session from which the last update was made.

These relationships ensure referential integrity and place this table as a critical link in the hierarchy of objects that define concurrent program release logic.