... [TABLES itab1 itab2 ...]
[USING a1 a2 ...]
[CHANGING a1 a2 ...].
1. ... TABLES itab1 itab2 ...
2. ... USING a1 a2 ...
3. ... CHANGING a1 a2 ...
These additions assign actual parameters to the formal parameters from the parameter interface for the subroutine subr. You can specify all data objects whose data type matches the
typing of the corresponding formal parameter (see
Check Typing) as actual parameters. Each formal parameter assumes all the properties of the actual parameter assigned to it when it is called.
... TABLES itab1 itab2 ...
If you specify the addition TABLES, each table parameter t1 t2 ... for the subroutine called that is defined with the addition TABLES to the FORM statement must be assigned an internal table itab as the actual parameter. The assignment of the actual parameters to the formal parameters takes place using their positions in the lists t1 t2 ... and itab1 itab2 ... .
You can only specify standard tables
for itab. Transfer takes place by means of a reference. If a specified table itab has a
header line, this is also transferred; otherwise, the header line in the corresponding table parameter t is blank when it is called.
Use of table parameters in the interface for subroutines is obsolete but a large number of subroutines
have not yet been converted to appropriately typed USING
or CHANGING parameters, so that they must still be supplied
with data by the TABLES addition to the PERFORM statement.
Static call of the internal subroutine select_sflight transferring a table parameter.
PARAMETERS: p_carr TYPE sflight-carrid,
p_conn TYPE sflight-connid.
DATA sflight_tab TYPE STANDARD TABLE OF sflight.
...
PERFORM select_sflight TABLES sflight_tab
USING p_carr p_conn.
...
FORM select_sflight TABLES flight_tab LIKE sflight_tab
USING f_carr TYPE sflight-carrid
f_conn TYPE sflight-connid.
SELECT *
FROM sflight
INTO TABLE flight_tab
WHERE carrid = f_carr AND
connid = f_conn.
ENDFORM.
... USING a1 a2 ...
... CHANGING a1 a2 ...
If you specify the additions USING and
CHANGING, an actual parameter a1 a2 ... of
the appropriate type must be assigned to each of the formal parameters u1
u2 ... and c1 c2 ... defined with the same
additions to the FORM statement.
The actual parameters specified after USING and
CHANGING form one shared list. They are assigned to the formal parameters after the position
in the shared list. The type of parameter transfer is defined with the additions
USING and CHANGING to the
FORM statement. The addition USING must be
before CHANGING. Otherwise, the assignment of the actual
parameters to the additions USING and
CHANGING is irrelevant to the PERFORM statement. It is also irrelevant whether only one or both of the additions is specified.
The following five PERFORM statements mean the same but only the fourth is recommended, since it is the only one that documents the interface of the subroutine called.
DATA: a1 TYPE string,
a2 TYPE string,
a3 TYPE string,
a4 TYPE string.
PERFORM test USING a1 a2 a3 a4.
PERFORM test CHANGING a1 a2 a3 a4.
PERFORM test USING a1 CHANGING a2 a3 a4.
PERFORM test USING a1 a2 CHANGING a3 a4.
PERFORM test USING a1 a2 a3 CHANGING a4.
...
FORM test USING p1 TYPE string
p2 TYPE string
CHANGING value(p3) TYPE string
value(p4) TYPE string.
...
ENDFORM.