Results for “phone_area_code”

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

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):

• STATUS = 'A' — only active contact points are returned.
• CONTENT_SOURCE_TYPE = 'USER_ENTERED' — only records entered by a user rather than system-derived sources.
• CONTACT_POINT_TYPE = 'PHONE' — restricts the result set to telephone contact points.
• OWNER_TABLE_NAME = 'HZ_PARTIES' — limits results to contact points owned directly by parties.
• PRIMARY_FLAG = 'Y' — returns only the designated primary phone for each party.

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:

• CONTACT_POINT_ID — primary key of the underlying contact point record; used for joins and de-duplication.
• OWNER_TABLE_ID — identifier of the owning party; joins to HZ_PARTIES.PARTY_ID.
• RAW_PHONE_NUMBER — the phone number as originally entered by the user, prior to normalization. This is the column most relevant to callers searching on raw_phone_number, and it preserves formatting, spacing, and punctuation exactly as captured.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — parsed components of the phone contact point.
• TRANSPOSED_PHONE_NUMBER — a reversed representation used for efficient suffix or pattern searching.
• CONTACT_POINT_PURPOSE and PRIMARY_BY_PURPOSE — purpose classification and primary-by-purpose indicator for the contact point.
• PHONE_LINE_TYPE, PHONE_TOUCH_TONE_TYPE_FLAG, TIME_ZONE, TIMEZONE_ID, TELEX_NUMBER — ancillary telephone attributes.
• STATUS, CONTENT_SOURCE_TYPE, CONTACT_POINT_TYPE — the filter columns, available for reference though fixed by the view's predicates.

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.