Results for “fnd_conc_release_states”

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

Overview

FND_CONC_RELEASE_STATES is an Application Object Library (FND) reference table in the APPLSYS schema that stores the named concurrent processing states available to Oracle E-Business Suite's Advanced Schedules feature. In Oracle EBS 12.1.1 and 12.2.2, Advanced Schedules allow administrators to define dependency conditions that determine when a concurrent program may release; the state definitions held in this table form the vocabulary from which those dependency rules are constructed. Each row represents one user-defined concurrent state, scoped to an application, with lifecycle metadata and an optional association to a concurrent state lookup type and a request or schedule owner.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive attributes (state name, enabled flag, status, effective dates) alongside audit columns pointing to FND_USER and FND_LOGINS, which is characteristic of a satellite attached to a parent application/key structure rather than an independent hub or an associative link.

Key Information Stored

The documented physical schema contains 17 columns. The most significant include:

• APPLICATION_ID — the owning application, part of both the primary key and the unique business key.
• CONCURRENT_STATE_ID — the surrogate identifier for each state; combined with APPLICATION_ID it forms the primary key FND_CONC_RELEASE_STATES_PK (and the unique index FND_CONC_RELEASE_STATES_U1).
• CONCURRENT_STATE_NAME — the user-visible state name; with APPLICATION_ID it forms the unique business key FND_CONC_RELEASE_STATES_UK1.
• ENABLED_FLAG — controls whether the state is active and selectable in schedule definitions.
• STATUS — the state's status value, resolved through LOOKUP_TYPE_ID.
• LOOKUP_TYPE_ID — foreign key to FND_CONC_STATE_LOOKUPS and FND_CONC_STATE_LOOKUP_TYPES, tying the state to its lookup classification.
• OWNER_REQ_ID, OWNER_SCH_ID, OWNER_SCH_APP_ID — identify the request or schedule that owns the state.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective date range governing when the state is valid.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns with foreign keys to FND_USER and FND_LOGINS.
• CREATION_DATE, LAST_UPDATE_DATE, UPDATED_FLAG — standard audit and synchronization metadata.

The surrogate primary key is the (APPLICATION_ID, CONCURRENT_STATE_ID) pair; the business-key candidate is (APPLICATION_ID, CONCURRENT_STATE_NAME).

Common Use Cases and Queries

Typical scenarios include listing all enabled states for a given application, auditing effective-date windows, and joining states to their lookup classifications for reporting on Advanced Schedule behavior.

• Enumerating active states: SELECT concurrent_state_id, concurrent_state_name FROM fnd_conc_release_states WHERE application_id = :app_id AND enabled_flag = 'Y';
• Resolving lookup classification: join LOOKUP_TYPE_ID to FND_CONC_STATE_LOOKUP_TYPES to report each state's category.
• Effectivity audit: filter on START_DATE_ACTIVE and END_DATE_ACTIVE to find states active as of a reporting date.
• Dependency analysis: join to FND_CONC_REL_DISJ_MEMBERS on STATE_APPLICATION_ID and STATE_ID to trace which Advanced Schedule rules reference each state.
• Translated reporting: join to FND_CONC_RELEASE_STATES_TL on APPLICATION_ID and CONCURRENT_STATE_ID for language-specific state names.

Related Objects

• FND_CONC_RELEASE_STATES_TL — translation table; joins on APPLICATION_ID and CONCURRENT_STATE_ID.
• FND_CONC_REL_DISJ_MEMBERS — disjunction members reference states via STATE_APPLICATION_ID and STATE_ID.
• FND_CONC_STATE_LOOKUPS — lookup values referenced by LOOKUP_TYPE_ID.
• FND_CONC_STATE_LOOKUP_TYPES — lookup type definitions referenced by LOOKUP_TYPE_ID.
• FND_USER — audit relationships via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — audit relationship via LAST_UPDATE_LOGIN.