Search Results wsh_exception_definitions_tl




Overview
Explore in AI Chat

Overview

WSH.WSH_EXCEPTION_DEFINITIONS_TL is the translation (TL) table for shipping exception definitions in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the language-specific, user-facing text associated with each exception definition created in the Shipping Execution module, which is used to flag shipment, delivery, trip, and pick-release conditions that require attention. The _TL suffix identifies this as the multi-language companion to the base table WSH_EXCEPTION_DEFINITIONS_B, which holds language-independent attributes.

The table is owned by the WSH schema, is documented as VALID in ETRM, and exposes eleven physical columns. It is the object of interest for developers and DBAs who need translated exception names and descriptions for reporting, alerts, and user-interface display across installed languages.

From a data-modeling perspective, ETRM heuristic analysis classifies this object as satellite-leaning. In Data Vault terms, it behaves as a satellite attached to the exception-definition hub (identified by EXCEPTION_DEFINITION_ID), with the language dimension supplying additional descriptive context rather than independent identity.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • EXCEPTION_DEFINITION_ID — Surrogate foreign key to WSH_EXCEPTION_DEFINITIONS_B; the core identity of each exception definition. It is not unique on its own in the TL table.
  • LANGUAGE — Language code of the translation row (for example, US). Combined with the ID, it provides translation uniqueness.
  • SOURCE_LANG — Source language from which the translation was derived.
  • EXCEPTION_NAME — The translated, user-visible name of the shipping exception.
  • DESCRIPTION — The translated narrative describing when the exception applies.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.
  • Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — capture who created and last modified each row and when.

The unique index WSH_EXCEPTION_DEFINITIONS_TL_U spans (EXCEPTION_DEFINITION_ID, LANGUAGE, ZD_EDITION_NAME), confirming that combination as the business-key candidate for this table.

Common Use Cases and Queries

Typical usage centers on resolving exception codes into meaningful, localized text for operational and analytical deliverables.

  • Reporting exception volumes by translated name, joining the TL and B tables and filtering by language.
  • Populating shipping exception alerts and dashboard prompts with the correct language-specific description.
  • Verifying translation completeness — identifying definitions in the base table that lack rows for a given LANGUAGE.

A representative query:

SELECT b.exception_definition_id, t.exception_name, t.description
FROM wsh_exception_definitions_b b,
wsh_exception_definitions_tl t
WHERE b.exception_definition_id = t.exception_definition_id
AND t.language = USERENV('LANG')
AND t.zd_edition_name = 'SET1';

Related Objects

  • WSH_EXCEPTION_DEFINITIONS_B — Base table joined on EXCEPTION_DEFINITION_ID; the FK relationship is the primary dependency.
  • WSH_EXCEPTION_DEFINITIONS_TL_U — Unique index enforcing the business key.
  • FND_LANGUAGES — Reference table validating the LANGUAGE and SOURCE_LANG values.
  • FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Context for the installed WSH language set.
  • WSH_EXCEPTIONS (runtime exception instances) — Indirectly consumed when resolving raised exceptions to display text.

Because translations in EBS are maintained through the multilingual (MLS) framework, direct DML against this table is not advised; changes should flow through the Shipping Execution setup or application translation utilities.