Results for “pa_res_types_tl”

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

Overview

PA_RES_TYPES_TL is the translation (TL) table for Oracle Projects resource types in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the PA schema and stores the language-dependent, translated attributes of resource type definitions. The table's base (non-translated) counterpart is PA_RES_TYPES_B, which stores language-independent columns. Together, the "_B" and "_TL" pair follows the standard Oracle Applications MLS (Multi-Language Support) pattern, where seeded or user-defined resource types such as People, Expense, and Equipment are surfaced in the user's session language. Only the display-oriented columns (NAME and DESCRIPTION) are translated; the resource type identity is held in PA_RES_TYPES_B and cross-referenced through RES_TYPE_ID.

From a Data Vault modeling perspective, the FK structure suggests classifying PA_RES_TYPES_TL as a link table. Its composite primary key (RES_TYPE_ID, LANGUAGE) connects the resource type hub (via RES_TYPE_ID) and the FND_LANGUAGES hub (via LANGUAGE and SOURCE_LANG), making it a relationship link between the resource type entity and its language-specific translation records rather than a standalone hub or satellite.

Key Information Stored

The table contains 11 documented columns. The most important are:

• RES_TYPE_ID — Surrogate identifier of the resource type; part of the composite primary key and FK to PA_RES_TYPES_B.
• LANGUAGE — The language code for this translation row; part of the primary key and FK to FND_LANGUAGES.
• SOURCE_LANG — The source language of the original translation; FK to FND_LANGUAGES, supporting MLS translation workflows.
• NAME — The translated display name of the resource type (e.g., "People," "Equipment").
• DESCRIPTION — The translated, free-text description of the resource type.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking who created and last modified the translation row and when.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (introduced in 12.2.x), preserving edition-aware reads.

The surrogate/business primary key is PA_RES_TYPES_TL_PK (RES_TYPE_ID, LANGUAGE). A unique index PA_RES_TYPES_TL_U1 (RES_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) is documented as a business-key candidate, extending the PK with the editioning column.

Common Use Cases and Queries

This table is primarily consumed to resolve resource type names into the user's language for reporting, LOVs, and integration extracts.

• Listing resource types in the current language:

  SELECT t.res_type_id, t.name, t.description
  FROM   pa_res_types_tl t
  WHERE  t.language = USERENV('LANG')
  AND    t.zd_edition_name = 'SET1';

• Joining base and translation tables:

  SELECT b.res_type_id, t.name
  FROM   pa_res_types_b b,
         pa_res_types_tl t
  WHERE  b.res_type_id = t.res_type_id
  AND    t.language = USERENV('LANG');

• Auditing translations across languages: query SOURCE_LANG to confirm which languages have been seeded or maintained.
• Reporting and ETL: resource type name is a common attribute in project expenditure and costing reports; extracts frequently join this table to convert codes into labels.

Related Objects

• PA_RES_TYPES_B — Base table holding language-independent resource type columns; join on RES_TYPE_ID.
• FND_LANGUAGES — Lookup for installed languages; referenced by LANGUAGE and SOURCE_LANG.
• PA_RES_TYPES_VL — The MLS view typically layered over the _B/_TL pair for simplified, language-aware access.
• PA_RES_TYPE_ASSIGNMENTS — Associates resource types with other Projects entities, depending on RES_TYPE_ID indirectly.
• PA_EXPENDITURES / PA_COST_DISTRIBUTION_LINES — Transactional tables where resource type identifiers are used and resolved to translated names in reporting.
• PA_RES_TYPES_TL_PK / PA_RES_TYPES_TL_U1 — Primary key and unique index enforcing row uniqueness per language and edition.