Search Results print_fn_label

Overview

ARP_FILE is a private utility package body owned by APPS that provides logging and debugging support for the Oracle Receivables (AR) module. It does not implement business transactions itself; rather, it serves as an internal instrumentation layer used by other Receivables PL/SQL packages to emit diagnostic and tracing information during execution. The package is classified as OTHER in the ETRM metadata, reflecting its supporting rather than functional role within the application architecture.

The package body is a long-standing component of the Receivables codebase; the embedded source header dates to 2000 and carries a 2003 revision marker, and the logic remains unchanged in the 12.1.1 and 12.2.2 releases. Its design centers on a single gating mechanism controlled by system parameter and profile option settings, ensuring that logging output is produced only when the relevant debug levels are enabled. This allows Oracle Support and development teams to enable targeted tracing in a production environment without materially affecting performance when logging is disabled.

Key Procedures and Functions

Two procedures are documented for this package:

• WRITE_LOG — The core logging routine. It accepts a text message and associated debug level and conditionally emits that message to the log. Output is written either to the concurrent request log file via the FND_FILE utility, when the package is executing within a concurrent request context, or to the application debug stream when invoked interactively. The decision to print is governed by a comparison between the configured log message level held in the Receivables system parameters and the level supplied by the caller. When debug is disabled, the procedure performs no output.
• PRINT_FN_LABEL — A convenience wrapper that prints a function label or descriptive text to the log. It delegates directly to WRITE_LOG, supplying the minimum debug level so that the label is emitted whenever logging is active. Its purpose is to delimit logical sections of execution trace, making the resulting log easier to interpret, particularly when the requested search term "print_fn_label" appears in generated output.

Tables Accessed

The package reads parameters from AR_SYSTEM_PARAMETERS, accessed through APPS synonyms. This table supplies the system-level configuration values that determine whether logging is active and at what message level. The primary value consumed is the log file message level, which is compared against the debug level passed into WRITE_LOG to decide whether a given message should be written. Profile option values, notably the Applications logging enablement flag, are also consulted through standard profile mechanisms to determine the appropriate output destination.

Usage Notes

ARP_FILE is not intended for direct invocation by end users or by customer-developed code. It is a private package body, and its procedures are called internally by other Receivables packages; the ETRM metadata records three packages that reference it. Developers extending or debugging Receivables should not call these procedures directly but should instead rely on the standard profile options and system parameters that control logging, since the package reads those settings at runtime.

In practice, the package is invoked during concurrent program execution, where messages are directed to the concurrent manager log, and during interactive sessions, where output is directed to the debug log. Because the logging decision is evaluated per call, enabling or disabling tracing requires only the appropriate profile or system parameter change, with no code modification or package recompilation. The "print_fn_label" output commonly appears in debug logs when support personnel enable Receivables logging to trace the sequence of package execution during problem diagnosis.