Search Results dump_line_detail_rec

Overview

APPS.CSI_T_GEN_UTILITY_PVT is a private (PVT) PL/SQL utility package that belongs to the CSI (Complex Maintenance, Repair and Overhaul / Enterprise Asset Management transaction) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is not a business-facing API; rather, it is an internal diagnostics and instrumentation toolkit used by other CSI packages. Its central purpose is to provide a consistent mechanism for debug message logging, structured record dumping, and error stack tracing during the execution of CSI transaction processing logic. The "T" in the name designates the transaction-processing layer of the CSI schema, and "_PVT" confirms an internal-only classification, meaning the package is not intended for direct invocation by external or customer code.

The most notable characteristic of this package — and the reason it is frequently encountered when administrators search for csi_logfile_path — is its use of the CSI_LOGFILE_PATH profile option. At initialization the package declares a directory global that resolves to nvl(fnd_profile.value('CSI_LOGFILE_PATH'), '/tmp'), meaning all debug output written by this utility is directed to the filesystem location defined in that profile option, defaulting to /tmp when the profile is unset. A second global reads the CSI_DEBUG_LEVEL profile option to control verbosity.

Key Procedures and Functions

• BUILD_FILE_NAME — Constructs the physical log file name from three caller-supplied segments, ensuring each debug session writes to a uniquely named file in the configured log directory.
• SET_DEBUG_ON / SET_DEBUG_OFF / IS_DEBUG_ON — Toggle and query the package-level debug flag, which governs whether subsequent ADD and dump calls actually emit output.
• ADD — Records a free-format debug message. This is the workhorse routine used liberally throughout dependent CSI packages to trace execution flow.
• DUMP_API_INFO — Writes package and API name information, with indentation, providing context headers in the log file.
• DUMP_ERROR_STACK — Two overloads (a procedure and a function returning a string) that capture and emit the PL/SQL error stack for diagnostic analysis of failures.
• Record dump routines — DUMP_TXN_SYSTEMS_REC, DUMP_TXN_LINE_REC, DUMP_LINE_DETAIL_REC, DUMP_PARTY_DETAIL_REC, DUMP_PTY_ACCT_REC, DUMP_II_RLTNS_REC, DUMP_ORG_ASSGN_REC, DUMP_TXN_EAV_REC, DUMP_CSI_EA_REC, and DUMP_CSI_EAV_REC each accept a strongly typed record from csi_t_datastructures_grp and format its contents for human-readable logging.
• Identifier dump routines — DUMP_LINE_DETAIL_IDS_REC, DUMP_PARTY_DETAIL_IDS_REC, and DUMP_PTY_ACCT_IDS_REC emit the corresponding ID records.

The package exposes 52 documented procedures and functions in total, following a uniform naming convention where every routine prefixed with DUMP handles a specific CSI transaction data structure.

Tables Accessed

The package does not query application tables. Its documented references are to the UTL_FILE built-in package, used to open, write, and close the log file in the directory defined by CSI_LOGFILE_PATH, and to PLITBLM, the internal PL/SQL table management package used by the PL/SQL runtime for bulk collection operations. Because output is directed to a database server file, DBAs must ensure the directory named in the profile option is accessible to the database process owner and permitted by UTL_FILE_DIR or a directory object.

Usage Notes

CSI_T_GEN_UTILITY_PVT is invoked internally by CSI transaction APIs rather than from Oracle Forms or concurrent program parameters. With 85 dependent packages, it is one of the most heavily reused utilities in the CSI transaction stack. Enabling diagnostic output requires setting the profile option CSI_DEBUG_LEVEL above zero and, where appropriate, invoking SET_DEBUG_ON; the resulting trace is written to the path resolved from CSI_LOGFILE_PATH. When that profile option is null, output silently falls back to /tmp, a common source of confusion when administrators search the file system for debug logs. Because the package is classified PVT, customizations should call the public CSI APIs instead and configure diagnostics through the supported profile options only.