Results for “fa_mass_reclass_pk”

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

Overview

FA_MASS_RECLASS is a transaction and staging table in the Oracle Assets (OFA) module of Oracle E-Business Suite, holding the definition of mass reclass requests. A mass reclassification allows a user to move many assets from one category, location, or other segment value to another within a range of assets, without editing each asset individually. FA_MASS_RECLASS captures the header-level request: the flexfield range used to select the affected assets, the "from" and "to" values applied, and the flags that govern behavior such as amortization of depreciation changes and inheritance of depreciation rules. In the documented 12.2.2 physical schema the table contains 104 columns and is owned by the FA schema.

From a dimensional or Data Vault perspective the metadata's heuristic classification is satellite-leaning, which suggests treating this object as descriptive, request-level detail attached to a primary business key rather than as a true hub or link in its own right. That classification is a modeling suggestion and does not alter the fact that FA_MASS_RECLASS has a single-column surrogate primary key.

Key Information Stored

The surrogate primary key is MASS_RECLASS_ID, enforced by FA_MASS_RECLASS_PK, with a unique index FA_MASS_RECLASS_U1 on the same column serving as the business-key candidate. The most important non-key columns are:

• BOOK_TYPE_CODE — identifies the depreciation book to which the request applies; foreign key to FA_BOOK_CONTROLS.
• STATUS — the processing state of the mass reclass request.
• DATE_EFFECTIVE and TRANSACTION_DATE_ENTERED — the effective date of the reclassification and the date it was entered; DATE_EFFECTIVE drives depreciation timing.
• CONCURRENT_REQUEST_ID — links the row to the concurrent program run that executes the mass reclass; foreign key to FND_CONCURRENT_REQUESTS.
• ASSET_TYPE — narrows the population of assets targeted.
• FROM_CATEGORY_ID and TO_CATEGORY_ID — the category moved from and to (foreign keys to FA_CATEGORIES_B).
• LOCATION_ID — the destination location (foreign key to FA_LOCATIONS).
• ASSET_KEY_ID — the asset key used to group related assets; foreign key to FA_ASSET_KEYWORDS.
• FROM_ASSET_NUMBER and TO_ASSET_NUMBER — the asset-number range that defines the records affected.
• FROM_COST and TO_COST — cost range filters applied to the selection.
• FROM_DATE_PLACED_IN_SERVICE and TO_DATE_PLACED_IN_SERVICE — date-placed-in-service range used to filter candidates.
• SEGMENT1_LOW … SEGMENT30_LOW and SEGMENT1_HIGH … SEGMENT30_HIGH — the flexfield key range identifying assets to be reclassified.
• AMORTIZE_FLAG, COPY_CAT_DESC_FLAG, INHERIT_DEPRN_RULES_FLAG, and INCLUDE_FULLY_RSVD_FLAG — processing behavior controls.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses center on reconciling submitted mass reclass requests with their concurrent program outcomes, reproducing the selection range of a past reclassification, and auditing which categories or locations were targeted. A request may be joined to its concurrent job to report success or failure; another common pattern joins to FA_ADDITIONS_B to confirm the asset-record impact. A representative query retrieving pending requests for a book is:

• SELECT mass_reclass_id, book_type_code, status, date_effective, from_category_id, to_category_id FROM fa_mass_reclass WHERE book_type_code = :book AND status = :status ORDER BY date_effective DESC;

Because the segment low/high columns define the flexfield range, an analyst auditing a reclassification typically extracts SEGMENT1_LOW through SEGMENT30_LOW and the matching HIGH values to reconstruct exactly which assets qualified. Reporting on the transaction pathway uses TRANSACTION_DATE_ENTERED and DATE_EFFECTIVE, while reconciliation with the interface table FA_MASS_RECLASS_ITF confirms which rows were processed.

Related Objects

The FA_MASS_RECLASS row participates in several join paths documented through its foreign keys and through tables that reference it:

• FA_ADDITIONS_B — the asset master, joined through FROM_ASSET_NUMBER and TO_ASSET_NUMBER.
• FA_CATEGORIES_B — the category definitions, joined through FROM_CATEGORY_ID and TO_CATEGORY_ID.
• FA_BOOK_CONTROLS — the depreciation book, joined through BOOK_TYPE_CODE.
• FA_LOCATIONS — the location definition, joined through LOCATION_ID.
• FND_CONCURRENT_REQUESTS — the concurrent request record, joined through CONCURRENT_REQUEST_ID.
• FA_ASSET_KEYWORDS — the asset key grouping, joined through ASSET_KEY_ID.
• FA_MASS_RECLASS_ITF — the interface/staging table, which references FA_MASS_RECLASS through MASS_RECLASS_ID and holds rows pending or processed by the mass reclass concurrent program.
• PSB_EMPLOYEES — the employee reference, joined through EMPLOYEE_ID.

Together these relationships make FA_MASS_RECLASS the defining header for a mass reclassification request, with FA_MASS_RECLASS_ITF acting as its execution interface and FA_ADDITIONS_B, FA_CATEGORIES_B, and FA_BOOK_CONTROLS supplying the master data the request operates against.