Search Results fa_additions_non_sec_vl




Overview
Explore in AI Chat

Overview

The FA_ADDITIONS_NON_SEC_VL view is a security-stripped, language-enabled reporting view owned by the APPS schema in the Oracle E-Business Suite Fixed Assets (OFA) module. In Release 12.1.1 and 12.2.2 it exposes the descriptive and financial-attribute columns of capital and CIP asset additions without imposing the row-level organization security that governs the operational concurrent programs and forms. The view is defined over the FA_ADDITIONS_B and FA_ADDITIONS_TL synonyms, presenting a single denormalized result set in which each asset appears exactly once.

Because the view is not organization-secure, it is intended for reporting, data extraction, and integration scenarios where the caller is already authorized to read the full asset book — for example, corporate roll-up reports, custom OBIEE or Discoverer datasets, and outbound interfaces feeding a data warehouse. It is not a substitute for the security-enabled FA_ADDITIONS_VL view used by the standard Fixed Assets forms, and privileges to query it should be granted deliberately within custom applications.

Underlying Base Objects

The view is defined over two documented base objects:

  • FA_ADDITIONS_B — the base table holding the non-translatable asset attributes such as ASSET_ID, ASSET_NUMBER, ASSET_KEY_CCID, PARENT_ASSET_ID, TAG_NUMBER, SERIAL_NUMBER, and the ATTRIBUTE1 through ATTRIBUTE30 flexfield columns. In the view text this table is aliased as B and supplies the ROWID as ROW_ID along with the majority of the columns.
  • FA_ADDITIONS_TL — the translation table holding the language-specific asset DESCRIPTION. In the view text this table is aliased as T; the join yields the DESCRIPTION column in the session's current language.

The view joins FA_ADDITIONS_B to FA_ADDITIONS_TL on ASSET_ID, so one row of FA_ADDITIONS_B is matched to the corresponding translated row in FA_ADDITIONS_TL. Because both source objects are referenced through APPS synonyms, the view resolves to the FA schema objects at runtime while remaining selectable by any user granted the appropriate APPS synonym and view privileges.

Key Columns

The projected columns fall into several functional groups:

Common Use Cases and Queries

Typical uses include asset master extracts, parent-child hierarchy reporting, and feeding downstream systems. A simple retrieval of asset identity and description:

  • SELECT asset_id, asset_number, tag_number, description FROM apps.fa_additions_non_sec_vl;

To identify children of a given parent asset, filtering on the searched column:

  • SELECT asset_id, asset_number, parent_asset_id FROM apps.fa_additions_non_sec_vl WHERE parent_asset_id = :parent_asset_id;

To list additions missing a description or to walk the hierarchy with a self-join:

  • SELECT c.asset_number, p.asset_number AS parent_number FROM apps.fa_additions_non_sec_vl c JOIN apps.fa_additions_non_sec_vl p ON c.parent_asset_id = p.asset_id;

Because the view is security-stripped and language-enabled, results reflect all assets in the environment and the DESCRIPTION returned matches the session language, making it well suited to reporting and integration rather than transactional processing.