Search Results phone_line_type_meaning




Overview
Explore in AI Chat

Overview

CS_SR_HZ_CONT_PTS_P_PHONES_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to list all active primary telephone numbers recorded against party contact points. The view is a reporting and integration convenience object: rather than requiring callers to join HZ_CONTACT_POINTS to the AR_LOOKUPS lookup tables and manually decode phone formatting and lookup meanings, the view presents a denormalized, presentation-ready result set.

The view restricts its output to rows where CONTACT_POINT_TYPE equals 'PHONE' and OWNER_TABLE_NAME equals 'HZ_PARTIES', so it is scoped to phone contact points belonging to parties rather than to other owner entities such as organizations, locations, or contacts held on other tables. It is commonly consumed by Service Request (SR) and TeleService style functionality that needs to display or dial a party's primary phone number.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects: AR_LOOKUPS (a view) and HZ_CONTACT_POINTS (referenced via a synonym). AR_LOOKUPS is referenced twice, using aliases AR and AR1, to resolve two distinct lookup types:

Both lookup joins are outer joins (indicated by the (+) syntax), so a phone contact point is still returned even when no matching lookup row exists. The driving table is HZ_CONTACT_POINTS, filtered to phone contact points owned by HZ_PARTIES.

Key Columns

  • PHONE — A concatenated display string built from PHONE_COUNTRY_CODE, PHONE_AREA_CODE, and PHONE_NUMBER, with hyphen separators inserted only where the component values are non-null.
  • PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — The raw phone components, retained individually for formatting, validation, or dialing logic.
  • CONT_POINT_TYPE_MEANING — The decoded meaning of CONTACT_POINT_TYPE from AR_LOOKUPS (COMMUNICATION_TYPE).
  • PHONE_LINE_TYPE_MEANING — The decoded meaning of the underlying PHONE_LINE_TYPE lookup code from AR_LOOKUPS (PHONE_LINE_TYPE), such as values describing whether the line is a home, work, mobile, fax, or similar line category. This is the column most relevant to searches for "phone_line_type_meaning".
  • OWNER_TABLE_ID — The identifier of the owning record, in this view the party identifier within HZ_PARTIES.
  • CONTACT_POINT_ID — The unique key of the contact point row in HZ_CONTACT_POINTS.
  • TIMEZONE_ID — The time zone associated with the contact point, useful for scheduling and outbound contact.
  • CONTACT_POINT_TYPE, PRIMARY_FLAG, STATUS — The raw type, primary indicator, and status values carried from the base table.
  • TRANSPOSED_PHONE_NUMBER — A reversed-order representation of the phone number, typically used for efficient suffix searching and "ends with" style queries.

Although the view name and description emphasize primary phones, the SELECT clause itself does not impose a PRIMARY_FLAG or STATUS filter in the documented view text; callers should apply those predicates explicitly when only active primary numbers are required.

Common Use Cases and Queries

Typical uses include resolving a party's primary phone for Service Request display, populating contact detail blocks, and validating that phone line type lookups are configured. A basic query by party is:

  • SELECT phone, phone_line_type_meaning, phone_extension FROM cs_sr_hz_cont_pts_p_phones_v WHERE owner_table_id = :party_id;
  • SELECT contact_point_id, phone, cont_point_type_meaning FROM cs_sr_hz_cont_pts_p_phones_v WHERE contact_point_id = :contact_point_id;
  • SELECT phone_line_type_meaning, COUNT(*) FROM cs_sr_hz_cont_pts_p_phones_v GROUP BY phone_line_type_meaning;

To honor the view's stated intent of returning only active primary phones, add predicates such as AND primary_flag = 'Y' AND status = 'A'. Because CONT_POINT_TYPE_MEANING and PHONE_LINE_TYPE_MEANING derive from outer joins, a null meaning indicates a missing or inactive AR_LOOKUPS entry rather than an absent phone record, which is a frequent diagnostic point when lookup-driven values fail to display.