Search Results get_vendor_id

Overview

OKL_SUPP_INVOICE_DTLS_PVT is a private (PVT) PL/SQL package body owned by APPS in the Oracle E-Business Suite, residing in the Oracle Lease and Finance Management (OKL) application schema. It encapsulates the database-layer logic required to maintain supplier invoice details associated with leased assets. Supplier invoices captured against a lease contract document tie vendor billing records to the assets financed under that contract, and this package provides the validation, persistence, and event-raising infrastructure that supports that relationship.

The package is designated as a private API, meaning it is intended for internal consumption by other OKL packages rather than for direct invocation by external or customer-written code. The ETRM metadata records that the package body is referenced by three other packages, confirming its role as a shared service layer within the OKL module. It also participates in the Workflow business event framework, raising events that notify downstream processes when supplier invoice data is created or modified.

Key Procedures and Functions

The ETRM metadata lists ten documented program units, of which five are identified by name:

• CREATE_SUP_INV_DTLS — Inserts new supplier invoice detail records into the OKL_SUPP_INVOICE_DTLS table, performing row-level validation before persistence and triggering the business event signaling that an asset supplier invoice has been created.
• LOCK_SUP_INV_DTLS — Acquires a locking handle on supplier invoice detail rows, used to serialize concurrent updates and prevent lost-update conditions when multiple processes act on the same invoice data.
• UPDATE_SUP_INV_DTLS — Modifies existing supplier invoice detail records, applying the same validation regime as creation and raising the corresponding update business event.
• DELETE_SUP_INVOICE_DTLS — Removes supplier invoice detail rows from the transactional table, typically as part of correcting or reversing an incorrectly captured invoice.
• VALIDATE_SUP_INV_DTLS — Centralises the business rule checks applied to supplier invoice detail data before any create, update, or delete operation is committed.

The package body excerpt further documents raise_business_event, a wrapper procedure that publishes workflow events using constants such as G_WF_EVT_ASSET_SUP_INV_CRTD and G_WF_EVT_ASSET_SUP_INV_UPTD. Parameters passed to this wrapper include the contract header identifier, asset identifier, vendor identifier, and event name, along with the standard API messaging parameters.

Tables Accessed

The package operates against the following documented tables, accessed through APPS synonyms:

• OKL_SUPP_INVOICE_DTLS — The primary transactional table holding supplier invoice detail rows. All create, update, delete, and lock operations target this table.
• OKC_K_HEADERS_B — Stores lease contract header information; read to resolve the contract context for an invoice and to obtain the contract identifier used in validation and event payloads.
• OKC_K_LINES_B — Stores contract line data, including leased assets; read to validate that an invoice detail references a legitimate asset line.
• OKC_K_PARTY_ROLES_B — Holds party role assignments on the contract; queried to resolve role-based relationships relevant to supplier invoice validation.
• WF_PARAMETER_LIST_T — The Oracle Workflow parameter list type used to assemble the payload passed to the business event APIs.

Usage Notes

Because OKL_SUPP_INVOICE_DTLS_PVT is classified as a private API, it is not exposed directly to end users. It is typically invoked from within the OKL application's higher-level public APIs, from Oracle Forms-based lease contract maintenance screens, or from concurrent programs that process supplier invoice imports and adjustments. The package's business event integration means that subscribers to the oracle.apps.okl.la.lease_contract.asset_supplier_invoice_created and ..._updated events are notified automatically whenever the corresponding operations succeed.

Custom developers should call the supported public wrapper packages rather than OKL_SUPP_INVOICE_DTLS_PVT directly, since private API signatures are subject to change without notice between releases such as 12.1.1 and 12.2.2.