SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Release-Specific Changes → Changes in Release 3.0 →
Assigning Formal Parameters in Release 3.0
Note: The following function can no longer be used with Release 4.6A.
If you are in the ABAP Editor and you choose Utilities → Type assignment,
you call a conversion program which assigns types to the formal parameters of all
FORM routines of an ABAP program and its includes.
Conversion is
possible if all the actual parameters corresponding to a particular formal parameter agree in type and
length, i.e. they are technically similar or all actual parameters have the same type (e.g. C).
If there are several framework
programs for an include, this is displayed at the end of the list. However, the conversion proposals
made refer only to the current framework program. The names of the FORM routines defined in this include appear in the list of conversion proposals underlined in red.
If there are external calls for a FORM routine, no conversion proposal is made. The names of any such routines are displayed at the end of the list.
If conversion is not possible, the reason is given at the end of the line. Possible reasons are:
It is possible to specify that you want to see the subroutines in the source code. If you want to convert the FORM routine, you must select the checkbox and use the pushbutton "Convert Coding". After the conversion has been carried out, the checkbox for the converted FORM routine is no longer ready for input. The program contains the old FORM routine as a comment. The newly converted FORM routine is inserted before it.