Purchase Requisition
Nat 4 Govender
ngovender4 at toyota.co.za
Sun Nov 5 23:58:53 EST 2006
Because initially when we start the workflow the consultants told us that
we could only use item level offcourse now we are a bit more wiser.
The problem is that we have done so much now working on the item level. To
implement the purchase requisition release at header level will be a
project and I was looking as ways to temporary solve this until we can
start with this process.
Regards
Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext. : 32645
Direct Line : +27 031 910 2645
Fax : +27 031 902 9633
E-mail : ngovender4 at toyota.co.za
=============================================
Never test the depth of the water with both feet.
=============================================
"Maorriyan
Santoso"
<maorriyan.santos To
o at gmail.com> "SAP Workflow Users' Group"
Sent by: <sap-wug at mit.edu>
sap-wug-bounces at m cc
it.edu
Subject
Re:
2006/11/06 01:34
AM
Please respond to
"SAP Workflow
Users' Group"
<sap-wug at mit.edu>
Hi Nat.
Just questioning from the MM business process point of view. Why you're not
using Workflow for Overall Release (header level) for this ?
On 11/3/06, Nat 4 Govender <ngovender4 at toyota.co.za> wrote:
Hi All,
We currently have a release strategy of purchase requisition based on
item level.
What the business now want is if a user get more than one purchase
requisition item for the same purchase requisition they want to release
them all at once.
I remember something about grouping tasks would did help?
Please advise
Thanking you in advance
Regards
Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext. : 32645
Direct Line : +27 031 910 2645
Fax : +27 031 902 9633
E-mail : ngovender4 at toyota.co.za
=============================================
Never test the depth of the water with both feet.
=============================================
This message is a privileged and private communication
and may be read,copied and used only by the intended recipient(s).
If you are not an intended recipient, please let us know by return
email. Please then delete the message and do not disclose its
contents to any person. Neither the sender nor Toyota South Africa
Motors accepts any liability whatsoever as a result of the further
dissemination of this message. Whilst all reasonable steps are
taken to avoid corruption of data or information, we do not accept
any liability should such corruption occur.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/50754181/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/50754181/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic24221.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/50754181/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/50754181/attachment-0002.gif
More information about the SAP-WUG
mailing list