Search Results carrier_site_number

Overview

The view APPS.WSH_CARRIER_SITE_DETAILS_V presents carrier site information, combining carrier identifiers with the physical address details of each carrier site. In Oracle EBS 12.1.1 and 12.2.2 it is owned by the APPS schema and is registered in FND Design Data as WSH.WSH_CARRIER_SITE_DETAILS_V. Its status is VALID, and it is classified as an internal view intended for use by standard Oracle Applications programs rather than direct customer access. The view serves as a reporting and integration convenience layer over carrier, party, and location data, exposing site-level attributes — most notably the CARRIER_SITE_NUMBER, the field users typically search for when looking up carrier site records.

Within the Shipping Execution (WSH) module, carrier sites define the pickup and drop-off locations associated with a carrier. Rather than requiring report authors and integration developers to join carrier, party, and location tables manually, this view returns the association in a single, denormalized result set suitable for concurrent programs, lookups, and outbound interfaces.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced as synonyms resolving to the corresponding HZ (Trading Community Architecture) tables:

• HZ_LOCATIONS — Supplies the physical address attributes such as ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, and COUNTY.
• HZ_PARTIES — Provides the carrier party context that links a site to its owning party record.
• HZ_PARTY_SITES — The intersection entity that associates a party with a location and carries the site-level attributes, including the site number and primary/active indicators.

The view is not referenced by any other database object, confirming it functions as a terminal reporting object rather than a building block for further views. Because the underlying address data resides in TCA tables, any change to a carrier site address in the TCA model is reflected immediately through this view without additional synchronization.

Key Columns

• CARRIER_ID (NUMBER) — Identifier of the carrier to which the site belongs.
• CARRIER_SITE_ID (NUMBER) — Primary key identifying the specific carrier site record.
• CARRIER_SITE_NUMBER (VARCHAR2(30)) — The user-visible site number; the primary search key for locating a site.
• LOCATION_ID (NUMBER) — Foreign key to HZ_LOCATIONS, linking the site to its address record.
• ADDRESS1–ADDRESS4 (VARCHAR2(240)) — Free-form address lines of the site location.
• CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, COUNTY (VARCHAR2) — Geographic attributes of the address.
• PRIMARY (VARCHAR2) — Flag indicating whether the site is the primary site for the carrier.
• ACTIVE (VARCHAR2) — Flag indicating whether the site is currently active and available for use.

Common Use Cases and Queries

Typical usage includes validating carrier site setup, populating shipping documents and carrier labels with pickup addresses, and extracting site data for integration with external transportation systems. A common starting point is a lookup by site number:

• SELECT carrier_id, carrier_site_id, carrier_site_number, city, state, country FROM apps.wsh_carrier_site_details_v WHERE carrier_site_number = :p_site_number;
• SELECT carrier_id, carrier_site_number, address1, city, postal_code FROM apps.wsh_carrier_site_details_v WHERE carrier_id = :p_carrier_id AND active = 'Y';
• SELECT carrier_site_number, city, country, primary FROM apps.wsh_carrier_site_details_v WHERE primary = 'Y';

Because the object is marked Oracle Internal Use Only, direct SQL access should be limited to diagnostic and reporting purposes, with preference given to supported APIs wherever transactional integrity is required.