Search Results wsh_freight_costs_interface




Overview

WSH_FREIGHT_COSTS_INTERFACE is a Shipping Execution (WSH) open interface table in Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It serves as the inbound staging area through which external systems, legacy applications, and custom programs load freight cost records into Oracle Transportation and Shipping Execution so that charges can ultimately be applied to trips, trip stops, deliveries, delivery legs, and delivery details. Records are typically written here by a feeder program, validated and processed by the Shipping Execution concurrent programs, and then transferred to the corresponding permanent freight cost tables. The table holds 60 documented columns and is owned by the WSH schema, with the primary key constraint SYS_C00191604 supported by the unique index WSH_FREIGHT_COSTS_INTERFACE_U1 on FREIGHT_COST_INTERFACE_ID.

From a data modeling perspective, the ETRM relationship metadata classifies this object heuristically as standalone, meaning it is not a pure dependent child of a single parent. In Data Vault terms this suggests a hub-like anchor keyed by FREIGHT_COST_INTERFACE_ID, surrounded by link references to multiple interface and production entities rather than a strictly enforced satellite structure. Modeling this table as a hub with satellite descriptors is a reasonable design suggestion, but the FK structure here is intentionally loose because interface rows may reference several parents at once while awaiting resolution.

Key Information Stored

The surrogate primary key is FREIGHT_COST_INTERFACE_ID, which alone constitutes the documented business-key candidate via unique index WSH_FREIGHT_COSTS_INTERFACE_U1. The most significant columns fall into three groups:

Common Use Cases and Queries

The primary use case is staging freight cost data for import into Shipping Execution. A typical monitoring query inspects unprocessed rows and their processing state:

  • SELECT FREIGHT_COST_INTERFACE_ID, FREIGHT_CODE, TOTAL_AMOUNT, CURRENCY_CODE, PROCESS_FLAG, PROCESS_STATUS_FLAG FROM WSH.WSH_FREIGHT_COSTS_INTERFACE WHERE PROCESS_FLAG = 'N' OR PROCESS_FLAG IS NULL;
  • Joining back to parent interfaces, for example WSH_TRIPS_INTERFACE or WSH_NEW_DEL_INTERFACE, to confirm the freight cost is attached to a valid shipment or trip.
  • Reconciliation reports comparing TOTAL_AMOUNT, CURRENCY_CODE, and CONVERSION_RATE against the permanent freight cost records after processing.
  • Error analysis for rows where INTERFACE_ACTION_CODE or DELETE_FLAG indicates a rejection, typically discovered by the concurrent program that validates the interface.

Related Objects

The documented foreign keys map this interface table to a set of parent and reference objects that should be used when diagnosing or reporting freight cost loads:

  • WSH_FREIGHT_COST_TYPES — joined on FREIGHT_COST_TYPE_ID; supplies the cost type definition.
  • WSH_TRIPS_INTERFACE — joined on TRIP_INTERFACE_ID; the staging parent trip.
  • WSH_TRIP_STOPS_INTERFACE — joined on STOP_INTERFACE_ID; the staging parent stop.
  • WSH_NEW_DEL_INTERFACE — joined on DELIVERY_INTERFACE_ID; the staging delivery header.
  • WSH_DEL_LEGS_INTERFACE — joined on DELIVERY_LEG_INTERFACE_ID; the staging delivery leg.
  • WSH_DEL_DETAILS_INTERFACE — joined on DELIVERY_DETAIL_INTERFACE_ID; the staging delivery detail.
  • WSH_TRIPS, WSH_TRIP_STOPS, WSH_DELIVERY_LEGS — joined on TRIP_ID, STOP_ID, and DELIVERY_LEG_ID; the production-side counterparts used for verification after processing.
  • FTE_TRIPS — joined on FTE_TRIP_ID; the Oracle Transportation Management integration reference.

Together these relationships allow a feeder program to load freight charges against any combination of trip, stop, delivery, or detail level, while the Shipping Execution processing engine resolves and moves each row to its permanent home.