Results for “uom_class”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.INV_UOM_API_PUB is a public PL/SQL API package within the Oracle E-Business Suite Inventory (INV) module. Its purpose is to provide a controlled, programmatic interface for maintaining and validating Units of Measure (UOM) definitions and UOM conversions in Oracle EBS Releases 12.1.1 and 12.2.2. Units of measure are foundational reference data in Oracle Inventory: nearly every material transaction, reservation, lot record, and receiving or shipping operation depends on a correctly defined UOM and on valid conversion relationships between a base unit and its alternate units.

The package is classified as a PUBLIC API, meaning it is intended to be called from external code, custom concurrent programs, forms personalizations, and integrations rather than being an internal-only construct. It is owned by the APPS schema and holds a VALID status in the ETRM metadata. The API encapsulates the business rules that govern UOM classes, unit definitions, and conversion factors, allowing callers to avoid writing directly against the underlying Inventory tables and thereby preserving data integrity and auditability.

Key Procedures and Functions

The ETRM documentation identifies three documented procedures and functions within the package. Parameter lists are not enumerated in the metadata and are therefore not restated here; the descriptions below reflect the documented purpose of each entry point.

  • UOM_CLASS — Handles the definition and maintenance of UOM classes. A UOM class groups related units of measure (for example, Quantity, Weight, or Volume) and defines the base unit against which conversions within that class are expressed. This procedure supports the creation and update of class-level UOM data.
  • UNIT_OF_MEASURE — Manages individual unit of measure definitions and their association to a UOM class. This routine governs the attributes of a specific UOM, ensuring it is properly classified and available for use in transactions and conversions.
  • UOM_CONVERSION — Maintains conversion relationships between units of measure. It is the mechanism by which alternate units are related to a base unit, either through direct conversion factors or through the standard UOM conversion logic, enabling accurate quantity translation across the inventory and manufacturing transactions that reference those units.

Tables Accessed

The package interacts with a broad set of Inventory and Process Manufacturing tables accessed through APPS synonyms. Core UOM and item data reside in MTL_SYSTEM_ITEMS_B and MTL_PARAMETERS, which provide the item-level and organizational context for UOM usage. Conversion definitions and lot-level conversion records are held in MTL_LOT_UOM_CLASS_CONVERSIONS and MTL_LOT_NUMBERS, while conversion audit information is captured in MTL_LOT_CONV_AUDIT_DETAILS. The sequence MTL_CONVERSION_ID_S supplies identifiers for conversion records.

Transactional tables such as MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_TRANSACTION_LOTS_TEMP, MTL_TRANSACTION_LOT_NUMBERS, and MTL_RESERVATIONS are referenced to ensure that UOM data remains consistent with in-flight and historical material activity. Process Manufacturing integration is supported through references to GME_BATCH_HEADER, GME_MATERIAL_DETAILS, and GME_TRANSACTION_PAIRS. FND_DUAL serves as the standard Oracle Applications dual table for validation and lookup operations within the PL/SQL logic.

Usage Notes

INV_UOM_API_PUB is typically invoked from Oracle Inventory setup forms, from concurrent programs that load or validate UOM and conversion data, and from custom PL/SQL integrations requiring programmatic UOM maintenance. Because the package is a public API, Oracle recommends calling it rather than inserting or updating the underlying Inventory UOM tables directly, since the API enforces validation rules, sequence usage, and audit conventions. The ETRM metadata records that this package is referenced by zero other packages, indicating it functions as an entry-point API rather than a shared internal dependency. Developers extending Oracle EBS should treat INV_UOM_API_PUB as the supported interface for UOM class, unit, and conversion operations, and should verify behavior against the specific release (12.1.1 or 12.2.2) in use, as underlying table structures and multi-organization behavior may differ between them.