SAP APC NON BLOCKING MODEL



Get Example source ABAP code based on a different SAP table
  



ABAP_APC - Non-Blocking Mode
Stateful APC processing takes place in an event-driven way:
AS ABAP as a stateful APC server
AS ABAP as a stateful detached APC client
To stop APC sessions of this type from being blocked for inbound messages, processing takes place in non-blocking mode. The following blocking statements are not allowed in non-blocking mode for APC:
Calls
SUBMIT
CALL TRANSACTION
CALL FUNCTION DESTINATION for sRFC
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 the runtime error APC_ILLEGAL_STATEMENT.



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 the ABAP Timer Manager and handled using the 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 APC processing, the statement CALL FUNCTION DESTINATION is allowed for sRFC in non-blocking mode for ADF.
ABAP_HINT_END