Triggering Events from External Programs (SAP Library

Triggering Events from External Programs

Use the R/3 program SAPEVT to trigger an event from a program running outside the R/3 System.

The syntax for SAPEVT is as follows:

sapevt <EVENTID> [-p <EVENTPARM>] [-t]
pf=<Profile Name>|name=<R/3 System name> nr=<R/3 System Number>

Example: sapevt END_OF_FI_DATATRANS name=C11 nr=11 triggers the event END_OF_FI_DATATRANS without a parameter. The event is triggered in R/3 System C11, instance number 11. Any jobs that are waiting for this event are started.

The SAPEVT parameters are as follows:

<EVENTID> : The name of the event as defined in the R/3 System with transaction SM62.

-p <EVENTPARM> : An optional argument for the EVENTID which qualifies the event. The EVENTPARM is not defined in the R/3 System.

-t : Causes SAPEVT to log its actions in a short trace file. You can find the trace file in the current directory of the user who called SAPEVT.

pf=<Profile Name> or name=<R/3 System Name> nr=<R/3 System Number> : Either pf or name and nr identify the R/3 System in which the event is to be triggered.

At least one instance of the R/3 System must be active when SAPEVT runs. Otherwise, the System will not know that the event has occurred. The instance must have the number specified in the SAPEVT call.

In more detail, the parameters for identifying the R/3 System are as follows:

pf <Profile Name> : Enter the name of the profile with which the R/3 background processing instance(s) are started. SAPEVT identifies the R/3 System from the specifications in the profile.

You can find R/3 system profiles in the globally shared R/3 directory SYS\profile (Windows NT), or SYS/profile (UNIX).

name=<R/3 System Name> nr=<R/3 System Number> : The name of the R/3 System (SID) and the R/3 System number.

Requirements for Using SAPEVT

To use SAPEVT to trigger an event, the following requirements must be met:

An R/3 instance that offers background processing must be running or the start of jobs waiting on the event will be delayed.

If no instance in an R/3 System is active when an external program triggers an event, than the event is ignored, the R/3 System will not know that the event has occurred.

If a job that was scheduled to run when an event occurs cannot be started immediately, it is rescheduled as an immediate-start job. It will then be run at the earliest possible opportunity.

If SAPEVT is started with a profile name as an argument, then the program must have access to the shared profile directory of the R/3 System. SAPEVT needs to read the profile of the system to which it is sending the event.

If access to the directory is not possible, then you can create a local profile for SAPEVT. This profile need only contain values for the parameters rdisp/mshost and rdisp/msserv. Take the values from the profiles of the target R/3 System. Specify the local profile in the SAPEVT command line.

Network connection: SAPEVT must be able to establish a TCP connection to the R/3 instance.

SAPEVT reports problems in establishing a connection to the R/3 System in its log file.

User search path: The R/3 executables and profile directories must lie in the search path of the user who starts the program that calls SAPEVT.

UNIX: /usr/sap/<R/3 System ID>/SYS/exe/run and SYS/profile

Windows NT: \\<Host Name>\sapmnt\<R/3 System ID>\SYS\exe\run and SYS\profile