Ansicht
Dokumentation
ABENAPC_NON_BLOCKING_MODEL - APC NON BLOCKING MODEL
ABAP Short Reference General Data in Customer MasterThis documentation is copyright by SAP AG.
- 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
- Exit
- CHECK, EXIT, STOP, and REJECT for exiting reporting events
- Wait
Using a statement like this in non-blocking mode produces the runtime error APC_ILLEGAL_STATEMENT.
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.
General Data in Customer Master rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 5497 Date: 20240426 Time: 063256 sap01-206 ( 52 ms )