Results for “transaction_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

FA_FINANCIAL_INQUIRY_UPL_V is an APPS-owned database view within the Oracle E-Business Suite Fixed Assets (OFA) module, classified as "Retrofitted" in the ETRM 12.2.2 metadata. It presents financial inquiry data for unplanned depreciation and related asset adjustments, specifically targeting transaction headers whose TRANSACTION_KEY falls within the set ('U', 'UA', 'UE'). The view consolidates adjustment amounts by combining data from both the single-set-of-books adjustment table (FA_ADJUSTMENTS) and its multi-currency counterpart (FA_MC_ADJUSTMENTS) through a UNION ALL operation.

The view's primary purpose is to expose financial adjustment detail for structured inquiry and reporting, particularly in contexts where users need to analyze unplanned depreciation transactions across books and accounting periods. Because it joins header-level transaction data with distribution-level adjustment amounts, it functions as a reporting layer over the transactional backbone of Fixed Assets, supporting both user-facing inquiries and downstream integration extracts. The "UPL" suffix, combined with the TRANSACTION_KEY filtering, indicates it serves the Unplanned Depreciation inquiry flow within the Assets workbench.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

  • FA_TRANSACTION_HEADERS — the primary driver, supplying transaction header identity, book type, asset, transaction type, and transaction subtype.
  • FA_ADJUSTMENTS — the operational adjustment distribution table, providing code combination, adjustment type, debit/credit indicator, and adjustment amount.
  • FA_MC_ADJUSTMENTS — the multi-currency reporting adjustment table, mirrored in the second UNION ALL branch and contributing its own SET_OF_BOOKS_ID.
  • FA_BOOK_CONTROLS — joined in the first branch only, to derive SET_OF_BOOKS_ID from the book type code.
  • FA_LOOKUPS — outer-joined to resolve the transaction subtype into a user-facing meaning via lookup type 'UNPLANNED DEPRN'.

All joins are managed through APPS synonyms, ensuring the view remains portable across customizations and schema upgrades.

Key Columns

  • TRANSACTION_HEADER_ID — unique identifier linking to the parent transaction header.
  • BOOK_TYPE_CODE — the asset book in which the adjustment was recorded.
  • ASSET_ID — the specific asset affected by the adjustment.
  • TRANSACTION_TYPE_CODE — restricted to 'ADJUSTMENT' by the view definition.
  • TRANSACTION_SUBTYPE — the classification code driving the user search term; decoded through FA_LOOKUPS for readability.
  • MEANING — the descriptive lookup meaning corresponding to the transaction subtype.
  • CODE_COMBINATION_ID — the accounting flexfield combination receiving the adjustment.
  • ADJUSTMENT_AMOUNT — an aggregated net amount computed with DECODE logic: debits increase, credits reduce; EXPENSE adjustments only.
  • SOB_ID / SET_OF_BOOKS_ID — the set of books identifier, resolved via FA_BOOK_CONTROLS in the first branch and drawn directly from FA_MC_ADJUSTMENTS in the second.

Common Use Cases and Queries

Analysts searching for transaction_subtype reports use this view to trace unplanned depreciation adjustments by subtype and accounting distribution. A representative query follows:

  • SELECT transaction_subtype, meaning, SUM(adjustment_amount) FROM fa_financial_inquiry_upl_v GROUP BY transaction_subtype, meaning;
  • SELECT asset_id, book_type_code, code_combination_id, adjustment_amount FROM fa_financial_inquiry_upl_v WHERE sob_id = :sob AND transaction_subtype = :subtype;
  • SELECT transaction_header_id, SUM(adjustment_amount) FROM fa_financial_inquiry_upl_v WHERE book_type_code = :book GROUP BY transaction_header_id;

Because the view aggregates by transaction header, code combination, and subtype, it is suited to reconciliation and drill-down reporting rather than transactional maintenance. Joins back to FA_ADDITIONS or FA_BOOKS are typically required to obtain asset descriptions and book names for presentation.