Results for “billable_basis”

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

Overview

WSH_FREIGHT_COSTS is a transactional table owned by the WSH (Shipping Execution) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the freight cost lines that Shipping Execution calculates, estimates, or records against trips, trip stops, deliveries, delivery legs, and delivery details. Each row captures either an estimated or an actual freight charge, along with the pricing basis, quantity, unit amount, and total amount used to derive that charge. The table therefore acts as the central repository for landed transportation cost information used by freight rating, freight audit, and shipping cost reporting processes.

Based on the foreign key structure documented in the ETRM metadata, the table is best modeled as satellite-leaning. Its primary key is a surrogate identifier rather than a natural business key, and the numerous foreign keys to parent shipping entities (trips, stops, deliveries, legs, details, and FTE trips) position it as a dependent, descriptive record attached to shipments and trips. The heuristic classification is a modeling suggestion only; the physical schema remains a standard EBS transactional table.

Key Information Stored

The primary key is FREIGHT_COST_ID, enforced by the unique index WSH_FREIGHT_COSTS_PK and mirrored by WSH_FREIGHT_COSTS_U1. It is a system-generated surrogate and is not a natural business key. The most business-relevant columns are:

• FREIGHT_COST_TYPE_ID – references WSH_FREIGHT_COST_TYPES and classifies the charge (for example, base freight, fuel, or accessorial).
• UNIT_AMOUNT, QUANTITY, UOM, TOTAL_AMOUNT – the pricing calculation inputs and result.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_DATE, CONVERSION_TYPE_CODE – currency and conversion context for the charge.
• CALCULATION_METHOD – the method used to derive the amount.
• TRIP_ID, STOP_ID, DELIVERY_ID, DELIVERY_LEG_ID, DELIVERY_DETAIL_ID, FTE_TRIP_ID – the parent shipping entities the cost is attached to.
• FREIGHT_CODE, LINE_TYPE_CODE – freight and line classification attributes.
• PRICING_LIST_HEADER_ID, PRICING_LIST_LINE_ID, APPLIED_TO_CHARGE_ID – links to pricing setup and charge relationships.
• CHARGE_UNIT_VALUE, CHARGE_SOURCE_CODE, ESTIMATED_FLAG – charge basis value, source, and whether the record is an estimate.
• BILLABLE_QUANTITY, BILLABLE_UOM, BILLABLE_BASIS – billable metrics used in downstream freight settlement.
• COMMODITY_CATEGORY_ID – commodity classification associated with the charge.

The table also carries the standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the WHO descriptive flexfield columns ATTRIBUTE_CATEGORY through ATTRIBUTE15.

Common Use Cases and Queries

Typical use cases include freight cost analysis by delivery, trip, carrier, or cost type; reconciliation of estimated versus actual charges using ESTIMATED_FLAG; freight audit reporting; and landed cost calculations. A representative query joins the cost table to its delivery parent:

• SELECT fc.FREIGHT_COST_ID, fc.DELIVERY_ID, fc.TOTAL_AMOUNT, fc.CURRENCY_CODE, fc.ESTIMATED_FLAG FROM WSH.WSH_FREIGHT_COSTS fc WHERE fc.DELIVERY_ID = :delivery_id;
• Aggregate freight by trip: SELECT fc.TRIP_ID, SUM(fc.TOTAL_AMOUNT) FROM WSH.WSH_FREIGHT_COSTS fc GROUP BY fc.TRIP_ID;
• Join to WSH_FREIGHT_COST_TYPES via FREIGHT_COST_TYPE_ID to report charges by type.

Related Objects

The table participates in a rich relationship network. It references WSH_TRIPS (TRIP_ID), WSH_TRIP_STOPS (STOP_ID), WSH_NEW_DELIVERIES (DELIVERY_ID), WSH_DELIVERY_LEGS (DELIVERY_LEG_ID), WSH_DELIVERY_DETAILS (DELIVERY_DETAIL_ID), WSH_FREIGHT_COST_TYPES (FREIGHT_COST_TYPE_ID), and FTE_TRIPS (FTE_TRIP_ID). It is itself referenced by OE_PRICE_ADJUSTMENTS through COST_ID, linking freight costs to order pricing adjustments. These joins should be driven from the documented foreign key columns when building reports or extensions.