Search Results get_lock_info

Overview

EGO_METADATA_BULKLOAD_PVT is a private (PVT) PL/SQL package in the APPS schema that supports the bulk loading of metadata into Oracle E-Business Suite. Its primary business function is to orchestrate the import of metadata definitions — specifically flex value sets and item catalog categories — from interface tables into the base EGO tables, while providing a controlled concurrency mechanism so that multiple concurrent load processes do not corrupt shared metadata. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer, which is consistent with its role as an internal worker unit invoked by higher-level public APIs and concurrent programs.

The package maintains global state to support WHO-column auditing (request ID, program application ID, program ID, user name, user ID, and login ID) and defines a set of lock-related constants that map logical entities to their interface table representations. These constants include EGO_VALUE_SET, EGO_ITEM_CATALOG_CATEGORY, VS_VERSION, ICC_VERSIONS, EGO_FLEX_VALUE_SET_INTF, and EGO_ICC_VERS_INTERFACE. Together they establish the naming convention the lock procedures use to identify and serialize access to each metadata entity type.

Key Procedures and Functions

• GET_LOCK_INFO — Retrieves lock information for a metadata object, allowing callers to determine whether an object is currently locked and by whom before attempting a load or update. This is the procedure most directly associated with the user's search term.
• LOCK_UNLOCK_OBJECT — Acquires or releases a lock on a specified metadata object. It works in conjunction with GET_LOCK_INFO to enforce serialized access to value sets and item catalog categories during bulk load operations.
• IMPORT_METADATA — Performs the core import of metadata records from the interface tables into the corresponding base tables, using the lock infrastructure to guard against concurrent modification.
• WRITE_DEBUG — Writes diagnostic trace messages, governed by the INV_DEBUG_TRACE profile option (user-facing name INV: Debug Trace), where a value of 1 enables tracing and 0 disables it. The header comments note this is preferred over MRP_DEBUG used elsewhere.
• GET_PARTY_NAME — Resolves a party name, typically from HZ_PARTIES, for use in metadata records that reference trading partners or party-based entities.

Tables Accessed

• EGO_OBJECT_LOCK / EGO_OBJECT_LOCK_S — The lock registry and its sequence. GET_LOCK_INFO and LOCK_UNLOCK_OBJECT read and write these tables to record which metadata objects are locked, by which user, and when.
• FND_USER — Supplies user name and user ID values used to populate WHO columns and to attribute lock ownership.
• HZ_PARTIES — Read by GET_PARTY_NAME to resolve party names referenced in metadata.
• PLITBLM — A standard EBS PL/SQL index-by table used for bulk operations, supporting the metadata import processing.

Usage Notes

As a PVT package, EGO_METADATA_BULKLOAD_PVT is not intended for direct invocation by end users or forms. It is referenced by six other packages, which are the public entry points that submit concurrent requests or call the private procedures on the caller's behalf. Typical invocation occurs through metadata bulk-load concurrent programs and from public EGO APIs that need to serialize metadata changes. GET_LOCK_INFO is commonly used in guard logic — callers query lock state before proceeding with an import, then call LOCK_UNLOCK_OBJECT to claim or release the object. Because the package relies on global variables for WHO context, the invoking concurrent program must initialize these values (request ID, program ID, and user identifiers) before calling the load procedures. The debug output controlled by INV_DEBUG_TRACE is written via WRITE_DEBUG and should be enabled only during troubleshooting, as it generates significant trace volume in production environments.