Results for “freight_terms_code”

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

Overview

The Oracle E-Business Suite view OE_AK_FREIGHT_TERMS_V is a lightweight, single-purpose database view owned by the APPS schema. It is delivered as part of the Order Management (ONT) product module and holds a VALID status in Oracle EBS 12.1.1 and 12.2.2. The view exists to expose the seeded and user-defined freight terms codes that Order Management uses to classify how freight charges on an order or order line are handled — for example, whether freight is prepaid, collect, billed to a third party, or otherwise allocated between buyer and seller.

In practice the view acts as a simplified lookup façade. Rather than requiring developers, report authors, and integration specialists to query the OE_LOOKUPS table directly with a hard-coded lookup type predicate, OE_AK_FREIGHT_TERMS_V returns only the rows relevant to freight terms. Its role in reporting and integration is therefore one of convenience and consistency: it centralizes the freight terms vocabulary so that concurrent programs, Oracle Reports, BI Publisher data templates, OAF pages, and inbound or outbound interfaces all resolve the same set of valid values. Because it is an APPS-owned object, it must be referenced with the APPS schema prefix or accessed through a synonym and appropriate grants in custom code.

Underlying Base Objects

The view is defined over a single documented base object: OE_LOOKUPS, itself a view rather than a physical table. OE_LOOKUPS is the Order Management-specific wrapper around the FND lookup infrastructure, presenting codes and meanings for lookup types that belong to the ONT application.

The view text is deliberately minimal:

• SELECT LOOKUP_CODE FROM OE_LOOKUPS WHERE LOOKUP_TYPE = 'FREIGHT_TERMS_CODE'

This means the view projects exactly one column — LOOKUP_CODE — filtered to the lookup type FREIGHT_TERMS_CODE. There is no join, no aggregation, and no additional business logic beyond the lookup type restriction. Any organization that adds or disables freight terms codes in the Order Management lookup type FREIGHT_TERMS_CODE will automatically see the change reflected through this view, subject to the underlying OE_LOOKUPS definition and any enabled-flag handling implemented there.

Key Columns

The view exposes a single column:

• FREIGHT_TERMS_CODE — the lookup code value for the FREIGHT_TERMS_CODE lookup type. This is the short, stored code (for example a value such as "PREPAID" or "COLLECT" as configured in the instance) that Order Management stores on order and line records to indicate the freight terms. It is the same token that appears in the corresponding descriptive flexfield or standard freight terms field and is the value expected by downstream pricing, shipping, and invoicing logic.

Because the view returns only the code and not the associated meaning or description, consumers that need a display label must join back to OE_LOOKUPS or FND_LOOKUP_VALUES on LOOKUP_CODE. This is an important design characteristic: the view is optimized for validation and enumeration of codes, not for presentation of descriptions.

Common Use Cases and Queries

Typical scenarios include populating a list of valid freight terms in a custom form or OAF page, validating an inbound interface file before loading order data, and driving a report parameter or value set.

A simple enumeration follows:

• SELECT freight_terms_code FROM apps.oe_ak_freight_terms_v ORDER BY 1;

To obtain descriptions alongside the code, join to the lookup source:

• SELECT v.freight_terms_code, l.meaning FROM apps.oe_ak_freight_terms_v v, apps.oe_lookups l WHERE l.lookup_type = 'FREIGHT_TERMS_CODE' AND l.lookup_code = v.freight_terms_code;

A validation query confirms that a code supplied by an interface exists:

• SELECT COUNT(*) FROM apps.oe_ak_freight_terms_v WHERE freight_terms_code = :p_code;

Because the view is read-only by construction and sourced from lookup metadata, it is safe for high-volume read access and is commonly embedded in value sets (for example, a table-validated value set pointing at FREIGHT_TERMS_CODE) and in concurrent program parameters that require a controlled list of freight terms. Custom development should treat it as a stable, documented interface object rather than replicating the lookup query inline.