Call transaction needs to return to workflow

Fri Aug 26 07:55:43 EDT 2011

Hi David,

I am glad everything is working for you.  Yes, you can use CALL TRANSACTION
to execute a transaction, you can use SUBMIT to execute a report, and you
can use CALL FUNCTION to execute a function module.  I use the SAP PRESS
Workflow and ABAP reference books which provide all of these details.

Regards.

SHELDON OXENBERG
System Architect Principal Leader
LMP Technical Architect, SAP Workflow
CSC

  From:       <david.s.dittmer at accenture.com>                                                                          

  To:         <sap-wug at mit.edu>                                                                                        

  Date:       08/25/2011 04:55 PM                                                                                      

  Subject:    RE: Call transaction needs to return to workflow                                                         

Hello Sheldon,
Profuse thanks..got it to work using the call transaction. For my future
edification so I do not have to ask such basic questions again would the
SUBMIT and RETURN feature be in place of the CALL TRANSACTION .

Thanks again.

regards
David Dittmer

________________________________________
From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
Sheldon Oxenberg [soxenber at csc.com]
Sent: Thursday, August 25, 2011 4:29 PM
To: SAP Workflow Users' Group
Subject: RE: Call transaction needs to return to workflow

If you use CALL TRANSACTION using BDC_TAB with MESSAGES INTO itab, then the
transaction messages can be retrieved from internal table itab.

Instead, if you use SUBMIT AND RETURN with EXPORTING LIST TO MEMORY, you
can retrieve the basic list from ABAP Memory using standard function
modules such as LIST_FROM_MEMORY.

Thank you.

SHELDON OXENBERG
System Architect Principal Leader
LMP Technical Architect, SAP Workflow
CSC

  From:       <david.s.dittmer at accenture.com>

  To:         <sap-wug at mit.edu>

  Date:       08/25/2011 03:34 PM

  Subject:    RE: Call transaction needs to return to workflow

Thank you Sheldon. Problem solved...after calling the transaction the
transaction returns to the method...one question I have is how would the
method  get the returned details from the transaction....would it be
necessary to populate a container in the SAVE transaction function.

regards
David Dittmer

________________________________________
From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
Sheldon Oxenberg [soxenber at csc.com]
Sent: Thursday, August 25, 2011 9:31 AM
To: SAP Workflow Users' Group
Subject: RE: Call transaction needs to return to workflow

Hi David,

Yes, the return to your method and to the workflow should be automatic and
work just fine.

If the recipient executes the work item from their inbox, and if this
executes your method in the task that calls a transaction, then the
transaction will return to the method when it is completed.  The method
would get the returned details from the transaction.  Is this where you are
having a problem?

Depending on the checkboxes you use in your workflow step, when your method
is completed the workflow will display a screen for the recipient to click
that "they are done with the work item" and then the workflow will continue
to your sub-workflow.  Is this where you are having a problem?

Regards.

SHELDON OXENBERG
System Architect Principal Leader
LMP Technical Architect, SAP Workflow
CSC

  From:       <david.s.dittmer at accenture.com>

  To:         <sap-wug at mit.edu>

  Date:       08/25/2011 08:45 AM

  Subject:    RE: Call transaction needs to return to workflow

Hello Michael,
This is not a binding issue. I am calling a transaction in a task which the
recipient must execute the transaction  and save in the inbox and after
saving it must return to the workflow to continue where I have set up a
sub-workflow.

Its this returning to the workflow that I am querying.

Thank you for replying

From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
michael.mcley at daimler.com [michael.mcley at daimler.com]
Sent: Wednesday, August 24, 2011 5:28 PM
To: sap-wug at mit.edu
Subject: Re: Call transaction needs to return to workflow

David,

Sorry if I'm wasting your (and anyone else who reads this)'s time, but are
we talking about the basics of "workflow bindings" here, or is there some
complication or detail I missed in your email?  If you are not familiar
with the term "binding" as it relates to SAP workflow, I would guess we are
talking about binding basics...;-)
Michael McLey
MBUSI - IT Parts & Administration
Mercedes-Benz US International, Inc.
1 Mercedes Drive
Vance, AL 35490
PHONE:  (205) 462 - 5239
EMAIL:   michael.mcley at daimler.com

 david.s.dittmer at accenture.com
 Sent by:
 sap-wug-bounces at mit.edu
 08/24/2011 04:06 PM                                                    To
                                           sap-wug at mit.edu
                                                                        cc
        Please respond to
         sap-wug at mit.edu                                           Subject
                                           Call transaction needs to
                                           return to workflow

Hello Experts,
I have designed a workflow where a transaction is called and after the
recipient has completed the transaction, details need to be returned to the
workflow so that further steps can be completed.

I am calling the transaction in a method but how would I ensure that the
details from the completion of the transaction are returned to the
workflow. ideally I would want to capture the details in the method after
completing the transaction.

I am sure this is really a basic step so apologize for asking but it just
seems a roadblock at the moment.

Thanks

David Dittmer
Accenture

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

If you are not the intended addressee, please inform us immediately that
you have received this e-mail in error, and delete it. We thank you for
your cooperation.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete the
original.  Any other use of the email by you is prohibited.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete the
original.  Any other use of the email by you is prohibited.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug