Search Results do_unplanned

Overview

FA_UNPLANNED_PVT is a private (PVT-classified) PL/SQL package in the Oracle E-Business Suite Fixed Assets (FA) module, owned by the APPS schema. It implements the internal business logic responsible for processing unplanned depreciation transactions within Oracle Assets. Unplanned depreciation is used when an asset must be depreciated outside the standard depreciation run — for example, when a one-time adjustment is required due to a correction, a change in the depreciation method or life, a revaluation, or a manual override of the calculated depreciation amount. As a private helper package, FA_UNPLANNED_PVT performs the low-level validation, data retrieval, and calculation work that underlies the public-facing Fixed Assets API surface.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer. Its header, last updated at version 120.3 (2009), exposes a single documented function, DO_UNPLANNED, and does not define any standalone procedures. It is one of the internal building blocks of the transactional asset API architecture, and it is referenced by one other package in the schema, indicating that it is invoked indirectly rather than directly by end users or external code.

Key Procedures and Functions

• DO_UNPLANNED — The sole documented function and the entry point of the package, matching the user search term "do_unplanned". It returns a BOOLEAN success/failure indicator and accepts a comprehensive set of record-type parameters covering the transaction, asset header, asset description, asset type, asset category, financial, depreciation, unplanned depreciation, and period records, together with an MRC set-of-books type code and a logging level record. In operation, DO_UNPLANNED drives the unplanned depreciation process: it receives the assembled asset and transaction context, resolves the applicable depreciation rules and book controls, computes the unplanned amount, validates the result, and writes the resulting depreciation data. Because this is a private package, the function is not intended for direct invocation from custom code; callers interact with the public Fixed Assets APIs, which in turn delegate to this routine.

Tables Accessed

The package reads and writes the following documented tables (referenced through APPS synonyms):

• FA_BOOKS — The central depreciation table holding per-book, per-asset, per-period cost and depreciation balances. DO_UNPLANNED reads current balances and writes the adjusted depreciation amounts resulting from the unplanned transaction.
• FA_BOOK_CONTROLS — Stores book-level configuration such as the depreciation calendar, accounting rules, and current open period. Used to validate that the transaction targets a valid, open book and period.
• FA_DEPRN_RULE_DETAILS — Contains the depreciation rule definition, including rate and life details. Consulted to determine the correct depreciation treatment for the asset.
• FA_METHODS — Defines depreciation methods and their calculation logic. Read to identify the method in effect so the unplanned amount is computed consistently.
• FA_TRANSACTION_HEADERS_S — The transaction header table that records asset transactions. The unplanned depreciation is associated with a transaction identifier created or updated here.
• DUAL — Used for single-row arithmetic and validation queries internal to the PL/SQL logic.

Usage Notes

FA_UNPLANNED_PVT is not a public API and is not designed to be called directly by forms, concurrent programs, or custom extensions. Custom code should instead invoke the supported public Fixed Assets APIs, which internally invoke DO_UNPLANNED as part of their processing. In the standard application, unplanned depreciation processing is reached through the Assets transaction and depreciation workflows rather than through a dedicated form that calls this package. Because the package is declared AUTHID CURRENT_USER and is classified as a private helper, any direct call from custom code carries risk: the interface is undocumented, subject to change between releases, and assumes the caller has already populated the full set of record-type parameters correctly. The metadata indicates a single referencing package, reinforcing that DO_UNPLANNED is an internal implementation detail. In both 12.1.1 and 12.2.2, the package structure and exposure remain consistent with the 120.3 header version, and the referenced tables are the standard Fixed Assets depreciation and transaction entities.