Search Results inventory_location_type




Overview
Explore in AI Chat

Overview

APPS.WMS_ZONE_LOCATORS_TEMP is a reporting and integration view in Oracle E-Business Suite, exposed under the APPS schema and documented in ETRM for releases 12.1.1 and 12.2.2. The view presents a denormalized projection of zone-to-locator assignment data used by Oracle Warehouse Management (WMS). Its name and column set indicate it serves as a temporary or staging presentation layer through which locator-level attributes — including subinventory context, picking and dropping order, and status information — are surfaced for consumption by concurrent programs, user interfaces, or integration endpoints.

The user's search term, locator_status, maps directly to a column exposed by this view. In WMS, locator status controls whether a locator is available for putaway, picking, or replenishment activity. Because the view carries both a status description (LOCATOR_STATUS) and a status code (LOCATOR_STATUS_CODE), it supports both display-oriented reporting and code-driven validation logic.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: WMS_ZONE_LOCATORS_GTMP, accessed through a synonym. The suffix _GTMP denotes a global temporary table. This is significant for how the view behaves. Unlike a conventional persistent table, a global temporary table holds session- or transaction-scoped rows, meaning the contents of WMS_ZONE_LOCATORS_TEMP are transient. Data is populated by a calling process, read back through the view, and then discarded at session or transaction completion.

The view itself is a straight SELECT from that temporary table without joins, filters, or aggregation. It exposes the temporary table's columns directly, along with ROWID aliased as ROW_ID. Consequently, the view inherits the temporary table's scoping rules: rows are visible only to the session that inserted them. Any query against this view outside the originating process will typically return no rows.

Key Columns

Common Use Cases and Queries

Because the object is a temporary-table view, its primary use is within the execution scope of a WMS process that populates WMS_ZONE_LOCATORS_GTMP. Typical scenarios include validating locator status before confirming a putaway suggestion, reviewing picking order across zone locators, and surfacing disable dates for locators that should be excluded from new work.

A representative query filtering on the searched attribute is:

SELECT organization_id, subinventory_code, locator_name, locator_status, locator_status_code, locator_disable_date FROM apps.wms_zone_locators_temp WHERE locator_status_code = 'XX';

For operational reporting, the same view can be joined back to persistent WMS and INV tables on INVENTORY_LOCATION_ID once the temporary rows are populated. Analysts should note that any such join must run in the same session that created the temporary data, or the result set will be empty.