standard workflow for release of Purchase Requisitions

[Vinod Ramchandani]

=20
Hi Marty,
 
I have done the Functional Settings(Release Strategy, Classification etc.=
) &
Technical Developments (Customizing and Interface to Lotus Notes) for thi=
s
workflow before few months.
If you will stuck  anywhere then mail me, I will try my best to help you.
See the attachment and Read it which is similar to the SAP Help.
I have some more documents which include all the relevant information &
screen shots, If  you interested than let me know.
It might be helpful to you.
 
Ok, Bye.
 
Thanks & Regards,
Vinod Ramchandani,
Software Engineer,
SAP Workflow Development Team,
EAI-SAP,
Patni Computer Systems Ltd,
Mumbai - 400701,
India.
Phone: +912227781006 Ext: 4006.
 
 
 -----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]  On Behalf Of
Marty Braithwaite
Sent:   Thursday, February 06, 2003 8:34 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: standard workflow for release of Purchase Requisitions
 
Thanks Vinod, I've already found the workflow and read up on it.  My prob=
lem
is, from what I've read in the documentation regarding this workflow is
there is a lot of config needed to be setup regarding classifications .
Basically all I want to do is demo this to 2 people who support our MM
module.  One of them can be the releaser of the requisition, the other ca=
n
be the approver/rejector...Just something really simple for now, I can ev=
en
hardcode the agents for simplicity.  There seems to be different release
strategies, but for now, like I said we just want to demo it with a small
group, so we aren't worried about cost center strategies or anything like
that, just that the workflows are directed to a couple of people.
Regards,
Marty Braithwaite
-----Original Message-----
From:   Vinod Ramchandani [mailto:vinod.ramchandani at patni.com]
Sent:   Wednesday, February 05, 2003 10:42 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: standard workflow for release of Purchase Requisitions
 
 
Hi Marty,
Look at the followings:=20
Workflow Name:          wf_req_rel
Workflow Template:      WS00000038
Workflow Description:  Workflow for requisition release
Try Txn:  OOCU=20
To see all the System defined Standard workflows in all areas.
 
I have configured this workflow, If you need any help/docs on it then I c=
an
help you out.
 
Thanks & Regards,
Vinod Ramchandani,
Software Engineer,
SAP Workflow Development Team,
EAI-SAP,
Patni Computer Systems Ltd,
Mumbai - 400701,
India.
Phone: +912227781006 Ext: 4006.
 
 
-----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]  On Behalf Of
        Marty Braithwaite
Sent:   Wednesday, February 05, 2003 8:45 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        standard workflow for release of Purchase Requisitions
 
Hi everyone, our shop is just starting to utilize workflow in may of our
applications.  On the MM side I have been given a request to demo the
standard Purch Req-release workflow (all items).  I am new to workflow, a=
nd
have been doing a lot of self learning.  I have looked at the documentati=
on
regarding the standard workflow and I'm wondering if there is a quick and
easy way to demo this workflow without performing a lot of pre-configurat=
ion
with classifications.  Any help would be greatly appreciated.
 
Thanks,
Marty Braithwaite
CPrail SAP Sustainment Team
 
 
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
------------------------------
 
Computer viruses can be transmitted via email. Recipient should check thi=
s
email and any attachments for the presence of viruses. Sender and sender
company accept no liability for any damage caused by any virus transmitte=
d
by this email.
 
This email transmission and any accompanying attachments contain
confidential information intended only for the use of the individual or
entity named above.  Any dissemination, distribution, copying or action
taken in reliance on the contents of this email by anyone other than the
intended recipient is strictly prohibited.  If you have received this ema=
il
in error please immediately delete it and  notify sender at the above ema=
il
address.=20
 
 
Le courrier =E9lectronique peut =EAtre porteur de virus informatiques.  L=
e
destinataire doit donc passer le pr=E9sent courriel et les pi=E8ces qui y=
 sont
jointes au d=E9tecteur de virus.  L'exp=E9diteur et son employeur d=E9cli=
nent
toute responsabilit=E9 pour les dommages caus=E9s par un virus contenu da=
ns le
courriel.
 
Le pr=E9sent message et les pi=E8ces qui y sont jointes contiennent des
renseignements confidentiels destin=E9s uniquement =E0 la personne ou =E0
l'organisme nomm=E9 ci-dessus.  Toute diffusion, distribution, reproducti=
on ou
utilisation comme r=E9f=E9rence du contenu du message par une autre perso=
nne que
le destinataire est formellement interdite.  Si vous avez re=E7u ce courr=
iel
par erreur, veuillez le d=E9truire imm=E9diatement et en informer l'exp=E9=
diteur =E0
l'adresse ci-dessus.
 
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
------------------------------
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
------------------------------
Computer viruses can be transmitted via email. Recipient should check thi=
s
email and any attachments for the presence of viruses. Sender and sender
company accept no liability for any damage caused by any virus transmitte=
d
by this email.
This email transmission and any accompanying attachments contain
confidential information intended only for the use of the individual or
entity named above.  Any dissemination, distribution, copying or action
taken in reliance on the contents of this email by anyone other than the
intended recipient is strictly prohibited.  If you have received this ema=
il
in error please immediately delete it and  notify sender at the above ema=
il
address.=20
 
Le courrier =E9lectronique peut =EAtre porteur de virus informatiques.  L=
e
destinataire doit donc passer le pr=E9sent courriel et les pi=E8ces qui y=
 sont
jointes au d=E9tecteur de virus.  L'exp=E9diteur et son employeur d=E9cli=
nent
toute responsabilit=E9 pour les dommages caus=E9s par un virus contenu da=
ns le
courriel.
Le pr=E9sent message et les pi=E8ces qui y sont jointes contiennent des
renseignements confidentiels destin=E9s uniquement =E0 la personne ou =E0
l'organisme nomm=E9 ci-dessus.  Toute diffusion, distribution, reproducti=
on ou
utilisation comme r=E9f=E9rence du contenu du message par une autre perso=
nne que
le destinataire est formellement interdite.  Si vous avez re=E7u ce courr=
iel
par erreur, veuillez le d=E9truire imm=E9diatement et en informer l'exp=E9=
diteur =E0
l'adresse ci-dessus.
------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
------------------------------