Performance problems when processing IDocs immediately

[] []

Symptom
All dialog work processes are used up processing IDocs. General performance problems when processing a high volume of IDocs. There is a delay in sending outbound IDocs (IDocs “stuck” in status 30).You note entries queued up on the sending side in transaction SM58 for function module IDOC_INBOUND_ASYNCHRONOUS with the status “Transaction Recorded”.There is a delay posting inbound IDocs on the receiving side(IDocs “stuck” in status 64).
Other terms
Status 64 No resources,immed. processing not possible.
Reason and Prerequisites
You are attempting to process a high volume of IDocs in the foreground.
Solution
The “Process Immediately” \ “Transfer Immediately” option should not be used for high volume, noncritical transactions because you will encounter resource problems such as this. Instead you need to ensure you are using background processing for your ALE communications. Configure program RBDAPP01 (inbound) \ RSEOUT00 (outbound) to run very
specifically for the high volume message types on your system. Schedule regular runs of reports RBDAPP01 & RESOUT00. These can be run for IDoc Type and\or Partner etc.. You can configure these reports to run every 10 minutes or as often as required.
Then change the processing mode for the IDocs in question as follows:
For inbound:
-> go to transaction WE20 -> Select Partner Select Inbound Message Type and change the processing method from “Trigger Immediately” to “Trigger by background program”.
For Outbound:
-> go to transaction WE20 -> Select Partner Select Outbound Message Type and change the processing method from “Transfer IDoc Immedi.” to “Collect IDocs”
What will happen then is that these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work
processes) in batch mode leaving dialog work processes free for
users and mission-critical processes. Hence you will not encounter
the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode
switches (see SAP note 74141). However when there are a large number of IDocs being processed this is not a practical solution.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment