Search Results wsh_exception_definitions_b




Overview
Explore in AI Chat

Overview

WSH_EXCEPTION_DEFINITIONS_B is the base (language-independent) definition table for exception definitions within the Oracle E-Business Suite Shipping Execution (WSH) module. It stores the master record for every shipping exception that the system can raise, track, and manage — such as delivery holds, pick confirmations issues, or shipment discrepancies. Each row defines a reusable exception "template" that shipping operations reference when generating runtime exceptions. The table is the foundation of the exception framework in WSH, controlling severity, handling behavior, and workflow integration.

In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the WSH schema and carries 31 documented columns, including the standard audit columns and a set of flexible attribute (descriptive flexfield) columns. Its heuristic Data Vault classification is hub-leaning, which suggests it functions primarily as a business-key hub: the stable identifier (EXCEPTION_DEFINITION_ID) anchors relationships, while descriptive properties and translations attach through satellite and translation tables. The presence of the ZD_EDITION_NAME column reflects the editioning framework introduced in 12.2.x for online patching.

Key Information Stored

The primary key is WSH_EXCEPTION_DEFINITIONS_B_PK, defined on EXCEPTION_DEFINITION_ID, a surrogate system-generated identifier. A unique business-key candidate is captured by WSH_EXCEPTION_DEFINITIONS_B_U1 (EXCEPTION_DEFINITION_ID, ZD_EDITION_NAME), which supports the editioning model used in multi-tenant patching.

Common Use Cases and Queries

This table is queried when configuring or auditing shipping exception rules, and when joining to the translation table to retrieve user-facing names and descriptions. Reporting scenarios include identifying enabled exceptions, reviewing workflow-enabled exceptions, and validating flexfield usage. Typical SQL:

  • List enabled exception definitions: SELECT EXCEPTION_DEFINITION_ID, EXCEPTION_TYPE, DEFAULT_SEVERITY FROM WSH.WSH_EXCEPTION_DEFINITIONS_B WHERE ENABLED = 'Y';
  • Find workflow-driven exceptions: SELECT EXCEPTION_DEFINITION_ID, WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS FROM WSH.WSH_EXCEPTION_DEFINITIONS_B WHERE INITIATE_WORKFLOW = 'Y';
  • Join to translations: SELECT B.EXCEPTION_DEFINITION_ID, T.NAME FROM WSH.WSH_EXCEPTION_DEFINITIONS_B B, WSH.WSH_EXCEPTION_DEFINITIONS_TL T WHERE B.EXCEPTION_DEFINITION_ID = T.EXCEPTION_DEFINITION_ID;

Related Objects

The most significant related object is the translation table, joined through the documented foreign key:

  • WSH_EXCEPTION_DEFINITIONS_TL — holds the language-specific name and description; joined on EXCEPTION_DEFINITION_ID.
  • Runtime shipping exception tables in the WSH schema that reference definitions when exceptions are raised against deliveries, trips, and containers (joined via EXCEPTION_DEFINITION_ID).
  • Oracle Workflow object (WF_ITEM_TYPES) referenced through WORKFLOW_ITEM_TYPE.
  • Shipping Execution setup and query views built over WSH_EXCEPTION_DEFINITIONS_B for the Shipping Transactions and exception inquiry forms.