Search Results fa_categories_b_kfv




Overview
Explore in AI Chat

Overview

APPS.FA_ASSET_HIST_WEB_V is a reporting view in the Oracle E-Business Suite Fixed Assets module that consolidates asset transaction history into a single, web-friendly result set. It is defined as a UNION of two nearly identical SELECT statements drawn from FA_ASSET_HISTORY and its supporting lookup and category tables. The view presents each asset movement as a row containing the transaction header identifiers (both inbound and outbound), the asset number and description concatenated into a single display string, the translated transaction type and asset type meanings, units, category concatenated segments, and the transaction name as a comment field.

Because the view resolves lookup codes into their display meanings through FA_LOOKUPS, it is particularly suited to Oracle Forms-based self-service screens and concurrent report output where users expect readable values rather than internal codes. The KEY column is populated from TRANSACTION_HEADER_ID_IN in the first branch and from TRANSACTION_HEADER_ID_OUT in the second branch, providing a stable join key for the history grid.

Underlying Base Objects

The view is owned by APPS and references the following documented objects: FA_ADDITIONS (synonym), FA_ASSET_HISTORY (synonym), FA_CATEGORIES_B_KFV (view), FA_LOOKUPS (synonym), and FA_TRANSACTION_HEADERS (synonym).

  • FA_ADDITIONS — supplies ASSET_NUMBER and DESCRIPTION, joined on ASSET_ID.
  • FA_ASSET_HISTORY — the driving table, providing transaction header IDs, asset ID, units, asset type, and category ID.
  • FA_TRANSACTION_HEADERS — provides TRANSACTION_NAME and the TRANSACTION_TYPE_CODE used to derive the transaction type meaning.
  • FA_LOOKUPS — used twice: once aliased LO against lookup type 'FAXOLTRX' for the transaction type meaning, and once aliased LU against lookup type 'ASSET TYPE' for the asset type meaning.
  • FA_CATEGORIES_B_KFV — a key flexfield view that returns CONCATENATED_SEGMENTS for the asset category, joined on ASSET_CATEGORY_ID.

Key Columns

  • TRANSACTION_HEADER_ID_IN / TRANSACTION_HEADER_ID_OUT — identifiers linking each history row to the originating and, where applicable, receiving transaction headers.
  • KEY — the effective header identifier, taken from the inbound ID in the first branch and the outbound ID in the second.
  • ASSET_ID — foreign key to FA_ADDITIONS.
  • ASSET_NUMBER — concatenation of ASSET_NUMBER and DESCRIPTION separated by a hyphen, formatted for display.
  • TRANSACTION_TYPE — the MEANING resolved from FA_LOOKUPS for lookup type 'FAXOLTRX'.
  • UNITS — the number of units moved in the transaction.
  • ASSET_TYPE — the MEANING resolved from FA_LOOKUPS for lookup type 'ASSET TYPE'.
  • CATEGORY — the concatenated category flexfield segments.
  • CATEGORY_ID — the numeric category identifier.
  • COMMENTS — the transaction name from FA_TRANSACTION_HEADERS.

Common Use Cases and Queries

The view supports asset history inquiries, audit reporting, and drill-down screens. A typical query returns the complete movement history for a given asset:

  • SELECT asset_number, transaction_type, units, category, comments FROM apps.fa_asset_hist_web_v WHERE asset_id = :asset_id ORDER BY key;
  • SELECT transaction_type, COUNT(*) FROM apps.fa_asset_hist_web_v GROUP BY transaction_type; — summarises activity by transaction type.
  • SELECT * FROM apps.fa_asset_hist_web_v WHERE transaction_type = 'Addition'; — filters for a specific lookup meaning.

Because transaction type and asset type are returned as lookup meanings rather than codes, the view is well suited to end-user reporting without additional decode logic. When developing against it, note that the UNION may produce duplicate-seeming rows for assets with both inbound and outbound header identifiers, and that filtering on TRUNCATED or transformed columns is best avoided to preserve index usage on the underlying FA_ASSET_HISTORY table.