MTSG
asked on
MM - Purchasing Messages - OPEN_FORM Error
PO Not being faxed or Printed. When I look at the message determination it says incorrectly processed. When I look at the processing log it says
error in OPEN_FORM for document "PO Number"
Using SAP Print Program and our own layout set.
Out put type NEU only fails. I have another ZNEU that does emailing and this works fine.
If I try to re-print or refax it allows me to do this.
What can the problem be???
ThanX
Y.M.
error in OPEN_FORM for document "PO Number"
Using SAP Print Program and our own layout set.
Out put type NEU only fails. I have another ZNEU that does emailing and this works fine.
If I try to re-print or refax it allows me to do this.
What can the problem be???
ThanX
Y.M.
ASKER
Hi Jon
Thanks for the response, but I forgot to mention that this does not happen all the time. It randomly happens to different Purchase Orders, if I repeat the output then it works fine with no errors.
Regards
YM.
Thanks for the response, but I forgot to mention that this does not happen all the time. It randomly happens to different Purchase Orders, if I repeat the output then it works fine with no errors.
Regards
YM.
OK.
I suspect then that this is something to do with the update task not being finished.
Is there anything in the log (SM21) when this happens ?
Does it only happen for the first attempt at sending the message when the PO is first saved ?
is there anything else in the processing log on the message that gives any more clues ?
Is there an applicaiton log for POs ? i can't remember.
Don't you just hate these un-reproduceable random errors !!!
I suspect then that this is something to do with the update task not being finished.
Is there anything in the log (SM21) when this happens ?
Does it only happen for the first attempt at sending the message when the PO is first saved ?
is there anything else in the processing log on the message that gives any more clues ?
Is there an applicaiton log for POs ? i can't remember.
Don't you just hate these un-reproduceable random errors !!!
ASKER
I had a look at SM21 there is no log for PO.
Yes, so far I only seen it happen on the first attempt.
No other clues just says message no 142 - Error in Open_Form for document
ThanX for the help.
YM.
Yes, so far I only seen it happen on the first attempt.
No other clues just says message no 142 - Error in Open_Form for document
ThanX for the help.
YM.
If it only happens on the first attempt it maybe that one of the Update tasks has not finished.
You could change the output condition so that the Output is sent "Send with perridoically scheduled Job" then schedule the job RSNASTED to run every 10 mins or so on.
What this will do is allow the update tasks to finish before it attemtps to send the message.
However this is just a guess - even with access to the system these types of problems are notoriously difficult to pin down.
Cheers
Jon
You could change the output condition so that the Output is sent "Send with perridoically scheduled Job" then schedule the job RSNASTED to run every 10 mins or so on.
What this will do is allow the update tasks to finish before it attemtps to send the message.
However this is just a guess - even with access to the system these types of problems are notoriously difficult to pin down.
Cheers
Jon
ASKER
Hi Jon
I think we have found the problem - There was a project done to change all the user names to the network logon names, seems that since than we started having these problems. It seems to only come up when PO's are mass released (If the first PO for release fails, it does not close_form and results to the rest of the PO for releasing to also fail.)
I think we have found the problem - There was a project done to change all the user names to the network logon names, seems that since than we started having these problems. It seems to only come up when PO's are mass released (If the first PO for release fails, it does not close_form and results to the rest of the PO for releasing to also fail.)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
CHeck to see if you have any related short dumps ST22 or Log entries SM21 that might give you a clue.
Otherwise you can debug the print program. As the messages are normally sent in a background task you cant debug from the ME22 so you need to send the output manually.
In order to do this place a breakpoint in the print program.,
Repeat the output record but select the "further data" and change the processing time to "Send with perridoically scheduled Job"
then go to transaction WE15
Enter the output type iput the PO number in the object key field with a * at either end of it.
and add the output type clear the transmission medium.
Run that and it should stop at your breakpoint.
When you debug you are looking for anything that causes the program to exit with anSy-SUBRC > 0.
Good luck.
Jon