ABAP_to_the_Future

Introduction
The first part of refactoring can be a static code check. SAP has come up with the
ABAP Test Cockpit, which is in some se nses an extension of the Extended Program
Check and the Code Inspector, with ex tra bits on top. It can also help you
prepare your programs for migration to an SAP HANA database.
Chapter 5: Debugger Scripting
After dealing with static checks of code at design time, you move on to debugging
the code at runtime. The debugger in AB AP has always been one of its strongest
features, and in this chapter you’ll look at a relatively new enhancement: the ability
to write programs within the debu gger to automate common or labor-intensive
tasks.
Debugging is also available from ABAP in Eclipse and can in fact do one amazing
thing that debugging in the SAP GUI cannot. Curious? Read Chapter 5!
Chapter 6: The Enhancement Framework and New BAdIs
I couldn’t leave the area of development tools without taking a quick look at the
enhancement framework. This is usually viewed solely as a means to stick user
exits all over the place, but it also has a role to play in your own custom developments.
Part II: Business Logic Layer
Chapter 7: Exception Classes and Design by Contract
As you start to write your business logic, you’ve already got a bunch of unit tests
and have performed static code checks and debugged running code. However, you
know that unexpected situations are bo und to occur and have to decide how to
handle this in your applications. The technical way to deal with such problems is to
make use of the exception classes that SAP introduced to replace traditional error
handling by means of return codes. I’ll also talk about one philosophical way to
look at this problem: the design by contract pattern invented by Bertrand Meyer.
Chapter 8: Business Object Processing Framework (BOPF)
Over the years, SAP has come up with many ways to model real-world objects
inside the ABAP system. The latest is the Business Object Processing Framework
28