Search Results fa_adjustment_pvt




Overview
Explore in AI Chat

Overview

FA_ADJUSTMENT_PVT is a private (PVT-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It encapsulates the core business logic used to create and validate financial adjustments against asset cost, including additions, revaluations, and other cost-basis changes recorded in Oracle Assets (Fixed Assets). Adjustments represent changes to an asset's cost or related financial attributes after the asset has been placed in service, and these changes flow through to depreciation and book balances. The package sits beneath the public adjustment API layer, specifically FA_ADJUSTMENT_PUB, and is therefore not intended to be called directly by external consumers. It provides the internal processing routines that the public API delegates to, ensuring that validation, stacking of transactions in the interface table, and eventual posting to the adjustment and depreciation tables occur in a controlled sequence. Its status in the data dictionary is VALID, and it depends on standard Oracle components including FA_API_TYPES, FND_GLOBAL, and the STANDARD package, with DBMS_LOCK used for concurrency control during adjustment processing.

Key Procedures and Functions

  • VALIDATE_ADJUSTMENT — Performs pre-processing validation on an adjustment request. It confirms that the asset, book, and adjustment attributes supplied by the caller are consistent with the configuration defined in the depreciation method, book, and formula setup tables before any data is written.
  • DO_ADJUSTMENT — Executes the actual adjustment processing once validation succeeds. This routine is responsible for applying the cost or financial change, propagating it to the adjustment and depreciation detail records, and handling multi-currency book implications where applicable.
  • PROCESS_TRX_STACK — Manages the transaction stack, the accumulation mechanism by which pending adjustment transactions are gathered and processed in a batch. It coordinates the ordering and commit behavior of queued transactions, using locking to prevent concurrent modification of the same asset or book records.

The three documented routines form a validate-then-execute pattern, with the stack processing routine providing the transactional wrapper that supports both single and bulk adjustment scenarios.

Tables Accessed

  • FA_ADJUSTMENTS — Primary destination for adjustment rows, storing the cost adjustments applied to assets.
  • FA_MC_ADJUSTMENTS — Corresponding adjustment records for multi-currency (reporting) books.
  • FA_BOOKS — Asset book balances, read to validate the asset's current cost and updated when adjustments alter the cost basis.
  • FA_DEPRN_DETAIL and FA_MC_DEPRN_DETAIL — Depreciation detail rows for the primary and multi-currency books, recalculated to reflect the adjusted cost.
  • FA_METHODS, FA_FORMULAS, FA_DEPRN_RULE_DETAILS — Depreciation setup tables consulted during validation to confirm that the adjustment is permissible under the assigned method and formula.
  • DBMS_LOCK and DUAL — Used for serialization of processing and utility queries respectively.

Usage Notes

Because this is a PVT package, it should not be invoked directly from custom code, concurrent programs, or forms. It is referenced by five higher-level packages: FA_ADDITION_PUB, FA_ADJUSTMENT_PUB, FA_CIP_PUB, FA_GROUP_RECLASS2_PVT, and FA_RETIREMENT_PVT, and is also self-referencing. Adjustments are normally initiated through the Oracle Assets forms (for example, the Asset Workbench and Adjustments windows) or through the public FA_ADJUSTMENT_PUB API, which in turn calls this package. In ETRM 12.2.2 the documented surface comprises exactly three procedures, so integrations should target the public layer; any direct dependency on FA_ADJUSTMENT_PVT risks breakage during patching or upgrades. The presence of DBMS_LOCK confirms that concurrent adjustment submissions against the same asset are serialized, so callers should expect standard locking behavior during high-volume batch runs.