Results for “quote_type”

50+ results




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

Overview

The OKL_H_AM_QUOTES_UV view is a reporting object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, residing in the APPS schema. It exposes a simplified, lookup-resolved representation of quote type information derived from the transactional quotes data model. Its role is to provide a concise enumeration of quotation types that are available for use in lease and finance quotation workflows, presenting each quote type code alongside its human-readable description resolved from the Oracle Application Object Library lookup infrastructure.

The view was designed primarily as a value-set or list-of-values supporting object, typically for form fields, concurrent program parameters, and integration interfaces that must present the set of valid, non-consolidated quote types. Because the view derives descriptions dynamically from FND_LOOKUPS rather than from a dedicated descriptive column, it ensures that the displayed description always reflects the current lookup meaning maintained under the OKL_QUOTE_TYPE lookup type. This makes the view particularly relevant to users searching on the term okl_quote_type, since the view is a direct consumer of that lookup type.

Underlying Base Objects

The view is defined over two documented base objects and is compiled within the APPS schema. The underlying objects are:

  • OKL_TRX_QUOTES_B (referenced as a synonym) — the transactional quotes base table that stores quote header records, including the quote type code (QTP_CODE) and the consolidation indicator (CONSOLIDATED_YN).
  • FND_LOOKUPS (view) — the Oracle Application Object Library lookup view that supplies the translated meaning for each lookup code.
  • FND_GLOBAL (package) — referenced by the view metadata, typically supplying session context such as organization or user identifiers used implicitly during evaluation.

The join is established by matching FL2.LOOKUP_TYPE = 'OKL_QUOTE_TYPE' with FL2.LOOKUP_CODE = OTQ.QTP_CODE, and by restricting the rows to OTQ.CONSOLIDATED_YN = 'N'. Consequently, only non-consolidated quote types present on transactional quote records are surfaced, and each is paired with the current lookup meaning.

Key Columns

  • QUOTE_TYPE — the quote type code sourced from OKL_TRX_QUOTES_B.QTP_CODE. This is the stored identifier used throughout the OKL applications and APIs to classify a quote.
  • QUOTE_TYPE_DESCRIPTION — the displayed meaning returned from FND_LOOKUPS.MEANING for the matching lookup code under the OKL_QUOTE_TYPE lookup type. This column provides the translated, user-facing description.

Because the description is resolved through the lookup mechanism, the view inherits lookup translation behavior, and the meaning may vary by language depending on the lookup translations defined in the environment.

Common Use Cases and Queries

The view is most commonly used to populate value sets, list of values, and parameter prompts. A typical query to retrieve all available quote types is:

  • SELECT quote_type, quote_type_description FROM apps.okl_h_am_quotes_uv ORDER BY quote_type_description; — returns the full enumerated list for display in an LOV or report parameter.
  • SELECT quote_type_description FROM apps.okl_h_am_quotes_uv WHERE quote_type = :p_quote_type; — resolves a single stored code into its description for reporting output.
  • SELECT COUNT(*) FROM apps.okl_h_am_quotes_uv; — used to validate that the lookup and transaction data are aligned during setup verification.

Because the view filters out consolidated quotes and depends on the existence of matching lookup rows, administrators troubleshooting missing quote types should verify that the relevant OKL_QUOTE_TYPE lookup code is enabled and that the associated quote record exists in OKL_TRX_QUOTES_B with CONSOLIDATED_YN = 'N'. When integrating with external systems, the view offers a stable, description-bearing interface for exchanging quote type values without requiring direct joins to the lookup tables.