Search Results contact_details

Overview

OKL_AM_CONTACT_POINTS_UV is a view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the OKL product family, Oracle Leasing and Finance Management, and presents contact point information for leasing parties in a flattened, reporting-friendly form. The "UV" suffix conventionally denotes a user-facing validation or reporting view intended for consumption by application logic, concurrent programs, and ad hoc queries rather than for direct DML operations. Because the object is documented with a VALID status, it can be relied upon as a supported read interface in both R12.1.1 and R12.2.2.

Its principal design role is to expose telephone and electronic contact data — the type of information end users seek when searching for a term such as contact_phone_number — without requiring callers to join or decode the underlying Trading Community Architecture (TCA) contact structures themselves. The view isolates active contacts belonging to HZ_PARTIES records and normalizes them into leasing-specific column names.

Underlying Base Objects

The view is defined exclusively over a single documented base object: OKX_CONTACT_POINTS_V, itself a view in the OKX (Oracle Contracts) schema. The defining query selects from this source with an alias of HZC and applies two filters:

• HZC.OWNER_TABLE_NAME = 'HZ_PARTIES' — restricts the result set to contact points whose owning entity is a party record, excluding contacts owned by other TCA entities.
• HZC.STATUS = 'A' — restricts to active contact points only, omitting inactive or logically deleted entries.

OKX_CONTACT_POINTS_V in turn resolves to the TCA contact point infrastructure, including HZ_CONTACT_POINTS and HZ_PARTIES. No tables are directly referenced by OKL_AM_CONTACT_POINTS_UV; all lineage flows through the OKX view, which means any change to that intermediate view is inherited by this object.

Key Columns

The view exposes ten columns. The following are the most significant:

• CONTACT_PARTY_ID (from OWNER_TABLE_ID) — the party identifier of the contact's owner; used to join back to HZ_PARTIES.
• CONTACT_CONTACT_POINT_ID — the TCA contact point identifier, the unique key for the contact method.
• CONTACT_CONTACT_POINT_TYPE — the classification of the contact point, for example phone, email, or fax.
• CONTACT_PHONE_NUMBER — the raw telephone number without formatting.
• CONTACT_PHONE_AREA_CODE and CONTACT_PHONE_EXTENSION — the area code and extension components stored separately in TCA.
• CONTACT_EMAIL_ADDRESS — the electronic mail address associated with the contact point.
• CONTACT_DETAILS — a concatenated display string built from email address, area code in parentheses, phone number, and extension prefixed with "EXT.". The DECODE and SIGN functions ensure that parentheses and extension text appear only when the corresponding components are populated.
• OWNER_TABLE_ID — a duplicate exposure of the owning party identifier.

Common Use Cases and Queries

The view is typically used to retrieve formatted contact information for a leasing party, to list all active phone numbers for a customer, or to supply data to correspondence and notification processes. A representative query returning phone details for a specific party is:

• SELECT contact_party_id, contact_phone_area_code, contact_phone_number, contact_phone_extension FROM okl_am_contact_points_uv WHERE contact_party_id = :party_id;
• SELECT contact_party_id, contact_details FROM okl_am_contact_points_uv WHERE contact_contact_point_type = 'PHONE';
• SELECT o.contact_party_id, o.contact_details FROM okl_am_contact_points_uv o, hz_parties p WHERE o.contact_party_id = p.party_id AND p.party_name LIKE :name;

Because the view is read-only and filters to active HZ_PARTIES contacts, it is safe to use in reports and integrations without additional status predicates, though callers should still restrict results by party to avoid full scans on large TCA installations.