Results for “unit_of_measure”

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 in Oracle E-Business Suite that exposes the business logic governing units of measure (UOM), UOM classes, and UOM conversions within the Oracle Inventory (INV) module. Its primary business function is to provide a sanctioned programmatic interface for creating, validating, and maintaining UOM definitions and their associated conversion relationships, ensuring that all unit-of-measure data conforms to the validation rules enforced by the Inventory application. The package is classified as a public API, meaning it is intended for invocation by external callers such as other Oracle modules, forms, concurrent programs, and custom extensions, rather than being reserved for internal use. This makes it a stable integration point for applications that must manipulate UOM data consistently with the seeded and user-defined records held in the Inventory tables.

Key Procedures and Functions

The package declares three documented public procedures and functions. Each encapsulates a distinct area of UOM maintenance.

• UOM_CLASS — Manages UOM class data. A related private helper, Uom_class_exists, checks whether a given UOM class already exists for the current language by querying the mtl_uom_classes_tl table and returning a Boolean result. This supports validation before creation and prevents duplicate class definitions.
• UNIT_OF_MEASURE — Handles the creation and maintenance of individual units of measure, including their association with a parent UOM class. This is the core entry point for defining new UOM records.
• UOM_CONVERSION — Manages conversion relationships between units of measure, allowing the system to translate quantities expressed in one UOM into another. This is essential for transactional accuracy across purchasing, receiving, inventory, and manufacturing.

A private procedure, validate_attr_info, validates descriptive flexfield attributes, checking whether attributes are enabled or required in the context of the UOM descriptive flexfield. This procedure supports the flexfield-driven extensibility of UOM records without exposing it as a public entry point.

Tables Accessed

The package interacts with a broad set of Inventory and Process Manufacturing tables through APPS synonyms. The UOM class and conversion logic relies on MTL_LOT_UOM_CLASS_CONVERSIONS, MTL_CONVERSION_ID_S, and MTL_LOT_CONV_AUDIT_DETAILS, which store class-level conversion definitions and their audit trail. Item and transaction context is drawn from MTL_SYSTEM_ITEMS_B, MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_TRANSACTION_LOT_NUMBERS, MTL_TRANSACTION_LOTS_TEMP, MTL_LOT_NUMBERS, and MTL_RESERVATIONS. System-level configuration is read from MTL_PARAMETERS. Process Manufacturing integration is provided through GME_BATCH_HEADER, GME_MATERIAL_DETAILS, and GME_TRANSACTION_PAIRS. The FND_DUAL table supports dual-table queries, and the package references FND_PROFILE.VALUE('INV_DEBUG_TRACE') to control debug tracing.

Usage Notes

INV_UOM_API_PUB is typically invoked from Oracle Inventory forms, concurrent programs that load or migrate UOM and conversion data, and custom PL/SQL code that must establish UOM definitions before processing transactions. Callers should invoke the public procedures rather than inserting directly into the underlying MTL tables, so that flexfield validation and conversion integrity rules are applied. The package is not referenced by any other documented package (0 references), indicating it is a leaf-level API consumed directly by client code. Debug output can be enabled by setting the INV_DEBUG_TRACE profile option, which is useful when diagnosing validation failures during UOM setup or conversion loading.