Search Results cs_party_roles_tl




Overview
Explore in AI Chat

Overview

CS_PARTY_ROLES_TL is a translated (multi-language support, MLS) table in the CS (Service) product module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific descriptive attributes of party role definitions used throughout Oracle Service and its dependent modules. The table is owned by the CS schema and is documented as VALID in the ETRM repository.

In Oracle EBS, party roles describe the capacities in which a party (person, organization, or group) can participate in a service, support, or transactional relationship — for example, "Customer," "Contact," or "Service Provider." The base definition of each role resides in CS_PARTY_ROLES_B, while CS_PARTY_ROLES_TL holds the translatable text (name and description) corresponding to each installed language. This separation follows the standard EBS MLS pattern: a "_B" table for language-independent rows and a "_TL" table for language-dependent rows.

From a Data Vault modeling perspective, the metadata's FK structure suggests a satellite-leaning classification. The presence of a foreign key from PARTY_ROLE_CODE to CS_PARTY_ROLES_B, combined with the composite primary key of PARTY_ROLE_CODE and LANGUAGE, is consistent with a satellite attached to a hub-like business entity rather than an independent hub or a link.

Key Information Stored

The table's documented schema contains 11 columns, of which the following are the most operationally significant:

  • PARTY_ROLE_CODE — The language-independent business identifier of the role. It forms part of the primary key and is the foreign key pointing to CS_PARTY_ROLES_B.
  • LANGUAGE — The language code for the translated row. Together with PARTY_ROLE_CODE it constitutes the composite primary key CS_PARTY_ROLES_TL_PK.
  • NAME — The translated, user-visible name of the party role. Note that NAME participates in the unique index CS_PARTY_ROLES_TL_U2, making it a business-key candidate alongside LANGUAGE and ZD_EDITION_NAME.
  • DESCRIPTION — The translated long description of the party role, used in setup and reference screens.
  • SOURCE_LANG — Identifies the language from which the row was originally entered or derived; standard in MLS translation workflows.
  • ZD_EDITION_NAME — The edition identifier used by Oracle's edition-based redefinition (EBR) framework, present in both unique indexes: CS_PARTY_ROLES_TL_U1 (PARTY_ROLE_CODE, LANGUAGE, ZD_EDITION_NAME) and CS_PARTY_ROLES_TL_U2 (NAME, LANGUAGE, ZD_EDITION_NAME).
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns that track row creation and modification, essential for reconciliation and audit reporting.

The surrogate primary key is the composite (PARTY_ROLE_CODE, LANGUAGE); the documented business-key candidates are CS_PARTY_ROLES_TL_U1 on (PARTY_ROLE_CODE, LANGUAGE, ZD_EDITION_NAME) and CS_PARTY_ROLES_TL_U2 on (NAME, LANGUAGE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage centers on lookup and validation of role descriptions in a specific language. A conventional query pattern joins the translated row to its base row and filters by language:

  • SELECT b.PARTY_ROLE_CODE, t.NAME, t.DESCRIPTION FROM CS_PARTY_ROLES_B b, CS_PARTY_ROLES_TL t WHERE b.PARTY_ROLE_CODE = t.PARTY_ROLE_CODE AND t.LANGUAGE = USERENV('LANG');
  • Reporting usage validates that every base role has a translation for each required language — a NOT EXISTS query against CS_PARTY_ROLES_TL identifies missing translations.
  • Setup and administration screens use these rows to populate LOVs and role-selection lists.
  • EBR-aware queries should include ZD_EDITION_NAME predicates when running against 12.2.x environments.

Related Objects

  • CS_PARTY_ROLES_B — The base (non-translated) table. Joined on CS_PARTY_ROLES_TL.PARTY_ROLE_CODE = CS_PARTY_ROLES_B.PARTY_ROLE_CODE; this is the documented foreign-key relationship.
  • CS_PARTY_ROLES — The runtime/denormalized view or table that typically presents the joined base and translation data to application code.
  • CS_PARTY_ROLES_TL_PK / CS_PARTY_ROLES_TL_U1 / CS_PARTY_ROLES_TL_U2 — The documented primary key and unique indexes that enforce uniqueness and support lookups.
  • HZ_PARTIES and related HZ_* party tables — Consume party role codes when defining which role a party plays in a service context.
  • Oracle Service (CS) setup and role-assignment screens — Depend on this table for translated role labels.