Hi
For a PR with Qty 1, Generally On PO can be created. (Take assigned PR)
But while processing through ME57 ,it is creating two PO's.
How ?
with one screen ME57 started and kept some where partially in the process of creating PO.
In another screen ,again through same me57 or ME59n ,processing the same PR and PO is created.
Now from the first screen , SAP is allowing to create another PO
Totally two PO's
How to rectify this error.
After creating PO's if we try for another PO means ,it is giving error that qty exceeded.
For your information,in our system ,we kept the message as warning which wont allow to create another PO.
What is the solution for this Issue.
Is there any OSS notes for this?
Below is the discussion for the same.
You mean , you are on the partial way of trying to create PO through ME57 and your colleagues is started processing same PR through ME59N.
After PO created by him, it is allowing you to create another PO also without error message.
REgards
KG Subramanian
<< Personal information removed >>
JK: Yes, that is exactly what we did. I run open purreqs with ME57, started to make PO of one of them (=> takes me in to ME21N) but I didn't save PO yet. Meanwhile my collague runs ME59N and after it has saved PO for this purreq I was able to save PO for same purreq without any warnings.
Where as if you try after this process you could not able to process another PO against the same PR.?
JK: Yes. If I try to find this purreq with ME57 (or ME59n) it doesn't find it which is logical as PO(s) are already there.
Also confirm me from your experience that whether is it allowed double POu2019s when these transactions done separately ? (not simultaneously processing the PRu2019s)
JK: From my experience I would say it is possible to create PO for same purreq if same purreq has been included in the original result and this "Update worklist" is not pressed:
This I'm not 100% sure and have not tested it but I'd assume so. If this update is pressed, it removes purreqs which have been turned to POseven if it is done by some other user.
Simply I can say the issue is because simultaneous processing of PRu2019s which allows creation of Double POu2019s.
Hope my understanding about the issue is correct.
Edited by: Rob Burbank on Feb 12, 2009 12:32 PM