Search Results pa_project_role_types_tl




Overview
Explore in AI Chat

Overview

PA_PROJECT_ROLE_TYPES_TL is the multi-lingual support (MLS) translation table for project role types defined in Oracle Projects. In an Oracle E-Business Suite 12.1.1 or 12.2.2 environment, it stores the language-specific display text — the translatable meaning and description — associated with each project role type, while the base table PA_PROJECT_ROLE_TYPES holds the language-independent definition. This separation allows a single role type record to be rendered in any installed language, enabling users to define, store, and print project role data in multiple languages within the same instance.

The object resides in the PA (Projects) schema and is documented as VALID in the ETRM 12.2.2 metadata, with eleven columns. From a data-modeling perspective, the mined foreign-key structure classifies this object as standalone. Heuristically, that suggests it is best treated as a satellite of PA_PROJECT_ROLE_TYPES rather than an independent hub: its rows are descriptive attributes attached to a parent role type entity, not an entity in its own right and not a many-to-many association between two entities.

Key Information Stored

The table's surrogate identity and foreign-key linkage to the base table is carried by PROJECT_ROLE_ID, which is documented as referencing PA_PROJECT_ROLE_TYPES. Two unique indexes define the business-key candidates:

  • PROJECT_ROLE_ID, LANGUAGE, ZD_EDITION_NAME — the unique index PA_PROJECT_ROLE_TYPES_TL_U1. This enumerates each role type once per language per edition, confirming the table's role as a language-keyed satellite.
  • MEANING, LANGUAGE, ZD_EDITION_NAME — the unique index PA_PROJECT_ROLE_TYPES_TL_U2. This guarantees that a given translated meaning is unique within a language and edition, which is important for list-of-values and lookup behavior.

The principal descriptive columns are MEANING, which holds the translated, user-facing name of the role type, and DESCRIPTION, which holds the translated long description. LANGUAGE identifies the installed language of the row, and SOURCE_LANG records the language in which the record was originally entered, which drives the MLS translation workflow (whether a row is a source record or a translated copy). ZD_EDITION_NAME supports edition-based data management. The remaining columns are the standard Oracle EBS WHO/audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most common access pattern is a join to the base table filtered by a specific language, typically the session or reporting language, when populating a role-type lookup or an LOV. A typical query pattern is:

  • SELECT t.project_role_id, t.meaning FROM pa_project_role_types_tl t WHERE t.language = USERENV('LANG') (or a literal such as 'US').
  • Translation completeness reporting: compare counts of rows per LANGUAGE to detect role types that have not yet been translated.
  • Source-language auditing: filter WHERE language <> source_lang to isolate translated rows and review translation quality or stale text.
  • Reporting on project role assignments and staffing where the role name must appear in a specific language for a multilingual user base.

Related Objects

  • PA_PROJECT_ROLE_TYPES — the base (non-translated) table; joined on PROJECT_ROLE_ID (documented FK). This is the primary parent.
  • PA_PROJECT_ROLE_TYPES_TL joins to assignment and staffing tables that carry PROJECT_ROLE_ID when role names must be resolved for display.
  • Project role/team assignment tables and project resource management views that reference project roles.
  • Oracle Projects concurrent programs and the Project Role Types setup form, which read and write the MLS rows.
  • Standard WHO/audit and edition-based management objects (ZD_EDITION_NAME) that govern the row set.

Practically, all queries that need human-readable role text should join this table to PA_PROJECT_ROLE_TYPES on PROJECT_ROLE_ID and constrain by LANGUAGE.