Search Results fa_mass_additions_gt




Overview
Explore in AI Chat

Overview

FA_MASS_ADDITIONS_GT is a global temporary table owned by the FA schema within the Oracle E-Business Suite OFA – Assets product family. It serves as the staging and interface structure for Mass Additions — the mechanism by which Oracle Payables invoice distribution lines, Oracle Projects expenditure items, and manually entered records are captured, reviewed, and ultimately converted into fixed asset records in FA_ADDITIONS_B. Each row represents a candidate asset or a component thereof awaiting review via the Mass Additions Prepare and Post process.

Rows move through the table in two controlled ways: the Oracle Payables Mass Additions Transfer process inserts invoice-sourced candidates, while the Post Mass Additions process (concurrent program FAMAPT, driven by FA_MASSADD_PUB API) creates the finalized asset rows and updates or deletes the corresponding staging rows. Because the table is a global temporary table, its row lifecycle is bounded by the load and post programs rather than by permanent retention, and it should never be treated as a historical record.

From a data vault modelling perspective, the FK topology mined from the parent-child relationships suggests this object behaves as a standalone structure rather than an integrated hub or link; it is best modelled as a link/satellite hybrid whose natural affinity is transactional staging rather than master data.

Key Information Stored

The documented physical schema exposes 173 columns. The most operationally significant include:

Business-key candidates are not strictly enforced; uniqueness is generally expected across (MASS_ADDITION_ID) plus the source document triad (INVOICE_ID, INVOICE_DISTRIBUTION_ID, LINE_NUM).

Common Use Cases and Queries

Typical scenarios include: reconciling Payables invoice distributions to assets; validating that all mass additions in a batch were posted; and reporting on unposted candidates by queue.

  • Find unposted mass additions awaiting review: 
    SELECT mass_addition_id, asset_number, invoice_number, fixed_assets_cost
FROM   fa_mass_additions_gt
WHERE  posting_status = 'POST' AND queue_name = 'DEFAULT';
  • Trace a Projects-sourced line back to its expenditure item: 
    SELECT m.mass_addition_id, m.project_id, m.task_id, e.expenditure_item_date
FROM   fa_mass_additions_gt m, pa_expenditure_items_all e
WHERE  m.expenditure_item_id = e.expenditure_item_id;
  • Group assets awaiting split/merge processing: filter on SPLIT_CODE or MERGED_CODE and join to FA_GROUP_ASSETS via GROUP_ASSET_ID.
  • Reconciliation reports: aggregate FIXED_ASSETS_COST by BOOK_TYPE_CODE and CREATE_BATCH_ID for period-close tie-outs to Payables.

Because the table is a GTT, the same queries are safe under concurrent Payables and Projects loads — each session sees only its own uncommitted rows.

Related Objects

  • FA_ADDITIONS_B / FA_ADDITIONS_TL — the destination asset tables; rows move here at post time via ASSET_ID.
  • FA_GROUP_ASSETS — grouped-asset definitions, joined on GROUP_ASSET_ID.
  • FA_WARRANTIES — warranty terms, joined on WARRANTY_ID.
  • PA_PROJECT_ASSET_LINES_ALL — Projects asset line source, joined on PROJECT_ASSET_LINE_ID.
  • PA_EXPENDITURE_ITEMS_ALL — expenditure item source, joined on EXPENDITURE_ITEM_ID.
  • AP_INVOICE_PAYMENTS_ALL — payment detail for invoice-originated lines, joined on INVOICE_PAYMENT_ID.
  • FA_MASSADD_PUB — the public API that inserts/updates rows and drives the Post Mass Additions concurrent program.
  • FA_MASS_ADDITIONS — the persistent counterpart view/table used for archived review.