Results for “okl_quote_parties_v”

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

Overview

OKL_QUOTE_PARTIES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite release 12.1.1 and 12.2.2, delivered as part of the OKL (Leasing and Finance Management) product family. The view presents the parties associated with a quote in Oracle Lease and Finance Management. A single quote may carry one or more OKL contract party roles, and this view exposes each such role assignment as an individual row, allowing reporting tools, concurrent programs, and custom integrations to resolve the full set of parties attached to a quote without joining the underlying transaction tables directly. Because the view is defined as a thin, column-for-column projection over its base table, it behaves as a stable, read-oriented data access point that shields consumers from the physical storage details of the quote party entity while preserving the ROWID and audit attributes required for downstream update logic.

Underlying Base Objects

The view is defined over a single documented base object: the synonym OKL_QUOTE_PARTIES, referenced in the view text by the alias QPYB. The query is a simple SELECT that maps each column of the base object to a corresponding view column, and it exposes QPYB.ROWID as ROW_ID. No joins, unions, or filter predicates are applied. Functionally, therefore, OKL_QUOTE_PARTIES_V is a pass-through view: every row in the base table produces exactly one row in the view, and the row identifiers remain consistent between the two. The synonym OKL_QUOTE_PARTIES resolves to the physical quote parties table in the APPS schema. ETRM metadata records the view as VALID, confirming that the underlying synonym is present and the column list is consistent in the documented releases.

Key Columns

• ROW_ID — The base table ROWID, exposed for row-level identification and update processing.
• ID — Primary identifier of the quote party record.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the OKL framework to detect concurrent modifications.
• QTE_ID — Foreign key to the quote header, linking each party row to its parent quote.
• CPL_ID — Identifier of the associated contract party line or party list entry.
• DATE_SENT — The date the quote or party communication was dispatched. This is the column most commonly searched by users, since it supports cycle-time and distribution tracking.
• QPT_CODE — Quote party type code, defining the role the party plays (for example, lessee, lessor, or guarantor).
• DELAY_DAYS — Number of days of delay associated with the party assignment.
• ALLOCATION_PERCENTAGE — Percentage allocated to the party where the role requires a share of the quote.
• EMAIL_ADDRESS — Electronic mail address of the party or contact, used for document delivery.
• PARTY_JTOT_OBJECT1_CODE / PARTY_OBJECT1_ID1 / PARTY_OBJECT1_ID2 — The JTF object-registry code and identifiers that resolve the party to the TCA/JTF party model.
• CONTACT_JTOT_OBJECT1_CODE / CONTACT_OBJECT1_ID1 / CONTACT_OBJECT1_ID2 — The corresponding JTF object-registry code and identifiers for the contact associated with the party.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns maintained by the OKL application framework.

Common Use Cases and Queries

Typical uses include quote distribution reporting, party-role audits, and integration extracts that feed external document or notification systems. A frequent operational question concerns which parties have been sent a quote and when, which maps directly to the DATE_SENT column.

Listing all parties for a quote, sorted by the date the quote was sent:

• SELECT qte_id, id, qpt_code, date_sent, email_address FROM okl_quote_parties_v WHERE qte_id = :p_quote_id ORDER BY date_sent, qpt_code;

Identifying parties not yet sent, for follow-up processing:

• SELECT qte_id, id, qpt_code, delay_days FROM okl_quote_parties_v WHERE date_sent IS NULL AND delay_days > 0;

Resolving the TCA party and contact behind a quote role:

• SELECT qte_id, qpt_code, party_jtot_object1_code, party_object1_id1, contact_object1_id1 FROM okl_quote_parties_v WHERE qte_id = :p_quote_id;

Because the view performs no filtering, callers should supply their own WHERE predicates on QTE_ID, QPT_CODE, or DATE_SENT to limit result sets. Users requiring party names and addresses must join the exposed JTF object identifiers to the TCA party and contact tables.