Skip to content

ABAP Keyword Documentation →  ABAP - Release-Specific Changes →  Changes in Releases 7.5x →  Changes in Release 7.50 

RFC and ABAP Channels in Release 7.50


1. Dynamic destinations in RFC


2. Point-to-point communication for AMC


3. Enhancements for APC


4. Forbidden accesses for APC

Other versions: 7.31 | 7.40 | 7.54

Modification 1

Dynamic Destinations in RFC

The methods of the class CL_DYNAMIC_DESTINATION are used to manage dynamic RFC destinations in Release 7.50 and higher. In particular, the method CREATE_RFC_DESTINATION makes it possible to create a dynamic destination, which can be used in the current sessions for RFCs.

Modification 2

Point-to-Point Communication for AMC

Alongside the general publish-and-subscribe mechanism, a point-to-point communication option was introduced for the ABAP messaging channels (AMC). Here, a sender object addresses precisely one receiver session. The send action can be either synchronous or asynchronous. This is done using the new factory method CREATE_MESSAGE_PRODUCER_BY_ID of the class CL_AMC_CHANNEL_MANAGER. The ID of a receiver session is provided by the method GET_CONSUMER_SESSION_ID of the same class.

Modification 3

Enhancements for APC

The framework for ABAP channels (APC) was expanded as follows:

  • Alongside communication using the WebSocket protocol, communication using TCP sockets is now also possible.
  • An AS ABAP used as an APC server can now also stateful. Until now, only stateless servers were possible.
  • An AS ABAP as operate as an APC client.
  • Clients known as detached clients make it possible to open an APC connection to a stateless or stateful APC server and then detach it again immediately so that it can be accessed using attached clients.
  • A connection handle can be used to access existing APC connections across the entire system.
  • A non--blocking model was introduced for stateful APC applications.
  • The class CL_APC_TIMER_MANAGER creates timer managers that can be accessed using the interface IF_APC_TIMER_MANAGER. A timer manager makes it possible to start and stop a timer in stateful APC applications in which the statement WAIT is not allowed. The interface IF_APC_TIMER_HANDLER is used to handle timer events.

See also the ABAP Channels documentation in SAP Help Portal.

Modification 4

Forbidden Accesses for APC

Up to now, any repeated attempts to bind a push channel to a bound messaging channel or any attempts to remove a nonexistent binding were ignored. From Release 7.50, both situations raise an exception.