Results for “source_type_name”

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

Overview

WSH_SOURCE_TYPES_V is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated list of valid source document types that can drive outbound shipping activity, limited to sales order lines. In the Oracle Shipping model, every delivery, delivery detail, and the associated move order or pick release flow must reference a source system and source type so that the application knows where the demand originated. WSH_SOURCE_TYPES_V supplies the "OE" (Order Entry) side of that list, exposing order transaction types that are assignable during shipping and shipping-related setup.

The view is not a base data entry object. It is a read-only, denormalized presentation layer used by forms, list-of-values (LOVs), concurrent programs, and integration interfaces that need to enumerate the order transaction types available as shipping sources. Because the view hard-codes the literal source system value 'OE' and filters out return categories, it represents a deliberately narrowed, shipping-specific slice of the broader order transaction type data maintained in Order Management.

Underlying Base Objects

The documented base object referenced by WSH_SOURCE_TYPES_V is OE_TRXT_TYPES_NOORGS_VL (VIEW). This is the Order Management "transaction types without organizations" view, the value-level (_VL) companion that supplies translated NAME and DESCRIPTION columns. WSH_SOURCE_TYPES_V selects directly from it and applies two filters:

• NVL(ORDER_CATEGORY_CODE, 'ORDER') <> 'RETURN' — excludes return transaction types, defaulting null categories to 'ORDER'.
• TRANSACTION_TYPE_CODE = 'ORDER' — restricts the results to standard order transaction types.

By selecting from the _VL view rather than the base table, the shipping view inherits language-dependent name and description values, so users see transaction type names in their session language. The dependency on OE_TRXT_TYPES_NOORGS_VL means any change to order transaction type setup in Order Management is immediately reflected in shipping LOVs and queries.

Key Columns

The view text defines four columns, mapped from the underlying order transaction type view:

• SOURCE_SYSTEM — a literal 'OE' value identifying the originating application as Order Entry.
• SOURCE_TYPE_NAME — the transaction type NAME from OE_TRXT_TYPES_NOORGS_VL, used as the display value in LOVs.
• DESCRIPTION — the translated DESCRIPTION of the transaction type.
• SOURCE_TYPE_ID — the TRANSACTION_TYPE_ID from the base view, used as the internal key when populating shipping source references.

Common Use Cases and Queries

The view supports shipping setup and integration scenarios requiring the set of order-driven source types. Typical usage includes populating source type LOVs on delivery and shipping transaction forms, validating incoming shipping interface data, and joining to WSH_DELIVERY_ASSIGNMENTS or delivery detail tables to label the origin of shipped lines.

• Listing all order-based source types: SELECT source_system, source_type_name, description, source_type_id FROM wsh_source_types_v ORDER BY source_type_name;
• Resolving a source type name to its ID: SELECT source_type_id FROM wsh_source_types_v WHERE source_type_name = :p_name;
• Joining to shipping data to label delivered lines: SELECT d.delivery_id, s.source_type_name FROM wsh_deliveries d, wsh_source_types_v s WHERE d.source_type_id = s.source_type_id AND s.source_system = 'OE';

In summary, WSH_SOURCE_TYPES_V provides a filtered, language-aware enumeration of order transaction types usable as shipping sources, derived from OE_TRXT_TYPES_NOORGS_VL and scoped to non-return, order-category transaction types.