Enterprise Resource Planning (ERP) Implementation Approaches and the Performance of Procure-to-Pay Business Processes: (Field Study in Companies that Implement Oracle ERP in Jordan)

Enterprise Resource Planning (ERP) Implementation Approaches and the Performance of Procure-to-Pay Business Processes: (Field Study in Companies that Implement Oracle ERP in Jordan)

Ibrahim Kofahi, Haroun Alryalat
DOI: 10.4018/IJITPM.2017010104
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

In spite of the importance of implementing Enterprise Resource Planning (ERP) system in any organization, there are still many fears of not getting the return on investment from implementing it. In addition, there are many ERP systems implemented in different organizations that claim they did not get enough benefit from these systems. For this reason, this paper is intended to study the impact of ERP implementation approaches (Agile, Big Bang, and Hybrid) on the performance of Procure-to-Pay business processes. This paper adapts the quantitative research approach by using the survey strategy, which is conducted by a questionnaire collected from 91 respondents working in fifteen companies that implement Oracle ERP in Jordan. The researcher uses the SPSS as an analysis technique to test all hypotheses. The findings of the study show that the two ERP Implementation approaches (Big Bang and Hybrid) have a significant impact on the performance of Procure-to-Pay business processes. On the other hand, the study shows that Agile (ERP) implementation approach has no significant impact on the performance of Procure-to-Pay business processes.
Article Preview
Top

1. Introduction

The popular of international organizations, particularly technologist “fast or first movers” who invest in a new enterprise resource planning systems (ERP) project (Cua and Reames, 2013). From this point, ERP systems are modular information systems that automate companies’ business processes such as Accounts Payable, Accounts Receivable, Sales, Purchasing, and Inventory (Fetouh et al., 2011).

Also, ERP has two important characteristics. Firstly, it streams the transfer of visual model of business processes to a software implementation of these processes. Secondly, ERP guarantees a level of integration, security, and data integrity, which is difficult to achieve if there are multiple software platforms (Fetouh et al., 2011).

Additionally, ERP systems are considered as tools that support management processes standardization of multinational organizations. ERP systems have a lot of functionalities based on best practices. These functionalities are provided to clients within ERP systems. “ERP meet the requirements of universality: that everyone should work in his own language and understand each other” (Chtioui, 2009). This standardization grants ERP system a characteristic that meets the general needs for any organization. Based on this standardization, organizations should find the right fit between ERP system and its business processes to guarantee successful ERP implementation. Furthermore, Kholeif et al. (2007) noted that if misfit happens between ERP system and the organization’s existing practice, there will be two options the organization can select from; organizational adaptation or system customization.

Nowadays, ERP has a special distinguishing characteristic. It is developed by big companies like Oracle, SAP, Microsoft and others depending on the latest best practices implemented in huge big organizations like Airbus, Boeing, telecommunication companies and others. These ERP companies release different versions of the software as they implement new features or enhancements to it. They develop these softwares using latest programming languages like Java. Companies that use these systems get the latest technology and the latest best practices. Whereas, companies depending on their own developed programing, suc as those building their systems using Cobol, will always face issues in transferring to new technologies or new best practices.

Marnewick and Labuschagne (2005) stated that in order to implement ERP system effectively, it should not be considered as an IS but as an integrated business system that includes all business function. Besides, they define ERP as a software package that joins both business processes and IT features. If ERP implementation is to be considered successful, it should involve redesigning business processes from an inflexible mass-transaction orientation to an agile, lean, and knowledge-based process (Law & Ngai, 2007; Tsai et al., 2010). Also, Chung et al. (2007); Wier et al. (2007) mentioned that the outcome of appropriately implementing ERP is to enhance firm performance, which can be achieved mainly by redesigning business processes, integrated managerial functions, speeding reporting cycles, and expanding information capabilities. Typically, when implementing ERP system, the implementation should be linked to business process reengineering so as to focus on business process activities through the company (Subramoniam et al., 2009).

Several previous researches have studied the impact of ERP implementation on organizational performance (Nicolaou & Bhattacharya, 2006; Chtioui 2009; Wieder et al. 2006); HassabElnaby et al., 2011). This research highlights the absence of studies linking different ERP implementation approaches with different organizational performance aspects and the lack of researches investigating appropriateness of approach selection of ERP systems with regard to organizational diversity. To address this issue, the researcher investigated the impact of ERP implementation approaches on the Performance of Procure-to-Pay Business Processes since ERP implementation approaches is considered one of the main factors that influence the project success.

Complete Article List

Search this Journal:
Reset
Volume 15: 1 Issue (2024)
Volume 14: 1 Issue (2023)
Volume 13: 4 Issues (2022): 3 Released, 1 Forthcoming
Volume 12: 4 Issues (2021)
Volume 11: 4 Issues (2020)
Volume 10: 4 Issues (2019)
Volume 9: 4 Issues (2018)
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing