Search Results ont_ear_sch_limit_def_util




Overview

The APPS.ONT_EAR_SCH_LIMIT_DEF_UTIL package is a utility (API classification: UTIL) within the Oracle Order Management (ONT) module of Oracle E-Business Suite. Its name references "Earliest Schedule Limit," indicating that its business purpose is to manage and provide access to the earliest scheduling limit configuration used by the order scheduling and fulfillment processes. The earliest schedule limit typically governs how far into the future (or past) an order line may be scheduled, and this utility package centralizes access to that configuration data so that other ONT components can retrieve and cache it consistently.

As the package header comment ("Spec of package ONT_EAR_SCH_LIMIT_Def_Util") and file history ("30-MAR-09 Created") confirm, the package was created in 2009 to provide a definition-level utility layer around the earliest schedule limit view, OE_AK_EAR_SCH_LIMIT_V. It is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the definer, which is typical for utility packages that read from public synonyms and views.

Key Procedures and Functions

The documented package exposes three functions:

  • GET_ATTR_VAL_VARCHAR2 — Returns a VARCHAR2 attribute value from a record of the OE_AK_EAR_SCH_LIMIT_V%ROWTYPE structure, identified by the attribute code passed in. This provides generic, code-driven access to character-typed columns of the earliest schedule limit view without hard-coding column names at the call site.
  • GET_ATTR_VAL_DATE — Returns a DATE attribute value from the same OE_AK_EAR_SCH_LIMIT_V%ROWTYPE record, again selected by attribute code. This supports generic retrieval of date-typed columns, such as an effective date or limit date associated with the earliest schedule limit.
  • SYNC_EAR_SCH_LIMIT_CACHE — Synchronizes the package's internal cached record (declared as g_cached_record OE_AK_EAR_SCH_LIMIT_V%ROWTYPE) using the earliest schedule limit numeric value supplied as input, and returns a NUMBER result indicating the outcome of the synchronization. This is the cache-management routine that keeps the in-memory copy of the limit definition current.

The parameter names for these functions are documented (for example, p_attr_code, p_record, and p_EARLIEST_SCHEDULE_LIMIT); no additional parameters should be assumed beyond those shown in the specification.

Tables Accessed

The package is built around the view OE_AK_EAR_SCH_LIMIT_V, whose %ROWTYPE defines both the generic retrieval signatures and the global cache variable g_cached_record. ETRM metadata does not enumerate any base tables referenced through APPS synonyms, so the primary documented data source is this view. In practice, the view supplies the earliest schedule limit definition rows that the utility reads, caches, and exposes attribute-by-attribute. Because the package is a utility, it is not expected to perform direct DML against transactional order tables; its role is read and cache access rather than data modification.

Usage Notes

According to ETRM metadata, this package is referenced by one other package, confirming it functions as a shared dependency rather than an entry point. It is typically invoked from other ONT scheduling or fulfillment code that needs either to refresh the cached earliest schedule limit via SYNC_EAR_SCH_LIMIT_CACHE or to extract individual attribute values from a limit definition record using the two generic accessor functions. Because the cache is held in a package global, values persist for the duration of the database session; callers should invoke the synchronization function after configuration changes to guarantee they read current data. In Oracle EBS 12.1.1 and 12.2.2, this package remains part of the APPS schema and is compiled against the current OE_AK_EAR_SCH_LIMIT_V definition. Customizations should call these documented functions rather than querying the underlying view directly, so that caching behavior and attribute-code handling remain consistent.