Results for “fa_cle_id”

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

Overview

OKL_SUPP_INVOICE_DTLS_H is the audit history table for OKL_SUPP_INVOICE_DTLS within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the OKL schema and holds the state-level history of supplier invoice detail records associated with lease and finance contracts. Where OKL_SUPP_INVOICE_DTLS maintains the current or effective version of each supplier invoice detail row, this companion table captures superseded versions created whenever an existing detail record is updated, allowing the application to retain a chronological trail of invoice changes.

Supplier invoice details in OKL represent the vendor-facing amounts tied to a lease contract, purchase order, or asset delivery — typically the invoice number, invoiced and due dates, and shipping address information used by the leasing settlement process. Because invoicing data is financial in nature, it is subject to audit, so Oracle preserves prior versions in this history table rather than overwriting them in place.

Following a heuristic Data Vault classification mined from its foreign key structure, this table can be modeled as a standalone object rather than a hub, link, or satellite, since no FK dependencies were detected. Practically, however, the composite key (ID plus MAJOR_VERSION) resembles a versioned satellite pattern, in which each ID identifies the underlying business entity and MAJOR_VERSION distinguishes successive historical states of that entity.

The table is documented at 32 columns in ETRM 12.2.2 and is identified by primary key OKL_SUPP_INVOICE_DTLS_H_PK, defined on the columns (ID, MAJOR_VERSION).

Key Information Stored

The most significant columns of this table are:

• ID — The surrogate identifier shared with the current-row table; part of the composite primary key and the principal join key to OKL_SUPP_INVOICE_DTLS.
• MAJOR_VERSION — The version number that, combined with ID, forms the primary key; it distinguishes each historical snapshot of the same invoice detail.
• OBJECT_VERSION_NUMBER — The optimistic locking counter carried into the history row to indicate the version context at which the snapshot was written.
• CLE_ID — The contract line identifier (contract line entity) to which the supplier invoice detail belongs.
• FA_CLE_ID — The financing asset contract line entity identifier associated with the invoice detail, linking the financial asset to the invoiced amount.
• INVOICE_NUMBER — The vendor or supplier invoice reference number.
• DATE_INVOICED — The date the supplier invoice was issued.
• DATE_DUE — The date payment is due on the invoice.
• SHIPPING_ADDRESS_ID1 and SHIPPING_ADDRESS_ID2 — The composite identifiers for the shipping address party or location.
• SHIPPING_ADDRESS_CODE — The human-readable shipping address code.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The extensible descriptive flexfield columns that carry customer-defined invoice attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle who-columns recording row creation and modification audit information.

The surrogate primary key is the composite (ID, MAJOR_VERSION). The column ID alone is a business-key candidate that also serves as the link back to the parent current-row record; MAJOR_VERSION is not a business key in its own right but is required to make the key unique across history.

Common Use Cases and Queries

Typical usages center on audit and reconciliation reporting: identifying what changed on a supplier invoice, who changed it, and when. A common pattern joins history rows to the current row on ID to compare versions:

• List all historical versions of a given invoice detail: SELECT * FROM OKL.OKL_SUPP_INVOICE_DTLS_H WHERE id = :p_id ORDER BY major_version DESC;
• Identify the latest historical snapshot per ID: SELECT id, MAX(major_version) FROM OKL.OKL_SUPP_INVOICE_DTLS_H GROUP BY id;
• Detect changes to invoiced / due dates: SELECT id, major_version, date_invoiced, date_due FROM OKL.OKL_SUPP_INVOICE_DTLS_H WHERE id = :p_id ORDER BY major_version;
• Audit who last touched a version: SELECT id, major_version, last_updated_by, last_update_date FROM OKL.OKL_SUPP_INVOICE_DTLS_H WHERE cle_id = :p_cle;
• Reconcile amounts by contract line and financing asset using CLE_ID and FA_CLE_ID.

Because the table is append-oriented, reporting queries should filter or aggregate by MAJOR_VERSION to avoid double counting invoice lines.

Related Objects

The following objects are most significant in relation to OKL_SUPP_INVOICE_DTLS_H:

• OKL_SUPP_INVOICE_DTLS — The current-row source table; join on ID (and conceptually MAJOR_VERSION) to compare history against the active record.
• OKL_SUPP_INVOICE_H / OKL_SUPP_INVOICE — The supplier invoice header tables that the detail rows roll up to; join via the invoice reference ultimately resolving through ID.
• OKL_CLE_ALL — The contract line entity table referenced through CLE_ID, providing contract line context.
• OKL_FA_CLE_ALL — The financing asset contract line table referenced through FA_CLE_ID.
• OKL_SUPP_INVOICE_DTLS_H_PK — The primary key constraint that enforces uniqueness on (ID, MAJOR_VERSION).
• Standard EBS audit views such as the OKL supplier invoice inquiry pages, which consume both current and history rows.

As the FK heuristic classifies this object as standalone, no enforced foreign keys were detected; relationships above are logical joins driven by the documented ID, CLE_ID, and FA_CLE_ID columns.