Search Results wsh_exception_definitions_vl




Overview
Explore in AI Chat

Overview

WSH_EXCEPTION_DEFINITIONS_VL is a language-translated (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the WSH – Shipping Execution product. It presents the set of shipping exception definitions configured in an EBS instance, exposing both the operational attributes of each exception and its language-dependent translated name and description. The view conforms to the standard Oracle EBS MLS (Multi-Language Support) pattern: transactional and setup attributes are held in a base (_B) table, while user-facing text is held in a translation (_TL) table. The VL view joins the two so that a query returns exactly one row per exception definition, resolved to the session's current language.

In the context of reporting and integration, the view is the recommended read-only access point for exception setup data. A user searching for "workflow_process" will find that the WORKFLOW_PROCESS column is exposed here, which explains why this view appears in that search. The view is documented as VALID in both EBS 12.1.1 and 12.2.2, and its structure is unchanged between those releases.

Underlying Base Objects

Per the documented view text, WSH_EXCEPTION_DEFINITIONS_VL is defined over two synonyms referencing the Shipping Execution exception tables:

The join is constrained by B.EXCEPTION_DEFINITION_ID = T.EXCEPTION_DEFINITION_ID AND T.LANGUAGE = USERENV('LANG'), so only the row matching the session language is returned. The view also projects B.ROWID as ROW_ID, which is a vestigial column from the client-side (Forms) era and should not be relied upon for DML. Because the owner is APPS and the underlying objects are accessed through synonyms, the view honors the standard EBS security model; direct grants to the view are typically managed by the product's setup responsibilities rather than granted to end users.

Key Columns

  • EXCEPTION_DEFINITION_ID – primary key of the exception definition; the join key between the _B and _TL tables.
  • EXCEPTION_TYPE – classified type of the exception.
  • DEFAULT_SEVERITY – default severity assigned when the exception is raised.
  • EXCEPTION_HANDLING – indicates how the exception is handled at runtime.
  • WORKFLOW_ITEM_TYPE – the Workflow item type associated with the exception.
  • WORKFLOW_PROCESS – the Workflow process (activity) to be invoked when the exception is raised. This is the column most relevant to searches on "workflow_process".
  • INITIATE_WORKFLOW – flag indicating whether the Workflow is launched automatically when the exception occurs.
  • UPDATE_ALLOWED – whether the exception definition may be modified by users.
  • ENABLED – whether the definition is active.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – flexfield-style descriptive columns for extensibility.
  • EXCEPTION_NAME, DESCRIPTION – translated, language-specific text from the _TL table.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns.

Common Use Cases and Queries

The view is used to report configured shipping exceptions, audit which exceptions trigger Workflow, and drive integrations that need the exception-to-process mapping. Typical statements include:

  • List all enabled exceptions with their severity and handling: SELECT exception_name, exception_type, default_severity, exception_handling FROM wsh_exception_definitions_vl WHERE enabled = 'Y';
  • Find exceptions that automatically launch a Workflow process: SELECT exception_name, workflow_item_type, workflow_process FROM wsh_exception_definitions_vl WHERE initiate_workflow = 'Y';
  • Resolve the Workflow process for a specific exception definition: SELECT workflow_process FROM wsh_exception_definitions_vl WHERE exception_definition_id = :id;
  • Join the view to shipping exception instances or to WF_ITEM_TYPES for integration and reconciliation reporting.

Because the view is MLS-driven, joining it to a non-translated table requires the same language filtering awareness; results depend on USERENV('LANG') and will differ by user session.