Search Results wsh_lookups




Overview

WSH_LOOKUPS is a Shipping Execution (WSH) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, language-aware subset of Oracle Application Object Library (FND) lookup values specifically associated with the Shipping Execution product, whose application identifier is 665. Rather than exposing all lookup codes maintained in the shared FND_LOOKUP_VALUES table, the view restricts output to lookup values owned by the WSH application and scoped to the default security group.

In EBS reporting and integration, WSH_LOOKUPS functions as a convenience access layer. Developers and report authors use it to resolve lookup codes — such as delivery statuses, freight terms, shipping priorities, or document types — into their user-facing meanings without writing the FND_LOOKUP_VALUES filtering logic themselves. Because the view embeds the language environment function USERENV('LANG'), it automatically returns lookup descriptions in the session language, which is important for multi-language deployments.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES, accessed through a synonym. The defining query selects LOOKUP_TYPE, LOOKUP_CODE, MEANING, DESCRIPTION, ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE, applying three predicates:

  • LANGUAGE = USERENV('LANG') — restrains rows to the current runtime language.
  • VIEW_APPLICATION_ID = 665 — limits rows to the Shipping Execution application.
  • SECURITY_GROUP_ID = 0 — restricts to the standard, non-secured lookup set.

Because FND_LOOKUP_VALUES is the central repository for all Oracle EBS lookups, WSH_LOOKUPS is effectively a curated projection of that table. The same underlying data can be reached through FND_LOOKUPS and the FND_LOOKUP_VALUES_VL synonym, but WSH_LOOKUPS narrows the result set so that only WSH-relevant values appear.

Key Columns

  • LOOKUP_TYPE — the lookup category (for example, a WSH shipping status or freight term type).
  • LOOKUP_CODE — the internal code stored on transactional records.
  • MEANING — the display value shown to users, translated by language.
  • DESCRIPTION — optional supplementary text for the code.
  • ENABLED_FLAG — Y/N indicator of whether the value is currently active.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range of the lookup value.

These columns mirror the standard FND lookup structure and support code-to-meaning translation, validity checks, and date-effective filtering.

Common Use Cases and Queries

Typical uses include decoding shipping codes on reports, validating that a code is enabled and within its active date range, and populating value lists in custom concurrent programs or OAF/Forms extensions.

A representative query returning active freight-term lookups is:

  • SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM WSH_LOOKUPS WHERE LOOKUP_TYPE = 'FREIGHT_TERMS' AND ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE);

To join transaction data to its translated meaning:

  • SELECT d.delivery_id, d.status_code, l.meaning FROM wsh_deliveries d, wsh_lookups l WHERE l.lookup_type = 'DELIVERY_STATUS' AND l.lookup_code = d.status_code;

Because the view reads the FND lookup tables at runtime, lookups changed in the application immediately affect query results, and no separate synchronization is required.