Hi,
An IDOC could go an error due any reason. It may not be created at the receiver end or may go to an error after being created.
If it's an error after being created check for the status of the IDOC and debug the IDOC correpondingly. These errors are mostly due to errors in configuration of IDOC like conversion rules and mapping. Check your configuration once and make sure its correct.
Check for the status of the IDOC and make sure if it's transferred or not.
If not transferred check the file log for any errors. For no error in file log check the system log for any error and restart from begining.
For any errors in file log, check the file contents at the record number logged in the file log. Fix the IDOC file from point of failure and restart from begining by copying the file with a different name.
Inspite of all things being right, an IDOC still can goto an error. This could be due to datatype mismatch or something like that in such a case you can try editing the IDOC while processing it. Though this is not recommended it helps out in these situations.
Before editing the editing the IDOC while processing make sure you have your superiors permission so that you are not in trouble when an audit is done.
Hope so am helpful to you.
Raga Suman.
just see the status of that IDoc if it turns RED then that IDoc is not transferred to destination system.
an error message pops for an IDoc soz even there is single error among 200 object it wont get transferred
WE02 or WE05 tx will help u see the status od an IDoc in inbound as wel as outbound systems.
Which status u found based on that we can excute the standard programs.
If it only one error in one record remining records are correct then it can transfer to target system. I think all the records having the same error.
I think u got the status in inbound is 21 or 61.
Error in application communication Error.
Plz chek the SM59.
And go through this we05 and we19(debug the idoc).
Bluesky
