Search Results cs_hz_sr_cp_pk

Overview

CS_HZ_SR_CONTACT_POINTS is a table owned by the CS (Service) schema in Oracle E-Business Suite and is documented as VALID in both 12.1.1 and 12.2.2. Its purpose is to store the contact points associated with a service request, effectively serving as the intersection between a service request (incident) and the parties and contact mechanisms through which the requester may be reached. Each row links a specific party to a specific incident and, optionally, to a particular contact point record in the Trading Community Architecture (TCA) model.

From a Data Vault modeling perspective, the metadata heuristic suggests a satellite-leaning classification. The table carries descriptive and state attributes (flags, active date ranges, audit columns) around the relationship between an incident and a party, rather than acting purely as a hub of unique business entities. Modelers should treat it as a candidate satellite or dependent link attached to the incident and party hubs when designing downstream analytical or integration models.

Key Information Stored

The table comprises 21 documented columns. The most significant are summarized below.

• SR_CONTACT_POINT_ID — The surrogate primary key of the table, backed by unique index CS_HZ_SR_CP_PK. A second unique index, CS_HZ_SR_CONTACT_POINTS_U2, is also defined on this column, reinforcing its role as the single-row identifier.
• PARTY_ID and INCIDENT_ID — Together these form the unique business key CS_HZ_SR_CONTACT_POINTS_UK1, meaning a given party may appear only once per service request. PARTY_ID references HZ_PARTIES, and INCIDENT_ID references CS_INCIDENTS_ALL_B.
• CONTACT_POINT_ID — References HZ_CONTACT_POINTS, identifying the specific TCA contact mechanism (for example, phone, email, or fax) recorded for the party on the service request.
• CONTACT_POINT_TYPE and CONTACT_TYPE — Classify the contact point and the nature of the contact relationship.
• PARTY_ROLE_CODE — References CS_PARTY_ROLES_B, describing the role the party plays relative to the incident, such as requester, owner, or affected party.
• PRIMARY_FLAG — Indicates whether the contact point is the primary one for the service request.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Define the active date window during which the contact point association is valid.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces multi-tenant data separation.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE capture standard EBS audit and program context.

Common Use Cases and Queries

This table is most frequently queried to retrieve the parties and contact methods attached to a service request, to identify the primary contact, and to reconcile service request activity with TCA contact data.

• Listing contacts for a given incident: SELECT p.party_id, p.contact_point_id, c.contact_point_type FROM cs_hz_sr_contact_points c, hz_parties p WHERE c.incident_id = :incident_id AND c.party_id = p.party_id;
• Identifying the primary contact for a service request using PRIMARY_FLAG and the active date window.
• Reporting on the roles played by parties across incidents by joining PARTY_ROLE_CODE to CS_PARTY_ROLES_B.
• Auditing changes over time through the companion audit table CS_HZ_SR_CONTACT_PNTS_AUDIT, which stores historical rows keyed by SR_CONTACT_POINT_ID.
• Determining the designated contact on the incident header via CS_INCIDENTS_ALL_B.PRIMARY_CONTACT_ID, which points back to this table.

Related Objects

The following objects are most significant in relation to CS_HZ_SR_CONTACT_POINTS.

• CS_INCIDENTS_ALL_B — Referenced through INCIDENT_ID, and it in turn references this table via PRIMARY_CONTACT_ID, forming a bidirectional relationship.
• HZ_PARTIES — Referenced through PARTY_ID, supplying party identity details.
• HZ_CONTACT_POINTS — Referenced through CONTACT_POINT_ID, providing the actual TCA contact mechanism.
• CS_PARTY_ROLES_B — Referenced through PARTY_ROLE_CODE, defining valid party roles.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for multi-tenant security.
• CS_HZ_SR_CONTACT_PNTS_AUDIT — The audit shadow table, keyed by SR_CONTACT_POINT_ID, capturing historical changes to contact point associations.