Results for “eam_asset_operation_txn_pvt”

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

Overview

EAM_ASSET_OPERATION_TXN_PVT is the private (PVT) implementation package for asset operation transaction processing within Oracle Enterprise Asset Management (EAM). It sits beneath the public wrapper package EAM_ASSET_OPERATION_TXN_PUB and carries the actual business logic that creates, validates, and persists asset operation transactions such as check-in and check-out events, meter readings, and quality plan associations recorded against asset instances.

The private/public pairing follows the standard Oracle EBS PL/SQL API architecture. The _PUB package exposes a stable, documented interface to external callers, while the _PVT package holds the internal procedures that perform data validation, derive default values, and execute DML against the EAM and quality tables. Because it is a private package, it is not intended to be called directly by customer extensions; it is invoked through the public API, typically during asset operation data entry in the Oracle EAM forms or through automated integrations.

Key Procedures and Functions

• GET_CREATED_BY — Retrieves the creating user identifier used to stamp audit columns on newly inserted transaction records, generally resolving the value from the FND_USER context of the calling session.
• INSERT_TXN — Performs the core insert of an asset operation transaction row into the EAM_ASSET_OPERATION_TXN table, assigning the surrogate key from the EAM_ASSET_OPERATION_TXN_S sequence and populating standard WHO columns.
• VALIDATE_TXN — Applies the business validation rules for an incoming transaction, verifying that the referenced asset instance, item, and organizational context are consistent before any data is written.
• PROCESS_CHECKINOUT_TXN — Handles the check-in and check-out transaction flow for an asset, recording the movement event and updating the associated asset instance state.
• INSERT_QUALITY_PLANS — Associates quality plans with the operation transaction, writing the relevant rows into the quality collection and plan tables so that inspection results can be captured against the asset activity.
• INSERT_METER_READINGS — Writes meter reading values supplied with the asset operation transaction, supporting usage-based maintenance and preventive maintenance scheduling.

Tables Accessed

• EAM_ASSET_OPERATION_TXN / EAM_ASSET_OPERATION_TXN_S — The primary transaction table and its surrogate key sequence, holding the recorded asset operation events.
• CSI_ITEM_INSTANCES — Provides the asset instance definition against which the operation transaction is recorded.
• MTL_SYSTEM_ITEMS_KFV and MTL_PARAMETERS — Supply item and inventory organization context and validation.
• QA_PLANS, QA_COLLECTION_ID_S, QA_RESULTS — Support quality plan association and collection identifier generation for inspection data.
• FND_USER — Resolves the application user for creation and update audit information.
• DUAL and PLITBLM — Used for scalar lookups and PL/SQL table manipulation within the package logic.

Usage Notes

EAM_ASSET_OPERATION_TXN_PVT is invoked indirectly through EAM_ASSET_OPERATION_TXN_PUB, which is the supported entry point for external callers. In standard EBS usage the package is driven by the Oracle EAM asset operation forms when users record check-in/check-out activity, enter meter readings, or attach quality plans to an asset transaction. It may also be invoked from concurrent programs or custom PL/SQL integrations that process asset operation data in bulk, provided they call the public API rather than the private package.

Both Oracle E-Business Suite 12.1.1 and 12.2.2 ship this package in the APPS schema with a VALID status. The package is referenced by two other packages, confirming its role as a shared internal component. Developers extending EAM should treat the package as internal infrastructure and rely on the public wrapper for all supported integration points.