Search Results record_process_exception

Overview

APPS.CN_UTILS is a shared utility package in the Oracle EBS Oracle Projects (formerly Oracle Projects/Costing) schema, delivered under the CN product family. Its primary role is to provide low-level programmatic helpers for constructing, formatting, and emitting PL/SQL source text and for managing module-level metadata within the CN_* repository tables. The package is declared with AUTHID CURRENT_USER, meaning that privileges on the tables it touches are resolved against the invoking schema rather than the package owner, which is an important consideration for any custom code that calls it.

The package exists largely to support the internal code-generation and repository-maintenance subroutines used by the CN modules and their dependency tracking. The CLIENT "dump_line" search term maps directly to the DUMP_LINE procedure, which is part of the family of text-emission helpers (APPEND, APPIND, APPENDCR, APPINDCR, STRIP, STRIP_PREV, DUMP_LINE). Together these routines manage a code_type record — a structured buffer containing object_id, line, indent, and text (VARCHAR2 or CLOB) — used to assemble source lines with proper indentation before persistence.

Key Procedures and Functions

The package exposes a documented surface of 52 procedures and functions. The most significant groups are:

• Session context: SET_ORG_ID and UNSET_ORG_ID — establish or clear the multi-org context for subsequent repository operations.
• Repository maintenance: DELETE_MODULE removes stale rows from CN_SOURCE and CN_MOD_OBJ_DEPENDS for a supplied module and its spec/body objects.
• Buffer initialisation: INIT_CODE (two overloads, one for code_type and one for clob_code_type) loads text, indent, and line values for a named object.
• Indentation control: INDENT and UNINDENT adjust or reverse indentation according to a nesting_level argument, keeping generated source aligned.
• Line emission: APPEND, APPIND, APPENDCR, and APPINDCR add text with optional indentation and carriage returns; STRIP and STRIP_PREV remove trailing or previously appended content; DUMP_LINE writes a completed line to its destination.
• Process auditing: RECORD_PROCESS_START, RECORD_PROCESS_SUCCESS, and RECORD_PROCESS_EXCEPTION write lifecycle rows to the CN_PROCESS_AUDITS tables.
• Package scaffolding: PKG_INIT, PKG_END, PKG_END_BOILERPLATE, and PROC_INIT emit the canonical header/footer boilerplate for generated packages and procedures.

The precise parameter lists are intentionally not enumerated here; consumers should reference the package specification before calling these routines from custom code.

Tables Accessed

Through APPS synonyms, CN_UTILS reads and writes a focused set of repository tables:

• CN_OBJECTS, CN_OBJECTS_S, CN_MODULES, CN_MOD_OBJ_DEPENDS, CN_MOD_OBJ_DEPENDS_S — describe the module/object structure and inter-object dependencies that DELETE_MODULE and the init routines rely upon.
• CN_SOURCE, CN_SOURCE_ALL, CN_SOURCE_S — store the generated or stored source lines manipulated by the APPEND/DUMP_LINE family.
• CN_REPOSITORIES — groups the modules within a given repository.
• CN_EVENTS — records lifecycle events emitted during generation.
• CN_PROCESS_AUDITS, CN_PROCESS_AUDITS_S — capture start/success/exception records written by the audit procedures.
• CN_DIM_HIERARCHIES and CN_PERIOD_STATUSES_ALL — supporting reference data used by the broader CN utility context.
• DBMS_LOB — invoked for CLOB-based code_type handling (clob_code_type overloads).

Usage Notes

CN_UTILS is an internally oriented helper package rather than a business-facing API; the ETRM classification is OTHER. It is referenced by nine other packages in the CN schema and is normally invoked from within those packages rather than directly from Forms or concurrent programs. Custom developers who need to generate PL/SQL source into the repository, or who need to record process-audit rows, can call it, but should first invoke SET_ORG_ID (and matching UNSET_ORG_ID) to establish the correct multi-org context. Because the package uses AUTHID CURRENT_USER, any calling schema must hold direct grants on the underlying CN_* tables. The presence of the clob_code_type overloads indicates use in environments where source text exceeds the VARCHAR2 limit, underscoring the package's role as a scalable text-emission engine within the CN repository toolchain.