Search Results sys_il0000098862c00020

Overview

APPLSYS.FND_LOG_MESSAGES is the central diagnostic logging table in Oracle E-Business Suite, holding the structured debug and trace output emitted by the FND_LOG instrumentation framework. Application code across Oracle EBS is sprinkled with calls that pass a log level, a module identifier, and a message to the FND_LOG package; when logging is enabled for the affected module and level, those calls write their output to this table. Administrators and developers then enable, disable, and inspect logging through the FND_LOG_VIEW package, typically invoked from the Oracle EBS login interface over HTTP. The table therefore serves as both a runtime troubleshooting resource and a historical trace of exception and diagnostic activity across the application tier.

The object is owned by APPLSYS, carries the FND design data reference FND.FND_LOG_MESSAGES, and is documented as VALID in ETRM 12.2.2 against the 12.1.1 / 12.2.2 code lines. It resides in the APPS_TS_TX_DATA tablespace with PCTFREE 5, and its indexes are split between APPS_TS_TX_DATA (the two LOB segments) and APPS_TS_TX_IDX (the B-tree indexes). The heuristic Data Vault classification mined from FK structure is standalone; in Data Vault modeling terms this object would most naturally be treated as a satellite rather than a hub or link, since it records descriptive event attributes rather than business keys or explicit many-to-many relationships. The classification should be regarded as a modeling suggestion only.

Key Information Stored

The table is dense with context columns. The most significant are:

• LOG_SEQUENCE — sequential identifier and part of the primary key.
• TIMESTAMP — the date/time the message was logged, and the leading column of the primary key FND_LOG_MESSAGES_PK (TIMESTAMP, LOG_SEQUENCE).
• MODULE — the source-code block identifier that produced the entry.
• LOG_LEVEL — severity of the message, from 1 (lowest) to 6 (highest).
• MESSAGE_TEXT — the logged message, up to 4000 characters.
• ENCODED — 'Y'/'N' flag indicating whether MESSAGE_TEXT stores an encoded Message Dictionary message rather than literal text.
• SESSION_ID and USER_ID — foreign keys to ICX_SESSIONS and FND_USER respectively, tying the entry to a user session.
• AUDSID — the database AUDSID; important because one database session may be shared by multiple ICX sessions.
• DB_INSTANCE — the database instance number.
• NODE, NODE_IP_ADDRESS, PROCESS_ID, JVM_ID, THREAD_ID — the application-tier execution context (server node, node IP, OS process, JVM, and Java thread).
• TRANSACTION_CONTEXT_ID, ECID_ID, and ECID_SEQ — transaction and execution-context identifiers used to correlate related entries.

The surrogate primary key is TIMESTAMP plus LOG_SEQUENCE. The documented unique indexes are the two LOB indexes, SYS_IL0000098862C00019$$ and SYS_IL0000098862C00020$$, on the APPS_TS_TX_DATA tablespace; these are internal LOB segments rather than true business keys, so no meaningful business-key candidate is documented for this table.

Common Use Cases and Queries

The primary use case is targeted diagnostics: a developer enables logging for a specific MODULE at a given LOG_LEVEL through FND_LOG_VIEW, reproduces an issue, then queries the table for the resulting entries. A typical pattern retrieves the most recent high-severity messages:

• Filter by MODULE and LOG_LEVEL, ordered by TIMESTAMP descending, to isolate a specific code path.
• Join to FND_USER on USER_ID to attribute entries to a named user.
• Group by TRANSACTION_CONTEXT_ID or ECID_ID to reconstruct a single logical transaction across nodes.
• Filter by NODE, PROCESS_ID, or JVM_ID to trace activity on one application-tier process.
• Use AUDSID and DB_INSTANCE to correlate application entries with database-side activity.

Index support is designed for these access paths: FND_LOG_MESSAGES_N4 on TRANSACTION_CONTEXT_ID, FND_LOG_MESSAGES_N5 on LOG_SEQUENCE, FND_LOG_MESSAGES_N7 on (TIMESTAMP, TRANSACTION_CONTEXT_ID), and FND_LOG_MESSAGES_N8 on (ECID_ID, ECID_SEQ). Reporting scenarios include volume analysis of error messages by module and period, and auditing of exception frequency across releases.

Related Objects

The most significant related objects are:

• FND_LOG — the PL/SQL package through which application code writes entries into this table.
• FND_LOG_VIEW — the package used by administrators and programmers to enable logging and view the data, commonly via HTTP.
• ICX_SESSIONS — joined via SESSION_ID to resolve the originating user session.
• FND_USER — joined via USER_ID to resolve the responsible application user.
• FND_LOG_MESSAGES_N4 / N7 — indexes supporting joins and lookups by TRANSACTION_CONTEXT_ID and TIMESTAMP.
• FND_LOG_MESSAGES_N8 — index supporting ECID-based correlation.
• FND_LOG_MESSAGES_PK — the primary key constraint underpinning unique row identification.

Because the object is classified as standalone, no foreign-key relationships to other business entities are documented; the relationships above are logical join paths through SESSION_ID, USER_ID, and the shared transaction context columns rather than enforced referential constraints.