Search Results get_onhand_quant

Overview

APPS.EAM_COMMON_UTILITIES_PVT is a private (PVT) PL/SQL package within the Oracle Enterprise Asset Management (EAM) module, declared with AUTHID CURRENT_USER. It functions as the internal shared-services layer for EAM, centralizing the common validation, lookup, and derivation logic that both EAM public APIs and internal module code depend upon. It is not intended to be a supported public interface; it consolidates reusable technical utilities so that EAM maintenance work orders, asset definitions, meter management, and departmental setup processing do not each re-implement identical lookups against inventory, Bills of Material, Enterprise Asset Management, and HR reference data.

The package header identifies an internal EAM utility layer carrying the standard Oracle API conventions: p_api_version, p_init_msg_list, p_commit, p_validation_level as standard IN parameters, and x_return_status, x_msg_count, and x_msg_data as standard OUT parameters. In EBS 12.1.1 and 12.2.2 the source file is versioned as EAMPUTLS.pls (120.14.12020000.3), and the package is referenced by 25 other EAM packages, confirming its role as a low-level dependency of the EAM call stack. Users searching for get_parent_asset reach this object because parent-asset and maintained-object hierarchy resolution is among the utility behaviors performed through the maintained-object and work-order relationship validations implemented here.

Key Procedures and Functions

ETRM documents 44 procedures and functions in the header, including the following named entries:

• GET_ORG_CODE — Returns the organization code for a supplied organization identifier, converting an internal numeric ID into the human-readable inventory organization code used by EAM forms and reports.
• GET_ITEM_ID and GET_ITEM_NAME — Bidirectional item resolution, translating between inventory item identifiers and concatenated item names for downstream EAM processing.
• INVALID_ITEM_NAME — Helper that reports or formats an invalid item name condition as part of item validation failure handling.
• GET_CURRENT_PERIOD — Derives the current accounting period, used to date-stamp EAM transactions and work-order activity.
• GET_CURRENCY — Returns the functional currency context required by EAM costing and asset value logic.
• GET_NEXT_ASSET_NUMBER — Generates the next asset number using the EAM numbering configuration, supporting automated asset definition.
• VERIFY_ORG — Confirms that an organization is a valid EAM-enabled maintenance organization before any EAM operation proceeds.
• GET_MFG_MEANING — Resolves a manufacturing lookup code to its display meaning for UI and message presentation.
• VALIDATE_* family — VALIDATE_INVENTORY_ITEM_ID, VALIDATE_SERIAL_NUMBER, VALIDATE_BOOLEAN_FLAG, VALIDATE_DEPARTMENT_ID, VALIDATE_EAM_LOCATION_ID, VALIDATE_EAM_LOCATION_ID_ASSET, VALIDATE_WIP_ACCT_CLASS_CODE, VALIDATE_METER_ID, VALIDATE_DESC_FLEX_FIELD, VALIDATE_MFG_LOOKUP_CODE, and VALIDATE_MAINTAINED_OBJECT_ID. Each validates a specific EAM attribute against its owning entity, location, asset, meter, or descriptive flexfield definition, returning standard FND_API status codes.

Tables Accessed

The documented tables are reached through APPS synonyms and fall into functional clusters:

• Organization and department setup: HR_ORGANIZATION_INFORMATION, EAM_ORG_MAINT_DEFAULTS, BOM_DEPARTMENTS, BOM_DEPT_RES_INSTANCES — used for organization verification, department validation, and maintenance defaults.
• Resources and labor: BOM_RESOURCES, BOM_RESOURCE_EMPLOYEES, FND_USER — used to validate resource and employee references.
• Assets, meters, and hierarchy: CSI_ITEM_INSTANCES, CSI_COUNTERS_B, CSI_COUNTER_TEMPLATE_B, EAM_WO_RELATIONSHIPS, EAM_LINEAR_LOCATIONS, MTL_EAM_LOCATIONS — the transactional core for asset instance, meter, work-order relationship, and linear location resolution, including maintained-object and parent-asset hierarchy checks.
• Incidents and period/currency context: CS_INCIDENTS_ALL_B, GL_PERIODS — support incident linkage and current accounting period/currency derivation.

Usage Notes

Because the API classification is PVT, EAM_COMMON_UTILITIES_PVT is not a supported integration surface. It is invoked directly by EAM public APIs, EAM forms, and concurrent programs (work order, asset definition, meter, and department setup flows), which call its validation routines before committing data. Oracle E-Business Suite users and developers should call the corresponding public EAM APIs rather than referencing this package; custom code that does call it must treat every signature as subject to change in patches and upgrades, including EBS 12.1.1 to 12.2.2 upgrades. When parent-asset hierarchy behavior must be customized or diagnosed, the recommended approach is to trace the public EAM API that invokes these utilities instead of modifying the private package logic.