Search Results cs_party_role_groups_b_u1




Overview

CS.CS_PARTY_ROLE_GROUPS_B is the base definition table within the Customer Service (CS) schema that stores all party role group definitions used in Oracle E-Business Suite. A party role group is a logical grouping of one or more party roles (such as customer, contact, or prospect) that allows application modules to treat a set of roles as a single unit for business rules, security, and presentation purposes. Records in this table establish the identity, active lifecycle window, and display ordering of each role group, and are subsequently mapped to individual roles through the CS_PARTY_ROLE_GROUP_MAPS child table and translated through CS_PARTY_ROLE_GROUPS_TL.

The physical schema resides in the APPS_TS_TX_DATA tablespace with indexes in APPS_TS_TX_IDX. In Release 12.2.2, the table carries a Zone/Data Vault editioning artifact (ZD_EDITION_NAME) and is classified heuristically as hub-leaning in a Data Vault model, meaning it functions primarily as a durable business-key hub of party role group identity, with descriptive attributes distributed across dependent link and satellite structures.

Key Information Stored

The table contains 28 documented columns. The most significant include:

The primary key is CS_PARTY_ROLE_GROUPS_B_PK on PARTY_ROLE_GROUP_CODE. The unique index referenced by the user's search, CS_PARTY_ROLE_GROUPS_B_U1, is documented in the 12.2.2 schema on (PARTY_ROLE_GROUP_CODE, ZD_EDITION_NAME), reflecting the editioning requirement. In the 12.1.1 representation the same logical uniqueness applies to PARTY_ROLE_GROUP_CODE alone.

Common Use Cases and Queries

Typical usage involves validating the active status of a role group, resolving a role group's display order, and joining to the mapping and translation tables for reporting.

Sample query to list active groups in display order:

  • SELECT party_role_group_code, start_date_active, end_date_active, sort_order FROM cs.cs_party_role_groups_b WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1) ORDER BY sort_order;

Sample query to resolve a group's mapped roles using the child mapping table:

  • SELECT b.party_role_group_code, m.party_role_code FROM cs.cs_party_role_groups_b b, cs.cs_party_role_group_maps m WHERE b.party_role_group_code = m.party_role_group_code;

Sample query to retrieve the translated display name:

  • SELECT b.party_role_group_code, t.role_group_name FROM cs.cs_party_role_groups_b b, cs.cs_party_role_groups_tl t WHERE b.party_role_group_code = t.party_role_group_code AND t.language = USERENV('LANG');

These patterns are commonly used in Customer Service setup reports, security definition extracts, and data migration validation scripts.

Related Objects

The following objects depend on or reference CS_PARTY_ROLE_GROUPS_B:

  • CS.CS_PARTY_ROLE_GROUPS_TL — translation table joining on PARTY_ROLE_GROUP_CODE; stores language-specific role group names and descriptions.
  • CS.CS_PARTY_ROLE_GROUP_MAPS — child mapping table joining on PARTY_ROLE_GROUP_CODE; links each group to its constituent party roles.
  • CS.CS_PARTY_ROLE_GROUPS_B_PK — the primary key constraint enforcing unique group codes.
  • CS.CS_PARTY_ROLE_GROUPS_B_U1 — the unique index on PARTY_ROLE_GROUP_CODE (and ZD_EDITION_NAME in R12.2.2).
  • CS.CS_PARTY_ROLE_GROUPS_B DFF definitions — registered through FND design data (CS.CS_PARTY_ROLE_GROUPS_B) for the ATTRIBUTE flexfield columns.

Together these objects form the party role group foundation used by Customer Service, Trade Management, and related modules for role-based grouping and eligibility logic.