Results for “from_life_in_months”

28 results




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

Overview

FA_MASS_CHANGES_ITF is an interface (staging) table in the Oracle Assets (OFA) module, owned by the FA schema. Its documented purpose is to serve as the interface table for Report eXchange reports. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 architecture, it holds the transient rows that describe mass changes to be applied to asset records — the "before" and "after" values for depreciation attributes such as method, life, convention, salvage, depreciation limit, bonus rule, and group asset assignment. Rather than being a permanent repository, it acts as the pre-processing bridge between the seeded Report eXchange interface rows and the mass change operations that ultimately affect the master asset tables.

From a dimensional modeling perspective, the mined Data Vault classification for this object is link. That is a heuristic suggestion: FA_MASS_CHANGES_ITF is dominated by foreign-key relationships to surrounding hubs and reference tables (assets, books, conventions, bonus rules, and the parent mass change record itself), which is consistent with a link entity connecting those business keys. It should not be treated as a satellite of any single parent.

Key Information Stored

The table contains 41 documented columns. The most operationally significant are the following:

The surrogate primary key is intended to be a system-generated identifier, while ASSET_ID plus BOOK plus MASS_CHANGE_ID functions as the practical business-key candidate for uniquely locating an asset's change line within a request.

Common Use Cases and Queries

The primary use case is validating and reporting on mass change submissions prior to commit, and diagnosing why a mass change failed. Typical queries join the interface to FA_MASS_CHANGES to review a batch:

  • List all interface lines for a given concurrent request: SELECT * FROM fa_mass_changes_itf WHERE request_id = :p_request_id;
  • Identify assets proposed for a method/life change by comparing FROM and TO columns: SELECT asset_number, from_method_code, to_method_code, from_life_in_months, to_life_in_months FROM fa_mass_changes_itf WHERE from_method_code <> to_method_code;
  • Detect rows where the book value or convention will shift, by joining to FA_BOOK_CONTROLS on BOOK.
  • Reconcile interface content against the parent definition: SELECT i.*, m.* FROM fa_mass_changes_itf i, fa_mass_changes m WHERE i.mass_change_id = m.mass_change_id;
  • Audit who created or modified interface rows using CREATED_BY and LAST_UPDATED_BY.

These queries support pre-submission verification, exception reporting, and reconciliation of Report eXchange output back to the asset register.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships:

  • FA_MASS_CHANGES — parent table joined via MASS_CHANGE_ID; defines the mass change request.
  • FA_ADDITIONS_B — referenced by ASSET_ID, ASSET_NUMBER, FROM_GROUP_ASSET_NUMBER, and TO_GROUP_ASSET_NUMBER; supplies asset and group asset identity.
  • FA_BOOK_CONTROLS — referenced by BOOK; defines depreciation book attributes.
  • FA_CONVENTION_TYPES — referenced by FROM_CONVENTION and TO_CONVENTION.
  • FA_BONUS_RULES — referenced by FROM_BONUS_RULE and TO_BONUS_RULE.
  • The Assets mass change concurrent programs and Report eXchange report definitions that populate and consume this interface table.

Together these relationships explain the link classification: FA_MASS_CHANGES_ITF sits at the intersection of a mass change request, an asset, a book, and the reference tables that govern depreciation behavior.