Search Results wms_wsh_wdd_gtemp




Overview
Explore in AI Chat

Overview

WMS_WSH_WDD_GTEMP is a transient staging table owned by the WMS (Warehouse Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The name follows Oracle's standard "GTEMP" convention used for global temporary or interface tables that hold intermediate rows during a concurrent program or PL/SQL processing run before final processing. The table carries 168 documented columns and is populated with delivery detail and shipment line information drawn from the shipping and warehouse execution flows, which is why its column set closely mirrors WSH_DELIVERY_DETAILS and its associated movement statistics structures.

The table is used by warehouse management and shipping processes such as the trip/delivery interface and the Ship Confirm / Movement Statistics interface. Rows are typically inserted in a batch, validated or transformed, and then written to the persistent shipping or movement statistics tables. Based on the foreign key structure supplied in the metadata, no incoming foreign keys from other tables are documented; the heuristic Data Vault classification is therefore standalone. Under a Data Vault-style model this table would most naturally be treated as a satellite (descriptive delivery attributes) rather than a hub or link, though that is a modeling suggestion rather than a documented constraint.

Key Information Stored

The primary business identifier in the delivery context is DELIVERY_DETAIL_ID, referenced by related shipping tables. The table's own surrogate identity is carried by the key columns in the delivery and movement context, with MOVEMENT_ID acting as the foreign key to the movement statistics table. The most significant columns include:

Standard EBS audit and interface columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, ATTRIBUTE1 through ATTRIBUTE15, and the TP_ATTRIBUTE series) are also present for traceability and extensibility.

Common Use Cases and Queries

Because the table is populated transiently, it is most useful during debugging and reconciliation of a failed interface run. A typical query confirms which lines were staged for a given request before final processing:

SELECT DELIVERY_DETAIL_ID, SOURCE_LINE_ID, INVENTORY_ITEM_ID,
       SHIPPED_QUANTITY, MOVEMENT_ID, RETURN_STATUS, R_MESSAGE_CODE
  FROM   WMS.WMS_WSH_WDD_GTEMP
  WHERE  REQUEST_ID = :request_id
  ORDER  BY SOURCE_LINE_ID;

Reporting scenarios include reconciling staged shipped vs. delivered quantities, isolating rows that did not interface (INV_INTERFACED_FLAG or OE_INTERFACED_FLAG), and auditing hazardous-material or container/LPN data included in a shipment. A further pattern joins the staged rows to MTL_MOVEMENT_STATISTICS by MOVEMENT_ID to verify that movement records were successfully generated.

Related Objects

The table is joined to the following significant objects:

  • MTL_MOVEMENT_STATISTICS – via MOVEMENT_ID, the principal downstream movement record.
  • PO_HAZARD_CLASSES_B – via HAZARD_CLASS_ID, hazardous material classification.
  • MTL_CUSTOMER_ITEMS – via CUSTOMER_ITEM_ID, customer item definitions.
  • WSH_DELIVERY_DETAILS – via DELIVERY_DETAIL_ID, the persistent delivery detail source.
  • WSH_TRIPS / WSH_DELIVERY_ASSIGNMENTS – the broader trip and delivery grouping structures.
  • MTL_SYSTEM_ITEMS_B – via INVENTORY_ITEM_ID, for item description and attribute lookups.

The shipping and Inventory movement statistics concurrent programs, together with the standard WSH and INV APIs, are the primary processes that populate and consume this temporary table.