Results for “okl_supp_invoice_dtls”

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

Overview

OKL_SUPP_INVOICE_DTLS is a contract line level table within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It records vendor invoice and shipping details associated with individual contract line items, serving as the transactional detail store that captures the supplier-facing financial and logistics information tied to a leased or financed asset. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the OKL schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the object is classified heuristically as satellite-leaning. This classification is inferred from its foreign key structure: the table carries a single outbound dependency to OKC_K_LINES_B via CLE_ID, and its own surrogate primary key, OKL_SUPP_INVOICE_DTLS_PK on ID, rather than a composite business key inherited from a parent hub. This pattern suggests the table functions as a descriptive satellite attached to the contract line, capturing attributes that change or accumulate over the lifecycle of a line item rather than defining new business entities or many-to-many relationships.

Key Information Stored

The table documents 31 columns. The most significant for functional and integration purposes are:

• ID — Surrogate primary key defined by OKL_SUPP_INVOICE_DTLS_PK and backed by unique index OKL_SUPP_INVOICE_DTLS_U1. This is the technical row identifier, not a business key.
• CLE_ID — Foreign key to OKC_K_LINES_B, establishing the contract line to which the vendor invoice and shipping detail belongs. This is the principal business relationship column.
• FA_CLE_ID — Secondary reference to a contract line, typically associated with a finance or asset-related line linkage.
• INVOICE_NUMBER — The vendor-supplied invoice identifier used for reconciliation and payment tracking.
• DATE_INVOICED — The date the vendor issued the invoice.
• DATE_DUE — The date payment is due, supporting aging and cash-flow reporting.
• SHIPPING_ADDRESS_ID1, SHIPPING_ADDRESS_ID2, and SHIPPING_ADDRESS_CODE — Shipping destination references used to capture where the leased or financed asset was delivered.
• OBJECT_VERSION_NUMBER — Optimistic locking column supporting concurrent update control in the OAF framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, enabling client-specific extensions without schema modification.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard WHO columns providing audit lineage.

Common Use Cases and Queries

The primary use case is retrieving vendor invoice and shipping information for a given contract line. A typical query joins the detail table to OKC_K_LINES_B to resolve the line context:

• Invoice lookup by contract line: SELECT d.invoice_number, d.date_invoiced, d.date_due FROM okl_supp_invoice_dtls d, okc_k_lines_b l WHERE d.cle_id = l.id AND l.id = :line_id;
• Aging and payment reporting: Aggregate DATE_DUE to identify overdue vendor invoices across a portfolio of leases.
• Shipping reconciliation: Use SHIPPING_ADDRESS_CODE and the two address ID columns to verify delivery destinations against asset records.
• DFF-based reporting: Filter on ATTRIBUTE_CATEGORY and specific ATTRIBUTEn columns where clients have configured flexfields for invoice or logistics attributes.

Because reporting is most often line-centric, the CLE_ID index and the unique index on ID are the critical access paths.

Related Objects

• OKC_K_LINES_B — Direct parent via the CLE_ID foreign key; supplies the contract line context for every detail record.
• OKC_K_LINES_TL — Translation table for contract line descriptive text, joined through the line ID to enrich reports.
• OKC_K_HEADERS_B — Contract header, reachable through the line to aggregate invoice details at contract level.
• OKL_SUPP_INVOICE_DTLS_PK / OKL_SUPP_INVOICE_DTLS_U1 — The primary key constraint and unique index enforcing row identity on ID.
• OKL_* transaction and asset tables — Downstream lease accounting and asset records that consume vendor invoice and shipping data associated with the same contract line.

Form and OAF-based UI layers within the OKL module reference this table through the CLE_ID relationship, and any custom reporting or integration should preserve the surrogate key semantics of ID while treating CLE_ID as the business join path.