Search Results destination_type




Overview
Explore in AI Chat

Overview

APPS.WSH_TRANSIT_TIMES_V is a reporting and integration view within the Oracle E-Business Suite Shipping (WSH) module. It presents a distinct set of origin and destination location, region, and type combinations used to define inter-organization shipping methods and their associated transit times. Rather than exposing raw transactional data, the view delivers a normalized, de-duplicated representation of the location matrix that governs transit time calculations between inventory organizations.

In Oracle EBS 12.1.1 and 12.2.2, transit times are a critical input for planning, order promising, and inter-org transfer scheduling. This view allows reporting tools, custom concurrent programs, and integrations to retrieve valid origin/destination pairings without querying the base shipping method table directly. Because it applies DISTINCT and NVL logic, it simplifies downstream consumption by ensuring each combination appears once and by defaulting null type indicators.

Underlying Base Objects

The view is defined over a single base object, referenced through a synonym:

  • MTL_INTERORG_SHIP_METHODS (accessed via synonym) — the base table storing inter-organization shipping method assignments, including shipping method, from/to locations, and origin/destination type and region information.

The view is a straightforward projection of selected columns from this table, wrapped in a SELECT DISTINCT. It introduces no joins and no aggregations. The NVL functions applied to DESTINATION_TYPE and ORIGIN_TYPE substitute a default value of 'L' (typically indicating a Location-level entry) whenever the underlying column is null. Because the view is owned by APPS and defined on a synonym, it is accessible to any user or responsibility granted the appropriate privileges.

Key Columns

  • FROM_LOCATION_ID — Identifier of the originating inventory location for the shipping method.
  • ORIGIN_TYPE — Classification of the origin, defaulted to 'L' via NVL when null. This column was the specific term searched by the user and distinguishes how the origin is interpreted (for example, location versus region).
  • FROM_REGION_ID — Identifier of the originating region when the origin is defined at a regional level.
  • TO_LOCATION_ID — Identifier of the destination inventory location.
  • DESTINATION_TYPE — Classification of the destination, defaulted to 'L' via NVL when null.
  • TO_REGION_ID — Identifier of the destination region when the destination is defined at a regional level.

Each row therefore represents a unique origin/destination tuple, with type indicators resolved and region columns available to support geographic transit modeling.

Common Use Cases and Queries

Typical scenarios include validating configured inter-org transit lanes, populating planning parameters, and driving integrations that require a list of supported origin/destination pairs. The following example filters on the origin type indicator, directly addressing the "origin_type" search:

SELECT from_location_id, origin_type, from_region_id,
to_location_id, destination_type, to_region_id
FROM apps.wsh_transit_times_v
WHERE origin_type = 'L';

A second common query retrieves all lanes involving a specific region:

SELECT from_location_id, from_region_id, to_location_id, to_region_id
FROM apps.wsh_transit_times_v
WHERE from_region_id = :p_region_id
OR to_region_id = :p_region_id;

Because the view is distinct and free of joins, it performs efficiently for these lookups and is well suited to embedded LOVs, BI Publisher data sets, and custom PL/SQL validation routines operating on inter-organization shipping configurations.