Until now, we have seen how we are able carry out the trace on our user, as well as without any restrictions. In this recipe, we will see how a trace may be carried out on other users along with additional imposed restrictions.
Problem areas may be difficult to find at first. One approach is to run an unrestricted trace in order to find out the problematic program/transaction or a user. We may then run a "restricted" trace focusing only on the particular program or user.
In addition, one more use of a restricted trace is when we run multiple programs/transactions in various sessions. We may run a time-consuming report of Finance (FI) module in one session, and at the same time, want to trace an HR transaction code, say PA30, in another session. We can then specify the transaction code of HR in the restriction criteria of a restricted trace. In this way, the trace records of the FI report that is running or any other activity in any session will not be included...