Search Results so_organization_id




Overview
Explore in AI Chat

Overview

The APPS.SO_LINE_DETAILS_VIEW_WIP_V view is an Oracle E-Business Suite (EBS) reporting and integration object that exposes order line supply details for Work-in-Process (WIP) related demand. It consolidates information from several Order Management, Inventory, and Manufacturing objects into a single denormalized structure, allowing report writers, forms, and interfaces to retrieve WIP-referenced sales order supply lines without manually joining the constituent base tables. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2.

The view is particularly important in environments where sales order lines are linked to discrete jobs or other WIP entities as a supply source. It surfaces the reserved and completed quantities carried on the sales order line detail, the associated WIP entity name, and descriptive item information resolved from the inventory item master.

Underlying Base Objects

The view is defined over the following documented base objects, expressed as synonyms, views, and packages in the APPS schema:

  • SO_LINE_DETAILS (SYNONYM) – the primary source of order line supply records, filtered to WIP supply source rows.
  • WIP_ENTITIES (SYNONYM) – provides the WIP entity name associated with the supply source header.
  • MTL_SYSTEM_ITEMS_VL (VIEW) – supplies the item description and participates in the coded item name resolution.
  • MTL_UNITS_OF_MEASURE (SYNONYM) – provides the UOM code for the line.
  • OE_QUERY (PACKAGE) – the package function ITEM_CONC_SEG resolves the concatenated item segment.
  • FND_PROFILE (PACKAGE) – supplies the SO_ORGANIZATION_ID profile value at runtime.

Notably, item enrichment is resolved at runtime through the FND_PROFILE package using the SO_ORGANIZATION_ID profile option. Both the MTL_SYSTEM_ITEMS_VL and WIP_ENTITIES joins are outer joins (denoted by the (+) operator), so lines without a matching item or WIP entity are still returned, with the item description defaulting to "NO DESCRIPTION AVAILABLE."

Key Columns

Common Use Cases and Queries

Typical use cases include reporting on WIP-linked sales order demand, reconciliation of reserved versus completed quantities, and integration extracts feeding manufacturing or planning systems.

The profile option SO_ORGANIZATION_ID should be set in the querying session so that ITEM and ITEM_DESC resolve correctly. A representative query selecting WIP supply details for a given order line is shown below:

  • 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;

Because the view relies on profile option values and package functions, performance is best preserved by filtering on indexed identifiers such as LINE_ID or LINE_DETAIL_ID rather than scanning by descriptive columns.