Proactive measures to avoid heavy load on background processing due to TRFC failure :
If errors occur during Remote Function Call, these are processed in individual error handling in the Standard R/3 System. For each incorrect RFC, the SAP R/3 System schedules a batch job (ARCF* jobs) which starts the RFC repeatedly until processing is successful. If the link to the destination system is interrupted, this can lead to a large number of batch jobs being created, thus placing a heavy load on the transmitting system that is processing the jobs. This heavy load on background processing might have performance impact on system.
Proactive measures to avoid this heavy load on background processing :
When the system is in use, it is absolutely necessary that you use the collective error handling facility to improve system performance. When you use this method, RFC transmissions are not automatically repeated immediately. Instead, a periodically scheduled batch job (RSARFCEX) collects the incorrect RFCs and transmits them again as a package. As a result, the number of batch jobs is kept to a low level. This feature is available for R/3 and TCP/IP links.
Settings needed in RFC connection :
Suppress background job by communication error : (Please have a look at OSS Note 185670)
1. Call Transaction SM59.
2. Choose the corresponding 'Internal connections' and enter an 'X' under 'Destination' --> 'TRFC options' for parameter 'Suppress background job if conn.error'.
3. Save the data.
Thanks
Atul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 |