Search Results replenishment_status




Overview
Explore in AI Chat

Overview

APPS.WSH_DELIVERY_DETAILS_OE_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the FND design data path WSH.WSH_DELIVERY_DETAILS_OE_V. It exposes delivery detail records specifically in the context of the Order Management (OE) fulfillment flow, joining delivery information to the source sales order line wherever the source code is OE. The view carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2.

Oracle classifies this object as Internal. The ETRM metadata carries an explicit warning that Oracle Corporation does not support access to applications data using this object except from standard Oracle Applications programs. Consequently, the view is intended primarily for Oracle's own shipping and order-management code paths, not as a public integration interface. Development and reporting teams that discover it — for example while searching for oe_interfaced_flag — should treat it as a read-only reference rather than a supported API surface, and should validate any dependency before promoting custom SQL to production.

Underlying Base Objects

The view is defined over a small set of documented base objects: OE_ORDER_LINES_ALL (synonym), WSH_DELIVERY_ASSIGNMENTS_V (view), WSH_DELIVERY_DETAILS (synonym), WSH_LOOKUPS (view), and WSH_NEW_DELIVERIES (synonym). WSH_NEW_DELIVERIES supplies the delivery header (DELIVERY_ID and DELIVERY_NAME), WSH_DELIVERY_DETAILS supplies the delivery line grain and the primary key DELIVERY_DETAIL_ID, and WSH_DELIVERY_ASSIGNMENTS_V provides the linkage between delivery details and the source order line. OE_ORDER_LINES_ALL supplies the Order Management line context, while WSH_LOOKUPS resolves descriptive meanings for the various status and flag values. The join to OE_ORDER_LINES_ALL is what constrains the result set to Order Management-sourced delivery lines, which is why the view is named with the OE suffix.

Key Columns

Common Use Cases and Queries

The principal use case is reconciling delivery activity back to Order Management — confirming that a delivery line has been interfaced to OM before downstream invoicing or order-line status updates proceed. A typical diagnostic query lists delivery lines awaiting OM interface for a given organization:

  • SELECT delivery_id, delivery_name, source_header_id, source_line_id, requested_quantity, oe_interfaced_flag, inv_interfaced_flag, released_status, delivered_date FROM apps.wsh_delivery_details_oe_v WHERE source_code = 'OE' AND organization_id = :org_id AND oe_interfaced_flag = 'N';
  • Confirm the interface state for a single sales order line by filtering on SOURCE_LINE_ID and joining to OE_ORDER_LINES_ALL for ordered versus shipped quantity comparison.
  • Report tracking information by selecting DELIVERY_NAME, TRACKING_NUMBER, and WAYBILL for delivered lines within a date range on DELIVERED_DATE.
  • Audit pick release progress using RELEASED_STATUS and ORIGINAL_LINE_STATUS to identify lines stuck between release and ship confirmation.

Because the object is flagged Internal, these queries should be confined to diagnostic and reconciliation purposes. Supported integration should instead use the documented Order Management and Shipping public APIs.