Search Results pa_res_types_tl




Overview
Explore in AI Chat

Overview

The PA_RES_TYPES_TL table is a core translation table within the Oracle E-Business Suite Projects (PA) module. It functions as the repository for multilingual descriptions of resource types, enabling the application to support global deployments. This table operates in conjunction with its base table, PA_RES_TYPES_B, which holds the language-independent, transactional data. The TL (Translation) table's primary role is to store the user-facing, translated names and descriptions for resource types, which are critical for defining the labor and non-labor resources that can be assigned to project tasks. Its existence is fundamental to the EBS Multi-Org and Multi-Language architecture, allowing a single installation to present data in multiple languages based on user preferences.

Key Information Stored

The table's structure is designed to manage translated text for each supported language. Its primary key is a composite of RES_TYPE_ID and LANGUAGE, ensuring a unique translation entry per resource type per language. Key columns include RES_TYPE_ID, which is the foreign key linking to the base resource type definition in PA_RES_TYPES_B. The LANGUAGE column holds the language code (e.g., 'US', 'FR') and is a foreign key to FND_LANGUAGES. The SOURCE_LANG column, also referencing FND_LANGUAGES, indicates the original language in which the data was entered, which is typically the installation base language. The most critical user-facing columns are NAME and DESCRIPTION, which store the translated text for the resource type's label and explanatory details, respectively.

Common Use Cases and Queries

This table is primarily accessed by the application's user interface to display resource type names in reports, lists of values (LOVs), and data entry forms according to the session language. A common reporting requirement is to extract a list of all resource types with their descriptions in a specific language. For example, to retrieve all active resource types in French, one might join to the base table for status and the translation table for the French text. A typical SQL pattern is:

  • SELECT b.RES_TYPE_ID, tl.NAME, tl.DESCRIPTION
  • FROM PA_RES_TYPES_B b, PA_RES_TYPES_TL tl
  • WHERE b.RES_TYPE_ID = tl.RES_TYPE_ID
  • AND tl.LANGUAGE = userenv('LANG')
  • AND b.END_DATE_ACTIVE IS NULL;

Data maintenance is typically performed via the Oracle Applications' translation forms or APIs, not via direct SQL updates, to maintain integrity with the seed data and base tables.

Related Objects

PA_RES_TYPES_TL has defined foreign key relationships with several key application objects, as documented in the ETRM metadata. Its primary relationship is with the base table PA_RES_TYPES_B via the RES_TYPE_ID column. This is a critical dependency, as every record in the TL table must correspond to a valid record in the base table. Furthermore, it has two foreign key relationships with the application's language table, FND_LANGUAGES. One relationship is via the LANGUAGE column to validate the translation language code, and another is via the SOURCE_LANG column to validate the code for the original source language of the data. These relationships enforce referential integrity and ensure that translations are only stored for installed and active languages within the EBS instance.