Search Results freight_carrier_code




Overview
Explore in AI Chat

Overview

WSHFV_DELIVERY is a reporting view in the Oracle E-Business Suite (EBS) Order Entry (OE) module, delivered as part of the shipping execution data model. It is documented in ETRM as a retrofitted object, meaning it was carried forward from an earlier EBS release and maintained for backward compatibility rather than introduced as a new 12.1.1 or 12.2.2 construct. The view presents delivery header information for outbound shipments, joining the delivery record to organization, carrier, departure, customer, and ship-to attributes so that a single row represents a consolidated, reporting-ready view of a delivery.

The view replaces the need to join multiple base tables manually for delivery-level reporting. It exposes both the departure associated with the planned departure (DPW_*) and the departure associated with the actual shipment confirmation (SC_*). This dual structure is significant for users tracing the freight carrier code at the time a delivery was planned versus the carrier code recorded when it was actually confirmed and shipped.

Underlying Base Objects

The ETRM metadata records no documented base objects and indicates the view is not implemented in the reference database, so the object text is the authoritative source. Parsing the view definition, WSHFV_DELIVERY is built on the WSH_DELIVERIES table (aliased DEL) as the driving source. It joins to:

  • ORG_ORGANIZATION_DEFINITIONS (ORG) for the organization code.
  • WSH_DEPARTURES (aliased DEP1) for the planned departure and (aliased DEP2) for the actual departure.
  • A customer/party source (RC) supplying customer name and number.
  • Location sources (SU1, SU2, SU3) supplying ultimate, intermediate, and pooled ship-to locations.
  • FND_USER (FU1, FU2) to resolve picker and packer names.
  • A report set source (SRS) for the report set name.

Key Columns

Because the user searched for freight_carrier_code, the most relevant columns are the two carrier exposures: DPW_FREIGHT_CARRIER_CODE from the planned departure and SC_FREIGHT_CARRIER_CODE from the actual departure. Additional carrier context appears in DEL.FREIGHT_CARRIER_CODE and FREIGHT_TERMS_CODE at the delivery level. Other notable columns include DELIVERY_ID, DELIVERY_NAME, ORGANIZATION_CODE, STATUS_CODE, SOURCE_CODE, WAYBILL, BILL_OF_LADING (as DPW_BOL and SC_BOL), GROSS_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE, ASN_DATE_SENT, ASN_SEQ_NUMBER, and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

The view supports carrier analysis, delivery status reporting, and ASN tracking. A typical query sourcing the freight carrier code is:

  • SELECT delivery_id, delivery_name, organization_code, dpw_freight_carrier_code, sc_freight_carrier_code, freight_carrier_code, status_code FROM wshfv_delivery;
  • Filtering by carrier: WHERE sc_freight_carrier_code = :carrier_code.
  • Reconciling planned versus actual carrier: comparing DPW_FREIGHT_CARRIER_CODE to SC_FREIGHT_CARRIER_CODE.
  • Weight/volume reporting by organization using GROSS_WEIGHT and VOLUME.

Because the view is retrofitted and not implemented in all databases, availability should be validated in the target instance before relying on it in custom reports or integrations.