Beruflich Dokumente
Kultur Dokumente
A graphical user interface (GUI): The GUI is the interface through which
the Basis administrator interacts with SAP systems.
User and system administration and monitoring tools: These allow the
Basis administrator to maintain the integrity and performance of SAP
systems and address user concerns along the way.
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.
Example:
C:>sapevt ZFI_LOAD_INVOICES
pf=sapprdsapmntPRDsysprofiledefault.pfl
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
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.
Example:
<=""
style="border: 0px; max-width: 600px;">
<=""
style="border: 0px; max-width: 600px;">
As mentioned earlier, however, you can check for services and do many
other things that we would normally have to do at a command prompt
session or by executing a program outside the SAP application. Among
them is the ability to reboot a server, start a specific service, run a batch
file, etc.
Well, this is nice except for two problems: first of all, it is not available in old
SAP releases; secondly, it only provides the release level (e.g. 620, 640)
and not the compilation and patch levels, which are things we have to know
as well.
So, how do we go about getting the GUI release, compilation and patch
levels of all computers? We can use the SAPVER program (available as a
free download in SAP note 526199 at the SAP Support Portal web site) or
a Windows [support tool] utility such as FILEVER.exe.
The following script gets the SAPGUI version, compilation and patch level
of a computer and it puts the information into a flat-file called
"GUIversion.txt". The locations of the SAPVER tool and the flat-file are
controlled in variables "share" and "flatfile" respectively:
@echo off
:: GetSAPGUIversion.bat
set share=fileservertools
set flatfile=fileservertoolsGUIversion.txt
set guicomp=%errorlevel%
set guipatch=%errorlevel%
As you may already know, the command "NET VIEW" lists all the
computers on the current Windows domain. We can script FILEVER to loop
through each computer on the network and output the SAPGUI version
information into a flat-file.
@echo off
:: SAPGUIversion.bat
:: Requirement: FILEVER.exe
set FlatFile=sfc2k007sapssoSAPGUI.txt
:: Delete previous flat file if found.
if exist "%%i%GUIpath%" (
echo %%i%%a%%b
The script above filters the output of "NET VIEW" for all entries starting with
a double backlash (). The path to the SAPGUI executable is controlled in
variable "GUIpath". The output file is a tab-delimited flat file, which can be
easily imported into a spreadsheet or database program.