The SQL trace is about tracing database activity, which can also be useful finding the origin of your data...
A runtime analysis may be easy, but an SQL trace should never be forgotten about. Tracing SQL steps is done for any transaction, report or even different transactions or reports. It records any actions in the database, in any (all) sessions (your sessions). It can also be used to "trace" only part of a transaction, by timing when to switch it on and off again. The great thing about the SQL trace is that is can be switched on when you expect a program to select data, and switched off again immediately afterwards, leaving you with a short trace on the tables you were searching for.
SQL traces can be initiated from any menu: System > Utilities > SQL trace or transaction ST05. An SQL trace is linked to the used in a certain client, thus it is session-independent. Normally, you would open a new session and start the trace in there. No need to actually stop the trace to have a look at it, the "List trace" functionality works on the last trace or the currently active trace. However: leaving a trace on is performance consuming - and the trace will become so big it becomes useless.
Never underestimate the power of an SQL trace. Fast, efficient, accurate...