Search Results ui_location_code




Overview
Explore in AI Chat

Overview

WSHFV_LOCATIONS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Shipping Execution (WSH) module. It is a public, customer-facing view designed to expose location information used by the shipping and logistics functions of EBS. The view presents shipping location records in a flattened, denormalized form that simplifies reporting and integration against the underlying transactional table. Because the view is created WITH READ ONLY, it cannot be used to insert, update, or delete records; it is intended strictly for query and extraction purposes.

This view is available across Oracle EBS 12.1.1 and 12.2.2, where the Shipping Execution product provides warehouse, carrier, and shipment-related location data. The "FV" naming convention typically denotes a "flexfield validation" or "formatted value" view used to surface descriptive attributes for flexfields and reporting. The presence of the USER-defined column UI_LOCATION_CODE, which the user searched for, indicates that the view reuses that column (aliased three times) to populate descriptive and code-based attributes such as LOCATION_CODE, LOCATION_DESCRIPTION, and SOURCE_LOCATION_DESCRIPTION.

Underlying Base Objects

According to the documented metadata, WSHFV_LOCATIONS is defined directly over the base synonym WSH_LOCATIONS (owner APPS). The view text confirms this: it selects from WSH_LOCATIONS and applies column aliasing and reordering. No joins, aggregations, or additional tables are present in the definition, meaning the view is a straightforward projection of the base shipping location entity.

The base table WSH_LOCATIONS stores location records referenced throughout the shipping execution flow, including ship-from, ship-to, carrier, and delivery destinations. Because the view references the underlying synonym without filtering or transformation logic, any row visible in WSH_LOCATIONS is eligible to appear in WSHFV_LOCATIONS, subject to the querying user's data access privileges and any Row-Level Security (RLS) or organization access controls applied through the Shipping Execution security model.

Key Columns

The view exposes the following significant columns:

  • WSH_LOCATION_ID — Primary surrogate key uniquely identifying each shipping location record.
  • LOCATION_SOURCE_CODE — Indicates the origin or source system of the location record (for example, how the location was created or derived).
  • LOCATION_CODE, LOCATION_DESCRIPTION, and UI_LOCATION_CODE — These three columns are all derived from the underlying UI_LOCATION_CODE attribute. UI_LOCATION_CODE represents the user-interface location code (a user-visible identifier), while LOCATION_CODE and LOCATION_DESCRIPTION surface aliased copies for reporting convenience.
  • SOURCE_LOCATION_ID and SOURCE_LOCATION_DESCRIPTION — Identify and describe the originating source location, again with SOURCE_LOCATION_DESCRIPTION aliased from UI_LOCATION_CODE.
  • Address columns — ADDRESS1 through ADDRESS4, CITY, STATE, COUNTY, COUNTRY, PROVINCE, and POSTAL_CODE provide the complete physical address of the location.
  • INACTIVE_DATE — Marks when a location was deactivated, enabling filtering of active versus inactive records.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN support change tracking and audit reporting.

Common Use Cases and Queries

WSHFV_LOCATIONS is commonly used to build shipping location reports, validate location codes during integration, and populate address data for carrier interfaces. A typical query to retrieve all active locations is:

SELECT wsh_location_id, ui_location_code, location_description, city, state, country FROM wshfv_locations WHERE inactive_date IS NULL;

To resolve a specific location by its user-interface code, the following pattern applies:

SELECT wsh_location_id, location_code, address1, address2, city, postal_code FROM wshfv_locations WHERE ui_location_code = 'WAREHOUSE_01';

Because the view is read-only, it should be used exclusively for extraction and reporting, with any data maintenance performed against the base WSH_LOCATIONS table through supported EBS APIs or forms.