Search Results total_transaction_amount




Overview
Explore in AI Chat

Overview

APPS.OKL_TRX_HEADER_UV is a UNION ALL view in Oracle Lease Management (OKL), part of the Oracle E-Business Suite 12.1.1 and 12.2.2 ETRM (Enterprise Transaction and Reporting Model) layer. It presents a consolidated, reporting-friendly projection of lease transaction headers, normalizing fields such as transaction identity, contract context, transaction type, status, date, amount, and currency into a single structure. Its principal role is to feed accounting and reporting flows where a uniform "transaction header" record is required regardless of the originating transaction sub-type.

The view is heavily referenced by downstream ETRM objects. According to documented metadata, it is a base object for OKL_VIEW_TRX_ASSETS_V and OKL_TAX_BK_TRX_ASSTS_V, indicating its use in asset-linked and tax book transaction reporting. The searched term "total_transaction_amount" maps to the TOTAL_TRANSACTION_AMOUNT column, which the view text exposes as a placeholder (NULL) in the header projection. This is a critical nuance: the column exists for structural conformity with the broader transaction model but is not populated at the header level in the excerpted definition. Reported totals are typically obtained by joining to line-level views such as OKL_TXL_CNTRCT_LNS_UV or by aggregating the AMOUNT column.

Underlying Base Objects

The view is defined over a join of OKL_TRX_CONTRACTS_ALL (aliased OTCB), OKC_K_HEADERS_B (OKHB), OKL_TRX_TYPES_V (OTTT), and GL_LEDGERS (GL). The join conditions require OTCB.KHR_ID = OKHB.ID, OTCB.TRY_ID = OTTT.ID, OTTT.AEP_CODE IS NOT NULL, and OTCB.SET_OF_BOOKS_ID = GL.LEDGER_ID. An EXISTS clause against OKL_TXL_CNTRCT_LNS_UV restricts results to contracts having at least one matching contract line.

Documented base objects further include OKL_ACCOUNTING_UTIL (PACKAGE), OKL_BILLING_UTIL_PVT, OKL_SYSTEM_PARAMS, OKL_SYS_ACCT_OPTS, OKL_TRX_ASSETS, OKL_TXL_ASSETS_B, and several OKL_BPD_* and FA_*/GL_LEDGERS synonyms used by the UNION ALL branches. The second branch introduces transaction matching amounts, CURRENCY_CODE from the contract header, and additional transaction fields, giving the view broader applicability across lease transaction sub-types.

Key Columns

Common Use Cases and Queries

Typical uses include lease transaction header reporting, reconciliation of draft and actual accounting status, and as a foundation for asset and tax reporting views. A representative query filtering contract transactions and joining line details for totals is shown below.

  • Header listing by contract: SELECT contract_number, transaction_number, transaction_type, transaction_status, transaction_date, amount, currency_code FROM okl_trx_header_uv WHERE contract_number = :p_contract;
  • Totals per transaction (line-level aggregation): SELECT h.trans_id, SUM(l.amount) total_transaction_amount FROM okl_trx_header_uv h, okl_txl_cntrct_lns_uv l WHERE h.khr_id = l.khr_id AND h.trans_id = TO_CHAR(l.tcn_id) GROUP BY h.trans_id;
  • Draft versus actual status review: SELECT transaction_number, actual_draft_status FROM okl_trx_header_uv WHERE actual_draft_status_code = 'DRAFT';

Because TOTAL_TRANSACTION_AMOUNT is not populated in the header definition, any requirement for a true total transaction amount must be satisfied through aggregation against the line-level view or the applicable sub-type view. This behavior is consistent across 12.1.1 and 12.2.2 and should be accounted for in any reporting logic built on OKL_TRX_HEADER_UV.