Search Results source_location_description

Overview

APPS.WSHFV_LOCATIONS is a read-only reporting view in Oracle E-Business Suite (documented in the ETRM for both 12.1.1 and 12.2.2) that exposes the location records used throughout the Oracle Shipping (WSH) module. Its defining characteristic is the prominent role played by the column ui_location_code: the view definition derives the descriptive columns LOCATION_DESCRIPTION and SOURCE_LOCATION_DESCRIPTION by aliasing UI_LOCATION_CODE under those names, and it also re-selects UI_LOCATION_CODE as a standalone column. This makes the view a convenient reporting interface for users who search on "ui_location_code" and expect a human-readable location identifier to appear wherever a location is referenced.

The "FV" mnemonic in the view name follows the Oracle convention for a formatted value view, indicating that the object exists primarily for query and integration convenience rather than for data maintenance. Because it is defined WITH READ ONLY, no DML may be performed against it; all maintenance occurs in the underlying table.

Underlying Base Objects

The view is owned by the APPS schema and is defined entirely over a single referenced base object, WSH_LOCATIONS, which the ETRM documents as a synonym. The complete view text is a projection — not a join — selecting the following columns from WSH_LOCATIONS:

• WSH_LOCATION_ID, LOCATION_SOURCE_CODE, LOCATION_CODE, SOURCE_LOCATION_ID
• UI_LOCATION_CODE (selected three times: twice aliased and once under its own name)
• ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, STATE, COUNTY, COUNTRY, PROVINCE, POSTAL_CODE
• Audit and status columns: INACTIVE_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN

The absence of any join or filter means the view returns every row of the synonym and preserves the one-to-one relationship with WSH_LOCATIONS; row counts and primary key values match exactly.

Key Columns

• WSH_LOCATION_ID — Primary surrogate key for the shipping location; the standard foreign key value used by other WSH entities.
• UI_LOCATION_CODE — The user-interface-facing location identifier. Because the view maps it into both description columns, it is the most heavily referenced column in reporting.
• LOCATION_DESCRIPTION — Alias of UI_LOCATION_CODE; supplies the descriptive text expected by forms, reports, and interfaces.
• SOURCE_LOCATION_DESCRIPTION — Also an alias of UI_LOCATION_CODE, associated with SOURCE_LOCATION_ID for source-location lookups.
• LOCATION_CODE / LOCATION_SOURCE_CODE — The internal code and the code identifying the origin of the location record.
• INACTIVE_DATE — Effective end date; rows with a populated value should generally be excluded from active-location queries.
• Address columns — Provide the full postal address for the location.

Common Use Cases and Queries

Typical uses include shipping reports, label and document generation, inventory-to-shipment reconciliation, and inbound interface validation where a readable location description is required. A simple lookup by identifier:

• SELECT wsh_location_id, ui_location_code, location_description FROM apps.wshfv_locations WHERE ui_location_code LIKE :p_code;

An active-location list for a report parameter:

• SELECT wsh_location_id, location_description FROM apps.wshfv_locations WHERE inactive_date IS NULL ORDER BY location_description;

A source-location resolution used when tracing shipping sources:

• SELECT wsh_location_id, source_location_id, source_location_description FROM apps.wshfv_locations WHERE location_source_code = :p_source;

Because the view is read-only and unfiltered, it can be used safely in concurrent programs and BI Publisher data templates without risk of write-back to the shipping location data.