ABAPTABLES_PARAMETERS_OBSOLETE - TABLES PARAMETERS OBSOLETE

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

FUNCTION, table_parameters

... TABLES p1  ${TYPE itab_type$} $| ${STRUCTURE struc$} $[OPTIONAL$]
           p2  ${TYPE itab_type$} $| ${ STRUCTURE struc$} $[OPTIONAL$]
           ...

Effect

Defines the table parameters t1 t2 ... in the function module interface display in the source code of function modules. Table parameters are obsolete CHANGING parameters that are typed as internal standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES.

For information about TYPE, STRUCTURE, and OPTIONAL, see Properties of the Interface Parameters. The following special rules apply to table parameters:

• Only pass by reference is allowed in TABLES parameters.

• Only the following types can be specified after TYPE:

• A table type itab_type from the ABAP Dictionary (including type pools) with the table category standard table with a flat line type. The table type can be complete or generic.

• The specified generic type STANDARD TABLE.

• If no type is specified explicitly, STANDARD TABLE is used implicitly.

• A type with TYPE REF TO is not allowed.

When TABLES parameters are accessed to which no type-friendly actual parameters are bound, a special exception situation can occur.

Notes

• The table key of a table parameter is either defined completely in the typing or it is taken from the actual parameter in the case of generic typing. This means that the table key of a table parameter is not necessarily the standard key.

• Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the statement DATA.

• Provided that basXML is not set as the RFC log, using TABLES parameters for remote-enabled function modules for RFC can be significantly faster than passing by means of the CHANGING parameter.

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4311 Date: 20230206 Time: 104954     sap01-206 ( 63 ms )