Search Results earliest_schedule_limit




Overview

APPS.OE_AK_EAR_SCH_LIMIT_V is a single-column database view owned by the APPS schema in Oracle E-Business Suite, registered under the FND design data object ONT.OE_AK_EAR_SCH_LIMIT_V. It exposes one numeric attribute, EARLIEST_SCHEDULE_LIMIT, and serves as a lightweight access point for the Order Management (ONT) module's earliest-schedule-limit configuration value.

The view is classified in the ETRM as Internal View Type with Status VALID in both 12.1.1 and 12.2.2. Oracle explicitly warns that the object is for internal use only and that Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. Accordingly, its role is not as a general reporting interface but as a supporting construct consumed by Oracle's own scheduling logic.

The user search term earliest_schedule_limit maps directly to the view's sole column and to the profile-driven behaviour it represents — the constraint that governs how far in the past (or relative to a baseline date) a scheduling request may be placed when orders and lines are scheduled.

Underlying Base Objects

The documented dependency list for OE_AK_EAR_SCH_LIMIT_V is minimal. The view references only DUAL, accessed through a PUBLIC synonym. In Oracle, DUAL is the canonical one-row, one-column pseudo-table used to evaluate expressions, return constants, or invoke functions without touching a physical table. This means the view does not read from any Order Management transactional or setup table directly; its value is derived or resolved at query time rather than stored in a dedicated base table.

On the referencing side, the ETRM records that the view is consumed by APPS.ONT_EAR_SCH_LIMIT_DEF_UTIL. This utility package is the documented internal client of the view, which is consistent with the designation of both objects as Oracle internal use only. The relationship is therefore one of internal plumbing: the utility resolves the earliest schedule limit through the view, and the view abstracts the source of that value behind a stable column name.

Key Columns

The view exposes a single column:

  • EARLIEST_SCHEDULE_LIMIT — NUMBER. This is the numeric limit value returned by the view. Because the view is defined over DUAL, the value is produced by the view's query expression rather than by a column in a base table. In Order Management scheduling terms, this value constrains how early a requested schedule date may fall relative to the applicable baseline, acting as a floor for scheduling validation.

The syntax documented for querying the object is a simple projection: SELECT EARLIEST_SCHEDULE_LIMIT FROM APPS.OE_AK_EAR_SCH_LIMIT_V;. No mandatory columns, join keys, or additional identifiers are exposed, which reinforces the view's narrow, single-purpose design.

Common Use Cases and Queries

The supported use case is internal resolution of the earliest schedule limit by Oracle scheduling utilities, principally ONT_EAR_SCH_LIMIT_DEF_UTIL. External integrators and report developers who encounter earliest_schedule_limit in Order Management scheduling behaviour should treat this view as diagnostic rather than as a supported extension point.

A minimal verification query returns the current value:

SELECT earliest_schedule_limit FROM apps.oe_ak_ear_sch_limit_v;

Where the limit influences schedule-date validation, a supporting query can frame the returned value against actual order schedule dates:

  • SELECT l.earliest_schedule_limit, o.order_number, o.request_date FROM apps.oe_ak_ear_sch_limit_v l, apps.oe_order_headers_all o WHERE o.request_date > l.earliest_schedule_limit;

Because the view draws only on DUAL, it incurs negligible cost and can be queried repeatedly without performance concern. Nevertheless, given the explicit Oracle restriction, any production integration should avoid a hard dependency on this object; the value is best obtained through Oracle's supported scheduling APIs and profile options rather than by direct selection from the view.