Search Results lock_item




Overview

APPS.EAM_ITEM_PVT is a private (PVT) PL/SQL package body within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Its principal business function is to encapsulate the item-definition logic that EAM requires when creating and maintaining asset items in the inventory item master. EAM asset items are distinct from standard inventory items in that they carry asset-group attributes, EAM item type classification, and serial-number generation rules. The package provides a programmatic, API-driven interface for these operations, shielding callers from the underlying Inventory item-definition APIs and the structure of the item master tables. The package header declares G_PKG_NAME as a constant and the body opens with the standard ETRM/API error-handling variables (x_return_status, x_msg_count, x_msg_data) consistent with the Oracle Application Object Library API error stack convention. The header comment ($Header: EAMPITMB.pls 120.7 2006/06/13) confirms the file has been maintained under the standard EBS source-control naming convention.

Key Procedures and Functions

The documented package exposes three procedures:

  • INSERT_ITEM — Creates a new EAM asset item. It accepts the descriptive key flexfield segments (p_segment1 through p_segment20), asset-group and organization context (p_asset_group, p_organization_id), template and source-template identifiers (p_source_tmpl_id, p_template_name), serialization controls (p_serial_generation, p_prefix_text, p_prefix_number), EAM item type, and a commit flag, returning the generated inventory item identifier through x_item_id and the standard API status variables.
  • UPDATE_ITEM — Modifies an existing EAM asset item, applying the same API error-handling contract to propagate validation and processing messages back to the caller.
  • LOCK_ITEM — Acquires the item-level lock required before an EAM item can be safely updated or processed. This is the procedure associated with the search term "lock_item" and is invoked to serialize concurrent modifications to an item record, preventing conflicting writes during item maintenance.

All three follow the EBS private-API pattern: a p_commit parameter defaulting to FND_API.G_FALSE, NOCOPY OUT parameters for return status, message count, and message data, and internal logging gated by FND_LOG runtime levels (unexpected, procedure, statement).

Tables Accessed

  • MTL_PARAMETERS — Read to resolve inventory organization parameters, in particular the master organization and item-definition defaults required when creating or updating an item in a given organization.
  • PLITBLM — The item master interface/parameter table used in conjunction with the Inventory item-definition API to stage and validate item attribute values during INSERT_ITEM and UPDATE_ITEM.

The package interoperates with the Inventory item group record type INV_Item_GRP.Item_Rec_Type (referenced as l_asset_group and l_x_curr_item_rec), which is the canonical structure used by the Inventory item APIs to carry item attribute data.

Usage Notes

EAM_ITEM_PVT is a private package and is not intended for direct invocation by end users or external integrations. It is typically called from EAM forms and concurrent programs that manage asset items, and from other EAM packages (such as EAM_ITEM_PUB or item-definition wrappers) that delegate to it. Custom code should invoke the corresponding public API rather than calling this private package directly, but where direct use is required, the caller must supply a valid organization context, populate the segment and asset-group inputs, initialize the standard FND_API error variables, check x_return_status after every call, and honor the p_commit flag by performing an explicit commit only when the procedure returns success. Because INSERT_ITEM and UPDATE_ITEM rely on template and organization metadata, the relevant EAM and Inventory setup must be complete before the procedures are invoked; LOCK_ITEM should be called to establish the item lock prior to any update path.