Search Results get_interval

Overview

The APPS.XNP_DEF_JEOPARDY_INT package is a PL/SQL database object residing in the APPS schema within Oracle E-Business Suite release 12.1.1 and 12.2.2. The XNP prefix associates it with Oracle's Supply Chain and Advanced Planning product family, specifically the procurement and order scheduling components that manage supplier commitments and delivery jeopardy conditions. In this context, "jeopardy" refers to the business state in which an order, schedule, or delivery line is at risk of missing a committed date. The _INT suffix indicates that the package functions as an integration-layer or internal utility object rather than a public end-user API.

The package carries an API classification of OTHER within the documented ETRM metadata, and its status is recorded as VALID. Its role is to provide supporting logic that evaluates interval-based timing criteria used to determine whether a given order or schedule line has entered a jeopardy condition, and to expose that determination to downstream processing and integration routines.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit within this package:

• GET_INTERVAL — The sole documented procedure or function. Its name indicates that it returns or computes an interval value, most plausibly a time or date span relevant to jeopardy evaluation, such as the window between a committed date and the current date, or a configured tolerance interval. Because parameter-level metadata is not published in the ETRM record, the exact argument list and return mode (procedure versus function) cannot be stated authoritatively; consumers should inspect the package specification in the target instance before invoking it directly. No other procedures, functions, or overloads are documented.

Tables Accessed

The package references a single documented application table through APPS synonyms:

• XDP_ORDER_HEADERS — An order header table belonging to the XDP (Order Management/Distributed Order) family. The package accesses order header data to supply the context required for interval computation, such as order dates, scheduling attributes, and header-level status that determine whether a jeopardy interval applies.

In addition to this application table, the recorded dependency list shows a reference to the SYS.STANDARD package, which is the standard Oracle PL/SQL built-in library and appears in virtually all compiled packages. No other schema objects are documented as dependencies.

Usage Notes

The ETRM dependency record indicates that XNP_DEF_JEOPARDY_INT is referenced by one other package, XNP_T_DEF_JEOPARDY_TMR_U. The _TMR_U naming convention is characteristic of Oracle's "Timer" or scheduled-trigger packages, which are typically executed by concurrent programs or background schedulers rather than invoked interactively. This strongly suggests that XNP_DEF_JEOPARDY_INT is a subordinate utility called during scheduled jeopardy-evaluation runs, with XNP_T_DEF_JEOPARDY_TMR_U acting as the driver.

Practically, the package is not exposed through a standard EBS form and is not intended for direct end-user invocation. Because it is classified as OTHER rather than as a supported public API, Oracle does not guarantee signature stability across patches, and customizations should avoid calling it directly. Where custom logic requires jeopardy interval data, the recommended approach is to replicate the interval derivation from configuration rather than depend on this internal package. Support and diagnostics are best directed at the parent timer process, since errors surfaced by GET_INTERVAL will appear in the log of the calling concurrent request.

As with all APPS-schema packages in EBS 12.1.1 and 12.2.2, the compiled body is editioned under the AD online patching model in 12.2.2, so any code inspecting or wrapping this package must account for edition-qualified references in that release.