Datasheet

SummAry 27
many more. One of the existing ISs may work for your business. If not, work with
SAP regarding your business needs; SAP may make—or allow you to make—SAP-
supported modications to your system.
SAP also provides what are called user exits in some standard programs. User exits
allow developers to create their own code that is called by a standard SAP program.
Once the custom code has nished, control returns to the standard SAP program
for further processing. Contrary to programming modications, home-brewed user
exits are a good idea. SAP is providing increasing numbers of user exits in upgrades
and new releases. To see if a program already has a user exit, while displaying the
program source code, search for the string customer exit. If this string is found,
the program already has a user exit. e transaction code CMOD also contains the
customization projects for activating all user exits. You can search through these
projects to see if the functionality you need is included.
Summary
In this chapter, you were introduced to the basic concepts you’ll need to understand
to get the most out of the rest of this book. You reviewed the basic conguration of
a three-tiered database and learned about a table-driven approach to designing your
own system. You also learned about transports and who has control over the vari-
ous aspects of preparing and implementing a transport. We walked you through the
IMG screens and a few tables that will be useful in conguration and customization.
And youre now more familiar with the sorts of changes that you shouldn’t make and
how to nd out about problems and solutions using the Service Market Place.
In the next chapter, we’ll cover the Organizational Structure of the FI Enterprise
system and begin to congure the system for our project company, Extreme Sports.
23288c01.indd 27 2/19/09 10:55:36 PM