Search Results property_type_meaning




Overview
Explore in AI Chat

Overview

FA_ADDITIONS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets) product family. It consolidates asset header information from the FA_ADDITIONS_B and FA_ADDITIONS_TL tables with descriptive and category data, parent-asset relationships, lease details, and lessor vendor information. The view presents a single, flat row per asset, making it suitable for ad-hoc reporting, discoverer workbooks, concurrent program extracts, and integration interfaces that need asset attributes without navigating the normalized base schema. In EBS 12.1.1 and 12.2.2 the object is documented as VALID in ETRM, indicating the view compiles against the referenced synonyms without error.

Underlying Base Objects

ETRM metadata records the following referenced base objects for FA_ADDITIONS_V: FA_ADDITIONS_B, FA_ADDITIONS_TL, FA_CATEGORIES_B, FA_LEASES, FA_LOOKUPS_B, FA_LOOKUPS_TL, and PO_VENDORS (itself a view). The join logic is visible in the view text: FA_ADDITIONS_B (aliased AD) supplies the core asset row, including ROWID, asset identifiers, category, parent, physical attributes, flags, and descriptive flexfield columns. FA_ADDITIONS_TL (ADT) supplies the translated description, joined at the asset level. FA_CATEGORIES_B provides category context, while FA_LEASES (LEASE) contributes lease number, description, lessor ID, and the lease descriptive flexfield attributes. PO_VENDORS (PV) resolves the lessor name. FA_LOOKUPS_B and FA_LOOKUPS_TL (LUTL_PT, LUTL_PC) translate the property type code and the property 1245/1250 code into their meanings. Parent asset details are self-joined back to FA_ADDITIONS_B and FA_ADDITIONS_TL, yielding PARENT_ASSET and PARENT_DESCRIPTION.

Key Columns

Common Use Cases and Queries

The view is typically queried for asset master extracts, lease reporting, and reconciliation between asset numbers and descriptive attributes. A basic asset listing:

SELECT asset_number, description, asset_type, tag_number,
       property_type_meaning, owned_leased
FROM   apps.fa_additions_v
WHERE  asset_number LIKE 'COMP%';

Leased-asset reporting with lessor detail:

SELECT asset_number, description, lease_number,
       lease_desc, lessor, LESSOR_ID
FROM   apps.fa_additions_v
WHERE  lease_id IS NOT NULL;

Parent/child hierarchy enquiry:

SELECT asset_number, description, parent_asset, parent_description
FROM   apps.fa_additions_v
WHERE  parent_asset_id IS NOT NULL
ORDER  BY parent_asset, asset_number;

Because joins to FA_ADDITIONS_TL and FA_LOOKUPS_TL are included, callers do not need to resolve translated descriptions or lookup meanings themselves; they only need to supply an appropriate language context. The view is read-only and should be treated as a reporting convenience layer rather than a transactional interface.