Search Results cs_party_roles_b

Overview

CS_PARTY_ROLES_B is the base definition table for party roles within the Oracle E-Business Suite Service (CS) module. It stores the seeded and user-defined role definitions that describe the function a party plays in a service context, such as contact, resource, or customer. The table resides in the CS schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. It is the master (or "header") record for each role, with translatable descriptive text held in the companion _TL table.

Under the heuristic Data Vault classification mined from the foreign-key topology, CS_PARTY_ROLES_B is a hub-leaning entity. It carries a stable business key (PARTY_ROLE_CODE) and is referenced by multiple dependent tables, which is the classic hub pattern: a central, non-transactional list of distinct business concepts that satellites and links attach to. Treating it as a hub is a modeling suggestion, not an EBS implementation detail.

Key Information Stored

The table is documented with 28 columns. The most significant are:

PARTY_ROLE_CODE — the business key and the column that forms the primary key CS_PARTY_ROLES_B_PK. It uniquely identifies each party role definition.
ZD_EDITION_NAME — part of the unique business-key index CS_PARTY_ROLES_B_U1 on (PARTY_ROLE_CODE, ZD_EDITION_NAME), supporting edition-based redefinition / multi-tenant data.
START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating columns controlling when a role is valid and active.
SEEDED_FLAG — indicates whether the role is Oracle-seeded or customer-defined, essential when protecting delivered setup.
SORT_ORDER — controls display sequence in list of values and pickers.
OBJECT_VERSION_NUMBER — optimistic-locking column used by the OAF/ADF layer for concurrent update protection.
ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS DFF (Descriptive Flexfield) container columns for extensibility.
CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance.

Only PARTY_ROLE_CODE functions as the surrogate primary key; the unique index adds ZD_EDITION_NAME as a second business-key component.

Common Use Cases and Queries

Typical uses include LOV/picker population, validation of role codes on transaction entry, and reporting on which roles exist and are active. A representative query returns active, non-seeded roles:

SELECT party_role_code, seeded_flag, start_date_active, end_date_active FROM cs.cs_party_roles_b WHERE seeded_flag = 'N' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
Joining to the translatable table to obtain display names: SELECT b.party_role_code, t.role_name FROM cs.cs_party_roles_b b, cs.cs_party_roles_tl t WHERE b.party_role_code = t.party_role_code AND t.language = USERENV('LANG');
Checking where a role is used: join to CS_HZ_SR_CONTACT_POINTS and CS_PARTY_ROLE_GROUP_MAPS on PARTY_ROLE_CODE to trace dependent setup before deletion.

Reporting often groups by SEEDED_FLAG and SORT_ORDER to present an ordered catalog of available roles.

Related Objects

The FK metadata identifies the following key dependents that reference CS_PARTY_ROLES_B via PARTY_ROLE_CODE:

CS_PARTY_ROLES_TL — the translatable (translation) child holding language-specific role text; joined on PARTY_ROLE_CODE.
CS_HZ_SR_CONTACT_POINTS — service-request contact points that reference a party role; joined on PARTY_ROLE_CODE.
CS_PARTY_ROLE_GROUP_MAPS — maps party roles into role groups; joined on PARTY_ROLE_CODE.
The primary-key index CS_PARTY_ROLES_B_PK and unique index CS_PARTY_ROLES_B_U1.

These relationships confirm the hub role of the table, with transaction-oriented and translation satellites converging on the single PARTY_ROLE_CODE key.

Table: CS_PARTY_ROLES_B 12.1.1
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_B, object_name:CS_PARTY_ROLES_B, status:VALID, product: CS - Service , description: This is the base table for storing all the party role definitions. , implementation_dba_data: CS.CS_PARTY_ROLES_B ,
Table: CS_PARTY_ROLES_B 12.2.2
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_B, object_name:CS_PARTY_ROLES_B, status:VALID, product: CS - Service , description: This is the base table for storing all the party role definitions. , implementation_dba_data: CS.CS_PARTY_ROLES_B ,
VIEW: CS.CS_PARTY_ROLES_B# 12.2.2
owner:CS, object_type:VIEW, object_name:CS_PARTY_ROLES_B#, status:VALID,
TRIGGER: APPS.CS_PARTY_ROLES_B+ 12.2.2
VIEW: APPS.CS_PARTY_ROLES_VL 12.1.1
TRIGGER: APPS.CS_PARTY_ROLES_B+ 12.2.2
owner:APPS, object_type:TRIGGER, object_name:CS_PARTY_ROLES_B+, status:VALID,
SYNONYM: APPS.CS_PARTY_ROLES_B 12.1.1
owner:APPS, object_type:SYNONYM, object_name:CS_PARTY_ROLES_B, status:VALID,
SYNONYM: APPS.CS_PARTY_ROLES_B 12.2.2
owner:APPS, object_type:SYNONYM, object_name:CS_PARTY_ROLES_B, status:VALID,
VIEW: APPS.CS_PARTY_ROLES_VL 12.2.2
View: CS_PARTY_ROLES_VL 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_PARTY_ROLES_VL, object_name:CS_PARTY_ROLES_VL, status:VALID, product: CS - Service , description: This is a _VL view. This view is based on table cs_party_roles_b and _tl table. , implementation_dba_data: APPS.CS_PARTY_ROLES_VL ,
View: CS_PARTY_ROLES_VL 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_PARTY_ROLES_VL, object_name:CS_PARTY_ROLES_VL, status:VALID, product: CS - Service , description: This is a _VL view. This view is based on table cs_party_roles_b and _tl table. , implementation_dba_data: APPS.CS_PARTY_ROLES_VL ,
FUNCTION: APPS.CS_PARTY_ROLES_B= 12.2.2
APPS.CS_PARTY_ROLES_PKG SQL Statements 12.2.2
APPS.CS_PARTY_ROLES_PKG SQL Statements 12.1.1
VIEW: CS.CS_PARTY_ROLES_B# 12.2.2
Table: CS_PARTY_ROLE_GROUP_MAPS 12.2.2
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLE_GROUP_MAPS, object_name:CS_PARTY_ROLE_GROUP_MAPS, status:VALID, product: CS - Service , description: This table stores mappings between Party Role Groups and Party Roles. , implementation_dba_data: CS.CS_PARTY_ROLE_GROUP_MAPS ,
Table: CS_PARTY_ROLES_TL 12.1.1
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_TL, object_name:CS_PARTY_ROLES_TL, status:VALID, product: CS - Service , description: This is a MLS table and stores party roles definition. , implementation_dba_data: CS.CS_PARTY_ROLES_TL ,
Table: CS_PARTY_ROLES_TL 12.2.2
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_TL, object_name:CS_PARTY_ROLES_TL, status:VALID, product: CS - Service , description: This is a MLS table and stores party roles definition. , implementation_dba_data: CS.CS_PARTY_ROLES_TL ,
Table: CS_PARTY_ROLE_GROUP_MAPS 12.1.1
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLE_GROUP_MAPS, object_name:CS_PARTY_ROLE_GROUP_MAPS, status:VALID, product: CS - Service , description: This table stores mappings between Party Role Groups and Party Roles. , implementation_dba_data: CS.CS_PARTY_ROLE_GROUP_MAPS ,
PACKAGE BODY: APPS.CS_PARTY_ROLES_PKG 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CS_PARTY_ROLES_PKG, status:VALID,
Table: CS_HZ_SR_CONTACT_POINTS 12.1.1
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_HZ_SR_CONTACT_POINTS, object_name:CS_HZ_SR_CONTACT_POINTS, status:VALID, product: CS - Service , description: This table stores contact points for a service requests. , implementation_dba_data: CS.CS_HZ_SR_CONTACT_POINTS ,
PACKAGE BODY: APPS.CS_PARTY_ROLES_PKG 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CS_PARTY_ROLES_PKG, status:VALID,
FUNCTION: APPS.CS_PARTY_ROLES_B= 12.2.2
owner:APPS, object_type:FUNCTION, object_name:CS_PARTY_ROLES_B=, status:VALID,
TABLE: CS.CS_PARTY_ROLES_B 12.1.1
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_B, object_name:CS_PARTY_ROLES_B, status:VALID,
TABLE: CS.CS_PARTY_ROLES_B 12.2.2
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_PARTY_ROLES_B, object_name:CS_PARTY_ROLES_B, status:VALID,
VIEW: APPS.CS_PARTY_ROLES_VL 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_PARTY_ROLES_VL, object_name:CS_PARTY_ROLES_VL, status:VALID,
Table: CS_HZ_SR_CONTACT_POINTS 12.2.2
owner:CS, object_type:TABLE, fnd_design_data:CS.CS_HZ_SR_CONTACT_POINTS, object_name:CS_HZ_SR_CONTACT_POINTS, status:VALID, product: CS - Service , description: This table stores contact points for a service requests. , implementation_dba_data: CS.CS_HZ_SR_CONTACT_POINTS ,
12.2.2 DBA Data 12.2.2
VIEW: APPS.CS_PARTY_ROLES_VL 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_PARTY_ROLES_VL, object_name:CS_PARTY_ROLES_VL, status:VALID,
12.2.2 DBA Data 12.2.2
PACKAGE BODY: APPS.CS_PARTY_ROLES_PKG 12.1.1
PACKAGE BODY: APPS.CS_PARTY_ROLES_PKG 12.2.2
PACKAGE BODY: APPS.CS_SERVICEREQUEST_UTIL 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CS_SERVICEREQUEST_UTIL, status:VALID,
PACKAGE BODY: APPS.CS_SERVICEREQUEST_UTIL 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CS_SERVICEREQUEST_UTIL, status:VALID,
12.2.2 FND Design Data 12.2.2
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
12.1.1 FND Design Data 12.1.1
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
APPS.CS_PARTY_ROLES_PKG dependencies on CS_PARTY_ROLES_B 12.1.1
APPS.CS_SERVICEREQUEST_UTIL dependencies on CS_PARTY_ROLES_B 12.1.1
APPS.CS_SERVICEREQUEST_UTIL dependencies on CS_PARTY_ROLES_B 12.2.2
APPS.CS_PARTY_ROLES_PKG dependencies on CS_PARTY_ROLES_B 12.2.2
eTRM - CS Tables and Views 12.2.2
eTRM - CS Tables and Views 12.1.1
description: Table to store web conference details for an SR. ,