Results for “add_to_asset_id”

50+ results




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

Overview

FA_MASS_ADDITIONS is a core table in the Oracle Assets (OFA) module of Oracle E-Business Suite, holding the staging and control records for assets that an external feeder system — such as Payables, Projects, Purchasing, or a third-party source — intends to add automatically into Oracle Assets. Each row represents a mass addition line that originates from an external source and is processed through the Mass Additions queue before being posted to the FA_ADDITIONS_B asset register (or rejected, merged, or split). The table supports the entire lifecycle of a mass addition: creation from an external source, review, adjustment, merge, split, and final posting to a book controlled by FA_BOOK_CONTROLS.

The ETRM metadata classifies this object heuristically as satellite-leaning. In a Data Vault 2.0 interpretation, FA_MASS_ADDITIONS would be modeled as a satellite on a business key such as ASSET_NUMBER or MASS_ADDITION_ID, with links to AP invoices, projects, purchase orders, and the asset register. This classification reflects the table's role as an attribute-rich, transaction-scoped record rather than a pure hub or link.

Key Information Stored

The table carries 205 documented columns and is uniquely identified by the surrogate primary key MASS_ADDITION_ID via FA_MASS_ADDITIONS_PK and the unique index FA_MASS_ADDITIONS_U1. Business-identifying attributes include:

Common Use Cases and Queries

The most frequent operational query is to inspect mass additions awaiting review or posting, often filtered by queue and book:

SELECT mass_addition_id, asset_number, description, book_type_code, posting_status, queue_name, fixed_assets_cost FROM fa.fa_mass_additions WHERE posting_status = 'ON QUEUE' AND book_type_code = :book;

Reporting patterns typically join to FA_ADDITIONS_B to reconcile posted mass additions against the asset register, to AP_INVOICES_ALL via INVOICE_ID for invoice-to-asset reconciliation, and to PA_PROJECT_ASSET_LINES_ALL via PROJECT_ASSET_LINE_ID for capitalized project costs. Common scenarios include: identifying duplicate invoices before posting, tracing merge/split lineage through PARENT_MASS_ADDITION_ID, and querying by FEEDER_SYSTEM_NAME to audit third-party integration feeds. The FA_MASSADD_DISTRIBUTIONS child table is frequently joined to obtain the multi-distribution breakdown per mass addition.

Related Objects