FORM Routines: Legacy but Still Important

Explanation

FORM routines are classical procedural modularization units created using FORM and called using PERFORM. They are common in legacy reports, SAP standard exits and old custom programs. FORM routines are easy to create and useful for small local logic, but they are weaker than methods for modern design. They often depend on global variables, are harder to unit test and do not provide strong object-oriented structure. Still, ABAP developers must understand FORM routines because many production systems contain thousands of legacy reports and exits using them.

Code example

FORM validate_sales_org.  IF p_vkorg IS INITIAL.    MESSAGE 'Sales organization is required' TYPE 'E'.  ENDIF.ENDFORM. START-OF-SELECTION.  PERFORM validate_sales_org.

Real project scenario

A delivery user exit in MV50AFZ1 may contain multiple FORM routines for validation, batch check and delivery block logic. While maintaining such exits, the developer must understand PERFORM flow and global data usage.

Common mistakes

- Creating very large FORM routines. - Using FORM routines as dumping ground for unrelated logic. - Relying too much on global variables. - Not passing parameters clearly.

Best practices

- Keep FORM routines small. - Use parameters instead of hidden global dependencies. - Use FORM mainly for local procedural logic. - Prefer methods for new reusable logic.

Interview angle

Interviewers may ask whether FORM routines are obsolete. A balanced answer is: they exist heavily in legacy systems, but new reusable logic should prefer methods/classes.