Results for “from_method_code”

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

Overview

FA_MASS_CHANGES is a transactional table in the Oracle E-Business Suite Fixed Assets (OFA) module, owned by the FA schema. It stores mass change request information — that is, user-defined requests to apply a common set of attribute modifications across multiple assets in a single operation. A mass change request is created when a user invokes the Mass Changes feature (for example, to reclassify a group of assets, change depreciation methods, extend useful lives, or adjust salvage values), and this table persists the parameters, status, and audit attributes of that request.

Under the heuristic Data Vault classification derived from its foreign key structure, FA_MASS_CHANGES models as satellite-leaning. It carries descriptive and historical change-request attributes linked to multiple parent entities (books, assets, methods, conventions, categories, and concurrent requests) rather than functioning as a pure hub or a pure associative link. Modelers should treat it as a descriptive satellite attached to the assets and book hubs, noting the unusually high number of foreign key references.

Key Information Stored

The table is documented with 71 columns, though the following are the most operationally significant.

• MASS_CHANGE_ID — the surrogate primary key, defined by the unique index FA_MASS_CHANGES_U1 and the FA_MASS_CHANGES_PK constraint. It also serves as the sole business-key candidate.
• BOOK_TYPE_CODE — the depreciation book against which the mass change applies; foreign key to FA_BOOK_CONTROLS.
• CONCURRENT_REQUEST_ID — links the request to the concurrent manager job (FND_CONCURRENT_REQUESTS) that processes the change.
• STATUS, TRANSACTION_DATE_ENTERED, and DATE_EFFECTIVE — control the lifecycle and effective dating of the request.
• FROM_/TO_ pairs — the change payload. These include FROM_ASSET_NUMBER/TO_ASSET_NUMBER, FROM_DATE_PLACED_IN_SERVICE/TO_DATE_PLACED_IN_SERVICE, FROM_CONVENTION/TO_CONVENTION, FROM_METHOD_CODE/TO_METHOD_CODE, FROM_LIFE_IN_MONTHS/TO_LIFE_IN_MONTHS, and the rate, salvage, and depreciation-limit equivalents (FROM_BASIC_RATE/TO_BASIC_RATE, FROM_SALVAGE_VALUE/TO_SALVAGE_VALUE, FROM_DEPRN_LIMIT/TO_DEPRN_LIMIT, and so on).
• CATEGORY_ID — target asset category, foreign key to FA_CATEGORIES_B.
• FROM_GROUP_ASSET_ID / TO_GROUP_ASSET_ID — group asset references to FA_ADDITIONS_B when the change targets grouped assets.
• AMORTIZE_FLAG / AMORTIZED_CHANGE / ALLOW_OVERLAPPING_ADJ_FLAG — control how the change interacts with amortization and prior adjustments.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN provide standard audit tracking.
• ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY_CODE — flexfield descriptors for extensibility.

Common Use Cases and Queries

Typical uses include auditing mass change history, diagnosing failed or pending requests, and reconciling asset attribute changes to their source request. A frequently used query lists completed changes for a book:

• SELECT mc.mass_change_id, mc.book_type_code, mc.status, mc.date_effective FROM fa_mass_changes mc WHERE mc.book_type_code = :book AND mc.status = 'COMPLETE' ORDER BY mc.transaction_date_entered DESC;
• Joining to the concurrent request to surface log and phase details: SELECT mc.mass_change_id, r.request_id, r.phase_code, r.status_code FROM fa_mass_changes mc, fnd_concurrent_requests r WHERE mc.concurrent_request_id = r.request_id;
• Reporting method or life changes: SELECT from_method_code, to_method_code, from_life_in_months, to_life_in_months FROM fa_mass_changes WHERE mass_change_id = :id;

Related Objects

The following depend on or are referenced by FA_MASS_CHANGES:

• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE.
• FA_ADDITIONS_B — joined on FROM_ASSET_NUMBER/TO_ASSET_NUMBER and FROM_GROUP_ASSET_ID/TO_GROUP_ASSET_ID.
• FA_METHODS — joined on FROM_METHOD_CODE and TO_METHOD_CODE.
• FA_CONVENTION_TYPES — joined on FROM_CONVENTION and TO_CONVENTION.
• FA_CATEGORIES_B — joined on CATEGORY_ID.
• FND_CONCURRENT_REQUESTS — joined on CONCURRENT_REQUEST_ID.
• FA_MASS_CHANGES_ITF — the interface table whose MASS_CHANGE_ID references this table, used during request processing.