Search Results fa_additions_tl_u1

Overview

FA.FA_ADDITIONS_TL is the translation (TL) table for asset additions in the Oracle E-Business Suite Fixed Assets (FA) module. In EBS multi-language installations, the base asset addition record is stored in FA_ADDITIONS_B, while FA_ADDITIONS_TL holds the language-specific descriptive attributes—most notably the user-facing description of the asset addition—keyed by ASSET_ID and LANGUAGE. This enables the same asset addition to display a description translated into any installed language without duplicating the entire addition record.

The object is owned by the FA schema and is registered under FND Design Data OFA.FA_ADDITIONS_TL. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index lives in APPS_TS_TX_IDX. The table is a standalone object: it does not reference any other database object through a declared foreign key, and it is referenced only by the APPS synonym FA_ADDITIONS_TL.

From a Data Vault perspective, the heuristic classification of this object is a satellite. It carries descriptive, language-dependent attributes attached to the asset addition business key rather than representing a hub or a link. The natural composite key is ASSET_ID combined with LANGUAGE, which functions as the surrogate primary key.

Key Information Stored

The table records nine documented columns. The most significant are:

• ASSET_ID (NUMBER, 15) — part of the composite primary key; identifies the parent asset addition in FA_ADDITIONS_B.
• LANGUAGE (VARCHAR2) — part of the composite primary key; the language code for the translated row.
• DESCRIPTION (VARCHAR2, 80) — the translated asset addition description, the principal end-user visible attribute held in this table.
• SOURCE_LANG (VARCHAR2) — indicates the source language from which the translation was derived.
• Standard WHO audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, which capture creation and change metadata for each translated row.

The surrogate primary key is FA_ADDITIONS_TL_PK (ASSET_ID, LANGUAGE). The documented unique index FA_ADDITIONS_TL_U1 also spans (ASSET_ID, LANGUAGE), confirming that this pair is the effective business key. The query term "fa_additions_tl_u1" corresponds directly to that unique index, which enforces one translated description per asset addition per language and supports fast lookup by asset. Because only ASSET_ID and LANGUAGE are mandatory, translations can exist with a null DESCRIPTION where a description has not yet been supplied for that language.

Common Use Cases and Queries

Typical use cases include multilingual asset reporting, verifying that an addition description exists in a required language, and auditing translations for completeness.

• Retrieving the description for a specific asset in a specific language: SELECT DESCRIPTION FROM FA.FA_ADDITIONS_TL WHERE ASSET_ID = :asset_id AND LANGUAGE = USERENV('LANG');
• Joining base and translation tables to report asset additions with their translated descriptions: SELECT b.ASSET_ID, t.DESCRIPTION FROM FA.FA_ADDITIONS_B b, FA.FA_ADDITIONS_TL t WHERE b.ASSET_ID = t.ASSET_ID AND t.LANGUAGE = 'US';
• Identifying asset additions missing a translation in an installed language by comparing FA_ADDITIONS_B against FA_ADDITIONS_TL.

Related Objects

• FA_ADDITIONS_B — base table holding the untranslated asset addition; joined on ASSET_ID.
• FA_ADDITIONS_TL_U1 — the unique index on (ASSET_ID, LANGUAGE) that enforces business-key integrity.
• FA_ADDITIONS_TL_PK — the composite primary key constraint.
• APPS.FA_ADDITIONS_TL — the APPS-level synonym used by application code and reports.
• FA_ADDITIONS_V and related FA views — views that expose translated addition information for forms and inquiries. These depend on this table primarily through ASSET_ID and LANGUAGE.