Search Results cs_sr_hz_cust_cont_v




Overview
Explore in AI Chat

Overview

The CS_SR_HZ_CUST_CONT_V view is a Service (CS) module database object owned by the APPS schema. Its stated purpose in Oracle E-Business Suite is to list all customer contacts whose party types are PARTY_RELATIONSHIP and PERSON. Because it consolidates contact identities drawn from the Trading Community Architecture (TCA) registry into a single, Service-friendly result set, the view is typically consumed by Service Request (SR) contact selection, notification, and customer-interaction features, as well as by custom reports and integrations that require a normalized list of contactable parties.

The object is recorded with status VALID in both the 12.1.1 and 12.2.2 environments, and its documented metadata applies to 12.2.2. Its definition uses a UNION ALL of two query blocks to cover direct person contacts and contacts that exist only through a party relationship. This dual-path construction is the key structural fact about the view and explains why it surfaces both PERSON and PARTY_RELATIONSHIP rows.

Underlying Base Objects

The ETRM metadata records the following referenced base objects: CS_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), HZ_CUST_ACCOUNTS (SYNONYM), HZ_PARTIES (SYNONYM), and HZ_RELATIONSHIPS (SYNONYM). The view text confirms that it joins HZ_PARTIES to HZ_CUST_ACCOUNTS by PARTY_ID (an outer join, A.PARTY_ID(+) = P.PARTY_ID), and cross-references CS_LOOKUPS on LOOKUP_TYPE = 'CS_SR_CONTACT_TYPE' to derive the PARTY_TYPE_MEANING display value.

The second query block introduces HZ_RELATIONSHIPS, joining REL.PARTY_ID = R.PARTY_ID and REL.SUBJECT_ID = P.PARTY_ID. This supports the party-relationship branch of the union, matching the metadata note that HZ_RELATIONSHIPS is a referenced object. Both branches filter P.STATUS IN ('A','I'), and the relationship branch additionally restricts R.STATUS IN ('A','I') and R.PARTY_TYPE = 'PARTY_RELATIONSHIP'. The presence of FND_GLOBAL in the metadata reflects standard Service security/context dependencies rather than an explicit column in the projected list.

Key Columns

  • PARTY_ID — Primary surrogate key identifying the contact party in the TCA registry.
  • PARTY_NUMBER — Externally meaningful, unique party number.
  • PARTY_TYPE — Indicates whether the row represents a PERSON or a PARTY_RELATIONSHIP.
  • PARTY_NAME — Display name of the party.
  • PERSON_FIRST_NAME / PERSON_LAST_NAME — Person name components, populated from the associated person record.
  • ACCOUNT_NUMBER / ACCOUNT_NAME — Customer account information joined (outer) through HZ_CUST_ACCOUNTS; may be null when no account exists.
  • PARTY_TYPE_MEANING — Lookup meaning sourced from CS_LOOKUPS for the CS_SR_CONTACT_TYPE lookup type.

Common Use Cases and Queries

The view is commonly queried to populate contact lists for Service Requests, to resolve a contact's person and account context, and to find parties linked through relationships rather than direct person records.

SELECT PARTY_ID, PARTY_NUMBER, PARTY_NAME,
       PERSON_FIRST_NAME, PERSON_LAST_NAME,
       ACCOUNT_NUMBER, ACCOUNT_NAME, PARTY_TYPE_MEANING
FROM   APPS.CS_SR_HZ_CUST_CONT_V
WHERE  PARTY_TYPE = 'PERSON';

To retrieve only relationship-based contacts, filter on PARTY_TYPE = 'PARTY_RELATIONSHIP'. Because the view unites both categories, a simple full query returns the complete set of Service-eligible customer contacts. Users searching on the term "party_relationship" will most often locate this object when tracing how relationship parties are exposed to Service. Given its dependency on TCA and CS lookup tables, the view should be used for reporting and read-only integration rather than as a data-entry target.