Results for “so_freight_charge_types_u2”

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

Overview

The SO_FREIGHT_CHARGE_TYPES table is a reference (setup) table in the Oracle Order Entry (OE) module. It stores the master list of freight charge types that the enterprise recognizes when calculating and recording shipping-related charges on sales orders. Each row defines a named, coded category of freight charge — for example a specific handling, fuel, or delivery surcharge — that can then be applied to actual order shipments and lines. The table resides in the OE schema and holds a VALID status in EBS 12.1.1 and 12.2.2.

In Data Vault modeling terms, the mined FK structure suggests this object is hub-leaning. It behaves as a business-key hub: it holds the durable, uniquely identified set of freight charge type definitions that surrounding transactional tables reference, rather than describing a single business event or acting as a pure link between entities. Transactional facts such as SO_FREIGHT_CHARGES reference this hub by surrogate key.

Key Information Stored

The table is uniquely identified by the surrogate primary key FREIGHT_CHARGE_TYPE_ID (constraint SO_FREIGHT_CHARGE_TYPES_PK). Two unique indexes act as business-key candidates: SO_FREIGHT_CHARGE_TYPES_U1 on FREIGHT_CHARGE_TYPE_ID and SO_FREIGHT_CHARGE_TYPES_U2 on NAME.

• FREIGHT_CHARGE_TYPE_ID — Surrogate primary key; the value propagated to all dependent transactional tables.
• NAME — User-facing name of the freight charge type; enforced unique via U2.
• FREIGHT_CHARGE_TYPE_CODE — Short internal code used to identify the charge type programmatically.
• FREIGHT_CHARGE_AMOUNT — Default or defined monetary value associated with the charge type.
• CURRENCY_CODE — Currency in which FREIGHT_CHARGE_AMOUNT is expressed.
• DESCRIPTION — Free-text explanation of the charge type's purpose.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating that governs when the charge type is valid for use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield storage for customer-defined extensions.

Common Use Cases and Queries

Typical scenarios include populating freight charge lookups in order-entry screens, validating freight charges captured against shipments, and reporting freight cost by charge type. Because the table is small and setup-driven, it is frequently the master side of joins to the larger SO_FREIGHT_CHARGES transaction table.

• List active charge types for a given date: select FREIGHT_CHARGE_TYPE_ID, NAME, FREIGHT_CHARGE_TYPE_CODE from SO_FREIGHT_CHARGE_TYPES where trunc(sysdate) between nvl(START_DATE_ACTIVE, trunc(sysdate)) and nvl(END_DATE_ACTIVE, trunc(sysdate + 1)).
• Freight cost by type: join SO_FREIGHT_CHARGES to SO_FREIGHT_CHARGE_TYPES on FREIGHT_CHARGE_TYPE_ID and aggregate FREIGHT_CHARGE_AMOUNT grouped by NAME.
• Validation lookups: resolve a charge's business NAME and CODE from its surrogate ID when displaying order freight lines.
• Setup audit / flexfield reporting: query CONTEXT and ATTRIBUTE columns to surface customer-defined freight attributes.

Related Objects

The FK metadata identifies the primary dependents that reference this hub by FREIGHT_CHARGE_TYPE_ID:

• SO_FREIGHT_CHARGES — Transactional freight charges; joins via SO_FREIGHT_CHARGES.FREIGHT_CHARGE_TYPE_ID → SO_FREIGHT_CHARGE_TYPES.FREIGHT_CHARGE_TYPE_ID. This is the principal consumer.
• WSH_FREIGHT_CHARGES_INTERFACE — Shipping/logistics interface table importing freight charges; references FREIGHT_CHARGE_TYPE_ID.
• ASO_FREIGHT_CHARGES — Order-capture/store freight charge table; references FREIGHT_CHARGE_TYPE_ID.

These three tables constitute the documented foreign-key relationships, each keyed back to the freight charge type definition via the shared FREIGHT_CHARGE_TYPE_ID column. The freight charge type master should therefore be maintained before dependent charge records are created, and reference-integrity constraints prevent deletion of a type that is still in use.