Search Results put_names

Overview

APPS.POA_LOG is a utility package body in the Oracle E-Business Suite Procurement (POA) module family. It provides a lightweight logging and diagnostics framework used by Oracle Purchasing and related procurement programs to write status, progress, and error messages to the concurrent manager log and output files. The package abstracts direct calls to the FND_FILE API and adds convenience functions for formatted output and conditional debug tracing.

The package is not a business-transaction API; it does not create, validate, or post procurement documents. Instead, it is an internal infrastructure package whose primary purpose is to standardize how procurement programs report execution progress and diagnostic information to users reviewing concurrent request output. It is classified as OTHER in the ETRM metadata, reflecting its supporting rather than transactional role. A significant indicator of its ubiquity is that 24 other packages reference it, confirming that POA_LOG is a shared logging layer used broadly across the POA codebase.

Key Procedures and Functions

The documented package exposes seven procedures and functions:

• PUT_NAMES — Intended to configure the log and output directory and filenames used by the program. In the shipped source, the call to FND_FILE.PUT_NAMES is commented out and the procedure simply returns, so it acts as a placeholder retained for interface compatibility. Its behavior is only relevant when a program is not executed through the concurrent manager.
• DURATION — A function that converts a numeric duration expressed in days into a human-readable string of the form "x Days HH:MM:SS," making elapsed-time reporting in log output more legible.
• DEBUG_LINE — A procedure that writes a line of text only when the internal debug flag (g_debug) is enabled, allowing verbose tracing to be suppressed in normal production runs.
• PUT_LINE — A wrapper procedure that forwards text to FND_FILE.PUT_LINE using the FND_FILE.LOG target, standardizing log writing across calling programs.
• OUTPUT_LINE — Provides the analogous capability for the report output file, allowing messages to be directed to the concurrent request output rather than the log.
• SETUP — Initializes package state, typically establishing the debug flag and any session-level logging configuration before a program begins writing messages.
• WRAPUP — Performs end-of-run cleanup and finalization, ensuring buffered log content is flushed and the logging session is properly closed.

Tables Accessed

The ETRM metadata lists no table references for this package. POA_LOG operates entirely through the Oracle Forms file APIs (FND_FILE) and package-level variables. It does not read from or write to any database tables, which is consistent with its role as a pure logging utility rather than a data-processing component.

Usage Notes

POA_LOG is invoked from PL/SQL concurrent programs and other packaged code within the Procurement suite. The typical pattern is to call SETUP at the start of a program, use PUT_LINE for standard log messages and DEBUG_LINE for conditional trace output during processing, optionally use DURATION to report elapsed time, and call WRAPUP when processing completes.

Because it is referenced by 24 other packages, POA_LOG functions as a de facto shared logging convention for the POA module. Customizations that call POA_LOG procedures should respect the same lifecycle: initialize with SETUP, write through PUT_LINE or OUTPUT_LINE, and finalize with WRAPUP. Developers should note that PUT_NAMES is effectively a no-op in the shipped version, so directory and filename control for log files is governed by the concurrent manager rather than by this package. Direct calls to FND_FILE remain valid, but using POA_LOG keeps custom code consistent with Oracle's standard procurement logging behavior.