Results for “rlm_rd_sv”

50+ results




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

Overview

RLM_RD_SV is a PL/SQL package body in the Oracle E-Business Suite Applications schema (APPS) that forms part of the Release Management (RLM) product family, specifically the Demand Planning / scheduling component. Its documented API classification is "OTHER," indicating it is an internal processing package rather than a public-facing API. The package provides the server-side logic required to record demand from scheduling interface data. The primary entry point, RecDemand, accepts an interface header identifier, a full row of RLM_INTERFACE_HEADERS, and a group record structure passed by reference from the companion package RLM_DP_SV, returning a status code to the caller.

The package header comment dates the source header to 2008, and the body carries several internal globals that reflect accumulated bug fixes — notably g_sch_line_qty (Bugfix 6131516), g_del_reconcile (Bugfix 6131516), and g_inc_exception (Bugfix 6159269). These globals govern line-quantity handling, delete/reconcile behavior, and exception inclusion during demand processing.

Key Procedures and Functions

ETRM documents 74 procedures and functions within this package body. The visible excerpt identifies the RecDemand procedure, which performs the following documented steps:

  • Initializes the return status to rlm_core_sv.k_PROC_SUCCESS at entry, converting it to an error status only if a failure occurs during processing.
  • Conditionally writes diagnostic output through rlm_core_sv.dpush and rlm_core_sv.dlog when the profile option RLM_DEBUG_MODE is enabled. The debug trace logs the interface header ID, schedule type, schedule purpose, schedule source, and schedule generation date.
  • Declares cursor references (t_Cursor_ref) and group record types (rlm_dp_sv.t_Group_rec) for regrouping demand records, indicating a loop that re-buckets schedule demand by group.
  • Declares a named exception e_lines_locked, indicating the procedure can encounter lock contention on interface or schedule lines and must handle that condition gracefully.
  • Tracks progress through a x_progress string (initialized to '010'), a conventional EBS technique for pinpointing failing steps in concurrent logs.

Because the ETRM metadata exposes only the first of the 74 documented units, the remaining procedures are named but not individually described. They collectively support the full demand-recording lifecycle: reading interface lines, applying schedule rules, grouping demand, and writing schedule headers and lines.

Tables Accessed

The package references the following tables through APPS synonyms:

Usage Notes

RLM_RD_SV is an internal package, not an end-user API. It is referenced by six other packages, which indicates it is invoked indirectly from higher-level demand planning or scheduling processors rather than called directly from a form. In a typical 12.1.1 or 12.2.2 deployment, the package is reached through the RLM concurrent program that processes the scheduling interface — the program reads interface rows, calls RecDemand for each header, and the debug profile RLM_DEBUG_MODE is set when troubleshooting is required. Customers performing custom integrations should not call RLM_RD_SV directly; they should populate the RLM interface tables and submit the standard concurrent request. The presence of the e_lines_locked exception means concurrent runs against the same interface set should be avoided, as competing processes can collide on locked schedule lines.