Search Results currency_conversion_type_code




Overview

WSHBV_FREIGHT_CHARGE is an APPS-owned database view in Oracle E-Business Suite, categorized under the Order Entry (OE) product family and marked as Retrofitted in the ETRM repository. The "BV" prefix designates a business view, indicating that its purpose is to present a reporting-friendly, denormalized projection of freight charge data to downstream consumers such as Oracle Shipping Execution, Order Management, and external integration layers. In EBS 12.1.1 and 12.2.2, the view exposes the freight charge records that Oracle Shipping uses to track the cost of transporting a delivery, a container, or an individual picking line. It is read-only in nature and serves as a stable interface layer so that reports, concurrent programs, and interfaces do not depend directly on the transactional base table structure.

The view was retrofitted to align column naming with the wider Oracle logistics data model. Notably, several conversion-related columns are renamed with a CURRENCY_ prefix, which is exactly what makes WSHBV_FREIGHT_CHARGE relevant to a search for currency_conversion_type_code: the base column CONVERSION_TYPE_CODE is surfaced here as CURRENCY_CONVERSION_TYPE_CODE.

Underlying Base Objects

The documented base object is SO_FREIGHT_CHARGES, referenced through a synonym. WSHBV_FREIGHT_CHARGE is therefore a thin, single-table projection: every row in the view maps one-to-one to a row in SO_FREIGHT_CHARGES, and no joins, unions, or aggregations are applied. Because SO_FREIGHT_CHARGES is the Order Management freight charge table, the view inherits all of its transactional semantics, including the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). The APPS synonym grants the view access to the underlying table under the EBS schema conventions.

Key Columns

Common Use Cases and Queries

The view is typically queried when reporting freight costs by delivery or container, when reconciling freight invoicing, and when auditing the currency conversion details applied to freight charges. A user searching for currency_conversion_type_code is usually validating which conversion type was used. For example:

  • Freight cost reporting by delivery, joining CURRENCY_CODE and CURRENCY_CONVERSION_RATE to convert AMOUNT to functional currency.
  • Audit of conversion types applied to freight charges for a given period.
  • Integration extracts feeding freight cost into external freight payment or analytics systems.
SELECT fc.freight_charge_id,
       fc.delivery_id,
       fc.amount,
       fc.currency_code,
       fc.currency_conversion_rate,
       fc.currency_conversion_type_code,
       fc.currency_conversion_date,
       fc.invoice_status
FROM   apps.wshbv_freight_charge fc
WHERE  fc.currency_conversion_type_code IS NOT NULL
ORDER  BY fc.delivery_id;

Because the view performs no transformation beyond column aliasing, all filtering and joins must be supplied by the calling query. Standard EBS security and MOAC constraints apply to the invoking responsibility, and the view should be treated as read-only.