Search Results primary_phone_area_code




Overview
Explore in AI Chat

Overview

AST_LM_PER_QUICK_V is an APPS-owned database view within the Oracle E-Business Suite TeleSales (AST) product family. It supplies a denormalized, read-only projection of person-type parties for use by the TeleSales Lead Management and Quick Search functionality, exposing party identity, address, status, e-mail, and telephony attributes in a single row per person. Because the view flattens data that is otherwise distributed across the Trading Community Architecture (TCA) model, it allows concurrent programs, Oracle Forms LOVs, and custom reports to resolve a "quick" person record without joining HZ_PARTIES, HZ_LOCATIONS, and HZ_CONTACTS independently.

The object is documented as VALID at release 12.1.1 and 12.2.2. Its most frequently searched column, PRIMARY_PHONE_NUMBER, is the raw telephone number component of the person's primary phone, disassociated from country code, area code, and extension so that it can be indexed, matched, or concatenated by calling applications.

Underlying Base Objects

The view text is defined over three documented base objects:

Only parties with a status of 'A' (active) or 'I' (inactive) are returned. Because the joins to FND_TERRITORIES_TL are outer (+), a person is retained even when no matching territory translation exists.

Key Columns

Common Use Cases and Queries

Typical consumers are TeleSales quick-search LOVs, agent-desk person lookups, outbound calling lists, and ad-hoc reporting where a compact person/phone record is required. The search for "primary_phone_number" usually reflects a need to filter or extract the raw number:

  • Locating a person by telephone number:
SELECT party_id,
       person_first_name,
       person_last_name,
       phone_area_code,
       phone_number,
       full_phone_number
FROM   apps.ast_lm_per_quick_v
WHERE  phone_number = :p_phone_number;
  • Producing a contact list with formatted numbers:
SELECT person_last_name || ', ' || person_first_name  contact,
       full_phone_number,
       email_address,
       status_mean
FROM   apps.ast_lm_per_quick_v
WHERE  status = 'A'
ORDER  BY person_last_name;
  • Matching on area code plus number, or restricting by country:
SELECT party_id, phone_area_number, country_name
FROM   apps.ast_lm_per_quick_v
WHERE  phone_area_number LIKE :p_prefix || '%';

Because CUST_ACCOUNT_ID and ACCOUNT_NUMBER are always NULL, the view cannot be used to resolve customer accounts; callers must join to HZ_CUST_ACCOUNTS externally. All queries should be issued against the APPS synonym, and the view's reliance on USERENV('LANG') means territory names reflect the session language.