Results for “deprn_reserve_acct”

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

Overview

FA_MASS_RECLASS_ITF is the Report eXchange interface table for the Oracle Assets (OFA) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the FA schema and is documented as a standard interface table used to stage and validate mass reclassification data prior to processing. The table is populated by Report eXchange (RX) reports and consumed by concurrent programs that perform bulk asset reclassification, allowing many assets to be moved from one asset category, depreciation method, convention, ceiling, or book to another in a single batch run.

From a modeling perspective, the table is classified heuristically as a link in the Data Vault sense, because its structure ties together several independent business entities — assets, asset books, and mass reclassification requests — through foreign keys rather than acting as a pure hub or satellite. The 29 documented columns capture both the target reclassification attributes and the audit and concurrency context required to drive the mass reclassification process.

Key Information Stored

The table stores both the identity of the asset being reclassified and the classification attributes to which it is being moved. The most significant columns are:

• MASS_RECLASS_ID — the primary business identifier of the mass reclassification transaction; foreign key to FA_MASS_RECLASS.
• ASSET_ID and ASSET_NUMBER — the surrogate and business identifiers of the asset, both derived from FA_ADDITIONS_B.
• BOOK — the depreciation book in which the reclassification applies; validated against FA_BOOK_CONTROLS.
• OLD_CATEGORY and NEW_CATEGORY — the source and destination asset categories driving the reclassification.
• CONVENTION, CEILING, and METHOD — depreciation convention, ceiling, and method codes validated against FA_CONVENTION_TYPES, FA_CEILING_TYPES, and FA_METHODS respectively.
• LIFE — the resulting useful life of the asset after reclassification.
• BASIC_RATE and ADJUSTED_RATE — the depreciation rates applied under the new method.
• COST_ACCT and DEPRN_RESERVE_ACCT — the cost and depreciation reserve accounts impacted by the change.
• REQUEST_ID — the concurrent request that created or processed the interface row; foreign key to FND_CONCURRENT_REQUESTS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ASSET_TYPE, DEPRECIATE_FLAG, BONUS_RULE, PRODUCTION_CAPACITY, UNIT_OF_MEASURE — additional depreciation and capacity attributes carried through the reclassification.

The metadata does not document a surrogate primary key separate from MASS_RECLASS_ID; no unique index is explicitly documented, so column combinations such as (MASS_RECLASS_ID, ASSET_ID, BOOK) are the practical business-key candidates.

Common Use Cases and Queries

Typical use cases include pre-processing validation of mass reclassification batches, reconciliation of staged rows against the final FA_MASS_RECLASS records, and audit reporting of which assets were moved and by which concurrent request.

A representative query to review staged reclassifications for a specific run is:

• SELECT asset_number, book, old_category, new_category, method, life, request_id FROM fa.fa_mass_reclass_itf WHERE request_id = :p_request_id;

A validation query joining to FA_ADDITIONS_B to confirm the asset exists in the expected book, and to FA_BOOK_CONTROLS to confirm the book is valid, is also common. Reporting extracts frequently join FND_CONCURRENT_REQUESTS to correlate the interface rows with the originating RX job.

Related Objects

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

• FA_MASS_RECLASS — drives the batch via MASS_RECLASS_ID.
• FA_ADDITIONS_B — source of ASSET_ID and ASSET_NUMBER.
• FA_BOOK_CONTROLS — validates the BOOK column.
• FA_METHODS — validates METHOD.
• FA_CONVENTION_TYPES — validates CONVENTION.
• FA_CEILING_TYPES — validates CEILING.
• FND_CONCURRENT_REQUESTS — links rows to the originating concurrent request via REQUEST_ID.

These relationships make FA_MASS_RECLASS_ITF the staging and validation layer between Report eXchange input and the permanent mass reclassification records held in FA_MASS_RECLASS.