Results for “fnd_log_transaction_context”

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

Overview

FND_LOG_TRANSACTION_CONTEXT is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite, and it is documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to store the context information for a transaction, meaning it captures the environmental and identity attributes that surround an activity executed by the EBS logging and diagnostic infrastructure — the user, responsibility, session, component, and related transaction identifiers that a runtime process was operating under when the transaction was recorded.

Because the table is documented as standalone under the heuristic Data Vault classification (mined from its foreign key structure), the modeling suggestion is that it behaves as an isolated or hub-like entity rather than as a dependent satellite or an associative link. Its only documented outbound foreign key is to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, which reinforces that the table primarily anchors transactional context rather than participating in a dense relational web. In practice the table supports the FND diagnostic and instrumentation framework, providing the descriptive context that complements log messages and profiling data generated by concurrent programs, forms sessions, and OAF pages.

Key Information Stored

The physical schema documented for 12.2.2 records 13 columns. The most significant are:

• TRANSACTION_CONTEXT_ID — the surrogate primary key and the business-key candidate, enforced by the unique index FND_LOG_TRANSACTION_CONTEXT_U1. Every context record is uniquely identified by this value.
• SESSION_ID — the session under which the transaction context was established, allowing contexts to be grouped by user session.
• TRANSACTION_TYPE and TRANSACTION_ID — the classification and identity of the transaction being contextualized, forming the business reference to the activity being logged.
• USER_ID — the application user associated with the transaction context.
• RESP_APPL_ID and RESPONSIBILITY_ID — the application and responsibility in effect, enabling responsibility-scoped analysis of logged activity.
• SECURITY_GROUP_ID — the security group, with a documented foreign key to FND_SECURITY_GROUPS.
• COMPONENT_TYPE, COMPONENT_APPL_ID, and COMPONENT_ID — identify the executing component, its owning application, and its internal identifier.
• PARENT_CONTEXT_ID — a self-referencing parent indicator used to express nesting or hierarchy among context records.
• CREATION_DATE — the timestamp at which the context row was created.

Common Use Cases and Queries

Typical scenarios include diagnosing user-reported errors by reconstructing the responsibility and session under which a transaction ran, auditing which components executed within a given responsibility, and correlating log output across sessions. A representative query joins the context to its security group:

• SELECT c.TRANSACTION_CONTEXT_ID, c.SESSION_ID, c.USER_ID, c.RESPONSIBILITY_ID, c.COMPONENT_TYPE, c.CREATION_DATE FROM FND_LOG_TRANSACTION_CONTEXT c WHERE c.TRANSACTION_ID = :transaction_id;
• SELECT c.*, g.SECURITY_GROUP_NAME FROM FND_LOG_TRANSACTION_CONTEXT c, FND_SECURITY_GROUPS g WHERE c.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID;
• Filter by SESSION_ID or USER_ID and constrain on CREATION_DATE to bound diagnostic reports to a time window.

Because contexts may nest via PARENT_CONTEXT_ID, recursive queries can reconstruct the full chain of context for a transaction.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; the only documented foreign key relationship.
• FND_LOG_MESSAGES — the companion logging table whose messages are interpreted alongside transaction context.
• FND_LOG_TRANSACTION_CONTEXT itself — referenced through PARENT_CONTEXT_ID for hierarchical context chains.
• FND_USER — supplies the user identity for USER_ID.
• FND_RESPONSIBILITY and FND_APPLICATION — resolve RESPONSIBILITY_ID and the application identifiers.