Search Results rlm_forecast_sv




Overview
Explore in AI Chat

Overview

RLM_FORECAST_SV is a server-side PL/SQL package in the Oracle E-Business Suite (12.1.1 and 12.2.2) that implements the business logic behind the Manage MRP Forecast API of the RLM Demand Processor. The package is owned by APPS and is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than the definer. As the "_SV" suffix implies, this is a service/validation layer: it encapsulates forecast maintenance operations—creating, replacing, changing, cancelling, and deleting forecast entries—so that callers do not manipulate the underlying planning tables directly.

The package header defines an extensive set of constants that reveal its domain. Operation-mode constants such as k_ORIGINAL, k_REPLACE, k_REPLACE_ALL, k_CHANGE, k_CANCEL, k_DELETE, k_INSERT, k_UPDATE, and k_UPDATE_ATTR govern how a forecast record is processed, while k_PLANNING, k_SHIPPING, and k_SEQUENCED indicate release/schedule contexts. Demand-class constants k_PAST_DUE_FIRM, k_FIRM, and k_FORECAST ('0','1','2') classify forecast lines by firmness. Sentinel constants (k_VNULL, k_NNULL, k_DNULL) provide null-substitution markers, and debug-level constants (k_TDEBUG, k_SDEBUG, k_DEBUG) tie into the RLM_CORE_SV logging framework.

Key Procedures and Functions

The ETRM metadata documents 16 procedures and functions, though only two names are exposed in the excerpt: NAME and PROCESSREPLACEALL.

  • NAME — The first documented entry; in RLM service packages a procedure of this kind typically handles naming or identification of a forecast object or operation. The available metadata does not disclose its parameter list.
  • PROCESSREPLACEALL — The second documented entry, corresponding to the k_REPLACE_ALL operation mode. It applies a wholesale replacement of forecast data, overwriting existing entries rather than merging or selectively changing them.

The remaining documented procedures are not individually described in the available excerpt, and their parameter lists have been intentionally omitted here to avoid speculation. Collectively they implement the operation set implied by the constants: insert, update, change, cancel, delete, and confirmation handling for forecast lines.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms:

Usage Notes

RLM_FORECAST_SV is referenced by four other packages, indicating it is a shared service layer rather than a standalone entry point. It is typically invoked indirectly—from RLM demand-processing logic, concurrent programs that load or refresh MRP forecasts, or custom code that needs to apply forecast changes. Callers supply the operation mode via the package constants and pass forecast data through the RLM interface tables. Direct invocation from Oracle Forms is possible where the Manage MRP Forecast UI requires server-side validation, but the primary consumption path is through the RLM Demand Processor and its dependent packages. Because the package runs with AUTHID CURRENT_USER, executing sessions must hold the appropriate privileges on the referenced APPS synonyms.