Page 52 -

Chapter 2
Any large software implementation is challenging—and ERP systems are no
exception. There are countless examples of large implementations failing, and it is easy
32 to understand why. Many different departments are involved, as are the many users of the
system, programmers, systems analysts, and other personnel. Without top management
commitment, large projects are doomed to fail. More implementation issues are discussed
in Chapter 7.
After a company chooses its major modules, it must make an incredible number of
decisions on how to configure the system. These configuration options allow the company
to customize the modules it has chosen to fit its needs. For example, in the Financial
Accounting (FI) module, a business might need to define limits on the dollar value of
business transactions that certain employees can process. This is an important
consideration in minimizing the risk of fraud and abuse, and is just one example of the
many decisions facing a company at the start of a major ERP implementation.

ANOTHER LOOK

Tolerance Groups
In configuring the SAP system, a company can define tolerance groups, which are
specific ranges that define transaction limits. An example of a tolerance group is shown
in Figure 2-6. As part of the configuration process, a company can define any number
of tolerance groups with a range of limits, and can then assign employees to these
tolerance groups.

Source Line: SAP AG.
FIGURE 2-6 A customization example: tolerance groups to set transaction limits
(continued)

Copyright 2012 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part. Due to electronic rights, some third party content may be suppressed from the eBook and/or eChapter(s).
Editorial review has deemed that any suppressed content does not materially affect the overall learning experience. Cengage Learning reserves the right to remove additional content at any time if subsequent rights restrictions require it.