Search Results wsh_carrier_sites




Overview
Explore in AI Chat

Overview

WSH_CARRIER_SITES is a Shipping Execution (WSH) table that stores carrier site-level configuration in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a specific carrier site — a physical or logical location belonging to a carrier (transportation provider) — and defines the operational parameters Oracle Shipping uses when tendering loads, transmitting tender documents, and applying weight or volume thresholds. The table therefore sits at the boundary between carrier master data (owned by the Trading Community/Receivables model) and outbound logistics execution, and it controls automated behavior during the pick-confirm, ship-confirm, and load-tender lifecycle.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. It carries descriptive and behavioural attributes whose grain is the carrier site, and its principal relationship resolves to HZ_PARTY_SITES via CARRIER_SITE_ID. This classification is a modeling heuristic only; in a normalized EBS context the table functions as a configuration child of carrier master data.

Key Information Stored

The table contains 18 documented columns. The most significant are listed below, distinguishing key columns from descriptive and control attributes:

  • CARRIER_SITE_ID — The primary identifier for the carrier site. Per the ETRM metadata, this column is also the join column to HZ_PARTY_SITES, meaning the carrier site identifier is sourced from and aligned with the Trading Community party site model rather than being an isolated WSH surrogate.
  • CARRIER_ID — Identifies the carrier to which the site belongs; the grouping key for all sites configured for a given transportation provider.
  • SUPPLIER_SITE_ID — Associates the carrier site with the corresponding supplier site, linking shipping execution configuration to the purchasing supplier model.
  • EMAIL_ADDRESS — Destination address used when tenders are transmitted electronically.
  • TENDER_TRANSMISSION_METHOD — Determines how a load tender is delivered (for example, by email or another supported channel).
  • ENABLE_AUTO_TENDER — Flag governing whether tenders are issued automatically for this site.
  • AUTO_ACCEPT_LOAD_TENDER — Indicates whether an inbound load tender may be accepted without manual intervention.
  • TENDER_WAIT_TIME and WAIT_TIME_UOM — Together define the tolerance period and its unit of measure before a tender is considered timed out or escalated.
  • WEIGHT_THRESHOLD_UPPER and WEIGHT_THRESHOLD_LOWER — Bound the acceptable shipment weight range for the site.
  • VOLUME_THRESHOLD_UPPER and VOLUME_THRESHOLD_LOWER — Bound the acceptable shipment volume range for the site.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns present on the table.

Common Use Cases and Queries

The primary scenario is carrier and tender configuration reporting: identifying which carrier sites have automatic tendering enabled, how tenders are transmitted, and what tolerances apply. A second scenario is threshold analysis, where planners review the weight and volume bands that gate tender acceptance.

A representative query joining the site configuration back to the Trading Community party site is:

  • SELECT cs.carrier_id, cs.carrier_site_id, cs.tender_transmission_method, cs.enable_auto_tender, cs.auto_accept_load_tender FROM wsh_carrier_sites cs WHERE cs.enable_auto_tender = 'Y';
  • SELECT cs.carrier_site_id, cs.email_address, cs.tender_wait_time, cs.wait_time_uom FROM wsh_carrier_sites cs, hz_party_sites ps WHERE cs.carrier_site_id = ps.party_site_id;

These patterns support audits of automated tendering, email notification validation, and reconciliation of carrier site configuration against the party site registry.

Related Objects

The most significant related objects, based on the documented foreign-key relationship and standard WSH integration points, are:

  • HZ_PARTY_SITES — Referenced through WSH_CARRIER_SITES.CARRIER_SITE_ID; supplies the underlying party site identity for the carrier site.
  • WSH_CARRIERS — The carrier master table, related through CARRIER_ID, providing carrier-level defaults that site rows may override.
  • POZ_SUPPLIER_SITES_ALL — Supplier site definition related through SUPPLIER_SITE_ID.
  • WSH_TRIPS and trip/load tender tables — Consume carrier site configuration during load tendering.
  • WSH_DELIVERY_ASSIGNMENTS and delivery/shipment tables — Determine carrier assignment against configured sites.

Together these objects position WSH_CARRIER_SITES as the operational control point between carrier master data and outbound shipment execution.