Results for “fnd_request_set_stages_tl”

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

Overview

FND_REQUEST_SET_STAGES_TL is the translation table for FND_REQUEST_SET_STAGES within the Oracle E-Business Suite Application Object Library (FND) product. It resides in the APPLSYS schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table stores language-specific, user-facing text for the stages that make up a request set, enabling Oracle EBS to present stage names and descriptions in the session language of any user while maintaining a single logical definition for all languages.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. FND_REQUEST_SET_STAGES_TL associates a parent stage record with a language identifier, forming a relationship table that joins stage identity to localized content. It sits beneath the base table FND_REQUEST_SET_STAGES, which holds the language-independent definition of each stage, and adds translated text keyed by language. This arrangement follows the standard Oracle EBS pattern in which a base table (often _B or the untranslated source) holds the primary record and a companion _TL table holds translated attributes such as names and descriptions.

Key Information Stored

The table contains 13 documented columns. The most significant are summarized below.

• SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID — Composite identifier components that, together with LANGUAGE, form the primary key FND_REQUEST_SET_STAGES_TL_PK. These columns link the translation to a specific stage within a specific request set owned by a specific application.
• LANGUAGE — The language of the translated row, a foreign key to FND_LANGUAGES. This distinguishes each localized variant of the stage text.
• SOURCE_LANG — The language in which the source record was originally created, also referencing FND_LANGUAGES.
• USER_STAGE_NAME — The translated, user-facing stage name. It participates in the unique index FND_REQUEST_SET_STAGES_TL_U2.
• DESCRIPTION — The translated descriptive text for the stage, presented to users in concurrent processing and request set setup forms.
• ZD_EDITION_NAME — Editioning column included in both unique indexes, supporting the online patching and edition-based redefinition architecture introduced in Oracle EBS 12.2.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-columns auditing row creation and modification. CREATED_BY and LAST_UPDATED_BY reference FND_USER; LAST_UPDATE_LOGIN references FND_LOGINS.

The surrogate primary key is FND_REQUEST_SET_STAGES_TL_PK (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, LANGUAGE). Business-key candidates are the unique indexes FND_REQUEST_SET_STAGES_TL_U1 (the full key plus ZD_EDITION_NAME) and FND_REQUEST_SET_STAGES_TL_U2, which substitutes USER_STAGE_NAME for the stage surrogate in the key.

Common Use Cases and Queries

Querying this table is typical when reporting request set stage definitions in a specific language, auditing translations for missing languages, or joining translated text into a report that otherwise reads only the base table. The following pattern joins the translation to its base stage record:

• SELECT t.user_stage_name, t.description FROM apps.fnd_request_set_stages_tl t WHERE t.request_set_id = :set_id AND t.language = USERENV('LANG');
• Join FND_REQUEST_SET_STAGES s to FND_REQUEST_SET_STAGES_TL t ON s.set_application_id = t.set_application_id AND s.request_set_id = t.request_set_id AND s.request_set_stage_id = t.request_set_stage_id.
• Detect missing translations by comparing stage counts per language against FND_LANGUAGES where INSTALLED_FLAG is set.
• Report stage ordering and naming for documentation or migration analysis by extracting USER_STAGE_NAME in the reporting language.

Related Objects

• FND_REQUEST_SET_STAGES — The base, untranslated stage table. Joins on SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID.
• FND_LANGUAGES — Referenced twice, by LANGUAGE and SOURCE_LANG, defining which locales are installed and active.
• FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN to record the login session of the last change.
• FND_REQUEST_SETS and the request set stage APIs/form-based setup — These consume the translated names when displaying and executing request sets.