Search Results location_source_code




Overview
Explore in AI Chat

Overview

WSH_LOCATIONS_HR_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, released under the WSH (Shipping Execution) product family in versions 12.1.1 and 12.2.2. The view presents a filtered, denormalized projection of shipping-execution location data restricted to records whose location source is Human Resources. It exists primarily to serve reporting, integration, and user-interface enrichment scenarios where a compact, human-readable location identifier is required without exposing the full address structure of the underlying base table.

The view is especially relevant to the ui_short_location_code search term, which corresponds directly to the UI_SHORT_LOCATION_CODE column articulated in the view's SQL definition. Because Oracle EBS shipping screens frequently must display locations in a concise dropdown or LOV format, the concatenation logic embedded in this view provides a convenient server-side representation suitable for external reporting layers or custom concurrent programs.

Underlying Base Objects

According to the ETRM metadata, WSH_LOCATIONS_HR_V references a single underlying object: the WSH_LOCATIONS synonym. The view is defined as a SELECT from WSH_LOCATIONS with an explicit WHERE predicate of LOCATION_SOURCE_CODE = 'HR'. This filter means that only HR-sourced locations are exposed; shipping locations originating from other source codes are excluded from the result set. Because the view is defined over a synonym rather than a physical table name, the reference resolves at runtime to the APPS schema's base table, allowing Oracle's synonym resolution to abstract the physical location.

The view does not perform joins to HR tables; instead, it relies on WSH_LOCATIONS already containing HR-derived rows. This design keeps the view simple and performant, and avoids any schema-crossing dependencies in the SQL text.

Key Columns

  • WSH_LOCATION_ID — Primary identifier for the shipping location record; used as the join key in shipping transactions and deliveries.
  • LOCATION_SOURCE_CODE — Always 'HR' in this view; distinguishes the origin of the location record.
  • SOURCE_LOCATION_ID — Identifier of the location in its source (HR) system.
  • LOCATION_CODE — The raw location code value carried from the source.
  • UI_LOCATION_CODE — A user-interface-oriented location code, typically normalized for display.
  • UI_SHORT_LOCATION_CODE — A concatenation of LOCATION_CODE and either CITY or the first 60 characters of ADDRESS1, separated by a colon. This is the primary column of interest for this search and provides a compact, informative label.
  • ADDRESS1 through ADDRESS4, CITY, STATE, COUNTRY, COUNTY, PROVINCE, POSTAL_CODE — Standard address attributes of the location.
  • INACTIVE_DATE — Date on which the location became inactive; NULL for active locations.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS WHO-column auditing.

Common Use Cases and Queries

Typical applications include shipment location LOVs, shipping label reporting, and integrations that need to resolve a human-readable location label from a WSH_LOCATION_ID. The following queries illustrate standard usage:

  • Retrieve all active HR-sourced locations: SELECT wsh_location_id, ui_short_location_code FROM apps.wsh_locations_hr_v WHERE inactive_date IS NULL;
  • Look up a location by its short code: SELECT wsh_location_id FROM apps.wsh_locations_hr_v WHERE ui_short_location_code = :p_code;
  • Resolve a label for a shipment's source location: SELECT v.ui_short_location_code FROM apps.wsh_locations_hr_v v WHERE v.wsh_location_id = :ship_from_id;
  • Report city and country distribution: SELECT country, city, COUNT(*) FROM apps.wsh_locations_hr_v GROUP BY country, city;

Because the view is a simple filtered projection with no aggregation or joins, it can generally be queried efficiently and combined with delivery or shipping tables in custom reporting extracts.