Search Results location_source_code




Overview
Explore in AI Chat

Overview

APPS.WSH_LOCATIONS_HR_V is a filtered view over the WSH_LOCATIONS table, one of the core location definition tables in the Oracle Warehouse Management and Shipping Execution (WSH) module. The view exposes only those location records whose LOCATION_SOURCE_CODE equals 'HR', meaning the underlying record was created or synchronized from Oracle Human Resources (HR) rather than being defined natively within WSH. Its primary purpose is to isolate HR-sourced inventory and shipping locations so that reports, integrations, and validation logic can query a stable, pre-filtered data set without repeatedly coding the source filter.

In Oracle EBS 12.1.1 and 12.2.2, WSH relies on WSH_LOCATIONS as a central registry of physical locations used during pick, pack, ship, and delivery transactions. When HR is configured as the source of truth for organizational locations, records flow into WSH_LOCATIONS with LOCATION_SOURCE_CODE = 'HR'. This view provides the canonical read interface for those records, and it is frequently referenced by shipping and warehouse reporting queries, customer-facing location lookups, and integration extracts where HR-maintained locations are required.

Underlying Base Objects

The documented metadata identifies a single referenced base object:

  • WSH_LOCATIONS (accessed via a SYNONYM owned by APPS) — the physical table that stores all WSH location records regardless of origin.

The view is defined with a restricting predicate: WHERE location_source_code = 'HR'. Consequently, every row returned by WSH_LOCATIONS_HR_V corresponds to exactly one row in WSH_LOCATIONS with that source code. No joins, aggregations, or unions are present in the view definition, so it behaves as a simple projection of selected columns plus the source-code filter. Because the view is a thin wrapper, it inherits the partitioning, indexing, and security characteristics of WSH_LOCATIONS and is always current with its base table.

Key Columns

  • WSH_LOCATION_ID — Primary key of the WSH location record; the identifier used by downstream shipping and warehouse transactions.
  • LOCATION_SOURCE_CODE — Always 'HR' in this view; indicates the record originated from Human Resources.
  • SOURCE_LOCATION_ID — The identifier of the originating record in the HR source system; useful for reconciliation between HR and WSH.
  • LOCATION_CODE — The business-facing location code used on forms and reports.
  • UI_LOCATION_CODE — User-interface rendering of the location code.
  • UI_SHORT_LOCATION_CODE — A concatenation of LOCATION_CODE and either CITY or the first 60 bytes of ADDRESS1, formatted as location_code:city_or_address. This is used for compact display in list-of-values and poplists.
  • ADDRESS1 through ADDRESS4, CITY, STATE, COUNTRY, COUNTY, PROVINCE, POSTAL_CODE — The full address structure associated with the location.
  • INACTIVE_DATE — Date the location was deactivated; null indicates an active location.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns.

Common Use Cases and Queries

Typical scenarios include validating HR-sourced ship-to locations during order entry, populating shipping documents with address details, and extracting address data for downstream integrations. A common reporting query lists active HR locations with their addresses:

  • SELECT wsh_location_id, location_code, city, state, postal_code FROM apps.wsh_locations_hr_v WHERE inactive_date IS NULL ORDER BY location_code;
  • SELECT location_code, ui_short_location_code FROM apps.wsh_locations_hr_v WHERE ui_short_location_code LIKE :search_term;
  • SELECT source_location_id, wsh_location_id FROM apps.wsh_locations_hr_v ORDER BY source_location_id;

Because the view is pre-filtered to location_source_code = 'HR', queries against it cannot return non-HR locations, which simplifies LOV definitions and integration extracts that must be restricted to HR-maintained data.