AW: AW: Executing a dialog transaction in background from a workf low

Tue Oct 14 11:31:36 EDT 2003

Tomasz and Phil,

Thanks for the info. As you can see I'm more a workflow developer than an ABAP consultant (and who understands
the importance of ABAP knowledge when developing workflows).

Regards,

Fred

"Zmudzin,Tomasz,FRANKFURT,Extern LG-DM" wrote:

> As long as you have control of how the report is called, you can use
>
>   submit ZMYREPORT to sap-spool
>
> or
>
>   SUBMIT ZMYREPORT AND RETURN EXPORTING LIST TO MEMORY.
>
> More details on
> http://help.sap.com/saphelp_46c/helpdata/en/d3/2e974d35c511d1829f0000e829fbf
> e/frameset.htm
>
> (Calling Executable Programs --> Affecting Lists in Called Programs)
>
> Best regards,
> Tomasz
>
> -----Ursprungliche Nachricht-----
> Von: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
> Gesendet: Dienstag, 14. Oktober 2003 13:57
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Re: AW: Executing a dialog transaction in background from a
> workflow
>
> Tomasz,
>
> Thank you for your help!
>
> The messages that are generated by the transaction (report) are now stored
> in i_messages, but another problem I
> bumped into is related to the fact that the report also produces some output
> that is displayed on the screen
> when executing the transaction in dialog (or when testing it using SWO1).
> When executing the transaction/report
> in background from a workflow the output cannot be handled and thus the step
> remains 'in process' (the
> synchronous method does not end).
>
> It's possible to define a job and specify in the job that the output must be
> sent to the spool.
>
> Is it possible to handle the output the transaction/report produces (f.i.
> send it to a spool or ignore it) and
> let the method/step finish? F.i., is it possible to 'tell' the method how to
> handle the output, or to schedule a
> job from a step in a workflow?
>
> Regards,
>
> Fred Kouw
>
> "Zmudzin,Tomasz,FRANKFURT,Extern LG-DM" wrote:
>
> > Fred,
> >
> > The canonical way of handling this is to
> >
> >   call transaction .... messages into i_messages
> >
> > in your ABAP code, then analyze i_messages and react within the workflow
> > accordingly.
> >
> > Best regards,
> > Tomasz
> > -----Ursprungliche Nachricht-----
> > Von: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
> > Gesendet: Montag, 13. Oktober 2003 10:53
> > An: SAP-WUG at MITVMA.MIT.EDU
> > Betreff: Executing a dialog transaction in background from a workflow
> >
> > Hi,
> >
> > I have a requirement for executing a dialog transaction (that calls a
> > report) in the background after a change document (MATERIAL) has been
> > created.
> >
> > Calling the transaction with a parameter ID is no problem: the report
> > runs. But during processing the report results in a message, normally
> > being displayed to the user. Due to this the status of the background
> > task (and workflow) remains 'In process'. When I execute the transaction
> > in dialog and in debug mode I see that the report continues to execute
> > after I display the message (by double clicking it). This explains the
> > behaviour of my workflow: the report doesn't finish after the message is
> > raised (cannot be displayed in background).
> >
> > Is there a way to ignore the message, let the report run/end and
> > complete the workflow no matter what occurs during processing of the
> > report? Do I have to change the report to be able to be called in
> > background from a workflow?
> >
> > Regards,
> >
> > Fred Kouw
> >
> > **********************************************************************
> > This e-mail and any attachment may contain confidential and privileged
> > material intended for the addressee only. If you are not the addressee,
> you
> > are notified that no part of the e-mail or any attachment may be
> disclosed,
> > copied or distributed, and that any other action related to this e-mail or
> > attachment is strictly prohibited, and may be unlawful. If you have
> received
> > this e-mail by error, please notify the sender immediately by return
> e-mail,
> > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> > subsidiaries and/or its employees shall not be liable for the incorrect or
> > incomplete transmission of this e-mail or any attachments, nor responsible
> > for any delay in receipt.
> > **********************************************************************
> >
> >
> ____________________________________________________________________________
> > _________________
> > This outbound message from KPN has been checked for all known viruses by
> KPN
> > IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
> ____________________________________________________________________________
> > _________________
> >
> >
> ____________________________________________________________________________
> _____________
> > This inbound message from KPN has been checked for all known viruses by
> KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
> ____________________________________________________________________________
> _________________
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have received
> this e-mail by error, please notify the sender immediately by return e-mail,
> and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor responsible
> for any delay in receipt.
> **********************************************************************
>
> ____________________________________________________________________________
> _________________
> This outbound message from KPN has been checked for all known viruses by KPN
> IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> ____________________________________________________________________________
> _________________
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________

**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************

_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________