Search Results oe_ship_methods_v

Overview

The view ASO_I_SHIPPING_METHODS_V is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and defined within the ASO – Order Capture product family. As documented in the ETRM repository for release 12.1.1 and 12.2.2, its status is VALID and its stated purpose is to “retrieve all valid shipping methods.” The view functions as a filtered presentation layer over the shipping method lookup data maintained in Oracle Order Management, exposing only those shipping methods that are currently active and enabled.

While the user search term “oe_ship_methods_v” points to the underlying Order Management view, ASO_I_SHIPPING_METHODS_V is the Order Capture–facing variant that curates that data for quotation, order capture, and pricing flows. Its role in reporting and integration is to provide a stable, pre-filtered list of shipping methods suitable for LOV (List of Values) population, interfacing, inbound data validation, and ad hoc operational reporting, without requiring downstream consumers to re-implement the enablement and date-validity logic.

Underlying Base Objects

Per the documented metadata, the view is defined over a single referenced base object: OE_SHIP_METHODS_V (itself a VIEW). The dependency chain is therefore a two-tier view hierarchy, in which ASO_I_SHIPPING_METHODS_V narrows and reshapes the columns returned by OE_SHIP_METHODS_V.

The definition applies two principal restrictions to the base view:

• An enablement filter, ENABLED_FLAG = 'Y', which excludes shipping methods that have been disabled by the user.
• A date-validity filter using NVL(START_DATE_ACTIVE, TRUNC(SYSDATE)) and NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)), ensuring the current system date falls within each method’s active window. Where the start or end date is null, the current date is substituted, so such rows are always considered effective.

Because the view derives from a view rather than base tables directly, the physical source of the data resides in the shipping method lookup tables maintained by Oracle Order Management; the ETRM metadata names only the immediate base object, OE_SHIP_METHODS_V.

Key Columns

The view exposes exactly three documented columns:

• SHIPPING_METHOD — The descriptive meaning of the shipping method (mapped from the MEANING column of the base view). This is the user-facing label, such as the display value shown in an LOV or on a printed order.
• SHIPPING_METHOD_CODE — The lookup code (mapped from LOOKUP_CODE) that uniquely identifies the shipping method. This is the value typically stored on transactional records and passed through interfaces.
• DESCRIPTION — The free-text description associated with the shipping method, providing supplementary detail about how or when the method is used.

Each column preserves the naming convention expected by Order Capture integration components, allowing the view to be consumed directly without column aliasing in most customer-facing queries.

Common Use Cases and Queries

Typical scenarios include populating shipping-method lists of values in custom concurrent programs, validating inbound orders or quotes before import, and building operational reports of available shipping options.

List all currently valid shipping methods:

SELECT shipping_method_code,
       shipping_method,
       description
FROM   apps.aso_i_shipping_methods_v
ORDER  BY shipping_method;

Resolve a code to its descriptive meaning for a report or interface mapping:

SELECT shipping_method
FROM   apps.aso_i_shipping_methods_v
WHERE  shipping_method_code = :p_shipping_method_code;

Validate that a value received from an external system is still active before processing:

SELECT COUNT(*)
FROM   apps.aso_i_shipping_methods_v
WHERE  shipping_method_code = :p_incoming_code;

Because the view is owned by APPS and returns only enabled, date-valid records, it should be referenced rather than querying OE_SHIP_METHODS_V directly whenever business logic requires the “valid shipping methods” semantics defined by Order Capture.