Results for “fob_code”

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

Overview

OE_FOBS_ACTIVE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the ONT (Order Management) product family. Its documented description identifies it simply as a "freight on board view." In practice the view exposes the set of currently active Freight on Board (FOB) lookup values configured in the application, presenting each FOB as a code paired with its user-facing meaning and its active date range. Because FOB codes drive title transfer, risk-of-loss, and freight responsibility on order and shipping transactions, consumers of this view — including order entry flexfields, shipping documentation, and custom reports — rely on it to enumerate only those FOB values that are enabled and valid for the current date. The view carries a VALID status in the ETRM 12.2.2 metadata and behaves identically in 12.1.1, since it is defined over core lookup infrastructure that is unchanged between those releases. A user searching on "fob_code" is typically looking for the column of that name exposed here, which returns the lookup code portion of each FOB value without the descriptive meaning text.

Underlying Base Objects

The view is defined over a single documented base object: AR_LOOKUPS, which is itself surfaced as a view in the APPS schema and serves as the central repository of Receivables and shared application lookup values. OE_FOBS_ACTIVE_V filters that source on LOOKUP_TYPE = 'FOB', meaning it isolates a single lookup type from the much broader set held in AR_LOOKUPS. Two further predicates narrow the result set: ENABLED_FLAG = 'Y' restricts output to lookups that have not been disabled, and a date-range condition requires the current system date to fall between the lookup's START_DATE_ACTIVE and END_DATE_ACTIVE, with NVL defaults substituting SYSDATE where either boundary is null. Consequently the view is a thin, filtered projection rather than an aggregation or join, and its contents change only when FOB lookup definitions or their effective dates are maintained through the application's lookup administration screens. No dependency on Order Management transaction tables exists; the view is purely reference data.

Key Columns

• FOB — The descriptive meaning of the FOB lookup, aliased from MEANING in AR_LOOKUPS. This is the text displayed to users, such as the named shipping term associated with the code.
• FOB_CODE — The lookup code value, aliased from LOOKUP_CODE. This is the stored, language-independent identifier used to attach an FOB value to an order, a ship-from/ship-to combination, or a shipping document, and is the column most commonly referenced by integrations and by name in user searches.
• START_DATE_ACTIVE — The date from which the FOB lookup becomes effective. When null, the view's predicate treats the lookup as active from the current date.
• END_DATE_ACTIVE — The date through which the FOB lookup remains effective. When null, the lookup is treated as open-ended and remains active indefinitely.

Common Use Cases and Queries

Typical uses include populating an FOB selection list on an order-entry or shipping form, validating an inbound FOB_CODE from an external system before accepting it, and driving report parameters that must offer only valid shipping terms. Because the view already enforces enablement and effective dating, callers avoid reimplementing that logic. A basic listing of all currently active FOB values is:

SELECT fob_code, fob FROM oe_fobs_active_v ORDER BY fob;

To retrieve only the code and its effective window, or to resolve a single code captured on an interface record:

SELECT fob, fob_code, start_date_active, end_date_active FROM oe_fobs_active_v;

SELECT fob FROM oe_fobs_active_v WHERE fob_code = :p_fob_code;

The second query is the standard pattern for validating a user-supplied or externally supplied fob_code; an empty result indicates the code is either undefined or no longer within its active date range. Because results are date-sensitive, any caching of this view should be refreshed daily.