Analyzing Problems with Events 

Purpose

Problems can occur in jobs with the start time After event.

The analysis of these problems depends on whether the event was raised from within the SAP system or from outside.

Process Flow

If the event was raised from within the SAP system (for example, with the function module BP_EVENT_RAISE), you must check the name of the application server.

...

       1.      For processing events, an application server is specified in the profile parameter rdisp/btcname.

       2.      An event-based job scheduler is started on this server. This checks whether there is a job which is waiting for this event which has occurred (see Analyzing Parts of the Runtime Environment). It is important that the parameter rdisp/btcname contains the name of an active application server.

       3.      Execute the ABAP program RSPARAM on the server on which the event was raised. This program displays the values of all active profile parameters on the server.

       4.      Check whether the name specified in rdisp/btcname is found in the list on your application server.

       5.      Another possible cause of errors is an invalid event name. Check the system log for the server on which the event was raised for entries indicating this kind of an error (see Analyzing the Work Processes and System Log of an Application Server).

If the event was raised from outside the SAP system (via the evt program at the operating system level), record a trace and check the trace file.

       6.      If you want to raise events from outside the SAP system, that is, from the operating system level, you can do this with the SAP program evt (see also Starting External Commands and Programs).

       7.      If you specify the -t option when calling evt, then a trace file with the name dev_evt is created. If evt discovers any problems, you can read about these in the trace file.