An Exploratory Case Study of Enterprise Resource Planning Implementation

International Journal of Enterprise Information Systems (IJEIS)

Volumn 1, Issue 1, 2005, Pages 23-38

  Subramanian, Girish H ^a   Hoffer, Christopher S ^a  

^a PENNSYLVANIA STATE UNIVERSITY   (United States)

Author keywords

ERP implementation; SAP software; technology adoption

Indexed keywords

EID: 85001720326     PISSN: 15481115     EISSN: 15481123     Source Type: Journal    
DOI: 10.4018/jeis.2005010102     Document Type: Article

References (27)

1. Bailey, J. (1999, June 9). Trash haulers are taking fancy software to the dump. Wall Street Journal.
2. Bingi, P., Sharma, M., & Godla, J. (1999). Critical issues affecting ERP implementation. Information Systems Management, 16(3), 7.
3. Bowman, B. (2002). Building knowledge management systems. Information Systems Management, 19(3), 32–40.
4. Bradford, M., & Roberts, D. (2001, September). Does your ERP system measure up? Strategic Finance, 30–34.
5. Brynjolfsson, E., & Hilt, M. (1998, August). Beyond the productivity paradox - Computers are the catalyst for bigger changes. Communications of the ACM, 41(1), 49.
6. Cooke, D., & Peterson, W. (1998). SAP Implementation: Strategies and results. New York: The Conference Board.
7. Cooper, R., & Zmud, R. (1990). Information technology implementation research: A technological diffusion approach. Management Science, 36(2), 123.
8. Davenport, T. (1998, July/August). Putting the enterprise into the enterprise system. Harvard Business Review, 76(4), 121.
9. Edwards, J. (1999). Three tier client/server at work. New York: John Wiley & Sons.
10. Girard, K., & Farmer, M. (1999, November 3). Business software firms sued over implementation. CNET News.com.
11. Hayes, D.C., Hunton, J., & Reck, J. (2001). Market reaction to ERP implementation announcements. Journal of Information Systems, 15(1), 3–18.
12. Hiquet, B., & Kelly, A.F. (1998). SAP R/3 implementation guide: A manager's guide to understanding SAP. Indiana: Macmillan Technical.
13. Hughes, K. (2000). The value relevance of non-financial measures of air pollution in the electric utility industry. The Accounting Review, 75(2), 209–228.
14. Kumar, K., & Van Hillegersberg, J. (2000). ERP experiences and evolution. Communications of the ACM, 43(4), 22.
15. Kwon, T., & Zmud, R. (1987). Unifying the fragmented models of information systems implementation. Critical issues in information systems research. New York: John Wiley.
16. Lang, M., & Warfield, T. (1997). Response to the FASB invitation to comment: Recommendations of the AICPA Special Committee on Financial Reporting and the Association for Investment Management and Research. Accounting Horizons, 11(1), 139–156.
17. Legare, T. (2002). The role of organizational factors in realizing ERP benefits. Information Systems Management, 19(4), 21–41.
18. Levine, D.M., Berenson, M., & Stephan, D. (1999). Statistics for managers (2nd ed.). New Jersey: Prentice Hall.
19. Rajagopal, P., & Frank, T. (2000, November) A comparative case analysis of enterprise resource planning systems implementation and performance - SAP. Annual Conference of Decision Sciences Institute Meeting.
20. Rajagopal, P., & Frank, T. (2002). Oracle ERP and network computing architecture: Implementation and performance. Information Systems Management, 19(2), 53–68.
21. Scheer, A., & Habermann, F. (2000, April). Making ERP a success. Communications of the ACM, 57–61.
22. Slater, D. (1998, January). ERP projects cost more than their measurable payback. CIO Enterprise, 26–28.
23. Soh, C., & Tay-Yap, J. (2000, April). Cultural fits and misfits: Is ERP a universal solution? Communications of the ACM, 47–51.
24. Stedman, C. (1999). Survey: ERP costs more than measurable ROI. ComputerWorld, 33(14), 6.
25. Stevens, T. (1997, August). Kodak focuses on ERP. Industry Week, 246(15), 130.
26. Wah, L. (2000, March). Give ERP a chance. Management Review, 20–24.
27. Wright, S., & Wright, A. (2002). Information system assurance for enterprise resource planning systems: Unique risk considerations. Journal of Information Systems, 16(1), 99–113.