Results for “freight_cost_type_id”

50+ results




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

Overview

WSH_FREIGHT_COST_TYPES is a table owned by the WSH (Shipping Execution) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and description indicate, it stores the master list of freight cost types — the classification codes used to categorize the various charges that arise from moving goods, such as freight, fuel surcharge, handling, and insurance. The table functions as a reference or lookup entity: it defines the allowable cost-type values that transaction-level freight cost records point back to.

Each row supplies a unique type identity (via its primary key), a user-facing name, a short code, a default amount and currency, and effective-dating fields that govern when a given type is valid for use. This makes the table the authoritative source for validating and describing freight charges throughout the order-to-shipment lifecycle. When freight costs are calculated, interfaced, or staged for processing, they consistently resolve their type against this master definition.

The metadata classifies this object with a heuristic Data Vault classification of hub-leaning. As a modeling suggestion, this reflects the table's role as a stable, business-key-identified center of reference data — a hub around which transactional freight cost satellites and links (such as the actual cost records in WSH_FREIGHT_COSTS) are organized.

Key Information Stored

The documented physical schema for 12.2.2 contains thirty-five columns. The most significant are:

The surrogate key FREIGHT_COST_TYPE_ID is distinct from the business-key candidates captured by unique indexes WSH_FREIGHT_COST_TYPES_U1 (FREIGHT_COST_TYPE_ID, ZD_EDITION_NAME) and U2 (NAME, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical scenarios include populating freight cost type selection lists, validating charges during freight calculation, and building cost-type-level reporting. A common pattern joins the transaction table to the type master:

  • Listing active types: SELECT freight_cost_type_id, name, freight_cost_type_code FROM wsh_freight_cost_types WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);
  • Summarizing charges by type: SELECT t.name, SUM(c.amount) FROM wsh_freight_costs c, wsh_freight_cost_types t WHERE c.freight_cost_type_id = t.freight_cost_type_id GROUP BY t.name;
  • Validating interface staging rows against valid type definitions before import.

Related Objects

Foreign-key metadata identifies the principal dependents that reference FREIGHT_COST_TYPE_ID:

These dependents confirm that WSH_FREIGHT_COST_TYPES acts as the reference hub supplying valid cost-type identities to both transactional and staging freight records.