Search Results fa_mass_additions_v




Overview
Explore in AI Chat

Overview

FA_MASS_ADDITIONS_V is an Oracle E-Business Suite Assets (OFA) view owned by the APPS schema. It exposes the contents of the mass additions interface table FA_MASS_ADDITIONS together with derived and secured data drawn from asset, book control, payables, and HR sources. The view is used extensively during the Oracle Payables to Oracle Assets mass additions flow, and it underpins the Mass Additions workbench, the Prepare Mass Additions form, and related concurrent programs and reports.

Because the view resolves security-sensitive elements (book security, asset security, and person information) through underlying packages and views such as FA_BOOK_CONTROLS_SEC, FA_ADDITIONS_NON_SEC_VL, HR_SECURITY, HR_GENERAL, and HR_PERSON_NAME, it presents a business-user-facing representation of mass addition lines rather than a raw table read. It is treated as a read-only view and is typically queried for reconciliation, interface troubleshooting, and custom reporting where the user needs visibility into expense, payables, and asset account code combinations for pending mass additions.

Underlying Base Objects

The view is defined over the following documented base objects:

  • FA_MASS_ADDITIONS (synonym) — the primary interface table holding mass addition lines posted from Payables or entered manually.
  • FA_ADDITIONS_B and FA_ADDITIONS_NON_SEC_VL — asset definition data used to link mass additions to existing assets and to resolve descriptions and identifiers.
  • FA_BOOK_CONTROLS_SEC — book security, restricting rows to books the user is authorized to see.
  • FA_LEASES, FA_LOOKUPS, FA_WARRANTIES — supporting reference and supplementary asset information.
  • PO_VENDORS — supplier information for mass additions originating from purchasing.
  • PER_PEOPLE_F — employee/person records for the Assigned To element.
  • HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — packaged functions controlling name formatting and security predicates.

Because the view embeds security logic, querying it as APPS returns only rows visible under the invoking user's asset book and organization security profile. Direct queries against FA_MASS_ADDITIONS do not enforce those predicates.

Key Columns

Principal columns exposed by the view include:

The presence of EXPENSE_CODE_COMBINATION_ID is central to account verification workflows, where the expense account on the mass addition must align with the depreciation expense account defined in the asset category and book.

Common Use Cases and Queries

Typical scenarios include identifying mass additions whose expense account is missing or mismatched, reconciling Payables-to-Assets transfers, and reporting on pending queues before running the Post Mass Additions program.

Sample query listing mass additions with unresolved expense accounts:

SELECT mass_addition_id,
       asset_number,
       book_type_code,
       posting_status,
       expense_code_combination_id,
       payables_code_combination_id,
       fixed_assets_cost
  FROM apps.fa_mass_additions_v
 WHERE expense_code_combination_id IS NULL
   AND posting_status = 'POST';

Sample query joining to the GL code combinations table to display the expense account string:

SELECT m.mass_addition_id,
       m.asset_number,
       m.book_type_code,
       gcc.concatenated_segments expense_account,
       m.fixed_assets_cost,
       m.invoice_number
  FROM apps.fa_mass_additions_v m,
       apps.gl_code_combinations_kfv gcc
 WHERE m.expense_code_combination_id = gcc.code_combination_id
   AND m.posting_status = 'POST';

Because the view enforces book and person security, these queries return only the rows authorized for the session user. For high-volume reconciliation, restricting by CREATE_BATCH_ID or ACCOUNTING_DATE improves performance, since the view aggregates several underlying objects.