Search Results dump_rel_rec

Overview

CSI_GEN_UTILITY_PVT is a private PL/SQL package in the APPS schema that provides the shared diagnostic and utility infrastructure for the Oracle E-Business Suite Convergence and Supplier Integration (CSI) product family. Its principal business function is not transactional processing but observability: it supplies the mechanisms by which CSI APIs and batch programs record trace information, capture error stacks, honor installation-level tracing parameters, and serialize the contents of the CSI data structures for inspection. The package is classified as PVT in ETRM, indicating that it is an internal implementation package rather than a published API, and direct invocation by customer extensions is unsupported. The header comment (csivgus.pls 120.4.12000000.2) reflects a file last revised in 2007, and the package remains present and functional through EBS 12.1.1 and 12.2.2. With 46 documented procedures and functions and references from 52 other packages, CSI_GEN_UTILITY_PVT is one of the most widely reused internal dependencies in the CSI codebase.

Key Procedures and Functions

The package exposes three functional groups. The first is generic tracing and logging:

• PUT_LINE — writes an arbitrary message line to the repository trace output.
• ENABLE_TRACE — accepts a trace flag and returns a status value controlling whether tracing is active.
• DUMP_ERROR_STACK — returns the formatted PL/SQL error stack for diagnostic reporting.

The second group serializes typed records and collections from CSI_DATASTRUCTURES_PUB, allowing developers to inspect in-memory payloads during debugging. Documented dump procedures include DUMP_TXN_REC, DUMP_TXN_TBL, DUMP_TXN_QUERY_REC, DUMP_TXN_SORT_REC, and DUMP_TXN_ERROR_REC for the transaction structures; DUMP_REL_REC, DUMP_REL_TBL, and DUMP_REL_QUERY_REC for relationship structures; DUMP_SYS_REC, DUMP_SYS_TBL, and DUMP_SYS_QUERY_REC for system structures; and DUMP_EXT_ATTRIB_REC for extended attributes. The third group covers instance-oriented structures and includes DUMP_INSTANCE_REC, DUMP_INSTANCE_QUERY_REC, DUMP_INSTANCE_HEADER_REC, DUMP_INST_PARTY_ID, and DUMP_INSTANCE_ASSET_REC. The user query for dump_instance_query_rec corresponds to the documented procedure at lines 58–59 of the package specification, which accepts a parameter declared as csi_datastructures_pub.instance_query_rec and emits its field values for diagnostic review.

Tables Accessed

The package operates against a small set of documented dependencies. CSI_INSTALL_PARAMETERS is read to resolve installation-level configuration—notably the g_cse_install and trace-related global settings that determine whether debugging output is produced. PLITBLM, the standard Oracle package line buffer table, backs PUT_LINE and the dump routines. UTL_FILE is invoked to direct debug output to a server-side file, consistent with the globals g_debug_level, g_debug_file, and g_debug_file_path declared in the specification. V$SESSION is queried to obtain session context, including the auditing session identifier retained in g_audsid, which allows trace output to be correlated to a specific user session. The package does not maintain application tables of its own.

Usage Notes

CSI_GEN_UTILITY_PVT is invoked indirectly rather than directly. The 52 downstream packages that reference it call the dump and trace routines at decision points, error handlers, and loop boundaries so that operations can be diagnosed without a debugger. Typical consumers include the CSI instance, transaction, and relationship processing APIs, which pass their working records to the appropriate dump routine when debug level is elevated. Tracing behavior is governed by installation parameters and by the session-level debug globals set at package initialization. Because the package is a PVT object, it is not exposed through Oracle Forms or standard concurrent program parameters and carries no security or grant structure for end users. Custom code should treat it as read-only diagnostic infrastructure: use ENABLE_TRACE and PUT_LINE only in development or controlled troubleshooting scenarios, and expect the output destination to follow the UTL_FILE path defined at initialization.