Results for “freight_charge_type_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.WSHFV_FREIGHT_CHARGE_TYPE view is a reporting and integration object registered in the Oracle E-Business Suite environment under the Order Entry (OE) product family. Its status is VALID and it is owned by the APPS schema in both EBS 12.1.1 and 12.2.2. The view presents a denormalized, read-friendly projection of freight charge type definitions, exposing the identifier, descriptive attributes, monetary amount, currency, and date-effectivity ranges associated with each freight charge type.

The object name follows Oracle's standard convention for a "flex" or "validation" style view (the FV suffix), which typically designates a view intended for use by Oracle Forms LOVs, concurrent programs, and external integration surfaces rather than for transactional inserts. In documentation metadata the description carries the designation "Retrofitted," indicating the object was added or reclassified during a later release cycle to preserve backward compatibility with reference implementations of the same object. For functional users and technical consultants searching on FREIGHT_CHARGE_TYPE_CODE, this view is the canonical read path to the freight charge type definition list, and it isolates that data from the operational table to which it is bound.

Underlying Base Objects

According to the documented view text, WSHFV_FREIGHT_CHARGE_TYPE is defined entirely over a single base object: SO_FREIGHT_CHARGE_TYPES. The referenced base object is recorded as a SYNONYM in the APPS schema, which in turn points to the underlying shipping/order-entry table in the Shipping Execution schema (WSH). No joins, filters, or aggregations are present: the view text is a straight, unfiltered SELECT of thirteen columns from the base object. Consequently, the view carries no additional business logic, no row-level security predicate, and no date filtering. Any restriction to currently active charge types must be applied by the calling application or query through the START_DATE_ACTIVE and END_DATE_ACTIVE columns. This one-to-one mapping to SO_FREIGHT_CHARGE_TYPES means the view is best understood as a stable synonym-style interface rather than a transformation layer.

Key Columns

• FREIGHT_CHARGE_TYPE_ID — Primary identifier for the freight charge type; the join key used by downstream freight cost and shipping transaction tables.
• FREIGHT_CHARGE_TYPE_CODE — The user-visible, unique short code used to reference a freight charge type in setup, integration payloads, and LOV queries. This is the column most frequently searched and referenced by external systems.
• NAME — Descriptive name of the freight charge type as displayed in the Order Management and Shipping setup windows.
• FREIGHT_CHARGE_AMOUNT — The amount associated with the charge type definition, interpreted in conjunction with CURRENCY_CODE.
• CURRENCY_CODE — Currency in which the freight charge amount is denominated.
• DESCRIPTION — Free-form text describing the purpose or applicability of the charge type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effectivity bounds establishing when the charge type is valid. A NULL END_DATE_ACTIVE generally denotes an open-ended, currently active definition.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Standard WHO columns supporting change tracking and reconciliation.

Common Use Cases and Queries

This view is typically consumed to build lookup lists, to validate an inbound freight charge type code, or to report on charge type configuration. A representative active-record query:

SELECT freight_charge_type_code,
       name,
       freight_charge_amount,
       currency_code
  FROM apps.wshfv_freight_charge_type
 WHERE start_date_active <= SYSDATE
   AND (end_date_active IS NULL OR end_date_active >= SYSDATE)
 ORDER BY name;

To resolve a specific code supplied by an external system:

SELECT freight_charge_type_id, name, freight_charge_amount
  FROM apps.wshfv_freight_charge_type
 WHERE freight_charge_type_code = :p_code;

Because the view performs no filtering, all date-effectivity and enabled/disabled logic must be applied explicitly. Best practice for integration is to reference the view rather than SO_FREIGHT_CHARGE_TYPES directly, preserving compatibility if Oracle later reshapes the underlying objects.