Search Results carrier_site_number

Overview

The WSH_CARRIER_SITE_DETAILS_V view is a Shipping Execution (WSH) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the carrier-facing identity of a party site alongside its full postal address, resolved from the Oracle Trading Community Architecture (TCA) registry. Because WSH stores carrier definitions as TCA parties, a carrier's individual pickup, delivery, or billing locations are modeled as party sites. This view denormalizes that relationship so that carrier addresses can be queried without hand-joining the three HZ tables that hold party, site, and location data.

The view is read-only and exposes no DML surface. Its principal role is reporting and integration: it supports freight and shipping reports, carrier reference listings, interface extracts into external transportation management or manifesting systems, and ad hoc address validation. The search term carrier_site_id refers to the view's CARRIER_SITE_ID column, which is the identifier most external systems use to key a specific carrier location. Note that the ETRM column list assigns business names (CARRIER_ID, CARRIER_SITE_ID, CARRIER_SITE_NUMBER, PRIMARY, ACTIVE) to the underlying TCA projection columns (PARTY_ID, PARTY_SITE_ID, PARTY_SITE_NUMBER, IDENTIFYING_ADDRESS_FLAG, STATUS), so the view presents carrier semantics over generic TCA storage.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all consumed through APPS synonyms: HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS. The view text confirms that no WSH-specific table is joined; the carrier context comes entirely from the TCA model. The driver is HZ_PARTIES (“HP”), the registry of all parties including carriers. HZ_PARTY_SITES (“HPS”) provides each site belonging to a party and links to a location via LOCATION_ID. HZ_LOCATIONS (“HL”) supplies the address attributes. Two equi-joins are applied: PARTY_ID between parties and party sites, and LOCATION_ID between party sites and locations. Because the joins are inner, only parties with at least one site and a valid location appear. The view carries no filter restricting rows to carriers specifically, so scoping to carriers requires the caller to constrain on carrier-holding parties independently.

Key Columns

• CARRIER_ID (PARTY_ID) — the TCA party identifier for the carrier organization.
• CARRIER_SITE_ID (PARTY_SITE_ID) — the unique party site identifier for a specific carrier location; the primary key of interest for integrations.
• CARRIER_SITE_NUMBER (PARTY_SITE_NUMBER) — the human-readable site number.
• LOCATION_ID — the address identifier linking the site to HZ_LOCATIONS.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, COUNTY — the unstructured postal address of the site.
• PRIMARY (IDENTIFYING_ADDRESS_FLAG) — flags the identifying/primary address for the site.
• ACTIVE (STATUS) — the site status code, used to exclude inactive carrier sites.

Common Use Cases and Queries

Typical usage includes listing all active locations for a carrier, resolving an address from a carrier site identifier, and extracting carrier site data for downstream systems.

• List sites for a carrier: SELECT carrier_site_id, carrier_site_number, city, state FROM wsh_carrier_site_details_v WHERE carrier_id = :p_carrier_id;
• Resolve one site: SELECT * FROM wsh_carrier_site_details_v WHERE carrier_site_id = :p_carrier_site_id;
• Active-only filter: ... WHERE active = 'A';

Because the view is unrestricted by carrier type, join to the appropriate WSH carrier definition view or table to guarantee that CARRIER_ID corresponds to a genuine carrier before reporting.