Skip to end of metadata
Go to start of metadata

Following are some details about the SAP Event:

An SAP event is a "flag" that is created in SAP (SM62). This event (or flag) can be triggered (from a Unix job to an incoming file), causing a job to execute in the background. This event (or flag) can be triggered within R/3 or can be done at the Unix level.

First, create an event in SM62. It's easy - just create it under "user event names" and "maintain". You'll find the create option from there.
Once created go to SM36 and create the job. Put in the job name you want to call it - fill in the ABAP/4 program you'll want executed, but under "START DATE" select option AFTER EVENT. Then plug in your SAP event name you created. Fill in the remaining information on this screen and save.
Once saved, an entry is put in table BTCEVTJOB. The entry is the name of the event you raised. This is the system's way of keeping track of which jobs are in the queue waiting for an event to occur.
Now, once the event is triggered this newly created job will execute. The event can be triggered via sap (SM64) or at the Unix level.
SM64 is pretty self-explanatory. To get the event triggered from Unix:
-Log into the <SID>adm user id at the Unix level and go to directory /usr/sap/<SYSID>/SYS/exe/run (there is an alias called 'cdexe' that will get you there)
-From there look for an executable called sapevt. Open another Unix window cause now you are going to need to cut and paste.

-At the other sap window switch user to the <SID>adm user and go to the /usr/sap/<SYSID>/SYS/profile directory ('cdpro' is the alias)

-Do an "ll | more" and look for the instance profile name (the sapevt executable will want this!) Example: <SID>DVEBMGS00<SYSNAME>

-Go back to the sapevt window and enter this command to get the event to raise:
sapevt <event_name> -t pf=<instance_profile_directory_and_name> nr=<SYS_number>
Example: sapevt roberts_test -t pf=/usr/sap/<SID>/SYS/profile/<SID>DVEBMGS00<SYSNAME> nr=00

-This will raise the event, and cause the job scheduled within SAP to execute.
Once the job has executed the SAP event that was in the table BTCEVTJOB will disappear.
Another table, TABTCO, will now have an entry in it with the SAP job that was executed. Once you've found that job name in this table you can double click on its entry and see that it was executed via an event.
To set TRACE level WITHOUT bringing down the system:

Find the dispatcher process at the Unix level like this:
ps -ef | grep | more
In the third column look for the "child" process ID number that repeats itself over and over
Then verify that number to the number in the second column, which should be the parent PID number.
Then issue the Unix command: kill -usr3 parent-pid-number (to turn on level 3 trace)
kill -usr2 parent-pid-number (to turn on level 2 trace)
kill -usr1 parent-pid-number (to turn on level 1 trace)


To Transport Maintenance Dialogs, you need to enter the object(s) in the following manner in the command file:

R3TR TOBJ tablename .... (11th position) S

Function Group

Table Structure

And the entries for your table in TVDIR and TDDAT


To see if a rollback is occurring at the Informix database level, do the following:

onstat -u | more

Look for the letter "R" in the 3rd column under the "flags". "R" means rollback - "P" means primary - "X" means critical

  • No labels