Results for “ast_l_contact_addr_v”

26 results




Overview
Explore in AI Chat

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

Overview

The AST_L_CONTACT_ADDR_V view is a TeleSales (AST) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated, presentation-ready list of customer contacts together with their associated address information, and joins each address to its territory description for display purposes. In the ETRM documentation the object is registered as a VIEW with VALID status, indicating that its definition compiles cleanly against the underlying dictionary.

Because TeleSales relies on the Oracle Trading Community Architecture (TCA) party model rather than storing contact and address data directly, this view functions as a convenience layer. It flattens the party-to-address relationship into a single relational shape, making it suitable for reporting, LOV (list of values) population, outbound call list building, and lightweight integration extracts. Typical consumers include concurrent programs, BI Publisher reports, OAF/Forms-based contact search pages, and custom SQL used by implementation teams to validate contact and address data during conversions or data audits.

Underlying Base Objects

The documented view text defines the object over three referenced base objects:

The join condition links CUST.PARTY_ID to ADDR.PARTY_ID, and then outer-joins ADDR.COUNTRY to TERR.TERRITORY_CODE, with TERR.LANGUAGE outer-joined to USERENV('LANG') so that the territory name is returned in the session language. The final filter restricts the result set to parties whose PARTY_TYPE is either 'PEOPLE' or 'ORGANIZATION'. Because the two principal sources are themselves TCA-based views, the lineage of AST_L_CONTACT_ADDR_V terminates at the TCA tables HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES, HZ_LOCATIONS and HZ_CUST_ACCT_SITES_ALL, although only the intermediate views are formally documented.

Key Columns

  • CUSTOMER_ID / PARTY_ID — the TCA party identifier for the contact or organization.
  • CUSTOMER_NAME — the party name formatted for display (person or organization).
  • ADDRESS_ID — the location/address identifier from TCA.
  • PARTY_SITE_ID — the party-site identifier linking the party to the address.
  • ADDRESS_TYPE — classification of the address, such as billing or shipping.
  • ADDRESS1 – ADDRESS4, CITY, POSTAL_CODE, STATE, COUNTY — the structured address elements.
  • COUNTRY / COUNTRY_CODE — the country value and its territory code; COUNTRY carries the translated territory short name from FND_TERRITORIES_TL.

Note that PARTY_ID appears twice in the documented select list, and that the columns listed in the ETRM column inventory include CUSTOMER_ID and COUNTRY_CODE, which map to the aliased expressions in the view text.

Common Use Cases and Queries

A frequent requirement is locating every contact and address belonging to a given customer, for example a telecommunications or utility subscriber servicing scenario. A representative query is:

SELECT customer_name, address1, address2, city, state, postal_code, country
FROM   apps.ast_l_contact_addr_v
WHERE  UPPER(city) = 'VIJAYAWADA';

Teams also search by contact name or by postal code to build call lists, or filter by COUNTRY_CODE to isolate records for a specific territory. Because the view exposes both PARTY_ID and ADDRESS_ID, it is useful for reconciliation between TCA address records and TeleSales contact assignments, and for ad-hoc extracts feeding external CRM or dialer systems. When using the view in custom code, standard EBS best practice applies: reference it through the APPS synonym, respect the USERENV('LANG') language dependency, and note that the outer joins on TERR mean an address with an unmapped country code will still be returned with a null country description. The view is read-only and should not be modified; any functional change is delivered by Oracle patches.