Ansicht
Dokumentation

ABENRFC_EXCEPTION - RFC EXCEPTION

ABENRFC_EXCEPTION - RFC EXCEPTION

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

- Exceptions

In the interface of a remote enabled function module, it is currently only possible to specify classic exceptions, that is, non-class-based exceptions. Class-based exceptions are supported only in internal SAP release tracks.

In an external function call, the non-class-based exceptions defined in the interface of the function module called using the EXCEPTIONS addition of the statements CALL FUNCTION or RECEIVE can be assigned return values.

If EXCEPTIONS is specified, classic exception handling is performed. If a remotely called function module raises a class-based exception, this exception is not transported and raises the predefined classical exception SYSTEM_FAILURE instead

In addition to the exceptions that are specified explicitly in the interface of a remote-enabled function module, the following predefined exceptions can occur in the RFC:

  • SYSTEM_FAILURE.
This exception can be caused, among other things, by error situations that arise when a remotely called function is executed on the RFC server. These error situations can be caused by runtime errors or sending a message of type A, E, or X.
  • COMMUNICATION_FAILURE, RESOURCE_FAILURE (only with pRFC or SYSTEM_FAILURE)
These exceptions are raised by all errors that occur when connections are being established, when resources are being assigned, or in the communication layer.

It is strongly recommended that all predefined exceptions are handled.

Notes

  • If a remotely called function module raises a class-based exception, this always raises the predefined exception SYSTEM_FAILURE of the RFC interface. Since no class-based exceptions can be specified in the interface of a remote-enabled function module, this only affects exceptions of the categories CX_NO_CHECK, especially CX_SY_NO_HANDLER.
  • The recommendation to handle all predefined exceptions is particularly important in avoiding incompatibilities with regard to the conversion to class-based exceptions in a future release.

More Information

For more information about exceptions during RFC calls, see the documentation RFC in SAP Help Portal.

Exception Handling in RFC






BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3297 Date: 20240419 Time: 005037     sap01-206 ( 51 ms )