Results for “ast_ls_org_phone_v”

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

Overview

AST_LS_ORG_PHONE_V is a TeleSales (AST) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates party-level organizational data with primary contact-point telephone information. The view presents one row per organization party that has a primary contact point flagged as the primary record in the HZ_CONTACT_POINTS table. It serves as a simplified, flattened source for TeleSales agents, list-generation routines, outbound calling screens, and integration extracts that require a display-ready organization name alongside a formatted telephone number. The view is documented in the ETRM (E-Business Suite Technical Reference Manual) with the note "Not implemented in this database" for the surveyed instance, meaning the definition exists in the application metadata but the object may not be deployed or may be absent in specific environments. Oracle EBS release 12.1.1 and 12.2.2 share a common data model in the Oracle Trading Community Architecture (TCA) tables on which this view depends, so the view's behavior is consistent across both releases.

Underlying Base Objects

The view is defined over two TCA tables:

• HZ_PARTIES PARTY — the master party record, filtered to PARTY_TYPE = 'ORGANIZATION' and STATUS = 'A' (active).
• HZ_CONTACT_POINTS CONT_POINT — the contact-point detail, joined on OWNER_TABLE_ID = PARTY.PARTY_ID with OWNER_TABLE_NAME = 'HZ_PARTIES', and restricted to PRIMARY_FLAG = 'Y'.

The join predicate requires that the contact point is owned by the party and that it is the primary contact point. No other base objects are documented in the ETRM metadata, and the referenced-base-object list is empty. The view therefore exposes a one-to-one relationship between an active organization party and its primary contact point, including its telephone attributes and address attributes carried from HZ_PARTIES.

Key Columns

• PARTY_NAME, PARTY_ID, PARTY_NUMBER — identity of the organization.
• PARTY_TYPE, CATEGORY_CODE, STATUS, SIC_CODE, TAX_REFERENCE — classification and status attributes of the party.
• COMPETITOR_FLAG, CUSTOMER_KEY — competitor designation and customer key.
• CURRENT_FY_REVENUE — exposed from PARTY.CURR_FY_POTENTIAL_REVENUE.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — raw telephone elements.
• FULL_PHONE_NUMBER — a concatenation of country code, area code, phone number, and extension using NVL placeholders and hyphen separators, producing a display-ready string.
• TELEPHONE_TYPE, PHONE_LINE_TYPE, CONTACT_POINT_TYPE, PRIMARY_FLAG — telephony classification attributes.
• EMAIL_ADDRESS — party e-mail address.
• ADDRESS1 through COUNTRY, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE — the organization address.
• ORIG_SYSTEM_REFERENCE, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit and concurrent-program traceability columns.

Common Use Cases and Queries

Typical uses include TeleSales prospect and customer lookup by organization name or phone number, outbound call-list generation, and directory-style extracts for downstream integrations. A simple lookup for an organization matching a search term such as a company name would be:

• SELECT party_name, full_phone_number, email_address FROM ast_ls_org_phone_v WHERE UPPER(party_name) LIKE '%TELECOMMUNICATION HEADSETS INDIA%';
• SELECT party_number, party_name, full_phone_number FROM ast_ls_org_phone_v WHERE phone_number = :p_number;
• SELECT party_id, party_name, full_phone_number, city, country FROM ast_ls_org_phone_v ORDER BY party_name;

Because the view restricts results to active organizations with a primary contact point, records without a primary telephone do not appear. Analysts requiring all contact points, alternate phone types, or inactive parties should query HZ_PARTIES and HZ_CONTACT_POINTS directly rather than relying on this view.