Results for “ship_tolerance_above”

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

Overview

The view APPS.OE_AK_SHIP_TOL_ABOVE_V is a metadata construct registered in the Oracle E-Business Suite Order Management (ONT) module. It is classified as a VALID database view owned by the APPS schema. Within the Oracle EBS 12.1.1 and 12.2.2 releases, this object forms part of the Order Management extensibility and validation framework, referenced by the ETRM (E-Business Suite Technical Reference Manual) repository that documents seed data, descriptive flexfields, and validation lookups. The view does not return transactional order data; rather, it exposes a single static result set that supports the ship tolerance "above" attribute used by Order Management validation logic. Its role in reporting and integration is therefore structural and referential: it provides a queryable identifier that downstream logic, forms, or integration maps can reference when applying ship tolerance rules to order lines. It is not a general-purpose reporting view, and its output is deterministic and fixed.

Underlying Base Objects

The documented definition of the view is deliberately minimal:

SELECT 1 FROM DUAL

The only referenced base object is the DUAL synonym, which in Oracle resolves to the built-in SYS.DUAL table. Because the view derives from DUAL, it carries no dependency on Order Management transactional tables such as OE_ORDER_HEADERS_ALL or OE_ORDER_LINES_ALL. The view is a constant-returning construct; it always yields the literal value 1. Its inclusion in the Order Management object inventory, alongside related ship tolerance views, means it is registered as part of the extensibility architecture for shipping tolerance attributes. In ETRM metadata for release 12.2.2, the owner is listed as APPS and the sole referenced base object is DUAL, corroborating that the view performs no joins and requires no privileges beyond access to the APPS schema object itself.

Key Columns

The view exposes a single column:

• SHIP_TOLERANCE_ABOVE — the only projected column, defined by the constant expression 1. In the ETRM-registered context, this column name aligns with the ship tolerance "above" concept in Order Management, where tolerance thresholds govern acceptable over-shipment or under-shipment quantities against ordered amounts. Because the view returns the scalar 1, the column functions as a sentinel or existence indicator rather than a computed tolerance value. Any consumer querying this view should treat the returned value as a fixed flag, not as a dynamic tolerance percentage or quantity. No additional columns, aggregates, or filters are present in the documented view text.

Common Use Cases and Queries

In practice, OE_AK_SHIP_TOL_ABOVE_V is used to assert the presence of the ship tolerance "above" attribute within Order Management setup or extensibility logic. Practical scenarios include:

• Existence verification during patching, cloning, or environment validation, confirming the object exists and is VALID after upgrade from 12.1.1 to 12.2.2.
• Referential wiring in Oracle Forms or OA Framework personalizations that require a queryable view name for the tolerance attribute during runtime validation.
• Integration mapping where an interface expects a constant driver row to seed a lookup or cross-reference.

A representative query is:

SELECT ship_tolerance_above
FROM   apps.oe_ak_ship_tol_above_v;

This returns a single row with the value 1 whenever the view exists and is valid. Because the view is defined over DUAL with no WHERE clause, no bind variables or filter predicates are meaningful. Analysts should not treat the output as business data; it serves as a static anchor point in the Order Management tolerance framework.