Results for “wsh_exception_definitions_v”

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

Overview

WSH_EXCEPTION_DEFINITIONS_V is an APPS-owned reporting view within the Oracle E-Business Suite Shipping Execution (WSH) product. It presents the seeded and user-defined shipping exception definitions that drive exception handling during picking, packing, shipping, and delivery confirmation. In EBS 12.1.1 and 12.2.2 the view is documented as VALID in the ETRM and is exposed through the APPS schema, making it the primary read-only interface for exception metadata used by reports, integrations, and diagnostic queries.

The view is significant because it resolves the two coded foreign keys on the exception definition — the exception category and its default severity — into their translatable display meanings. This denormalization means consumers do not need to join FND_LOOKUP_VALUES_VL themselves, and lookups are always resolved to the appropriate language for the session. Because the base exception definitions table is a _VL (translated) table, the view returns the translated EXCEPTION_NAME and DESCRIPTION as well.

Underlying Base Objects

The view text defines it over three objects:

• WSH_EXCEPTION_DEFINITIONS_VL — aliased A; the translated base view holding the exception definition rows (identity, name, description, type, severity, handling, workflow attributes, DFF attributes, and Who columns).
• FND_LOOKUP_VALUES_VL — aliased B; joined on A.EXCEPTION_TYPE = B.LOOKUP_CODE with B.LOOKUP_TYPE = 'EXCEPTION_TYPE', supplying the EXCEPTION_TYPE_M meaning.
• FND_LOOKUP_VALUES_VL — aliased C; joined on A.DEFAULT_SEVERITY = C.LOOKUP_CODE with C.LOOKUP_TYPE = 'EXCEPTION_BEHAVIOR', supplying the DEFAULT_SEVERITY_M meaning.

Both joins are effectively mandatory equijoins, so any exception definition whose type or severity has no matching active lookup value in the lookup view will be filtered out of the result set. Organizations that extend the lookup sets must therefore keep 'EXCEPTION_TYPE' and 'EXCEPTION_BEHAVIOR' lookup values synchronized with the definitions they maintain.

Key Columns

• ROW_ID — internal unique row identifier.
• EXCEPTION_DEFINITION_ID — primary surrogate key of the exception definition.
• EXCEPTION_NAME / DESCRIPTION — translated name and free-text description of the exception.
• EXCEPTION_TYPE / EXCEPTION_TYPE_M — the lookup code for the exception category and its translated meaning (from lookup type 'EXCEPTION_TYPE').
• DEFAULT_SEVERITY / DEFAULT_SEVERITY_M — the severity lookup code and its translated meaning (from lookup type 'EXCEPTION_BEHAVIOR').
• EXCEPTION_HANDLING — indicates how the exception is processed.
• WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS, INITIATE_WORKFLOW — the workflow item type, process, and flag that govern whether a workflow is launched when the exception occurs.
• UPDATE_ALLOWED, ENABLED — flags controlling whether the definition may be modified and whether it is active.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns available for customer extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who audit columns.

Common Use Cases and Queries

Typical uses include validating that exception definitions are enabled before a shipping integration raises them, auditing which definitions trigger workflow, and building picklists keyed on exception type or severity. The following query lists enabled exceptions with their meanings:

SELECT exception_definition_id, exception_name, exception_type_m, default_severity_m, exception_handling
FROM apps.wsh_exception_definitions_v
WHERE enabled_flag = 'Y'
ORDER BY exception_type_m, exception_name;

A second scenario resolves the workflow configuration for exceptions that launch a process:

SELECT exception_name, exception_type_m, workflow_item_type, workflow_process
FROM apps.wsh_exception_definitions_v
WHERE initiate_workflow = 'Y';

For troubleshooting, querying by EXCEPTION_TYPE isolates all definitions belonging to a category, while selecting the ATTRIBUTE columns supports reports that rely on flexfield-captured configuration data. Because the view already contains translated meanings, it is well suited to multi-language reporting and to integration feeds that populate external exception-monitoring dashboards.