Ansicht
Dokumentation

ABENNON_BLOCKING_MODEL - NON BLOCKING MODEL

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

APC - Non-Blocking Model

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, the programming must follow a model known as the non-blocking model. The following blocking statements are not allowed in the non-blocking model:

• Calls

• SUBMIT

• CALL TRANSACTION

• CALL FUNCTION DESTINATION for sRFC

• CALL DIALOG

• CALL SCREEN

• CALL SELECTION-SCREEN

• SET SCREEN

• COMMIT WORK

• 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 ...

• MESSAGE with the message types "I", "W", and "E"

• COMMUNICATION

Using a statement like this in the non-blocking model produces the runtime error APC_ILLEGAL_STATEMENT.

Note

The statement WAIT is not allowed in the non-blocking model. To make it possible to wait for specific events despite this (such as ending a callback routine in aRFC), the class CL_APC_TIMER_MANAGER can be used to create a timer manager accessed using the interface IF_APC_TIMER_MANAGER. A timer manager makes it possible to start and stop a timer in stateful APC applications. Classes that implement the interface IF_APC_TIMER_HANDLER can handle events of the timer such as ON_TIMEOUT.

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4795 Date: 20240420 Time: 052127     sap01-206 ( 22 ms )