Results for “to_location_id”

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

Overview

WSH_TRANSIT_TIMES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the WSH (Shipping Execution) product family. The view exposes the location and region combinations that participate in inter-organization shipping methods, effectively providing a distinct list of origin-to-destination lanes that can be associated with transit time definitions. It does not itself store numeric transit durations; rather, it surfaces the routing dimensions (from/to locations and from/to regions) defined on the underlying shipping method records. Those dimensions are then referenced by shipping execution logic and by downstream transit time setups to determine expected delivery intervals between inventory organizations.

In both release 12.1.1 and 12.2.2 the object is registered in the ETRM as a VIEW with a status of VALID, and its only documented referenced base object is the synonym MTL_INTERORG_SHIP_METHODS. Because it is a reporting and lookup view rather than a transactional entity, it is typically queried by reports, integration extracts, and custom validation logic that need to enumerate valid shipping lanes without duplicating the DISTINCT and NVL logic embedded in the view definition.

Underlying Base Objects

The view is defined with a single documented dependency: the synonym MTL_INTERORG_SHIP_METHODS, which resolves to the base table of the same name in the INV schema. MTL_INTERORG_SHIP_METHODS stores the shipping method assignments used when inventory is transferred between organizations, including the origin and destination location and region identifiers and their associated type codes.

The view text applies two transformations to that base object. First, a DISTINCT clause collapses duplicate lane combinations that arise from multiple shipping method rows sharing the same origin and destination dimensions. Second, NVL is applied to DESTINATION_TYPE and ORIGIN_TYPE so that a NULL type code is presented as 'L', denoting a location-type endpoint. The result is a de-duplicated, normalized lane listing derived entirely from the shipping method table, with no additional joins to location, region, or transit time tables in the documented definition.

Key Columns

• FROM_LOCATION_ID — Identifier of the originating inventory location for the shipping lane.
• ORIGIN_TYPE — Type of the origin endpoint, normalized via NVL so that NULL values are returned as 'L' (location).
• FROM_REGION_ID — Identifier of the originating region, used when the origin is defined at a regional rather than a specific location level.
• TO_LOCATION_ID — Identifier of the destination inventory location.
• DESTINATION_TYPE — Type of the destination endpoint, likewise normalized to 'L' when NULL.
• TO_REGION_ID — Identifier of the destination region for region-level lane definitions.

Together these columns describe a routing lane as a pairing of origin and destination, each of which may be expressed as either a specific location or a broader region depending on the type code recorded on the shipping method.

Common Use Cases and Queries

The view is most often used to enumerate valid inter-organization shipping lanes for a given organization pair, to drive carrier and transit time lookups, or to feed extracts that populate external transportation planning systems. A typical query lists all lanes terminating at a specific destination location:

• SELECT from_location_id, origin_type, to_location_id, destination_type FROM wsh_transit_times_v WHERE to_location_id = :p_to_location;
• SELECT from_region_id, to_region_id FROM wsh_transit_times_v WHERE origin_type = 'L' AND destination_type = 'L';
• SELECT DISTINCT from_location_id, to_location_id FROM wsh_transit_times_v ORDER BY from_location_id, to_location_id;

Because the view returns no transit duration, consumers join it to shipping method or transit time setup tables, or apply their own lead-time calculation. Queries should account for the fact that either endpoint may be region-based, so filtering solely on location identifiers can omit region-defined lanes. As with all APPS-owned reporting views, direct DML against this object is not supported; it is intended strictly for read access.