Search Results cs_cont_contacts_rg_v




Overview
Explore in AI Chat

Overview

CS_CONT_CONTACTS_RG_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. Its documented purpose is to expose "Contact Information," presenting person-type contact records together with their formatted names, consolidated addresses, and telephone, fax, and email details in a single flattened result set. The view is marked VALID in both Oracle EBS 12.1.1 and 12.2.2, and the metadata excerpt documentation confirms that it is built with a mix of a base synonym, profile-driven package functions, and territory lookup data rather than simple direct table joins.

In reporting and integration terms, the view serves as a convenient denormalized access point for contact data without requiring the calling program to reproduce the multi-element name and address concatenation logic or to call the phone and email lookup functions individually. Because several of its columns are derived at runtime from function calls and profile option values, the view reflects both persistent party data and environment-dependent configuration.

Underlying Base Objects

The ETRM documentation records four referenced objects for this view: CS_PARTIES_PKG (PACKAGE), FND_PROFILE (PACKAGE), FND_TERRITORIES_VL (VIEW), and HZ_PARTIES (SYNONYM). The view text selects HZP.PARTY_ID, HZP.PARTY_NUMBER, and the individual name and address attributes from HZ_PARTIES, filtered by HZP.PARTY_TYPE = 'PERSON'. FND_TERRITORIES_VL is outer-joined on HZP.COUNTRY = FT.TERRITORY_CODE(+), so contact records are retained even where no matching territory row exists.

Telephone, fax, and email values are obtained through CS_PARTIES_PKG functions, namely GET_PARTY_PHONE, GET_PARTY_EMAIL, and GET_PARTY_FAX. The phone type arguments are resolved from profile options via FND_PROFILE.VALUE_WNPS, using CS_AR_WORK_PHONE_TYPE, CS_AR_CELL_PHONE_TYPE, CS_AR_PAGER_PHONE_TYPE, and CS_AR_HOME_PHONE_TYPE. The specific phone type attached to each column therefore depends on how those profile options are set in the operating environment.

Key Columns

The documented columns are:

  • PARTY_NAME — a composite display name assembled from the prefix/adjunct, first, middle, and last name elements, including conditional spacing for missing middle or last names.
  • FIRST_NAME — the person's first name taken directly from HZ_PARTIES.
  • ADDRESS — a concatenation of ADDRESS1 through ADDRESS4, CITY, STATE, POSTAL_CODE, PROVINCE, and COUNTY, with comma separators applied conditionally.
  • WORK_PHONE_NUMBER, CELL_PHONE_NUMBER, PAGER_PHONE_NUMBER, HOME_PHONE_NUMBER — phone numbers retrieved by CS_PARTIES_PKG.GET_PARTY_PHONE for the profile-defined phone types.
  • FAX_NUMBER — the fax number obtained through CS_PARTIES_PKG.GET_PARTY_FAX.
  • EMAIL_ADDRESS — the email address obtained through CS_PARTIES_PKG.GET_PARTY_EMAIL.
  • PARTY_ID and PARTY_NUMBER — the surrogate identifier and the user-visible party number for the contact.

Common Use Cases and Queries

Typical uses include service-agent contact lookups, call-center screen displays, and ad hoc reporting where a single contact-centric record is required. Because the view returns only person parties, organizations are excluded automatically, which suits service contact directories.

A basic query retrieving all contact information is:

  • SELECT party_name, first_name, address, work_phone_number, cell_phone_number, email_address, fax_number FROM cs_cont_contacts_rg_v;
  • SELECT party_number, party_name, home_phone_number FROM cs_cont_contacts_rg_v WHERE party_id = :party_id;
  • SELECT party_id, party_name, email_address FROM cs_cont_contacts_rg_v WHERE UPPER(party_name) LIKE UPPER(:search_pattern);

Where large volumes of contacts must be processed, querying this view may be less efficient than direct access to HZ_PARTIES, since the package functions execute per row and can introduce performance overhead. It remains the most direct documented means of reproducing standard Service contact information formatting.