nestle erp
The Emerald Research Register for this journal is available at www.emeraldinsight.com/researchregister The current issue and full text archive of this journal is available at www.emeraldinsight.com/1463-7154.htm Success and failure factors of adopting SAP in ERP system implementation Vidyaranya B. Gargeya
Success and failure factors of adopting SAP
501
The University of North Carolina at Greensboro, Greensboro,
North Carolina, USA, and
Cydnee Brady
Volvo Trucks North America, Greensboro, North Carolina, USA
Abstract
Purpose – Enterprise resource planning (ERP) systems are software packages that allow companies to have more real time visibility and control over their operations. This paper aims to investigate and analyze common circumstances that occur within most ERP projects, and determines the areas that are key to success versus those that contribute to failure.
Design/methodology/approach – The study is based on a content analysis of published articles reporting SAP implementations in 44 companies.
Findings – Identifies six common factors that are indicative of successful or non-successful SAP implementations. It has been found that the lack of appropriate culture and organizational (internal) readiness as the most important factor contributing to failure of SAP implementations in 15 companies.
The presence of project management approaches and appropriate culture and organizational (internal) readiness are the most important factors contributing to the success of SAP implementations in
29 organizations.
Research limitations/implications – The data analyzed is from secondary sources published in the press. Secondary reporting could increase objectivity; however, the weakness is that not all the factors might have been reported.
Originality/value – Identifies factors critical to the success of SAP implementation
Keywords Manufacturing resource planning, Critical success factors
Paper type Research paper
Introduction
Success and failure factors of adopting SAP
501
The University of North Carolina at Greensboro, Greensboro,
North Carolina, USA, and
Cydnee Brady
Volvo Trucks North America, Greensboro, North Carolina, USA
Abstract
Purpose – Enterprise resource planning (ERP) systems are software packages that allow companies to have more real time visibility and control over their operations. This paper aims to investigate and analyze common circumstances that occur within most ERP projects, and determines the areas that are key to success versus those that contribute to failure.
Design/methodology/approach – The study is based on a content analysis of published articles reporting SAP implementations in 44 companies.
Findings – Identifies six common factors that are indicative of successful or non-successful SAP implementations. It has been found that the lack of appropriate culture and organizational (internal) readiness as the most important factor contributing to failure of SAP implementations in 15 companies.
The presence of project management approaches and appropriate culture and organizational (internal) readiness are the most important factors contributing to the success of SAP implementations in
29 organizations.
Research limitations/implications – The data analyzed is from secondary sources published in the press. Secondary reporting could increase objectivity; however, the weakness is that not all the factors might have been reported.
Originality/value – Identifies factors critical to the success of SAP implementation
Keywords Manufacturing resource planning, Critical success factors
Paper type Research paper
Introduction
References: Aladwani, A.M. (2001), “Change management strategies for successful ERP implementation”, Business Process Management Journal, Vol Atkinson, H. (1999), “ERP software requires good planning”, Journal of Commerce, 9 December, p Burns, M. (1999), “ERPs: a buyers’ market”, CAmagazine, Vol. 132 No. 7, pp. 37-45. Business Wire (2001), “Keebler sharpens demand planning processes with my SAP”, Supply Chain Management, 19 April. Caldwell, B. (1998), “GTE goes solo on SAP R/3”, Information Week, No. 685, p. 150. Campbell, S. (1999), “Merisel gets powered by SAP ERP”, Computer Reseller News, 19th April, p Koch, C. (1996), “Flipping the switch”, CIO, Vol. 9 No. 17. CIO (2000), “Does ERP build a better business?”, 15 February, pp. 114-24. Collett, S. (1999a), “Rayovac charges into SAP with a big bang”, ComputerWorld, 23 August, p Collett, S. (1999b), “SAP gets stuck in the spin cycle”, ComputerWorld, 8 November, p. 1. Davenport, T. (2000), Mission Critical – Realizing the Promise of Enterprise Systems, Harvard Business School Publishing, Boston, MA. Dong, L. (2001), “Modeling top management influence on ES implementation”, Business Process Management Journal, Vol Geishecker, L. (1999), “ERP vs best of breed”, Strategic Management, March, pp. 63-6. Gillooly, C. (1998), “Disillusionment”, Information Week, 16 February, pp. 46-56. Huang, Z. and Palvia, P. (2001), “ERP implementation issues in advanced and developing countries”, Business Process Management Journal, Vol Jesitus, J. (1997), “Change management – energy to the people”, Industry Week, Vol. 246 No. 16, p Krippendorf, K. (1980), Content Analysis – An Introduction to its Methodology, Sage, Newbury Park, CA. Levin, R. (1998), “Faster ERP rollouts”, Information Week, 13 July, p. 24. Mabert, V.A., Soni, A. and Venkataramanan, M.A. (2000), “Enterprise resource planning survey of US manufacturing firms”, Production and Inventory Management Journal, Second May, L. (1998), “Major causes of software project failure”, Crosstalk, July. Mearian, L. (2000), “CEO: SAP installation caused problems”, ComputerWorld, Vol. 34 No. 48, p Nah, F.F., Lau, J.L. and Kuang, J. (2001), “Critical factors for successful implementation of enterprise systems”, Business Process Management Journal, Vol Nash, K.S. (2000a), “A really bad bet for drug distributor”, ComputerWorld, 30 October, p. 36. Nash, K.S. (2000b), “Companies don’t learn from previous IT snafus”, ComputerWorld, 30 December, pp O’Brien, G. (1999), “Business West’s top 25 public companies”, Business West, Vol. 16 No. 6, p. 28. Osterland, A. (2000), “Blaming ERP”, CFO, January, pp. 89-93. PR Newswire (2001), 21 May. Ptak, C. (2000), ERP – Tools, Techniques and Applications for Integrating the Supply Chain, New York, NY, St Lucie Press. Sandoe, K., Corbitt, G. and Boykin, R. (2001), Enterprise Integration, Wiley, New York, NY. Shaw, M. (2000), “All systems go”, Pulp & Paper, Vol. 74 No. 9. Stedman, C. (1999), “ERP flops point to user’s plans”, ComputerWorld, 15 November, p. 1. Stein, T. (1998), “SAP installation scuttled”, Information Week, 26 January p. 34. Themistocleous, M., Irani, Z. and O’Keefe, R.M. (2001), “ERP and application integration”, Business Process Management Journal, Vol Umble, E.J. and Umble, M. (2001), “Enterprise resource planning systems: a review of implementation issues and critical success factors”, Proceedings of the 32nd Annual Meeting of the Decision Sciences Institute, pp. 1109-11. Vaughan, J. (1996), “Enterprise applications”, Software Magazine, Vol. 16 No. 5, pp. 67-72. Wheatley, M. (2000), “ERP disasters – bet the company and lose”, Financial Director, 1 March, p Wilder, C. (1998), “False starts, strong finishes”, Information Week, 30 November, p. 41. Zerega, B. (1997), “Management support a must for big bang”, InfoWorld, 8 September, p. 100.