Results for “class_application_id”

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

Overview

FND_CONC_REL_CONJ_MEMBERS is a table in the APPLSYS schema of Oracle E-Business Suite, belonging to the FND – Application Object Library product. Its documented description, "Members of Conjunctions," identifies its role in the concurrent program release-classification framework. The table records which release classes participate in a given conjunction expression that has been associated with a concurrent program grouping. It is a low-level configuration and processing object that supports the rules governing how concurrent requests are selected, generated, and released.

Within a Data Vault modeling taxonomy, the FK structure suggests this object is best treated as a link. Its primary key is composed entirely of foreign key attributes pointing to the release class and disjunction tables, and the table’s purpose is to resolve and record a many-to-many style association rather than to store enduring descriptive context. This is a modeling suggestion inferred from the documented key relationship, not a statement of Oracle’s internal design intent.

Key Information Stored

The table stores association data rather than descriptive text. The most important columns are:

• CLASS_APPLICATION_ID and RELEASE_CLASS_ID — identify the release class that is a member of the conjunction, referencing FND_CONC_RELEASE_CLASSES.
• DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID — identify the disjunction to which the release class belongs, referencing FND_CONC_RELEASE_DISJS.
• OWNER_REQ_ID, OWNER_SCH_ID, and OWNER_SCH_APP_ID — capture ownership context, associating the conjunction membership with a specific request and schedule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard audit columns, with the latter two referencing FND_USER and FND_LOGINS respectively.
• CREATION_DATE and CREATED_BY — creation audit columns, with CREATED_BY referencing FND_USER.

The surrogate primary key is documented as FND_CONC_REL_CONJ_MEMB_PK, comprising CLASS_APPLICATION_ID, RELEASE_CLASS_ID, DISJUNCTION_APPLICATION_ID, and DISJUNCTION_ID. A unique index, FND_CONC_REL_CONJ_MEMB_U1, carries the identical column set, making it the documented business-key candidate and reinforcing that the four FK columns uniquely identify a membership row.

Common Use Cases and Queries

Typical usage centers on diagnosing why a concurrent request was or was not released under a conjunction rule, and on reporting the effective membership of release classes within disjunctions.

• List members for a disjunction: SELECT * FROM fnd_conc_rel_conj_members WHERE disjunction_application_id = :app AND disjunction_id = :id;
• Resolve class and disjunction detail via joins to FND_CONC_RELEASE_CLASSES and FND_CONC_RELEASE_DISJS using the documented FK columns.
• Trace ownership context by filtering on OWNER_REQ_ID or OWNER_SCH_ID when investigating request-specific release behavior.
• Audit recently modified membership rows using LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATED_BY.

Related Objects

• FND_CONC_RELEASE_CLASSES — joined via CLASS_APPLICATION_ID and RELEASE_CLASS_ID.
• FND_CONC_RELEASE_DISJS — joined via DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID.
• FND_USER — joined via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — joined via LAST_UPDATE_LOGIN.

These documented FK relationships define the object’s principal dependencies; any broader concurrent-manager processing logic consumes FND_CONC_REL_CONJ_MEMBERS indirectly through the release class and disjunction framework.