SAP Note 24762 - Blocking with quantities and late exclus. block

Symptom:

Program terminations, RFC problems, locking problems

Cause and prerequisites

Incorrect configuration

Solution

Change the configuration parameters in the SAP profile. If the new blocking procedure and/or the late exclusive material block is to be implemented, make sure that an RFC is sent to the lock indicator server for each availability check and/or material movement. Since, in principle, many availability checks and/or material movements can be carried out in parallel, some gateway and SAP profile parameters need to be extended to avoid terminations due to lack of system resources.

1. There needs to be enough dialog work processes on the enqueue
server, since the RFCs are processed in dialog work processes.
(approx. 5 dialog work processes)

2. Users log on to the enqueue server using the RFCs, therefore, the
following parameters need to be at least as large as the maximum
number of parallel open SAP transactions which are carried
out by at least one availability check (for example, VA01

VL01).and/or one material movement (for example, MB01,...).

rdisp/tm_max_no
rdisp/max_comm_entries
gw/max_conn

These parameters do not use many resources (storage), and can, therefore, be selected generously - approx. 500 is normally completely sufficient.

3. Additional SAP rolling occurs on the enqueue server due to the
RFCs, therefore, rdisp/ROLL_SHM may need to be extended

The profile parameters only become effective after restarting the application servers.

Additional key words

Blocking with quantities, late exclusive material block, OMJI
COMMUNICATION_FAILURE