Search Results wip_completed_quantity




Overview
Explore in AI Chat

Overview

SO_LINE_DETAILS_VIEW_WIP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing within the Order Entry (OE) product family. It is a denormalized, convenience-oriented projection of the SO_LINE_DETAILS synonym, joining that table to work-in-process entity information, item master data, and unit-of-measure codes. Its principal purpose is to expose the WIP (Work in Process) supply dimension of an order line detail record alongside human-readable item and WIP entity identifiers, which are otherwise stored as surrogate keys. The view is documented in ETRM 12.2.2 as VALID and is equally applicable to 12.1.1, where the underlying base objects share the same structure. Because it consolidates WIP reserved quantity, WIP completed quantity, and schedule status into a single readable row, it is typically used for reporting, diagnostics, and lightweight integration rather than for transactional processing.

Underlying Base Objects

The view is defined over four referenced data objects: SO_LINE_DETAILS, an APPS synonym for the order line detail table; WIP_ENTITIES, the synonym over the WIP entity master; MTL_UNITS_OF_MEASURE, the synonym over the units-of-measure definitions; and MTL_SYSTEM_ITEMS_VL, the item master view. It also invokes two programmatic references: FND_PROFILE, a package supplying the SO_ORGANIZATION_ID profile value that scopes item and WIP lookups to the current operating unit's inventory organization, and OE_QUERY, a package providing the ITEM_CONC_SEG function used to concatenate the item key flexfield segments into a display string. The join to MTL_SYSTEM_ITEMS_VL is an outer join keyed on both INVENTORY_ITEM_ID and the profile-derived ORGANIZATION_ID, and the join to WIP_ENTITIES is likewise outer-joined on SUPPLY_SOURCE_HEADER_ID. Consequently, line details that have no WIP supply source or no resolvable item in the current organization still appear in the result set, with nulls for the corresponding columns.

Key Columns

LINE_DETAIL_ID is the primary unique identifier for the underlying detail row and is the natural pivot for joins back to SO_LINE_DETAILS. WIP_ENTITY_NAME is the descriptive name of the WIP job associated with the supply source; it is null when no WIP entity exists. ITEM is the concatenated, flexfield-segmented item key derived through OE_QUERY.ITEM_CONC_SEG. WIP_RESERVED_QUANTITY and WIP_COMPLETED_QUANTITY express, respectively, quantity reserved against the WIP job and quantity already completed for the supply. SCHEDULE_STATUS_CODE conveys the scheduling state of the WIP supply. UOM_CODE is the unit of measure, defaulted to 'EA' via NVL when SLD.UNIT_CODE is null. ITEM_DESC returns the item description or 'NO DESCRIPTION AVAILABLE' when the description is missing. SUPPLY_SOURCE_HEADER_ID and LINE_ID link the record to its order line and supply source. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ROW_ID round out the projection.

Common Use Cases and Queries

Typical uses include reconciling WIP reservations and completions against sales order lines, validating that a supply source is properly wired to a WIP entity, and building operational reports for shop-floor or planning users who need readable item and job names. A representative query following the documented structure is:

  • SELECT LINE_DETAIL_ID, WIP_ENTITY_NAME, ITEM, WIP_RESERVED_QUANTITY, WIP_COMPLETED_QUANTITY, SCHEDULE_STATUS_CODE FROM APPS.SO_LINE_DETAILS_VIEW_WIP_V WHERE LINE_ID = :line_id;
  • SELECT WIP_ENTITY_NAME, ITEM, ITEM_DESC, WIP_COMPLETED_QUANTITY FROM APPS.SO_LINE_DETAILS_VIEW_WIP_V WHERE SUPPLY_SOURCE_HEADER_ID = :wip_entity_id ORDER BY CREATION_DATE;
  • SELECT ITEM, UOM_CODE, SUM(WIP_RESERVED_QUANTITY), SUM(WIP_COMPLETED_QUANTITY) FROM APPS.SO_LINE_DETAILS_VIEW_WIP_V GROUP BY ITEM, UOM_CODE;

Because ITEM resolution depends on FND_PROFILE.VALUE('SO_ORGANIZATION_ID'), applications and reports querying this view should run within a correctly initialized session where the SO organization profile is populated; otherwise item joins may return null and descriptions may fall back to the default text. The outer joins further mean callers must handle null WIP_ENTITY_NAME values for non-WIP supply sources.