Search Results fnd_conc_release_states




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_STATES table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS), versions 12.1.1 and 12.2.2. It functions as the master definition table for concurrent states, which are user-defined conditions used to control the execution of scheduled concurrent programs. Specifically, these states are integral to the Advanced Schedules feature, enabling the conditional release of concurrent requests based on complex, configurable business logic. The table resides in the APPLSYS schema and maintains the fundamental attributes and metadata for each state, establishing relationships with other key concurrent processing entities.

Key Information Stored

The table's structure is designed to uniquely identify and describe each concurrent state within a specific application. The primary key is a composite of APPLICATION_ID and CONCURRENT_STATE_ID, ensuring uniqueness across the EBS instance. The CONCURRENT_STATE_NAME, paired with APPLICATION_ID in a unique key constraint, provides a human-readable identifier. Other critical columns include LOOKUP_TYPE_ID, which links the state to its defined type in the FND_CONC_STATE_LOOKUP_TYPES table, and STATUS, which indicates the active or inactive status of the state definition. The table also contains standard Oracle Applications columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing purposes.

Common Use Cases and Queries

This table is primarily referenced for administrative reporting, troubleshooting schedule dependencies, and data validation. A common use case involves identifying all active concurrent states defined for a particular application to audit or clean up schedule definitions. For example, a query to list all states for the General Ledger application (APPLICATION_ID = 101) would be:

  • SELECT cs.concurrent_state_name, cs.status, ltl.meaning FROM apps.fnd_conc_release_states cs, apps.fnd_conc_state_lookups_tl ltl WHERE cs.application_id = 101 AND cs.lookup_type_id = ltl.lookup_type_id AND cs.status = ltl.lookup_code AND ltl.language = USERENV('LANG');

Another scenario involves diagnosing a schedule that fails to release requests by verifying the underlying state definitions and their statuses. Developers may also query this table when building custom extensions that interact with the Advanced Schedules framework.

Related Objects

FND_CONC_RELEASE_STATES has documented relationships with several other EBS objects, primarily through foreign key constraints. The most significant relationships are:

  • FND_CONC_RELEASE_STATES_TL: The Translation table, joined on APPLICATION_ID and CONCURRENT_STATE_ID, stores the user-facing name in multiple languages.
  • FND_CONC_STATE_LOOKUP_TYPES and FND_CONC_STATE_LOOKUPS: Joined via LOOKUP_TYPE_ID, these tables define the valid state types and their display values.
  • FND_CONC_REL_DISJ_MEMBERS: Joined on STATE_APPLICATION_ID (maps to APPLICATION_ID) and STATE_ID (maps to CONCURRENT_STATE_ID), this table links states to disjunction members within complex schedule logic.
  • FND_USER (twice) and FND_LOGINS: Standard tables for tracking the user (CREATED_BY, LAST_UPDATED_BY) and login session (LAST_UPDATE_LOGIN) responsible for creating or modifying a state record.