Results for “cplv_id”

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

Overview

OKL_TRX_AP_INVOICES_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL - Lease and Finance Management product. The suffix _UV (user view) follows Oracle naming conventions for views exposed to end-user reporting and inquiry rather than to internal transactional processing. The view presents lease-related accounts payable invoice header data that has been generated by Oracle Lease Management and is destined for, or reconciled against, Oracle Payables. Because Oracle Lease and Finance Management drives invoice creation for lease funding, borrowing, and other transaction types, this view consolidates the invoice header information with transaction type description data in a single queryable structure.

The view is implemented over the OKL_TRX_AP_INVS_ALL_B synonym, aliased TAPB, which supplies the primary invoice header rows, joined to OKL_TRX_AP_INVOICES_TL, aliased TAPT, which supplies the translatable description column. The metadata further documents a reference to OKL_TRX_TYPES_TL and OKC_K_HEADERS_B, both synonyms, in addition to a call to the OKL_ACCOUNTING_UTIL package. The view is valid and supported on both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The ETRM documentation lists five referenced base objects. Each plays a distinct role in composing the view.

• OKL_TRX_AP_INVS_ALL_B (synonym): the principal invoice header table, contributing the majority of the columns including transaction status, currency, set of books, funding type, and all descriptive attributes.
• OKL_TRX_AP_INVOICES_TL (synonym): the translatable table supplying the language-specific DESCRIPTION column.
• OKL_TRX_TYPES_TL (synonym): the translatable transaction type table, referenced through the transaction type identifier for joining type descriptions.
• OKC_K_HEADERS_B (synonym): the contract headers base table from the OKC contract module, providing the contract context associated with the lease.
• OKL_ACCOUNTING_UTIL (package): invoked at query time through FORMAT_AMOUNT, which applies currency formatting to the raw AMOUNT value.

The presence of OKL_ACCOUNTING_UTIL.FORMAT_AMOUNT means the AMOUNT column is computed at runtime rather than stored, so query performance depends partly on the function's implementation.

Key Columns

The view exposes a wide column set. Among the most significant are the following.

• ID / ROW_ID: the primary key of the invoice header and the physical row identifier, used for direct row lookup and update-context joins.
• TRX_STATUS_CODE: the lease transaction status that governs whether the invoice is pending funding, approved, or otherwise.
• INVOICE_NUMBER, DATE_INVOICED, DATE_GL: the Payables-facing invoice identifier and key accounting dates, used for reconciliation between Lease Management and Oracle Payables.
• TAP_ID_REVERSES: identifies the original invoice record that the current invoice is a reversal of — the column referenced by the search term "tap_id_reverses".
• CURRENCY_CODE, SET_OF_BOOKS_ID, AMOUNT: the currency context and the formatted invoice amount.
• FUNDING_TYPE_CODE, KHR_ID, ART_ID, CCF_ID, TRY_ID, IPPT_ID, IPVS_ID, TCN_ID, CPLV_ID: foreign keys linking the invoice to the funding, contract, rate, and pricing entities in the lease model.
• WORKFLOW_YN, CONSOLIDATE_YN, WAIT_VENDOR_INVOICE_YN: workflow and consolidation control flags that drive invoice generation behavior.
• DATE_ENTERED, CREATED_BY, LAST_UPDATED_BY and the ATTRIBUTE1 through ATTRIBUTE15 columns: standard audit and descriptive flexfield columns.

Common Use Cases and Queries

A typical use is the reconciliation of Lease Management invoices to Oracle Payables, reporting on status, amount, and accounting date. A second common scenario is tracing reversals and adjustment chains using TAP_ID_REVERSES.

To identify all invoices that reverse another invoice:

• SELECT ID, INVOICE_NUMBER, TAP_ID_REVERSES, TRX_STATUS_CODE, AMOUNT FROM OKL_TRX_AP_INVOICES_UV WHERE TAP_ID_REVERSES IS NOT NULL;

To trace a full reversal chain from a specific invoice:

• SELECT ID, INVOICE_NUMBER, TAP_ID_REVERSES FROM OKL_TRX_AP_INVOICES_UV START WITH ID = :p_id CONNECT BY PRIOR ID = TAP_ID_REVERSES;

To reconcile funded lease invoices against a general ledger date range:

• SELECT INVOICE_NUMBER, DATE_INVOICED, DATE_GL, CURRENCY_CODE, AMOUNT, FUNDING_TYPE_CODE FROM OKL_TRX_AP_INVOICES_UV WHERE SET_OF_BOOKS_ID = :p_sob AND TRX_STATUS_CODE = 'FUNDED' AND DATE_GL BETWEEN :p_from AND :p_to;

Because AMOUNT is computed via OKL_ACCOUNTING_UTIL.FORMAT_AMOUNT, queries filtering or aggregating on amount should validate numeric behavior against the base table OKL_TRX_AP_INVS_ALL_B when precision matters.