When you work with SAP Enterprise Portal, sometimes it’s useful to use the System Trace tool, enabled by the ERP system. Typically, Portal applications use backend function modules (or BAPIs) for which they make constant execution calls via RFC (Remote Function Call). So, if you’re facing a problem with a Portal application, independent if it a standard ESS or MSS application or your own custom one, learn how to check which function modules are being executed, among other customizable information. Using this procedure will help you isolate an error and help you understand what happens in the “backstage” of portal applications.

1. Enter transaction code ST01.

2. Click on “Analysis” to access the options for the Trace Analysis program.

3. Configure the necessary parameters. In the example below, the trace records selected to be captured where “Kernel Functions” and “RFC Calls”. Tip: this procedure is also useful to perform Authorization Checks. In this case, we should only select “Authorization Check” from the Trace Records option list.

4. Go to the front-end and browse to the immediate point before you need to start capturing the trace records. This is important because as soon as you activate the trace, all actions will be stored in the log record. In the example, user would click in the standard Manager Self-Service Universal Worklist application

5. As soon as you have your browsing aligned in the front-end side, go back to ST01 and click on execute. Return to the Portal and click on the Universal Worklist link.

6. In ST01, click on “Analysis” to view the results. The result list will show something like the screenshot below. Notice that I’ve highlighted the standard function modules that were executed (SWN_UWL_GET_WORK and SYSTEM_RESET_RFC):

7. By double-clicking the Function Modules, you’ll be able to dig deeper and view more detailed information:

7. When you finish your analysis, don’t forget to switch off the trace analysis program. This is important because when the trace is active it will be gathering information at all times, which is a resource consuming operation: