Search Results user_line_num




Overview
Explore in AI Chat

Overview

WIP_SALES_ORDER_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). It presents sales order demand lines that are associated with build-in-WIP items, exposing the subset of demand records that originate from sales orders and are relevant to Work in Process planning and execution. The view is not a transactional object; it is a read-only projection designed to support inquiry, reporting, and integration scenarios where downstream logic must reconcile sales order demand against WIP supply.

Because the view filters on configuration status, demand type, and reservation type, it returns only demand rows that represent buildable sales order lines tied to configured or standard items. This makes it particularly useful for supply chain analysts, discrete manufacturing planners, and custom reports that need to correlate sales order commitments with WIP-driven supply.

Underlying Base Objects

The view is defined over two documented base objects: MTL_DEMAND (referenced as a synonym) and MTL_SYSTEM_ITEMS (SYNONYM). MTL_DEMAND stores all demand and supply records in the planning and inventory model, including sales order demand, work order demand, and transfer demand. MTL_SYSTEM_ITEMS is the item master at the organization level and supplies item attributes such as BUILD_IN_WIP_FLAG and BOM_ITEM_TYPE.

The join between the two tables is performed on INVENTORY_ITEM_ID and ORGANIZATION_ID, ensuring that only items defined within the same inventory organization are considered. The view restricts the item population to those with BUILD_IN_WIP_FLAG = 'Y' and BOM_ITEM_TYPE = 4, meaning only buildable items are surfaced. Additional predicates on MTL_DEMAND restrict the result set to reservation type 1, row status flag 1, demand source type 2 (sales order), and demand type 4 or 6 with CONFIG_STATUS = 20. Records with a parent demand, a supply source header, or a supply group are excluded, as are lines where completed quantity has reached or exceeded ordered quantity.

Key Columns

  • DEMAND_SOURCE_LINE — The source document line identifier for the sales order demand.
  • USER_LINE_NUM — The user-visible line number on the originating sales order, commonly used for customer-facing reporting and reconciliation.
  • DEMAND_SOURCE_DELIVERY — The delivery identifier linked to the demand source.
  • USER_DELIVERY — The user-visible delivery number.
  • REQUIREMENT_DATE — The date by which the demand must be satisfied, driving scheduling and planning decisions.
  • PRIMARY_UOM_QUANTITY — Demand quantity expressed in the item's primary unit of measure.
  • UOM_CONVERSION_RATE — Derived as LINE_ITEM_QUANTITY divided by PRIMARY_UOM_QUANTITY, providing the conversion factor between the line item UOM and the primary UOM.
  • UOM_CODE — The unit of measure code applicable to the demand line.
  • INVENTORY_ITEM_ID — The inventory item identifier for the demanded item.
  • DEMAND_CLASS — Classification of the demand, typically used to distinguish order types.
  • SUBINVENTORY — The subinventory associated with the demand, if specified.
  • DEMAND_SOURCE_HEADER_ID — The header identifier of the originating sales order.
  • ORGANIZATION_ID — The inventory organization in which the demand is defined.

Common Use Cases and Queries

A typical use case is identifying open sales order demand for buildable items that has not yet been fully supplied. Analysts frequently retrieve demand lines by organization, requirement date, or item to drive WIP scheduling.

SELECT USER_LINE_NUM,
       DEMAND_SOURCE_HEADER_ID,
       DEMAND_SOURCE_LINE,
       REQUIREMENT_DATE,
       PRIMARY_UOM_QUANTITY,
       UOM_CODE,
       INVENTORY_ITEM_ID
FROM   APPS.WIP_SALES_ORDER_LINES_V
WHERE  ORGANIZATION_ID = :org_id
AND    REQUIREMENT_DATE BETWEEN :start_date AND :end_date
ORDER BY REQUIREMENT_DATE, USER_LINE_NUM;

The user_line_num column is often queried directly when reconciling a report against the sales order line visible to end users. A common pattern joins the view to MTL_SYSTEM_ITEMS for item descriptions, or to sales order tables via DEMAND_SOURCE_HEADER_ID and DEMAND_SOURCE_LINE for order context. Because the view already enforces build-in-WIP and configuration filters, it is well suited to dashboards that monitor WIP-related sales order backlog without additional filtering logic.