Search Results primary_phone_extension




Overview
Explore in AI Chat

Overview

APPS.AST_LM_PER_QUICK_V is a reporting and integration view in Oracle E-Business Suite that presents a consolidated, denormalized projection of person-type parties together with their primary telephone contact information. The view name reflects its purpose within the Oracle CRM/Telephony and Leads Management (AST_LM) family of objects: it provides a "quick" lookup of persons suitable for lightweight reference queries, list-of-values implementations, and downstream data extraction. It surfaces identity, address, status, and phone attributes in a single row, sparing callers from joining multiple HZ_PARTIES-related sources themselves.

The view is particularly relevant to searches involving primary_phone_number, since it exposes the primary telephone number and its component parts directly. All rows returned are restricted to parties whose PARTY_TYPE is 'PERSON', so the view never returns organization records. It is defined in the APPS schema and is generally treated as a read-only reporting object rather than a table that application code writes to.

Underlying Base Objects

The view is defined over the following documented objects:

  • HZ_PARTIES (synonym) — the primary source of person identity, address, email, status, and phone columns. Aliased as PARTY.
  • AR_LOOKUPS (view) — supplies the decoded meaning of the party status code via ALK.MEANING.
  • FND_TERRITORIES_TL (synonym) — supplies the translated territory short name (FTT.TERRITORY_SHORT_NAME) for the party's country.

The join to AR_LOOKUPS is an inner join constrained by LOOKUP_TYPE = 'CODE_STATUS' and LOOKUP_CODE = PARTY.STATUS. The joins to FND_TERRITORIES_TL are outer joins (denoted by the (+) operator), keyed on PARTY.COUNTRY = FTT.TERRITORY_CODE and filtered by the session's language through USERENV('LANG') on both LANGUAGE and SOURCE_LANG. Because the territory join is outer, parties without a matching territory translation still return a row, with a null territory short name.

Key Columns

The presence of a bare primary_phone_number column, alongside these derived forms, makes the view a natural target when a search calls for phone-based lookups.

Common Use Cases and Queries

The view is typically used for person lookups where a single-row profile including phone data is required. A representative query matching a specific phone number follows:

  • SELECT party_id, person_last_name, primary_phone_number FROM apps.ast_lm_per_quick_v WHERE primary_phone_number = '5551234';
  • SELECT party_id, person_first_name, person_last_name, primary_phone_area_code, primary_phone_number, meaning FROM apps.ast_lm_per_quick_v WHERE meaning = 'Active' ORDER BY person_last_name;
  • SELECT party_id, primary_phone_area_code || primary_phone_number AS dialable, city, province FROM apps.ast_lm_per_quick_v WHERE country = 'US';

Because CUST_ACCOUNT_ID is always null, callers should not use the view to resolve customer accounts; it serves purely as a person-and-phone reference. Queries should also account for the restriction to person parties and the A/I status filter, which excludes other status values from the result set.