ERP2005: step type Web Activity and Web Dynpro
Dart, Jocelyn
jocelyn.dart at sap.com
Thu Dec 14 17:32:53 EST 2006
Ok folks... a little confusion happening here
If you don't use UWL - use transaction WF_EXTSRV - you need to first do
a one-off set up of the workflow handler in WF_HANDCUST.
If you use UWL - you can use transaction WF_EXTSRV or SWFVISU or UWL XML
configuration
If you use Guided Procedures - make sure you are on at least SP10 if its
an ABAP WebDynpro application.
And I would strongly advise using the UWL as your inbox - i.e. configure
up the GP Connector for the UWL in UWL Administration
With WF_EXTSRV you don't need a business object - you can generate the
task with a generic business object from WF_EXTSRV
It's very simple - just put in your URL connection details and
parameters and then generate the task.
On transport you need to change the system/client for the task in table
SWLSSTPID (that's from memory so its something like that - look for
SWL*SS*)
If you use SWFVISU or UWL XML configuration that overrides whatever
object/method you use in the task so a BOR object or ABAP OO class or
even just a dummy utility is possible - although of course you may need
the BOR or ABAP OO object to provide the data for your link anyway.
Any issues with using these very simple transactions - search the SDN
BPM forum for previous answers.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com <http://www.sap.com/>
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Kjetil Kilhavn
Sent: Thursday, 14 December 2006 7:37 PM
To: SAP Workflow Users' Group
Subject: RE: ERP2005: step type Web Activity and Web Dynpro
Ahhh... e-mails crossing each other here.
My main concern is now parameters, and it worries me a bit that you say
a dummy method will do. I hope that doesn't mean that there is no
possibility to pass parameters. This may turn into an opportunity to
create an ABAP Objects based workflow! That's a piece of good news among
the bad news :-)
I'll have to look into things.
--
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Markus Klein
Sent: Thursday, December 14, 2006 9:23 AM
To: SAP Workflow Users' Group
Subject: RE: ERP2005: step type Web Activity and Web Dynpro
Hello Kjetil,
actually you dont need a own business object. All you need is
for your Workfow-task which calls a WebDynpro Application a dummy method
which does do anything. You could use a simple abap class which
implements the interface if_workflow. Very easy to design. Take the
standard task 12300097, which the absence request workflow uses for the
Approveal activity (its a WebDynpro application). The rest of config is
done, as Jocely already stated, with transaction swfvisu.
cheers,
Markus
_________________
Markus Klein
SAP Senior Consultant
ABS Team GmbH
Muehlenweg 65
37120 Bovenden
Tel +49 551 820 33 0
Mobil +49 151 126 23 047
Email klein at abs-team.de
www.abs-team.com <http://www.abs-team.com/>
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Kjetil Kilhavn
Sent: Thursday, December 14, 2006 9:07 AM
To: SAP Workflow Users' Group
Subject: RE: ERP2005: step type Web Activity and Web Dynpro
Bijay, I forgot to inform about our reason for trying this
approach: our Guided Procedure system won't be available until it is too
late for the first release cycle. You know how managers sometimes like
to brag about things they don't have a clue about? This is one of these
cases, where someone high above us working ants has promised delivery in
February.
And sometimes (workflow) developers like to brag that "anything
can be done" in workflow. That's me in this case :-(
Jocelyn, you just ruined my day... and probably next week. But
thanks anyway ;-)
Not good news at all, as it seems I will have to create my own
business object if we are going down this road. At least I can't seem to
find anything relevant in SWO1.
--
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
________________________________
From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Dart, Jocelyn
Sent: Thursday, December 14, 2006 12:04 AM
To: SAP Workflow Users' Group
Subject: RE: ERP2005: step type Web Activity and Web
Dynpro
Actually you don't need Guided Procedures to call a
WebDynpro application.
You can do that easily enough from transaction SWFVISU,
UWL XML configuration of the launch mechanism for that task, or
transaction WF_EXTSRV.
The "web activity" step is to do with WF-XML - and is
not relevant to simply calling a WebDynpro application.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
________________________________
From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Shrestha, Bijay
Sent: Thursday, 14 December 2006 5:57 AM
To: SAP Workflow Users' Group
Subject: RE: ERP2005: step type Web Activity and Web
Dynpro
Hi Kjetil,
If you're going to make a new workflow by calling a Web
Dynpro application, I think it's better to design in Guided Procedure.
The prerequisite is Netweaver Portal.
It's lot easier to design a Guided Procedure which will
give you possiblility to call any webie program e.g. Webdynpro ABAP,
WebDynpro Java, iView, iView from Visual composer etc.
Bijay
-----Original Message-----
From: sap-wug-bounces at mit.edu on behalf of
Kjetil Kilhavn
Sent: Wed 12/13/2006 11:59 AM
To: SAP Workflow User's Group
Cc:
Subject: ERP2005: step type Web Activity and Web
Dynpro
My intuition tells me it should be possible to
call a Web DynPro screen from a web activity step - and preferrably even
a Web DynPro for ABAP and not just the Java version.
However, during my attempt in our sandbox system
I have become quite depressed. I can't even get a simple workflow where
the URL is fixed (http://www.google.com/) working. The single-test of
the step works, but not the workflow.
When I try to test it fails with error message
SWP135 (Unable to determine work item type for step at node 0000000004).
That message looks just plain stupid in my eyes, I thought I pretty much
defined the step type when I selected the "Web activity" icon, but
perhaps there is something I have missed.
Our config seems OK, transaction SWU3 shows
green lights everywhere it should matter (definition environment and
runtime environment).
The OSS search doesn't help me, nothing is
returned for <SWP135>, nothing was returned for <"determine work item
type">. When searching for <determine work item type> a lot of messages
about other items and types were found. So I restricted it to area
BC-BMT and got it reduced to 16 messages, of which zero were relevant
when we don't consider "Analysis for workflow problems" (322526) and
other generic notes relevant.
I have also tried SWUD with the trace on.
Unfortunately, I can't really say I felt enlightened after looking at
the trace.
Anyone care to help a clueless beginner? Not
that I think this WWW thing is here to stay anyway...
--
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL
and is
intended for the addressee only. Any unauthorised use,
dissemination of the
information or copying of this message is prohibited. If you are
not the
addressee, please notify the sender immediately by return e-mail
and delete
this message.
Thank you.
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and
delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061215/6051642a/attachment.htm
More information about the SAP-WUG
mailing list