Search Results check_trans_date_book

Overview

FARX_RP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified under the ETRM taxonomy as an "OTHER" API, meaning it is not a formally published open interface but is instead an internal utility package that supports the Oracle Assets mass reclassification feature. The package encapsulates the logic required to preview and stage the results of a mass reclassification run before any data is committed to the production asset tables.

Mass reclassification allows an organization to move many assets from one asset category, depreciation book, or distribution combination to another in a single operation. Because such a change affects depreciation, distribution history, and general ledger balances, Oracle Assets provides a preview step so that users may review the proposed changes before confirming them. FARX_RP supplies the server-side machinery for that preview, validating each candidate asset against the reclassification rules and writing the accepted rows into an interface table for downstream review and reporting.

Key Procedures and Functions

The package exposes three documented procedures:

• PREVIEW_RECLASS — The primary procedure for mass reclass preview. It is invoked from the concurrent wrapper procedure FARX_C_RP.Mass_Reclass_Preview(). It calls the Reclass Validation Engine to determine whether a given asset may be reclassified, and, when validation succeeds, inserts the resulting rows into the FA_MASS_RECLASS_ITF interface table. User asset selection and reclass criteria are read from FA_MASS_RECLASS. It accepts a mass reclass identifier, a flag indicating whether the call originates from the RX report, and the standard concurrent retcode and errbuf OUT parameters used to communicate completion status and messages.
• STORE_RESULTS — Stores the preview results for an asset into a private PL/SQL asset table defined by the FA_MASS_REC_UTILS_PKG.asset_table type, covering every book to which the asset belongs. Output conversions are handled within this procedure. It also supports retrieving new depreciation rules from FA_LOAD_TBL_PKG.deprn_table when the caller elects to re-default them.
• CHECK_TRANS_DATE_BOOK — A supporting validation routine, referenced by the package metadata, used in conjunction with mass reclassification processing to verify transaction date and book relationships before staging results.

Tables Accessed

The package reads and writes a defined set of Oracle Assets and related tables, accessed through APPS synonyms:

• FA_MASS_RECLASS and FA_MASS_RECLASS_ITF — the driver table holding user selection and reclass criteria, and the interface table receiving preview results.
• FA_ADDITIONS, FA_BOOKS, FA_BOOK_CONTROLS, FA_DEPRN_PERIODS — asset definition, book assignment, book control, and depreciation period data used during validation.
• FA_DISTRIBUTION_HISTORY and FA_TRANSACTION_HEADERS — distribution and transaction history required to assess reclassification impact.
• FA_LOOKUPS and FA_SYSTEM_CONTROLS — reference and system-level control information.
• GL_CODE_COMBINATIONS — general ledger account validation for destination distribution combinations.
• PLITBLM — the PL/SQL table used for internal collection processing.

Usage Notes

FARX_RP is not intended for direct invocation by end users or by custom integrations. It is called internally from the concurrent wrapper FARX_C_RP.Mass_Reclass_Preview(), which is registered as a concurrent program in Oracle Assets. The typical invocation path is: a user defines a mass reclassification in the Mass Reclassifications form or concurrent program, the request is submitted, and FARX_C_RP calls FARX_RP.PREVIEW_RECLASS to validate and stage the results. The preview rows in FA_MASS_RECLASS_ITF may then be reviewed before the user confirms the reclassification.

Because the package is an "OTHER" classification object and is referenced by one other package, it should be treated as internal implementation. Customizations should not call FARX_RP directly, as its signature and behavior are not guaranteed across patches or point releases; instead, custom code should use supported Oracle Assets APIs or the delivered concurrent programs.