Search Results okl_party_payment_dtls




Overview
Explore in AI Chat

Overview

The OKL_PARTY_PAYMENT_DTLS table is a core transactional data store within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It functions as the detailed line-level repository for payment information associated with parties involved in leasing and financing contracts. The table's primary role is to record and manage the specific payment instructions, remittance details, and vendor site linkages for each party role defined in a contract, thereby enabling accurate payment processing and financial settlement within the complex workflows of asset leasing.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented foreign key relationships definitively indicate the critical data elements stored. The table's primary key is the ID column. Each record is fundamentally linked to a payment header via the PAYMENT_HDR_ID, grouping details under a common payment instruction. The VENDOR_ID and PAY_SITE_ID columns store the identifiers for the paying party and their specific remittance address, integrating with both Payables (AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL) and Purchasing (PO_VENDORS, PO_VENDOR_SITES_ALL) supplier master data. The crucial CPL_ID (Contract Party Line ID) foreign key ties each payment detail record directly to a specific party role (e.g., lessor, lessee, payee) on a contract in the OKC_K_PARTY_ROLES_B table, ensuring payment rules are enforced per the contractual agreement.

Common Use Cases and Queries

This table is central to operations involving payment generation and inquiry for lease contracts. A primary use case is the generation of payment batches or electronic funds transfer (EFT) files, where the system queries this table to determine the correct payee, amount, and remittance-to address for each scheduled payment. It is also essential for reporting on vendor payment history across contracts and for troubleshooting payment application issues. A typical analytical query would join this table to the party payment header and contract party roles to assess payment details for a specific contract or vendor.

SELECT ppd.*, pph.payment_number, okr.object1_id1 as contract_id
FROM okl_party_payment_dtls ppd,
     okl_party_payment_hdr pph,
     okc_k_party_roles_b okr
WHERE ppd.payment_hdr_id = pph.id
AND ppd.cpl_id = okr.id
AND okr.object1_id1 = '<Contract Number>';

Related Objects

The OKL_PARTY_PAYMENT_DTLS table maintains integral relationships with several key EBS objects, as documented by its foreign keys:

  • OKL_PARTY_PAYMENT_HDR: Linked via PAYMENT_HDR_ID. This is the parent header table that groups payment details.
  • OKC_K_PARTY_ROLES_B: Linked via CPL_ID. This connects the payment detail to the specific party (e.g., supplier, customer) role on a leasing contract.
  • AP_SUPPLIERS & PO_VENDORS: Linked via VENDOR_ID. These tables provide the supplier master information from both Payables and Purchasing perspectives.
  • AP_SUPPLIER_SITES_ALL & PO_VENDOR_SITES_ALL: Linked via PAY_SITE_ID. These tables provide the specific remittance address for the paying party.