Results for “ui_short_location_code”

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

Overview

WSH_SHIP_TO_LOCATIONS_V is an Oracle E-Business Suite seeded view owned by the APPS schema and classified under the WSH - Shipping Execution product. In both Release 12.1.1 and 12.2.2 it is documented as VALID. The view exposes valid "ship-to" customer locations in a form suitable for Shipping Execution and downstream reporting or integration. It is not a base table; it is a denormalized projection that joins WSH_LOCATIONS to the Oracle Trading Community Architecture (TCA) customer model, primarily HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and HZ_PARTY_SITES. Its purpose is to translate between the WSH internal location identifiers and the TCA customer site hierarchy, returning a small, stable set of identifiers used wherever Shipping needs to identify a receiving location. Because the view filters on active status and the SHIP_TO site-use code, it is the correct source for any report or interface that must only surface currently usable ship-to destinations rather than all addresses on file.

Underlying Base Objects

The documented base objects are HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, and WSH_LOCATIONS, all referenced through APPS synonyms. The join path follows the standard TCA model: a customer account (HZ_CUST_ACCOUNTS, STATUS = 'A') owns one or more account sites (HZ_CUST_ACCT_SITES_ALL, STATUS = 'A'), each of which may carry one or more site uses (HZ_CUST_SITE_USES_ALL, STATUS = 'A', SITE_USE_CODE = 'SHIP_TO'). Party records (HZ_PARTIES, HZ_PARTY_SITES) tie the account and site to the party and its location. That location is then linked to WSH_LOCATIONS via HPS.LOCATION_ID = WHZL.SOURCE_LOCATION_ID, with WHZL.LOCATION_SOURCE_CODE restricted to 'HZ'. The org_id is matched with NVL(..., -999) on both the site use and account site, which prevents null org contexts from being silently dropped. The GROUP BY over WSH_LOCATION_ID, UI_LOCATION_CODE, and the concatenated short code collapses duplicate rows produced by multiple matching site-use rows.

Key Columns

• WSH_LOCATION_ID — Surrogate identifier from WSH_LOCATIONS; the primary key used to reference the location within Shipping Execution and related WSH tables.
• UI_LOCATION_CODE — The user-facing location code drawn from WSH_LOCATIONS; this is the value displayed in Shipping forms and typically used in interfaces and pick lists.
• UI_SHORT_LOCATION_CODE — A derived short display string formed as LOCATION_CODE concatenated with a colon and either the CITY or, when CITY is null, the first 60 bytes of ADDRESS1 via SUBSTRB. Useful for compact list-of-values displays and reports where space is constrained.

The projection is deliberately narrow; there is no customer name, address detail, or org column exposed, so consumers needing those attributes must join back to TCA or WSH_LOCATIONS explicitly.

Common Use Cases and Queries

The view is typically used to populate ship-to list-of-values, to validate a location before writing to shipping interface tables, or to reconcile WSH locations against TCA ship-to sites. A representative query returns locations for a given customer account:

• SELECT v.wsh_location_id, v.ui_location_code, v.ui_short_location_code FROM apps.wsh_ship_to_locations_v v ORDER BY v.ui_location_code;
• SELECT COUNT(*) FROM apps.wsh_ship_to_locations_v; — used to confirm the volume of active ship-to locations.
• Joining to WSH_LOCATIONS on WSH_LOCATION_ID to retrieve additional address attributes not exposed by the view.

Because the view enforces STATUS = 'A' on the account, account site, and site use, it automatically excludes inactive or end-dated ship-to sites, making it safe for operational interfaces. For integration, it is commonly queried to resolve a user-entered location code into the numeric WSH_LOCATION_ID required by Shipping Execution APIs and open interface staging tables.