Search Results cs_party_role_group_maps_u1

Overview

CS.CS_PARTY_ROLE_GROUP_MAPS is a reference and relationship table in the Oracle E-Business Suite Customer Service (CS) schema. It stores the mappings between Party Role Groups and Party Roles, allowing the application to associate an individual party role (for example, a specific role such as contact or resource) with a broader grouping of roles used for role-based processing, routing, and security. The table resides in the APPS_TS_TX_DATA tablespace in Oracle EBS 12.1.1 and 12.2.2, and its design data is registered under FND Design Data CS.CS_PARTY_ROLE_GROUP_MAPS.

Under a heuristic Data Vault classification derived from its foreign key structure, this table behaves as a link. It connects two business entities — the party role group and the party role — and carries its own mapping attributes such as active dates, seeded flag, and edition name. Modeling it as a link table is a reasonable suggestion because it resolves a many-to-many relationship between the group and role dimensions and records the temporal validity of each association.

Key Information Stored

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

• PARTY_ROLE_GROUP_MAPPING_ID — Numeric surrogate primary key for the mapping record. It is the sole column of the CS_PARTY_ROLE_GROUP_MAPS_U1 unique index along with ZD_EDITION_NAME, and forms the basis of the CS_PARTY_ROLE_GROUP_MAPS_PK constraint.
• PARTY_ROLE_GROUP_CODE — Identifier for the party role group. It participates in the business-key candidate CS_PARTY_ROLE_GROUP_MAPS_U2 and is a foreign key reference to CS_PARTY_ROLE_GROUPS_B.
• PARTY_ROLE_CODE — Identifier for the party role. Together with PARTY_ROLE_GROUP_CODE and ZD_EDITION_NAME it forms the U2 unique index, and it references CS_PARTY_ROLES_B.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Date range during which the party role mapping is active or inactive, supporting effective-dated lookups.
• SEEDED_FLAG — Indicates whether the mapping was delivered as seed data by Oracle or created by the customer.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• ZD_EDITION_NAME — Edition identifier supporting the EBS 12.2 online patching and editioning model; it appears in both unique indexes.
• The standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture row creation and modification metadata.

Common Use Cases and Queries

Typical uses include resolving which roles belong to a given party role group, determining whether a mapping is currently active, and reporting seeded versus customer-defined mappings. The following query returns all active roles for a specified group:

• SELECT party_role_code FROM cs.cs_party_role_group_maps WHERE party_role_group_code = :group_code AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

To join mappings with their parent role and group definitions for a reporting view, the pattern typically combines the two foreign keys with CS_PARTY_ROLES_B and CS_PARTY_ROLE_GROUPS_B. Filtering by SEEDED_FLAG is useful when auditing customer extensions versus Oracle-provided seed data, and filtering by ZD_EDITION_NAME is important in 12.2 run-time and patch editions to avoid reading data from the wrong edition.

Related Objects

The table is directly referenced or linked by the following significant objects:

• CS_PARTY_ROLES_B — joined via PARTY_ROLE_CODE; holds the party role definition.
• CS_PARTY_ROLE_GROUPS_B — joined via PARTY_ROLE_GROUP_CODE; holds the party role group definition.
• CS_PARTY_ROLE_GROUP_MAPS# — the editioning/trigger-related companion object within the CS schema that references this table.
• CS_PARTY_ROLE_GROUP_MAPS_PK — primary key constraint on PARTY_ROLE_GROUP_MAPPING_ID.
• CS_PARTY_ROLE_GROUP_MAPS_U1 and CS_PARTY_ROLE_GROUP_MAPS_U2 — unique indexes enforcing surrogate and business-key uniqueness respectively.

The table does not reference any database objects outside those listed in its foreign key definitions, and no other external object dependencies are documented beyond the CS schema companion object.