Improving the Quality of ABAP Code

Paul Hardy joined Heidelberg Cement in the UK in 1990. For the first seven years, he worked as an accountant. In 1997, a global SAP rollout came along and he jumped on board and has never looked back. He has worked on country-specific SAP implementations in the United Kingdom, Germany, Israel, and Australia. After starting off as a business analyst configuring the good old IMG, Paul swiftly moved on to the wonderful world of ABAP programming. After the initial run of data conversion programs, ALV reports, interactive Dynpro screens, and SAPscript forms, he yearned for something more and since then has been eagerly investigating each new technology as it comes out, which culminated in him writing the book, ABAP to the Future. Paul became an SAP Mentor in March 2017 and can regularly be found blogging on the SAP Community site and presenting at SAP conferences in Australia (Mastering SAP Technology and the SAP Australian User Group annual conference)and at SAP TECHED Las Vegas. If you happen to be at one of these conferences, Paul invites you to come and have a drink with him at the networking event in the evening and to ask him the most difficult questions you can think of, preferably about SAP.

Chapter 1: Why Object-Oriented Programming Is a Must for Code Quality.- Chapter 2: Why Test-Driven Development Is a Must for Code Quality.- Chapter 3: Clarity—The First Pillar of Code Quality.- Chapter 4: Stability—The Second Pillar of Code Quality.- Chapter 5: Performance—The Third Pillar of Code Quality.- Chapter 6: User Friendliness—Ensuring UI Quality.- Chapter 7: User Exits—Defusing a Potential Time Bomb.- Chapter 8: Ensuring Code Runs in S/4HANA.- Chapter 9: Ensuring Code Runs in ABAP in the Cloud.- Chapter 10: Creating Your Own Custom ATC Checks.