Search Results post_transfer




Overview
Explore in AI Chat

Overview

IA_POST_REQUEST_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Assets Mass Additions and asset transfer processing flow. In ETRM 12.2.2 it is classified as an "OTHER" API, meaning it is not a published open interface but an internal helper package invoked by Oracle Assets forms and concurrent programs. Its core responsibility is to post asset transfer requests — records captured in the IA_REQUEST_HEADERS and IA_REQUEST_DETAILS tables — into the Oracle Assets depreciation and distribution structures, updating FA_ADDITIONS, FA_BOOK_CONTROLS, FA_DEPRN_PERIODS, and FA_DISTRIBUTION_HISTORY accordingly. In effect, the package converts a staged transfer request into an actual change of asset assignment, location, and depreciation distribution across books and periods. It is a dependent object of the SYS STANDARD package and is referenced only within APPS, consistent with its internal-facing role.

Key Procedures and Functions

The ETRM metadata documents a single entry point:

  • POST_TRANSFER — performs the posting of an asset transfer request. It validates the request identified by the caller, applies the transfer to the asset record, and propagates the resulting distribution changes to the affected depreciation books and open periods. The procedure is the mechanism by which a staged IA request becomes a committed change in Oracle Assets; no additional parameters are documented in the ETRM extract, so callers should rely on the packaged signature in the 12.1.1 / 12.2.2 source rather than assuming a public specification.

Because only one procedure is documented, the package should be treated narrowly: it is not a general-purpose transfer API, and the full parameter list must be confirmed against the deployed package specification in the target instance before any custom invocation.

Tables Accessed

The documented table references, all resolved through APPS synonyms, reflect the package's posting logic:

  • IA_REQUEST_HEADERS and IA_REQUEST_DETAILS — the staged transfer request and its line-level detail, read to determine what to post and updated to reflect posting status.
  • FA_ADDITIONS — the asset master record, updated with the new assignment, location, or employee information resulting from the transfer.
  • FA_BOOK_CONTROLS — depreciation book definition and control data, consulted to identify the books affected by the transfer.
  • FA_DEPRN_PERIODS — open and closed period status per book, used to determine the earliest period into which the transfer can be posted and to drive period-opening logic.
  • FA_DISTRIBUTION_HISTORY — the depreciation distribution rows, where new effective distribution records are inserted or existing ones end-dated.
  • PLITBLM — the standard Oracle Applications PL/SQL table of VARCHAR2 used for in-memory list processing during the posting routine.

Usage Notes

IA_POST_REQUEST_PKG is typically invoked indirectly rather than called directly by end users. In a standard EBS 12.1.1 or 12.2.2 environment it is reached from the Oracle Assets transfer request forms and from the concurrent programs that process staged IA requests, most notably during the posting step that follows entry and validation of an asset transfer. It is appropriate for custom code to call POST_TRANSFER only when the same staging tables and validation rules are respected, since bypassing the normal form or concurrent flow can leave IA_REQUEST_HEADERS and IA_REQUEST_DETAILS in an inconsistent status relative to the FA tables. Because the package is referenced by no other packaged APIs, there is no documented downstream contract to preserve beyond the FA base tables it writes. Any extension should be limited to read-only inspection of the IA request tables, with posting performed through the standard Oracle Assets process to ensure period status, book controls, and distribution history remain synchronized.