... [EXPORTING p1 = a1 p2 = a2 ...]
[IMPORTING p1 = a1 p2 = a2 ...]
[CHANGING p1 = a1 p2 = a2 ...]
[TABLES t1 = itab1 t2 = itab2 ...]
[EXCEPTIONS [exc1 = n1 exc2 = n2 ...]
[system_failure = ns [MESSAGE smess]]
[communication_failure = nc [MESSAGE cmess]]
[OTHERS = n_others]].
These additions are used to assign actual parameters to the formal parameters of the function module and return values to exceptions that are not class-based. The additions have the same meaning as in the general function module call with the exceptions that only tables with flat row types can be passed and that a header, if existing, cannot be passed when using the addition TABLES. As of release 4.6c, the additions EXPORTING, IMPORTING, and CHANGING enable you to pass tables with deep row types, deep structures, and strings. In addition, you can add an optional addition MESSAGE after EXCEPTIONS for the specific exceptions SYSTEM_FAILURE or COMMUNICATION_FAILURE. If one of these exceptions are raised, the first row of the corresponding short dump is displayed in the field smess or cmess, which must be flat and character-type.
In contrast to the general function module call, an exception is not raised during RFC in Unicode programs if an incorrect formal parameter is specified during static specification of the function.