Search Results cont_point




Overview
Explore in AI Chat

Overview

APPS.WSH_PRIMARY_CONTACT_PHONE_V is a reporting and integration view in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It exposes the primary telephone contact point for each customer account role held by a party. The view joins the contact point model in Oracle Trading Community Architecture (TCA) with the customer account role model used by Order Management, Shipping, and Receivables. It is primarily consumed by Shipping Execution (WSH) and related modules that must resolve a single, reliable telephone number for a ship-to contact, an order contact, or a customer account role without traversing the full HZ_CONTACT_POINTS hierarchy.

The view is read-only and returns one row per qualifying primary contact point per customer account role. Because it filters on PRIMARY_FLAG = 'Y', consumers are relieved of the responsibility to rank multiple contact points themselves, which simplifies downstream SQL and PL/SQL logic. The search term "cont_point" reflects the internal alias CONT_POINT assigned to HZ_CONTACT_POINTS in the view definition.

Underlying Base Objects

The documented base objects are two TCA synonyms owned effectively by the APPS schema:

  • HZ_CONTACT_POINTS — aliased CONT_POINT. Stores contact point records (phone, fax, telex, e-mail, web, EDI) belonging to parties, locations, and other entities identified by OWNER_TABLE_NAME and OWNER_TABLE_ID.
  • HZ_CUST_ACCOUNT_ROLES — aliased CAR. Stores the roles (for example, Bill-To, Ship-To, or other account role types) that a party plays for a customer account.

The join condition is CAR.PARTY_ID = CONT_POINT.OWNER_TABLE_ID, constrained by CONT_POINT.OWNER_TABLE_NAME = 'HZ_PARTIES'. This restricts the contact points considered to those owned directly by the party, and links them to the party's customer account roles.

Key Columns

  • CONTACT_ID — sourced from CAR.CUST_ACCOUNT_ROLE_ID. Identifies the customer account role, not the party; a party holding several roles yields several rows.
  • AREA_CODE — sourced from CONT_POINT.PHONE_AREA_CODE. The telephone area code for the primary contact point.
  • PHONE_NUMBER — a DECODE expression: when CONTACT_POINT_TYPE = 'TLX' the value is TELEX_NUMBER; otherwise it is PHONE_NUMBER. This allows the view to return a single unified number column across telephone and telex contact points.

Filtering predicates are significant to interpretation. Contact point types EDI, EMAIL, and WEB are excluded. The expression NVL(PHONE_LINE_TYPE, CONTACT_POINT_TYPE) = 'GEN' restricts results to general-purpose lines. Rows with a null CUST_ACCOUNT_ROLE_ID are discarded, and the presence of DISTINCT indicates that duplicate rows can arise from the underlying join.

Common Use Cases and Queries

Typical scenarios include resolving a contact telephone for a ship-to or bill-to role, populating shipping documents, and driving outbound notifications. A representative query is:

  • SELECT contact_id, area_code, phone_number FROM apps.wsh_primary_contact_phone_v WHERE contact_id = :p_role_id;
  • SELECT car.cust_account_role_id, v.phone_number FROM apps.wsh_primary_contact_phone_v v, apps.hz_cust_account_roles car WHERE v.contact_id = car.cust_account_role_id AND car.cust_account_id = :p_account_id;

Because the view exposes only the role identifier and the primary number, more detailed attributes such as contact name, role type, or account number must be obtained by joining back to HZ_CUST_ACCOUNT_ROLES and HZ_CUST_ACCOUNTS. This view should be treated as a convenience access path, not as a substitute for the full TCA contact point model.