Search Results reservation_uom_code




Overview
Explore in AI Chat

Overview

WIP_RESERVATIONS_V is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Work in Process (WIP) product and serves a specific, narrow purpose: selecting material reservations that are supplied to WIP Discrete Jobs or WIP Flow Schedules. The view joins reservation records in MTL_RESERVATIONS to the originating sales order demand stored in OE_ORDER_LINES_ALL and MTL_SALES_ORDERS, filtered to sales-order demand classes and WIP supply sources. It therefore exposes the intersection of sales order reservation activity and WIP demand, which is useful for reporting on components reserved against discrete jobs and flow schedules.

Because it is a view rather than a table, it carries no storage of its own and reflects live transactional data. It is typically consumed by reports, custom concurrent programs, and integrations that need to reconcile sales-order-driven reservations against WIP entities.

Underlying Base Objects

The documented base objects referenced by the view are:

  • MTL_RESERVATIONS (SYNONYM) — aliased MR, the primary source of reservation rows, quantities, UOMs, and lot/serial/subinventory detail. The view selects its ROWID and reservation attributes.
  • OE_ORDER_LINES_ALL (SYNONYM) — aliased OOL, joined on DEMAND_SOURCE_LINE_ID = LINE_ID, providing line number, demand class, and the order quantity UOM.
  • MTL_SALES_ORDERS (SYNONYM) — aliased MSO, joined on SALES_ORDER_ID = DEMAND_SOURCE_HEADER_ID, supplying the order number across SEGMENT1, SEGMENT2, and SEGMENT3.
  • INV_CONVERT (PACKAGE) — a PL/SQL package invoked in the SELECT list to convert primary reservation quantities into the order line UOM.

The join predicates restrict DEMAND_SOURCE_TYPE_ID to 2 or 8 (the OE source-type globals) and require SUPPLY_SOURCE_TYPE_ID = 5, the WIP supply source. This combination is what limits the result set to sales-order reservations feeding WIP supply.

Key Columns

The view exposes the reservation identity and demand context through columns such as ROW_ID, RESERVATION_ID, ORGANIZATION_ID, DEMAND_SOURCE_TYPE_ID, DEMAND_SOURCE_NAME, DEMAND_SOURCE_HEADER_ID, and DEMAND_SOURCE_LINE_ID, along with DEMAND_SOURCE_LINE_NUMBER. Sales order identification is delivered via SEGMENT1, SEGMENT2, and SEGMENT3, while DEMAND_CLASS_CODE and REQUIREMENT_DATE describe the demand itself.

Item and stocking detail includes INVENTORY_ITEM_ID, ITEM_REVISION, SUBINVENTORY_CODE, LOCATOR_ID, LOT_NUMBER, and SERIAL_NUMBER. Quantity information spans several UOM representations:

WIP_ENTITY_ID links the reservation to its discrete job or flow schedule. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The RESERVATION_UOM_CODE column is directly relevant to queries that compare reserved quantities across differing units of measure.

Common Use Cases and Queries

Typical scenarios include auditing reservations tied to a specific WIP entity, comparing reservation quantities against primary and order-line UOMs, and reporting sales-order demand reserved into WIP. The following query lists reservations with their UOM context for a given organization:

  • SELECT RESERVATION_ID, WIP_ENTITY_ID, INVENTORY_ITEM_ID, RESERVATION_UOM_CODE, RESERVATION_QUANTITY, PRIMARY_UOM_CODE, PRIMARY_QUANTITY FROM WIP_RESERVATIONS_V WHERE ORGANIZATION_ID = :org_id;
  • SELECT RESERVATION_ID, SEGMENT1, DEMAND_SOURCE_LINE_NUMBER, RESERVATION_UOM_CODE, RESERVATION_QUANTITY FROM WIP_RESERVATIONS_V WHERE DEMAND_SOURCE_LINE_ID = :line_id;

Because the view performs several joins and calls INV_CONVERT per row, queries should be constrained by ORGANIZATION_ID, WIP_ENTITY_ID, or RESERVATION_ID wherever possible to limit conversion overhead at high reservation volumes.