Search Results pa_resource_classes_tl




Overview
Explore in AI Chat

Overview

The PA_RESOURCE_CLASSES_TL table is a core data object within the Oracle E-Business Suite (EBS) Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It functions as a translation table, storing multilingual descriptions for resource classes defined in the system. Its primary role is to support global deployments by enabling the storage of user-friendly resource class names in multiple languages, which are then displayed within the application's user interface based on the user's session language. This table is integral to the Projects module's resource management and reporting capabilities, ensuring that resource classifications are comprehensible across different linguistic regions.

Key Information Stored

The table's structure is designed to hold language-specific translations linked to a base resource class identifier. Based on the provided metadata, the critical columns include:

  • RESOURCE_CLASS_ID: The primary key column and a foreign key to the base table PA_RESOURCE_CLASSES_B. This column uniquely links each translated row to its corresponding master resource class definition.
  • LANGUAGE: A foreign key to FND_LANGUAGES, this column stores the code (e.g., 'US', 'FR', 'DE') for the language of the translated text in that row.
  • SOURCE_LANG: Also a foreign key to FND_LANGUAGES, this column indicates the original language in which the data was entered. It is used by the EBS translation utilities to identify which rows require translation.
  • RESOURCE_CLASS_NAME: While not explicitly listed in the brief metadata, this is the standard column in translation tables that holds the actual translated text for the resource class's name or description.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to display localized resource class names. Common practical scenarios include generating multi-language project reports, configuring resource assignments, and performing data extracts for external systems that require translated labels. A typical query to retrieve translated resource class information for a specific language would join this table with its base table.

Sample SQL Pattern:
SELECT b.RESOURCE_CLASS_CODE,
tl.RESOURCE_CLASS_NAME,
tl.LANGUAGE
FROM PA_RESOURCE_CLASSES_B b,
PA_RESOURCE_CLASSES_TL tl
WHERE b.RESOURCE_CLASS_ID = tl.RESOURCE_CLASS_ID
AND tl.LANGUAGE = USERENV('LANG') -- or a specific language code
AND b.END_DATE_ACTIVE IS NULL; -- to get active classes

For reporting, this table is often joined through views to project assignments, expenditure items, or planning resources to present user-friendly, translated class names instead of internal codes.

Related Objects

As indicated by the foreign key constraints, PA_RESOURCE_CLASSES_TL has direct dependencies on several key EBS objects.

  • PA_RESOURCE_CLASSES_B: This is the base (or "seed data") table. It stores the fundamental, non-translatable attributes of a resource class, such as CODE and enabled dates. The TL table provides the language-specific NAME for these base records.
  • FND_LANGUAGES: This Application Object Library table is referenced twice, validating the LANGUAGE and SOURCE_LANG columns to ensure they contain installed and supported language codes within the EBS instance.
  • Related Views/APIs: While not specified in the metadata, the Projects module likely provides views (e.g., PA_RESOURCE_CLASSES_VL) that perform a outer join between the _B and _TL tables for simplified querying. Data in this table is typically maintained via the Oracle Projects application forms or underlying PL/SQL APIs, not via direct DML.