How to enable Diagnostics in Oracle Applications R12

Users may not able to able to see Help >Diagnostics option or get an error “Function Not Available to this Responsibility. Please check with your system administrator.”

These profiles need to be set at user level. So specific user can access this functionality (ex. Support folks/Developers)

Navigation: Go to System Administrator responsibility
Profile> System

Profile Option Name: Utilities:Diagnostics
User Level: Yes


Profile Option Name: Hide Diagnostics menu entry
User Level: NO

Save changes
Have user logout of Oracle Application and login again

User should be able to access Help >Diagnostics Menu



2 thoughts on “How to enable Diagnostics in Oracle Applications R12

  1. Hi Sir,

    I have used the same procedure but still the option is not enabled for me. Is there any other way of doing it. Please advise.


    • Make sure the Hidden Profile is set to no for the USER (User Level). If you trying to debug a form, you can try the below option.

      How to enable and retrieve FND debug log messages (Doc ID 433199.1)

      1) Set up profiles for the User / Responsibility to be used to reproduce the issue

      Responsibility: System Administrator
      Navigation: Profile > System

      Query up the Application, Responsibility, and User you will use to reproduce the issue you want to debug.
      For example:
      Application = Receivables
      Responsibility = Receivables Manager
      User = MYUSER1
      Profile = FND%Debug%

      sample setting to debug everything :

      FND: Debug Log Enabled YES
      FND: Debug Log Filename NULL
      FND: Debug Log Level STATEMENT
      FND: Debug Log Module %

      sample setting to debug ONLY Receivables :

      FND: Debug Log Enabled YES
      FND: Debug Log Filename NULL
      FND: Debug Log Level STATEMENT
      FND: Debug Log Module ar%

      2) Since the debugging routine will start writing messages to the table, we want to know which messages pertain to our test.
      a) If you are tracking the debug messages for a concurrent request, take note of the Concurrent Request id
      retrieve the current max value of log sequence as follows:


      3) Run your test case, try to stay on track in reproducing the issue and leave out extraneous steps so that you don’t end up with debug messages that are not relevant to your issue.

      4) If you run the script above to get the log_sequence, do it again now, after you have completed the steps to reproduce the issue:

      SELECT MAX(LOG_SEQUENCE) after_seq

      A. Retrieve the debug messages for a concurrent request ID:

      SELECT log.module, log.message_text message
      FROM fnd_log_messages log,
      fnd_log_transaction_context con
      WHERE con.transaction_id = &request_id
      AND con.transaction_type = ‘REQUEST’
      AND con.transaction_context_id = log.transaction_context_id
      ORDER BY log.log_sequence;

      b) Otherwise, retrieve debug messages using a log_sequence range:

      SELECT module, message_text
      FROM fnd_log_messages
      WHERE log_sequence between &before_seq and &after_seq
      ORDER BY log_sequence;

      6) Don’t forget to turn OFF debugging, otherwise, all your actions will be logged and this could impact the performance of the application.

      FND: Debug Log Enabled = NO


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s