Results for “wsh_carrier_ship_methods”

50+ results




Overview
Explore in AI Chat

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

Overview

The WSH_CARRIER_SHIP_METHODS table resides in the WSH schema, which is owned by the Oracle Shipping Execution module. It stores the definition of carrier ship methods — the transportation service levels and delivery modes offered by a given carrier for a given organization. Each row associates a carrier (a supplier in PO_VENDORS) with a shipping method code and a set of operational attributes that control how that service is used during the shipping and manifest process. This object is referenced heavily throughout WSH when rates, service levels, or freight terms must be resolved for a delivery or a shipment line.

Based on the foreign key topology mined from the ETRM metadata, the table is best described as satellite-leaning within a Data Vault model. It holds descriptive attributes about a carrier relationship rather than functioning as a pure hub. Its only foreign key, CARRIER_ID → PO_VENDORS, anchors it to the vendor hub, while the local surrogate and business keys make it a durable, versionable source for downstream dimensional modeling.

Key Information Stored

The physical schema documented for ETRM 12.2.2 lists 35 columns. The most significant are:

  • CARRIER_SHIP_METHOD_ID — Surrogate primary key (WSH_CARRIER_SHIP_METHODS_PK) and the target of every foreign key reference from downstream shipment tables.
  • CARRIER_ID — Foreign key to PO_VENDORS identifying the carrier or freight provider.
  • SHIP_METHOD_CODE — The business-facing code for the shipping method (for example, ground, express, overnight) that appears on delivery records.
  • ORGANIZATION_ID — The operating unit or inventory organization under which the ship method is defined. Together with SHIP_METHOD_CODE it forms unique index WSH_CARRIER_SHIP_METHODS_U1, a documented business-key candidate.
  • ENABLED_FLAG — Controls whether the ship method is active for selection at shipping time.
  • WEB_ENABLED — Indicates whether the method is exposed for web-order or self-service use.
  • SERVICE_LEVEL — The carrier service tier (for example, priority, standard) used in rating and routing decisions.
  • SUPPORTED_CARRIER — Identifies the carrier system or integration profile that supports this method.
  • CARRIER_SITE_ID — Points to the specific carrier site from which the method operates.
  • FREIGHT_CODE — The freight classification applied to shipments using this method.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns present on all EBS transactional entities.
  • ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — The flexfield (descriptive flex) block used for customer-specific extensions.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrency and program context columns, useful for tracing which concurrent manager process inserted or updated a row.

Note that the unique indexes expose both a surrogate (WSH_CARRIER_SHIP_METHODS_U1 on CARRIER_SHIP_METHOD_ID) and a natural composite (WSH_CARRIER_SHIP_METHODS_U2 on ORGANIZATION_ID + SHIP_METHOD_CODE). The natural key is the safer choice for joins in reporting.

Common Use Cases and Queries

Typical reporting scenarios include retrieving active ship methods for a carrier, validating that a ship method code exists for an organization, and joining ship methods to shipment lines for freight analysis. A common pattern is:

SELECT sm.ship_method_code,
       sm.service_level,
       sm.enabled_flag,
       v.vendor_name
  FROM wsh_carrier_ship_methods sm,
       po_vendors v
 WHERE sm.carrier_id = v.vendor_id
   AND sm.organization_id = :org_id
   AND sm.enabled_flag = 'Y';

Analysts use this table to reconcile shipping charges against carrier-defined service levels, to drive pick-release and document-print behavior, and to troubleshoot why a given ship method is unavailable on an order. Because the ATTRIBUTE columns are free-form flexfields, avoid relying on them without validating against the client's registered value set. The PROGRAM_* columns are useful for auditing which concurrent request last touched a ship method definition.

Related Objects

  • PO_VENDORS — Parent of the CARRIER_ID foreign key. Supplies carrier name, vendor site, and contact details.
  • WSH_DELIVERY_ASSIGNMENTS — Assigns deliveries to ship methods during the shipping lifecycle.
  • WSH_NEW_DELIVERIES — Stores the ship method used on each delivery; joined on carrier ship method or code.
  • WSH_TRIPS / WSH_TRIP_STOPS — Trip planning references ship methods for rate and routing decisions.
  • WSH_FREIGHT_COSTS — Freight cost lines often key back to the ship method employed.
  • OE_ORDER_LINES_ALL — Order lines carry shipped method attributes that default from this table.
  • MTL_SYSTEM_ITEMS_B / FND_LOOKUP_VALUES — Commonly joined for item and lookup-based decoding of service levels.
  • WSH_CARRIER_SHIP_METHODS API and the Shipping Execution concurrent programs — Programs such as interface and manifest routines read this table when validating carrier methods.