exception in class and passing of parameters

[Dart, Jocelyn]

Hi Robert,
That doesn’t sound right to me… Returning is a completely different concept to exceptions and they are not used in the same way.
It is possible to use returning parameters with workflow but it’s a bit of a pain… so I tend to stick to exporting which is more straightforward.
I think you are going down the wrong track there… look at my other response re the correct exception classes to use.
Regards,
Jocelyn

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Robert van den Berg
Sent: Thursday, 20 May 2010 7:33 PM
To: sap-wug at mit.edu; SAP Workflow Users' Group; SAP Workflow Users' Group
Subject: Re: Re: RE: exception in class and passing of parameters


Hi all,



I discovered where the evil is. In the old situation with BOR objects, the method has a return parameter (setting on the method). So the 'exceptions' are not exceptions but return values.



Is there a possibility to use this with a Class method?



Best regards,

Robert

On May 20, 2010 10:58 "Robert van den Berg" <wug at bergtop-ict.nl><mailto:wug at bergtop-ict.nl> wrote:

Mike,



it does not realy need a statement to pass the value, does it?



The export parameter is set by the normal ABAP statement:

APPEND ls_amr TO amr_reject.

AMR_REJECT is set as exporting parameter.



Regards,

Robert

On May 20, 2010 10:48 "Mike Gambier" wrote:
Jocelyn,

I'm not sure that's entirely accurate anymore. ABAP was adjusted some time ago to return EXPORTING, TABLES and CHANGING parameters in FMs or ABAP Class Methods even if you raise an exception.

We have several examples of where an Exception is thrown and we can still trust the value of an Exporting 'Error' flag or Application Log instance as well.

The flaw highlighted by Robert I think is buried in the way the value being received is being bound (or not) into the Method container.

Mike GT

________________________________
From: jocelyn.dart at sap.com
To: sap-wug at mit.edu
Date: Thu, 20 May 2010 10:30:07 +0200
Subject: RE: exception in class and passing of parameters

Hi Robert,



If you raise an exception, the exporting parameters are NOT returned to the calling application (not just workflow – all calling applications)  – exact same behaviour as function modules.  The test tool “cheats” a little.



So for a synchronous task either use an additional exporting parameter to indicate success/failure or use an exception class to update the workflow log with your returned value.

Or raise an event (with or without parameters) – and make your task asynchronous.



Regards,

Jocelyn



From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Robert van den Berg
Sent: Thursday, 20 May 2010 6:17 PM
To: SAP Workflow Users' Group
Subject: exception in class and passing of parameters


Hi Group,

I have a task which uses a method of a class. This method has export parameters and exceptions.
Before the exception is raised, the export parameter is set.

The problem is that, when the exception is raised, the export parameter is empty. When I test the method from the class builder, the export parameter contains a value but when I test the workflow, the workflow container is empty.

Does anyone have an idea?

Regards,
Robert


________________________________
Get a free e-mail account with Hotmail. Sign-up now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100521/0d7b2151/attachment.htm