What does it do? These additions assign actual parameters to the formal parameters of the parameter interface of the subroutine subr>. All data objects whose data type matches the typing> of the corresponding formal parameter can be specified (see Check Typing>) as actual parameters. Each formal parameter assumes all the properties of the actual parameter assigned to it when it is called. The order of the additions is fixed.
Latest notes: NON_V5_HINTS A system field> should never be used an actual parameter >. ABAP_HINT_END
ABAP Addition
What does it do? The addition TABLES> must be used to assign an internal table itab> as an actual parameter to each table parameter t1 t2 ... > defined for the called subroutine using the addition TABLES > of the statement FORM>>. The assignment of the actual parameters to the formal parameters takes place using their positions in the lists t1 t2 ...> and itab1 itab2 ...> Only standard tables> can be specified for itab>. The data is passed by reference. If a specified table itab> has a header line>, this is also passed. Otherwise, the header line in the corresponding table parameter t> is initial when it is called.
Latest notes: The use of table parameters in the interface of subroutines is obsolete, but a large number of subroutines have not yet been switched to appropriately typed USING> parameters or CHANGING> parameters and must still be filled by the addition TABLES> of the statement PERFORM>. NON_V5_HINTS ABAP_HINT_END
Example ABAP Coding
Static call of the internal subroutine select_sflight> while passing a table parameter. ABEXA 00495 ABAP_EXAMPLE_END
ABAP Addition
ABAP Addition
What does it do? If the additions USING> and CHANGING> are specified, a type-specific actual parameter a1 a2 ...> must be assigned to each of the formal parameters u1 u2 ...> and c1 c2 ...> defined for the called subroutine using the identically named additions of the statement FORM>>. The actual parameters specified after USING> and CHANGING> form one single shared list. They are assigned to the formal parameters in accordance with the position in the shared list. The type of parameter passing is defined by the additions USING> and CHANGING> in the statement FORM >. The addition USING> must be in front of CHANGING>. Otherwise, the assignment of the actual parameters to the additions USING> and CHANGING> is ignored by the statement PERFORM >. It is also irrelevant whether only one or both of the additions are specified.
Latest notes:
For program documentation purposes, it is best to specify the additions USING> and CHANGING> in the statement FORM> in accordance with the definition of the parameter interface.
No substring access> is possible to an actual parameter of type string> or xstring> specified after USING> or CHANGING>.
Upcasts> are not possible when passing an actual parameter to a USING> parameter typed as a reference variable.
A USING> parameter declared for pass by reference> behaves in the same way as a CHANGING> parameter, which means that the content of the actual parameter could be changed in a forbidden way. NON_V5_HINTS ABAP_HINT_END
Example ABAP Coding
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 called subroutine. ABEXA 00496 ABAP_EXAMPLE_END