Search Results qst_code




Overview
Explore in AI Chat

Overview

The view APPS.OKL_AM_QUOTE_AMT_SUMMARY_UV is a reporting and integration object within the Oracle E-Business Suite Lease and Finance Management (formerly Oracle Lease Management, ETRM) module. Its purpose is to aggregate monetary amounts recorded against quote lines for a given quote, presenting a consolidated amount summary keyed by quote number, quote line type, and the associated quote status and type codes. The suffix _UV denotes a user or UI-oriented view, typically consumed by Oracle Forms or OAF-based ETRM quote entry screens and by concurrent/reporting queries that need a summarized monetary picture of a quote without drilling into each transaction line individually.

The view is central to quote amount rollup reporting, combining line-level amounts across line types while explicitly excluding certain internal accounting line codes and separately re-injecting tax amounts through a union branch. This design allows the view to present a single coherent amount per quote line type alongside tax totals, each aligned to the same lookup-driven description.

Underlying Base Objects

The view is defined over a multi-table join and union construct. Documented base and referenced objects include:

  • OKL_TRX_QUOTES_B — the primary quote header table, supplying quote number, status code (QST_CODE), quote type code (QTP_CODE), asset value, residual value, unbilled receivables, and gain/loss fields.
  • OKL_TXL_QTE_LINES_ALL_B — the quote line table, supplying line type code (QLT_CODE), the contract line reference (KLE_ID), stream type reference (STY_ID), and the aggregated line AMOUNT.
  • FND_LOOKUPS — joined on lookup type OKL_QUOTE_LINE_TYPE to deliver the human-readable MEANING for each line type code.
  • OKC_K_LINES_B — the contract line table, joined outer to resolve line identity; it is a supported reference that may be null for some quote lines.
  • OKL_STRM_TYPE_V — the stream type view, joined outer, contributing a stream name appended to the description via NVL2.
  • OKL_TAX_SOURCES — used only in the second union branch to supply TOTAL_TAX amounts for the AMCTAX pseudo line type.
  • Package references — FND_GLOBAL and OKL_ACCOUNTING_UTIL are documented as referenced objects, typically involved through dependent logic or session/context resolution surrounding the view.

Key Columns

  • QUOTE_NUMBER — the business-facing identifier of the quote from OKL_TRX_QUOTES_B.
  • QLT_CODE / MEANING — the quote line type code and its decoded lookup meaning.
  • QTE_ID — internal identifier of the quote, useful for joins back to the quote header.
  • FULL_DESCRIPTION — concatenation of lookup meaning and, where a stream type name exists, the string "- " plus that name.
  • AMOUNT — the summed monetary amount per line type, or summed TOTAL_TAX in the tax branch.
  • QST_CODE — the quote status code, which is the column a user searching for "qst_code" is most likely seeking; it indicates the lifecycle state of the quote.
  • QTP_CODE — the quote type code.
  • TOTAL_ASSET_VALUE, TOTAL_RESIDUAL_VALUE, TOTAL_UNBILLED_RECEIVABLES, GAIN_LOSS — header-level monetary metrics carried through to each summarized row.

Note that the first union branch filters out line types AMCFIA and AMCTAX, while the second branch reintroduces tax as AMCTAX, ensuring tax is not double-counted and appears once per quote.

Common Use Cases and Queries

Typical uses include quote amount summary screens, exception reports on quote status, and integration extracts that need one row per quote line type. A query filtering on quote status might read:

  • SELECT quote_number, qst_code, qlt_code, amount FROM apps.okl_am_quote_amt_summary_uv WHERE qst_code = 'ACTIVE';
  • SELECT quote_number, full_description, amount FROM apps.okl_am_quote_amt_summary_uv WHERE qte_id = :quote_id ORDER BY qlt_code;
  • SELECT quote_number, total_asset_value, total_residual_value, gain_loss FROM apps.okl_am_quote_amt_summary_uv WHERE qst_code IN ('ACTIVE','BOOKED');

Because the view pre-aggregates amounts and decodes lookups, it is well suited to read-only reporting and cannot be used for DML. Users referencing qst_code should query this view directly rather than reconstructing the join against OKL_TRX_QUOTES_B and the lookup tables.