Assigning Types to Formal Parameters 
You can use the Types function to avoid unnecessary type conversions in your ABAP programs. This function evaluates the parameters in the PERFORM statements. PERFORM statements are subroutine calls. Where possible, the Type assignment function proposes types for the corresponding formal parameters in the FORM statements. The systems then allows you to convert your code according to these proposals.
To use the type assignment function:
The system displays a selection screen.
The system looks for formal parameters that are technically similar, that is, that have the same type and length. When it locates a match, the system proposes a type for that formal parameter. The proposed type is usually an ABAP Dictionary field but it can also be a global variable type.

The Type assignment function can result in a violation of encapsulation rules.
If conversion is not possible for a formal parameter, the system displays a reason. Possible reasons for inability to convert are as follows:
Reason |
Explanation |
Leng |
The actual parameters have different lengths |
Type |
The actual parameters have different types |
Loca |
The actual parameter(s) is (are) locally defined variables |
+(.) |
Offset and/or length specification in actual parameter |
<..> |
The actual parameter is a field symbol |
Parm |
The actual parameter is a non-convertible formal parameter of another FORM routine. |
Recu |
Recursive call of the FORM routine |
Expe |
The actual parameter is the formal parameter of a FORM routine that is only called externally (or in other programs of the same include). |
If you want to display the program code of a FORM routine, either double-click the routine or select the appropriate checkbox and choose Choose.
To convert FORM routines as proposed, select the appropriate check box(es) and choose Convert code. For each FORM routine you select, the system inserts the converted code and retains the old FORM routine specification as a comment underneath.