Search Results so_freight_terms_active_v

Overview

The SO_FREIGHT_TERMS_ACTIVE_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and exposes the set of freight terms values that are currently valid and enabled. Freight terms define the commercial arrangement governing who bears transportation cost and risk on a shipment — for example, prepaid, collect, or third-party billing — and they are referenced throughout order capture, shipping, and invoicing flows.

The view is deliberately narrow in purpose. It does not store transactional freight data; instead, it presents a filtered, presentation-ready list of the active freight term lookup codes so that concurrent programs, forms, reports, and external integration layers can retrieve valid values without embedding lookup logic themselves. Because it filters on both the ENABLED_FLAG and the effective-date window, callers receive only values that are legitimately available for selection at the moment of query execution. This makes the view a convenient source for list-of-values (LOV) population, validation routines, and outbound interface extract files.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the documented referenced base objects are SO_LOOKUPS (accessed through a synonym) and the FND_GLOBAL package. All freight term data originates from the SO_LOOKUPS table, which is the Order Entry lookup repository storing lookup types, codes, meanings, descriptions, enablement flags, and effective date ranges.

The view text confirms this relationship. It selects from SO_LOOKUPS with a fixed predicate of LOOKUP_TYPE = 'FREIGHT_TERMS', restricts rows to ENABLED_FLAG = 'Y', and applies a date-range test using TRUNC(SYSDATE) bounded by NVL(START_DATE_ACTIVE, TRUNC(SYSDATE)) and NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). The NVL constructs ensure that lookups with no start or end date are treated as open-ended and therefore always eligible.

Although FND_GLOBAL is documented as a referenced object, the published view text does not invoke it directly. Its presence in the dependency chain typically reflects the standard Oracle EBS practice of initializing the applications session context (APPS, ORG_ID, user identity) that surrounds execution of seeded views. No ORG_ID predicate appears in the view definition, indicating the definition is not organization-striped and returns the same freight term set across operating units.

Key Columns

• FREIGHT_TERMS — The user-facing meaning of the lookup, derived from MEANING in SO_LOOKUPS. This is the descriptive label displayed to users and is the appropriate column for reports and LOV display fields.
• FREIGHT_TERMS_CODE — The stored lookup code from LOOKUP_CODE. This is the value typically persisted on transactional tables such as order headers and is the correct column for joins and programmatic comparisons.
• DESCRIPTION — The extended description maintained against the lookup, providing supplementary explanatory text for the freight term.

All three columns are functionally dependent on the lookup row. The view exposes no primary key column, so the combination of FREIGHT_TERMS_CODE and lookup type is the effective unique identifier.

Common Use Cases and Queries

The primary use cases are value validation, LOV construction, and interface extraction. A typical retrieval of all currently active freight terms is:

• SELECT freight_terms_code, freight_terms, description FROM apps.so_freight_terms_active_v ORDER BY freight_terms;
• Validating a code supplied by an external system: SELECT freight_terms FROM apps.so_freight_terms_active_v WHERE freight_terms_code = :p_code;
• Resolving a stored code to its display label when joining order data to the view on freight_terms_code.

Because the view applies an inline date filter using SYSDATE, results change over time without any data modification. Integrations that cache results should refresh periodically, and any code that passes validation today may become invalid once its END_DATE_ACTIVE passes or its ENABLED_FLAG is cleared.