Search Results contact_person




Overview
Explore in AI Chat

Overview

OKL_CS_LC_HEADER_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Lease and Finance Management) product family. It consolidates lease contract header information with associated customer, contact, and phone details into a single denormalized row per lease contract. In release 12.1.1 and 12.2.2 the view carries a VALID status and is exposed as a reporting and integration surface for lease contract header data, typically consumed by custom concurrent programs, BI Publisher reports, Oracle Discoverer workbooks, and outbound interfaces. Because the view joins translated contract headers, translated statuses, and Trading Community Architecture (TCA) party data, it is most useful when a flattened, presentation-ready view of a lease contract and its primary contact is required, rather than when transactional updates are performed.

Underlying Base Objects

The view is defined over eight documented base objects: OKC_K_HEADERS_B, OKC_K_HEADERS_TL, OKC_STATUSES_TL, OKL_K_HEADERS, OKL_PRODUCTS, HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CONTACT_POINTS. The core contract record is sourced from OKC_K_HEADERS_B (CHR), which supplies contract number, dates, PO number, currency, inventory organization, status code, and customer account identifier. OKL_K_HEADERS (KHR) extends that record with lease-specific attributes and links to OKL_PRODUCTS (PDT) for the product name. Translated descriptions come from OKC_K_HEADERS_TL (CHRT), and translated status meanings from OKC_STATUSES_TL (STST); both are filtered to USERENV('LANG'). The customer and contact side is drawn from TCA: HZ_CUST_ACCOUNTS (HCA) resolves the account to a party, HZ_PARTIES (HZP) supplies the party, contact person, address, and email, and HZ_CONTACT_POINTS (HCP) supplies phone-related attributes. Notably, the outer joins against HZ_CONTACT_POINTS are constrained to STATUS = 'A', PRIMARY_FLAG = 'Y', and CONTACT_POINT_TYPE = 'PHONE', so the view returns at most the active primary phone contact point for each party.

Key Columns

The view exposes twenty-three columns. CONTRACT_NUMBER, START_DATE, END_DATE, DESCRIPTION, CURRENCY_CODE, ORG_ID, and CONTRACT_ID identify the lease contract. CONTRACT_STATUS provides the translated status meaning, and PRODUCT_NAME identifies the leased product. Customer-facing columns include CUSTOMER (party name), CONTACT_PERSON (concatenated person name), TITLE, ADDRESS, EMAIL, and ORGANIZATION_NAME_PHONETIC. Phone columns are PHONE_COUNTRY, PHONE_AREA, PHONE_NUMBER, and PHONE_EXTENSION. The column of interest to users searching on "fax_number" is FAX_NUMBER, which the view text maps from HCP.TELEX_NUMBER on HZ_CONTACT_POINTS. This is a legacy TCA convention: TELEX_NUMBER is the underlying storage attribute historically repurposed for fax numbers, so FAX_NUMBER reflects the primary phone contact point's telex/fax value. Where no qualifying contact point row exists, FAX_NUMBER and the other HCP-derived columns return NULL. PARTY_ID and CUST_ACCOUNT_ID provide the TCA identifiers for downstream joins.

Common Use Cases and Queries

Typical uses include extracting lease contract details for customer correspondence, producing contact sheets that include fax numbers, and joining lease headers to downstream billing or asset data. The following query lists active lease contracts with their primary contact fax number:

  • SELECT contract_number, customer, contact_person, fax_number, phone_number FROM okl_cs_lc_header_uv WHERE fax_number IS NOT NULL;
  • SELECT contract_number, product_name, contract_status, start_date, end_date FROM okl_cs_lc_header_uv WHERE org_id = :p_org_id;
  • SELECT h.contract_number, h.customer, h.fax_number FROM okl_cs_lc_header_uv h, okl_k_lines_v l WHERE h.contract_id = l.contract_id;

Because the view applies outer joins with restrictive filter conditions on the contact point, callers should not expect multiple fax numbers per contract. When a complete list of all contact points is required, query HZ_CONTACT_POINTS directly, joining on PARTY_ID. Implementations upgrading from 12.1.1 to 12.2.2 should also verify that the synonym chain resolves to the ONLINE (or appropriate edition) TCA objects in their environment.