Results for “status_value”

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

Overview

FND_CONC_REL_DISJ_MEMBERS is a core configuration table within the FND - Application Object Library product of Oracle E-Business Suite, owned by the APPLSYS schema. It stores the individual members that compose a disjunction within the Concurrent Processing release rules framework. In Oracle EBS concurrent processing, release rules determine whether a concurrent program is allowed to run based on conditions such as the login state of the requesting user, the responsibility, or time-based periods. A disjunction groups multiple such conditions together, and FND_CONC_REL_DISJ_MEMBERS captures the constituent members of those disjunctions, along with their negation and period-or-state behavior.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure suggests this object behaves as a link table. It connects a parent disjunction definition to the states and periods that serve as member conditions, while also carrying descriptive attributes such as negation and status flags and audit columns inherited from the standard EBS WHO columns.

Key Information Stored

The primary key FND_CONC_REL_DISJ_MEMB_PK is a composite surrogate key spanning DISJUNCTION_APPLICATION_ID, DISJUNCTION_ID, PERIOD_OR_STATE_FLAG, NEGATION_FLAG, STATE_APPLICATION_ID, STATE_ID, PERIOD_APPLICATION_ID, and PERIOD_ID. A unique index FND_CONC_REL_DISJ_MEMB_U1 mirrors this same column list, confirming it as the documented business-key candidate.

• DISJUNCTION_APPLICATION_ID / DISJUNCTION_ID — identify the parent disjunction in FND_CONC_RELEASE_DISJS that this member belongs to.
• PERIOD_OR_STATE_FLAG — indicates whether the member references a period (time-based) condition or a state (login/application) condition.
• NEGATION_FLAG — specifies whether the member condition is negated (a NOT condition) within the disjunction.
• STATE_APPLICATION_ID / STATE_ID — foreign key to FND_CONC_RELEASE_STATES, referencing the state condition used when the member is state-based.
• PERIOD_APPLICATION_ID / PERIOD_ID — foreign key to FND_CONC_RELEASE_PERIODS, referencing the period condition used when the member is period-based.
• STATUS_VALUE — holds the status or evaluation value associated with the member.
• OWNER_REQ_ID, OWNER_SCH_ID, OWNER_SCH_APP_ID — identify the owning request and schedule context for the member.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER and LAST_UPDATE_LOGIN referencing FND_LOGINS.

Common Use Cases and Queries

Administrators and developers query this table to understand and troubleshoot why a concurrent program is or is not released to a given user or request. Typical reporting includes listing all members of a disjunction, or searching for disjunctions that include a specific state or period.

• Retrieve disjunction members joined to their state definitions to review login-state conditions.
• Generate rules documentation for concurrent program release, exposing NEGATION_FLAG and PERIOD_OR_STATE_FLAG behavior.
• Audit queries filtering on CREATION_DATE or LAST_UPDATE_DATE to track configuration changes and identify which FND_USER made them.
• Diagnostic SQL that reconstructs the full logical condition by joining members to FND_CONC_RELEASE_DISJS, FND_CONC_RELEASE_STATES, and FND_CONC_RELEASE_PERIODS.

Related Objects

• FND_CONC_RELEASE_DISJS — parent disjunction table; joins on DISJUNCTION_APPLICATION_ID and DISJUNCTION_ID.
• FND_CONC_RELEASE_STATES — state condition definitions; joins on STATE_APPLICATION_ID and STATE_ID.
• FND_CONC_RELEASE_PERIODS — period condition definitions; joins on PERIOD_APPLICATION_ID and PERIOD_ID.
• FND_USER — audit user reference; joins on CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — login audit reference; joins on LAST_UPDATE_LOGIN.