Results for “wms_exceptions”

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

Overview

The WMS_EXCEPTIONS table resides in the WMS (Warehouse Management) schema of Oracle E-Business Suite and is documented as a valid table in both 12.1.1 and 12.2.2. Its stated purpose is to capture task exceptions — deviations, discrepancies, or failures that arise while warehouse operators execute dispatched tasks such as picking, put-away, replenishment, or move orders. When an operator cannot complete a task as expected (for example, an item is missing, damaged, or a quantity differs), the warehouse management engine records the exception in this table so that supervisors and downstream processes can review, resolve, or escalate the issue.

Based on the foreign-key topology mined from the ETRM metadata, the heuristic Data Vault classification for this object is link. This is a modeling suggestion: the table sits at the intersection of a dispatched task, an inventory item, a person, a reason code, and a location, making it a natural association record rather than a pure hub or satellite. In practice, it behaves as a transactional junction table that connects warehouse execution activity to inventory and human-resource master data.

Key Information Stored

The table contains 39 documented columns. The most operationally significant are:

• TASK_ID — Reference to the originating task in WMS_DISPATCHED_TASKS; the anchor of the exception record.
• SEQUENCE_NUMBER and WMS_TASK_TYPE — Together with TASK_ID these form the unique index WMS_EXCEPTIONS_U1, the business-key candidate, distinguishing multiple exceptions per task.
• ORGANIZATION_ID — The warehouse/inventory organization in which the exception occurred.
• INVENTORY_ITEM_ID — The item involved, joined to item master and lot/revision tables.
• PERSON_ID — The operator or employee responsible, validated against PER_ALL_PEOPLE_F using the EFFECTIVE_START_DATE/EFFECTIVE_END_DATE date-tracked key.
• REASON_ID — The coded explanation from MTL_TRANSACTION_REASONS.
• DISCREPANCY_TYPE — Categorizes the nature of the exception.
• INVENTORY_LOCATION_ID and SUBINVENTORY_CODE — Where the exception was raised.
• LOT_NUMBER and REVISION — Lot and revision context for lot-controlled or revision-controlled items.
• TRANSACTION_HEADER_ID — Link to MTL_MATERIAL_TRANSACTIONS_TEMP pending transaction data.
• ARCHIVE_FLAG, WF_ITEM_KEY, and LPN_ID — Archive status, workflow correlation key, and license plate number reference.
• The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ATTRIBUTE1–15 for extensibility.

No surrogate single-column primary key is documented; the unique index serves as the business-key identifier.

Common Use Cases and Queries

Warehouse supervisors use this table to build exception dashboards, monitoring unresolved discrepancies by warehouse or operator. A typical query joins task and item data:

• Exceptions for a specific task: SELECT * FROM WMS_EXCEPTIONS WHERE TASK_ID = :task_id;
• Exceptions by employee: SELECT * FROM WMS_EXCEPTIONS WHERE PERSON_ID = :person_id;
• Discrepancy summary by reason: SELECT REASON_ID, COUNT(*) FROM WMS_EXCEPTIONS GROUP BY REASON_ID;
• Exceptions by warehouse: SELECT * FROM WMS_EXCEPTIONS WHERE ORGANIZATION_ID = :org_id AND ARCHIVE_FLAG = 'N';

Reporting typically groups by DISCREPANCY_TYPE or REASON_ID to identify recurring operational problems.

Related Objects

• WMS_DISPATCHED_TASKS — Parent task via TASK_ID.
• MTL_SYSTEM_ITEMS_B — Item master via INVENTORY_ITEM_ID + ORGANIZATION_ID.
• MTL_TRANSACTION_REASONS — Reason codes via REASON_ID.
• PER_ALL_PEOPLE_F — Operator via PERSON_ID and date-tracked keys.
• MTL_ITEM_LOCATIONS — Location via INVENTORY_LOCATION_ID + ORGANIZATION_ID.
• MTL_SECONDARY_INVENTORIES — Subinventory via SUBINVENTORY_CODE + ORGANIZATION_ID.
• MTL_LOT_NUMBERS and MTL_ITEM_REVISIONS_B — Lot and revision validation.
• MTL_MATERIAL_TRANSACTIONS_TEMP — Pending transaction via TRANSACTION_HEADER_ID.
• MTL_PARAMETERS — Organization context via ORGANIZATION_ID.