Results for “quote_org_id”

20 results




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

Overview

The APPS.OKL_AM_QUOTE_HEADER_UV view is a denormalized, user-facing reporting object within the Oracle Leasing and Finance Management (OKL) module, delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes quote header details that originate from the leasing quote transaction entity, joining the underlying quote record to its associated contract header, customer party, program, and lookup-derived descriptive values. The view is intended to consolidate, in a single queryable surface, the business attributes most commonly required for quote analysis, operational reporting, and downstream integration.

Because it is a view rather than a base table, OKL_AM_QUOTE_HEADER_UV presents no independent storage and carries no direct DML capability; it is documented as VALID under the APPS schema. Its primary value is that it resolves foreign-key relationships, performs lookup code translation, and asserts several computed measures through the OKL_AM_UTIL_PVT package, sparing report developers from replicating that logic manually.

Underlying Base Objects

The view is defined over the following documented base objects:

Key Columns

Each row is keyed by ID (the quote identifier) and exposes QUOTE_NUMBER together with QUOTE_TYPE and QUOTE_TYPE_DESCRIPTION, and QUOTE_STATUS with QUOTE_STATUS_DESCRIPTION via lookups. The KHR_ID and CONTRACT_NUMBER tie the quote to its contract; CUSTOMER and PRIVATE_LABEL identify the lessee and private-label party. QUOTE_ORG_ID carries the operating unit for multi-org filtering.

Financial and date attributes include TOTAL_ASSET_VALUE, TOTAL_RESIDUAL_VALUE, TOTAL_UNBILLED_RECEIVABLES, GAIN_LOSS, AMOUNT (computed by GET_QUOTE_AMOUNT), and ANTICIPATED_BILL_AMOUNT (GET_ANTICIPATED_BILL). DATE_EFFECTIVE_FROM and DATE_EFFECTIVE_TO bracket the quote's effective window, QUOTE_CREATION_DATE records creation, and DATE_ACCEPTED — the column associated with the search term "date_accepted" — captures the date the quote was accepted by the customer.

Common Use Cases and Queries

Typical scenarios include quote pipeline and aging reports, reconciliation of accepted quotes against contract headers, and extraction of quote values for integration. A representative query filtering accepted quotes within an operating unit is:

  • SELECT id, quote_number, quote_type_description, customer, date_accepted, amount FROM apps.okl_am_quote_header_uv WHERE org_id = :p_org_id AND date_accepted IS NOT NULL AND date_accepted BETWEEN :p_from AND :p_to ORDER BY date_accepted DESC;
  • Status-based reporting: filter by QUOTE_STATUS_DESCRIPTION or QUOTE_TYPE_DESCRIPTION rather than raw codes.
  • Joins to OKC_K_HEADERS_ALL_B or OKL_K_HEADERS on KHR_ID or CONTRACT_NUMBER for deeper contract-level analysis.

Because DATE_ACCEPTED may be null for open quotes, queries aggregating acceptance should apply an IS NOT NULL predicate. Consumption of this view in concurrent programs or BI Publisher data sets requires read privileges on OKL_TRX_QUOTES_ALL_B and the joined objects, since the view executes with the caller's privileges.