Triggering jobs inside and outside SAP

SM62 is used to create SAP events, transaction SM64 is used to trigger SAP events within the application, and SAPEVT.exe is used to trigger SAP events while outside the application. Transaction SM36 is used to create background jobs and transaction SM37 is used to monitor and manage background jobs.

Transaction SM62 -- Define events You can create and display "User Event Names" via SM62. Although user event names don't have to start with the letter "Z", I recommend you use it to quickly differentiate between predelivered SAP events and your own. Example:

An event by itself doesn't do anything. A background job needs to be defined and configured to wait for the event. Therefore, you create the background job via SM36 and specify the new event name as the "Start Condition". Example:

Notice that the new background job can be defined as a periodic job. This allows you to trigger the job in the future as opposed to one time only. Transaction SM64 -- Trigger events within SAP To trigger an event, run transaction SM64 and specify the event name. Example:

Executable SAPEVT SAPEVT.exe is part of the R/3 Kernel and located under the usrsapsysexerun directory on the central instance. The syntax is as follows: sapevt &ltEventName> pf=&ltPath_to_Default_Profile> Example: C:>sapevt ZFI_LOAD_INVOICES pf=sapprdsapmntPRDsysprofiledefault.pfl SAPEVT is a stand-alone executable that can be copied into remote computers. That's right! You can execute an event right from your laptop or desktop computer. So, is there anything else required on the remote computer besides the executable? Yes. You need to have an entry in the "services" file with the TCP port for the SAP messenger of the SAP instance. You can edit the file with Notepad or any plain-text editor and add the necessary entry at the end. The file is located under the %systemroot%system32driversetc directory. Example: C:>notepad windowssystem32driversetcservices Add the line below and save the file: sapmsPRD 3600/tcp Also, please notice that you need to have read access to the "default.pfl" file on the SAP instance.

Now that you know how to trigger events to kick off SAP jobs you can smile every time an interface job is needed.