A while ago, the German SAP User Group (DSAG) released a best practices guideline for ABAP development*. It provides valuable technical content mixed with practical recommendations how to set up and maintain a process for “ABAP quality”. This new guideline for the first time delivered a holistic view on ABAP development.
The DSAG guideline points out common security risks**, describes how to establish general ABAP quality standards in a company and how a QA process should be set up. All in all a great 360° overview of ABAP code quality and security best practices, that enable quality-minded companies and organizations to build ABAP development strategies that are (and stay) state-of-the-art.
DSAG received very good feedback on the quality of the content.
Finally (and thanks to an initiative started by co-author Juergen Wachter) DSAG decided to translate the guideline. Several of the original authors helped in translating the content, with the great support of native speakers and other helping hands/eyes.
The English version of the guideline is in sync with the German version, in order to avoid content mismatches.
It is available at http://www.dsag.de/Go/E-Development-Engl