Results for “okl_quote_parties”

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

Overview

The OKL_QUOTE_PARTIES table is a core data object within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It stores the parties associated with a lease or finance quote, capturing one or more OKL contract party roles for each quotation. Because a single quote frequently involves multiple parties — lessees, lessors, guarantors, contacts, and other role-bearing entities — this table provides the linkage that connects a quote header to the party roles defined in the broader contract management model. The table resides in the OKL schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This classification is a modeling suggestion rather than a physical attribute: the table functions as an associative entity that resolves the many-to-many relationship between quotes and contract party roles. Two of its foreign keys (QTE_ID and CPL_ID) point to distinct hubs, while the JTF_OBJECTS_B references add resolution to the party and contact object identifiers.

Key Information Stored

The table contains 20 documented columns. The most operationally significant are:

• ID — The surrogate primary key, enforced by OKL_QUOTE_PARTIES_PK and uniquely indexed by OKL_QUOTE_PARTIES_U1. This is the single unique business-key candidate documented.
• QTE_ID — Foreign key to OKL_TRX_QUOTES_ALL_B, identifying the parent quote to which this party record belongs.
• CPL_ID — Foreign key to OKC_K_PARTY_ROLES_B, referencing the underlying contract party role definition. This is the primary semantic anchor of the link.
• QPT_CODE — The quote party type/role code that determines the party's function on the quote.
• PARTY_JTOT_OBJECT1_CODE, PARTY_OBJECT1_ID1, PARTY_OBJECT1_ID2 — The JTF object code and Object1 identifier pair resolving the party entity to JTF_OBJECTS_B.
• CONTACT_JTOT_OBJECT1_CODE, CONTACT_OBJECT1_ID1, CONTACT_OBJECT1_ID2 — The equivalent resolution columns for the associated contact, also joining to JTF_OBJECTS_B.
• EMAIL_ADDRESS — The contact email captured against the party for this quote.
• DATE_SENT — The date the quote or correspondence was dispatched to the party.
• DELAY_DAYS — The delay interval associated with the party's processing or response.
• ALLOCATION_PERCENTAGE — The percentage of the quote allocated to the party, supporting split or co-lessee arrangements.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit and concurrency-control columns.

The surrogate ID should be distinguished from business identity: the practical business key is the combination of QTE_ID and CPL_ID (the quote-to-role pairing), while the surrogate key remains stable across updates.

Common Use Cases and Queries

Typical reporting scenarios include listing all parties for a given quote, identifying the primary lessee's contact and email, calculating allocation splits among co-lessees, and auditing dispatch dates.

• Retrieve parties for a quote: SELECT qp.qpt_code, qp.email_address, qp.allocation_percentage FROM okl.okl_quote_parties qp WHERE qp.qte_id = :quote_id;
• Join role definitions: SELECT qp.id, cpr.role, qp.date_sent FROM okl.okl_quote_parties qp, okc.okc_k_party_roles_b cpr WHERE qp.cpl_id = cpr.id AND qp.qte_id = :quote_id;
• Resolve party names through the JTF object view using PARTY_OBJECT1_ID1/ID2 paired with PARTY_JTOT_OBJECT1_CODE.
• Validate allocation totals per quote by summing ALLOCATION_PERCENTAGE grouped by QTE_ID.

These patterns support quote status dashboards, party-responsibility reports, and reconciliation of quote parties against executed contracts.

Related Objects

• OKL_TRX_QUOTES_ALL_B — Parent quote header; joined via QTE_ID.
• OKC_K_PARTY_ROLES_B — Contract party role definitions; joined via CPL_ID.
• JTF_OBJECTS_B — JTF object registry referenced twice, through PARTY_JTOT_OBJECT1_CODE and CONTACT_JTOT_OBJECT1_CODE, with Object1 ID1/ID2 resolution columns for party and contact.
• OKC_K_PARTY_ROLES_TL and related OKC party role translations/views — supply role descriptions.
• Quote and contract party reporting views in the OKL schema that denormalize this link for inquiry screens.