Recommendations for Modifying the SAP Standard

  • Include related repairs and corrections in a single request. Divide the changes you want to make in your SAP System into projects. Each project is represented by a local or transportable change request. The repairs and corrections belong to the request.
  • You should encapsulate your changes as much as possible in subroutines.

When you create subroutines, you must assign them to an include. You are advised to use one include in the customer namespace for each SAP program.

SAP has reserved namespaces for customer objects. For more information on valid conventions, see Customer Name Ranges.

Keep subroutines as clear as possible. If you are carrying out extensive modifications, create a new subroutine for each area (function) in your modification.

  • Avoid using statements in subroutines which could have unintended side-effects (for example, a COMMIT in the subroutine).
  • Avoid changing objects, such as function modules, tables, or messages, which occur in more than one place.
  • You should not change the length of domains! Otherwise, any dependent tables will have to be restructured in the database. Furthermore, any fields which have been lengthened could exceed area limits on screens.
  • You should ensure that modifications do not increase response times unreasonably. For further information, please refer to the section on Optimizing Performance.