Search Results wms_packing_material_v

Overview

The APPS.WMS_PACKING_MATERIAL_V view is a public, valid database object in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Warehouse Management (WMS) product family and is registered in the E-Business Suite Technical Reference Manual (ETRM). Its documented description — "View to be used for Packing Workbench eligible material spreadtable" — defines its primary purpose: it exposes a flattened, query-ready result set of materials that are eligible for packing in the Packing Workbench. Rather than storing data, the view acts as a lightweight presentation and integration layer over a global temporary table, allowing reports, forms, and custom code to consume packing-eligible material rows through a stable, named interface.

Because the view is owned by APPS and defined with a broad SELECT * projection, it functions as a spreadtable source for OAF-based and Oracle Forms-based Packing Workbench screens. It also supports downstream reporting and integration requirements for outbound logistics, shipping, and warehouse operations.

Underlying Base Objects

The view is defined simply as:

• SELECT * FROM WMS_PACKING_MATERIAL_GTEMP

The single documented base object is WMS_PACKING_MATERIAL_GTEMP, referenced in the ETRM metadata as a synonym. In EBS 12.1.1 and 12.2.2, global temporary tables are session-scoped: rows are visible only to the session that inserts them and are typically cleared on commit or session termination. This design means the view is not a persistent reporting source — its content is populated at runtime by the Packing Workbench processing logic before being queried and displayed. Because the view performs no joins or filters itself, all eligibility logic, shaping, and enrichment are applied upstream by the process that loads the temporary table. The view therefore inherits the temporary table's structure and any synonym-based redirection.

Key Columns

The view exposes a comprehensive set of packing, shipping, and order attributes. Notable columns include:

• Move order context: MOVE_ORDER_HEADER_ID, MOVE_ORDER_LINE_ID, TXN_SOURCE_ID, DELIVERY_DETAIL_ID.
• Inventory context: ORGANIZATION_ID, ORGANIZATION_CODE, SUBINVENTORY, LOCATOR_ID, LOCATOR, INVENTORY_ITEM_ID, ITEM, ITEM_DESCRIPTION, REVISION, UOM, LOT_NUMBER, QUANTITY, SECONDARY_QUANTITY, SECONDARY_UOM_CODE, GRADE_CODE.
• LPN hierarchy: LPN_ID, LPN, PARENT_LPN_ID, PARENT_LPN, OUTERMOST_LPN_ID, OUTERMOST_LPN.
• Project/task: PROJECT_ID, PROJECT, TASK_ID, TASK_NUMBER, TASK_NAME.
• Delivery/trip: DELIVERY_ID, DELIVERY, DELIVERY_COMPLETED, TRIP_ID, TRIP, CARRIER_ID, CARRIER.
• Order/customer: ORDER_HEADER_ID, ORDER_NUMBER, ORDER_LINE_ID, ORDER_LINE_NUM, CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME, SHIP_TO_LOCATION_ID, SHIP_TO_LOCATION, SHIP_SET_ID, SHIP_SET.
• Document/receiving: RECEIPT_NUM, DOCUMENT_TYPE, DOCUMENT_ID, DOCUMENT_NUMBER, DOCUMENT_LINE_ID, DOCUMENT_LINE_NUM, VENDOR_ID, SOURCE_ORG_ID, TRADING_PARTNER, RECEIVING_LOCATION_ID, RECEIVING_LOCATION.
• Flags: PTO_FLAG (the user's search term) and SELECTED_FLAG, which participate in Packing Workbench selection and eligibility logic.

The PTO_FLAG column is of particular interest: it typically indicates whether the underlying material is associated with a Pick-To-Order (PTO) configured item or shipping model, influencing how the Packing Workbench spreads and groups eligible material. Its value is derived from the source data loaded into the global temporary table.

Common Use Cases and Queries

The principal use case is the Packing Workbench's eligible-material spreadtable, where rows feed the interactive packing UI. Secondary uses include custom validation, diagnostics, and troubleshooting packing eligibility — especially around the PTO_FLAG and SELECTED_FLAG attributes.

A representative query within the same session that populated the temporary table:

• SELECT move_order_line_id, delivery_detail_id, item, uom, lot_number, lpn, pto_flag, selected_flag FROM apps.wms_packing_material_v WHERE pto_flag = 'Y';

Because the view selects from a global temporary table, queries issued from a different session will not return the populating session's rows. Queries are therefore meaningful primarily immediately after the WMS packing process runs, within the originating session. Teams should avoid treating this view as a persistent reporting object and instead rely on permanent WMS and shipping base tables for historical analysis.