Search Results source_system




Overview

APPS.WSH_PURGE_SOURCE_TYPES_V is a reporting view in the Oracle E-Business Suite Shipping Execution (WSH) module. It presents a consolidated, user-facing list of the source systems and source document types that can be selected when purging or managing shipping transaction data. The view answers the practical question of which originating documents — purchase order types on one hand, and order management order types on the other — are valid candidates for purge-related processing.

Because the view is defined as a UNION of two independent queries, it normalizes two structurally different sources (Purchasing and Order Management) into a single uniform result set. Each row carries a source system code, a numeric source code, descriptive text for both the source type and the source system, and a localized meaning. This makes the view suitable for LOV (List of Values) population, concurrent program parameter lists, and integration layer lookups where a flat, consistent enumeration of purge sources is required across EBS 12.1.1 and 12.2.2.

The view honors the session language through USERENV('LANG'), so displayed meanings and descriptions respect the runtime localization of the querying session.

Underlying Base Objects

The view is owned by APPS and is documented as referencing three objects:

  • FND_LOOKUP_VALUES (SYNONYM) — the Oracle Application Object Library lookup repository. It supplies the Purchasing branch of the UNION, filtered on lookup_type = 'PO TYPE'.
  • WSH_LOOKUPS (VIEW) — a shipping lookup view that supplies the source system codes and their meanings. It is filtered on lookup_type = 'SOURCE_SYSTEM' and enabled_flag = 'Y'.
  • WSH_ORDER_TYPES_REGULAR_V (VIEW) — supplies the Order Management order types and their descriptions for the OE branch of the UNION.

The first branch is effectively a semi-join keyed to the Purchasing lookup code 'PO'; the second branch is keyed to the shipping lookup code 'OE'. Both branches share the WSH_LOOKUPS source system metadata, which is why the source_system and source_system_meaning columns appear in both halves.

Key Columns

  • source_system — the lookup_code from WSH_LOOKUPS; either 'PO' or 'OE'. This is the discriminator most users search on.
  • source_code — a numeric code. For Purchasing it is derived via DECODE from the PO TYPE lookup (STANDARD maps to 1, BLANKET to 2, default 1). For Order Management it is the order_type_id from WSH_ORDER_TYPES_REGULAR_V.
  • source_type_meaning — for PO, the lookup meaning of the PO TYPE code; for OE, the order_type_name.
  • source_type_desc — the description of the type; for PO the lookup description, for OE the order type description.
  • source_system_meaning — the localized meaning of the source system from WSH_LOOKUPS, such as Purchase Order or Order Entry.

Common Use Cases and Queries

Typical uses include populating source-type selection lists in purge concurrent programs, validating parameters supplied to shipping purge requests, and driving integration mappings that require a canonical list of source system/type pairs.

Enumerate all available purge source types:

SELECT source_system,
       source_code,
       source_type_meaning,
       source_type_desc,
       source_system_meaning
  FROM apps.wsh_purge_source_types_v
 ORDER BY source_system, source_code;

Restrict to Purchase Order sources only:

SELECT source_type_meaning, source_code
  FROM apps.wsh_purge_source_types_v
 WHERE source_system = 'PO';

Look up the numeric source code for a known source system and type:

SELECT source_code
  FROM apps.wsh_purge_source_types_v
 WHERE source_system = 'OE'
   AND source_type_meaning = :p_order_type_name;

Because the view joins localized lookups, results may vary by session language; callers should therefore not hard-code source_type_meaning values for comparisons. Filter on source_system and source_code, which are stable across languages.