Search Results ast_lm_per_fuzzy_v




Overview
Explore in AI Chat

Overview

AST_LM_PER_FUZZY_V is a TeleSales (AST) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The name follows the standard TeleSales lead management naming convention: "AST_LM" denotes Lead Management, "PER" indicates the person entity, and "FUZZY" identifies the fuzzy-match search capability used to surface likely duplicate or candidate person records during lead qualification. The view is reported as VALID in the ETRM dictionary.

Functionally, the view presents a flattened, presentation-ready projection of person party data drawn from the Trading Community Architecture (TCA) model. It is consumed wherever TeleSales needs to display candidate persons matched against a fuzzy search context, particularly in the Lead Management module and any surrounding reporting or integration that renders person search results.

Underlying Base Objects

The view text joins four documented base objects:

  • HZ_PARTIES (PARTY) — the primary TCA registry source providing person name components, address elements, email, and status.
  • HZ_MATCHED_PARTIES_GT (SMARTPER) — a global temporary table holding the results of a fuzzy match run, including SEARCH_CONTEXT_ID. The join SMARTPER.PARTY_ID = PARTY.PARTY_ID restricts output to parties returned by that match.
  • AR_LOOKUPS (ALK) — supplies the translated status meaning where LOOKUP_TYPE = 'CODE_STATUS' and LOOKUP_CODE = PARTY.STATUS.
  • FND_TERRITORIES_TL (FTT) — an outer-joined (+) territory translation table resolving the country code into a territory short name for the session language.

Filtering is fixed: only PARTY_TYPE = 'PERSON' and statuses of 'A' (Active) or 'I' (Inactive) are eligible. The view is therefore a curated superset of fuzzy-match candidates rather than a general person listing.

Key Columns

Note that ACCOUNT_NUMBER and CUST_ACCOUNT_ID are declared but populated with NULLs; the view is purely person-oriented and does not join to accounts receivable customers.

Common Use Cases and Queries

The principal use is rendering fuzzy person-match results for lead qualification, de-duplication review, and TeleSales list management. A representative query:

SELECT party_id, person_first_name, person_last_name, full_phone_number, email_address, status_mean FROM apps.ast_lm_per_fuzzy_v WHERE search_context_id = :p_context ORDER BY person_last_name, person_first_name;

A second common pattern filters by contactability:

SELECT party_id, person_last_name, city, country_name FROM apps.ast_lm_per_fuzzy_v WHERE phone_area_number IS NOT NULL AND status = 'A';

Because the view does not expose account identifiers, it is not appropriate for AR customer reporting; it should be regarded strictly as a TeleSales fuzzy person-match reporting surface over the TCA registry.