SAP Note 11661 - Event-driven call of background jobs does not work.

Symptom

It is not possible to trigger a background job with an operating system event.

Cause and prerequisites

1. sapevt is not called correctly

2. Event is not defined in R/3

3. Profiles have not been maintained correctly

4. Message server can not be reached

Solution

Background jobs triggered by an operating system event in R/3 are called by program sapevt, which is located in
directory /usr/sap//SYS/exe/run.

1. The call is:
sapevt pf= or
sapevt name= nr=

In the latter case, the message "sapparam(1c): No Profile used." is issued. You can ignore this message.
You can also specify the following options:
-t writes trace file 'dev_evt' into local directory
-p

If a parameter is specified when scheduling an event-driven job, and the event is then called, the job is started only when sapevt is called with the relevant parameter.
If a parameter is not specified during scheduling, the job is always started when the event is called regardless of whether sapevt is called with a parameter or without.

Events are not saved; Instead, they start the jobs that have been released at the exact time of the call.

2. The event must be known in the SAP cystem (transaction SM62). Otherwise, the call has no effect.

3. Check whether the spelling of the event name being called exactly corresponds to the one in the SAP system. This is particularly important when long event names are used.

4. Check the profile parameters rdisp/mshost and rdisp/msserv in the default and instance profiles.

5. Check in UNIX /etc/services whether the message server has been defined. Example: sapmsBIN 3604/tcp

6. Check with ping whether the message server can be reached.

Additional key words

sapevt