5/11/2021 Re-process the IDOC ID | SAP Blogs

Community

Ask a Question Write a Blog Post Login

Technical Articles

Anusha Kotagiri
October 23, 2019 2 minute read

Re-process the IDOC ID

Follow RSS feed Like

2 Likes 9,055 Views 8 Comments

Introduction:

This blog post is about reprocess the IDOC, while getting an error to post the inbound IDOC.

In this blog post you can see how to nd the issue or how to debug the existing error IDOC.

Requirement:

Getting an Error in the existed IDOC ID while processing. To Find out the Error need to re process and debug the
IDOC ID the below steps as follows.

Steps to Re-process the IDOC ID:

 Step 1:

1.  Go to the Transaction “WE02“. To display the IDOC information i.e existing IDOC.

2.  Enter the Idoc as shown in the below.

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 1/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

3.Click on execute button then it will display the information of IDOC as shown in below screen.

4. It shows the current status of IDOC, In the above screen shot it shows the error message(Application
Document not posted) and current status as 51.

Step 2:

1.  Go to the Transaction “WE19”. To get more information about the existing IDOC.

2.  Enter the existing IDOC and execute as shown in the below.

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 2/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

3. Then we will get the below screen  and click on Standard Inbound as shown in the below screen shot.

4. Then it will show the Function Module name and logical message as shown in the below screen.

 
https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 3/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

5. Then click on OK button  and it will generate the IDOC.

6. Copy that newly generated IDOC shown in the below.

Step 3: 

1. Then go to the Transaction “SE37” and enter the function module (ZAU_CONCUR_IDOC_UPLD) put a break
point in the function module as shown in the below.

Step 4: 

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 4/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

1.Go the Transaction “BD20“, enter the newly generated IDOC and execute.

2. After click on execute button, it will trigger into the function module as shown in the below.

3.By debugging the function module,we can able to gure out the issue, why the Idoc is not processed.

Conclusion:

After triggering into the Function module by giving the newly generated IDOC number, then we can debug that
function module, at some point we are able to gure out  the issue with the below messages and status.

Error message with the description:

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 5/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

Status                                         Description

51                                                Application document not posted

52                                                Application document not fully posted

Success message with the description:

Status                                        Description

53                                                Application document posted

Thanks in advance!!

Alert Moderator

Assigned tags

ABAP Development | SAP ERP | abap idoc | sap abap |

Related Blog Posts

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 6/10
5/11/2021 Re-process the IDOC ID | SAP Blogs
Sending a IDOC to the same client in a SAP system
By Mainak Aich , Sep 20, 2015
Add customized message during Idoc outbound processing for output type
By Jigang Zhang 张吉刚 , Mar 25, 2021
LSMW – use IDOC to create source list
By Former Member , Nov 06, 2013

Related Questions

Can I Re-process Idoc from status 68 to any other status?

By Former Member , May 09, 2007
IDOCs
By Former Member , Mar 29, 2007

regarding errpr idoc reprocess

By Former Member , Apr 14, 2009

8 Comments

You must be Logged on to comment or reply to a post.

Sandra Rossi

October 23, 2019 at 7:18 pm

Your scenario works only when the partner pro le (WE20) is de ned with the option "Trigger by background
program". If it's de ned with the option "Trigger immediately", the function module is called immediately after
the IDoc is created, and it's not needed to run BD20 in that case.

Speci cally, in the step 2, if you see a green icon with the text "Trigger immediately" (instead of yellow icon with
the text "Trigger by background program"), add a breakpoint immediately to the function module before "5.
Then click on OK button  and it will generate the IDOC".

Like(4)

Jelena Per ljeva

October 23, 2019 at 8:31 pm

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 7/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

1. This is not "reprocessing", WE19 creates a copy of an IDoc. In this scenario nothing happens to the original
IDoc. For the real reprocessing (i.e. processing an IDoc in error again) we can use BD87 transaction. And
there is no such thing as "reprocessing IDoc ID". Sorry, that just makes no sense.
2. The blog leaves an impression that WE19 is the only tool to do this. But in fact, we could use the actual re-
processing transaction BD87 just as well with the original IDoc. It's also not explained in the blog what WE19
actually does.
3. Why are we going to WE02? Where did you get the IDoc number? And, when in WE02, we don't even expand
the status to check the error message? What is the purpose of any of these activities?
4. As Sandra correctly noted, this process works only with the speci c con guration. In other cases, we'd need
to set up a breakpoint rst and then start IDoc processing. BD20 may not be needed at all and again, no
explanation, what does it do exactly.
5. Setting a breakpoint in the processing FM could take one on an extremely long journey in debugger. I'd
suggest to set a breakpoint somewhere closer to where the actual problem occurs. (This could be an IDoc
user exit, for example.) But, unfortunately, this goes back to the previous points: it's not explained what the
problem is in the rst place and why are we doing this.
6. The conclusion is confusing: there is no problem with the success status, so how is this relevant? Also WE19
can be used for many other things. But that was just left out completely from the blog, unfortunately.

Going forward, I'd suggest the following when considering posting a blog on SCN:

1. Search for the existing blogs to identify if new information needs to be added or if some points were not well
covered. Include the links to any existing SCN posts and other sources. E.g. this is an existing blog on WE19.
2. Describe the back story and purpose more clearly. For example, what prompted posting a blog? What
speci c issue have you encountered?
3. When telling the readers to do the speci c steps, we need to be able to explain to them why this is needed.
Why this transaction and not the other? What is the purpose and expected outcome? Unless it's a personal
story, a technical blog needs to educate the readers.
4. Make sure to use proper SAP and IT terminology, proper grammar and capitalization. For example, it's
"IDoc", not "IDOC" or "Idoc". Attention to details is important and lackadaisical approach to technical writing
re ects poorly on the author.

Please update the title to avoid misleading the readers and I hope that your next post will be written with the
information above in mind.

Thank you.

Like(10)

Sijin Chandran

October 24, 2019 at 8:23 am

Am pretty much sure your comment will garner more "Likes" than this Blog post's.

Like(0)

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 8/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

Sandra Rossi

October 24, 2019 at 9:35 am

Here is my little word for encouraging:

This blog post is not bad at all, compared to many others. Of course it misses the context as you explain well,
and there are approximations, but people can't be experts in everything.

I see an important e ort to explain the most clearly possible what the poster knows. Bloggers are often not
experts and so there are some uncertainties in what they say Our job as “SME” is to correct them, and the
poster should then check if what we say makes sense and is true (who knows we are really “experts”?), and edit
the post to improve it.

I tried to nd another blog post about the topic of reprocessing, and couldn’t nd something equivalent. So the
post is interesting. Adjusting its content would be really great

Of course, thank you Jelena for this big e ort to explain the approximations, and give these smart tips for better
blogging (the 3 rst steps are nicely expressed and so much important – worth a blog post? I don’t nd one in
SCN)

Like(2)

Jelena Per ljeva

October 24, 2019 at 7:56 pm

Sandra Rossi - thanks for your comment! There was one blog posted speci cally about WE19 (linked in my
comment) but it's not very good. It's pretty much the same information but at least it correctly identi es the
purpose of this transaction.

There are actually tons of blogs already on how to write better blogs, if only people would read them. Just a
few from the top of the Google search:

How to write the perfect blog post

Build a Better Blog

Bloggers: Write Frankly and Fearlessly (some great recommendations from Jim Spath )

Like(1)

Sandra Rossi

October 24, 2019 at 9:06 pm

Thank you. After reading quickly these posts, I nd your advice even better

Like(0)

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 9/10
5/11/2021 Re-process the IDOC ID | SAP Blogs

Mohit Sharma

October 24, 2019 at 8:56 am

Hi Anusha Kotagiri

Please make the adjustments as already suggested by Sandra and Jelena.

I am glad to see the SME's like Sandra Rossi and Jelena Per ljeva sharing there valuable experiences, which
indeed will help all of us to improve.

Regards,

Mohit Sharma

Like(3)

Thammunuri Ramya

December 16, 2020 at 10:06 am

Nice blog Anusha, thanks for sharing.

Like(0)

Find us on

Privacy Terms of Use

Legal Disclosure Copyright

Trademark Cookie Preferences

Newsletter Support

https://blogs.sap.com/2019/10/23/re-process-the-idoc-id/ 10/10