Search Results install_at




Overview
Explore in AI Chat

Overview

OKL_LA_INSTALL_SITE_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management. The view exists to populate the list of values (LOV) page that presents "install_at" party site options to the user. In practice, it drives the selection of a customer site to which leased equipment is to be installed or delivered during the creation and maintenance of a lease contract.

The view is not an operational base table; it is a read-only, denormalized projection assembled from trading community and contract core tables. Its purpose is to expose a compact result set of party sites that carry the INSTALL_AT site use type, filtered to the lessee role of a specific contract, so that the OKL forms layer can present them in a picklist. Because the view resolves address formatting and relationship joins at runtime, it centralizes that logic and keeps the UI layer simple. Developers and report writers use it when a query needs to reproduce exactly the same candidate install-at sites that the Lease Management form offers to an end user.

Underlying Base Objects

Documented ETRM metadata lists the following referenced objects, all accessed through APPS synonyms: HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS, HZ_CUST_ACCT_SITES, OKC_K_HEADERS_B, OKC_K_PARTY_ROLES_B, and the package ARP_ADDR_LABEL_PKG.

  • HZ_PARTY_SITES — holds each party site and its name; supplies PARTY_ID and LOCATION_ID linkage.
  • HZ_PARTY_SITE_USES — classifies a site by use; the view keeps only SITE_USE_TYPE = 'INSTALL_AT'.
  • HZ_LOCATIONS — the raw address components passed to the formatting package.
  • HZ_CUST_ACCT_SITES — ties the party site to a customer account, which in turn must match the contract's account.
  • OKC_K_HEADERS_B — the contract header, joined on DNZ_CHR_ID and CUST_ACCT_ID.
  • OKC_K_PARTY_ROLES_B — the contract party role assignment, restricted to the LESSEE role.
  • ARP_ADDR_LABEL_PKG — its FORMAT_ADDRESS function renders a single-line description from the HZ_LOCATIONS columns.

The join chain enforces that the site returned belongs to the lessee of the contract selected, that the site is linked to the contract's customer account, and that the site carries the INSTALL_AT use. The roles join also filters on JTOT_OBJECT1_CODE = 'OKX_PARTY' and OBJECT1_ID2 = '#', distinguishing the party role records relevant to this context.

Key Columns

  • PARTY_SITE_ID — mapped from HPSU.PARTY_SITE_USE_ID; the value returned to the form when the user picks a site and the identifier used to join back to the site use.
  • CHR_ID — mapped from CPLB.DNZ_CHR_ID; the contract identifier, allowing the LOV to be scoped to the contract currently in context.
  • NAME — mapped from HPS.PARTY_SITE_NAME; the short site name displayed in the list.
  • DESCRIPTION — the first 80 characters of the formatted address produced by ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS, shown alongside the name.

Common Use Cases and Queries

Typical uses include confirming which install-at sites the OKL form will offer for a given lease, backfilling reports that must show delivery/install destinations per contract, and diagnosing why a site does not appear in the LOV (for example, because its site use is not INSTALL_AT or its customer account is not the contract's account).

A representative query filters by contract:

  • SELECT PARTY_SITE_ID, CHR_ID, NAME, DESCRIPTION FROM APPS.OKL_LA_INSTALL_SITE_UV WHERE CHR_ID = :contract_id;

To confirm whether a specific site would be offered, query by site identifier:

  • SELECT NAME, DESCRIPTION FROM APPS.OKL_LA_INSTALL_SITE_UV WHERE CHR_ID = :contract_id AND PARTY_SITE_ID = :site_use_id;

Because the view already restricts to lessee party sites with the INSTALL_AT use and a matching customer account, no additional role or site-use filtering is required in the calling SQL.