Search Results fa_transaction_headers




Overview
Explore in AI Chat

Overview

The FA_TRANSACTION_HEADERS table is the central transactional ledger within the Oracle Assets (OFA) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master repository for recording all asset-related financial activities, providing a complete audit trail for every transaction processed by the system. Each row represents a distinct transaction header that groups one or more detailed transaction lines, which are stored in related child tables. Its primary role is to maintain the integrity and sequence of asset transactions, linking them to the specific asset, book, and source document. The table's extensive foreign key relationships underscore its critical position as the nexus for asset accounting, depreciation, and historical tracking.

Key Information Stored

The table's structure is designed to capture the essential metadata of a transaction. The primary key, TRANSACTION_HEADER_ID, uniquely identifies each transaction record. Other critical columns establish the transaction's context and relationships. The BOOK_TYPE_CODE and ASSET_ID columns link the transaction to a specific depreciation book and asset master record, respectively. The TRANSACTION_TYPE_CODE defines the nature of the action, such as addition, transfer, adjustment, retirement, or reclassification. The table also maintains referential integrity through columns like SOURCE_TRANSACTION_HEADER_ID and MEMBER_TRANSACTION_HEADER_ID, which track relationships between grouped or derived transactions (e.g., mass transactions or split/merge operations). Additional columns typically store the transaction date, period, and status, governing how the transaction flows through the asset lifecycle and posting to the general ledger.

Common Use Cases and Queries

This table is fundamental for troubleshooting, audit reporting, and data extraction. A common use case is tracing the complete history of an asset. Analysts frequently join FA_TRANSACTION_HEADERS with FA_ADDITIONS and FA_BOOKS to generate asset life cycle reports. Another critical scenario involves reconciling depreciation or net book value by verifying all transactions posted within a specific accounting period. Sample SQL patterns often include filtering by transaction type and date range to analyze capital activity or audit specific event sequences, such as transfers followed by adjustments.

  • Asset Transaction History: SELECT th.* FROM fa_transaction_headers th, fa_additions a WHERE th.asset_id = a.asset_id AND a.asset_number = '<ASSET_NUMBER>' ORDER BY th.transaction_date;
  • Transaction Audit for a Period: SELECT transaction_type_code, COUNT(*), MIN(transaction_date), MAX(transaction_date) FROM fa_transaction_headers WHERE book_type_code = '<BOOK>' AND transaction_date BETWEEN :p_start_date AND :p_end_date GROUP BY transaction_type_code;

Related Objects

As indicated by the foreign key metadata, FA_TRANSACTION_HEADERS has a foundational relationship with numerous core Assets tables. It is a direct parent to tables storing transaction details: FA_ADJUSTMENTS (for depreciation and cost adjustments), FA_ASSET_HISTORY (for category and location changes), and FA_DISTRIBUTION_HISTORY (for assignment changes). Its relationship with FA_BOOKS is particularly crucial, as the TRANSACTION_HEADER_ID_IN and _OUT columns on FA_BOOKs link the transaction that opened and closed an asset's book record. The table also references control tables like FA_BOOK_CONTROLS and source documents via FA_INVOICE_TRANSACTIONS. The self-referencing foreign keys for SOURCE and MEMBER transaction headers manage complex transactional hierarchies within the system.