Results for “fnd_request_sets_tl”

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

Overview

FND_REQUEST_SETS_TL is the translation (language) table for the Oracle E-Business Suite concurrent request set definitions stored in FND_REQUEST_SETS. It resides in the APPLSYS schema and belongs to the FND – Application Object Library product, and its structure is consistent between release 12.1.1 and 12.2.2. While FND_REQUEST_SETS holds the language-independent attributes of a request set, FND_REQUEST_SETS_TL stores the translated, user-facing text — the request set name and description — for each installed language. The suffix "_TL" follows the standard EBS convention for translation tables, which typically hold one row per (entity, language) combination and are populated by the Translation Synchronization / language installation process using a designated source language.

Under the heuristic Data Vault classification supplied in the metadata, this table is treated as a link, reflecting its role in joining a request set to a specific language. From a dimensional-modeling perspective it may equally be regarded as a descriptive satellite attached to FND_REQUEST_SETS, because it carries language-dependent descriptive attributes rather than transactional events.

Key Information Stored

The table is documented with twelve physical columns. The most significant are:

• APPLICATION_ID – identifies the application that owns the request set; part of the composite primary key and of the foreign key to FND_REQUEST_SETS.
• REQUEST_SET_ID – the internal identifier of the request set being translated; with APPLICATION_ID it anchors each row to its parent record.
• LANGUAGE – the installed language of the translated text; part of the primary key and a foreign key to FND_LANGUAGES.
• SOURCE_LANG – the language from which the translation was derived, also referencing FND_LANGUAGES. This is the standard EBS marker used to identify translatable base rows.
• USER_REQUEST_SET_NAME – the translated display name of the request set, visible to users in the Submit Request Set form and in lists of requests.
• DESCRIPTION – the translated description providing context on the purpose of the request set.
• CREATION_DATE, CREATED_BY – audit columns recording when the translation row was created and by which FND_USER.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO columns tracking the most recent change and the FND_LOGINS session that made it.
• ZD_EDITION_NAME – the editioning discriminator used in the online patching (ADOP) architecture from 12.2 onward.

The surrogate primary key FND_REQUEST_SETS_TL_PK is composed of APPLICATION_ID, REQUEST_SET_ID, and LANGUAGE. Two unique indexes act as business-key candidates: FND_REQUEST_SETS_TL_U1 (APPLICATION_ID, REQUEST_SET_ID, LANGUAGE, ZD_EDITION_NAME) and FND_REQUEST_SETS_TL_U2 (USER_REQUEST_SET_NAME, APPLICATION_ID, LANGUAGE, ZD_EDITION_NAME). The latter enforces uniqueness of the translated request set name within an application and language, reinforcing that USER_REQUEST_SET_NAME is the primary business identifier for users.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include retrieving the user-visible name of a request set in the session language, listing all translations available for a given set, and validating that translations exist for every installed language. A representative query joins the translation table to its base table:

• SELECT t.user_request_set_name, t.description, t.language, t.source_lang FROM apps.fnd_request_sets_tl t WHERE t.application_id = :app AND t.request_set_id = :set_id ORDER BY t.language;
• A language-specific lookup filters on t.language = USERENV('LANG') so the returned name matches the user's session.
• A completeness check compares rows in FND_REQUEST_SETS_TL against FND_LANGUAGES to find request sets lacking a translation for a given language.
• Audit queries use CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY to track when a name or description was changed and by whom.

Because request set names appear in the Concurrent Requests and Request Sets forms, translation rows directly affect what end users see when submitting or reviewing a request set.

Related Objects

The table's documented foreign keys identify the principal objects it depends on:

• FND_REQUEST_SETS – the base table; joined on APPLICATION_ID and REQUEST_SET_ID. Every translation row requires a corresponding parent request set.
• FND_LANGUAGES – referenced twice, via LANGUAGE and SOURCE_LANG, supplying the valid language codes.
• FND_USER – referenced by CREATED_BY and LAST_UPDATED_BY for creation and update accountability.
• FND_LOGINS – referenced by LAST_UPDATE_LOGIN to attribute the last change to a specific login session.

These relationships confirm that FND_REQUEST_SETS_TL operates strictly as a dependent, language-scoped extension of the core request set definition, and that any maintenance or extraction should preserve the APPLICATION_ID / REQUEST_SET_ID / LANGUAGE key whenever reconciling translations against the base table.