Results for “area_code”

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

Overview

The WSH_PRIMARY_CONTACT_PHONE_V view is a Shipping Execution (WSH) reporting object owned by the APPS schema. It exposes the primary telephone number associated with customer account role contacts, providing a denormalized and filtered perspective on Oracle's Trading Community Architecture (TCA) contact data. Rather than requiring callers to resolve the relationships between contact points and customer account roles directly, the view presents a single, consistent row per contact holding the designated primary general-purpose phone number.

Within Oracle EBS 12.1.1 and 12.2.2, the view serves as a lightweight read-only interface for shipping-related reporting, label printing, carrier documentation, and integrations that need a contactable phone number for a customer or account role. Because the view abstracts the TCA join logic and pre-filters on the primary flag, it reduces the risk of duplicate or ambiguous phone number results in downstream logic. The object is documented as VALID and is classified under the WSH product, indicating it is intended primarily for Shipping Execution modules such as delivery, trip, and manifest processing.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• HZ_CONTACT_POINTS — the TCA table storing contact point records (phone, email, EDI, web, telex, and so on) for parties and other owners.
• HZ_CUST_ACCOUNT_ROLES — the TCA table defining the roles that parties play for a customer account, such as contact roles.

The join is established on CAR.PARTY_ID = CONT_POINT.OWNER_TABLE_ID, with the additional predicate CONT_POINT.OWNER_TABLE_NAME = 'HZ_PARTIES', ensuring that only contact points owned directly by parties are considered. The view filters contact point types to exclude EDI, EMAIL, and WEB, and requires that either the phone line type or the contact point type equals GEN, thereby restricting results to general-purpose telephony records. Only contact points marked with PRIMARY_FLAG = 'Y' are returned, and rows with a null customer account role ID are discarded. A SELECT DISTINCT is applied to eliminate duplicate rows.

Key Columns

• CONTACT_ID — the customer account role identifier (CUST_ACCOUNT_ROLE_ID), not a party or contact point ID. It keys the view to a role-level contact.
• AREA_CODE — the telephone area code from the contact point record (PHONE_AREA_CODE).
• PHONE_NUMBER — the contact telephone number. A DECODE is applied so that when the contact point type is TLX the telex number is returned; otherwise the standard phone number is returned.

Common Use Cases and Queries

Typical scenarios include displaying a primary contact number on shipping documents, populating carrier or customs forms, and enriching delivery notifications. Because the view keys on the customer account role, it is often joined back to order, delivery, or customer master data. A representative query follows:

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

These queries illustrate the intended usage: resolving a single primary general phone number per contact role for shipping-related reporting and integration.