Search Results store_results

Overview

FARX_MCP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM taxonomy as OTHER. It forms part of the Oracle Assets (FA) mass change feature set, which allows users to apply attribute changes — such as category, depreciation method, life, or cost adjustments — across large populations of assets in a single operation rather than editing each asset individually. The "MCP" suffix denotes mass change preview. The package operates with AUTHID CURRENT_USER and is designated as ship-eligible code, with a header lineage traced to FARXMCPS.pls (version 120.1, March 2009).

In Oracle EBS 12.1.1 and 12.2.2, mass change processing follows a preview-then-commit model. FARX_MCP supports the preview phase by computing the effect of a proposed change on each selected asset and staging the outcome for review before any permanent update is applied. This design protects the fixed asset register from unintended revaluation or reclassification.

Key Procedures and Functions

Two procedures are documented in the ETRM metadata for this package.

• PREVIEW_CHANGE — Generates the preview results for a mass change. It is invoked from the concurrent wrapper procedure FARX_C_CP.Mass_Change_Preview(), indicating that it is normally executed through a concurrent program rather than interactively. It reads the user's asset selection and change criteria from the FA_MASS_CHANGES table, evaluates the impact of the proposed change, and inserts the resulting rows into the FA_MASS_CHANGE_ITF interface table. Its documented parameters include X_Mass_Change_Id (the identifier from FA_MASS_CHANGES), X_RX_Flag (indicating whether the call originated from an RX report), and the standard OUT parameters retcode and errbuf that communicate completion status (0 normal, 1 warning, 2 error) and any error or warning text.
• STORE_RESULTS — Persists the preview results for an individual asset into a private PL/SQL asset table declared as FA_MASS_CHG_UTILS_PKG.asset_table, covering all books to which the asset belongs. The procedure applies the necessary output conversions so that computed values are suitable for display or further processing. Its documented parameters include X_mc_rec (a record of type FA_MASS_CHG_UTILS_PKG.mass_change_rec_type) and X_To_RSR, the new rate source rule. In effect, STORE_RESULTS is the per-asset accumulator that PREVIEW_CHANGE and related logic draw upon when assembling interface rows.

Tables Accessed

The documented table references, resolved through APPS synonyms, reflect the breadth of data required to model an asset change:

• FA_MASS_CHANGES and FA_MASS_CHANGES_ITF — the mass change definition and its interface (staging) table; FARX_MCP reads criteria from the former and writes preview output to the latter.
• FA_ADDITIONS and FA_ADDITIONS_B — the base asset rows (the _B and _TL pair pattern used throughout Oracle Applications); the _B table holds the language-independent asset definition.
• FA_BOOKS — the per-book asset balances, needed because an asset may belong to multiple depreciation books.
• FA_METHODS — depreciation method definitions, relevant when a mass change alters method or rate.
• FA_LOOKUPS — Oracle Assets lookup values used for validating or decoding codes.
• FA_SYSTEM_CONTROLS — system-level settings, including the set of books and control parameters governing asset processing.
• PLITBLM — the PL/SQL table-to-indexed-table alignment utility used by the Oracle Forms infrastructure, indicating the package interacts with or is callable from Assets forms.

Usage Notes

FARX_MCP is not an end-user-facing API. It is an internal component executed in two principal contexts. First, PREVIEW_CHANGE is driven by the concurrent program wrapper FARX_C_CP.Mass_Change_Preview(), which is submitted from the Oracle Assets Mass Changes form or the concurrent manager. Second, STORE_RESULTS is called within the mass change processing flow to accumulate per-asset results across books. The package is referenced by one other package, consistent with its supporting role.

Because the package holds AUTHID CURRENT_USER privileges and manipulates fixed asset financial data, customizations should not call it directly. Integrations that require mass asset updates should instead use the supported Mass Changes form and concurrent program, letting FARX_MCP manage preview staging and interface population internally. The FA_MASS_CHANGE_ITF rows it produces are the recommended integration point for downstream reporting or validation before the change is committed.