Search Results cs_party_role_groups_b




Overview
Explore in AI Chat

Overview

CS_PARTY_ROLE_GROUPS_B is the base table in the Service (CS) module of Oracle E-Business Suite that stores the master definitions of party role groups. A party role group is a named grouping of party roles (for example, roles such as customer contact, resource, or vendor contact) that can be reused throughout Service functionality, including field service dispatch, resource assignment, and contact management. The "_B" suffix indicates that this is the base (language-independent) table in a translated pair, meaning that the descriptive, user-facing text for each group is held in a corresponding "_TL" table keyed by language.

The table resides in the CS schema and is present in both EBS 12.1.1 and 12.2.2. The documented physical schema for 12.2.2 lists 28 columns and a unique business-key index, CS_PARTY_ROLE_GROUPS_B_U1, on PARTY_ROLE_GROUP_CODE and ZD_EDITION_NAME. The single-column primary key constraint, CS_PARTY_ROLE_GROUPS_B_PK, is defined on PARTY_ROLE_GROUP_CODE. Heuristic Data Vault classification of this object is hub-leaning: the stable business key PARTY_ROLE_GROUP_CODE and the absence of dependent descriptive attributes suggest modeling it as a hub, with descriptive data flowing to the satellite-style _TL table.

Key Information Stored

The most significant columns in this table are:

  • PARTY_ROLE_GROUP_CODE — the business key and primary key value that uniquely identifies each party role group definition. It is also the join column to the translation and mapping tables.
  • ZD_EDITION_NAME — the edition indicator used by Oracle's edition-based redefinition (EBR) architecture, forming part of the unique index CS_PARTY_ROLE_GROUPS_B_U1 alongside the group code.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating that controls whether a group definition is currently usable.
  • SEEDED_FLAG — identifies Oracle-delivered (seeded) groups versus user-defined groups.
  • SORT_ORDER — controls the display sequence of groups in Service UI list-of-values and pickers.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying AOL/BC4J framework to detect concurrent updates.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing who created and last modified each row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) columns available for customer-specific extension of the group definition.

The surrogate primary key is therefore the PARTY_ROLE_GROUP_CODE constraint, while the date-effective versioning key is the composite of PARTY_ROLE_GROUP_CODE and ZD_EDITION_NAME.

Common Use Cases and Queries

Typical reporting and integration scenarios include:

  • Listing all currently active party role groups for use in setup or LOV population:
SELECT prg.party_role_group_code, prg.sort_order, prg.seeded_flag
FROM   cs.cs_party_role_groups_b prg
WHERE  SYSDATE BETWEEN NVL(prg.start_date_active, SYSDATE)
                   AND NVL(prg.end_date_active, SYSDATE)
ORDER  BY prg.sort_order;
  • Joining to the translation table to retrieve the user-visible name for a given language:
SELECT b.party_role_group_code, t.party_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');
  • Auditing seeded versus user-defined groups via SEEDED_FLAG, or reviewing DFF values stored in ATTRIBUTE1 through ATTRIBUTE15.
  • Validating that every group has at least one role mapping in CS_PARTY_ROLE_GROUP_MAPS as a data-quality check.

Related Objects

Two documented foreign keys reference this table:

  • CS_PARTY_ROLE_GROUPS_TL — the translated table storing the language-specific group name and description; joined on CS_PARTY_ROLE_GROUPS_TL.PARTY_ROLE_GROUP_CODE = CS_PARTY_ROLE_GROUPS_B.PARTY_ROLE_GROUP_CODE.
  • CS_PARTY_ROLE_GROUP_MAPS — the mapping table that links each group to its constituent party roles; joined on CS_PARTY_ROLE_GROUP_MAPS.PARTY_ROLE_GROUP_CODE = CS_PARTY_ROLE_GROUPS_B.PARTY_ROLE_GROUP_CODE.

In practice these objects are referenced alongside the Service role and resource tables, and are typically administered through the Service setup and party role group maintenance windows rather than through direct DML. Because of the EBR column ZD_EDITION_NAME, queries should account for edition context when running against 12.2.x online patching environments.