Search Results freight_code_tl




Overview
Explore in AI Chat

Overview

WSH_FREIGHT_CARRIERS_ACTIVE_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, defined within the WSH – Shipping Execution product family. The view supplies a filtered, presentation-oriented list of freight carriers that are currently active at a given organization. Rather than exposing raw carrier records, it applies a date-based filter that excludes any carrier whose DISABLE_DATE has already passed, so callers receive only carriers eligible for use as of the current system date (TRUNC(SYSDATE)).

The view is significant in integration and reporting scenarios because it decouples consumers from the underlying ORG_FREIGHT table's lifecycle columns. Lists of values, shipping execution screens, and external interfaces that need a simple "active carriers" set can query this view without replicating the disable-date logic. It also resolves the carrier display name through an NVL expression, returning DESCRIPTION when populated and falling back to FREIGHT_CODE_TL otherwise.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: ORG_FREIGHT, accessed through a SYNONYM in the APPS schema. ORG_FREIGHT is the shipping execution table that stores organization-specific freight carrier definitions, including the carrier code, descriptive text, organization context, and the enable/disable dates that govern carrier availability.

The view text confirms this dependency directly:

SELECT NVL(DESCRIPTION, FREIGHT_CODE_TL) FREIGHT_CARRIER,
       FREIGHT_CODE_TL,
       DESCRIPTION,
       ORGANIZATION_ID
FROM   ORG_FREIGHT
WHERE  TRUNC(SYSDATE) < TRUNC(NVL(DISABLE_DATE, SYSDATE+1))

The WHERE clause is the defining behavior: a carrier row survives the filter when the current date is strictly earlier than its disable date. When DISABLE_DATE is null, NVL substitutes SYSDATE+1, so a null disable date effectively renders the carrier permanently active.

Key Columns

  • FREIGHT_CARRIER — The display label for the carrier. Computed as NVL(DESCRIPTION, FREIGHT_CODE_TL), it prefers the descriptive name and degrades gracefully to the translatable freight code when no description exists.
  • FREIGHT_CODE_TL — The translatable freight carrier code from ORG_FREIGHT. This is the identifier commonly used in lookups and joins, and is the column most often associated with the search term "freight_code_tl".
  • DESCRIPTION — The free-text description of the carrier, passed through unmodified from the base table.
  • ORGANIZATION_ID — The organization to which the carrier definition belongs. Because ORG_FREIGHT is organization-scoped, consumers must filter on this column to isolate a single operating unit or inventory organization's carrier list.

Common Use Cases and Queries

Typical uses include populating carrier selection lists in shipping execution pages, validating carrier codes during shipment or manifest interfaces, and feeding freight-cost reporting that must exclude retired carriers.

A standard query retrieving active carriers for one organization:

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

Resolving a display name for a known code:

SELECT freight_carrier
FROM   apps.wsh_freight_carriers_active_v
WHERE  freight_code_tl = :p_freight_code
AND    organization_id = :p_org_id;

An integration or concurrent program can join the view to shipment tables to confirm that a carrier referenced on a delivery remains active, thereby avoiding assignment of disabled carriers. Because the activity test is evaluated against SYSDATE at query time, results are dynamic; scheduled jobs executed on different days may legitimately return different carrier sets, and queries should not be cached across date boundaries.