Search Results rlm_debug_mode

Overview

RLM_CUM_UPGRADE_SV is a server-side PL/SQL package body owned by the APPS schema within Oracle E-Business Suite. Its name and header comments identify it as an upgrade API for cumulative history data, allowing Oracle to migrate or reset cumulative quantity and shipment history as part of an ETRM maintenance or patch cycle. ETRM, delivered through the Release Management and Telebusiness/Advanced Pricing integration set, maintains cumulative pricing, accrual, and threshold history for customers and agreements. The "_SV" suffix follows the EBS convention of denoting a service layer exposed to callers through forms, concurrent programs, or other PL/SQL APIs.

The package header comment cites the original owner as MPAREKH and shows a revision of 120.0 dated 2005/05/26, indicating a long-standing seeded object retained through the 12.1.1 and 12.2.2 releases. Specifically because the sole documented routine is inert in the source excerpt, the package appears to be a stub or shell upgrade shell, reserved for a future or discontinued migration routine rather than active business logic.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure, reported under the placeholder name "NAME":

• UpgradeCumHistory — the procedure named in the package body that performs the cumulative history upgrade. It is the only exposed entry point and defines no documented parameters; callers invoke it without arguments. In the excerpt the body does nothing except, when debugging is enabled, raise a debug trace (rlm_core_sv.start_debug, dpush, dpop, and stop_debug) and exit. No cursor activity, DML, or return status is exercised in the visible code, though the local v_ReturnStatus BOOLEAN declaration hints at a status mechanism in an earlier or later version.

Tables Accessed

No base tables or APPS synonyms are listed in the documented metadata, and the surviving procedure body contains no SELECT, INSERT, UPDATE, or DELETE statements. The package therefore does not read or write cumulative history tables under the surface of this revision. In functional terms, an upgrade of cumulative history would ordinarily touch ETRM cumulative and history structures (the family of RLM_% history and cumulative tables owned by Advanced Pricing and Release Management), but the excerpt provides no evidence of such access and none can be asserted from the metadata alone.

Usage Notes

The package is classified as API classification OTHER and is referenced by zero other packages, which confirms that no seeded EBS module depends on it internally. It is a leaf object, not part of a call chain.

Its debug behavior is governed by the profile option RLM_DEBUG_MODE, read once into the package-level constant l_DEBUG via NVL(fnd_profile.value('RLM_DEBUG_MODE'),-1). This explains the search term "rlm_debug_mode": if the profile is set to any value other than -1 (including zero), the IF (l_debug <> -1) test is true and the package engages the RLM_CORE_SV debug stack, writing an "UpgradeCumHistory" frame to the C_SDEBUG log and a "Reset cum completed" message to the C_DEBUG log. Administrators diagnosing ETRM pricing or cumulative issues commonly set RLM_DEBUG_MODE, then query the resulting debug output to confirm that upgrade logic executed.

Because the routine takes no parameters and returns nothing, it is typically invoked from SQL*Plus or a custom concurrent program with a simple anonymous block calling RLM_CUM_UPGRADE_SV.UpgradeCumHistory; there is no seeded form or standard concurrent program listed in the metadata for it. In 12.1.1 and 12.2.2 this is a no-op or near-no-op object; it should not be relied upon in customizations, and clients should validate behavior against their release's file system version, since the body is trivial and only the debug path is exercised.