Results for “oks_contact_points_v”

24 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKS_CONTACT_POINTS_V view is a Service Contracts (OKS) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to display all contact points associated with a contact entered through the Service Authoring form. In practical terms, it exposes the phone numbers, email addresses, and fax numbers held against party-level contact records so that service contract authoring, service fulfillment, and downstream notification processes can retrieve communication details for a given contact.

This view is a filtered projection rather than a stored entity. It restricts the broader contact-point data set to records whose owner table is HZ_PARTIES and whose CONTACT_POINT_TYPE is one of PHONE, EMAIL, or FAX. The view also reshapes the data by suppressing phone-related attributes for email rows, so that consumer logic does not have to interpret phone columns when the contact point is an email address. This design makes it a convenient integration and reporting layer for Service Contracts functionality that needs party contact points.

Underlying Base Objects

The documented view definition selects from a single referenced object: OKX_CONTACT_POINTS_V, itself a view in the APPS schema. OKX_CONTACT_POINTS_V is the Contact Points descriptive flexfield/extension view that, in a standard configuration, reads the contact point records managed by Oracle Trading Community Architecture (TCA) via HZ_CONTACT_POINTS. In the ETRM metadata the only referenced base object recorded is OKX_CONTACT_POINTS_V; OKS_CONTACT_POINTS_V does not join additional tables directly.

The relationship is therefore a layered one: TCA contact point tables supply the physical rows, OKX_CONTACT_POINTS_V exposes them with their flexfield context, and OKS_CONTACT_POINTS_V narrows that set to party-owned phone, email, and fax contact points for use by the Service Contracts module. Because the view is defined over another view rather than a table, its contents depend on TCA data integrity and on the compilation status of OKX_CONTACT_POINTS_V.

Key Columns

  • CONTACT_POINT_TYPE — The kind of contact point: PHONE, EMAIL, or FAX. This is the most frequently queried column and is the filter that defines the view's scope.
  • OWNER_TABLE_ID — The identifier of the owning record, used with the owner table name to associate the contact point with a specific party. With the view's OWNER_TABLE_NAME = 'HZ_PARTIES' filter, this is the PARTY_ID.
  • PHONE_LINE_TYPE — The line type classification for the contact point, distinguishing the technology or purpose of the phone or fax line.
  • EMAIL_ADDRESS — The email address for email contact points.
  • PHONE_AREA_CODE — The area code, returned as NULL for email rows by the DECODE logic in the view definition.
  • PHONE_COUNTRY_CODE — The country dialing code, also NULL for email rows.
  • PHONE_NUMBER — The phone or fax number, NULL for email rows.
  • PHONE_EXTENSION — The extension associated with the number, NULL for email rows.

Common Use Cases and Queries

Typical consumers use this view to populate contact selection lists in Service Authoring, to resolve contact details during contract generation, and to drive outbound notifications. A common reporting query retrieves all contact points for a party:

  • SELECT contact_point_type, email_address, phone_country_code, phone_area_code, phone_number, phone_extension FROM oks_contact_points_v WHERE owner_table_id = :party_id;
  • SELECT owner_table_id, email_address FROM oks_contact_points_v WHERE contact_point_type = 'EMAIL';
  • SELECT owner_table_id, phone_number FROM oks_contact_points_v WHERE contact_point_type IN ('PHONE','FAX');

Because phone attributes are null for email rows, queries that select phone columns should filter on CONTACT_POINT_TYPE to avoid returning sparse results. The view exposes no CONTACT_POINT_ID or primary key column, so joins to contract or party tables must be performed on OWNER_TABLE_ID. No DML should be attempted against this object; it is strictly read-only.