Search Results do_delete

Overview

APPS.FA_DELETION_PUB is a public PL/SQL API package in Oracle E-Business Suite Fixed Assets (product FA). It exposes a programmatic interface for permanently removing asset records from the system, a function that is otherwise performed through the Fixed Assets asset inquiry and maintenance forms. The package is classified as a Public (PUB) API in the ETRM repository, meaning Oracle documents it as a supported integration point that customers and partners may call from custom code. The header comment identifies the package as the "Delete Asset API," with a scope of public and an active lifecycle, and assigns it to the FA_ASSET business entity. The package source carries the header identifier FAPDELS.pls, version 120.3, dated 2006/06/30, indicating that the interface has been stable across the 11i, 12.1.1, and 12.2.2 release lines. Because asset deletions are destructive and carry accounting and audit implications, the package encapsulates the referential cleanup logic rather than leaving it to the caller, ensuring that dependent asset rows are handled consistently.

Key Procedures and Functions

The package documents a single public program unit:

• DO_DELETE — Deletes an asset from the system. The procedure accepts the standard Oracle API control parameters: an API version, an initialize-message-list flag, a commit flag, a validation level, and the name of the calling function. It returns the standard API outcome parameters (return status, message count, and message data) plus an IN OUT asset header record typed as FA_API_TYPES.asset_hdr_rec_type, through which the asset to be deleted is identified and returned. The p_commit flag determines whether the deletion is committed within the call or left to the caller, and p_validation_level governs the degree of pre-deletion validation applied. Callers must inspect x_return_status and, when x_msg_count exceeds one, retrieve messages via the FND_MSG_PUB message stack.

Tables Accessed

The package reads and writes across the Fixed Assets base and multi-currency table set. Core asset master data is touched in FA_BOOKS, FA_BOOK_CONTROLS, FA_CATEGORIES, FA_ASSET_HISTORY, and FA_DISTRIBUTION_HISTORY. Financial and transactional rows affected by deletion include FA_ADJUSTMENTS, FA_ASSET_INVOICES, FA_CAPITAL_BUDGET, FA_DEPRN_DETAIL, FA_DEPRN_EVENTS, FA_DEPRN_SUMMARY, and FA_ADD_WARRANTIES. Multi-currency counterparts FA_MC_BOOKS, FA_MC_ADJUSTMENTS, and FA_MC_ASSET_INVOICES are also maintained so that reporting in reporting currencies stays consistent with the primary ledger. Access occurs through APPS synonyms; the API is the only supported mechanism for clearing these rows, because direct DML would bypass the depreciation and book control logic maintained by the deletion process.

Usage Notes

FA_DELETION_PUB is invoked from Fixed Assets forms and concurrent programs that perform asset deletion, and it may be called directly from custom PL/SQL, OAF pages, or SOA/Bpel integrations that need to remove assets in bulk or as part of a data cleanup routine. Standard Oracle API conventions apply: initialize the session with FND_GLOBAL.APPS_INITIALIZE, set p_init_msg_list to FND_API.G_TRUE to obtain a fresh message list, and validate x_return_status against FND_API.G_RET_STS_SUCCESS before proceeding. Deletion should be treated as irreversible; the p_commit parameter lets callers group multiple deletions into a single transaction, but partial failure may leave prior calls committed if that flag was set to true on each invocation. Because the package is supported across 12.1.1 and 12.2.2 without signature changes, custom code written against DO_DELETE remains portable between those releases.