Search Results set_trace_off

Overview

OKC_DEBUG is a diagnostic utility package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Contracts (OKC) product family and is classified under the generic API classification OTHER, indicating that it is not a business-facing public API but an internal instrumentation and tracing facility used across the Contracts module and its dependent code. Its primary business function is to provide developers and support engineers with a controlled mechanism for emitting diagnostic messages, indenting nested call output, capturing session context, and toggling trace behavior at runtime. Because it declares AUTHID CURRENT_USER, all unqualified object references resolve according to the invoking schema, which also means the package executes with the privileges of the caller rather than the definer — a deliberate design choice for a debugging utility that must be callable from arbitrary code paths without granting elevated privileges.

Key Procedures and Functions

The package exposes six documented procedures. Together they form a lightweight tracing framework rather than a functional business API.

• LOG — The central message emitter. It accepts a message plus optional level and module identifiers, allowing callers to classify the severity or verbosity of a message and tag it with the originating module (defaulting to 'OKC'). This is the procedure most commonly called inside other OKC packages.
• SET_TRACE_OFF — Disables trace output. This corresponds directly to the search term "set_trace_off" and is the documented switch used to stop diagnostic emission at runtime.
• SET_TRACE_ON — The complementary switch that enables trace emission, forming a paired on/off control with SET_TRACE_OFF.
• SET_INDENTATION — Increases or sets the indentation level used when formatting logged output, so that nested procedure calls appear visually nested in the trace log.
• RESET_INDENTATION — Returns indentation to its baseline, typically invoked when unwinding out of a nested call sequence.
• SET_CONNECTION_CONTEXT — Establishes session-level context information used by the logging routines, allowing trace output to be attributed to a specific runtime environment or connection.

The package additionally declares public variables including g_session_id, g_profile_log_level, and g_set_trace_off, which carry trace state across the session.

Tables Accessed

The only documented table reference is PLITBLM, reached through an APPS synonym. PLITBLM is the standard EBS profiler-related table traditionally associated with PL/SQL instrumentation and line-level tracing. Given the diagnostic nature of OKC_DEBUG, this reference supports the package's role in capturing and correlating trace information rather than storing business data. No Contracts business tables are documented as accessed by this package.

Usage Notes

OKC_DEBUG is an internal dependency of the Contracts codebase — ETRM records that it is referenced by 91 other packages, confirming that it is woven throughout OKC module code as an instrumentation layer rather than being called deliberately by end users. In practice it is invoked from within PL/SQL routines that wish to emit trace messages, and its SET_TRACE_ON and SET_TRACE_OFF procedures are toggled at runtime by developers or support personnel during debugging sessions. Because trace state is held in package globals such as g_set_trace_off and g_profile_log_level, the on/off state and verbosity apply for the duration of the database session. It is not surfaced through standard concurrent programs or forms; typical invocation is from custom code, SQL*Plus sessions, or internal OKC package calls where a developer needs visibility into execution flow without modifying production logic.