Search Results fnd_request_sets_tl_uk

Overview

The FND_REQUEST_SETS_TL table is a core Application Object Library table within Oracle E-Business Suite (EBS) that stores translated, language-specific text for request sets. It is a child table of the base table FND_REQUEST_SETS, which holds the core definition of a request set—a group of concurrent programs that can be submitted together. The primary role of the TL (Translation) table is to support the multilingual capabilities of EBS by storing translated values for user-facing fields, such as the request set name and description, for each installed language. This enables users to view and interact with request set definitions in their preferred language, a critical feature for global deployments of EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to manage translations through a combination of key and descriptive columns. Its primary key (FND_REQUEST_SETS_TL_PK) uniquely identifies a translation row using APPLICATION_ID, REQUEST_SET_ID, and LANGUAGE. A unique key (FND_REQUEST_SETS_TL_UK) also enforces that the USER_REQUEST_SET_NAME is unique per APPLICATION_ID and LANGUAGE. Key columns include APPLICATION_ID and REQUEST_SET_ID, which link back to the parent FND_REQUEST_SETS table. The LANGUAGE and SOURCE_LANG columns track the translation language and the original language of the record, respectively, with foreign key references to FND_LANGUAGES. The primary user-facing translated data is stored in USER_REQUEST_SET_NAME and DESCRIPTION. Standard Oracle WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track row history.

Common Use Cases and Queries

A primary use case is generating reports of request sets in a specific language for user documentation or system audits. Developers and DBAs query this table to verify or update translations, especially after implementing new languages or customizations. A common pattern is to join it with the base table to get a complete, translated definition.

• List Request Set Names and Descriptions in a Specific Language:
  SELECT t.user_request_set_name, t.description
  FROM fnd_request_sets_tl t, fnd_request_sets b
  WHERE t.request_set_id = b.request_set_id
  AND t.application_id = b.application_id
  AND t.language = USERENV('LANG')
  AND b.application_id = &app_id;
• Identify Missing Translations for a Request Set:
  SELECT l.language_code
  FROM fnd_languages l
  WHERE l.installed_flag in ('I', 'B')
  MINUS
  SELECT t.language
  FROM fnd_request_sets_tl t
  WHERE t.request_set_id = &req_set_id
  AND t.application_id = &app_id;

Related Objects

FND_REQUEST_SETS_TL has integral relationships with several key EBS objects. Its primary parent is the FND_REQUEST_SETS table, which contains the non-translatable definitional data. It maintains foreign key relationships to FND_LANGUAGES for both the LANGUAGE and SOURCE_LANG columns, ensuring data integrity for language codes. For audit trail purposes, it references FND_USER (for CREATED_BY and LAST_UPDATED_BY) and FND_LOGINS (for LAST_UPDATE_LOGIN). From an application perspective, translations are typically managed via the Oracle Application Developer forms or APIs, rather than through direct DML on this table.