Results for “dropping_order”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.WMS_ZONE_LOCATORS_V view is a Warehouse Management (WMS) reporting and integration object that presents the association between warehouse zones and the inventory locators (locations) they contain. It is defined over the base table WMS_ZONE_LOCATORS, which stores the physical mapping of stock locators to picking, put-away, or storage zones within a warehouse. The view enriches this mapping by joining to locator and subinventory definition tables so that zone-locator relationships can be reported at the level of descriptive names rather than surrogate keys. Its status is VALID in the APPS schema and it is typically used by Oracle Warehouse Management and adjacent modules for directed put-away, picking, replenishment, and zone-based querying. For users who search on locator_disable_date, this view is significant because it exposes LOCATOR_DISABLE_DATE, allowing a zone-locator record to be filtered or reported based on whether the underlying inventory locator has been end-dated.

Underlying Base Objects

The view text joins four documented objects. The primary base object is WMS_ZONE_LOCATORS (referenced as a synonym), which supplies ORGANIZATION_ID, ZONE_ID, SUBINVENTORY_CODE, and INVENTORY_LOCATION_ID. MTL_ITEM_LOCATIONS_KFV (a view) is outer-joined on INVENTORY_LOCATION_ID and ORGANIZATION_ID, supplying the concatenated locator name, picking order, dropping order, inventory location type, disable date, and locator status. MTL_SECONDARY_INVENTORIES (a synonym to the subinventory definition) is joined on subinventory name and organization to provide the subinventory type and status identifier. WMS_ZONES_TL (a synonym) is joined on ZONE_ID and restricted to LANGUAGE = USERENV('LANG') to return the translated zone name. The outer join to the item locations view means zone-locator rows persist even when the locator record itself is absent.

Key Columns

• ORGANIZATION_ID — The inventory organization (warehouse) owning the zone-locator relationship.
• ZONE_ID / ZONE_NAME — The zone identifier and its language-specific display name from WMS_ZONES_TL.
• SUBINVENTORY_CODE — The subinventory in which the locator resides.
• INVENTORY_LOCATION_ID / LOCATOR_NAME — The locator primary key and its concatenated segment name; the name is null when no matching locator exists (via DECODE on the outer join).
• LOCATOR_DISABLE_DATE — The disable/end-date of the inventory locator, sourced from MIL.DISABLE_DATE. This is the column of primary interest to users searching for inactive locators.
• LOCATOR_STATUS — The status of the inventory locator (for example, active or inactive).
• PICKING_ORDER / DROPPING_ORDER — Sequence values governing pick and put-away ordering within the zone.
• INVENTORY_LOCATION_TYPE — The locator type (for example, storage, receiving, staging).
• SUBINVENTORY_TYPE and SUBINVENTORY_STATUS — The subinventory type and its status identifier.

Common Use Cases and Queries

Typical uses include listing all locators belonging to a given zone, resolving zone membership for a specific locator, and — most relevant to the searched term — identifying zone-locators whose underlying locator has been disabled. A representative query for active zone-locators is:

SELECT organization_id, zone_name, subinventory_code,
       locator_name, picking_order, locator_status
FROM   apps.wms_zone_locators_v
WHERE  organization_id = :org_id
AND    zone_name = :zone_name
AND    locator_disable_date IS NULL
ORDER BY picking_order;

To review disabled locators still mapped to zones, the filter is reversed:

SELECT zone_name, subinventory_code, locator_name,
       locator_disable_date, locator_status
FROM   apps.wms_zone_locators_v
WHERE  organization_id = :org_id
AND    locator_disable_date IS NOT NULL;

Because ORGANIZATION_ID is a mandatory join column on all base objects, queries should always constrain it to one warehouse for performance and correctness. The view is read-only and is suited to reporting and integration extracts rather than transactional updates.