Workflow Form as "secondary method"

[Daniel Schorsch]

Hi Mark,

thanks for your input. Parameter passing for secondary methods is 
possible. You just have to give it to the task container so the secondary 
method can access it. I allready did that with other methods (e.g. 
starting a self developed method "displaywithparameters of type BUS3003). 
It functioned well, that is why I thought it should also work in the same 
way with the form object :-(



Mit freundlichen Grüßen / With kind regards / Met vriendelijke groeten

Daniel Schorsch
Philips Medical Systems DMC GmbH
Information Technology - Technical Automation
Röntgenstraße 24
22335 Hamburg
Tel.: +49/40/5078-1505
Fax: +49/40/5078-1793
Email: Daniel.Schorsch at philips.com
Intranet: http://pww.de.ms.philips.com/

Geschäftsführung: Diedrich Dirks (Vorsitzender), Christoph Wittler
Sitz der Gesellschaft: Hamburg
Registergericht Hamburg, 66 HRB 77 839
Steuernummer: 22/27/278/00800








"Mark Pyc" <mark.pyc at gmail.com> 
Sent by:
sap-wug-bounces at mit.edu
05.11.2007 12:33
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>


To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
Re: Workflow Form as "secondary method"
Classification







G'day Daniel,
 
I'm not sure but I don't think you can do anything so tricky from a 
secondary method. I believe you can only call simple methods of the 
primary object (_WI_OBJECT_ID) despite the fact that you can specify other 
objects on that tab. I'm assuming that your primary object in this case 
will be the material object rather than the form object. In which case you 
may need a new method on the material object. 
 
Again I'm not claiming to be an expert on secondary methods, but I believe 
that they're not even really intended to have import/export parameters. 
This may not be true in the later releases, but they were originally just 
intended for display of additional data which didn't require parameter 
passing. 
 
Good luck,
Mark

 
On 05/11/2007, Daniel Schorsch <daniel.schorsch at philips.com> wrote: 

Hi all, 

I have got a Workflow using formsteps. Now I would like to make this form 
that was filled in during the workflow to appear just for viewing via a 
secodary method of a workflow step for creating a new material. 

I did the following: 

Entering on the "methods tab" of the workflow step a secondary methode 
Container Element is type BO.DYNP_FORM, method is display. 

Furthermore I pass the following parameters via binding to the task: 
        - FORMPROGRAM (programm to execute) 
        - FORMDYNPRO (dynpro to open) 
        - FORMCONTAINERELEMENT (structure for the form) 
        - DYNP_FORM (Form Object) 

When I now execute the task the secondary methode is not called (or let's 
say the form does not open up). Is there something missing? Is is there 
another way to display a workflow form as a secondary method?? 

Thank you very much!!! 


Mit freundlichen Grüßen / With kind regards / Met vriendelijke groeten

Daniel Schorsch
Philips Medical Systems DMC GmbH
Information Technology - Technical Automation
Röntgenstraße 24
22335 Hamburg
Tel.: +49/40/5078-1505
Fax: +49/40/5078-1793
Email: Daniel.Schorsch at philips.com
Intranet: http://pww.de.ms.philips.com/

Geschäftsführung: Diedrich Dirks (Vorsitzender), Christoph Wittler 
Sitz der Gesellschaft: Hamburg
Registergericht Hamburg, 66 HRB 77 839
Steuernummer: 22/27/278/00800
_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071105/16c4907e/attachment.htm