Results for “itg_debug_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.ITG_DEBUG_PUB is a public PL/SQL utility package in the Oracle E-Business Suite application schema, delivered as part of the Integration Tools/Enterprise Transaction Management (ITG/ETRM) product family. Its purpose is to provide a centralized, reusable debugging framework for the ITG integration stack, particularly the inbound and outbound synchronization APIs that exchange supplier, item, field, and exchange data with external trading partners.

The package is classified with an API classification of PUB, indicating it is intended for direct invocation by other application code rather than being a private helper. It carries a documented status of VALID and is present in both 12.1.1 and 12.2.2 environments.

Functionally, ITG_DEBUG_PUB exposes a lightweight, session-scoped debug buffer. Application routines call it to register their current processing state, accumulate diagnostic messages, and later replay or inspect that information. Because the package reads its enablement state from a profile option and can write output through UTL_FILE, it allows developers and support staff to trace integration execution without modifying the calling code.

Key Procedures and Functions

The ETRM metadata documents 14 subprograms in the package. The principal ones are:

• SET_DEBUG_MODE — Master switch that configures whether debugging is active for the current session.
• INITIALIZE — Sets up the internal debug structures, clearing index position and buffer state so a new trace can begin.
• DEBUG_ON / DEBUG_OFF — Explicitly enable or disable debug capture at runtime, independent of profile settings.
• ISDEBUGON — Returns whether debugging is currently enabled; used by callers to guard expensive message construction.
• GETDEBUGCOUNT — Returns the number of debug entries accumulated in the current buffer.
• ADD — Appends a debug message to the internal buffer.
• GETFIRST / GETNEXT / GETNEXTBUFFER — Iteration routines that walk the stored debug entries, supporting ordered retrieval for display or logging.
• RESETINDEX — Resets the read cursor so iteration can restart from the beginning.
• SETDEBUGLEVELFROMPROFILE — Initializes the debug level from the configured profile option, giving administrators central control.
• SETDEBUGLEVEL — Sets the debug level programmatically.
• A remaining numbered entry (2) is catalogued in the metadata but not individually named in the excerpt.

Tables Accessed

• CLN_DEBUG_S — The persistent debug repository; the primary table this package reads from and writes to when storing or retrieving trace records.
• DUAL — Used for scalar evaluations and profile lookups in the SELECT list.
• UTL_FILE — Not a table but the PL/SQL file I/O package, referenced via synonym; used to write debug output to server-side files.
• PLITBLM — An internal PL/SQL table structure used for in-memory buffering of messages.

Usage Notes

ITG_DEBUG_PUB is not exposed to end users through standard Oracle Forms; it is invoked programmatically. Its documented dependents confirm this: ITG_BOAPI_UTILS, ITG_BOAPI_WRAPPERS, ITG_OUTBOUND_UTILS, ITG_SETUP, ITG_SYNCCOAINBOUND_PVT, ITG_SYNCEXCHINBOUND_PVT, ITG_SYNCFIELDINBOUND_PVT, ITG_SYNCITEMINBOUND_PVT, ITG_SYNCSUPPLIERINBOUND_PVT, and ITG_WF_UTILS all reference it. It also references itself and FND_API and FND_PROFILE.

Typical invocation occurs inside the ITG synchronization concurrent programs and workflow utilities. Administrators enable tracing by setting the relevant FND_PROFILE option, after which SETDEBUGLEVELFROMPROFILE picks up the value automatically. Support engineers use GETFIRST/GETNEXT iteration to dump accumulated messages when diagnosing partner integration failures.