Search Results wsh_carriers




Overview
Explore in AI Chat

Overview

WSH_CARRIERS is the master reference table for shipping carrier information within the Oracle E-Business Suite Shipping Execution (WSH) module. Every carrier record that Oracle Shipping Execution, Oracle Transportation Management integrations, freight rating, manifesting, and delivery planning logic consumes originates from this table. The object resides in the WSH schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2, carrying 70 physical columns in the 12.2.2 schema.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. WSH_CARRIERS holds a single foreign key to HZ_PARTIES through CARRIER_ID, which means it does not originate its own identity independently of the Trading Community Architecture party model; instead it extends and qualifies a party record with carrier-specific operational attributes. Analysts should treat WSH_CARRIERS as an extension of the party hub, not as a standalone hub entity.

Key Information Stored

The table is keyed on CARRIER_ID, which is both the surrogate primary key and the unique index WSH_CARRIERS_U1. This column doubles as the foreign key to HZ_PARTIES.CARRIER_ID (in practice, the party identifier of the carrier organization). A second unique index, WSH_CARRIERS_U2, is defined on FREIGHT_CODE, making it the primary business-key candidate used by downstream applications when carriers are referenced by user-facing code rather than by internal ID.

Common Use Cases and Queries

Typical usage centers on carrier lookup by code, carrier eligibility for manifesting, and join-back to the party for names and addresses. A frequent reporting pattern resolves carrier identity across the TCA boundary:

SELECT c.carrier_id, c.freight_code, c.scac_code, p.party_name
FROM wsh_carriers c, hz_parties p
WHERE c.carrier_id = p.party_id
AND c.manifesting_enabled_flag = 'Y';

Freight settlement teams join WSH_CARRIERS to AP supplier tables via SUPPLIER_ID and SUPPLIER_SITE_ID to reconcile freight invoices against carrier records. Transportation planners filter on the MAX_* constraint columns to determine which carriers can legally or contractually service a given route. Analysts building freight cost models frequently aggregate by FREIGHT_CODE and CURRENCY_CODE. The DIM_* dimensional columns support dimensional weight calculation for parcel and LTL rating scenarios.

Related Objects

The documented foreign-key relationship establishes HZ_PARTIES as the master party reference, joined on CARRIER_ID (WSH_CARRIERS.CARRIER_ID → HZ_PARTIES). Beyond this explicit FK, WSH_CARRIERS is referenced heavily by shipping execution transactional and setup objects. Delivery and trip planning tables in the WSH schema (such as delivery and trip records) resolve carrier identity through CARRIER_ID. Freight cost and rate objects consume FREIGHT_CODE and the rating attributes. Payables supplier records (AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL) are reached indirectly through SUPPLIER_ID and SUPPLIER_SITE_ID. Because the table is a TCA extension, HZ_LOCATIONS and HZ_PARTY_SITES are typically joined to surface address data associated with each carrier. Integration users should also note the SCAC_CODE as the key exchanged with external manifesting and EDI systems.