Idoc Status 30

[chunhan]

Hi Expert ,

I believe that most of you already familiar with the issue which is idoc stuck on status 30.
However , I still cannot find any solution yet.

Here is my problem :

I have a scheduled job to process idoc status 30 daily. However , it didn't work since few days ago and there is no changes recently.
I did checked the job and there is no error and the job status is finished.

WE20 setting: Collect Idocs /  output mode 4.

My question is:
Any other settings or configuration that I can check ?

Thanks.

[engswee · Accepted solution]

Hi Chun Han

Is the background job using standard program RSEOUT00 or some custom program?

Are you able to manually trigger the IDocs from status 30 to 03 using tcode BD87?

Can you check if there are any lock entries in tcode SM12 for the IDoc tables (EDID*)

Rgds

Eng Swee

[chunhan · Accepted solution]

We use custom program to trigger the idocs to middleware. I tried to check lock table thru SM12 but not able to find anything related.
Those pending idoc not able to push out with bd87 or we14. So i guess its locked in some where else.

Anyhow , I will ask our ABAP team to check where was the idoc locked. 😃

[chunhan · Accepted solution]

Do u have any idea why i'm not able to use BD87 to push out the idoc ?

this is the screenshot after i process from bd87.

[engswee · Accepted solution]

Hi Chun Han

My previous encounters with outbound IDocs being stuck at status 30 is due to the IDoc have lock entries.

Not sure why even using BD87 does not work in your case.

One more alternative you can try is to use the program RC1_IDOC_SET_STATUS to change the status 30 --> 03, then change it back to 03 --> 30, then reexecute BD87.

Rgds

Eng Swee

[chunhan · Accepted solution]

Hi Eng Swee ,

It doesn't work.
EDID* table no lock entries , SM58 no queue transaction , BD87 cannot process idoc.
Kinda frustrating . . . .

thanks