Search Results concat_address




Overview
Explore in AI Chat

Overview

AST_LM_PER_SMARTSEARCH_V is an Oracle E-Business Suite internal view owned by the APPS schema and registered under FND Design Data as AST.AST_LM_PER_SMARTSEARCH_V. It exposes the person-level result set produced by the Oracle Applications "Smart Search" (search-matching) framework used within Oracle Sales and Telesales functionality. In EBS 12.1.1 and 12.2.2, the view is marked VALID and is delivered as an unsupported, Oracle-internal object; Oracle Corporation does not support direct access to applications data through this view except from standard Oracle Applications programs.

The view presents a denormalized, presentation-ready view of a matched person: full name components, party identifiers, a preformatted concatenated address, individual address attributes, scoring information, contact points (email, phone), party status, URL, account number and customer account identifier. Because it joins to the matching global temporary tables (HZ_MATCHED_CPTS_GT, HZ_MATCHED_PARTIES_GT, HZ_MATCHED_PARTY_SITES_GT), the row set it returns reflects the outcome of an active match/search session rather than a static master list. This makes it fundamentally a runtime search-results object, not a general-purpose party query view.

Underlying Base Objects

The documented dependencies reveal a TCA (Trading Community Architecture) and Receivables foundation. The view is defined over the HZ synonym family:

Key Columns

The CONCAT_ADDRESS column (VARCHAR2 4000) is the pre-concatenated, formatted address string — the column most relevant to searches for "concat_address." It is populated via ARP_ADDR_LABEL_PKG from the underlying location and party-site records. Individual address parts (ADDRESS, CITY, COUNTY, STATE, POSTAL_CODE, PROVINCE, COUNTRY) remain separately available for filtering and sorting. Person identity is carried by PERSON_FULL_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PARTY_ID, and PARTY_NUMBER. SCORE (NUMBER) conveys match confidence. STATUS and STATUS_MEAN decode the party status via AR_LOOKUPS. ACCOUNT_NUMBER and CUST_ACCOUNT_ID link the person to Receivables customer data. SEARCH_CONTEXT_ID is exposed by the view query text but is not itemized in the documented column dictionary excerpt.

Common Use Cases and Queries

Smart Search results are typically consumed by the standard Telesales and Sales "Find Person" flows, where Oracle programs read SCORE to rank candidate parties. Custom reporting should treat the view cautiously, because the global temporary tables are transaction-scoped and only populated during an active match operation. A representative query includes:

SELECT PERSON_FULL_NAME, PARTY_NUMBER, CONCAT_ADDRESS, SCORE, EMAIL_ADDRESS, FULL_PHONE_NUMBER FROM APPS.AST_LM_PER_SMARTSEARCH_V WHERE SCORE >= 90 ORDER BY SCORE DESC;

Because the view is flagged Oracle Internal Use Only and querying its underlying GTTs outside a live match session generally yields no rows, supported integration should instead use TCA APIs (HZ_PARTY_V2PUB) or the HZ_PARTIES-based views. The view remains documented here as a reference to the internal Smart Search contract in both 12.1.1 and 12.2.2.