Results for “sold_to”

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

Overview

FA_MASS_EXT_RETIREMENTS is the mass external retirements interface table in the Oracle E-Business Suite Fixed Assets (OFA) module, owned by the FA schema. It serves as a staging and interface structure through which externally sourced retirement transactions are loaded before being validated, processed, and ultimately transferred into the core FA_RETIREMENTS table. The table is central to high-volume asset disposal workflows, where thousands of retirements cannot reasonably be entered manually and must instead be imported from external systems, feeder files, or spreadsheets.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is best modeled as a link entity. It resolves and connects multiple business hubs — assets, retirements, accounting flexfields, locations, distribution history, and concurrent request context — rather than acting as a standalone reference hub or a purely descriptive satellite. Each row represents one retirement line staged for processing within a named batch and reviewed through a defined review status lifecycle.

Key Information Stored

The table contains 68 documented columns at the 12.2.2 schema level, with the most business-critical fields outlined below:

• MASS_EXTERNAL_RETIRE_ID — surrogate primary key, enforced by unique index FA_MASS_EXT_RETIREMENTS_U1. It uniquely identifies each interface line and is the primary business-key candidate.
• BATCH_NAME — groups interface rows into a processing batch for concurrent request submission and reconciliation.
• RETIREMENT_ID — links the staged row to the FA_RETIREMENTS record generated after successful processing.
• BOOK_TYPE_CODE — identifies the depreciation book to which the retirement applies.
• ASSET_ID — the asset being retired.
• REVIEW_STATUS — controls whether the row is accepted, pending, or rejected during validation.
• DATE_RETIRED / DATE_EFFECTIVE — the physical and accounting retirement dates.
• COST_RETIRED, UNITS, PERCENTAGE — define the scope of the partial or full retirement.
• PROCEEDS_OF_SALE, COST_OF_REMOVAL, RETIREMENT_TYPE_CODE — drive gain/loss calculation.
• STL_METHOD_CODE, STL_LIFE_IN_MONTHS, STL_DEPRN_AMOUNT — support straight-line retirement accounting where applicable.
• DISTRIBUTION_ID, CODE_COMBINATION_ID, LOCATION_ID — foreign keys to FA_DISTRIBUTION_HISTORY, GL_CODE_COMBINATIONS, and FA_LOCATIONS respectively.
• REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, tying the batch to its concurrent program execution.
• ATTRIBUTE1–15 and TH_ATTRIBUTE1–15 — two descriptive flexfield contexts for client-specific extension.

Common Use Cases and Queries

Typical scenarios include loading mass retirements from a legacy system, reporting rejected lines, and reconciling staged batches against posted retirements. A representative query lists pending interface lines by batch:

• SELECT batch_name, asset_id, book_type_code, review_status, date_retired FROM fa.fa_mass_ext_retirements WHERE review_status = 'PENDING' AND book_type_code = :book;
• SELECT m.mass_external_retire_id, r.retirement_id FROM fa.fa_mass_ext_retirements m, fa.fa_retirements r WHERE m.retirement_id = r.retirement_id AND m.batch_name = :batch;

Reconciliation reports commonly join to FA_MASS_EXT_RET_EXCEPTS to isolate validation failures, and to FND_CONCURRENT_REQUESTS to trace batch execution history.

Related Objects

The following objects are most significant to this table's operation:

• FA_RETIREMENTS — target table populated on successful processing; joined on RETIREMENT_ID.
• FA_MASS_EXT_RET_EXCEPTS — exception table referencing MASS_EXTERNAL_RETIRE_ID for failed rows.
• FA_EXT_INV_RETIREMENTS — retained-inventory retirement interface referencing the same key.
• FA_DISTRIBUTION_HISTORY — joined on DISTRIBUTION_ID for cost distribution context.
• FA_LOCATIONS — joined on LOCATION_ID for asset location.
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID for accounting flexfield validation.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to link batches to concurrent program runs.