Search Results shipping_method




Overview
Explore in AI Chat

Overview

ASO_I_SHIPPING_METHODS_V is a VALID Oracle E-Business Suite view owned by the APPS schema, registered under FND Design Data as ASO.ASO_I_SHIPPING_METHODS_V. It is classified as an internal view type, and the ETRM documentation carries the standard Oracle Internal Use Only advisory: Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. In practice, this means the view exists to support Oracle's own shipping and fulfillment processing logic rather than as a sanctioned public interface.

The view presents a denormalized, reporting-friendly list of shipping methods available to the Order Management and Shipping Execution functional areas. Each row combines the human-readable shipping method name with its underlying lookup code and a longer description, sourced from the shipping method lookup values maintained in Oracle Order Management. Its principal role is to give internal Oracle code a stable, read-only projection of shipping methods without requiring direct joins to lookup tables at runtime. Because it exposes a compact, code-and-description pairing, it is also a convenient reference for reporting and integration where a validated list of shipping methods is required.

Underlying Base Objects

Per the documented dependency information, ASO_I_SHIPPING_METHODS_V is defined over a single referenced base object: OE_SHIP_METHODS_V, itself a view owned by APPS. The view therefore acts as a thin, curated layer above the Order Management shipping methods view, inheriting its filtering and semantics rather than reading base tables directly.

On the consuming side, ASO_I_SHIPPING_METHODS_V is referenced by ASO_SHIPMENTS_BALI_V, confirming its role in the shipping/fulfillment data chain. Data is ultimately derived from shipping method lookup values of lookup type 'SHIPPING_METHOD' in OE_LOOKUPS, which supplies the meaning, lookup code, and description exposed through the query text.

Key Columns

  • SHIPPING_METHOD (VARCHAR2, 80): The meaning, or display name, of the shipping method from OE_LOOKUPS for lookup type 'SHIPPING_METHOD'. This is the value typically shown to users.
  • SHIPPING_METHOD_CODE (VARCHAR2, 30): The lookup code from OE_LOOKUPS for the same lookup type. This is the short code used for programmatic identification and validation.
  • DESCRIPTION (VARCHAR2, 240): The description from OE_LOOKUPS for the lookup type 'SHIPPING_METHOD', providing extended explanatory text.

All three columns are non-mandatory at the view level, permitting nulls where lookup data is incomplete.

Common Use Cases and Queries

The view is most often used to populate shipping method lists in reports, interfaces, and validation routines. A typical retrieval of all available methods is straightforward:

SELECT SHIPPING_METHOD, SHIPPING_METHOD_CODE, DESCRIPTION FROM APPS.ASO_I_SHIPPING_METHODS_V;

A common refinement is to resolve a stored code back to its display name, for example: SELECT SHIPPING_METHOD FROM APPS.ASO_I_SHIPPING_METHODS_V WHERE SHIPPING_METHOD_CODE = :p_code; This pattern appears in validation logic that must confirm a submitted shipping method code is active before persisting it.

Because the view is documented as internal and unsupported for direct external access, any custom report or interface should treat it as a read-only reference and be aware that Oracle may change its definition between releases. Where possible, confirm current behavior against your specific 12.1.1 or 12.2.2 instance before relying on it in production customizations.