FW: Workflow of Purchase Orders

[Bradshaw-Long, Kathleen]

=20
-----Original Message-----
From: Vineet.Mehta at mbusi.daimlerchrysler.com =
[mailto:Vineet.Mehta at mbusi.daimlerchrysler.com]=20
Sent: Thursday, February 05, 2004 10:59 AM
To: Bradshaw-Long, Kathleen
Subject: Re: Workflow of Purchase Orders
 
 
 
 Except if you use two different document types, you are approving the =
same dollars twice. It also means you are booking double the amount of =
commitments than you need. You definitely need to be aware of this. It =
could potnetially result in two POs for same items..
 
You could however, try this, have two different classifications (which =
might be identical). One classfication for Overall release and one for =
itemwise release.
 
This is possible via IMG (or directly transaction OMGQ). Release group> =
one overall checked and for other class take OverReqReL off. Again this =
is only theoretical
 
=20
 
Sorry Kathleen I could not post this message because I am sending it in =
html format or something (I am using webmail). Can you post it for me? =
Please?
 
=20
 
Regards,
 
Vineet
 
Kathleen.Bradshaw-Long at getronics.com
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
02/05/2004 10:06 EST
Please respond to SAP-WUG
 
To: SAP-WUG at MITVMA.MIT.EDU
cc:=20
bcc:=20
Subject: Re: Workflow of Purchase Orders
 
 
 
 
Hi Richard,
 
I believe that the release strategy and the workflow for the purchase =
req. would start again, if someone such as a buyer, changed the =
quantity/value of a purchase requisition after it was approved. This =
would be determined by the field selection key in the release status.
 
As far as changes to a req. line item after it becomes a  PO, I'm not =
sure.  However, if the business practice is that PO changes aren't =
allowed unless they originate from a requisition, then the risk of =
unauthorized changes is more limited.
 
Kathleen
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Schmidinger, Heinz (Unaxis IT BZ)
Sent: Thursday, February 05, 2004 2:09 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Workflow of Purchase Orders
 
 
Hi Richard,
 
use Start-Konditions (SWETYPV) or - so I prefer - check-function-modules =
in the eveent-linkage (SWB_COND).
 
 
Maybe the check-f.m. is based for PO-CREATE, where you can check if its =
is based on a Request and if it is checked.
 
maybe it helps
 
regards
 
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: Richard Williams (FCF) [mailto:Richard.Williams at fcf.co.nz]
Gesendet am: Mittwoch, 4. Februar 2004 20:44
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Workflow of Purchase Orders
 
We have workflow for Purchase Requisition approval, the business have =
asked me if it is possible to workflow the PO if, and only if the =
quantity, price or vendor gets changed during the PR - PO conversion.
 
Can this be done and if so is there any one that can give me a few =
pointers, how would I get the system to know that there has been a =
change from the original PR?
 
Thank you for your help.
 
Richard Williams
Fletcher Challenge Forests
SCG, Rotorua
07-349 5224
0274 865 160