Results for “eam_asset_number_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.EAM_ASSET_NUMBER_PVT is a private PL/SQL package within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite. Its purpose is to provide the internal validation and persistence logic required to create, update, and interrogate asset number records associated with Enterprise Asset Management installations. In EAM, an "asset" is the tracked instance of a maintainable item that is installed at a location and for which maintenance activities, cost rollups, and financial linkage to Oracle Assets are maintained. This package encapsulates the low-level insert, update, and locking routines plus the higher-level business operations—asset creation, asset update, serial number validation, and asset search—that the public EAM asset APIs and the EAM asset workbench depend upon.

The package is classified as PVT (private) in the ETRM metadata, meaning it is not intended to be called directly by customer extensions. It is an implementation detail invoked by other, public-facing packages and by the EAM application forms and concurrent processes. The header comment confirms an API version parameter, standard FND_API message list and commit flags, and a full validation level default, indicating conformance to the Oracle Application Object Library (AOL) API design standards.

Key Procedures and Functions

The ETRM metadata documents seven procedures within this package:

• INSERT_ROW — Performs the physical insert of a new asset number record into the underlying EAM asset table, populating the audit columns (creation date, created by, last update date, last updated by, last update login, request ID, and program identifiers) passed by the caller.
• UPDATE_ROW — Applies modifications to an existing asset number record, again maintaining the standard audit and concurrency columns.
• LOCK_ROW — Obtains a row-level lock on the target asset number record so that concurrent sessions cannot modify it during an update transaction.
• CREATE_ASSET — The primary creation operation. It validates the supplied item, serial number, organization, location, and category combination, then invokes the insert logic and any dependent processing required to register a new EAM asset.
• UPDATE_ASSET — The primary modification operation. It validates and applies changes to an existing asset, including attributes, financial asset linkage, criticality, and maintainability flags.
• SERIAL_CHECK — Validates the serial number associated with the asset against the serial number control setup for the item and organization, ensuring that the asset is not duplicated and that the serial exists where required.
• FIND_ASSETS — Provides a search/query capability that returns asset records matching the supplied criteria, used by the asset workbench and related inquiry screens.

No individual parameter lists are reproduced here, consistent with the documented source header.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• CSI_ITEM_INSTANCES and CSI_INSTALL_PARAMETERS — Installed base instance records and their associated installation parameters, which form the foundation of an EAM asset instance.
• CSI_I_ASSETS — The interface/association table linking installed base instances to asset representations.
• EAM_ASSET_RESULTS_GTT — A global temporary table used to stage validation or processing results during asset creation and update.
• EAM_ORG_MAINT_DEFAULTS — Organization-level maintenance defaults that govern asset numbering and maintenance behavior.
• MTL_SYSTEM_ITEMS, MTL_SERIAL_NUMBERS, and MTL_PARAMETERS — Inventory item definitions, serial number records, and organization parameters used to validate the item and serial combination.
• MTL_EAM_ASSET_ACTIVITIES and MTL_OBJECT_GENEALOGY — Asset activity and object genealogy records that track the asset's maintenance history and parent-child relationships.
• FA_ADDITIONS, FA_BOOKS, FA_BOOK_CONTROLS, and FA_DISTRIBUTION_HISTORY — Oracle Assets tables used when an EAM asset is linked to a fixed asset, including book controls and distribution history.

Usage Notes

Because EAM_ASSET_NUMBER_PVT is a private package, it is not a supported integration point. It is invoked internally by the public EAM asset APIs and by the Oracle EAM asset workbench forms when users manually create or modify assets. Concurrent programs that mass-create or update assets—and any internal EAM processes that perform serial number validation—also call into these routines. The metadata records that two other packages reference this package, confirming its role as a building block rather than an entry point.

Developers extending EAM should call the public asset APIs rather than EAM_ASSET_NUMBER_PVT directly, since the private package's signature may change between releases. The header and metadata reflect the 12.1.1 and 12.2.2 code lines; the package references only APPS synonyms and does not expose customer-callable interfaces. Any custom code that must manipulate asset numbers should route through the supported public API layer to preserve validation, audit, and concurrency behavior.