SAP Knowledge Base Article - Preview

1872637 - Delays posting inbound IDocs (status 64) which have been configured to trigger immediately

Symptom

  • Too many dialog work processes are used up processing IDocs.
  • Delays posting inbound IDocs (IDocs "stuck" in status 64)
  • ST22 dump EXPORT_TOO_MUCH_DATA CX_SY_COMPRESSION_ERROR when using RBDAPP01

For example inbound MATMAS IDocs are configured as follows in partner profile LS/T90CLNT090 (transaction WE20):

Inbound Partner Profile Before Change.png

The majority of these Idocs are not being posted to the application layer immediately - when user display them using transaction WE02, can see they are stalled in status 64:

Status_64_Screen1.PNG

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


Read more...

Environment

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

Product

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

Keywords

BASIS_ALE, MATMAS, Trigger Immediately, Trigger by background program, batch mode, RBDAPP01, dialog, work processes, sleep, F111, RBDSTATE, ORDCHG , KBA , BC-MID-ALE , Integration Technology ALE , SV-PERF , Performance Problems , Problem

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.