Search Results contact_point_purpose_meaning




Overview
Explore in AI Chat

Overview

AST_CONTACT_POINTS_V is a TeleSales (AST) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes contact point records maintained in the Oracle Trading Community Architecture (TCA) layer and enriches them with decoded lookup meanings and time zone attributes required by the TeleSales and interaction-center functionality. The view is a denormalized, read-oriented projection over HZ_CONTACT_POINTS, joining several AR_LOOKUPS views to translate coded lookup values into user-facing meanings and FND_TIMEZONES_VL to resolve time zone identifiers.

In reporting and integration contexts, the view serves as the canonical source for contact point information such as e-mail addresses, telephone numbers, URLs, and EDI-specific location attributes. Because it carries the EDI columns (EDI_TRANSACTION_HANDLING, EDI_ID_NUMBER, EDI_PAYMENT_METHOD, EDI_PAYMENT_FORMAT, EDI_REMITTANCE_METHOD, EDI_REMITTANCE_INSTRUCTION, EDI_TP_HEADER_ID, and EDI_ECE_TP_LOCATION_CODE), it is frequently referenced by Trading Partner and e-commerce integrations — which is consistent with the search term "edi_ece_tp_location_code" that maps to the EDI_ECE_TP_LOCATION_CODE column.

Underlying Base Objects

The view is defined over the following documented base objects:

  • HZ_CONTACT_POINTS (referenced as a synonym) — the primary TCA table holding contact point records for parties, locations, and trading partners. All non-lookup columns in the view originate from this table.
  • AR_LOOKUPS (view, aliased LKUP1, LKUP2, LKUP4, LKUP5) — supplies decoded meanings. LKUP1 decodes COMMUNICATION_TYPE, LKUP2 decodes the telephone line type, and LKUP4/LKUP5 decode contact point purpose (with a DECODE selecting LKUP5 for WEB contact point types and LKUP4 otherwise).
  • FND_TIMEZONES_VL (view, aliased TM) — provides time zone name and related attributes.

All AR_LOOKUPS joins are outer joins (indicated by the "(+)" syntax), so contact points without a matching lookup value are still returned with a null meaning.

Key Columns

Common Use Cases and Queries

Typical scenarios include resolving EDI trading partner locations, extracting e-mail/telephone contact data for TeleSales campaigns, and populating integrations that require decoded contact point purposes. A representative query filtering on the EDI location code is shown below.

  • Look up contact points by EDI location code for a trading partner integration.
  • Extract primary e-mail and telephone contacts per owner for a campaign.
  • Report communication type distribution using the decoded MEANING column.

SELECT contact_point_id, contact_point_type, meaning, email_address, phone_number, edi_ece_tp_location_code FROM apps.ast_contact_points_v WHERE edi_ece_tp_location_code = :p_location_code;

Because the view inherits the HZ_CONTACT_POINTS structure and applies only lookup/time zone enrichment, it should be treated as a read-only reporting object; write operations must target the base TCA tables directly.