TRFC issue Check the LUW,s in SAP transaction SM58.

The ones that are stuck in the queue will be shown as red. You can reprocess with F6. There is also a job that can do this automatically for you.

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.

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.

In SM58 I can see the tRFCs with a status of 'Transaction recorded'. These can be pushed through in SM58 via 'Execute LUW' or by running RSARFCSE and specifying the Transaction ID. However, running RSARFCSEX seems to do nothing at all.

To ensure this, an entry category in SMQS can have the following values/definitions:

"R": The destination has been registered with the QOUT Scheduler. The QOUT Scheduler executes the transfer or processing of the tRFC/qRFC records.

"U": The destination has been registered temporarily. All entries with this destination remain in the status "Transaction recorded" until this destination has been registered or these entries have been manually activated using transaction SM58 (for tRFC) or transaction SMQ1 (for qRFC). This is necessary to debug the tRFC/qRFC function or to suspend the transmission for a certain period of time.

"N": Destination is excluded for the QOUT Scheduler. The sending occurs as previously (immediately and asynchronously to the application). Note that, as described in Note 437718, problems with resource bottlenecks could occur in connection with the update, although this problem was significantly reduced as of qRFC version 6.20.043.

tRFC & qRFC queue in Transaction Recorded status

Written by Kevin Wilson

tRFC Monitor (tx: SM58), qRFC Monitor for the outbound queue (tx:SMQ1): Status Transaction recorded (LUW with update records) {mosbanner:id=42,41} This status appears when both the update task and tRFCs or qRFCs are called within the application LUW. The tRFCs or qRFCs are delayed until the V1 update is complete. The status of the tRFC or qRFC LUWs is then set to READY and the LUWs are executed. If the update record is deleted in transaction SM13, all related tRFC LUWs and qRFC LUWs are deleted from the tRFC and qRFC tables.