Idocs stuck in tRFC queue - why?

[Former Member]

We had an issue where 2 Idocs looked like they where sent from our

logistics box to our HR box, but in reality, they were stuck in the tRFC

queue in our logistics box.

The idocs were created 2 days ago and were never processed. When I found

them in SM58, I executed them and they were sent and processed

successfully.

Why would those idocs get stuck in the tRFC queue? Shouldn't the queue

auto-process those idocs?

thanks,

robert.

[Former Member]

We had an issue where 2 Idocs looked like they where sent from our

logistics box to our HR box, but in reality, they were stuck in the tRFC

queue in our logistics box.

The idocs were created 2 days ago and were never processed. When I found

them in SM58, I executed them and they were sent and processed

successfully.

Why would those idocs get stuck in the tRFC queue? Shouldn't the queue

auto-process those idocs?

thanks,

robert.

[varma_narayana]

Hi..

Normally this will happen when you Set the "Collect IDOCs" Option in the Partner profile Outbound Message type.

In that case these IDOCs will be dispatched only when the RSEOUT00 program runs in Batch or Explicitly.

If you set "Transfer Immediately" option in Partner profiles then they will be dispatched Immediately.

reward if Helpful.

[Former Member]

these idocs are set to trigger immediately .

as far as collecting them, that's not the same queue i'm talking about. those idocs that are collected can be processes with BD87.

these idocs looks as if they have already been through RSEOUT00 but they were really in the tRFC queue waiting to be processed.

[Former Member]

<b>note</b>: there were several hundred other idocs of the same message type processed before and after these 2 were stuck.

I simply went to SM58 and processed them - they were not incorrect in any way.

[Former Member]

Hi,

There are a number of reasons to get entries in SM58. For instance if the receiving system is not reachable (e.g. network problems). (Or if there is a short-dump when the receiving system tries tro process the call I think).

You can schedule report RSARFCEX to automatically process entries that are stuck in SM58.

BR,

Peter

[Former Member]

thanks.. we do plan on scheduling RSARFCEX to run daily... but we wanted to get an idea why they were stuck in the first place.

[Former Member]

Hi, have you already found the reason?

[Former Member]

I think the only hint you can get on what went wrong is looking at the "Status Text" field in SM58 before you reprocess the entry.