Search Results pa_project_role_types_tl_u2




Overview
Explore in AI Chat

Overview

PA.PA_PROJECT_ROLE_TYPES_TL is the multi-lingual support (MLS) table for project role types defined in Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, MLS architecture separates language-independent attributes from translatable text. The base table, PA_PROJECT_ROLE_TYPES, stores the role identifier and non-translatable attributes, while PA_PROJECT_ROLE_TYPES_TL stores the user-facing name (MEANING) and description (DESCRIPTION) for each installed language. This design allows a single role type to be presented in the session language of any user without duplicating the underlying business entity.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its unique indexes reside in APPS_TS_TX_IDX. From a dimensional modeling perspective, the mined relationship structure classifies this object as a standalone table (no foreign keys are documented as outgoing references from the TL table itself, though PROJECT_ROLE_ID logically maps to the base table). In Data Vault terms, this would be modeled as a satellite hanging off the PA_PROJECT_ROLE_TYPES hub, carrying the descriptive, language-dependent attributes.

Key Information Stored

The primary key of the table is the combination of PROJECT_ROLE_ID and LANGUAGE. Documented unique indexes define two business-key candidates, both including ZD_EDITION_NAME in 12.2.2:

  • PA_PROJECT_ROLE_TYPES_TL_U1 — unique on (PROJECT_ROLE_ID, LANGUAGE, ZD_EDITION_NAME); the surrogate-to-language lookup key.
  • PA_PROJECT_ROLE_TYPES_TL_U2 — unique on (MEANING, LANGUAGE, ZD_EDITION_NAME); enforces that a role name is unique within a given language and edition. This is the index referenced by the user's search term pa_project_role_types_tl_u2.

The most significant columns are:

  • PROJECT_ROLE_ID — system-generated number uniquely identifying the project role type; joins to the base table.
  • LANGUAGE — the language code for the translated row.
  • SOURCE_LANG — the language in which the row was originally entered, used by MLS to determine translation status.
  • MEANING — the 80-character user-defined name that uniquely identifies the role type within a language.
  • DESCRIPTION — a 250-character free-text description of the role type.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ZD_EDITION_NAME — the edition discriminator supporting Online Patching in 12.2.2.

Common Use Cases and Queries

Typical uses include validating that a role type has been translated into the required languages, exporting role names for reporting in a specific locale, and confirming uniqueness of MEANING per language. A representative query joining the base and translation tables is:

  • SELECT b.project_role_id, t.meaning, t.description, t.language FROM pa.pa_project_role_types b, pa.pa_project_role_types_tl t WHERE b.project_role_id = t.project_role_id AND t.language = USERENV('LANG') AND t.source_lang = USERENV('LANG');
  • To audit missing translations: filter rows where SOURCE_LANG <> LANGUAGE, or use the MLS views to list rows lacking a translation for a target language.
  • To troubleshoot U2 uniqueness violations, query by MEANING and LANGUAGE to detect duplicate role names before defining a new role type.

Related Objects

The principal related objects, based on the documented relationship data, are:

  • PA.PA_PROJECT_ROLE_TYPES — the base (non-translated) table; joined on PROJECT_ROLE_ID.
  • PA_PROJECT_ROLE_TYPES_TL (APPS synonym) — the APPS-layer synonym used by concurrent programs and forms.
  • MLS views such as PA_PROJECT_ROLE_TYPES_VL — the language-joined view exposing base and translated columns for the current session language.
  • Role assignment and resource tables in Oracle Projects that reference project roles by PROJECT_ROLE_ID.
  • Standard MLS infrastructure objects (_TL pattern) shared across Oracle Applications for multi-language lookups.