Search Results okx_contact_points_v




Overview
Explore in AI Chat

Overview

OKX_CONTACT_POINTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKX product family, Contracts Integration, which supplies the data structures used when contract data is exchanged with external systems and downstream applications. The view presents a filtered and denormalized projection of contact point records, exposing the identifiers, contact mechanisms, and status attributes required by integration and reporting logic without forcing callers to reference the full Oracle Trading Community Architecture (TCA) model.

The view is deliberately restricted. Its defining predicate is HCP.CONTENT_SOURCE_TYPE = 'USER_ENTERED', which means only contact points created directly by users are returned. Records generated automatically by import processes, third-party feeds, or system-seeded sources are excluded. This restriction makes the view well suited to business-facing reports and to integration extracts where only manually maintained contact data is meaningful.

Underlying Base Objects

The view is defined over a single base object, HZ_CONTACT_POINTS, accessed in the APPS schema through a synonym. HZ_CONTACT_POINTS is the TCA table that stores the individual contact points — e-mail addresses, telephone numbers, and related entries — associated with a party, party site, or location. Each contact point is attributed to a parent record through the OWNER_TABLE_NAME and OWNER_TABLE_ID pair, which forms a polymorphic foreign key rather than a fixed relational join. Because the view selects directly from this table with one filter and no joins, its column list mirrors the base table columns, and its row count is a strict subset of HZ_CONTACT_POINTS.

Key Columns

The view exposes fifteen columns. Because the article was retrieved by a search on "email_format," the e-mail-related columns warrant particular attention:

  • CONTACT_POINT_ID — primary identifier of the contact point record.
  • CONTACT_POINT_TYPE — classifies the record, for example EMAIL or PHONE.
  • EMAIL_FORMAT — indicates the format or encoding applicable to the e-mail address, such as plain text or HTML.
  • EMAIL_ADDRESS — the actual e-mail address stored for the contact point.
  • STATUS — lifecycle status of the contact point (for example active or inactive).
  • OWNER_TABLE_NAME / OWNER_TABLE_ID — identify the parent entity that owns the contact point.
  • PRIMARY_FLAG — denotes whether the contact point is the primary one for its owner.
  • TELEPHONE_TYPE, PHONE_AREA_CODE, PHONE_COUNTRY_CODE, PHONE_NUMBER, PHONE_EXTENSION, PHONE_LINE_TYPE — telephone-specific attributes.
  • CONTENT_SOURCE_TYPE — the source of the record; in this view it is always USER_ENTERED.

Common Use Cases and Queries

Typical consumers use the view to validate, extract, or reconcile user-maintained contact data during contract integration. A frequent requirement is confirming which e-mail format convention applies to a given address:

  • Retrieve all user-entered e-mail contact points:
    SELECT contact_point_id, email_address, email_format, primary_flag
    FROM okx_contact_points_v
    WHERE contact_point_type = 'EMAIL';
  • Locate primary e-mail addresses for a specific owner record:
    SELECT contact_point_id, email_address, email_format
    FROM okx_contact_points_v
    WHERE owner_table_name = :p_owner_table
    AND owner_table_id = :p_owner_id
    AND primary_flag = 'Y';
  • Audit format usage across the integration:
    SELECT email_format, COUNT(*)
    FROM okx_contact_points_v
    GROUP BY email_format;

Because the view carries no joins and a single static predicate, these queries execute efficiently against HZ_CONTACT_POINTS and are suitable for concurrent-program extracts and ad hoc analysis alike.