Why are 'exporting' parameters NOT passed back from an OO method to the workflow?

[Dart, Jocelyn]

Hi Paul, 
Well I can only assume you are calling the method as a "functional method" in a binding instead of in a task or is your task Asynchronous? 
 
If you call it as a functional method, e.g. in a binding, then only the returning parameter would be passed back as a functional method call by definition only returns a single result.  
 
If you call a method in a class all exporting parameters will be passed back (so long as the task is Synchronous of course and you have matching container elements in the task) and I have never had a problem with this in any release/support pack.
 
By definition Asynchronous tasks do not return a result directly - only via terminating events.
 
So suggest you check how you have made the call and your settings on the task.  If you are doing an explicit method/task binding, I would suggest instead that you use the implicit task binding - let the task container be generated from the class/method so that all parameters are passed by identical name. 
 
Hope that helps.
Regards,
Jocelyn
 
 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Florin Wach
Sent: Wed 11/03/2009 9:23 PM
To: SAP Workflow Users' Group
Subject: Re: Why are 'exporting' parameters NOT passed back from an OO method to the workflow?



hrm.

It seems to be okay under SAP ECC 6.00 SAP Basis 700 Patch Level 17
On this release I can't find anything particular that filters any export-parameters. Furthermore I have a workflow tasks having two export parameters (one table and one simple) and both worked fine.

What's *not* implemented currently is, to have the RESULT-Parameter with fixed domain values giving different outcomes of the activity when modelling the workflow pattern.

Best wishes,
   Florin

-------- Original-Nachricht --------
> Datum: Wed, 11 Mar 2009 16:57:00 +1000
> Von: Neil Gardiner <neil.gardiner at gmail.com>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: Re: Why are \'exporting\' parameters NOT passed back from an OO method       to the workflow?

> Hi Paul,
>
> This is currently a feature of workflow in OO but currently there seems to
> be no clear reason for this. Unless, Jocelyn et al, I am mistaken?
>
> Cheers,
> Neil.
> 2009/3/11 <Paul.Bakker at osr.treasury.qld.gov.au>
>
> >
> > Hi,
> >
> > I have a simple question:
> >
> >   Why are 'exporting' parameters NOT passed back from an OO method call
> to
> > the workflow?
> >
> > We have this setup:
> >
> > A custom OO method exports table ET_MESSAGES -> binds to Task container
> ->
> > binds to Workflow container
> >
> > The problem: the method is populating ET_MESSAGES, but it
> > is NOT being passed back to the task (or the workflow). So the workflow
> log
> > cannot tell us whether the method succeeded or not.
> >
> > In debug I found out the reason why. The SAP function module
> > SWF_UTL_INVOKE_CLIF_METHOD seems to be checking all method
> > parameters, and passing back only those that are of type
> > 'RETURNING'.
> >
> > Whereas my parameter ET_MESSAGES is of type 'EXPORTING'.
> >
> > When I change it to 'RETURNING', it works.
> >
> > Is this a bug or a feature? Or am I doing something wrong??
> >
> > thanks in advance!
> > Paul
> >
> > (PS We're on ECC 6.0. I have searched OSS and WUG but found nothing. SDN
> is
> > down.)
> >
> >
> >
> >
> ******************************************************************************************************************************************************
> >
> > Only an individual or entity who is intended to be a recipient of this
> > e-mail may access or use the information contained in this e-mail or any
> of
> > its attachments.  Opinions contained in this e-mail or any of its
> > attachments do not necessarily reflect the opinions of Queensland
> Treasury.
> >
> > The contents of this e-mail and any attachments are confidential and may
> be
> > legally privileged and the subject of copyright.  If you have received
> this
> > e-mail in error, please notify Queensland Treasury immediately and erase
> all
> > copies of the e-mail and the attachments.  Queensland Treasury uses
> virus
> > scanning software.  However, it is not liable for viruses present in
> this
> > e-mail or in any attachment.
> >
> >
> >
> ******************************************************************************************************************************************************
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>
>
>
> --
> Neil Gardiner
> Mob: +61 421 451 295
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug