Search Results fa_asset_v




Overview
Explore in AI Chat

Overview

FA_ASSET_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Assets (OFA) product family. It is classified in ETRM as providing "asset identification and financial information," and it serves as a consolidated reporting and integration interface for fixed asset records across identification attributes and book-level financial attributes. In EBS 12.1.1 and 12.2.2 the object is documented with status VALID and is defined over four synonym references in APPS, making it suitable for custom reports, discoverer workbooks, concurrent program extracts, and inbound/outbound interface queri es where a single flattened row per asset per book is required. Because the view embeds business filters, it returns only a constrained slice of the underlying asset population, which is an important consideration for any integration expecting exhaustive asset data.

Underlying Base Objects

The documented base objects are FA_ADDITIONS (SYNONYM), FA_BOOKS (SYNONYM), FA_BOOK_CONTROLS (SYNONYM), and FA_CATEGORIES_B (SYNONYM), all resolving to the APPS tables FA_ADDITIONS, FA_BOOKS, FA_BOOK_CONTROLS, and FA_CATEGORIES_B. The view text joins FA_ADDITIONS AD to FA_BOOKS BK on ASSET_ID, then to FA_BOOK_CONTROLS BC on BOOK_TYPE_CODE, and to FA_CATEGORIES_B CA on ASSET_CATEGORY_ID. Three joins are therefore mandatory: an asset must have a corresponding FA_BOOKS row, a matching FA_BOOK_CONTROLS row, and a valid category row.

Two predicates materially restrict the result set. First, BC.BOOK_CLASS = 'CORPORATE' limits output to book controls whose book class is the seeded CORPORATE value, so tax and other non-corporate books are excluded. Second, BK.PERIOD_COUNTER_FULLY_RETIRED IS NULL and BK.DATE_INEFFECTIVE IS NULL exclude assets that are fully retired or whose book assignment has been made ineffective. The view is consequently a "live corporate book" asset listing rather than a complete historical asset register.

Key Columns

The view exposes sixteen columns. Identification columns include ASSET_NUMBER (the user-facing asset number), TAG_NUMBER, DESCRIPTION, MANUFACTURER_NAME, SERIAL_NUMBER, and MODEL_NUMBER, all sourced from FA_ADDITIONS. Category columns are MAJOR_CATEGORY, mapped from FA_CATEGORIES_B.SEGMENT1, and SUB_CATEGORY, mapped from FA_CATEGORIES_B.SEGMENT2. This is the column most often located through keyword searches such as "sub_category," and it is important to note that the view text carries a /* CUSTOMIZE */ comment on both category columns, indicating they are intended as customer-extensible mappings rather than strictly fixed semantics. Financial and depreciation columns come from FA_BOOKS: BOOK_TYPE_CODE, DATE_PLACED_IN_SERVICE, DEPRN_METHOD_CODE, LIFE_IN_MONTHS, COST, SALVAGE_VALUE, ADJUSTED_RATE, and PRODUCTION_CAPACITY.

Common Use Cases and Queries

Typical uses include corporate book asset listings, category-based cost reporting, reconciliation of depreciation attributes, and extracts feeding downstream asset systems. Because SUB_CATEGORY is derived from SEGMENT2 of the category key flexfield, queries filtering on sub-category must account for the site's flexfield segment definition.

  • List corporate book assets with category breakdown: SELECT asset_number, tag_number, major_category, sub_category, book_type_code, cost FROM apps.fa_asset_v WHERE sub_category = 'COMPUTERS';
  • Depreciation review: SELECT asset_number, deprn_method_code, life_in_months, adjusted_rate FROM apps.fa_asset_v WHERE book_type_code = 'CORP';
  • Identification extract: SELECT asset_number, tag_number, serial_number, manufacturer_name, model_number FROM apps.fa_asset_v ORDER BY asset_number;
  • Cost and salvage analysis: SELECT major_category, SUM(cost), SUM(salvage_value) FROM apps.fa_asset_v GROUP BY major_category;

Users requiring retired assets, non-corporate books, or assets lacking book controls must query the base tables directly, since the view's filters preclude those rows.