Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

Developing a cultural perspective on ERP

Developing a cultural perspective on ERP Purpose – To develop an analytical framework through which the organizational cultural dimension of enterprise resource planning (ERP) implementations can be analyzed. Design/methodology/approach – This paper is primarily based on a review of the literature. Findings – ERP is an enterprise system that offers, to a certain extent, standard business solutions. This standardization is reinforced by two processes: ERP systems are generally implemented by intermediary IT organizations, mediating between the development of ERP‐standard software packages and specific business domains of application; and ERP systems integrate complex networks of production divisions, suppliers and customers. Originality/value – In this paper, ERP itself is presented as problematic, laying heavy burdens on organizations – ERP is a demanding technology. While in some cases recognizing the mutual shaping of technology and organization, research into ERP mainly addresses the economic‐technological rationality of ERP (i.e. matters of effectiveness and efficiency). We want to supplement and complement this perspective with a cultural approach. How do individuals in organizations define and experience ERP‐standards? How and to what extent are management and working positions redefined in the process of developing and implementing ERP? In the paper, we highlight three perspectives from which ERP systems can be experienced, defined and analyzed. These perspectives are specified as the “constitution” of ERP, ERP as a “condition” of organizations, and the (unintended) “consequences” of ERP. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png Business Process Management Journal Emerald Publishing

Developing a cultural perspective on ERP

Business Process Management Journal , Volume 11 (2): 14 – Apr 1, 2005

Loading next page...
 
/lp/emerald-publishing/developing-a-cultural-perspective-on-erp-cmBuvLl0E5

References (64)

Publisher
Emerald Publishing
Copyright
Copyright © 2005 Emerald Group Publishing Limited. All rights reserved.
ISSN
1463-7154
DOI
10.1108/14637150510591138
Publisher site
See Article on Publisher Site

Abstract

Purpose – To develop an analytical framework through which the organizational cultural dimension of enterprise resource planning (ERP) implementations can be analyzed. Design/methodology/approach – This paper is primarily based on a review of the literature. Findings – ERP is an enterprise system that offers, to a certain extent, standard business solutions. This standardization is reinforced by two processes: ERP systems are generally implemented by intermediary IT organizations, mediating between the development of ERP‐standard software packages and specific business domains of application; and ERP systems integrate complex networks of production divisions, suppliers and customers. Originality/value – In this paper, ERP itself is presented as problematic, laying heavy burdens on organizations – ERP is a demanding technology. While in some cases recognizing the mutual shaping of technology and organization, research into ERP mainly addresses the economic‐technological rationality of ERP (i.e. matters of effectiveness and efficiency). We want to supplement and complement this perspective with a cultural approach. How do individuals in organizations define and experience ERP‐standards? How and to what extent are management and working positions redefined in the process of developing and implementing ERP? In the paper, we highlight three perspectives from which ERP systems can be experienced, defined and analyzed. These perspectives are specified as the “constitution” of ERP, ERP as a “condition” of organizations, and the (unintended) “consequences” of ERP.

Journal

Business Process Management JournalEmerald Publishing

Published: Apr 1, 2005

Keywords: Manufacturing resource planning; Organizational culture; Standardization; Social factors

There are no references for this article.