Search Results date_last_inspection




Overview
Explore in AI Chat

Overview

OKL_LA_REAL_ESTATE_UV is a user interface view owned by the APPS schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKL product family — Leasing and Finance Management — and serves as the presentation-layer data source for the asset real estate page. The name suffix "UV" denotes a "user view," a convention in Oracle EBS indicating that the object is designed to feed a specific OAF or Forms-based UI page rather than to serve as a general-purpose reporting entity.

Functionally, the view flattens a single row per lease line into a horizontally oriented record describing real-estate-specific attributes: physical characteristics of the property (year built, square footage, occupancy, coverage), valuation and financing data (appraisal value, refinance amount, bond equivalent yield, weighted average life), inspection dates, and deal qualification flags. Because the view is bound to the transaction UI, it is also accessible for ad-hoc SQL reporting against the APPS schema, which makes it a frequent target for extract and integration programs that need real-estate attributes at the contract line level.

Underlying Base Objects

The documented view text confirms that OKL_LA_REAL_ESTATE_UV selects exclusively from OKL_K_LINES, aliased KLE, and does not perform any join itself. However, the ETRM metadata records the broader dependency set referenced by the OKL real estate page: OKC_K_LINES_B, OKC_K_LINES_TL, OKC_K_PARTY_ROLES_B, OKL_K_LINES, and PO_VENDORS (itself a view). OKL_K_LINES is the leasing-specific extension table that stores the real-estate attribute columns surfaced here, while OKC_K_LINES_B and OKC_K_LINES_TL hold the base contract line definition and its translated (TL) descriptive text. OKC_K_PARTY_ROLES_B supplies the party role assignments — tenants, lessors, and related parties — used on the page, and PO_VENDORS provides supplier context for the associated parties.

In practice, real-estate attributes are stored in OKL_K_LINES only for lines where the line type or price code (PRC_CODE) identifies a real-estate asset, so the view is sparse by design; rows for non-real-estate lines carry nulls in the real-estate columns.

Key Columns

The view exposes nineteen columns, most of them numeric values cast with TO_CHAR so the UI can present them without implicit formatting:

Common Use Cases and Queries

Typical uses include real-estate portfolio reporting, inspection scheduling, valuation tracking, and data validation before migrating lease contracts. Because YEAR_BUILT is stored as a number in OKL_K_LINES but rendered as text by the view, filtering on it requires either an implicit numeric conversion or a TO_NUMBER wrapper.

  • List real-estate lines built after a given year: 
    SELECT id, year_built, gross_square_footage, appraisal_value
FROM   apps.okl_la_real_estate_uv
WHERE  TO_NUMBER(year_built) >= 2000
ORDER  BY id;
  • Identify properties due for inspection: 
    SELECT id, date_last_inspection, date_next_inspection_due
FROM   apps.okl_la_real_estate_uv
WHERE  date_next_inspection_due BETWEEN SYSDATE AND SYSDATE + 90;
  • Summarize secured versus unsecured real-estate exposure: 
    SELECT secured_deal_yn, COUNT(*), SUM(TO_NUMBER(amount))
FROM   apps.okl_la_real_estate_uv
GROUP  BY secured_deal_yn;

When joining to contract headers, link BACK to OKL_K_LINES or OKC_K_LINES_B on ID to obtain contract number, line number, and party role detail supplied by the companion OKC base objects.