Results for “fa_mass_ret_excepts”

19 results




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

Overview

FA_MASS_RET_EXCEPTS is an Oracle Assets (OFA) table that stores exception records generated during mass retirement processing. When a user initiates a mass retirement transaction in Oracle E-Business Suite, the Mass Retirement program attempts to retire a defined group of assets in a single operation. Assets that cannot be successfully retired — for example, because of invalid validation rules, status conflicts, or data integrity issues — are not discarded silently. Instead, a corresponding row is written to FA_MASS_RET_EXCEPTS, recording the specific asset and the reason it was excluded from the batch.

The table therefore functions as a diagnostic and audit artifact for the mass retirement workflow. It allows users to review why certain assets within a selected group were skipped, correct the underlying issues, and reprocess those assets in a subsequent run. Without this table, failed retirements within a batch would provide no actionable feedback to the user.

From a dimensional modeling perspective, the metadata classifies FA_MASS_RET_EXCEPTS as a standalone object based on its foreign key structure. In Data Vault terms, this suggests treating it as a satellite-like exception record attached to the mass retirement event, rather than a hub or link, because it captures descriptive outcome detail about a parent transaction rather than defining an independent business entity or a relationship between two entities.

Key Information Stored

The table is documented with eight columns. The most significant are:

  • MASS_RETIREMENT_ID — The foreign key identifying the parent mass retirement transaction. This column links every exception back to the specific batch run recorded in FA_MASS_RETIREMENTS.
  • ASSET_ID — The identifier of the individual asset that could not be retired. This is the primary business attribute explaining which asset failed.
  • REASON_CODE — A code indicating why the asset was excluded from the mass retirement. This drives the diagnostic value of the table.
  • CREATION_DATE, CREATED_BY — Standard WHO columns capturing when and by whom the exception record was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and the login session responsible.

The metadata does not document an explicit single-column surrogate primary key or a unique business-key index; the effective uniqueness of a row is implied by the combination of MASS_RETIREMENT_ID and ASSET_ID. The foreign key relationship is defined as FA_MASS_RET_EXCEPTS.MASS_RETIREMENT_ID referencing FA_MASS_RETIREMENTS.

Common Use Cases and Queries

The most common use case is troubleshooting a mass retirement run. Users query the exceptions associated with a given MASS_RETIREMENT_ID to determine which assets failed, then resolve the issues and rerun. Another use case is reporting on retirement failure rates by reason code to identify recurring data problems.

Typical query patterns include joining to FA_MASS_RETIREMENTS on MASS_RETIREMENT_ID to obtain batch context, and joining to FA_ADDITIONS or FA_BOOKS on ASSET_ID to retrieve asset descriptions. A sample pattern:

  • SELECT e.asset_id, e.reason_code FROM fa_mass_ret_excepts e WHERE e.mass_retirement_id = :batch_id;
  • SELECT m.*, e.asset_id, e.reason_code FROM fa_mass_retiremements m JOIN fa_mass_ret_excepts e ON e.mass_retirement_id = m.mass_retirement_id;

Because the table is transactional and grows with each failed retirement attempt, it should be included in any purge or archival strategy for the Assets module.

Related Objects

  • FA_MASS_RETIREMENTS — The parent table; joined on MASS_RETIREMENT_ID. Holds the header record for each mass retirement run.
  • FA_ADDITIONS — Stores asset master data; joined on ASSET_ID to obtain asset_number and description.
  • FA_BOOKS — Contains book-level asset balances; used to validate retirement eligibility alongside exception records.
  • FA_RETIREMENTS — Stores successfully processed retirement transactions, providing the contrast to exception rows.
  • FA_MASS_RET_EXCEPTS reports and concurrent programs — the Mass Retirement process itself is the primary consumer that populates and reads this table.