It’s hard to be a complete Oracle Applications Consultant, unless you know the enough tricks to debug Oracle eBusiness Suite. Some of the debugging techniques in EBS are documented, but yet many of the very practical debugging techniques aren’t documented anywhere.

In this article, we will see PowerPoint presentations to debug Oracle Forms in eBusiness Suite.

Where do we start?If you wish to debug and know SQL & DML Statements that get executed from Oracle Form, then it is best to run the SQL*Trace for that forms session. However you must keep in mind that pl/sql statements like IF THEN ELSE etc never get captured in the SQL*Trace. To debug those, you are at the mercy of there being enough FND_Log messages that exist to capture execution points.

What are the various techniques that can be applied to debug Oracle Forms?1. Run SQL Trace to debug Oracle Forms. Have a look at this PowerPoint presentation for a practical example. In this example, we try to answer a question such as “Why that LOV [List of Values in EBS D2K screen] not bringing back the desired records”?Click here to see the presentation for the demo of this technique

3. Use FND Logging to debug messages in Oracle form Triggers and in the attached pll files. This technique will also give you insight of the debug messages generated from Pl/SQL or Workflows or business events, in case any of these were invoked as a result of an action in Oracle Forms.Understanding Common FND Logging

There are further techniques that can be applied [like those based on FND_Messaging], but I shall discuss those in future series of debugging articles.