Search Results okl_request_type




Overview
Explore in AI Chat

Overview

The view APPS.OKL_LEASE_RENEWALS_ALL_UV is a user-facing (UV) database view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the data stored in the transaction request table OKL_TRX_REQUESTS, presenting lease restructuring, renewal, and renegotiation requests in a denormalized, report-ready format. The view consolidates technical identifiers, monetary terms, dates, and descriptive lookup meanings into a single queryable object, allowing reporting tools, concurrent programs, and integration interfaces to retrieve lease renewal information without reconstructing the joins against lookup and user tables.

Because the view is owned by APPS and built on a multi-org style naming convention with the _ALL_UV suffix, it is intended for use in both single-org and multi-org (MOAC) reporting contexts within EBS 12.1.1 and 12.2.2. It does not perform row-level security itself; consumers must apply appropriate operating unit or business unit filters where relevant.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKL_TRX_REQUESTS (SYNONYM) — the primary transactional table holding lease renewal, restructuring, and refinancing request records. Aliased as TRQ.
  • FND_LOOKUPS (VIEW) — joined twice, as STAT and TYPE, to decode the request status and request type codes into readable meanings.
  • FND_USER (SYNONYM) — aliased as USR, joined on TRQ.LAST_UPDATED_BY = USR.USER_ID to expose the requesting user's name.
  • FND_GLOBAL (PACKAGE) — referenced in view metadata for session and security context, consistent with MOAC-enabled views.

Two outer joins to FND_LOOKUPS resolve codes using the lookup types OKL_REQUEST_STATUS and OKL_REQUEST_TYPE, so the view always returns the request rows while simultaneously providing human-readable status and type descriptions.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on pending renewals, tracking restructure effective dates, and feeding downstream calculations. A representative query selecting by restructure date:

SELECT request_number,
       request_status,
       request_type,
       restructure_date,
       start_date,
       end_date,
       rent,
       currency_code,
       requested_by
FROM   apps.okl_lease_renewals_all_uv
WHERE  restructure_date BETWEEN :from_date AND :to_date
AND    request_type = 'RENEWAL'
ORDER BY restructure_date;

Because the view exposes both raw codes and decoded meanings, it supports both analytical reporting and integration scenarios where codes are required for programmatic processing. All joins to lookups and users are pre-built, minimizing development effort and ensuring consistent interpretation of lease renewal data across the enterprise.