The purpose of this document is to provide some high level generic tips and tricks you can potentially use to optimise ALE performance.
This is a list of a few useful tips and tricks to help you optimize ALE performance. These suggestions are of course very general - there is no way to cover all possible customer permutations.
Bundle Idocs where possible when sending and updating
This avoids problems with many “little” IDocs flooding the system. Also be sure to use an appropriate "packet size" in the partner profile so a number of IDocs are bunched together in the same DIA work process for processing. This again reduces the burden placed on the system by the ALE layer and will help optimise overall system performance.
When possible avoid processing IDocs during peak usage times
Process IDocs with batch jobs and schedule these jobs (reports RBDAPP01 for inbound posting and RSEOUT00 for outbound) where posible to run during times of low resource usage in the landscape.
Schedule mass transfer/updates when there is low dialog activity. If that is not possible spread out the work load evenly over a larger time frame and limit the resources for IDoc processing.
Avoid processing mode “immediately” whenever possible (sender and receiver)
SAP always recommends you process Idocs in the background when possible. For more information on this please see SAP note 1333417 "Performance problems when processing IDocs immediately".
Archive/delete IDocs and work items (error notifications and container linkage items) on a regular basis
Adjust the number of dialog work processes (sender and receiver).
Use RFC server groups for parallel update and post IDocs in parallel
In systems with a high volume of Idocs for processing, it has been shown that the use of special “RFC” application servers makes it easier for customers to avoid overload situations and balance the load generated during peak times. For more information please see SAP notes 103523 "RFC Load Balancing", 986373 "RFC load distribution"