Results for “okl_trx_quotes_v”

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

Overview

OKL_TRX_QUOTES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL – Leasing and Finance Management product family. It exposes quote information generated during lease transaction processing, specifically covering termination, restructure, and repurchase (end-of-term) quotes. In the ETRM (Enterprise Transaction and Relationship Management) data model used by Oracle Leasing, a quote represents a priced proposal or counter-proposal associated with a contract, asset, or party, capturing the financial terms a lessor offers to a lessee under a given transaction type.

The view consolidates descriptive header attributes from the quotes base table with translated, language-dependent text from the quotes translation table. Because it joins the base and translation entities, it presents a single, denormalized row per quote that includes both the operational fields and the free-form COMMENTS text. This makes it suitable as a reporting and integration source: BI Publisher reports, concurrent program extracts, OAF-based inquiry pages, and downstream interfaces can query the view directly rather than reconstructing the join themselves.

Underlying Base Objects

Per the documented metadata, the view is defined over two referenced objects:

• OKL_TRX_QUOTES_B (accessed through a SYNONYM) — the base table holding the language-independent quote attributes, including identifiers, dates, amounts, flags, and descriptive flexfield columns.
• OKL_TRX_QUOTES_TL (accessed through a SYNONYM) — the translation table holding language-specific content such as COMMENTS.

The view aliases the base table as QTEB and the translation table as QTET, selecting nearly all columns from the base and the COMMENTS column from the translation table. The ROWID of the base table is surfaced as ROW_ID, and OBJECT_VERSION_NUMBER is retained to support optimistic locking semantics. In the ETRM 12.2.2 model, translation tables are typically linked by the primary key ID and language columns; the view is designed so that consumers do not need to be aware of the multi-language structure.

Key Columns

• ID / ROW_ID / OBJECT_VERSION_NUMBER — primary identifier, physical row locator, and concurrency control value.
• QUOTE_NUMBER — the user-facing quote reference number.
• QRS_CODE, QST_CODE, QTP_CODE, TRN_CODE — codes identifying quote reason, status, type, and originating transaction.
• DATE_REQUESTED — the date on which the quote was requested; the field most commonly used to age or filter quotes. It sits alongside DATE_PROPOSAL, DATE_ACCEPTED, DATE_DUE, DATE_EFFECTIVE_FROM, DATE_EFFECTIVE_TO, and the restructure start/end dates.
• REQUESTED_BY — the party or user who raised the quote request.
• Flags — EARLY_TERMINATION_YN, PARTIAL_YN, PREPROCEEDS_YN, APPROVED_YN, ACCEPTED_YN, PAYMENT_RECEIVED_YN, CONSOLIDATED_YN, SUMMARY_FORMAT_YN, and SFWT_FLAG describe the quote's nature and lifecycle state.
• Financial fields — PRINCIPAL_PAYDOWN_AMOUNT, RESIDUAL_AMOUNT, YIELD, RENT_AMOUNT, TERM, PURCHASE_PERCENT, PAYMENT_FREQUENCY, REMAINING_PAYMENTS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–11 — descriptive flexfield segments for customer-defined data.
• COMMENTS — translated narrative text sourced from the translation table.

Common Use Cases and Queries

Typical reporting scenarios include listing open termination quotes by requested date, tracking acceptance against approval, and reconciling quoted paydown or residual amounts to contract balances.

• Quotes requested within a date range, ordered by DATE_REQUESTED.
• Termination quotes still awaiting acceptance.
• Repurchase quotes showing purchase percent and residual amount.

For example:

SELECT quote_number, trn_code, qst_code,
       date_requested, requested_by,
       rent_amount, residual_amount, accepted_yn
FROM   apps.okl_trx_quotes_v
WHERE  date_requested BETWEEN :p_from AND :p_to
AND    early_termination_yn = 'Y'
ORDER  BY date_requested DESC;

Because the view joins base and translation rows, join criteria must be applied so that only the desired language record is returned; consumers using a single-language implementation will receive one row per quote.