Search Results eam_asset_move_util




Overview
Explore in AI Chat

Overview

APPS.EAM_ASSET_MOVE_PUB is a public PL/SQL API package within the Oracle Enterprise Asset Management (eAM) module of Oracle E-Business Suite. Its principal business function is to manage the movement of assets between organizations, subinventories, and locators, including the transfer of serialized and non-serialized eAM assets. The package acts as the programmatic entry point for asset move transactions, allowing both standard eAM functionality and custom extensions to stage, validate, and process asset relocation requests in a controlled and auditable manner. In releases 12.1.1 and 12.2.2 the object is documented as VALID in the APPS schema, with an API classification of PUB, indicating that it is intended for supported external invocation by forms, concurrent programs, and custom code.

The package encapsulates the business logic required to prepare an asset move, build the asset hierarchy, populate a temporary staging structure, and ultimately push transactions into the Oracle Inventory transaction interface for processing. This design pattern keeps the complex validation and setup logic separate from the underlying Inventory transaction engine.

Key Procedures and Functions

ETRM documents nine procedures and functions in this package. PREPAREMOVEASSET performs the initial setup and validation required before an asset move can proceed. GETASSETHIERARCHY retrieves the parent-child structure of assets, which is essential when moves affect components or nested asset relationships. POPULATETEMP loads the temporary work structure used to stage move data prior to processing. ADDASSETSTOINTERFACE inserts the prepared asset move records into the transaction interface for subsequent processing.

PROCESSASSETMOVETXN drives the actual processing of the staged asset move transaction. GET_LOCATORCONTROL_CODE returns the locator control setting, which governs whether locators must be specified for the affected inventory organizations. DYNAMIC_ENTRY_NOT_ALLOWED is a validation routine that enforces restrictions on dynamic entry of data. ADDASSETSFORMISCRECEIPT and ADDASSETSFORMISCISSUE handle the specialized cases of adding assets as part of miscellaneous receipt and miscellaneous issue transactions respectively. Together these procedures cover the complete lifecycle of an asset move, from preparation through interface population to final transaction execution.

Tables Accessed

The package references a broad set of Inventory and eAM tables through APPS synonyms. CSI_ITEM_INSTANCES stores the installed base asset instance records, which are central to identifying the assets being moved. EAM_ASSET_MOVE_TEMP provides the temporary staging area for asset move data. MTL_MATERIAL_TRANSACTIONS_S and MTL_TRANSACTIONS_INTERFACE support transaction creation and interface processing. MTL_OBJECT_GENEALOGY captures the asset hierarchy relationships consulted by GETASSETHIERARCHY. MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_INTERFACE handle serialized asset tracking. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B supply item validation and attribute data. MTL_SECONDARY_INVENTORIES and MTL_PARAMETERS provide subinventory and organization-level setup, including locator control. MTL_TRANSACTION_TYPES defines valid transaction types, ORG_ACCT_PERIODS validates open accounting periods, and WIP_EAM_PARAMETERS supplies eAM-specific configuration. DUAL is used for standard single-row queries.

Usage Notes

EAM_ASSET_MOVE_PUB is typically invoked from eAM asset movement forms and concurrent programs that execute asset transfers, as well as from custom PL/SQL code requiring programmatic asset relocation. Developers should invoke the documented public procedures rather than manipulating the underlying tables directly, since the package enforces validation, hierarchy resolution, and interface population logic. Because the package depends on open accounting periods and valid subinventory and locator configuration, callers must ensure that ORG_ACCT_PERIODS and related setups are correct before execution. The package is referenced by EAM_ASSET_MOVE_UTIL, indicating that the utility layer wraps or extends this public API. As with all public APIs, error handling should anticipate validation failures returned from the staging and interface procedures.