Results for “contact_point_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSC_HZ_PHONES_V is a reporting view owned by the APPS schema within the Customer Care (CSC) product family of Oracle E-Business Suite. It is registered as a VALID database object in both EBS 12.1.1 and 12.2.2. Its stated purpose is narrow and deliberate: to concatenate the area code and phone number of a contact point into a single display column. This allows Oracle EBS reporting tools, Oracle Discoverer worksheets, Oracle XML Publisher templates, and custom OAF or Forms-based pages to render a subscriber's telephone number as one formatted string rather than forcing the consumer of the data to assemble the pieces manually.

Because the view exposes the raw AREA_CODE and PHONE_NUMBER fragments alongside the concatenated PHONE column, it serves both presentation-layer and parsing-layer requirements simultaneously. A report author seeking a human-readable telephone field selects PHONE; a downstream integration requiring the discrete components selects AREA_CODE and EXTENSION independently.

Underlying Base Objects

The view is defined over a single documented base object: CSC_HZ_CONTACT_POINTS_V, itself a view within the same APPS schema. This layering places CSC_HZ_PHONES_V two levels above the physical TCA (Trading Community Architecture) tables that ultimately store contact point data, notably HZ_CONTACT_POINTS and its related phone and e-mail child entities.

The defining query is:

• SELECT DISTINCT AREA_CODE || PHONE_NUMBER PHONE, PHONE_LINE_TYPE, CONTACT_POINT_TYPE, COUNTRY_CODE, AREA_CODE, EXTENSION FROM CSC_HZ_CONTACT_POINTS_V WHERE PHONE_NUMBER IS NOT NULL

Two characteristics of this definition merit attention. First, the DISTINCT keyword eliminates duplicate rows arising from the parent view's join logic, which is important because contact points can be associated with multiple parties or relationships. Second, the WHERE PHONE_NUMBER IS NOT NULL predicate restricts output to records that possess an actual dialable number, excluding contact points that carry only fax references, e-mail addresses, or incomplete records. No other filter is applied, so the view returns contact points across all contact point types present in the parent view.

Key Columns

• PHONE — The concatenation of AREA_CODE || PHONE_NUMBER. No separator, hyphen, or parenthesis is inserted by the view; formatting must be applied downstream. If AREA_CODE is null, the concatenation silently yields only the phone number, which can matter for international records.
• PHONE_LINE_TYPE — Classifies the line, typically distinguishing business, home, mobile, fax, and similar categories inherited from the underlying TCA phone definitions.
• CONTACT_POINT_TYPE — Identifies the contact point category, permitting callers to filter out non-telephone contact points that may have survived into the parent view.
• COUNTRY_CODE — The international country dialing code, essential when the subscriber base spans multiple countries.
• AREA_CODE — The area, city, or regional dialing prefix. This is the object of the frequently searched term and is exposed directly so that searches, groupings, and territory analyses can be performed without string manipulation.
• EXTENSION — The extension number associated with the contact point, used primarily for internal directory lookups.

Common Use Cases and Queries

The most common requirement is retrieving a display-ready telephone number for a party or contact. A typical query filters by area code, which is the exact search pattern users bring to this object:

• SELECT PHONE, CONTACT_POINT_TYPE, COUNTRY_CODE FROM APPS.CSC_HZ_PHONES_V WHERE AREA_CODE = '415';
• SELECT AREA_CODE, PHONE, EXTENSION FROM APPS.CSC_HZ_PHONES_V WHERE CONTACT_POINT_TYPE = 'PHONE' AND COUNTRY_CODE = 'US' ORDER BY AREA_CODE;
• SELECT DISTINCT COUNTRY_CODE, AREA_CODE FROM APPS.CSC_HZ_PHONES_V ORDER BY COUNTRY_CODE, AREA_CODE;

Additional scenarios include populating a customer care agent's screen with a contiguous dialing string, generating directory extracts for telephony integration, and performing data quality audits that quantify how many contact points lack an area code or extension. Because the view applies no security predicates of its own, any deployment relying on it must enforce organizational or data access restrictions in the calling query or the surrounding application layer.