Search Results delivered_qty

Overview

APPS.WMS_WP_LINES_GTMP_V is a reporting and integration view in the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The view presents warehouse planning line detail — the row-level information associated with wave planning, pick release, and shipment execution — in a denormalized, consumer-friendly format. Rather than requiring callers to join the global temporary table WMS_WP_LINES_GTMP against order, item, customer, and shipment masters, the view exposes a broad, pre-flattened column set suitable for direct consumption by reports, concurrent programs, interfaces, and diagnostic queries. Its naming convention (the _GTMP suffix and _V extension) indicates that it is a view layered over a global temporary table whose contents are session-scoped and typically populated by WMS planning or wave-processing logic during a given run.

Underlying Base Objects

The view is defined over a single documented base object: the synonym WMS_WP_LINES_GTMP. The view text is a straight projection — SELECT with an explicit column list and no joins, filters, or transformation logic — so the view adds no business logic of its own. It functions purely as a stable, readable interface over the temporary table. Because the base object is a global temporary table, the data returned is visible only within the session or transaction context that populated it; the view is therefore most meaningful while a WMS wave-planning or pick/ship process is active, or within a program that has already seeded the temporary table. Any column list changes to the temporary table will propagate to the view and should be validated when applying patches or upgrades.

Key Columns

The column list is extensive and covers the full lifecycle of a warehouse line. Notable groups include:

• Shipment quantity columns: SHIPPED_QTY, DELIVERED_QTY, REQUESTED_QTY, SOURCE_REQUESTED_QTY, and the secondary-UOM counterparts SECONDARY_SHIPPED_QTY, SECONDARY_DELIVERED_QTY, SECONDARY_REQUESTED_QTY, and SECONDARY_SRC_REQ_QTY. These are the fields most commonly referenced when users search for shipped_qty, since they carry the actual quantity shipped versus planned or requested.
• Fill-rate metrics: PLANNED_FILL_RATE, RELEASE_FILL_RATE, and PICK_FILL_RATE provide planning-versus-execution efficiency indicators.
• Line status and progress: LINE_STATUS, LINE_PROGRESS, and EXCEPTION_ID identify where the line stands and whether an exception was raised.
• Order and delivery identifiers: ORDER_NUMBER, SOURCE_LINE_NUMBER, DELIVERY, DELIVER_TO, SHIP_TO, WAVE_FIRMED_FLAG, REMOVE_FROM_WAVE_FLAG, TRIP, and LOADING_SEQUENCE.
• Item and logistics attributes: ITEM, ITEM_DESCRIPTION, REVISION, LOT, LOCATOR, BATCH, GROSS_WEIGHT, NET_WEIGHT, TARE_WEIGHT, VOLUME, and their UOM columns.
• Dates and parties: DATE_REQUESTED, DATE_SCHEDULED, EARLIEST_SHIP_DATE, EARLIEST_DELIVERY_DATE, LATEST_DELIVERY_DATE, CARRIER, SHIP_METHOD, and CUSTOMER.
• Diagnostics: MESSAGE carries a status or error message for the line.

Common Use Cases and Queries

Typical scenarios include reconciling shipped quantities against requested quantities during wave release, investigating short-ships or pick exceptions, and feeding downstream shipment-confirmation interfaces. A representative query retrieving shipped quantity per order line is:

• SELECT order_number, source_line_number, item, requested_qty, shipped_qty, delivered_qty, line_status FROM apps.wms_wp_lines_gtmp_v WHERE shipped_qty > 0;
• SELECT order_number, item, (shipped_qty / NULLIF(requested_qty,0)) AS ship_ratio FROM apps.wms_wp_lines_gtmp_v WHERE exception_id IS NOT NULL; — useful for exception analysis and fill-rate review.

Because the underlying object is a session-scoped global temporary table, these queries return rows only when executed in the session that populated the table or within the WMS process that owns the data.