Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from R. N. Wilhite on Mar 30 at 9:47 AM Just to add to the confusion. SAP does not necessarily follow their own
rules. 53 should not be applied before the final commit is successful.
However SAP might do something else, like... go to the commit supporting
module of the transaction and assuming that it will go through apply the
53. Then a user exit may hit, fail, and cause a rollback. Your IDoc now
has what SAP considers to be a legitimate 53, but an error occurred that
stopped what SAP expected.
Neal
| | | ---------------Original Message---------------
From: john.louk
Sent: Friday, March 29, 2013 2:37 PM
Subject: Can a IDOC 53 have any errors?
I can code any number of messages in the Inboind IDoc routine (usually a function module). I can also set the status for every message. This is possible in a custom IDoc program and may of the standard programs (user-exits, enhancement spots). It also depends whether the message returned into the inbound idoc routine are of the correct severity (i.e., error, etc.). Also, like the Sales Order example it could be that the data would cause errors that would then be placed on the sales order's incompletion log. This would probably not send back the severity that would cause an IDoc error status.
Also, usually the 51 status is used for errors where there is no document created or updated in SAP. This means that he IDoc can be fixed and re-processed. And, a 68 status is often used when there is an error but some document was successfully created/changed in SAP but there were errors (maybe a followon document could not be created). This means that the IDoc CANNOT be changed and re-processed. This can also be coded.
So, is the Idoc using custom code or standard code? |
| Reply to this email to post your response. __.____._ |   _.____.__ |
