Results for “ast_ls_contacts_v”

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

Overview

AST_LS_CONTACTS_V is a reporting and integration view within the Oracle E-Business Suite TeleSales (AST) module. Its purpose is to consolidate party, contact, address, and telephone information for individuals who are related to organizations through party relationships. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is most commonly joined against TeleSales and Trade Management data sets where sales agents need a flattened, denormalized picture of a contact without navigating the normalized TCA (Trading Community Architecture) schema directly.

The view is significant because it exposes both the organization-side party attributes and the person-side attributes in a single row, eliminating the need for multiple joins between HZ_PARTIES, HZ_PARTY_RELATIONSHIPS, and HZ_ORG_CONTACTS. This is particularly useful for outbound calling lists, contact-center dashboards, and lead/opportunity reporting where a contact number must be resolved quickly. A search such as "zag limited contact number" reflects a typical user need: retrieving the telephone contact point for a named organization and its associated person contacts. This view supports exactly that pattern.

Underlying Base Objects

According to the published view text, AST_LS_CONTACTS_V is defined over six TCA base tables through an inner join for the relationship structure and outer joins for the phone contact points:

• HZ_PARTY_RELATIONSHIPS (REL) — the driving relationship between the organization and the person. Only relationships with STATUS = 'A' (active) are returned.
• HZ_PARTIES (O) — the organization party, restricted to PARTY_TYPE = 'ORGANIZATION'.
• HZ_PARTIES (P) — the person party that is the subject of the relationship.
• HZ_PARTIES (R) — the party that owns the primary phone contact point.
• HZ_ORG_CONTACTS (CNT) — the organization contact record linked by PARTY_RELATIONSHIP_ID, providing job title and department.
• HZ_CONTACT_POINTS (CPT) — outer-joined on OWNER_TABLE_NAME = 'HZ_PARTIES', OWNER_TABLE_ID = REL.PARTY_ID, with PRIMARY_FLAG = 'Y', CONTACT_POINT_TYPE = 'PHONE', and STATUS = 'A'.

The ETRM metadata documents no additional referenced base objects, and the join predicates above are the definitive relationship definition. In Oracle EBS 12.1.1 and 12.2.2 the TCA tables share the same structure, so the view remains portable between the two releases.

Key Columns

The view returns a wide set of columns. The most important include PARTY_NAME (organization name), PARTY_ID, PARTY_NUMBER, PARTY_TYPE (always 'PARTY_RELATIONSHIP' as a derived literal), and the organization attributes COMPETITOR_FLAG, CUSTOMER_KEY, STATUS, SIC_CODE, and TAX_REFERENCE.

Person-side columns include PERSON_ID, PERSON_FIRST_NAME, PERSON_LAST_NAME, and a derived FULL_NAME concatenation. Address columns (ADDRESS1 through ADDRESS4, CITY, STATE, COUNTRY, POSTAL_CODE) are exposed for convenient display. The telephone resolution columns are CONTACT_NUMBER, CONTACT_KEY, ORG_CONTACT_ID, JOB_TITLE, DEPARTMENT, and the contact-point attributes PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, and PHONE_EXTENSION. A derived FULL_PHONE_NUMBER concatenates country code, area code, number, and extension. Note that because the contact-point join is outer, these phone columns may be NULL when no active primary phone exists.

Common Use Cases and Queries

The primary use case is resolving a contact telephone number for a named organization. The following query demonstrates the pattern for a search such as "zag limited contact number":

• Contact lookup by organization name: SELECT party_name, full_name, full_phone_number FROM ast_ls_contacts_v WHERE UPPER(party_name) LIKE '%ZAG%';
• Contact-center calling list: SELECT party_name, full_name, job_title, full_phone_number FROM ast_ls_contacts_v WHERE status = 'A' ORDER BY party_name;
• Phone present only: SELECT party_name, full_name, contact_number FROM ast_ls_contacts_v WHERE contact_number IS NOT NULL;

Because the view restricts to active relationships and active primary phone contact points, results are immediately usable for dialing and integration without further filtering. Reporting teams typically wrap it in custom BI Publisher or Discoverer reports that the TeleSales module references for agent productivity screens.