Search Results raw_phone_number




Overview
Explore in AI Chat

Overview

AMS_LT_HZ_PHONE_1 is a Marketing (AMS) module data source view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in the E-Business Suite Technical Reference Manual (ETRM) with a status of VALID. The view exists to expose the primary identity phone number associated with a party, drawing its content from the Oracle Trading Community Architecture (TCA) contact point model. Its specific purpose, as stated in the ETRM documentation, is to serve as a "Data Source view based on hz_contact_points to get primary identify phone number."

Within the AMS architecture, "LT" data source views such as this one act as standardized, flattened access layers that marketing list generation, campaign execution, and audience selection processes use as a source of record attributes. By pre-filtering contacts to the active, user-entered, primary phone for parties, the view relieves callers from repeatedly encoding the same business predicates, ensuring consistent phone-number selection across marketing operations and integrated reporting.

Underlying Base Objects

The view is defined over a single referenced base object: HZ_CONTACT_POINTS, accessed through a SYNONYM in the ETRM metadata. HZ_CONTACT_POINTS is the central TCA table that stores contact mechanisms — phones, e-mail addresses, URLs, and similar entities — for parties, locations, and other owners.

The defining SELECT applies four restrictive predicates to HZ_CONTACT_POINTS (aliased HCP):

Because the view inherits the TCA ownership and multi-org security layers of HZ_CONTACT_POINTS, joins back to HZ_PARTIES on OWNER_TABLE_ID are the standard method of resolving the party identity.

Key Columns

The view exposes eighteen columns, all passed through from HZ_CONTACT_POINTS. Principal columns include:

Common Use Cases and Queries

Typical usage centers on marketing list builds and party-level phone lookups where the primary phone must be retrieved alongside the party. A representative query joining to the party master is:

SELECT p.party_id,
       p.party_name,
       v.raw_phone_number,
       v.phone_country_code,
       v.phone_number,
       v.phone_extension
FROM   ams_lt_hz_phone_1 v,
       hz_parties p
WHERE  v.owner_table_id = p.party_id;

To resolve a number from a user-supplied raw string, the RAW_PHONE_NUMBER column can be constrained directly:

SELECT owner_table_id, raw_phone_number
FROM   ams_lt_hz_phone_1
WHERE  raw_phone_number = '&entered_number';

Because TRANSPOSED_PHONE_NUMBER is exposed, suffix-based searching is also supported. In all cases, callers should note the view returns at most one row per party-phone primary record and cannot be used to retrieve secondary or non-user-entered phone numbers; those requirements demand direct queries against HZ_CONTACT_POINTS.