Search Results wsh_freight_costs_interface_n2

Overview

WSH.WSH_FREIGHT_COSTS_INTERFACE is the Oracle Shipping (WSH) open interface table used to load freight cost records into Oracle E-Business Suite Release 12.1.1 and 12.2.2. It acts as the staging area for transportation and freight charge data that must be validated and imported into the operational freight cost tables during the delivery, trip, and delivery-leg processing cycle. Records placed in this table are read by the concurrent freight cost import program, which resolves the interface surrogate keys to their corresponding operational identifiers and inserts the resulting rows into the production freight cost structures. The table resides in the APPS_TS_INTERFACE tablespace with a PCTFREE of 10 and carries the standard Oracle Applications internal-use warning: it is not supported for direct access except through standard Oracle Applications programs.

Under a heuristic Data Vault classification, this object models as a standalone interface structure rather than as a hub, link, or satellite. Although it contains foreign keys to several operational interfaces, the metadata reports no incoming relationships and no dependent child tables, so it is best treated as a staging entity whose lifecycle is transient.

Key Information Stored

The surrogate primary key is FREIGHT_COST_INTERFACE_ID, enforced by the unique index WSH_FREIGHT_COSTS_INTERFACE_U1 and backed by the constraint SYS_C00191604. This is the documented business-key candidate and the column the import process uses to identify each interface row. No alternate unique index exists on the table, so uniqueness is guaranteed only on this surrogate column.

• FREIGHT_COST_TYPE_ID / FREIGHT_COST_TYPE_CODE — the freight cost type being applied; the ID is a foreign key to WSH_FREIGHT_COST_TYPES.
• UNIT_AMOUNT, QUANTITY, TOTAL_AMOUNT — the monetary and volumetric components of the charge.
• CALCULATION_METHOD, UOM — how the charge was derived and the unit of measure for the quantity.
• CURRENCY_CODE, CONVERSION_DATE, CONVERSION_RATE, CONVERSION_TYPE_CODE — currency and conversion attributes used when the freight cost is expressed in a non-functional currency.
• BILLABLE_QUANTITY, BILLABLE_UOM, BILLABLE_BASIS — the billable measure and the basis on which the charge is billable.
• TRIP_INTERFACE_ID, STOP_INTERFACE_ID, DELIVERY_INTERFACE_ID, DELIVERY_LEG_INTERFACE_ID, DELIVERY_DETAIL_INTERFACE_ID — the interface-side foreign keys that position the cost within the trip, stop, delivery, leg, and delivery detail hierarchy.
• TRIP_ID, STOP_ID, DELIVERY_ID, DELIVERY_LEG_ID, DELIVERY_DETAIL_ID — the resolved operational identifiers populated as the interface is processed.
• FREIGHT_CODE, INTERFACE_ACTION_CODE, PROCESS_FLAG, PROCESS_MODE, PROCESS_STATUS_FLAG, DELETE_FLAG, LOCK_FLAG — control columns governing insert, update, or delete semantics and processing state.

Fifteen ATTRIBUTE columns provide a configurable descriptive flexfield, preceded by ATTRIBUTE_CATEGORY. The table also carries WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID).

Common Use Cases and Queries

The dominant use case is populating the interface from an external transportation management system or legacy load, then submitting the freight cost import concurrent program. A typical staged load supplies the interface keys plus the cost attributes, leaving the resolved operational IDs null until processing.

To review records pending import:

• SELECT FREIGHT_COST_INTERFACE_ID, FREIGHT_COST_TYPE_CODE, TOTAL_AMOUNT, CURRENCY_CODE, PROCESS_FLAG, PROCESS_STATUS_FLAG FROM WSH.WSH_FREIGHT_COSTS_INTERFACE WHERE PROCESS_FLAG IS NULL OR PROCESS_STATUS_FLAG = 'ERROR';

To reconcile staged costs back to their delivery and trip interface parents before import:

• SELECT f.FREIGHT_COST_INTERFACE_ID, f.DELIVERY_INTERFACE_ID, f.DELIVERY_DETAIL_INTERFACE_ID, f.TRIP_INTERFACE_ID, f.STOP_INTERFACE_ID FROM WSH.WSH_FREIGHT_COSTS_INTERFACE f WHERE f.DELIVERY_LEG_INTERFACE_ID = :leg_id;

Reporting queries frequently join to the resolved operational tables once TRIP_ID, DELIVERY_ID, and DELIVERY_LEG_ID are populated, enabling variance analysis between the charged and actual freight amounts per delivery leg. Error diagnostics commonly filter on PROCESS_STATUS_FLAG and join back to the parent interface rows using the nonunique indexes WSH_FREIGHT_COSTS_INTERFACE_N1 (DELIVERY_DETAIL_INTERFACE_ID) and WSH_FREIGHT_COSTS_INTERFACE_N2 (DELIVERY_INTERFACE_ID).

Related Objects

The table is heavily referenced outward, and the following relationships are the most significant for troubleshooting and data extraction:

• WSH.WSH_FREIGHT_COST_TYPES — joined on FREIGHT_COST_TYPE_ID to resolve the cost type definition.
• WSH.WSH_TRIPS_INTERFACE — joined on TRIP_INTERFACE_ID for trip staging.
• WSH.WSH_TRIP_STOPS_INTERFACE — joined on STOP_INTERFACE_ID for trip stop staging.
• WSH.WSH_NEW_DEL_INTERFACE — joined on DELIVERY_INTERFACE_ID for delivery header staging.
• WSH.WSH_DEL_LEGS_INTERFACE — joined on DELIVERY_LEG_INTERFACE_ID for delivery leg staging.
• WSH.WSH_DEL_DETAILS_INTERFACE — joined on DELIVERY_DETAIL_INTERFACE_ID for delivery detail staging.
• WSH.WSH_TRIPS, WSH.WSH_TRIP_STOPS — operational trip and stop tables joined on TRIP_ID and STOP_ID after import.
• WSH.WSH_DELIVERY_LEGS — operational delivery leg table joined on DELIVERY_LEG_ID.
• FTE.FTE_TRIPS — the freight and transportation execution table joined on the undocumented-in-detail FTE_TRIP_ID column, which also has a companion FTE_TRIP_INTERFACE_ID.

The table is maintained exclusively through the standard Oracle freight cost import API and concurrent program rather than by direct DML, consistent with the internal-use-only restriction documented for this object.