Search Results oe_ak_fob_point_v




Overview
Explore in AI Chat

Overview

The OE_AK_FOB_POINT_V view is a lightweight, read-only database object owned by the APPS schema in Oracle E-Business Suite. It is registered to the Order Management (ONT) product and remains VALID in both release 12.1.1 and 12.2.2. The view exposes the set of valid Free On Board (FOB) point codes used within order management, shipping, and pricing flows. Its definition is deliberately minimal: it projects a single column from the Oracle Order Management lookup infrastructure, presenting only those lookup codes where the lookup type equals FOB_POINT_CODE.

The "AK" prefix in the object name signals that the view participates in the Oracle Application Framework's attribute/key flexfield generation mechanism, historically associated with descriptive and extensibility attributes on order entities. In practice, the view functions as a secure, reusable value source for LOV (list of values) queries, reports, and integration extracts that need to resolve the permitted FOB point codes without directly querying the shared OE_LOOKUPS table. By isolating a single lookup type, the view reduces the risk of application code retrieving unrelated lookup values and provides a stable, named contract that customizations and interfaces can depend upon.

Underlying Base Objects

The view is defined over exactly one documented base object: OE_LOOKUPS, itself exposed to the APPS schema as a view. OE_LOOKUPS is the standard Order Management lookup repository, storing code/meaning pairs keyed by LOOKUP_TYPE and filtered by enabled flags and language attributes in the underlying lookup tables. The view text as documented in ETRM is:

  • SELECT LOOKUP_CODE FROM OE_LOOKUPS WHERE LOOKUP_TYPE = 'FOB_POINT_CODE'

Because the projection depends on a base view rather than a physical table, the set of returned codes may change as FOB point lookups are added, end-dated, or disabled by the application administrator. Implementers should therefore treat the view as a dynamic enumeration of active lookup codes rather than a static reference list.

Key Columns

  • FOB_POINT_CODE — The only column exposed. It carries the lookup code component of each FOB point definition. For example, standard Order Management configurations include codes such as ORIGIN and DESTINATION, representing shipment terms where title and risk transfer at the shipping origin or at the receiving destination, respectively. The corresponding descriptive meaning text is not surfaced by this view; consumers requiring the user-facing description must join back to OE_LOOKUPS or the underlying lookup tables on LOOKUP_CODE and LOOKUP_TYPE = 'FOB_POINT_CODE'.

Common Use Cases and Queries

The view is most frequently used to drive list-of-values queries on order entry forms, order import validation routines, and custom concurrent programs that must validate or translate FOB point values before insert into order tables. A typical lookup is:

  • SELECT fob_point_code FROM oe_ak_fob_point_v ORDER BY 1;

For validation during interface processing, the view can be joined to staging data to reject invalid codes:

  • SELECT s.order_number, s.fob_point FROM xx_order_stage s WHERE NOT EXISTS (SELECT 1 FROM oe_ak_fob_point_v v WHERE v.fob_point_code = s.fob_point);

When the descriptive meaning is required for reports, supplement the view with a join to the lookup repository. Because the view returns no language-specific meaning and no enabled flag, join predicates against OE_LOOKUPS should filter on LOOKUP_TYPE = 'FOB_POINT_CODE' and the appropriate VIEW_APPLICATION_ID or language context. Note that as a one-column view, OE_AK_FOB_POINT_V is not suited to update operations; it should be treated exclusively as a read-only reference source within ONT-related reporting and integration solutions.