Search Results cs_party_roles_b_u1




Overview
Explore in AI Chat

Overview

CS.CS_PARTY_ROLES_B is the base definition table for party roles within the Oracle E-Business Suite Customer Service (CS) schema. It stores the master list of party role definitions used to categorize the relationship a party (person or organization) holds in a given business context, such as contact, customer contact, or resource. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the single source of truth for role codes before translation and mapping logic is applied through companion objects.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index, CS_PARTY_ROLES_B_U1, is housed separately in APPS_TS_TX_IDX. The documented physical schema contains 28 columns. Based on FK structure analysis, the metadata suggests a hub-leaning Data Vault classification: CS_PARTY_ROLES_B behaves as a hub because it holds a stable, unique business key (PARTY_ROLE_CODE) referenced by multiple dependent tables, with descriptive attributes that can be modeled as satellite data.

Key Information Stored

The most significant columns in CS_PARTY_ROLES_B are:

  • PARTY_ROLE_CODE — The short code uniquely identifying each party role; this is the documented primary key column and also the leading column of the unique index CS_PARTY_ROLES_B_U1.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — Define the effective date range during which the role is valid or active. These support date-effective querying and role lifecycle management.
  • SEEDED_FLAG — Indicates whether the role is seeded by Oracle (system-delivered) or user-defined, which is critical for upgrade and customization decisions.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control at the row level.
  • SORT_ORDER — Controls the display sequence in which party roles appear in lists and LOVs.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns used to capture extensible, client-specific attributes without schema changes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

In the documented 12.2.2 physical schema, a second unique index candidate includes ZD_EDITION_NAME alongside PARTY_ROLE_CODE, reflecting the editioning feature introduced for online patching. The primary surrogate identifier is PARTY_ROLE_CODE, while the business-key candidate is the combination captured by CS_PARTY_ROLES_B_U1.

Common Use Cases and Queries

Typical usage involves resolving active party roles for validation, LOV population, and reporting. A common pattern filters by effective dates and sort order:

  • Listing active roles: SELECT PARTY_ROLE_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE FROM CS.CS_PARTY_ROLES_B WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)+1) ORDER BY SORT_ORDER;
  • Identifying seeded versus custom roles: SELECT PARTY_ROLE_CODE, SEEDED_FLAG FROM CS.CS_PARTY_ROLES_B WHERE SEEDED_FLAG = 'N';
  • Joining to translations for display names: use PARTY_ROLE_CODE as the join key between CS_PARTY_ROLES_B and CS_PARTY_ROLES_TL.
  • Reporting role assignments: join CS_HZ_SR_CONTACT_POINTS or CS_PARTY_ROLE_GROUP_MAPS on PARTY_ROLE_CODE to aggregate usage by role.

Related Objects

Several objects depend on CS_PARTY_ROLES_B through the PARTY_ROLE_CODE join column:

  • CS.CS_PARTY_ROLES_TL — Translation table providing language-specific role names and descriptions; joined on PARTY_ROLE_CODE.
  • CS.CS_HZ_SR_CONTACT_POINTS — Stores service request contact points associated with a party role; references PARTY_ROLE_CODE.
  • CS.CS_PARTY_ROLE_GROUP_MAPS — Maps party roles into role groups; references PARTY_ROLE_CODE.

These relationships confirm the hub role of CS_PARTY_ROLES_B, with dependent tables supplying role attributes, translations, and grouping semantics.