jazgeek
IS-IT--Management
- Jan 29, 2004
- 541
Interesting bug that may occur in an environment where purchase order processing is being used. I've verified it on 2 installations and I'm wondering if it's just me or a coding issue.
This bug has been in the system since at least v5.5 and perhaps before that if using explorer(smartlist)
Anyway, onto the bug.
open a purchase order
produce the purchase order as you normall would, filling in header and at least 1 detail ine.
now before saving, go to smartlist and browse purchase orders. Select one you know is still an open/unreceived purchase order and double click it as if you wanted to open it in the purchase order entry screen.
The purchase order entry screen should now have your smartlist selected purchase order in it right?
Ok.... but what happened to your unsaved purchase order? Clear the smartlist selected purchase order and try to open up the purchase order you were entering and didnt' save.
"unable to open purchsae order because someone is editing it" error should occur.
solution, open SY00801 from enterprise manager in sql and delete the line with the unsaved purchase order on it.
I get this error at least 6 times a week.
-----------
and they wonder why they call it Great Pains!
jaz
This bug has been in the system since at least v5.5 and perhaps before that if using explorer(smartlist)
Anyway, onto the bug.
open a purchase order
produce the purchase order as you normall would, filling in header and at least 1 detail ine.
now before saving, go to smartlist and browse purchase orders. Select one you know is still an open/unreceived purchase order and double click it as if you wanted to open it in the purchase order entry screen.
The purchase order entry screen should now have your smartlist selected purchase order in it right?
Ok.... but what happened to your unsaved purchase order? Clear the smartlist selected purchase order and try to open up the purchase order you were entering and didnt' save.
"unable to open purchsae order because someone is editing it" error should occur.
solution, open SY00801 from enterprise manager in sql and delete the line with the unsaved purchase order on it.
I get this error at least 6 times a week.
-----------
and they wonder why they call it Great Pains!
jaz