Results for “fob_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
SO_FOBS_ACTIVE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Order Entry (OE). It presents the set of Free On Board (FOB) codes currently active in the system, exposing them in a simplified two-column format that is convenient for reporting, integration, and validation purposes. The view is defined over the AR_LOOKUPS lookup table, filtering to the 'FOB' lookup type and restricting results to enabled lookup codes whose active date range includes the current system date.
Unlike the base AR_LOOKUPS table, which stores many lookup types alongside descriptive and administrative columns, SO_FOBS_ACTIVE_V narrows the scope exclusively to FOB values. This specialization makes it a reliable reference source when consumers require only currently valid FOB codes without needing to understand lookup type filtering or date-range logic. In ETRM 12.1.1 and 12.2.2, the view is documented with owner APPS and references AR_LOOKUPS as its base object. Its role is largely read-only reference data; it is generally not used for transactional processing within Order Entry, but supports queries, reports, and integrations that need to resolve FOB codes to meanings.
Underlying Base Objects
The view is defined exclusively over AR_LOOKUPS, the shared Oracle Receivables lookup repository, which in turn is exposed as a view over the lookup base tables. The dependency chain is therefore AR_LOOKUPS → SO_FOBS_ACTIVE_V. No Order Entry transactional tables, order lines, or shipping tables are referenced; the view is a pure lookup projection.
The defining query filters AR_LOOKUPS on three conditions. First, LOOKUP_TYPE is restricted to 'FOB', ensuring only FOB lookup values are returned. Second, ENABLED_FLAG must equal 'Y', excluding disabled codes. Third, the current date (TRUNC(SYSDATE)) must fall within the active window defined by START_DATE_ACTIVE and END_DATE_ACTIVE, each defaulted to the current date through NVL when null. This means a lookup with no start date is treated as active from the current date, and one with no end date remains active indefinitely as of the query date.
Key Columns
- FOB — The descriptive meaning of the lookup code, sourced from the MEANING column of AR_LOOKUPS. This is the human-readable FOB description presented to users and reports.
- FOB_CODE — The lookup code itself, sourced from LOOKUP_CODE. This is the encoded value used in transactional records, interfaces, and validations to identify the FOB term.
The two columns provide a code-to-meaning pairing analogous to a lightweight reference list, allowing consumers to join or validate against the FOB_CODE while displaying the corresponding FOB meaning.
Common Use Cases and Queries
Typical usage includes populating FOB selection lists in concurrent programs, validating imported order or shipping data, and resolving codes to descriptions in custom reports. The following examples illustrate practical access patterns.
Retrieve all active FOB codes and descriptions:
SELECT fob_code, fob FROM apps.so_fobs_active_v ORDER BY fob;
Validate a specific FOB code against the active set:
SELECT COUNT(*) FROM apps.so_fobs_active_v WHERE fob_code = :p_fob_code;
Join the view to a staging or transactional dataset to translate codes into meanings:
SELECT t.order_number, v.fob
FROM xx_order_stage t,
apps.so_fobs_active_v v
WHERE t.fob_code = v.fob_code;
Because the view already applies the enabled flag and date-range logic, consumers avoid duplicating those conditions and automatically respect lookup maintenance, including any newly disabled or expired FOB entries. Queries should reference the APPS schema explicitly or use a synonym granted to the executing schema.
-
View: SO_FOBS_ACTIVE_V 12.2.2
-
View: SO_FOBS_ACTIVE_V 12.1.1
-
Open or planned deliveries created using Departure Planning Workbench
APPS.WSH_DELIVERIES_DPW_LOV_V·↳ WSH_DELIVERIES·↳ WSH_DEPARTURES·Explore OE module →
-
Open or planned deliveries created using Departure Planning Workbench
APPS.WSH_DELIVERIES_DPW_LOV_V·↳ WSH_DELIVERIES·↳ WSH_DEPARTURES·Explore OE module →
-
View: SO_HEADERS_INTERFACE 12.2.2
APPS.SO_HEADERS_INTERFACE·↳ SO_HEADERS_INTERFACE_ALL·Explore OE module →
-
View: WSHBV_DELIVERY 12.2.2
- Retrofitted
-
View: SO_HEADERS 12.1.1
-
View: SO_ORDER_TYPES_115 12.1.1
APPS.SO_ORDER_TYPES_115·↳ SO_ORDER_TYPES_115_ALL·Explore OE module →
-
View: SO_ORDER_TYPES_115 12.2.2
APPS.SO_ORDER_TYPES_115·↳ SO_ORDER_TYPES_115_ALL·Explore OE module →
-
View: SO_HEADERS_INTERFACE 12.1.1
APPS.SO_HEADERS_INTERFACE·↳ SO_HEADERS_INTERFACE_ALL·Explore OE module →
-
View: WSH_SHIPPING_DETAILS_V 12.2.2
APPS.WSH_SHIPPING_DETAILS_V·↳ HR_LOCATIONS_ALL·↳ OE_INSTALL·↳ OE_ORDER_HEADERS_ALL·Explore OE module →
-
View: WSH_SHIPPING_DETAILS_V 12.1.1
APPS.WSH_SHIPPING_DETAILS_V·↳ HR_LOCATIONS_ALL·↳ OE_INSTALL·↳ OE_ORDER_HEADERS_ALL·Explore OE module →
-
View: WSHBV_DELIVERY 12.1.1
- Retrofitted
-
Order types
-
Shipping deliveries
-
Order types
-
View: SO_HEADERS 12.2.2
-
Shipping deliveries
-
Imported order header information
-
Interface table containing deliveries
-
Order header information
-
Imported order header information
-
Interface table containing deliveries
-
Order header information
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_OEXORRSO_V 12.2.2
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_OEXORRSO_V 12.1.1
Not implemented in this database·Explore OE module →
-
View: SO_TAX_LINES_SUMMARY_V 12.2.2
Not implemented in this database·Explore OE module →
-
View: SO_TAX_LINES_SUMMARY_V 12.1.1
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
Not implemented in this database·Explore OE module →
-
View: WSHFV_DELIVERY 12.1.1
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: WSHFV_DELIVERY 12.2.2
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_CANCEL_V 12.1.1
Not implemented in this database·Explore OE module →
-
View: WSHFV_PICK_LINE_DETAIL 12.2.2
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: WSHFV_PICK_LINE_DETAIL 12.1.1
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: SO_HEADERS_CANCEL_V 12.2.2
Not implemented in this database·Explore OE module →
-
View: WSH_DELIVERIES_V 12.2.2
Deliveries for departure planning or ship confirm
Not implemented in this database·Explore OE module →
-
View: WSH_DELIVERIES_V 12.1.1
Deliveries for departure planning or ship confirm
Not implemented in this database·Explore OE module →