Component : Background Processing -

Solution : https://service.sap.com/sap/support/notes/11661 (SAP Service marketplace login required)

Summary :
The issue addressed concerns the inability to trigger background jobs using an OS event. The cause could be improper sapevt invocation, undefined events in R/3, unmaintained profiles, or the unreachable message server. The solution involves using the sapevt program located in /usr/sap//SYS/exe/run. The call format is sapevt pf= or sapevt name= nr=. Additional options include -t for trace file and -p for parameters. The event must be defined in transaction SM62. Ensure the event name matches exactly and verify profile parameters, message server definition in /etc/services, and connectivity with ping.

Key words :
located indirectory /usr/sap/<sid>/sys/exe/run, sapevt <eventid> pf=<profile>      orsapevt <eventid>, reached solution background jobs triggered, additional key words sapevt, writes trace file 'dev_evt', profile parameters rdisp/mshost, =<sid> nr=<instance>, long event names, operating system event, event-driven job

Related Notes :

449270

Job RDDIMPDP is not triggered by sapevt