Search Results contact_party_name




Overview
Explore in AI Chat

Overview

OKL_AM_CONTACTS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Leasing and Finance Management) product family. The view exposes contact and party relationship information drawn from Oracle's Trading Community Architecture (TCA) party model, filtered and reshaped for consumption by leasing and finance management reporting and integration flows. It provides a denormalized, business-friendly projection of contact data that abstracts the complexity of the underlying TCA relationship tables.

Because it is a view rather than a table, OKL_AM_CONTACTS_UV carries no physical storage of its own. It functions primarily as a reporting and integration surface, allowing inquiries, concurrent programs, and external interfaces to retrieve contact party details for a customer without navigating the full TCA relationship schema. The view is marked VALID in the ETRM metadata and is available in both Oracle EBS 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over a single documented base object: OKX_PARTY_CONTACTS_V, itself a view in the APPS schema. OKL_AM_CONTACTS_UV aliases this source as HZPS and performs a straightforward SELECT projection rather than a join, so its row cardinality and filtering behaviour are inherited entirely from OKX_PARTY_CONTACTS_V.

The prefix "OKX" indicates an Oracle Contracts/TCA integration view, and the "HZPS" alias reflects the underlying HZ (TCA) party schema lineage. Practically, this means OKL_AM_CONTACTS_UV resolves — through OKX_PARTY_CONTACTS_V — to TCA party relationship data, including the relationship between a contact party and its associated customer party. No tables are referenced directly; all access is mediated by the intermediate view.

Key Columns

  • PARTY_RELATIONSHIP_ID — The unique identifier of the party relationship record, sourced from HZPS.PARTY_RELATIONSHIP_ID. This is the primary key of the view's row and links back to the TCA relationship definition.
  • PARTY_RELATIONSHIP_TYPE — The classification of the relationship (for example, contact-of or employee-of). It qualifies how the contact party is associated with the customer party.
  • CONTACT_PARTY_ID — The party identifier of the contact, mapped from HZPS.ID1. Use this to resolve the contact's party record in TCA.
  • CONTACT_PARTY_TYPE — The party type of the contact (such as PERSON or ORGANIZATION), sourced from HZPS.PARTY_TYPE.
  • CONTACT_PARTY_NAME — The descriptive name of the contact, derived from HZPS.DESCRIPTION. This is the column most often searched by users, commonly surfaced as "contact_party_name".
  • CUSTOMER_PARTY_ID — The party identifier of the associated customer, mapped from HZPS.PARTY_ID, identifying the account to which the contact belongs.

Common Use Cases and Queries

A frequent requirement is locating a contact by name, which is why "contact_party_name" is a common search term. The following query retrieves all contacts whose name begins with a given value:

  • SELECT contact_party_id, contact_party_name, contact_party_type, customer_party_id FROM okl_am_contacts_uv WHERE contact_party_name LIKE 'SMITH%';

To list all contacts belonging to a specific customer, filter on the customer party identifier:

  • SELECT contact_party_id, contact_party_name, party_relationship_type FROM okl_am_contacts_uv WHERE customer_party_id = :p_customer_party_id;

For integration extracts, the view supplies a compact source for populating external systems with leasing contact data. Joining CONTACT_PARTY_ID or CUSTOMER_PARTY_ID back to TCA tables (for example, HZ_PARTIES) enriches the result with addresses, email, and phone details. Because the view inherits its logic entirely from OKX_PARTY_CONTACTS_V, performance depends on that underlying view's query plan; standard TCA indexing on party identifiers and relationship keys generally supports efficient access. No DML should be attempted against this view.