SAP ADF NON BLOCKING MODEL



Warning: file_get_contents(/customers/9/5/e/s4hd.com/httpd.www/global/php/adxcode.txt): Failed to open stream: No such file or directory in /customers/9/5/e/s4hd.com/httpd.www/global/php/helpers.php on line 89

Get Example source ABAP code based on a different SAP table
  

Warning: Undefined variable $prev in /customers/9/5/e/s4hd.com/httpd.www/sap/help/index.php on line 55

ABAP_ADF - Non-Blocking Mode
ABAP daemon processing is event-driven. To prevent an ABAP daemon session type from being blocked for inbound messages, the session runs in non-blocking mode. 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.



Latest 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.
ABAP_HINT_END