Skip to main content Accessibility help
×
Hostname: page-component-cd9895bd7-gxg78 Total loading time: 0 Render date: 2024-12-27T19:24:11.878Z Has data issue: false hasContentIssue false

16 - An Exploratory Analysis of the Sources and Nature of Misfits in ERP Implementations

from Part IV - Cultural Aspects of Enterprise Systems

Published online by Cambridge University Press:  05 February 2012

Sia Siew Kien
Affiliation:
Associate Director of Information Management Research Centre, Nanyang Business School, NTU
Christina Soh
Affiliation:
Director of the Information Management Research Centre, Nanyang Business School, NTU
Graeme Shanks
Affiliation:
University of Melbourne
Peter B. Seddon
Affiliation:
University of Melbourne
Leslie P. Willcocks
Affiliation:
University of Warwick
Get access

Summary

Introduction

ERPs – software packages that manage and integrate business processes across organizational functions and locations – cost millions to buy, several times as much to implement, and necessitate disruptive organizational change. While some companies have enjoyed significant gains, others have had to scale back their projects and accept minimal benefits, or even abandon implementation (Marcus and Tanis, 2000).

Historically, a common problem when adopting package software has been the issue of ‘misfits’, that is, the gaps between the functionality offered by the package and that required by the adopting organization (Davis, 1988; Lucas, Walton, and Ginzberg, 1988). As a result, organizations have had to choose among adapting to the new functionality, living with the shortfall, instituting workarounds, or customizing the package. ERPs, as a class of package software, also present this problematic choice to organizations.

Even though there are many built-in switches that one can manipulate to customize the software, smooth alignment of the software functionality to business requirements is still far from ideal as many of these issues have to be dealt with at the application architecture level. AeroGroup, for example, has dropped the Apparel Footwear Solution of SAP/R3 because of its inability to model the uniqueness and complexities of the footwear business. Similarly, the failure of Fox Meyer could also be partially attributed to the adoption of an ERP system that was designed more for manufacturers rather than wholesale distributors.

Type
Chapter
Information
Second-Wave Enterprise Resource Planning Systems
Implementing for Effectiveness
, pp. 373 - 387
Publisher: Cambridge University Press
Print publication year: 2003

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

Davis, G. B. (1988) Commentary on Information Systems: To Buy, Build, or Customize? Accounting Horizons, March, 101–103
Hippel, E. V. (1994) Sticky Information and the Locus of Problem Solving: Implications for Innovation. Management Science, 40(4), 429–439CrossRefGoogle Scholar
Lucas, H. C. Jr., Walton, E. J., and Ginzberg, M. J. (1988) Implementing Packaged Software. MIS Quarterly 12, 537–549CrossRefGoogle Scholar
Markus, M. L. and Tanis, C. (2000) The Enterprise Systems Experience: From Adoption to Success. In Framing the Domains of IT Research: Glimpsing the Future Through the Past, Zmud, R. W. (ed.), Cincinnati, OH: Pinnaflex Educational Resources
Soh, C., Sia, S. K., Boh, W. F., and Tang, M. (2001) Misalignments in ERP Implementations: A Dialectic Perspective. Journal of Human-Computer Interaction, forthcoming
Soh, C., Sia, S. K., and Tay-Yap, J. (2000) Cultural Fits and Misfits: Is ERP a Universal Solution?Communications of the ACM, 43(4), 47–51CrossRefGoogle Scholar
Volkoff, O. (1999) Enterprise System Implementation: A Process of Individual Metamorphosis. In Proceedings of the Academy of Management '99 Conference, August, Chicago

Save book to Kindle

To save this book to your Kindle, first ensure no-reply@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×