Search Results close_debug_session

Overview

APPS.ENG_CHANGE_ACTIONS_UTIL is a utility package in the Oracle E-Business Suite Engineering (ENG) module. Its primary business function is to support Engineering Change Management (ECM) by providing programmatic utilities for creating and maintaining change actions, manipulating change order lines, and driving Oracle Workflow notifications associated with engineering change orders. The package is classified as a UTIL object within ETRM, meaning it is intended to be called by other application objects rather than executed directly by end users. In addition to its change-management responsibilities, the package exposes a set of diagnostic routines—Open_Debug_Session, Close_Debug_Session, Write_Debug, and Get_Debug_Mode—that allow developers and support personnel to capture runtime trace output to a server-side file for troubleshooting. The header comment confirms the source file as ENGUCCMB.pls (version 120.3), and the package is referenced by four other packages, establishing it as a shared dependency within the Engineering transaction flow.

Key Procedures and Functions

• OPEN_DEBUG_SESSION — Initializes a debug session. It accepts an optional output directory and file name, defaulting the directory to the ECX_UTL_LOG_DIR profile option and the file name to a standard log name. It validates the directory against the database utl_file_dir parameter before opening the file and setting the internal debug flag.
• CLOSE_DEBUG_SESSION — Terminates the debug session and releases the UTL_FILE handle opened by Open_Debug_Session. This is the routine most commonly associated with the user search term "close_debug_session."
• WRITE_DEBUG — Writes a formatted debug message to the active debug file, provided a debug session has been opened and the debug flag is enabled.
• GET_DEBUG_MODE — Returns the current state of the package-level debug flag so callers can conditionally execute diagnostic logic.
• CREATE_CHANGE_ACTION — Creates a new change action record, forming the core business operation for adding actions to an engineering change order.
• UPDATE_WORKFLOW_INFO — Updates Workflow-related attributes associated with a change action, keeping the change record synchronized with its notification process.
• RESPOND_NOTIFICATION — Records a response to a Workflow notification linked to a change action, typically an approval or rejection action.
• GET_WORKFLOW_NOTIF_ID — Retrieves the Workflow notification identifier for a given change action so that notification status can be queried or acted upon.
• DELETE_LINE_ACTIONS — Removes line-level actions associated with a change order, supporting cleanup and revision of change line details.

Tables Accessed

The package operates against the Engineering change action tables through APPS synonyms. ENG_CHANGE_ACTIONS is the primary table read and written when creating, updating, and deleting change actions and their line-level counterparts. ENG_CHANGE_ACTIONS_S is the corresponding sequence-backed or shadow table used during insert operations to generate keys. DUAL is referenced for trivial single-row queries and validations. UTL_FILE and V$PARAMETER are accessed exclusively by the debug routines: V$PARAMETER supplies the utl_file_dir setting that Open_Debug_Session validates against, and UTL_FILE provides the file I/O primitives used to open, write, and close the debug log. No other application tables are documented as dependencies.

Usage Notes

ENG_CHANGE_ACTIONS_UTIL is an internal utility and is not intended for direct invocation by end users. It is typically called from Engineering change order forms, from Oracle Workflow notification handlers that process change action approvals, and from concurrent programs or custom extensions that need to create or maintain change actions programmatically. Custom code invoking the debug routines must ensure that the target log directory is registered in the utl_file_dir database parameter; otherwise Open_Debug_Session silently returns without enabling the debug flag. A corresponding Close_Debug_Session call should always follow an open session to flush and release the file handle. Because the package is referenced by four other packages, changes to its behavior can affect the broader Engineering Change Management workflow, and callers should rely on the published procedure signatures rather than internal globals.