Last updated on SEPTEMBER 07, 2017
Applies to:Oracle Service Contracts - Version 11.5.10 and later
Oracle TeleSales - Version 126.96.36.199 and later
Oracle Marketing - Version 188.8.131.52 and later
Oracle Sales - Version 184.108.40.206 and later
Oracle Trade Management - Version 11.5.10 and later
Information in this document applies to any platform.
Sometimes, an Oracle application fails with an unexpected error, or a "silent" error or any other system failure and you need to get more information for Development to help troubleshoot an issue. In most cases you will be requested to provide an FND debug log. This note explains the steps needed to gather debug information from the FND debug tables, which you can then upload to a Service Request for review by Support or Development.
Starting in 11.5.10, FND has incorporated a debugging technique to enable debug messages to get stored into the table FND_LOG_MESSAGES. This method was introduced in 11.5.10 and it is available in subsequent releases. This note gives simple steps on how to enable and retrieve the debug messages.
This method will pick up *all* debug messages from a particular log_sequence value. As such, it is particularly useful when you are having trouble retrieving the debug messages associated to a particular concurrent request, or user. However, if there are multiple users with FND debugging enabled running various processes, you could end up picking up debug messages pertaining to their activities.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms