Results for “rlm_debug_pipe”

2 results




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

Overview

APPS.RLM_CORE_SV is a server-side PL/SQL package within the Oracle E-Business Suite Release Management (RLM) module, part of the Order Management family. The package header identifies it as a utility and infrastructure layer that "contains common routines required by Release Management." It is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the defining schema, and it is owned by the APPS schema. Its $Header token (RLMCORES.pls 120.2 2006/04/17) indicates it has been shipped and stable since Release 12.0, and it remains present and documented through 12.2.2. The ETRM classification of the package is "OTHER," confirming it is not a public business API but a supporting library. Its principal documented function is diagnostic instrumentation: it provides a self-contained debugging framework for Release Management code, exposing procedures such as debug, enable_debug, disable_debug, debug_enabled, get_debug_levels, and print_debug_stuff. It also defines the shared collection and record types used by Release Management routines, including t_dynamic_tab, t_Cursor_ref, t_DebugLevels, t_TimeType/t_TimeStack for timing call stacks, and t_CallStack.

Key Procedures and Functions

The package exposes 53 documented procedures and functions, with the header naming the debug family explicitly. The documented debug routines are:

  • debug — the primary tracing entry point, emitting diagnostic output at a caller-specified level.
  • enable_debug — activates debugging for the session, setting the internal debug flag and output destination.
  • disable_debug — turns debugging off for the session.
  • debug_enabled — a function returning whether debugging is currently active, allowing callers to guard expensive trace code.
  • get_debug_levels — returns the configured debug level mask.
  • print_debug_stuff — flushes accumulated debug buffer content to the selected output channel.

Internal constants define the output channels (C_FILE, C_PIPE, C_SCREEN, C_SQLTRACE) and ten-plus level flags (C_LEVEL1 through C_LEVEL11+), with g_MaxLevels defaulting to 31. Output is directed to a database pipe named RLM_DEBUG_PIPE or to a UTL_FILE handle, controlled by the profile option RLM_DEBUG_MODE. Parameter lists for these routines are not published in the metadata and should not be assumed.

Tables Accessed

Through APPS synonyms the package references UTL_FILE (the file I/O package, used as the debug file sink) plus a broad set of Release Management and Order Management base tables. The RLM tables — RLM_INTERFACE_HEADERS, RLM_INTERFACE_LINES, RLM_SCHEDULE_HEADERS, RLM_SCHEDULE_LINES, and RLM_SCHEDULE_LINES_ALL — hold the interface and scheduling data the core routines manipulate. Order data comes from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, while customer and item context derives from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, MTL_CUSTOMER_ITEMS, and MTL_PARAMETERS. HR_ORGANIZATION_INFORMATION supplies organization-level attributes. These accesses support validation and lookup performed by the shared routines rather than primary transaction posting.

Usage Notes

RLM_CORE_SV is not intended for direct invocation by end users. It is referenced by 18 other packages, which call its debug, type, and utility routines internally. Developers troubleshooting Release Management behavior enable tracing by setting the RLM_DEBUG_MODE profile option and calling enable_debug from a session, then reading output from the debug pipe or file. Because the package is AUTHID CURRENT_USER, callers must have appropriate grants on the underlying tables and on UTL_FILE. It is invoked from concurrent programs, forms, and custom PL/SQL that participate in the RLM flow, and any modification should be treated as an upgrade-sensitive change given its 120.x version lineage.