Help needed with this scenario

Wed Sep 7 08:09:12 EDT 2005

Its described quite well in the standard SAP Library Help.
That's your best reference.  
And no you don't need to add a button (although you can).  
Standard behaviour is that you can choose in the customizing whether
submitting the 
form starts a workflow or not, and which workflow to start. 

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

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. 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of vijay srikanth
Sent: Wednesday, 07 September 2005 9:55 PM
To: sap-wug at mit.edu
Subject: RE: Help needed with this scenario

Hi,

I wish I knew this way before. But actually the portal part is being
handled 
by some other persons.
hey can u send me some docs..containing exact examples of usage of 
QISRSCENARIO transaction,
and general usage of ISRs like that way you told me to. As of what I
have 
understood,
you would preferrably want the form to be designed in QISRSCENARIO, then
put 
it in EP.
and then link a submit button in the form to a workflow created event.
Maybe 
next time I'll give this suggestion.

Thanks,
Vijay

>From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: Help needed with this scenario
>Date: Wed, 7 Sep 2005 19:39:41 +0800
>
>No you wouldn't link an existing form this way.  Its much easier to
>create everything from scratch using QISRSCENARIO.
>
>If its an existing form with an application behind it then yes an RFC
of
>some kind is probably easiest.  If you are in a decent release you can
>redisplay your form using the webservices WF_EXTSRV transaction and
>SWFVISU to launch the web service.
>
>Its a shame because QISRSCENARIO would have done pretty much everything
>for you up to and including the workflow.   Now you'll have to work out
>the rest yourself.
>
>
>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
>
>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.
>
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
>Of vijay srikanth
>Sent: Wednesday, 07 September 2005 9:21 PM
>To: sap-wug at mit.edu
>Subject: RE: Help needed with this scenario
>
>
>Hi,
>
>First of all..thanks for taking time out..
>The issue with this thing is that the form in the portal is a custom
>form,
>and it's already been built in a particular way and I'm not sure of how
>to
>use these "Internet Service Requests" (never worked on it before). Can
>you
>tell me how to use this transaction QISRSCENARIO-what exactly is it
for.
>It
>says some scenario description and some characteristics and tasks. How
>can
>the portal form which is already been created, link into the workflow
>using
>this transaction.
>
>
>Regards,
>Vijay
>
>
> >From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >Subject: RE: Help needed with this scenario
> >Date: Wed, 7 Sep 2005 18:31:14 +0800
> >
> >Yes I thought you meant EP 6.0 - that's why I suggested Internet
>Service
> >Requests.
> >
> >It really is a lot less effort than the way you propose, because
> >Internet Service Requests is all pre-built and configurable.  It
handle
> >forms very well with the Portal as I said, this is the way all the
ESS
> >forms for the portal are handled.  Plus you can see the form from R/3
>as
> >well if you wish.
> >
> >You configure what fields you want on your form and you can generate
>the
> >iview or equivalent from QISRSCENARIO.  This is generic functionality
> >that is available for all R/3 applications.
> >
> >Seriously - it's a lot easier than reinventing the wheel.
> >
> >
> >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
> >
> >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.
> >
> >
> >-----Original Message-----
> >From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>Behalf
> >Of vijay srikanth
> >Sent: Wednesday, 07 September 2005 6:56 PM
> >To: sap-wug at mit.edu
> >Subject: RE: Help needed with this scenario
> >
> >Hi Jocelyn,
> >
> >By portal I meant Enterprise Portal 6.0, not just any internet
> >portal.(sorry
> >if i led you wrongly)
> >What I have thought of is to have an RFC call from EP to an FM in
R/3.
> >Then
> >the FM will call,
> >a business object which will trigger an event to start the workflow.
In
> >turn
> >the workflow will generate a form to have the details as per on the
> >portal.
> >Do you find any flaws in this approach.
> >
> >
> >Regards,
> >Vijay
> >
> >
> > >From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > >To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > >Subject: RE: Help needed with this scenario
> > >Date: Wed, 7 Sep 2005 00:22:46 +0800
> > >
> > >Hi Vijay,
> > >Easiest approach would be to use general notifications with
Internet
> > >Service Requests.
> > >
> > >This will give you the form-based approach with plenty of stuff
based
> >on
> > >configuration and/or generated for you.  Plus its all based around
> > >portals as ESS uses this approach heavily.
> > >
> > >It starts a standard workflow e.g. WS50000040/41/42 based on
business
> > >object BUS7051 but you can replace this with your own workflow
doing
> > >whatever process you want.
> > >
> > >You use a BADI to check the data and there are also function
modules
>to
> > >read the form data attached to the notification, e.g. if you want
to
> > >pass the data on to start/execute a transaction/BAPI at some point
in
> > >your workflow.
> > >
> > >Have a look at transaction QISRSCENARIO - you'll need to configure
>your
> > >form here.  Depending on your release you can create an Adobe form
or
>a
> > >Java iview form or an ITS form.
> > >
> > >Read the doco on Internet Service Requests (or as ESS calls them...
> > >Personnel Change Requests, which are really the just same thing
> > >re-badged).
> > >
> > >
> > >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
> > >
> > >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.
> > >
> > >
> > >-----Original Message-----
> > >From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> >Behalf
> > >Of vijay srikanth
> > >Sent: Wednesday, 07 September 2005 1:12 AM
> > >To: sap-wug at mit.edu
> > >Subject: Help needed with this scenario
> > >
> > >Hi,
> > >
> > >This is a scenario to be implemented using workflows.
> > >Can you tell me how to go about with this.
> > >
> > >There is a form on the portal. User enters some details there. Then
> > >there is
> > >a submit button. when the user presses the submit button, a
workflow
>is
> > >triggered on the R/3 side. A work item is sent to the manager which
>has
> > >a
> > >form ( the form's layout and data are the same as that of the
portal
> > >screen
> > >). Basically whatever the user enters in the portal screen is sent
as
>a
> > >form
> > >to his manager, who can then approve it or reject it.
> > >
> > >Can anyone tell me how this can be done.....the general
> > >steps...connectivity
> > >between portal and R/3 workflow
> > >
> > >
> > >_______________________________________________
> > >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
> >
> >
> >_______________________________________________
> >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
>
>
>_______________________________________________
>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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug