Search Results oe_line_util




Overview
Explore in AI Chat

Overview

OE_DUAL_UOM_HOOK is an APPS-owned PL/SQL package classified under the OTHER API category. Its name and dependency footprint identify it as a secondary hook package within the Oracle Order Management (ONT) dual unit of measure framework. Oracle EBS supports order lines that carry two distinct units of measure: a pricing UOM, used to express the selling price of an item, and a fulfillment (base) UOM, used to drive shipping, reservation, and inventory transactions. In release 12.1.1 and 12.2.2, this dual UOM architecture is implemented in the OE_ORDER_PUB API and its supporting utilities, and OE_DUAL_UOM_HOOK provides the plug-in style abstraction that determines which of the two UOM values applies in a given context.

The package is a hook rather than a full business API. It exposes a small, well-defined surface that the core dual UOM utilities call at runtime, allowing the resolution of UOM semantics to remain centralized and overridable without changing the primary order entry logic. It is declared VALID in the ETRM documentation, confirming it is compiled and active in the standard APPS schema.

Key Procedures and Functions

Two documented program units are exposed by the package:

  • GET_FULFILLMENT_BASE — Resolves and returns the fulfillment base unit of measure associated with an order line context. It supports the fulfillment side of the dual UOM model, where quantity, shipping, and inventory movements must be expressed in the base UOM regardless of the pricing UOM used on the order line.
  • GET_PRICING_UOM — Resolves and returns the pricing unit of measure for the same context. This is the UOM in which list prices, adjustments, and order line selling prices are maintained.

Both functions are deterministic lookup helpers rather than transaction processors; they do not create, update, or validate order data directly. Their purpose is to supply the correct UOM to the calling utility so that downstream calculations remain consistent.

Tables Accessed

The only documented table reference is OE_ORDER_LINES_ALL, accessed through the standard APPS synonyms. That table is the primary store of order line attributes, including the pricing and fulfillment UOM columns, quantities, and item references. The package reads this table to derive the appropriate UOM values for the line being processed. No documented write operations to OE_ORDER_LINES_ALL are attributed to this package, which reinforces its role as a read-oriented resolution layer.

Usage Notes

OE_DUAL_UOM_HOOK is an internal dependency rather than an end-user entry point. It is referenced by OE_DUAL_UOM_HOOK's own body and by OE_DUAL_UOM_UTIL and OE_LINE_UTIL, and it references OE_ORDER_PUB and Oracle STANDARD utilities. This makes it an active participant in the OE_LINE_UTIL processing chain — the exact utility path targeted by searches for oe_line_util.

  • Invocation: Called implicitly by OE_LINE_UTIL and OE_DUAL_UOM_UTIL during order line creation, update, and validation. It is not invoked directly by users.
  • Forms and concurrent programs: Operations triggered via the Sales Orders form or Order Import concurrent program reach the package indirectly through the public OE_ORDER_PUB API and the line utility layer.
  • Custom code: Customers extending dual UOM behavior should treat GET_FULFILLMENT_BASE and GET_PRICING_UOM as the sanctioned seam for customization, but should avoid modifying the seeded APPS package. Customizations must preserve the SIGNATURE and return semantics expected by OE_LINE_UTIL, as the utility layer depends on consistent UOM resolution for correct pricing and fulfillment processing.
  • Diagnostics: Because the package is a leaf dependency of OE_LINE_UTIL, compilation errors or invalid status in OE_DUAL_UOM_HOOK will cascade failures into order line processing, making it a routine target during order entry troubleshooting.