Search Results freight_code_tl




Overview

APPS.WSH_FREIGHT_CARRIERS_ACTIVE_V is a reporting and integration view in the Oracle E-Business Suite Shipping (WSH) module. Its purpose is to expose the set of freight carriers currently active for a given organization, filtering out carriers whose disable date has already passed. The view is defined in Oracle EBS 12.1.1 and 12.2.2 with identical column semantics, and it is widely referenced by shipping, order management, and logistics reporting routines that need a reliable, date-aware list of carriers.

The view derives its name from the term "freight carrier," which in EBS corresponds to a freight code maintained in the ORG_FREIGHT table. The reserved word ACTIVE in the object name signals that the view performs a validity check against the disable date. Because the filter uses TRUNC(SYSDATE), a carrier is considered active on the day it is disabled only if the disable date has not yet passed at the day level.

Underlying Base Objects

The documented base object for this view is ORG_FREIGHT, accessed via a synonym in the APPS schema. ORG_FREIGHT is the Shipping module's master table for freight codes and carrier definitions, organized by inventory organization. Each row represents a freight code belonging to one organization, with attributes including the translatable carrier name (FREIGHT_CODE_TL), a description, an enable/disable date pair, and the owning ORGANIZATION_ID.

The view performs a single-table selection with no joins, so its performance profile mirrors that of a filtered query on ORG_FREIGHT. The NVL expression in the first column indicates that DESCRIPTION is a denormalized human-readable label while FREIGHT_CODE_TL is the translatable carrier code value.

Key Columns

  • FREIGHT_CARRIER — A computed column, defined as NVL(DESCRIPTION, FREIGHT_CODE_TL). It returns the description if present, otherwise falls back to the translatable freight code. This is the primary column downstream reports typically display.
  • FREIGHT_CODE_TL — The translatable freight code / carrier name as stored in ORG_FREIGHT. This is the value users search for when they query "freight_code_tl."
  • DESCRIPTION — An optional descriptive text for the carrier, which may be null.
  • ORGANIZATION_ID — The inventory organization to which the freight carrier record belongs. It is essential for multi-org filtered queries.

Common Use Cases and Queries

The view is commonly used in shipping execution, carrier selection lists, and integration extracts that must exclude retired carriers. A typical query filtered by organization is:

SELECT freight_carrier, freight_code_tl, description, organization_id
FROM   apps.wsh_freight_carriers_active_v
WHERE  organization_id = :org_id
ORDER BY freight_carrier;

Because the view does not itself filter by organization, callers must supply the ORGANIZATION_ID predicate when restricting output to a single operating unit's inventory organization. A lookup by code is also common:

SELECT freight_carrier, organization_id
FROM   apps.wsh_freight_carriers_active_v
WHERE  freight_code_tl = :code;

Integration teams frequently leverage the view to populate carrier picklists in custom forms or to drive carrier validation before freight cost calculation. Note that the view filters on TRUNC(SYSDATE) < TRUNC(NVL(DISABLE_DATE, SYSDATE+1)), so a carrier with a null disable date is treated as active indefinitely, and a carrier disabled today may still appear depending on time-of-day truncation. Query authors should account for this behavior when reconciling the view against ORG_FREIGHT directly.