Results for “labor_enabled”

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

Overview

WMS_ZONES_B is the base (header) table in the Oracle Warehouse Management System (WMS) schema that defines warehouse zones. A zone is a logical grouping of physical stocking locations used to organize material handling, picking, putaway, and replenishment activities within a warehouse organization. In Oracle EBS 12.1.1 and 12.2.2, zones act as the intermediate grouping layer between a subinventory and its individual locators, enabling planners and warehouse supervisors to direct work to a region of the warehouse rather than to a single bin.

The table resides in the WMS schema, is classified VALID status, and contains 27 documented columns. It is accessible to functional users through the Warehouse Management setup menus and to developers through the public WMS schema views. Under a heuristic Data Vault classification mined from the foreign-key structure, WMS_ZONES_B presents as a standalone hub: no foreign keys are defined from this table to other tables, while numerous dependent tables reference it through ZONE_ID. This suggests WMS_ZONES_B holds the durable business key (the zone identity) around which satellites and downstream link tables may be modeled.

Key Information Stored

The surrogate primary key is ZONE_ID, enforced by the constraint WMS_ZONES_B_PK and additionally protected by the unique index WMS_ZONES_B_U1. Because both the primary key and the sole unique index are defined on ZONE_ID, the effective business key and the technical key are the same column in the documented schema; there is no separate natural-key composite in the metadata.

• ZONE_ID — the system-generated unique identifier for the zone; referenced by all dependent tables.
• ORGANIZATION_ID — the inventory organization to which the zone belongs, tying the zone to a specific warehouse.
• ENABLED_FLAG — indicates whether the zone is currently active and selectable for warehouse operations.
• DISABLE_DATE — the date on which the zone was deactivated, supporting historical reporting.
• ZONE_TYPE — the functional classification of the zone (for example, picking, staging, or storage), which influences how the zone is used by WMS engines.
• LABOR_ENABLED — controls whether labor management and labor standards apply to work directed to the zone.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns present on nearly all EBS transactional tables.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexible descriptive flexfield (DFF) columns allowing customer-specific zone attributes without schema change.

The remaining documented columns support these core fields; only the audit and DFF segments, plus the five functional columns above, are materially significant for integration and reporting.

Common Use Cases and Queries

Typical usage includes listing all active zones for an organization, identifying zones where labor management is enabled, and joining zones to locators for directed picking. A representative query is:

• SELECT zone_id, organization_id, zone_type, enabled_flag FROM wms_zones_b WHERE organization_id = :org_id AND enabled_flag = 'Y';
• Join to locators: SELECT z.zone_id, z.zone_type, l.locator_id, l.inventory_location_id FROM wms_zones_b z, wms_zone_locators l WHERE z.zone_id = l.zone_id;
• Picking rule analysis: SELECT p.picking_rule_name, z.zone_type FROM wsh_picking_rules p, wms_zones_b z WHERE p.zone_id = z.zone_id;
• Labor reporting: SELECT zone_id, zone_type FROM wms_zones_b WHERE labor_enabled = 'Y' AND organization_id = :org_id;

Reporting use cases include zone utilization summaries, labor-enabled zone audits, and validation of picking rule configurations before go-live.

Related Objects

WMS_ZONES_B is heavily referenced. The most significant dependencies follow:

• WMS_ZONE_LOCATORS.ZONE_ID → WMS_ZONES_B.ZONE_ID — associates physical locators with zones.
• WSH_PICKING_RULES.ZONE_ID → WMS_ZONES_B.ZONE_ID — links picking rules to the zones they govern.
• WSH_PICKING_BATCHES.ZONE_ID → WMS_ZONES_B.ZONE_ID — assigns picking batches to zones.
• MSC_ITEM_SOURCING.ZONE_ID → WMS_ZONES_B.ZONE_ID — supports sourcing rules by zone in Advanced Supply Chain Planning.
• MSC_DEMANDS.ZONE_ID and MSC_DEMANDS_F.ZONE_ID → WMS_ZONES_B.ZONE_ID — connect planning demand records to zones.
• MSC_EXCEPTION_DETAILS.ZONE_ID and MSC_INT_ASCP_EXCEPTION_DETAILS.ZONE_ID → WMS_ZONES_B.ZONE_ID — exception reporting by zone.
• FTE_INTERFACE_ZONES.ZONE_ID → WMS_ZONES_B.ZONE_ID — fleet/transportation interface reference.
• MSC_SUPPLIES.ZONE_ID, MSC_BIS_INV_DETAIL.ZONE_ID, MSC_FORECAST_UPDATES.ZONE_ID → WMS_ZONES_B.ZONE_ID — additional planning and inventory intelligence dependencies.

These relationships confirm the table's role as a foundational reference for both execution and planning in Oracle EBS.