Search Results po_uom_sv2




Overview
Explore in AI Chat

Overview

PO_UOM_SV2 is a server-side PL/SQL package in the Oracle E-Business Suite Applications schema (APPS) that provides unit of measure (UOM) conversion services for inventory-sourced purchasing and requisition transactions. The package carries an AUTHID CURRENT_USER declaration, meaning its SQL statements execute with the privileges of the calling user rather than the definer, which is consistent with its role as a shared utility invoked from forms and other server-side components. Its header identifies it as part of the RCVTXUOS library, and the source history shows an original creation date in 1995 with a revision in 2003, making it a long-standing component of the procurement and receiving stack. The package addresses a recurring requirement in Oracle Purchasing: when a requisition or purchase order line is sourced from inventory, the unit of measure on the transaction may differ from the item's primary UOM in the source organization. Converting quantities and costs between these units correctly is essential for accurate pricing, inventory valuation, and downstream receipt processing. PO_UOM_SV2 encapsulates that logic so that client-side and server-side callers do not each have to reimplement conversion and rounding rules.

Key Procedures and Functions

The documented program units in the package number three, covering the function names NAMES and NAME along with the principal conversion routines exposed in the source excerpt. The two central routines are convert_quantity and convert_inv_cost:

  • convert_quantity — Described in the package header as the server-side component of the client-side round_line_quantity function. It handles unit of issue conversion for inventory-sourced requisition lines. The function returns a BOOLEAN indicating whether the conversion should proceed: TRUE if the calling function should continue with the conversion, and FALSE if conversion is not required or not possible. It accepts the item identifier, source organization, order quantity, and order UOM as inputs and returns the converted quantity through an OUT parameter.
  • convert_inv_cost — Applies when the current UOM differs from the primary UOM for an inventory-sourced line. It rounds the inventory cost based on the primary UOM in the source organization, using the item's UOM conversion between the current and primary units. It returns a BOOLEAN and passes the resulting price back through an OUT NOCOPY parameter, which avoids a copy of the value on return for performance.
  • NAMES / NAME — Documented as additional program units within the package, typically utility or lookup functions supporting the conversion logic.

Tables Accessed

The package reads from several core Purchasing and Inventory tables through APPS synonyms:

  • MTL_SYSTEM_ITEMS — Supplies item attributes, including the primary unit of measure and item-level conversion information used to translate between the order UOM and the inventory UOM.
  • MTL_UNITS_OF_MEASURE — Provides UOM definitions and conversion relationships required to compute converted quantities and costs.
  • PO_REQUISITIONS_INTERFACE — Supports processing of requisition interface records where inventory-sourced lines require quantity conversion before import.
  • PO_SYSTEM_PARAMETERS — Supplies purchasing configuration settings that govern how conversions and rounding are applied.

Usage Notes

PO_UOM_SV2 is typically invoked from Oracle Purchasing and iProcurement forms during requisition and purchase order entry, and from concurrent or interface programs that load requisition data through PO_REQUISITIONS_INTERFACE. Because convert_quantity and convert_inv_cost return BOOLEAN values, callers are expected to test the return status and only apply the OUT parameter values when TRUE is returned; a FALSE result signals that conversion is unnecessary or cannot be performed for the given item and organization combination. The package is referenced by four other packages within the E-Business Suite, confirming its role as a shared dependency rather than a standalone entry point. In Oracle EBS 12.1.1 and 12.2.2, customizations that manipulate inventory-sourced requisition quantities or costs should call these routines rather than performing manual UOM arithmetic, ensuring that rounding behavior remains consistent with standard Purchasing functionality. The AUTHID CURRENT_USER declaration also means that invoking sessions must have appropriate privileges on the underlying MTL and PO tables.