Results for “complete_contract_number”

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

Overview

OKI_CONTACT_POINTS_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Contracts Intelligence (OKI) product family. Its stated purpose is to expose contact point information — email addresses, telephone numbers, and related attributes — for contacts associated with contracts. The view consolidates contact point records held in the Oracle Trading Community Architecture (TCA) contact point table (HZ_CONTACT_POINTS) with contract header data from the sales/contract header structure and lookup translations from AR_LOOKUPS.

The view is intended for reporting and integration scenarios where an application or inquiry needs a flat, denormalized presentation of contract-linked telephone and email details. Because it joins contract headers to their associated contacts and then to each contact's active contact points, it allows a single query to return, for example, the primary phone number of the contact attached to a given contract number. Queries referencing business phone information for a supplier, partner, or internal contact associated with a contract are a typical pattern. Note that results depend on the contract contacts being maintained in OKC_CONTACTS and on the contact points being active, user-entered, and not flagged as do-not-use.

Underlying Base Objects

The view is defined over four base objects, all in the APPS schema context:

• HZ_CONTACT_POINTS (CPT) — the TCA contact point table holding email and phone records, including type, format, country/area code, number, and extension.
• AR_LOOKUPS (ALP) — the lookup table supplying the meaning (translation) for the phone line type code, restricted to LOOKUP_TYPE = 'PHONE_LINE_TYPE'.
• OKC_CONTACTS (CTT) — the contract contacts table linking a contact identity to a contract header through OBJECT1_ID1 and DNZ_CHR_ID.
• OKI_SALES_K_HDRS (SHD) — the contract/sales header source providing contract ID, contract number, modifier, and complete contract number.

The join path runs from the contract header (SHD) through OKC_CONTACTS (CTT), then to HZ_CONTACT_POINTS (CPT) via OWNER_TABLE_ID, and finally to AR_LOOKUPS (ALP) for the phone type meaning. Explicit filter predicates restrict the result set to non-do-not-use ('N'), active ('A') contact points owned by HZ_PARTIES and populated via user entry.

Key Columns

• CONTACT_POINT_ID — primary identifier of the contact point record.
• CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, COMPLETE_CONTRACT_NUMBER — contract identification attributes derived from the header source.
• CONTACT_ID — identifier of the contact (OWNER_TABLE_ID from the contact point).
• CONTACT_POINT_TYPE — indicates whether the record is a phone or email contact point.
• EMAIL_FORMAT, EMAIL_ADDRESS — email format flag and the email address itself.
• PHONE_TYPE, PHONE_TYPE_MEANING — the phone line type code and its decoded meaning from AR_LOOKUPS.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — the decomposed telephone number fields for international and domestic dialing formats.
• PRIMARY_FLAG — indicates whether the contact point is the primary one for the contact.
• CREATION_DATE, LAST_UPDATE_DATE — audit columns for record lifecycle tracking.

Common Use Cases and Queries

Typical uses include contract contact directories, telephone and email extracts for integrations, and ad hoc reports that need to resolve a contract number to a reachable contact. To retrieve all phone contact points for a specific contract:

• SELECT contract_number, contact_id, phone_type_meaning, phone_country_code, phone_area_code, phone_number, phone_extension FROM oki_contact_points_v WHERE contract_number = :p_contract_number AND contact_point_type = 'PHONE' ORDER BY primary_flag DESC;
• SELECT contract_number, contact_id, email_address FROM oki_contact_points_v WHERE contact_point_type = 'EMAIL' AND primary_flag = 'Y';

Because the view filters on active, non-do-not-use, user-entered contact points owned by parties, developers should expect only currently valid contact details to appear. Joins to HZ_PARTIES or HZ_PERSON_PROFILES on CONTACT_ID can enrich results with contact name and party information when a fuller contact directory is required.