Search Results fa_addition_pub




Overview
Explore in AI Chat

Overview

FA_ADDITION_PUB is a public PL/SQL API package in the APPS schema that governs the creation of asset additions in Oracle E-Business Suite Fixed Assets. In Oracle EBS 12.1.1 and 12.2.2, the package serves as the single supported public entry point for inserting new asset cost transactions into the FA_TRANSACTION_HEADERS_S interface, thereby registering an addition against an existing asset or a newly formed one. It belongs to the PUB API classification layer, meaning its signature and behavior are intended to remain stable for external callers, including Oracle's own product modules and customer extensions.

The package underpins the transactional integrity of asset capitalization. Rather than allowing direct DML against Fixed Assets transaction tables, the API validates the requested addition, applies book-control and period requirements, derives the correct transaction type and source, and writes the transaction header row from which the Fixed Assets posting process later generates journal entries and asset cost balances.

Key Procedures and Functions

The documented public interface exposes a single procedure:

  • DO_ADDITION — The core public routine responsible for creating an asset addition transaction. It accepts the caller's asset identification, book, amount, and context information, performs API-level validation through FND_API and FND_GLOBAL utilities, and inserts the transaction header record necessary to represent the addition. It relies on standard error-handling conventions (return status and message stack) consistent with the FND_API model used across EBS public APIs.

FA_ADDITION_PUB also depends on FA_API_TYPES, which supplies the shared record and table-type definitions used to pass asset addition data between Fixed Assets APIs. No additional documented procedures or functions exist in the ETRM metadata.

Tables Accessed

The documented table references are:

  • FA_BOOK_CONTROLS — Read to obtain book-level setup and control information, such as the accounting period status and depreciation rules, ensuring additions are created only for valid, open books.
  • FA_TRANSACTION_HEADERS_S — The primary write target; the procedure inserts the addition transaction header that the Fixed Assets posting engine processes.
  • DUAL — Used for single-row selection and expression evaluation during validation or defaulting logic.
  • PLITBLM — The standard EBS PL/SQL table-to-integer-table mapping object used internally for message handling and list processing.

Usage Notes

FA_ADDITION_PUB is normally invoked indirectly rather than by end users. It is referenced by ten other APPS packages, including FA_ADJUSTMENT_PVT, FA_CIP_PUB, FA_CREATE_GROUP_ASSET_PKG, FA_MASSADD_PKG, FA_MASSCP_PKG, and FA_TRANS_API_PUB, along with several Oracle Leasing (OKL) private packages such as OKL_ACTIVATE_ASSET_PVT, OKL_AM_LEASE_TRMNT_PVT, OKL_LIKE_KIND_EXCHANGE_PVT, and OKL_SPLIT_ASSET_PVT. This pattern reflects its role as the common addition-creation service consumed by mass additions, CIP capitalization, transfers, lease activation, and asset build functionality.

In practical terms, the procedure is reached through Fixed Assets forms (for example, manual asset additions and mass additions), through concurrent programs that import and post additions, and through custom PL/SQL integrations that need to register an asset addition programmatically. Because it enforces API validation, period control, and consistent transaction header creation, developers should call DO_ADDITION instead of performing direct inserts. Any custom invocation must respect FND_GLOBAL initialization (application, responsibility, and user context) and should check the returned API status before committing.