Obtaining debug log output

The chapter provides you with instructions on how to generate debug log files. If raising a support call, you will often be asked to perform the steps outlined below; they can also be useful for testing when developing custom extensions.

Turning on logging

If a REST API exhibits unexpected behavior the user will most likely see a generic, user-friendly message explaining that a problem has occurred. The REST APIs use FND Logging to capture details of the run-time program units, their sequence, and values of parameters and variables. During development and testing, it is recommended that you set the following profile options:

• Set FND: Debug Log Enabled to Yes at Site Level
• Set FND: Debug Log Level to Error at Site Level

You will need to clear the cache using the Functional Administrator responsibility:

Functional Administrator: Core Services: Caching Framework: Global Configuration: Clear All Cache

This will ensure that any unexpected problems that occur, together with the user's context at the time of the error, are logged in fnd_log_messages.

Getting log output

With logging enabled perform the actions you wish to investigate. For product errors, reproduce the error or behavior for which you wish to create the log output.

To retrieve the log output, run the following query:

  SELECT *
  FROM fnd_log_messages
  WHERE module like 'xxas%'
  ORDER BY log_sequence desc;