How To Collect FND Diagnostics Trace (aka FND:Debug)
(Doc ID 372209.1)
Last updated on SEPTEMBER 07, 2018
Applies to:Oracle Applications Framework - Version 126.96.36.199 to 12.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Explain how to gather a FND Global Diagnostics trace - Generic steps and troubleshooting tips.
If a concurrent request is failing, you can diagnose the cause via a Concurrent Request trace. See <Note 123222.1>.
If a program is failing when it touches the database, you can diagnose the cause via an SQL. There are several notes and white papers on this. See for example <Note 130182.1>, Section 1.
If a particular user gets an error, you can gather a User Event Trace. See section 2c "Trace ALL user actions" in <Note 296559.1> .
But increasingly in E-Business Suite, there are situations where none of these serve the purpose. When an error occurs when users click a particular button without launching a concurrent request or touching the database. This is where a Global Diagnostics Trace should help you. This note has been created to tell you a way of diagnosing that, for analysis by a DBA, Oracle Consultant or Support Engineer, or for uploading to a bug for analysis by Development.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document