Search Results wsh_purge_source_types_v




Overview
Explore in AI Chat

Overview

The WSH_PURGE_SOURCE_TYPES_V view is a Shipping Execution (WSH) dictionary object owned by the APPS schema. It exposes the set of purge-eligible source systems and their associated source document types, providing a normalized enumeration that the purge engine uses to identify the origin of shipment and delivery data. Rather than hard-coding source references, purge concurrent programs, reports, and integration routines query this view to resolve a source system code (for example PO or OE) into a numeric source code and descriptive attributes.

The view is a UNION of two branches that together cover the two principal order streams supported by Shipping Execution: purchasing documents and sales order documents. Its columns supply both a machine-oriented key (SOURCE_CODE) and a user-facing label (SOURCE_TYPE_MEANING, SOURCE_TYPE_DESC) localized to the session language via USERENV('LANG'). This makes it suitable for LOV definitions, purge parameter validation, and reporting where source context must be rendered consistently. The view exists in both 12.1.1 and 12.2.2 and is reported as VALID in ETRM metadata.

Underlying Base Objects

The view is defined over three referenced objects, each accessed through a synonym or view in the APPS schema:

  • FND_LOOKUP_VALUES (SYNONYM) — the Oracle Application Object Library lookup values table. The first UNION branch filters on LOOKUP_TYPE = 'PO TYPE' and the language setting, restricting to the lookup codes STANDARD and BLANKET.
  • WSH_LOOKUPS (VIEW) — the Shipping Execution lookup view. Both branches use it to resolve source system lookups where LOOKUP_TYPE = 'SOURCE_SYSTEM' and ENABLED_FLAG = 'Y', limited to codes PO and OE respectively.
  • WSH_ORDER_TYPES_REGULAR_V (VIEW) — the regular order types view supplying ORDER_TYPE_ID, ORDER_TYPE_NAME, and DESCRIPTION for the sales order branch.

The two branches are joined by the constant source system context (PO or OE) rather than by a foreign key relationship, so the view behaves as a curated reference list rather than a transactional join.

Key Columns

  • SOURCE_SYSTEM — the lookup code from WSH_LOOKUPS identifying the originating system family; documented values are PO (purchasing) and OE (order entry). This is the column most often matched against a user's source_system search term.
  • SOURCE_CODE — a numeric discriminator. For the PO branch it is a DECODE result mapping STANDARD to 1 and BLANKET to 2 (default 1); for the OE branch it is ORDER_TYPE_ID.
  • SOURCE_TYPE_MEANING — the user-facing type name, derived from FND_LOOKUP_VALUES.MEANING (PO branch) or ORDER_TYPE_NAME (OE branch).
  • SOURCE_TYPE_DESC — the longer description, drawn from FND_LOOKUP_VALUES.DESCRIPTION or ORDER_TYPES_REGULAR_V.DESCRIPTION.
  • SOURCE_SYSTEM_MEANING — the translated meaning of the source system lookup (WSH_LOOKUPS.MEANING).

Common Use Cases and Queries

Typical uses include constraining a purge parameter LOV, labeling purge audit output, and validating source references during integration. A representative query lists all purge source types:

  • SELECT source_system, source_code, source_type_meaning, source_system_meaning FROM wsh_purge_source_types_v ORDER BY source_system, source_code;
  • Filtering to purchasing sources: SELECT * FROM wsh_purge_source_types_v WHERE source_system = 'PO';
  • Resolving a display label for a known code: SELECT source_type_meaning FROM wsh_purge_source_types_v WHERE source_system = 'OE' AND source_code = :order_type_id;
  • Feeding an LOV: SELECT source_system_meaning || ' - ' || source_type_meaning label, source_code FROM wsh_purge_source_types_v;

Because the view filters on enabled lookups and session language, results are inherently restricted to configured, active source systems, which keeps purge processing aligned with shipping setup data.