Web Enabled Workflows

[Dart, Jocelyn]

Hi Bill,=20
A few suggestions based on my experiences in this area:
 
1. For approval workitems (i.e. where the user actually
approves/rejects), use tasks with object FORM method HTMLPROCESS,=20
the workflow web transaction generation option to create
a web transaction for the workitem, and=20
SAP at WebStudio to create ITS service/template files matching=20
the web transaction.  There is quite a bit of info in the=20
R/3 library on this - look in the workflow section - you should
find a section on web handling near the section on Exchange handling.
The entry point for users is then the web inbox - i.e. ITS service
BWSP.  You can use report RSWUWFML to send reminder emails to users
with outstanding workitems - it's worthwhile including the URL
to the BWSP service as part of the text message as Exchange will
turn this into a hyperlink encouraging users to deal with workitems
on the spot. =20
 
Don't forget that user decisions are already web-enabled and it is=20
possible to create your own user decision task (object DECISION
method PROCESS) - if your display needs are very simple this can save
some development.=20
 
2. Business Connector is really for automated communication of=20
documents not dialog communication.  So if you want to send a
document out at some time during your workflow this is possible, but
it's not the sort of thing to use for the actual approval workitem.
 
3. Workplace gives you access to R/3 via SAPGUI for HTML. =20
One of the big benefit of using workplace for workflow is the workflow=20
miniapp, which can synchronise workitems from multiple R/3 systems.
However implementing Workplace is non-trivial and would not be =
justified
purely to handle workitems.  So if you are implementing Workplace for=20
other reasons by all means take advantage of it, but if you aren't, =
option
1 above is usually sufficient to solve the immediate problem.=20
 
Hope that helps.
Regards,
        Jocelyn Dart=20
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)=20
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>=20
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Bill Barthel [mailto:wfbarthe at collins.rockwell.com]
Sent: Thursday, 25 January 2001 11:36 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Web Enabled Workflows
 
 
A few thoughts ... I think you left out an important option - SAP DCOM. =
 If
you have a development staff strong in ABAP (Dialog) and weak =
VB/ASP/COM
... ITS is your answer.  If you have a strong VB/ASP/COM shop ... SAP =
DCOM
is your choice .. both work ... it really depends on what technology =
you
want to support.  I'm leaning towards SAP DCOM these days ...
 
Bill Barthel
Rockwell Collins
 
 
 
 
Raju Omkaram <romkaram at hotmail.com>@MITVMA.MIT.EDU> on 01/24/2001 =
05:46:51
PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
 
Subject:  Web Enabled Workflows
 
 
 
Hello Workflow Gurus,
 
What is the best way to make workflows web enabled from  technical
architecture perspective?
Currently, we have the following available:
1. ITS using Web Studio
2. SAP Business connector
3. SAP Workplace.
 
We want to use Approval (workflow) process over the web to  replace =
MAPIs
and dial ups to corporate office.=A0 We use SAP BC for B2B  purposes. =
How can
I make use of this architecture for web enabling the  workflows?
we are on 4.0B and no plans for upgrade until Q1 of  02.
 
Any guidance is highly appreciated.
 
Thanks
 
Raj