Results for “fa_deleted_mass_additions”

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

Overview

FA_DELETED_MASS_ADDITIONS is a table in the Oracle E-Business Suite Assets (OFA) module, owned by the FA schema. It stores the invoice and descriptive information of mass addition records that users have removed from the FA_MASS_ADDITIONS interface table through the Delete Mass Additions form. When a pending mass addition is deleted rather than posted to a fixed asset, Oracle Assets relocates the associated invoice details into this table so that a complete audit trail of rejected or discarded capitalizable items is preserved. This enables reconciliation between Oracle Payables invoices and the assets that ultimately entered the fixed asset register.

From a data modeling perspective, the mined relationship data suggests FA_DELETED_MASS_ADDITIONS behaves as a link construct. Its row structure centers on associations between a source mass addition, a payables accounting distribution, a book, and optionally project and task entities, rather than functioning as a pure descriptive satellite.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• MASS_ADDITION_ID — Surrogate primary key (FA_DELETED_MASS_ADDITIONS_PK) and unique business-key column via index FA_DELETED_MASS_ADDITIONS_U1; identifies the deleted mass addition.
• INVOICE_ID and INVOICE_DISTRIBUTION_ID — Link the deleted line to the originating Oracle Payables invoice and its distribution.
• INVOICE_LINE_NUMBER and AP_DISTRIBUTION_LINE_NUMBER — Position the item within the source invoice and AP distribution.
• PAYABLES_CODE_COMBINATION_ID — The payables accounting flexfield for the deleted item, referencing GL_CODE_COMBINATIONS.
• PAYABLES_COST and PAYABLES_UNITS — Cost and unit quantity carried from Payables.
• BOOK_TYPE_CODE — The asset book context, referencing FA_BOOK_CONTROLS.
• PROJECT_ID, TASK_ID, and PROJECT_ASSET_LINE_ID — Project and task identifiers linking back to PA_PROJECTS_ALL, PA_TASKS, and PA_PROJECT_ASSET_LINES_ALL.
• CREATE_BATCH_ID, POST_BATCH_ID, and CREATE_BATCH_DATE — Batch provenance for the original mass addition load.
• INVOICE_DATE, DESCRIPTION, STATUS, and REVIEWER_COMMENTS — Descriptive and status attributes retained for audit.

Common Use Cases and Queries

Typical reporting scenarios include reconciliation of deleted capital line items against Payables and investigation of why specific mass additions never became assets. A reviewer may query this table by book and batch to understand deletion volume:

• Reconciliation query: SELECT m.MASS_ADDITION_ID, m.INVOICE_ID, m.PAYABLES_COST, m.BOOK_TYPE_CODE FROM FA.FA_DELETED_MASS_ADDITIONS m WHERE m.BOOK_TYPE_CODE = :book AND m.CREATE_BATCH_ID = :batch.
• Project asset audit: join PROJECT_ID, TASK_ID, and PROJECT_ASSET_LINE_ID to the PA tables to confirm which project-related additions were discarded.
• Payables linkage: join PAYABLES_CODE_COMBINATION_ID to GL_CODE_COMBINATIONS for accounting validation.

Related Objects

The most significant related objects, based on the documented foreign keys, are:

• FA_MASS_ADDITIONS — joined on MASS_ADDITION_ID; the source interface table from which records were deleted.
• GL_CODE_COMBINATIONS — joined on PAYABLES_CODE_COMBINATION_ID for accounting flexfield validation.
• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE to provide book context.
• PA_PROJECTS_ALL — joined on PROJECT_ID for project details.
• PA_TASKS — joined on TASK_ID for task-level detail.
• PA_PROJECT_ASSET_LINES_ALL — joined on PROJECT_ASSET_LINE_ID to trace project asset lines.