Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title FND Log Messages | Oracle EBS SQL Report
description – Oracle E-Business Suite SQL report
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, FND, Log, Messages, fnd_log_messages, fnd_log_transaction_context
permalink /FND%20Log%20Messages/

FND Log Messages – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

None

Report Parameters

User Name, Module, Module Contains, Logged within x Days, Date From, Date To, Log Level From, Log Level To

Oracle EBS Tables Used

fnd_log_messages, fnd_log_transaction_context

Report Categories

Enginatics

Related Reports

CAC Interface Error Summary, FND Messages, CST Inventory Value - Multi-Organization (Element Costs) 11i, FND Concurrent Requests 11i, FND Concurrent Requests, GL Summary Account Upload

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output FND Log Messages - Summary by month - Excel pivot 30-Aug-2025 152352.xlsx
Blitz Report™ XML Import FND_Log_Messages.xml
Full SQL on Enginatics www.enginatics.com/reports/fnd-log-messages/

Executive Summary

The FND Log Messages report provides access to the Oracle EBS debug log (FND Logging). It is the primary tool for diagnosing runtime errors and performance issues.

Business Challenge

  • Error Diagnosis: Finding the specific error message and stack trace when a user reports a "System Error".
  • Performance Tuning: Analyzing the timing of log messages to identify slow-running code blocks.
  • Security Audit: Reviewing login failures or access denials logged by the system.

The Solution

This Blitz Report queries FND_LOG_MESSAGES:

  • Message Text: The actual log entry.
  • Module: The code module (e.g., fnd.plsql.Security).
  • User: The user who triggered the message.
  • Level: The severity (Statement, Procedure, Event, Exception, Error, Unexpected).

Technical Architecture

The report queries FND_LOG_MESSAGES and joins to FND_USER for context.

Parameters & Filtering

  • User Name: Filter for logs generated by a specific user session.
  • Module Contains: Filter for specific code areas (e.g., %OAF%).
  • Log Level: Filter to see only Errors or Exceptions.

Performance & Optimization

  • High Volume: The log table can be massive. Always filter by Date and User/Module.
  • Retention: Logs are typically purged daily or weekly, so run this report soon after the issue occurs.

FAQ

  • Q: Why is the report empty?
    • A: FND Logging must be enabled via profile options (FND: Debug Log Enabled, FND: Debug Log Level) for messages to be written to the database.

Useful Links

© 2026 Enginatics