Search Results aso_i_contact_points_v




Overview
Explore in AI Chat

Overview

The view ASO_I_CONTACT_POINTS_V is an Oracle E-Business Suite database object owned by the APPS schema and categorized under the ASO - Order Capture product family. It exposes contact point information—telephone numbers, email addresses, URLs, and related communication attributes—used by order capture and fulfillment processes. The view is a thin, denormalized projection defined over the Oracle Trading Community Architecture (TCA) entity HZ_CONTACT_POINTS, providing ASO-specific access to the master contact point records maintained centrally within TCA.

Its role is primarily integration and reporting: rather than duplicating contact point data within ASO-specific tables, the view surfaces the authoritative TCA rows in a form suitable for order capture inquiries, order import interfaces, and downstream reporting. Because it is a view and not a table, it carries no independent storage, and its column set reflects the structure of HZ_CONTACT_POINTS at the version for which it was registered. In Oracle EBS 12.1.1 and 12.2.2, this object is listed as VALID and is available for use in custom reports, BI Publisher data models, and PL/SQL packages executed against the APPS schema.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: HZ_CONTACT_POINTS, accessed through a synonym. The view text is a straightforward SELECT of columns from that table with no joins, aggregations, filters, or functions. Consequently, the relationship between the view and HZ_CONTACT_POINTS is one of direct column passthrough: each row in the view corresponds exactly to one row in the base table, and the ROWID of the base row is exposed as ROWID within the view.

This design means the view inherits the TCA data model's semantics and constraints. Any validation, status transition, or merge behavior applied to contact points through TCA APIs is reflected immediately, since no materialization or copy occurs. From an upgrade and patching perspective, the view is dependent on the continued presence and structure of HZ_CONTACT_POINTS; changes introduced to the base table through TCA patch levels can affect the view's exposed columns.

Key Columns

Because the view mirrors HZ_CONTACT_POINTS, the columns fall into several functional groups:

Common Use Cases and Queries

Typical scenarios include retrieving contact details for a customer during order entry, validating do-not-use restrictions before outbound communication, and extracting contact data for interfaces. The following query returns telephone contact points of a specific type for a given owner:

  • SELECT contact_point_id, owner_table_id, telephone_type, phone_country_code, phone_area_code, phone_number, phone_extension, primary_flag, do_not_use_flag
  • FROM aso_i_contact_points_v
  • WHERE contact_point_type = 'PHONE'
  • AND telephone_type = :p_telephone_type
  • AND owner_table_name = :p_owner_table
  • AND owner_table_id = :p_owner_id;

To list only active, preferred contact points, a report can filter on STATUS = 'A' and PRIMARY_FLAG = 'Y'. Because the view is a direct projection, no additional joins to HZ_CONTACT_POINTS are required, and ROWID may be retained for row-level identification. When TELEPHONE_TYPE values are reported, they correspond to the TCA lookup values configured for telephone classifications, so reporting queries should account for site-specific lookup customization.