Results for “fa_transaction_detail”

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

Overview

APPS.OKL_FA_TRX_LINE_UV is a union-based Oracle EBS view that consolidates Oracle Lease Management (OKL) contract asset activity with Oracle Assets (FA) transaction and depreciation data. It exposes a normalized "line" representation of fixed asset transactions tied to leased assets and their originating contracts. The view is primarily a reporting and integration object: it supplies a single, uniform transaction-detail record set that downstream accounting, reconciliation, and analytics processes can consume without joining the underlying FA and OKL schemas themselves. This is the object surfaced when users search for "fa_transaction_detail," and the literal string 'FA_TRANSACTION_DETAIL' is in fact returned as the SOURCE_TABLE value for the transaction branch of the union.

Underlying Base Objects

The documented base objects are: FA_ADDITIONS, FA_CATEGORIES_B_KFV, FA_DEPRN_DETAIL, FA_DEPRN_PERIODS, FA_TRANSACTION_HEADERS, OKC_K_HEADERS_ALL_B, OKL_ACCOUNTING_UTIL (package), and OKL_VIEW_TRX_ASSETS_V (view). The first union branch joins OKL_VIEW_TRX_ASSETS_V, OKC_K_HEADERS_ALL_B, FA_TRANSACTION_HEADERS, FA_ADDITIONS, and FA_CATEGORIES_B_KFV. The second branch draws depreciation activity from FA_DEPRN_DETAIL and FA_DEPRN_PERIODS. Asset-to-contract linkage is established by matching OALV.DNZ_CHR_ID to OKHB.ID and OALV.ASSET_ID to FTH.ASSET_ID, with the corporate book aligned to the FA book type. The OKL_ACCOUNTING_UTIL package supplies the amount, currency, and date-boundary logic used to filter and quantify each branch.

Key Columns

• ID / TRANSACTION_ID — A composite key formed from book type, asset number, and transaction header (or distribution/period) identifiers.
• LINE_NUMBER — Constant line indicator (1) used for line-level formatting.
• DESCRIPTION — Book type concatenated with the asset category concatenated segments.
• AMOUNT — Derived transaction amount (via OKL_ACCOUNTING_UTIL.get_fa_trx_amount) or the depreciation amount from FA_DEPRN_DETAIL.
• CURRENCY_CODE — Functional currency returned by OKL_ACCOUNTING_UTIL.GET_FUNC_CURR_CODE.
• ASSET_ID / BOOK_TYPE_CODE — The FA asset and book context for the transaction.
• DISTRIBUTION_ID / PERIOD_COUNTER — Distribution and depreciation period identifiers.
• CONTRACT_NUMBER / KHR_ID — The OKL/OKC contract header that owns the asset.
• SOURCE_TABLE — Literal 'FA_TRANSACTION_DETAIL' identifying the originating data set.
• STREAM_TYPE / STREAM_TYPE_PURPOSE — Null in the documented text, retained for interface completeness.

Common Use Cases and Queries

Typical uses include reconciling lease-driven asset transactions against FA books, reporting transaction detail by contract, and feeding accounting extract processes. The date boundaries are enforced through OKL_ACCOUNTING_UTIL.get_fa_trx_start_date and get_fa_trx_end_date, so results are scoped to valid contract periods.

Sample query for a specific contract and book:

• SELECT transaction_id, description, amount, currency_code, asset_id, book_type_code, contract_number FROM apps.okl_fa_trx_line_uv WHERE contract_number = :p_contract AND book_type_code = :p_book ORDER BY transaction_id;
• SELECT book_type_code, SUM(amount) FROM apps.okl_fa_trx_line_uv WHERE asset_id = :p_asset GROUP BY book_type_code;

Because the view performs concatenated-string key generation and calls package functions per row, filtering by contract, asset, or book is recommended for performance in larger data sets.