|
Launching SAP transaction bypassing MAPI |
|
|
|
|
Written by Kevin Wilson
|
|
Saturday, 24 February 2007 |
This information describes a possibility to replace the complicated creation of "SAP Business Workflow" workitems inside R/3 and using MAPI service to provider to access it from outside R/3 by creating a simple datafile outside R/3 and sending this workitem-replacement via EMail.
First thing you should know before: It is possible to start a transaction, sending data to the first sreen and skip this screen by simply typing /* = in the transaction window of your SAPGUI, for example /*VA03 VBAK-VBELN=12000001
Now this is not very user friendly, but now there is a possibility to put this action into an icon and start it by double-clicking on it or just pulling it onto your already opened SAPGUI!
All you have to do is to create a text file with the extension ".SAP" for example "VA03.SAP". The content of this file should look like this (example for a system called DEV and a user named TESTUSER, that should use transaction VA03 to view Nr. 12000001 jumping into this transaction automatically):
[System]
Name=DEV
Client=010
Description=Development
[User]
Name=TESTUSER
Language=EN
Password=
[Function]
Command=*VA03 VBAK-VBELN=12000001
Title=Order
Type=Transaction
You can edit it by right mouse clicking the icon an choosing "edit".
Now to the workflow part: You can create this sort of datafile manually or by any programming language and send it to anyone who can be reached via EMail. Just tell them that to do with this item ("put it on the desktop and double-click it or pull it onto your already opened SAPGUI") and all he has to know is his R/3 password to log in. No MAPI service provider and no workflow
programming is needed to do that - however it is already a simple notification workflow!
Related Items:
|
ABAP Tips - System Fields, Program Types, Screen Types, ...
Developing a BAPI and Calling it with JCo
Taking you through ALE
SAP Order Status tables and Doc Flow table
E-Book - ABAP Programs (1449)