Search Results transfer_sub_code

Overview

WMS_DEVICE_REQUESTS_WCSV is a seeded Oracle E-Business Suite view owned by the APPS schema and defined within the Warehouse Management (WMS) product family. It is documented as the view on which both device request queries and device response queries can be based, making it the standard reporting and integration access point for radio-frequency (RF) and material-handling device activity. Rather than exposing the raw transactional table WMS_DEVICE_REQUESTS in isolation, the view denormalizes that table and joins it to device definitions, lookup meanings, item master data, locator information, and license plate numbers, producing a single flattened row suitable for direct consumption by external systems or ad-hoc reporting.

The view is especially relevant to users searching on outfile_name: this column is exposed directly from WMS_DEVICE_REQUESTS and identifies the output file associated with a device request, which is commonly used when integrating Oracle WMS with warehouse control systems (WCS) or when auditing device-generated output. The view carries STATUS VALID status on both 12.1.1 and 12.2.2, so it is considered a supported, upgrade-safe object.

Underlying Base Objects

Per the documented metadata, WMS_DEVICE_REQUESTS_WCSV is defined over the following objects:

• WMS_DEVICE_REQUESTS (synonym) — the driving transactional table holding each device request record.
• WMS_DEVICES (synonym) — supplies device name, device ID, and device type ID.
• WMS_LICENSE_PLATE_NUMBERS (synonym) — supplies the LPN (license plate number) associated with the request.
• MTL_SYSTEM_ITEMS (synonym) — supplies the item segment (ITEM = SEGMENT1).
• MTL_ITEM_LOCATIONS (synonym) — supplies the locator segments and the inventory location ID used by the locator function.
• MFG_LOOKUPS (view) — joined on lookup type 'WMS_BUS_EVENT_TYPES' to translate BUSINESS_EVENT_ID into a readable BUSINESS_EVENT meaning.
• INV_PROJECT (package) — its GET_LOCSEGS function is invoked to render the concatenated LOCATOR value from the inventory location ID and organization ID.

Note that the joins to MFG_LOOKUPS and MTL_ITEM_LOCATIONS use outer-join syntax (+), so device requests without a matching lookup row or location row still appear in the result set with nulls in those columns.

Key Columns

• REQUEST_ID, TASK_ID, SEQUENCE_ID — identifiers for the device request, its task, and the ordering sequence within the task.
• TASK_TYPE_ID, BUSINESS_EVENT_ID, BUSINESS_EVENT — the type and business event classification; BUSINESS_EVENT is the decoded lookup meaning.
• STATUS_CODE, STATUS_MSG — processing status and any associated status message for the request.
• OUTFILE_NAME — name of the output file linked to the request, typically used by WCS integrations and device output processing.
• DEVICE_ID, DEVICE_NAME, DEVICE_TYPE_ID — the device that generated or received the request.
• ITEM, INVENTORY_ITEM_ID, REVISION, UOM — item identification and unit of measure.
• QUANTITY, TRANSACTION_QUANTITY, LOT_NUMBER, LOT_QTY, SERIAL_NUMBER — quantities and lot/serial tracking data.
• SUBINVENTORY_CODE, LOCATOR, LOCATOR_ID, SEGMENT1..SEGMENT20 — inventory location detail, with the concatenated LOCATOR produced via INV_PROJECT.GET_LOCSEGS.
• LPN — license plate number from WMS_LICENSE_PLATE_NUMBERS.
• TRANSFER_ORG_ID, TRANSFER_SUB_CODE, TRANSFER_LOC_ID — destination organization, subinventory, and locator for transfer transactions.
• RELATION_ID, TASK_SUMMARY — supporting linkage and descriptive summary of the task.

Common Use Cases and Queries

Typical scenarios include monitoring pending and completed device requests, tracing outbound files written by the device layer, reconciling RF transactions against inventory, and feeding external WCS or MHE systems. A common starting query filters on OUTFILE_NAME and status:

• SELECT request_id, device_name, business_event, item, quantity, status_code, outfile_name FROM wms_device_requests_wcsv WHERE outfile_name IS NOT NULL;
• SELECT request_id, task_id, lpn, subinventory_code, locator, transaction_quantity FROM wms_device_requests_wcsv WHERE device_id = :device_id AND status_code = 'PENDING';
• SELECT item, serial_number, lot_number, transfer_org_id, transfer_sub_code FROM wms_device_requests_wcsv WHERE business_event = 'Putaway' AND task_type_id = :task_type_id;
• SELECT outfile_name, COUNT(*) FROM wms_device_requests_wcsv GROUP BY outfile_name ORDER BY 2 DESC;

Because the view already resolves lookups, items, and locators, reports and interfaces can be built against it without repeating those joins, simplifying both custom reporting and WCS integration logic.