Search Results fnd_concurrent_debug_info




Overview
Explore in AI Chat

Overview

FND_CONCURRENT_DEBUG_INFO is a table owned by the APPLSYS schema in the Oracle E-Business Suite FND (Application Object Library) product. It stores debug information that is captured when specific debug mechanisms are activated at the request of an Oracle developer. The table is classified as VALID and is present in both release 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the mined foreign key structure suggests a link classification, since the table records associations between session, user, and login identities together with the diagnostic events they produce. This classification should be treated as a heuristic modeling suggestion rather than a normative definition.

Key Information Stored

The documented physical schema comprises 16 columns. The primary key is defined by the constraint FND_CONCURRENT_DEBUG_INFO_PK over the composite of SESSION_ID, USER_ID, and LOGIN_ID. These three columns constitute the surrogate identifier for a debug record; because they are a composite primary key rather than a single generated value, they are also the principal business-key candidates for the row.

  • SESSION_ID, USER_ID, LOGIN_ID — the composite primary key identifying the session, database user, and login context in which debug output was captured.
  • FUNCTION, TIME, ACTION, MESSAGE — the diagnostic payload, describing the debugged function or event, its timestamp, the action performed, and the associated message text.
  • TIME_IN_NUMBER — a numeric representation of the event time, supporting ordering and interval calculations.
  • SECURITY_GROUP_ID — the security group context, referencing FND_SECURITY_GROUPS.
  • RESP_APPL_ID and RESPONSIBILITY_ID — the application and responsibility under which the concurrent activity executed.
  • PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID — the concurrent program and its owning application.
  • CONCURRENT_QUEUE_ID — the concurrent queue associated with execution.
  • TRANSACTION_ID and SOURCE_TYPE — the transaction reference and the origin classification of the debug record.

Common Use Cases and Queries

This table is primarily consulted during developer-initiated diagnostics of concurrent processing. A typical query retrieves the most recent debug messages for a specific user session:

SELECT session_id, user_id, login_id, time, function, action, message FROM applsys.fnd_concurrent_debug_info WHERE session_id = :session_id ORDER BY time_in_number;

Common scenarios include isolating the message sequence leading to a failed concurrent request, correlating debug output to a specific concurrent program or responsibility, and reporting on debug activity by source type. Because the table can accumulate significant volume, reporting queries should always be bounded by session, login, or time range.

Related Objects

  • FND_USER — referenced through FND_CONCURRENT_DEBUG_INFO.USER_ID, providing the user identity for each debug record.
  • FND_LOGINS — referenced through FND_CONCURRENT_DEBUG_INFO.USER_ID, linking debug output to the login session.
  • FND_SECURITY_GROUPS — referenced through FND_CONCURRENT_DEBUG_INFO.SECURITY_GROUP_ID, supplying security group context.
  • FND_CONCURRENT_REQUESTS — the natural parent for concurrent execution data, joining via CONCURRENT_PROGRAM_ID and request identifiers.
  • FND_CONCURRENT_PROGRAMS — joined via CONCURRENT_PROGRAM_ID and PROGRAM_APPLICATION_ID to resolve program names.
  • FND_RESPONSIBILITY — joined via RESPONSIBILITY_ID and RESP_APPL_ID to resolve the active responsibility.