Search Results web_type




Overview
Explore in AI Chat

Overview

APPS.OE_PRINT_CONT_POINTS_V is a reporting and integration view in Oracle E-Business Suite that exposes active contact point records associated specifically with parties. Positioned within the Oracle Order Management (OE) schema naming convention, the view is designed to support printing, correspondence, and outbound communication processes that require phone, web, and telex contact information. Because the view restricts its output to contact points whose owner is a party and whose status is active, consumers of the view receive a pre-filtered, ready-to-use result set without needing to apply the same predicates themselves. This makes it particularly useful in reporting contexts, interface programs, and concurrent requests where contact details must be retrieved reliably and consistently.

Underlying Base Objects

The view is defined over a single referenced base object, HZ_CONTACT_POINTS, which is exposed to the APPS schema through a synonym. HZ_CONTACT_POINTS is the central TCA (Trading Community Architecture) table that stores all contact point records across parties, locations, and organizations. OE_PRINT_CONT_POINTS_V narrows that broad population by applying three documented predicates in its defining query:

  • OWNER_TABLE_NAME = 'HZ_PARTIES' — restricts the result set to contact points owned by party records, excluding those owned by other entities such as locations or organizations.
  • STATUS = 'A' — restricts to active contact points only, filtering out inactive or logically deleted records.
  • CONTACT_POINT_TYPE IN ('PHONE', 'WEB', 'TLX') — limits the result set to telephone, web, and telex contact point types, excluding other classifications such as email or fax where separately modeled.

Because it is a simple, non-aggregated view over a synonym, it inherits the columns and data types of HZ_CONTACT_POINTS directly and introduces no additional joins or derivations.

Key Columns

The view projects a defined column list from HZ_CONTACT_POINTS. The principal columns include:

  • CONTACT_POINT_ID — the unique primary key identifier for each contact point record.
  • CONTACT_POINT_TYPE — the classification of the contact point; limited by the view to PHONE, WEB, or TLX.
  • STATUS — the record status; the view exposes only active ('A') records.
  • OWNER_TABLE_NAME / OWNER_TABLE_ID — identify the owning entity; the view fixes the owner table to HZ_PARTIES and carries the corresponding party identifier.
  • PRIMARY_FLAG — indicates whether the contact point is the primary one for its owner and type.
  • PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION, PHONE_LINE_TYPE — the component fields describing telephone contact points.
  • TELEX_NUMBER — the telex identifier for telex-type contact points.
  • WEB_TYPE, URL — the classification and address for web-type contact points. The WEB_TYPE column, which the user searched for, distinguishes categories of web contact points and is the field most relevant to web-based correspondence and integration scenarios.

Common Use Cases and Queries

Typical uses include retrieving phone or web contact information for a party during order printing, generating outbound correspondence, and populating integration payloads. A representative query retrieves all web contact points for a specific party:

  • SELECT contact_point_id, web_type, url, primary_flag FROM apps.oe_print_cont_points_v WHERE owner_table_id = :party_id AND contact_point_type = 'WEB';
  • SELECT contact_point_id, phone_number, phone_area_code, primary_flag FROM apps.oe_print_cont_points_v WHERE owner_table_id = :party_id AND contact_point_type = 'PHONE' AND primary_flag = 'Y';

Because the view already enforces the party-owner and active-status filters, queries against it remain concise while returning only operationally valid contact points suitable for printing and communication processes.