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 you display them using transaction WE02 you can see they are stalled in status 64:

Status_64_Screen1.PNG


Read more...

Environment

Release Independent

Product

SAP NetWeaver all versions

Keywords

KBA , BC-MID-ALE , Integration Technology ALE , SV-PERF , Performance Messages , Problem

About this page

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

Search for additional results

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