Search Results khr_line_amount




Overview
Explore in AI Chat

Overview

The view APPS.OKL_BPD_AP_INVOICE_UV is an Oracle E-Business Suite database object owned by the APPS schema. It belongs to the Oracle Lease and Finance Management (OKL) module, which forms part of the E-Business Suite financials family and is often described under the broader Enterprise Contracts and leasing umbrella. The view carries an FND Design Data registration of OKL.OKL_BPD_AP_INVOICE_UV and holds a status of VALID in both the 12.1.1 and 12.2.2 releases.

Oracle classifies this object as a supplementary view used to simplify forms coding. This classification has an important consequence: the view exists primarily to support the Oracle Forms-based user interface rather than to serve as a supported integration or reporting interface. Oracle explicitly warns that it does not recommend querying or altering data through such views, because their definition may change dramatically in subsequent minor or major releases. The "_UV" suffix in the name is consistent with this role, denoting a user-facing validation or display view.

In practical terms, the view presents a consolidated, denormalized picture of accounts payable (AP) invoices linked to lease and finance contracts, bringing together invoice header details, contract identifiers, and derived line amounts in a single queryable structure.

Underlying Base Objects

The view is defined over a set of base tables, views, and one package. The documented references are:

  • AP_INVOICES_ALL — the core Payables invoice header table, supplying invoice number, date, amount, currency, payment status, and type information.
  • AP_INVOICES_PKG — the Payables PL/SQL package, referenced for its derived values and status-handling logic.
  • OKL_K_HEADERS and OKC_K_HEADERS_B — contract header tables (OKL and the shared Oracle Contracts OKC layer), providing contract number and contract identifier.
  • OKL_TRX_AP_INVOICES_B — the transactional link between lease transactions and AP invoices.
  • OKL_TXL_AP_INV_LNS_B — the invoice line detail table, which is the source for the aggregated line amount exposed as KHR_LINE_AMOUNT.
  • OKL_CNSLD_AP_INVS_ALL — the consolidated AP invoice table, supplying the consolidated invoice identifier.
  • FND_APPLICATION — the application registration lookup used to resolve application context.

The view itself is referenced by APPS.OKL_TRX_HEADER_UV, indicating it feeds other forms-supporting views within the OKL transaction hierarchy.

Key Columns

The view exposes eighteen columns. The most significant, particularly in relation to the search term khr_line_amount, are described below.

  • KHR_LINE_AMOUNT (NUMBER) — the sum of line amounts for a given contract id. This is an aggregated figure derived from the invoice line detail, and is the column users most commonly search for when reconciling invoice totals against summed line values.
  • INVOICE_AMOUNT (NUMBER) — the invoice header amount, useful for comparing the header total against the aggregated line total.
  • KHR_ID (NUMBER) — the contract identifier, the grouping key over which KHR_LINE_AMOUNT is summed.
  • CONTRACT_NUMBER (VARCHAR2) — the human-readable contract number associated with the invoice.
  • INVOICE_ID, INVOICE_NUM, INVOICE_DATE, DESCRIPTION — standard invoice header attributes.
  • INVOICE_CURRENCY_CODE, INVOICE_TYPE_LOOKUP_CODE, SET_OF_BOOKS_ID — currency, invoice type, and ledger context.
  • PAYMENT_STATUS_FLAG and TRANSACTION_STATUS (VARCHAR2 4000) — status indicators supporting forms display.
  • TRY_ID, PDT_ID, ORG_ID, VENDOR_ID — transaction type, product, operating unit, and supplier identifiers.
  • CNSLD_AP_INV_ID (VARCHAR2 150) — foreign key to okl_ext_pay_invs_all_b.consld_ap_inv_id, linking to consolidated payment processing.

Common Use Cases and Queries

Because the view is forms-supporting, it is most appropriate for diagnostics and reconciliation rather than production reporting. A typical query retrieves invoice and contract information for a specific contract:

  • Reconciling KHR_LINE_AMOUNT against INVOICE_AMOUNT for a given KHR_ID.
  • Filtering by CONTRACT_NUMBER to locate all AP invoices tied to a lease contract.
  • Filtering by PAYMENT_STATUS_FLAG to identify unpaid or partially paid invoices.

Example:

  • SELECT CONTRACT_NUMBER, INVOICE_NUM, INVOICE_AMOUNT, KHR_LINE_AMOUNT, PAYMENT_STATUS_FLAG
  • FROM APPS.OKL_BPD_AP_INVOICE_UV
  • WHERE KHR_ID = :contract_id;

Given Oracle's release-change warning, any dependency on this view should be treated as unsupported and subject to verification against each target release.