SAP Knowledge Base Article - Preview

1869191 - Backlog when sending IDocs in the foreground using outbound qRFC through a registered RFC destination


During times of peak load user experiencing the following:

  • In the ALE layer outbound IDocs are delayed in status 30 (delays transferring the outbound IDoc from the ALE layer to the RFC layer). For example:


"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

  • When these IDocs are finally passed to the RFC layer (status 03) there are again delays transferring them onto their final RFC destination.
  • The Max. Connection setting for the used outbound RFC destination in SMQS is not being fully utilized  - for example users have registered the destination with a max. connection setting of 5 but you only ever see 2 active connections for this destination in SMQS (despite the fact that there is a backlog of requests for this destination waiting to be processed).



  • SAP Basis ALE
  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4 HANA
  • ABAP PLATFORM - Application Server ABAP


ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions


BASIS_ALE, qRFC, tRFC, SMQS, Max.Conn., Max. Conn., Max. Runtime, No tRFC, Scheduler Monitoring, RFC Destination, ALE Layer , KBA , BC-MID-ALE , Integration Technology ALE , BC-MID-RFC , RFC , BC-CST-GW , Gateway/CPIC , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.