Results for “ship_tolerance_below”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The Oracle EBS object OE_AK_SHIP_TOL_BELOW_V is a database view owned by the APPS schema and registered under the Order Management (ONT) product family. In ETRM metadata for both Oracle E-Business Suite 12.1.1 and 12.2.2, the object carries a status of VALID and is classified as a VIEW. Its purpose is to expose a single, static value identified by the column name SHIP_TOLERANCE_BELOW, which is associated with shipping tolerance configuration in Order Management.

Although the internal implementation of this view is deliberately minimal — the documented View Text is simply SELECT 1 FROM DUAL — its presence in the APPS data dictionary reflects the design pattern Oracle uses for reference or placeholder views. These lightweight objects allow Oracle Application Object Library components, forms, or descriptive flexfield (DFF) validators to reference a named view without requiring access to a complex underlying query. Within reporting and integration contexts, the view therefore functions primarily as a named handle for the shipping-tolerance-below attribute rather than as a rich data source.

Underlying Base Objects

The documented view metadata for Oracle EBS 12.2.2 indicates that the only referenced base object is DUAL, which appears in the data dictionary as a SYNONYM. DUAL is the standard Oracle single-row, single-column dummy table used when an application needs to return a constant or perform a synthetic lookup.

Because the view is defined over DUAL, it has no dependency on Order Management transaction tables such as OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, or the shipping tolerance setup tables that would normally store a numeric tolerance value. This means the view does not join to inventory, shipping, or pricing entities and does not carry a real tolerance percentage or quantity. Its relationship to those objects is by convention and naming rather than by foreign-key or join dependency.

Key Columns

The view exposes a single column:

• SHIP_TOLERANCE_BELOW — The only documented column returned by the view. As implemented (SELECT 1 FROM DUAL), this column returns the constant 1 for each row, producing exactly one row when queried. In the context of Order Management shipping tolerances, the name implies a reference to the below-tolerance dimension of a shipping tolerance rule, but the implemented value is a placeholder rather than a stored configuration figure.

No additional columns, aliases, or computed expressions are documented in the ETRM metadata.

Common Use Cases and Queries

Given its implementation, OE_AK_SHIP_TOL_BELOW_V is used less for data extraction and more as a reference object. Typical practical scenarios include:

• Existence and metadata checks — DBAs and developers verifying that the object is installed and VALID after an upgrade or patch in 12.1.1 or 12.2.2.
• Placeholder lookups — Application components or descriptive flexfield validation logic that require a named view supplying a constant value.
• Integration scaffolding — Interfaces that reference the view by name as a stub, expecting future customization or extension.

A basic query returns the constant row:

• SELECT ship_tolerance_below FROM apps.oe_ak_ship_tol_below_v; — returns 1.

To confirm dictionary status:

• SELECT object_name, object_type, status FROM all_objects WHERE object_name = 'OE_AK_SHIP_TOL_BELOW_V';

Because the view does not query Order Management tables, it should not be relied upon to retrieve actual shipping tolerance thresholds. Real tolerance values reside in the Order Management setup tables, and queries intended to drive business logic must target those base tables rather than this placeholder view.