Ansicht
Dokumentation
ABAPRECEIVE_PARA - RECEIVE PARA
BAL_S_LOG - Application Log: Log header data ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
RECEIVE, parameter_list
... $[IMPORTING p1 = a1 p2 = a2 ...$]
$[TABLES t1 = itab1 t2 = itab2 ...$]
$[CHANGING p1 = a1 p2 = a2 ...$]
$[EXCEPTIONS $[exc1 = n1 exc2 = n2 ...$]
$[system_failure = ns $[MESSAGE smess$]$]
$[communication_failure = nc $[MESSAGE cmess$]$]
$[OTHERS = n_others$]$].
Effect
These additions are used to pass the specified formal parameters of the function module func specified after RECEIVE to the actual parameter of the callback routine in the calling program. The meaning of the additions is the same as for synchronous RFC. However, values are only applied by actual parameters specified using CHANGING or TABLES and are not passed.
EXCEPTIONS is used to perform non-class-based exception handling. Return codes are assigned to the non-class-based exceptions. The same exceptions can be raised as in synchronous RFC, that is, exceptions that are defined in the interface of the function module and the predefined exceptions of the RFC interface. If no exceptions are raised, RECEIVE sets the content of sy-subrc to 0.
Note
CALL FUNCTION and RECEIVE are currently decoupled with regard to the addition EXCEPTIONS. This changes when class-based exceptions are introduced. For this reason, it is advisable to use the addition EXCEPTIONS in the same way for CALL FUNCTION and RECEIVE.
Fill RESBD Structure from EBP Component Structure ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 2805 Date: 20240419 Time: 073751 sap01-206 ( 28 ms )
