Search Results order_line_uom_code

Overview

APPS.WIP_RESERVATIONS_V is a seeded Oracle E-Business Suite view that exposes material reservation detail for Work in Process (WIP) demand. It is owned by the APPS schema and carries the FND Design Data reference WIP.WIP_RESERVATIONS_V, indicating it is delivered as part of the Discrete Manufacturing/WIP product family and registered within the Application Object Library. The view has a VALID status in both 12.1.1 and 12.2.2 and is defined internally as an Oracle internal-use-only object.

The view presents one row per reservation record, joining reservation attributes to the associated WIP entity, demand source, item, and unit-of-measure conversion data. Because it surfaces reservation quantities expressed in multiple UOM contexts, it is a convenient reporting entry point for questions such as the one that prompted the search for reserved_line_uom_quantity. As with other internal Oracle Application views, Oracle does not support direct customer access except from standard Oracle Applications programs; customers query it at their own risk and should treat it as read-only.

Underlying Base Objects

The documented 12.2.2 metadata identifies the referenced base objects as INV_CONVERT (PACKAGE), MTL_RESERVATIONS (SYNONYM), MTL_SALES_ORDERS (SYNONYM), and OE_ORDER_LINES_ALL (SYNONYM). The core reservation data originates in MTL_RESERVATIONS, which stores reservation_id, organization_id, inventory_item_id, subinventory, locator, lot, serial, and demand source references. MTL_SALES_ORDERS and OE_ORDER_LINES_ALL supply sales-order demand context, including the order number and line information exposed through the SEGMENT1/SEGMENT2/SEGMENT3 and DEMAND_SOURCE_LINE_NUMBER columns. INV_CONVERT is the standard inventory conversion package used to derive alternate-UOM quantities from the primary reservation quantity, which is how columns such as RESERVATION_QUANTITY and RESERVED_LINE_UOM_QUANTITY are populated relative to PRIMARY_QUANTITY and PRIMARY_UOM_CODE. The WIP_ENTITY_ID column links each reservation row to the discrete job or repetitive schedule that created the demand.

Key Columns

• RESERVATION_ID — primary identifier of the reservation record in MTL_RESERVATIONS.
• ORGANIZATION_ID — inventory organization owning the reservation.
• DEMAND_SOURCE_NAME / DEMAND_SOURCE_TYPE_ID / DEMAND_SOURCE_HEADER_ID / DEMAND_SOURCE_LINE_ID / DEMAND_SOURCE_LINE_NUMBER — describe the originating demand; for WIP these reference the work order, and for sales orders the order header and line.
• DEMAND_CLASS_CODE — classification of the demand (for example, WIP or sales order).
• SEGMENT1/SEGMENT2/SEGMENT3 — descriptive segments of the demand source (typically order or work order number components).
• REQUIREMENT_DATE — date the reserved material is required by the demand source.
• INVENTORY_ITEM_ID, ITEM_REVISION, SUBINVENTORY_CODE, LOCATOR_ID, LOT_NUMBER, SERIAL_NUMBER — the exact material reserved, down to locator and lot/serial granularity.
• PRIMARY_UOM_CODE / PRIMARY_QUANTITY — reservation quantity in the item's primary unit of measure.
• RESERVATION_UOM_CODE / RESERVATION_QUANTITY — quantity expressed in the reservation UOM.
• ORDER_LINE_UOM_CODE / RESERVED_LINE_UOM_QUANTITY — the quantity reserved expressed in the order-line UOM, which is the column users search for when reconciling reservation totals against order line quantities.
• WIP_ENTITY_ID — the WIP entity (job or schedule) associated with the reservation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard WHO/audit and concurrent program columns.

Common Use Cases and Queries

Typical uses include verifying that reserved quantities match order-line or work-order requirements, reporting reservations by organization, item, or requirement date, and building custom alerts or extracts for shortages. The view is also used to reconcile PRIMARY_QUANTITY against RESERVATION_QUANTITY and RESERVED_LINE_UOM_QUANTITY when UOM conversions are involved.

Sample query listing reservations for a specific organization and item:

• SELECT reservation_id, organization_id, inventory_item_id, demand_source_name, demand_source_line_number, requirement_date, primary_uom_code, primary_quantity, reservation_uom_code, reservation_quantity, order_line_uom_code, reserved_line_uom_quantity, wip_entity_id FROM apps.wip_reservations_v WHERE organization_id = :org_id AND inventory_item_id = :item_id AND demand_class_code = 'WIP' ORDER BY requirement_date;

A second common pattern aggregates reserved quantities per work order:

• SELECT wip_entity_id, SUM(primary_quantity) total_primary_qty, SUM(reserved_line_uom_quantity) total_line_uom_qty FROM apps.wip_reservations_v WHERE organization_id = :org_id GROUP BY wip_entity_id;

Because the view is documented as Oracle internal use only, production reports should preferably use supported APIs or the underlying MTL_RESERVATIONS table where a supported path exists, and queries should always be filtered by ORGANIZATION_ID and key demand columns to control cost.