CoChat

ERP implementation: lessons from a case study

Al‐Mashari, Majed, Al‐Mudimigh, Abdullah · 2003 · Information Technology & People

The DOI matches its Crossref record; 23 of the 24 references it cites were found in a registry or an index.

Abstract

Many organizations have moved from stand‐alone business information systems applications to integrated enterprise‐wide systems, enterprise resource planning (ERP). The implementation of ERP packages has created an opportunity to re‐engineer business processes within and beyond the organizational scope. Most notably, SAP R/3 has been widely implemented to create value‐oriented business processes that enable a high level of integration, improve communication within internal and external business networks, and enhance the decision‐making process. Though many organizations have reported dramatic improvements from SAP R/3 implementation, others have experienced difficulties in getting the R/3 modules aligned with other business components and systems. This paper describes a case study of a failed implementation of SAP R/3 to re‐engineer the business processes of a major manufacturer. Lessons in terms of factors that led to failure and their future implications are discussed in the light of the contrasting experiences of several best practice companies.

Overview

Integrity signals

Registry

Crossref · 10.1108/09593840310463005

Cites

23 of 23 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cites

Show all 23 references

Research works printed but not linked: 11

  1. Buck‐Emden, R. (2000), The SAP R/3 System: An Introduction to ERP and Business Software Technology, Addison‐Wesley, Reading, MA.
  2. Caldwell, B. (1998), “GTE goes solo on SAP R/3”, in, Information Week, No. 685, pp. 150–1.
  3. Elliott, H. (1997), “Don't be late for those important dates”, Electronic Business Today, Vol. 23 No. 7, pp. 34–6.
  4. Francesconi, T. (1998), “Transforming Lucent's CFO”, Management Accounting, Vol. 80 No. 1, pp. 22–30.
  5. Jesitus, J. (1997), “Change management: energy to the people”, Industry Week, Vol. 246 No. 16, pp. 37–41.
  6. Martin, M. (1998), “Enterprise resource planning”, Fortune, Vol. 137 No. 2, pp. 149–51.
  7. Rick, M. (1997), “IT integration programmed for global operation”, Chemical Week, Vol. 159 No. 6, pp. 21–7.
  8. Romei, L. (1996), “New technology strengthens new commitment”, Managing Office Technology, Vol. 41 No. 7, pp. 18–20.
  9. Stevens, T. (1997), “Kodak focuses on ERP”, Industry Week, Vol. 246 No. 15, pp. 130–5.
  10. Stevens, T. (1998), “Proof positive”, Industry Week, Vol. 247 No. 15, pp. 22–8.
  11. Braddely, P. (1999), “Managers look to supply chain to cut costs”, Logistics Management and Distribution Report, Vol. 38 No. 1, pp. 21–2.

Cited by

See all 254

Metadata

Authors
Al‐Mashari, M., & Al‐Mudimigh, A.
Affiliations
King Saud University (SA)
Venue
Information Technology & People
Publisher
Emerald
Published
2003-03-01
Volume
16
Issue
1
Pages
21-33
ISSN
0959-3845 (ISSN-L)
OpenAlex
W2104198702
Cited by
205
References
24
Citations by year
2026: 1 · 2025: 4 · 2024: 4 · 2023: 2 · 2022: 2 · 2021: 2 · 2020: 8 · 2019: 12 · 2018: 12 · 2017: 6 · 2016: 8 · 2015: 14 · 2014: 20 · 2013: 13 · 2012: 17
FWCI
15.64
Type
journal article
Language
en
Open access
closed
Licence
www.emerald.com/insight/site-policies (tdm)
Locations
Information Technology and People (publishedVersion)
Topics
  • Social Sciences › Business, Management and Accounting › Management Information Systems › ERP Systems Implementation and Impact
  • Social Sciences › Business, Management and Accounting › Strategy and Management › Corporate Governance and Management
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Business Process Modeling and Analysis
Keywords
enterprise resource planning, ERP implementation, SAP R/3, business process reengineering, implementation failure, manufacturing companies, information systems integration, decision-making

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: ERP implementation: lessons from a case study. https://app.cochat.ai/papers/10.1108/09593840310463005
The paper
Al‐Mashari, M., & Al‐Mudimigh, A. (2003). ERP implementation: lessons from a case study. Information Technology & People. https://doi.org/10.1108/09593840310463005

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.