How can I debugg a role on 4.0B?

Pokraka, Michael michael.pokraka at kcc.com
Mon Oct 28 12:28:07 EST 2002


OK, plan b then... Try logging the FM parameters somewhere into a z-table to
make sure everything's received as you think it's getting there. At the end
of the FM, add another log entry as to what it's passing back.
I've found it useful to have a table + a couple of debugging modules handy
for this type of purpose in every dev system.
 
Cheers
Michael
 
 
-----Original Message-----
From: Torsten Schnorpfeil [mailto:torsten at processflow.de]
Sent: 28 October 2002 17:04
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How can I debugg a role on 4.0B?
 
 
Michael,
 
thanks for you reply. In 4.0b is neither a feature to test roles nor a
breakpoint in the FM would work during runtime of a workflow (as far as I
know)!
 
Any other suggestions?
 
Torsten
 
----- Original Message -----
From: "Pokraka, Michael" <michael.pokraka at kcc.com>
To: <SAP-WUG at MITVMA.MIT.EDU>
Sent: Monday, October 28, 2002 11:39 AM
Subject: Re: How can I debugg a role on 4.0B?
 
 
> Can't remember the details, but is there not a test function in the role
> definition?
> If so, add a breakpoint in your FM and you should be OK.
>
>
> -----Original Message-----
>> From: Torsten Schnorpfeil [mailto:torsten at processflow.de]
> Sent: 28 October 2002 16:31
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: How can I debugg a role on 4.0B?
>
>
> Hi Flowies,
>
> here's the thing: I've created a dynamic role on 4.0B. When I'm testing
the
> function module everything is working fine. But within the role the
function
> module doesn't return any values to the workflow. The container defintion
of
> the role should be fine.
> Is there a way to debugg this thing? Unfortunatly the features from 4.6
are
> not on this R/3 release.
>
> Any help highly appreciated!
>
> Regards,
> Torsten
>
> --------------------------------------------------------------------------
----
> This e-mail is intended for the use of the addressee(s) only and may
contain privileged, confidential, or proprietary information that is exempt
from disclosure under law.  If you have received this message in error,
please inform us promptly by reply e-mail, then delete the e-mail and
destroy any printed copy.   Thank you.
>
>
 ===========================================================================
==
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.
 
 =============================================================================
 


More information about the SAP-WUG mailing list