Search Results cs_party_role_groups_tl_u2

Overview

CS.CS_PARTY_ROLE_GROUPS_TL is the translation (Multi-Lingual Support, MLS) table for the CS_PARTY_ROLE_GROUPS entity within the Oracle E-Business Suite Customer Service (CS) schema. It stores the language-dependent attributes of party role group definitions, while the corresponding base table, CS_PARTY_ROLE_GROUPS_B, holds language-independent columns. In Oracle EBS 12.1.1 and 12.2.2, every MLS-enabled entity is implemented as a _B/_TL pair, and this table conforms to that pattern.

From a Data Vault modeling perspective, the table is classified as satellite-leaning. This is a heuristic suggestion: the table carries descriptive, language-specific attributes keyed by a code and language, which is characteristic of a satellite attached to a hub or link. Analytical models that reconstruct a Data Vault should treat CS_PARTY_ROLE_GROUPS_TL as a descriptive satellite dependent on PARTY_ROLE_GROUP_CODE, not as an independent hub or link.

Key Information Stored

The table is defined in the ETRM 12.2.2 metadata with eleven columns. The most significant are listed below.

• PARTY_ROLE_GROUP_CODE VARCHAR2(30) — the short code uniquely identifying the party role group. It is the business key carried into the translation table.
• LANGUAGE VARCHAR2 — the language of the translated row. Together with PARTY_ROLE_GROUP_CODE this forms the primary key CS_PARTY_ROLE_GROUPS_TL_PK.
• NAME VARCHAR2(90) — the translated display name of the party role group.
• DESCRIPTION VARCHAR2(720) — the translated descriptive text for the group.
• SOURCE_LANG VARCHAR2 — the source language from which the translation originated, used by the MLS infrastructure.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns maintained by the EBS framework.
• ZD_EDITION_NAME — the editioning column present in 12.2.x, supporting the Edition-Based Redefinition (EBR) online patching architecture.

The surrogate primary key is the composite (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 user search term "cs_party_role_groups_tl_u1" corresponds directly to the U1 unique index, which enforces uniqueness on the code and language combination (edition-aware in 12.2.2).

Common Use Cases and Queries

This table is queried primarily for multi-lingual reporting and for validating translated role group names. A common pattern is to join the translation table back to the base table to retrieve both language-independent and language-specific attributes for a target language.

• Listing translated role groups for a specific language: SELECT PARTY_ROLE_GROUP_CODE, NAME, DESCRIPTION FROM CS.CS_PARTY_ROLE_GROUPS_TL WHERE LANGUAGE = 'US';
• Validating business-key integrity against the U1 index columns (PARTY_ROLE_GROUP_CODE, LANGUAGE, ZD_EDITION_NAME).
• Reconciling base-to-translation completeness by comparing row counts in CS_PARTY_ROLE_GROUPS_B and CS_PARTY_ROLE_GROUPS_TL grouped by LANGUAGE.
• Feeding downstream localization or data-warehouse extract processes where role group labels must appear in the user's session language.

Related Objects

The translation table depends on and is referenced by the following significant objects.

• CS.CS_PARTY_ROLE_GROUPS_B — the base table; PARTY_ROLE_GROUP_CODE is the foreign key from CS_PARTY_ROLE_GROUPS_TL.PARTY_ROLE_GROUP_CODE referencing CS_PARTY_ROLE_GROUPS_B.PARTY_ROLE_GROUP_CODE.
• APPS.CS_PARTY_ROLE_GROUPS_TL — the APPS synonym through which the table is normally accessed.
• CS_PARTY_ROLE_GROUPS_TL_U1 and CS_PARTY_ROLE_GROUPS_TL_U2 — the unique indexes enforcing code/language and name/language uniqueness.
• CS_PARTY_ROLE_GROUPS_TL_PK — the primary key constraint on (PARTY_ROLE_GROUP_CODE, LANGUAGE).

The table is classified VALID and resides in the APPS_TS_TX_DATA tablespace; its indexes are stored in APPS_TS_TX_IDX.