Search Results invoice_status




Overview
Explore in AI Chat

Overview

WSHFV_FREIGHT_CHARGE is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It presents freight charge records associated with outbound order entry and shipping activity, joining freight charge data defined on sales orders to picking, container, delivery, and charge type reference information. The view is catalogued under the Order Entry (OE) product family and is documented as retrofitted, meaning it was preserved or reconstructed to maintain compatibility with earlier releases across both 12.1.1 and 12.2.2. Because it exposes a consolidated, denormalized picture of freight charges, it serves as a convenient reporting and integration surface for parties that need freight cost visibility without navigating the underlying transactional tables directly.

Of particular interest to users searching on invoice_status, the view surfaces the INVOICE_STATUS column directly from SO_FREIGHT_CHARGES. This column indicates the invoicing state of a freight charge line, allowing reports to distinguish charges that have been passed to receivables or billing from those still pending. This makes the view a natural starting point for reconciliation queries over freight billing activity.

Underlying Base Objects

The view is defined over six base objects, referenced through APPS synonyms:

  • SO_FREIGHT_CHARGES (FC) — the driving table, supplying freight charge amounts, currency details, and INVOICE_STATUS.
  • SO_FREIGHT_CHARGE_TYPES (FT) — the charge type reference table, supplying name, code, and description.
  • SO_PICKING_HEADERS_ALL (PH) — links a freight charge to its picking header and, through it, to the order header.
  • SO_HEADERS_ALL (H) — the sales order header, supplying ORDER_NUMBER and HEADER_ID.
  • WSH_PACKED_CONTAINERS (PC) — supplies container sequence information where a charge is associated with a packed container.
  • WSH_DELIVERIES (WDL) — supplies the delivery name for charges tied to a shipment.

The joins are predominantly outer joins: PH, H, PC, and WDL are all joined with the (+) operator, while SO_FREIGHT_CHARGE_TYPES is joined as an inner join. This means a freight charge row will still be returned when the picking header, order header, container, or delivery association is absent, but a charge type record must always exist. The structure supports both order-level and delivery-level freight charge contexts.

Key Columns

Common Use Cases and Queries

Typical scenarios include freight cost analysis by order or delivery, charge type distribution reporting, currency exposure summaries, and invoice status reconciliation. A representative query retrieving freight charges with their invoicing status follows:

  • SELECT order_number, delivery_name, freight_charge_type_name, amount, currency_code, invoice_status FROM apps.wshfv_freight_charge WHERE invoice_status IS NOT NULL ORDER BY order_number;
  • SELECT invoice_status, COUNT(*), SUM(amount) FROM apps.wshfv_freight_charge GROUP BY invoice_status;
  • SELECT freight_charge_type_code, currency_code, SUM(amount) FROM apps.wshfv_freight_charge WHERE header_id = :p_header_id GROUP BY freight_charge_type_code, currency_code;

Because the view contains no bind parameters or PL/SQL logic, it can be queried directly from BI Publisher, Oracle Reports, OAF pages, or external integration SQL. Analysts should note that outer joins can produce rows with null order or delivery attributes, so filters on those columns should account for charge records not yet tied to an order or shipment.