Results for “fa_additions_tl”

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

Overview

FA_ADDITIONS_TL is the translated (Multi-Language Support, MLS) descriptive table for the Oracle Assets (OFA) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the FA schema and holds language-specific descriptive text for asset records maintained in the base asset table, FA_ADDITIONS_B. In an MLS-enabled EBS instance, each translatable attribute is stored once per installed language, allowing asset descriptions to be presented in the language of the logged-in user rather than in a single base language.

The object's primary key is FA_ADDITIONS_TL_PK, defined on the composite columns ASSET_ID and LANGUAGE. A second unique index, FA_ADDITIONS_TL_U1, is documented on the same column pair (ASSET_ID, LANGUAGE), confirming the business key of the table. The ETRM metadata classifies FA_ADDITIONS_TL heuristically as standalone within a Data Vault modeling scheme; in practice, however, its dependency on FA_ADDITIONS_B via ASSET_ID and LANGUAGE suggests it is best modeled as a satellite attached to the asset hub, holding descriptive, language-dependent attributes. The table contains nine documented columns and is a narrow, purpose-built structure rather than a transaction-bearing entity.

Key Information Stored

The table's two identifying columns form both the primary key and the unique business key:

• ASSET_ID — the surrogate identifier of the asset, joining to the base asset row in FA_ADDITIONS_B.
• LANGUAGE — the language code identifying which translation of the descriptive text is stored.
• SOURCE_LANG — the source language from which the current row was derived; used by the MLS translation framework to track the origin of a translated value.
• DESCRIPTION — the translated descriptive text for the asset, and the principal payload of this table.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns recording creation and last-modified audit information for the row.

The distinction between the surrogate primary key (ASSET_ID, LANGUAGE) and the unique index (ASSET_ID, LANGUAGE) is nominal here: because the table stores one description per asset per language, both keys resolve to the same column pair. SOURCE_LANG is the column most often overlooked; it signals whether a row represents a primary translation or a derived one, which matters when diagnosing stale or missing translations.

Common Use Cases and Queries

The most frequent requirement is retrieving an asset description in the user's session language, joining the translation table to the base table:

• Retrieve the translated description for a known asset:

  SELECT tl.description
    FROM fa.fa_additions_tl tl
   WHERE tl.asset_id = :p_asset_id
     AND tl.language = USERENV('LANG');

• Report assets missing a translation in a given language, which surfaces setup gaps after a language is installed:

  SELECT b.asset_id, b.asset_number
    FROM fa.fa_additions_b b
   WHERE NOT EXISTS (SELECT 1
            FROM fa.fa_additions_tl tl
           WHERE tl.asset_id = b.asset_id
             AND tl.language = :p_lang);

• Audit recent description changes using the WHO columns:

  SELECT asset_id, language, description,
         last_updated_by, last_update_date
    FROM fa.fa_additions_tl
   WHERE last_update_date >= :p_since;

• Asset register and fixed-asset reporting extracts that require localized descriptions for statutory or management reporting.
• Data migration and reconciliation scripts that verify description parity across languages before and after a patch or upgrade.

Related Objects

FA_ADDITIONS_TL does not participate in foreign-key relationships outward; the ETRM relationship data classifies it as standalone. Its dependencies are therefore by convention rather than by enforced constraint:

• FA_ADDITIONS_B — the base (non-translated) asset table; joins on ASSET_ID and is the parent of the translation row.
• FA_ADDITIONS_VL — the MLS view that unions FA_ADDITIONS_B and FA_ADDITIONS_TL and is the object most application queries should use.
• FA_ADDITIONS — the legacy view presenting addition information for reporting.
• FA_BOOKS — asset distribution across books, joined on ASSET_ID for combined financial and descriptive reporting.
• FA_ASSET_HISTORY and FA_TRANSACTION_HEADERS — joined on ASSET_ID for audit and transaction reporting that requires translated descriptions.
• FND_LANGUAGES — the language registry validating the LANGUAGE column.

Because only FA_ADDITIONS_B, the MLS view FA_ADDITIONS_VL, and FND_LANGUAGES are structurally implicated, direct DML against FA_ADDITIONS_TL should be avoided; description maintenance is performed through the Assets application, which keeps the base and translated tables synchronized.