Results for “quote_reason”

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

Overview

OKL_AM_QUOTES_UV is an APPS-owned, valid database view in the OKL (Lease and Finance Management) product family of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It presents a denormalized, reporting-oriented projection of lease quotation header data combined with associated contract header, quote-party, and contract-party attributes. The view resolves the transactional quote record in OKL_TRX_QUOTES_V against lookup meanings, contract header details, and party role assignments, and it exposes translated descriptions rather than raw codes wherever possible. Because it joins quotation data to both the originating contract and the counterparties attached to that contract, it functions as a single-row-per-quote-party reporting surface used by lease quotation inquiries, integration extracts, and custom operational reports. Users searching on the column contract_party_id arrive at this view because it is one of the few public OKL objects that simultaneously exposes quote identifiers, contract identifiers, and the party identifiers (CONTRACT_PARTY_ID, QUOTE_PARTY_ID, and RECIPIENT_ID) required to trace a quote back to its contracting counterparty.

Underlying Base Objects

The view is documented as being defined over the following referenced objects: FND_GLOBAL (package), FND_LOOKUPS (view), HZ_PARTIES (synonym), OKC_K_PARTY_ROLES_B (synonym), OKC_STATUSES_V (view), OKC_UTIL (package), OKL_AM_UTIL_PVT (package), OKL_K_HEADERS_FULL_V (view), OKL_QUOTE_PARTIES (synonym), and OKL_TRX_QUOTES_V (view). The primary driving entity is the quotation record sourced through OKL_TRX_QUOTES_V, whose columns are aliased as OTQ. Contract header context is drawn from OKL_K_HEADERS_FULL_V (alias OKF), supplying contract number, product type, start and end dates, and status code. Party role records are read from OKL_QUOTE_PARTIES (alias QPT) and OKC_K_PARTY_ROLES_B (alias KPR and KPR2), while descriptions are resolved through FND_LOOKUPS (aliases FL1 through FL5) and status meanings through OKC_STATUSES_V (OSV). HZ_PARTIES provides party master data. The packages FND_GLOBAL, OKC_UTIL, and OKL_AM_UTIL_PVT supply session context and the utility functions GET_JTF_OBJECT_NAME, GET_JTF_OBJECT_COLUMN, GET_TRX_MSGS_YN, and GET_QUOTE_AMOUNT.

Key Columns

• ID and QUOTE_NUMBER — the quotation primary key and user-facing quote number.
• QUOTE_TYPE / QUOTE_TYPE_DESCRIPTION, QUOTE_STATUS / QUOTE_STATUS_DESCRIPTION — coded values and their lookup meanings.
• CONTRACT_NUMBER, CONTRACT_START_DATE, CONTRACT_END_DATE, CONTRACT_STATUS_CODE, CONTRACT_STATUS_MEANING — contract header context.
• QUOTE_PARTY_ID, QUOTE_PARTY_ROLE, QUOTE_PARTY_DESCRIPTION, DATE_SENT — the party assigned to the quote.
• CONTRACT_PARTY_ID, CONTRACT_PARTY_ROLE, CONTRACT_PARTY_DESCRIPTION — the party role on the underlying contract.
• RECIPIENT_ID, RECIPIENT_NAME, RECIPIENT_NUMBER — the resolved recipient, derived via NVL2 across either the contract party or the quote party depending on the presence of QPT.CPL_ID.
• AMOUNT, MESSAGES_YN, APPROVED_YN, ACCEPTED_YN, CONSOLIDATED_YN, LESSEE_KPR_ID, QUOTE_ORG_ID — financial and workflow flags used in reporting filters.

Common Use Cases and Queries

Typical usage includes quotation-status dashboards, recipient/party reconciliation, and extract programs requiring the link between a quote and its contract party. Because CONTRACT_PARTY_ID distinguishes contract-level roles from quote-level roles, the view supports queries that resolve the counterparty on a contract when a quote party is not explicitly linked.

SELECT quote_number, contract_number, contract_party_id,
       contract_party_role, recipient_name, amount
FROM   apps.okl_am_quotes_uv
WHERE  contract_party_id = :p_contract_party_id;

A second common pattern retrieves quotes for a contract with their status meanings and recipient identity:

SELECT q.quote_number, q.quote_status_description,
       q.contract_party_description, q.recipient_number, q.date_sent
FROM   apps.okl_am_quotes_uv q
WHERE  q.contract_number = :p_contract_number
AND    q.approved_yn = 'Y';

Both queries benefit from the view's pre-resolved lookup meanings and recipient columns, eliminating the need to join FND_LOOKUPS, HZ_PARTIES, and the OKC party role tables directly.