Search Results oe_print_cont_points_v

Overview

OE_PRINT_CONT_POINTS_V is an APPS-owned reporting view in the Oracle Order Management (ONT) product family, validated and shipped with Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to expose the modes of communication recorded against a customer contact so that they can be printed on order-related output. The view is therefore a print-oriented projection rather than a transactional entity: it returns a read-only, filtered list of contact points that Oracle Order Management can render onto pick slips, order acknowledgements, packing slips, and similar documents where the customer's telephone, web, and telex details are required.

The view is significant to the "telex_number" search because TELEX_NUMBER is one of the fourteen columns it publishes. Telex remains a valid contact-point type in Oracle's Trading Community Architecture (TCA), and order documents in regions where telex is still used for commercial correspondence depend on this view to source the value. Because the view restricts CONTACT_POINT_TYPE to PHONE, WEB, and TLX only, it deliberately excludes other TCA contact mechanisms such as e-mail and fax, keeping the printed output concise.

Underlying Base Objects

The documented base object is HZ_CONTACT_POINTS, referenced through a synonym in the APPS schema. HZ_CONTACT_POINTS is the TCA table that stores every contact point for parties, locations, and contacts, discriminated by the OWNER_TABLE_NAME column. The view text is a simple, non-joined SELECT over that single table, applying three predicates:

• OWNER_TABLE_NAME = 'HZ_PARTIES' — restricting rows to contact points owned directly by a party record rather than by an account, site, or contact.
• STATUS = 'A' — returning only active contact points.
• CONTACT_POINT_TYPE IN ('PHONE', 'WEB', 'TLX') — limiting output to the three communication modes intended for printing.

No joins, aggregations, or functions are present, so the view inherits the partitioning and indexing characteristics of HZ_CONTACT_POINTS. It is a lightweight, deterministic projection; row counts and performance track the base table directly.

Key Columns

• CONTACT_POINT_ID — Primary key of the contact point in HZ_CONTACT_POINTS; the unique handle for the communication record.
• CONTACT_POINT_TYPE — PHONE, WEB, or TLX, indicating which mode of communication the row represents.
• STATUS — Always 'A' in this view, since inactive rows are filtered out.
• OWNER_TABLE_NAME / OWNER_TABLE_ID — Identify the owning entity; the view always returns 'HZ_PARTIES', and OWNER_TABLE_ID carries the corresponding party identifier.
• PRIMARY_FLAG — Indicates whether this is the primary contact point for its type, allowing printed documents to select a preferred number or address.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION, PHONE_LINE_TYPE — The component parts of a telephone contact point, including line type (for example, voice or fax-capable line).
• TELEX_NUMBER — The telex address for the party, populated when CONTACT_POINT_TYPE is TLX. This is the column sought by users searching on "telex_number".
• WEB_TYPE, URL — The web contact point classification and the associated uniform resource locator.

Common Use Cases and Queries

Typical usage is in Oracle Reports and BI Publisher layouts that print order or customer documents, and in ad hoc queries that need a consolidated contact list per party. A common retrieve for telephone and telex coverage is:

SELECT contact_point_id, contact_point_type, primary_flag, phone_country_code, phone_area_code, phone_number, phone_extension, telex_number, url
FROM oe_print_cont_points_v
WHERE owner_table_id = :party_id
ORDER BY contact_point_type, primary_flag DESC;

To isolate the telex information specifically:

SELECT owner_table_id, telex_number
FROM oe_print_cont_points_v
WHERE contact_point_type = 'TLX'
AND primary_flag = 'Y';

Because the view already filters for active party-owned phone, web, and telex entries, callers need not re-apply the STATUS or OWNER_TABLE_NAME predicates. When additional contact types such as e-mail or fax are required, HZ_CONTACT_POINTS must be queried directly, as this view intentionally omits them.