Search Results debug_level_2

Overview

ARP_FILE is a utility package owned by the APPS schema in Oracle E-Business Suite Receivables (AR). Its role is diagnostic rather than transactional: it provides a standardized logging and tracing facility that other Receivables PL/SQL programs call to record runtime messages, trace information, and debug output. The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the calling user and resolves unqualified object references through that user's schema and synonyms. A private set of constants establishes the severity scale used throughout the package: MIN_DEBUG_LEVEL (0), DEBUG_LEVEL_1 (1), DEBUG_LEVEL_2 (2), DEBUG_LEVEL_3 (3), INFO_LEVEL (90), and MAX_DEBUG_LEVEL (99). Callers pass one of these levels to the logging routine so that output can be filtered by verbosity without modifying the calling code. The package header shipped in release 12.1.1 and remains present in 12.2.2; the $Header comment identifies the last source change as version 120.2, dated 2005, indicating a long-stable interface.

Key Procedures and Functions

The documented public interface consists of two procedures.

• WRITE_LOG — The principal logging entry point. It accepts a text message and a numeric level, where the level defaults to MAX_DEBUG_LEVEL when the caller does not supply one. Messages submitted at the default level therefore represent the highest verbosity and are intended for arbitrary, always-emitted diagnostics, while callers that pass INFO_LEVEL or one of the DEBUG_LEVEL_n constants signal progressively narrower categories of output. This convention allows a single logging stream to be segmented by purpose.
• PRINT_FN_LABEL — A lightweight tracing helper that records a function or procedure label. It is typically called at the entry point of a program unit so that the log shows the execution path through nested routines. It takes only the label text and does not participate in level filtering.

Both procedures are exposed in the package specification; the body is not part of the documented interface and should be treated as private implementation.

Tables Accessed

The only documented table reference is AR_SYSTEM_PARAMETERS, reached through an APPS synonym. This is the Receivables system options table, which holds installation-wide configuration for the AR module. A logging utility reads it to determine environment-specific behavior — for example, whether logging is enabled and at what threshold — rather than to persist log rows. The package is not documented as writing application data; any output it produces is directed to the supported diagnostic destinations rather than to Receivables business tables.

Usage Notes

ARP_FILE is an internal support package. It is not invoked directly by end users and has no associated form or concurrent program of its own. Instead, it is called from other PL/SQL units in Receivables that need consistent, level-aware diagnostics — the metadata shows three packages referencing it, and custom extensions that follow Oracle's logging conventions frequently do the same. Typical usage is a call to PRINT_FN_LABEL on entry to a procedure, followed by one or more WRITE_LOG calls with an appropriate level constant. Because the level constants are defined in the specification, callers should reference them symbolically rather than hard-coding numeric values.

Two cautions apply during upgrades and customization. First, log volume at MAX_DEBUG_LEVEL can be substantial, so production code should restrict itself to INFO_LEVEL or higher-severity categories. Second, because the package is owned by APPS and its interface has been unchanged since 2005, custom code may safely depend on it, but that dependency couples the customization to an Oracle-internal utility that Oracle may change without a public API commitment.