Search Results fa_additions_vl




Overview
Explore in AI Chat

Overview

FA_ADDITIONS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is part of the OFA (Oracle Assets / Fixed Assets) product family and is classified as VALID in the ETRM data dictionary. The view presents asset addition information — the descriptive and financial attributes recorded for assets in the FA_ADDITIONS entity — by joining a base table to its translation table and restricting the translated rows to the session's current language.

Functionally, FA_ADDITIONS_VL serves as the reporting and integration surface for asset addition data in a language-aware manner. The "_VL" suffix indicates that the view resolves description text against the language returned by USERENV('LANG'), the standard EBS mechanism for displaying translatable descriptive columns in the user's preferred language. This makes the view suitable for concurrent programs, OBIEE/XML Publisher reports, custom forms, and outbound interfaces that must present asset descriptions in the operating language rather than in a fixed base language.

Underlying Base Objects

The documented view metadata for 12.2.2 lists two referenced base objects, both exposed as synonyms: FA_ADDITIONS_B and FA_ADDITIONS_TL. FA_ADDITIONS_B supplies the base (non-translated) asset addition columns, while FA_ADDITIONS_TL supplies the translatable description text.

The view definition confirms this relationship: it selects the base columns from FA_ADDITIONS_B (aliased B) and the DESCRIPTION column from FA_ADDITIONS_TL (aliased T), joining the two on ASSET_ID and filtering by T.LANGUAGE = USERENV('LANG'). The join key ASSET_ID therefore carries referential integrity between the base and translation segments. Each asset addition produces exactly one row per language in the translation table, and the view projects the single row matching the caller's language. This is the conventional VL pattern and should be understood when tracing lineage: the view is not a simple projection of one table but a language-filtered join.

Key Columns

The view exposes a broad set of asset attributes sourced from FA_ADDITIONS_B. The ROW_ID column carries B.ROWID, providing the physical row identifier of the base row. ASSET_ID is the primary key and the join key. ASSET_NUMBER, TAG_NUMBER, SERIAL_NUMBER, MODEL_NUMBER, and MANUFACTURER_NAME provide identification attributes. ASSET_CATEGORY_ID and PARENT_ASSET_ID establish the asset's category and hierarchical (parent-child) relationships.

Common Use Cases and Queries

Typical uses include asset addition reporting, reconciliation of additions to the asset register, and integration extracts where a human-readable description is required. Because the view enforces language filtering, a caller with no active language setting or with a session language that has no translation row will receive no data for that asset; this is a common diagnostic point for "missing rows" issues.

A representative query listing asset additions with their localized description:

  • SELECT asset_id, asset_number, tag_number, description, asset_category_id FROM apps.fa_additions_vl WHERE asset_number LIKE 'ADDN%';
  • SELECT asset_id, current_units, in_use_flag, owned_leased FROM apps.fa_additions_vl WHERE created_by = :user_id;
  • SELECT b.asset_id FROM fa_additions_b b WHERE NOT EXISTS (SELECT 1 FROM fa_additions_vl v WHERE v.asset_id = b.asset_id);

The third pattern is useful for identifying base assets lacking a translation row in the current language. For performance, joins should reference ASSET_ID, the indexed primary key, and consumers should avoid selecting the full flexfield column set unless required, since the view projects more than ninety columns.