Results for “concurrent_state_id”

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

Overview

FND_CONC_RELEASE_STATES_TL is the translation table for FND_CONC_RELEASE_STATES in the Oracle E-Business Suite Application Object Library (FND). It resides in the APPLSYS schema and stores the language-specific, user-facing names and descriptions associated with concurrent program release states used by the Concurrent Manager. Because Oracle EBS supports multiple installed languages via the Multi-Language Support (MLS) architecture, the base table holds the language-independent rows, while the corresponding _TL table holds translated descriptive text keyed by language.

This object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its structure is identical across those releases. From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is link. This reflects the table's role in joining the base release-state entity to the FND_LANGUAGES dimension across a composite key (APPLICATION_ID, CONCURRENT_STATE_ID, LANGUAGE).

Key Information Stored

The table contains eleven documented columns. The most significant are:

• APPLICATION_ID — identifies the owning application; part of the composite business and primary key.
• CONCURRENT_STATE_ID — the release-state identifier from the base table; part of the composite key.
• LANGUAGE — the language code for the translated row; the third component of the composite key.
• SOURCE_LANG — the language of the source row from which the translation was derived.
• USER_CONCURRENT_STATE_NAME — the translated, user-displayable name of the concurrent release state.
• DESCRIPTION — the translated descriptive text for the release state.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording row provenance.

The primary key is FND_CONC_RELEASE_STATES_TL_PK (APPLICATION_ID, CONCURRENT_STATE_ID, LANGUAGE). A unique index, FND_CONC_RELEASE_STATES_TL_U1, shares the same column set (APPLICATION_ID, CONCURRENT_STATE_ID, LANGUAGE), making it the documented business-key candidate. The composite PK therefore serves as the surrogate identifier while the same combination enforces one translation row per language per release state.

Common Use Cases and Queries

Typical reporting scenarios involve resolving the language-neutral concurrent state into a readable, locale-appropriate label for concurrent request monitoring and administrator dashboards. A representative query joins the base and translation tables:

• SELECT b.concurrent_state_id, t.user_concurrent_state_name, t.description FROM fnd_conc_release_states b, fnd_conc_release_states_tl t WHERE b.application_id = t.application_id AND b.concurrent_state_id = t.concurrent_state_id AND t.language = USERENV('LANG');
• Joining to FND_LANGUAGES via t.language to report which translations exist for a given state.
• Auditing stale translations by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY against FND_USER.

Related Objects

The following objects are the most significant dependents or references, based on documented foreign keys:

• FND_CONC_RELEASE_STATES — the base table; joined on APPLICATION_ID and CONCURRENT_STATE_ID.
• FND_LANGUAGES — referenced by LANGUAGE and SOURCE_LANG.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.