This parameter determines the maximum number of asynchronous requests that can be kept in the local work process queue.

The value should only be changed after consultation with SAP.


If a lot of RFC balancing accumulates on one application server and the value of parameter rdisp/max_comm_entries has been increased to accommodate this, we recommend you set rdisp/max_arq to the same value.


AA A SAP work process can contain diverse messages: 

?     Requests from a SAP-GUI

?     Requests from an ABAP program (RFC requests)

?     Requests from other WPs/application servers (messages)

?     Results of outstanding calls (enqueues, RFCs)

The procedure is always that a message leads to the work process being activated. The work process performs an action, possibly sends a result back and then waits for a new message.

There are also cases where while one message is being processed, other messages are sent and depending on the circumstances, it may take a while before they can be dealt with. Examples of this are enqueue and establishing RFC connections. Particularly with asynchronous RFC, the RFC replies can be sent at any time you want.

As the work process cannot, however, process every type of message in every situation, each WP context has a local queue. Here messages that cannot be immediately processed are stored temporarily. The parameter rdisp/max_arq defines the size of this local queue.


Work area



Integer value

Standard value


Dynamically changeable

Local and on all servers