Search Results oe_ship_methods_v




Overview
Explore in AI Chat

Overview

OE_SHIP_METHODS_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite Order Management (ONT) module. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the object type is VIEW and its status is VALID. The view presents a filtered, secured projection of shipping method (carrier/service level) lookup values, exposing the reference data that Order Management uses to classify how ordered goods are dispatched. Rather than maintaining a dedicated ship method entity, Oracle EBS stores shipping methods as lookup codes under the FND lookup type SHIP_METHOD, and OE_SHIP_METHODS_V surfaces those codes in a form suitable for LOVs, reports, concurrent programs, and interface extraction.

Because shipping method values are seeded and maintained as application reference data, the view functions as a read-only window onto the standard lookup infrastructure. It enables report developers and integration architects to query valid, language-aware ship method definitions without needing to reconstruct the underlying FND_LOOKUP_VALUES predicates, thereby enforcing consistent filtering across custom artifacts.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES, accessed through a SYNONYM in the APPS schema. The view text explicitly restricts the result set with the following predicates:

  • LANGUAGE = USERENV('LANG') — returns only the lookup rows whose language matches the session language, ensuring translated MEANING and DESCRIPTION values are presented to the user.
  • VIEW_APPLICATION_ID = 3 — limits results to lookups owned by application identifier 3 (Oracle Order Management).
  • LOOKUP_TYPE = 'SHIP_METHOD' — isolates the shipping method lookup category.
  • SECURITY_GROUP_ID = 0 — restricts to the standard, non-secured lookup set.

Consequently, the view inherits its column structure directly from FND_LOOKUP_VALUES while applying the Order Management context. No joins to order, shipping, or inventory tables are performed within the view definition.

Key Columns

  • LOOKUP_TYPE — the lookup category; always returns SHIP_METHOD when queried through this view.
  • LOOKUP_CODE — the internal code stored on transactional records such as order lines and delivery details; this is the value typically referenced by foreign-key style relationships in OE_ORDER_LINES_ALL and related tables.
  • MEANING — the user-facing, language-specific display name for the ship method.
  • DESCRIPTION — an optional extended description of the shipping method.
  • ENABLED_FLAG — indicates whether the ship method is currently active (Y) or disabled (N) for selection.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the lookup is valid.

Common Use Cases and Queries

Typical usage includes populating shipping method list of values in custom forms and OAF pages, driving shipping labels and carrier reports, and extracting reference data for data warehouse or integration staging tables. The view also supports validation routines that confirm a submitted ship method code is enabled and effective as of a given date.

A basic query returning only active shipping methods:

  • SELECT lookup_code, meaning, description FROM oe_ship_methods_v WHERE enabled_flag = 'Y' ORDER BY meaning;

To validate a specific code against its active date range:

  • SELECT meaning FROM oe_ship_methods_v WHERE lookup_code = :p_code AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Because the view is language-aware, joining it to order lines by lookup_code yields user-facing descriptions appropriate to the session language, making it suitable for multi-language reporting environments.