ENQUEUE PROCESS Explanation

ENQUEUE PROCESS

It is used to enque/deque (lock/unlock) the objects during an update. By default one enue process is installed along with Message Server. It is possible to configure more than one enque process in a massive update system. Enque processes are configured by using parameter.

rdisp/wp_no_enq=2

ENQUEUE PROCESS FLOW

1. User submits the request for an update.

2. The request is received by dispatcher and keeps it in wait queue.

3. Based on freely available Dialog process, the dispatcher allocates a process to user request.

4. When dialog identifies update then it communicates with enque process to obtain lock on the record, so that no other user modifies it and has only a display access. These locks are displayed in SM12.

5. If the update request is made through an application server. The Dialog Process communicates with message server and message server in turn communicates with enque process to obtain lock on behalf of the dialog process.

Message server obtains the lock from enque process and provides to dialog process.

Generally the enque time on the Central Instance is 1ms to 5ms. If more than one dialog instances are configured then the enque time can go up to 100ms(if it goes beyond then turn on the enque trace for RCA(ROOT CAUSE ANALYSIS))
‪@sapbasishana‬
For MORE details - contact: [email protected]

#SAP #BASIS #SAPHANA #SAPECC #TRAINING #PRACTICAL #JOBORIENTED #HANDSON
#MIGRATION #S/4HANA #s4hana #IT #freshersjob #FRESHERTRAINING #freshersworld #STUDENT # ​#REALTIMETRAINING #BEGINERS #saphanatraining #saptraining #sapbtp #sapbasis #saptraining #sapbasishana #btp #s #telugu #trending #s4hana