Screen transactions from Workflow

Dart, Jocelyn jocelyn.dart at sap.com
Fri Aug 9 02:47:44 EDT 2002


Hi Kevin/Lola,
Using an event is infinitely preferable to using GPA/SPA parameter ids
- you cannot rely on GPA/SPA parameter ids as they are affected by
other sessions the user has open not just the current call.
I wouldn't even rely on GPA/SPA in an ABAP program - they are only
intended for defaulting in values and that's it.
 
Once you have the event you can of course access any data linked
to the event object via its attributes - a much safer and reliable
option.  The documentation on events in the SAP Library help is
extensive and worth reading - plus it includes tutorials for
configuring events.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
* jocelyn.dart at sap.com
* +61 412 390 267
7 +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Lola Oluwa [mailto:Lola.Oluwa at outokumpu.net]
Sent: Friday, 9 August 2002 3:52 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Screen transactions from Workflow
 
 
 
One way is by using  parameter ids. If you are not familliar with ABAP
statements, I suggest that you take a look at some example of how this is
done from the standard SAP objects. Object BKPF, method create is an
example.Use transaction SWO1.
 
The above is not a fool-proof method depending on what exaclly your
scenairo is. Could you detail the scenairo you are implementing a bit more?
 
If you are familliar with ABAP, then you could consider generating an event
after the end user has executed an action (I have only used this in the
OPEN_FI interface). Here you can uniquelly capture each end-user's action
from the system fields and application tables. In your workflow, you could
then wait for this event or use the event as a trigger.
The rule-of-thumb (for me) for when implementing own
workflows/tasks/methods, is to use as guidelines  SAPs'  implementation of
simillar scenairo.
 
Good luck!
 
Lola.
 
 
 
                    "May, Kevin"
                    <KMay at petro-canada.c        To:     SAP-WUG at MITVMA.MIT.EDU
                    a>                          cc:     (bcc: Lola Oluwa/Outokumpuext)
                    Sent by: SAP                Subject:     Re: Screen transactions from Workflow
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    08.08.2002 16:39
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
Hi Lola,
Thanks for your help.  However, now I have another question.  How can I
access variables in the task container from the screen called in the object
method?
 
Thanks,
 
Kevin
 
-----Original Message-----
From: Lola Oluwa [mailto:Lola.Oluwa at outokumpu.net]
Sent: Wednesday, August 07, 2002 8:25 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Screen transactions from Workflow
 
 
 
Hi May,
Here is one way to do it (a very simple example):
   Create own Object method .
   In the method  call your transaction. eg:
 
begin_method create changing container.
 
  CALL TRANSACTION 'MIRO'.
 
 
end_method.
 
 
   Create your task and select the object and method you have defined. It
   is that simple!
 
You will of course need to define  input parameters if you need to pass
initial data to your transaction. Export parameters are also needed if you
need to pass back some values to your workflow.
 
Hope this helps.
 
Lola.
 
 
 
 
                    "May, Kevin"
 
                    <KMay at petro-canada.c        To:
SAP-WUG at MITVMA.MIT.EDU
                    a>                          cc:     (bcc: Lola
Oluwa/Outokumpuext)
                    Sent by: SAP                Subject:     Screen
transactions from Workflow
                    Workflow
 
                    <Owner-SAP-WUG at MITVM
 
                    A.MIT.EDU>
 
 
 
 
 
                    07.08.2002 14:52
 
                    Please respond to
 
                    "SAP Workflow Users'
 
                    Group"
 
 
 
 
 
 
 
 
 
Hi,
I would like to know if it's possible to call a screen transaction from a
workflow task.  If it is, could someone please explain the steps required
to
do this.
 
Thanks,
 
Kevin
 
 
                         ********************
 
This email communication is intended as a private communication for the
sole
use of the primary addressee and those individuals listed for copies in the
original message. The information contained in this email is private and
confidential and if you are not an intended recipient you are hereby
notified that copying, forwarding or other dissemination or distribution of
this communication by any means is prohibited.  If you are not specifically
authorized to receive this email and if you believe that you received it in
error please notify the original sender immediately.  We honour similar
requests relating to the privacy of email communications.
 
Cette communication par courrier ilectronique est une communication privie
`
l'usage exclusif du destinataire principal ainsi que des personnes dont les
noms figurent en copie.  Les renseignements contenus dans ce courriel sont
confidentiels et si vous n'jtes pas le destinataire privu, vous jtes avisi,
par les prisentes que toute reproduction, tout transfert ou toute autre
forme de diffusion de cette communication par quelque moyen que ce soit est
interdit.  Si vous n'jtes pas spicifiquement autorisi ` recevoir ce
courriel
ou si vous croyez l'avoir regu par erreur, veuillez en aviser l'expiditeur
original immidiatement.  Nous respectons les demandes similaires qui
touchent la confidentialiti des communications par courrier ilectronique.
 
 
 
 
                         ********************
 
This email communication is intended as a private communication for the
sole
use of the primary addressee and those individuals listed for copies in the
original message. The information contained in this email is private and
confidential and if you are not an intended recipient you are hereby
notified that copying, forwarding or other dissemination or distribution of
this communication by any means is prohibited.  If you are not specifically
authorized to receive this email and if you believe that you received it in
error please notify the original sender immediately.  We honour similar
requests relating to the privacy of email communications.
 
Cette communication par courrier ilectronique est une communication privie
`
l'usage exclusif du destinataire principal ainsi que des personnes dont les
noms figurent en copie.  Les renseignements contenus dans ce courriel sont
confidentiels et si vous n'jtes pas le destinataire privu, vous jtes avisi,
par les prisentes que toute reproduction, tout transfert ou toute autre
forme de diffusion de cette communication par quelque moyen que ce soit est
interdit.  Si vous n'jtes pas spicifiquement autorisi ` recevoir ce
courriel
ou si vous croyez l'avoir regu par erreur, veuillez en aviser l'expiditeur
original immidiatement.  Nous respectons les demandes similaires qui
touchent la confidentialiti des communications par courrier ilectronique.
 


More information about the SAP-WUG mailing list