ABAP Keyword Documentation →  ABAP − Reference →  Data Interfaces and Communication Interfaces →  ADF - ABAP Daemon Framework 

ADF - Non-Blocking Mode

ABAP Daemon processing is event-driven To stop an ABAP Daemon session type from being blocked for inbound messages, the the session runs in non-blocking model. In non-blocking mode for ADF, the following blocking statements are forbidden in ABAP Daemon processing and in the procedures called here:

• Calls

• SUBMIT

• CALL TRANSACTION

• CALL DIALOG

• CALL SCREEN

• CALL SELECTION-SCREEN

• SET SCREEN

• Exit

• LEAVE LIST-PROCESSING

• LEAVE PROGRAM

• LEAVE SCREEN

• LEAVE TO TRANSACTION

• LEAVE TO LIST-PROCESSING

• CHECK, EXIT, STOP, and REJECT for exiting reporting events

• Wait

• WAIT UP TO, WAIT FOR ...

• COMMUNICATION

Using a statement like this in non-blocking mode produces a runtime error.

Other versions: 7.31 | 7.40 | 7.54

Notes

• The statement WAIT is not allowed in non-blocking mode. To be able to wait for certain events despite this restriction (such as the end of a callback routine in aRFC, ABAP Timers can be used. An ABAP Timer is created by ABAP Timer Manager and handled using ABAP Timer handlers. The associated class and interfaces are CL_ABAP_TIMER_MANAGER, IF_ABAP_TIMER_MANAGER, and IF_ABAP_TIMER_HANDLER. ABAP Timers can only be used in non-blocking mode, namely APC and ABAP Daemon sessions.

• Unlike in non-blocking mode for APC, the statement CALL FUNCTION DESTINATION for sRFC is allowed in ABAP Daemon processing.