Search Results cs_party_role_groups_tl




Overview
Explore in AI Chat

Overview

CS_PARTY_ROLE_GROUPS_TL is a Multi-Lingual Support (MLS) translation table owned by the CS (Service) schema in Oracle E-Business Suite. It stores the translatable attributes—primarily the display name and description—of party role group definitions used by the Service module. Party role groups provide a mechanism to segment parties (customers, contacts, organizations) by the roles they play, enabling targeted service, warranty, and support processing. Because the table is MLS-enabled, one logical role group can be represented by multiple rows, one per installed language, keyed by PARTY_ROLE_GROUP_CODE and LANGUAGE.

Following a Data Vault modeling heuristic derived from its foreign key structure, this object is classified as satellite-leaning. It carries descriptive, language-dependent context that hangs off the base definition rather than introducing new business entities or relationships. The parent table CS_PARTY_ROLE_GROUPS_B holds the language-independent definition; CS_PARTY_ROLE_GROUPS_TL holds the language-dependent translation layer.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • PARTY_ROLE_GROUP_CODE — The business identifier for the role group; part of the primary key and the foreign key to CS_PARTY_ROLE_GROUPS_B.
  • LANGUAGE — The NLS language code of the row; part of the primary key and the discriminator that makes this an MLS table.
  • NAME — The translated display name of the party role group, shown to users in the selected language.
  • DESCRIPTION — The translated descriptive text for the role group.
  • SOURCE_LANG — The language in which the base record was originally created, used for MLS fallback behavior.
  • ZD_EDITION_NAME — The editioning column used in EBS 12.2 online patching; appears in both unique indexes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking insert and update metadata.

The surrogate/primary key is CS_PARTY_ROLE_GROUPS_TL_PK, defined on (PARTY_ROLE_GROUP_CODE, LANGUAGE). Two unique indexes act as business-key candidates: CS_PARTY_ROLE_GROUPS_TL_U1 on (PARTY_ROLE_GROUP_CODE, LANGUAGE, ZD_EDITION_NAME) and CS_PARTY_ROLE_GROUPS_TL_U2 on (NAME, LANGUAGE, ZD_EDITION_NAME). The U2 constraint supports the convention that a role group name is unique within a given language.

Common Use Cases and Queries

Typical usage retrieves translated role group names for reporting, LOV definition, or service configuration screens. A join to the base table is required to obtain language-independent attributes:

  • Retrieve names in a specific language: SELECT tl.name, tl.description FROM cs_party_role_groups_tl tl WHERE tl.language = USERENV('LANG') AND tl.party_role_group_code = :code;
  • Join base and translation: SELECT b.party_role_group_code, t.name FROM cs_party_role_groups_b b, cs_party_role_groups_tl t WHERE b.party_role_group_code = t.party_role_group_code AND t.language = 'US';
  • Audit languages available for a group: SELECT language FROM cs_party_role_groups_tl WHERE party_role_group_code = :code;
  • Reporting on translated role groups for a multi-language rollout, filtering by SOURCE_LANG to distinguish original vs. translated rows.

Because the table is MLS, direct DML is generally discouraged; use the EBS MLS APIs or the underlying setup forms so the base and translation rows stay synchronized.

Related Objects

The following objects are most significant to working with this table:

  • CS_PARTY_ROLE_GROUPS_B — The MLS base table; joined on PARTY_ROLE_GROUP_CODE. All language-independent attributes reside here.
  • CS_PARTY_ROLE_GROUPS_TL_PK — Primary key constraint on (PARTY_ROLE_GROUP_CODE, LANGUAGE).
  • CS_PARTY_ROLE_GROUPS_TL_U1 / U2 — Unique indexes supporting business-key uniqueness.
  • FND_LANGUAGES — Join on LANGUAGE to resolve language descriptions.
  • FND_TERRITORIES / NLS views — Supporting MLS metadata used to filter and display translations.
  • Service module party role setup forms — The UI layer that populates these tables through the CS product configuration flows.

Consult the ETRM and CS product documentation for the authoritative definition before extending or integrating against this table.