Results for “okl_quote_reason”

48 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OKL_AM_RESTRUCTURE_QUOTES_UV is a reporting view in the Oracle E-Business Suite Lease and Finance Management (formerly Oracle Lease Management, OKL) module, part of the ETRM application family. It presents a consolidated, human-readable projection of restructuring quotes — quotes that carry a quote type code beginning with "RES" in the OKL_TRX_QUOTES_V transaction quotes view. Rather than exposing raw lookup codes, the view joins four instances of FND_LOOKUPS to translate internal status, type, reason, and acceptance flags into their descriptive MEANING values, producing a denormalized result set suitable for reporting, inquiry screens, and downstream integration. The "UV" suffix denotes a user-facing validation view, typically consumed by Oracle Forms, OAF pages, or BI Publisher reports rather than by transactional processing logic. The view also left-outer-joins to the contract header base table OKC_K_HEADERS_ALL_B, so restructuring quotes remain visible even when no corresponding contract header record exists. This object is a key reference point for users searching on "okl_quote_reason," since it exposes the QUOTE_REASON column derived from the OKL_QUOTE_REASON lookup type.

Underlying Base Objects

The documented base objects for this view are FND_LOOKUPS (VIEW), OKC_K_HEADERS_ALL_B (SYNONYM), OKL_TRX_QUOTES_V (VIEW), and the FND_GLOBAL package. The primary driver is OKL_TRX_QUOTES_V, aliased OTQ, which supplies the quote header attributes. OKC_K_HEADERS_ALL_B, aliased OKF, is joined on OTQ.KHR_ID = OKF.ID using an outer join (+), providing contract number, start date, and end date. Four aliased instances of FND_LOOKUPS — FL1, FL2, FL3, and FL4 — resolve lookup meanings against the lookup types OKL_QUOTE_STATUS, OKL_QUOTE_TYPE, OKL_QUOTE_REASON, and OKL_YES_NO respectively. The filter on QTP_CODE LIKE 'RES%' restricts the result set to restructuring quote types only. FND_GLOBAL is referenced for session context such as organization and user identification, which supports multi-org security (ORG_ID is exposed as a column) and auditability.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting outstanding restructure quotes by reason, analyzing accepted versus rejected offers, and feeding external pricing or approval workflows. A sample query retrieving active restructure quotes with their reasons is:

  • SELECT quote_number, quote_type, quote_status, quote_reason, rent_amount, term FROM apps.okl_am_restructure_quotes_uv WHERE accepted_yn = 'N' AND approved_yn = 'N';
  • SELECT quote_reason, COUNT(*) FROM apps.okl_am_restructure_quotes_uv GROUP BY quote_reason;
  • SELECT contract_number, quote_number, date_restructure_start, date_restructure_end FROM apps.okl_am_restructure_quotes_uv WHERE org_id = :p_org_id;

Because the view decodes lookups at query time, results reflect current FND_LOOKUPS definitions, and any ad-hoc lookup value change propagates immediately to reports. Queries should include ORG_ID predicates to honor multi-org access, and joins to OKC_K_HEADERS_ALL_B should account for the outer join when contracts are not yet created.