Results for “discrepancy_type”

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

Overview

The WMS_SKIP_TASK_EXCEPTIONS table in the WMS (Warehouse Management) schema of Oracle E-Business Suite stores exception records generated when a warehouse operator elects to skip an assigned warehouse execution task. It captures the operational context of the skip — who performed it, which task and item were involved, the reason for skipping, and the resulting transaction association — providing an audit trail and enabling downstream reconciliation, discrepancy analysis, and productivity reporting.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as a link. This classification is a modeling suggestion derived from its dense foreign-key structure: the table does not simply describe a single business entity, but rather associates multiple hubs (task, item, person, reason, location) around a discrete execution event. Each row represents an intersection of these participating entities at the point of task skipping.

Key Information Stored

The table contains 37 documented columns in the 12.2.2 physical schema. The unique index WMS_SKIP_TASK_EXCEPTIONS_U1 spans (TASK_ID, SEQUENCE_NUMBER, WMS_TASK_TYPE), forming the business-key candidate that uniquely identifies each skip exception. There is no separately documented surrogate primary key.

• TASK_ID — Foreign key to WMS_DISPATCHED_TASKS; the warehouse task that was skipped.
• SEQUENCE_NUMBER — Ordinal distinguishing multiple exceptions recorded against the same task.
• WMS_TASK_TYPE — The category of the affected task; combined with the above two, forms the unique key.
• ORGANIZATION_ID — Warehouse/inventory organization context (FK to MTL_PARAMETERS).
• INVENTORY_ITEM_ID — The item being handled at the time of the skip.
• PERSON_ID — The operator or user who skipped the task (FK to PER_ALL_PEOPLE_F, effective-dated).
• REASON_ID — User-supplied reason for the skip (FK to MTL_TRANSACTION_REASONS).
• DISCREPANCY_TYPE — Categorization of the underlying discrepancy.
• INVENTORY_LOCATION_ID, SUBINVENTORY_CODE — Physical location context (FKs to MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES).
• LOT_NUMBER, REVISION — Lot and revision detail (FKs to MTL_LOT_NUMBERS and MTL_ITEM_REVISIONS_B).
• TRANSACTION_HEADER_ID — Links the exception to a pending transaction in MTL_MATERIAL_TRANSACTIONS_TEMP.
• ARCHIVE_FLAG — Indicates whether the record has been archived.
• Attribute1–Attribute15 and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — descriptive flexfield and audit fields.

Common Use Cases and Queries

The primary operational uses are auditing skipped tasks, analyzing skip reasons for process improvement, resolving inventory discrepancies, and troubleshooting missing or stuck transactions.

A typical query retrieves skip exceptions with their reason and operator, joined to the reasons table:

SELECT e.task_id, e.sequence_number, e.wms_task_type,
       e.inventory_item_id, e.person_id, r.reason_name
FROM   wms.wms_skip_task_exceptions e,
       mtl_transaction_reasons r
WHERE  e.reason_id = r.reason_id
  AND  e.organization_id = :org_id;

Discrepancy trending groups skips by reason and item to expose recurring warehouse issues. Reconciliation reports join ARCHIVE_FLAG and TRANSACTION_HEADER_ID against MTL_MATERIAL_TRANSACTIONS_TEMP to verify whether skipped tasks produced pending transactions. Because the table forms the basis of both audit and productivity measurements, queries filtering on PERSON_ID and CREATION_DATE support operator-level analysis.

Related Objects

Ten foreign keys connect this table to surrounding WMS/inventory entities:

• WMS_DISPATCHED_TASKS — joined on TASK_ID; the skipped task itself.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item attributes.
• MTL_LOT_NUMBERS and MTL_ITEM_REVISIONS_B — joined on item/lot/revision for lot-controlled and revision-controlled items.
• MTL_TRANSACTION_REASONS — joined on REASON_ID for reason descriptions.
• PER_ALL_PEOPLE_F — joined on PERSON_ID with effective dates for operator identity.
• MTL_MATERIAL_TRANSACTIONS_TEMP — joined on TRANSACTION_HEADER_ID for pending transaction data.
• MTL_SECONDARY_INVENTORIES, MTL_ITEM_LOCATIONS, and MTL_PARAMETERS — joined on ORGANIZATION_ID plus subinventory/location for physical context.

These relationships confirm the table's role as an event link anchoring WMS execution exceptions to core inventory and HR master data.