Results for “okl_txl_quote_lines_v”

50+ results




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

Overview

OKL_TXL_QUOTE_LINES_V is an APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 / 12.2.2 Leasing and Finance Management (OKL) module. It exposes the quote lines generated by the termination, restructure, or repurchase (TXL) quoting engine — the pricing structures authored during what Oracle historically labels "termination, restructure and repurchase" analysis. Each row represents a single quote line belonging to a TXL quote header, providing the financial terms (amounts, periods, yields, interest rates, residual values) plus the multi-lingual descriptive text needed for display and downstream processing.

Because the view joins the transactional base to its translation table, it is the natural read-only entry point for reports, concurrent program extraction, and integrations that must surface quote line data in a language-aware format without replicating the TL join logic themselves. The view is documented as VALID, confirming that its definition compiles cleanly against the shipped 12.2.2 schema.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKL_TXL_QUOTE_LINES_B — the transactional base table holding one row per quote line, including all numeric, flag, foreign-key, and DFF (Descriptive Flexfield) columns, plus the standard WHO audit columns and ORG_ID.
  • OKL_TXL_QUOTE_LINES_TL — the translation table supplying language-dependent content; only DESCRIPTION and SFWT_FLAG are sourced from it in the documented view text.

The view is essentially a thin projection: nearly every column is inherited directly from TQLB (the _B alias), while DESCRIPTION and SFWT_FLAG come from TQLT (the _TL alias). No filtering, aggregation, or business-rule transformation is applied in the documented text, so the view behaves as a denormalized convenience layer over the _B/_TL pair.

Key Columns

Common Use Cases and Queries

Typical scenarios include extracting quote line schedules for a given quote, reconciling asset quantity against asset value for restructure analysis, and feeding BI Publisher reports. A representative query filtering on the searched attribute:

  • SELECT id, line_number, qte_id, asset_quantity, quote_quantity, asset_value, amount FROM okl_txl_quote_lines_v WHERE asset_quantity > 0;
  • SELECT id, line_number, description, implicit_interest_rate, number_of_periods FROM okl_txl_quote_lines_v WHERE qte_id = :p_quote_id AND org_id = :p_org_id ORDER BY line_number;

Because the view is read-only and depends solely on the TXL quote tables, queries should always constrain on ORG_ID and QTE_ID to avoid unnecessary scans across Multi-Org data.