ERP II Readiness in Jordanian Industrial Companies

Similar documents
Toward a Unified View of Customer Relationship Management

Oracle Business Intelligence Applications Overview. An Oracle White Paper March 2007

ACS-1803 Introduction to Information Systems. Enterprise Information Systems. Lecture Outline 6

26/10/2015. Enterprise Information Systems. Learning Objectives. System Category Enterprise Systems. ACS-1803 Introduction to Information Systems

ENTERPRISE APPLICATIONS

Supply Chain Technology Foundations

Performance Management Applications. Gain Insight Throughout the Enterprise

ENTERPRISE ASSET MANAGEMENT (EAM) The Devil is in the Details CASE STUDY

4 Key Tools for Managing Shortened Customer Lead Times & Demand Volatility

AC : ENTERPRISE RESOURCE PLANNING: A STUDY OF USER SATISFACTION WITH REFERENCE TO THE CONSTRUCTION INDUSTRY

Business Intelligence Meets Business Process Management. Powerful technologies can work in tandem to drive successful operations

Customer Relationship Management. EC-Council

Building Relationships by Leveraging your Supply Chain. An Oracle White Paper December 2001

Make the right decisions with Distribution Intelligence

White Paper February IBM Cognos Supply Chain Analytics

SAP ERP OPERATIONS SOLUTION OVERVIEW

The Real ROI from SAP

E-Business: How Businesses Use Information Systems

Four distribution strategies for extending ERP to boost business performance

ORACLE PROCUREMENT AND SPEND ANALYTICS

Supplier Relationship Management Analysis PURCHASING FINANCIAL SUPPLIER BUYER PERFORMANCE ANALYSIS PERFORMANCE PERFORMANCE

Is it Time to Purchase a Fashion Enterprise Solution?

Software Industry KPIs that Matter

Oracle Business Intelligence Applications: Complete Solutions for Rapid BI Success

Relationship management is dead! Long live relationship management!

Demand Chain Management: The Other Side of Supply Chain Management. Abstract

Enterprise Resource Planning Analysis of Business Intelligence & Emergence of Mining Objects

Effect of E-Commerce on Accounting Information System, Computerization Process and Cost Productivity

ORACLE FINANCIAL ANALYTICS

KEYWORDS: Value chain, Accounting, Information, System, Decision Making

An Integrated Model for Knowledge Management and Electronic Customer Relationship Management. Wael Hadi 1, *, Jaber Al-Widian 2

Chapter 9. Video Cases. 6.1 Copyright 2014 Pearson Education, Inc. publishing as Prentice Hall

Oracle istore. Deliver Intelligent, Personalized Customer Experiences

Business Intelligence and Analytics: Leveraging Information for Value Creation and Competitive Advantage

CSCMP Level One : Cornerstones of Supply Chain Management. Learning Blocks

ENTERPRISE MANAGEMENT AND SUPPORT IN THE TELECOMMUNICATIONS INDUSTRY

BUSINESS INTELLIGENCE. Keywords: business intelligence, architecture, concepts, dashboards, ETL, data mining

Management Information Systems Role in Decision-Making During Crises: Case Study

Management Update: The Cornerstones of Business Intelligence Excellence

Endeavour Dynamics Offering

SAP's MDM Shows Potential, but Is Rated 'Caution'

A Grid Architecture for Manufacturing Database System

US ONSHORING OFFERS SUPERIOR EFFECTIVENESS OVER OFFSHORE FOR CRM IMPLEMENTATIONS

A Comparative Analysis of User Satisfaction with Enterprise Resource Planning

Corporate Performance Management Framework

SAP PRACTICE AT INFOSYS

ORACLE PROJECT ANALYTICS

An Enterprise Resource Planning Solution (ERP) for Mining Companies Driving Operational Excellence and Sustainable Growth

THE IMPACT OF USING ACCOUNTING INFORMATION SYSTEMS ON THE QUALITY OF FINANCIAL STATEMENTS SUBMITTED TO THE INCOME AND SALES TAX DEPARTMENT IN JORDAN

White Paper March Government performance management Set goals, drive accountability and improve outcomes

Aligning Quality Management Processes to Compliance Goals

Business Intelligence: Effective Decision Making

Business Intelligence

P&SM: eprocurement. CIPS Position on Practice

COLLABORATIVE DEMAND FORECASTING: A TOOL FOR SURVIVAL. One-number forecasting, coupled with performance measurement, reduces costly surprises

An Analytical Study of CRM Practices in Public and Private Sector Banks in the State of Uttar Pradesh

Redefining Partner Relationship Management Inform Transact Serve

Akamai for SAP Acceleration:

Spanning the Oracle EBS

Case No COMP/M SAP / BUSINESS OBJECTS. REGULATION (EC) No 139/2004 MERGER PROCEDURE. Article 6(1)(b) NON-OPPOSITION Date: 27/11/2007

Supply Chain Management and Value Creation

Oracle Fusion CRM Fixed Scope Cloud Implementation Offering

Best Practices in the Procure-to-Pay Cycle: Perspectives from Suppliers and Industry Experts

Targeting. 5 Tenets. of Modern Marketing

n For next time q Read Cisco Case n Hwk 2 due by start of class Tuesday n On ecommons q Database Assignment 1 posted

Cognos e-applications Fast Time to Success. Immediate Business Results.

Executive Master's in Business Administration Program

Community Development and Training Centre Semester IT 245 Management Information Systems

TIM 50 - Business Information Systems

The Impact of Information Technology on Knowledge Management Practices

Curriculum for the Bachelor Degree in Business Administration

Introduction to Supply Chain Management Technologies

Name of the system: Accura Supply Chain Name of the company offering it: Accura Software Link to website:

ORACLE BUSINESS INTELLIGENCE APPLICATIONS FOR JD EDWARDS ENTERPRISEONE

Application Extent of the Enterprise Resource Planning Systems (ERP) Main Components in the Jordanian Industrial Public Firms

8/25/2008. Chapter Objectives PART 3. Concepts in Enterprise Resource Planning 2 nd Edition

Management Accountants and IT Professionals providing Better Information = BI = Business Intelligence. Peter Simons peter.simons@cimaglobal.

Supply Chain Management Build Connections

Master Data Management (MDM) in the Sales & Marketing Office

Improve the Agility of Demand-Driven Supply Networks

How To Save Money On Production

Implementing Oracle BI Applications during an ERP Upgrade

Management Information Systems

PROCUREMENT: A Strategic Lever for Bottom Line Improvement

Infor Healthcare Overview

Pondicherry University India- Abstract

What to Look for When Selecting a Master Data Management Solution

Government Business Intelligence (BI): Solving Your Top 5 Reporting Challenges

RealTests.M questions

Integrating CRM with ERP

CONCEPTUALIZING BUSINESS INTELLIGENCE ARCHITECTURE MOHAMMAD SHARIAT, Florida A&M University ROSCOE HIGHTOWER, JR., Florida A&M University

How To Improve Your Business

The role of business intelligence in knowledge sharing: a Case Study at Al-Hikma Pharmaceutical Manufacturing Company

Transcription:

ERP II Readiness in Jordanian Industrial Companies Joseph O. Chan Roosevelt University, USA jchan@roosevelt.edu Husam Abu-Khadra Roosevelt University, USA habukhadra@roosevelt.edu Nidal Alramahi Zarka Private University, Jordan ramahinedal@zpu.edu.jo ABSTRACT Enterprise systems have evolved in the last three decades from MRP (material requirements planning), MRP II and ERP (enterprise resource planning) to ERP II in the turn of the century. ERP II integrates the core ERP system with specialized solutions in SCM (supply chain management), SRM (supplier relationship management), CRM (customer relationship management), PRM (partner relationship management) and KM (knowledge management), enabled by e-business technologies. This research investigates the readiness of Jordanian industrial companies for ERP II implementation via an empirical study using a self-administered questionnaire. The study results revealed that the Jordanian industrial companies have all of the ERP II components with the exception of CRM and PRM, while suffering from significant integration deficiency, and lacking KM and BI (business intelligence) support. The findings of this study shall encourage the Jordanian industrial companies to review their ERP II integration strategies to maximize the IT investment return. INTRODUCTION The Y2K problem has prompted the proliferation of ERP (enterprise resource planning) systems in the 1990s where companies rushed to replace outdated operational systems to comply with the requirements for the 4-digit year code. The implementation of ERP has helped companies to integrate disparate intra-enterprise functions, increase operational efficiency and effectiveness (Beatty & Williams, 2006; Kang, Park, & Yang, 2008). Business strategies have evolved at the turn of the century from the focus of internal operations to the external focus of managing relationships with customers, suppliers and channel partners. ERP II brings the promise of enabling the business strategy of extending a firm s value chain to the value network in the extended enterprise. From the systems perspective, ERP II succeeds a number of enterprise systems: MRP (material requirements planning), MRP II and ERP. ERP II emerged in the early 2000s as the next generation of ERP. The Gartner Group described ERP II as a business strategy and a set of Communications of the IIMA 2011 51 2011 Volume 11 Issue 2

industry-domain-specific applications that build customer and shareholder value by enabling and optimizing enterprise and inter-enterprise, collaborative, operational and financial processes (Gartner Group, 2000). ERP II can be characterized as a competitive strategy that integrates the core ERP system with specialized solutions such as supply chain management system and knowledge management system (Mohamed, 2002). It provides the integrated platform for business transactions and collaboration of the entire value network. In the new economy fueled by the Internet and globalization, companies no longer have to make or distribute the products that they sell, and can leverage a virtual network of companies in support of their operations (Turner & Chung, 2005). Relationship management and knowledge management are two critical ingredients for competitive business strategies in the new economy, where the business performance measures exceed the traditional metrics of product excellence and operational efficiency (Folorunso, Adewale, Ogunde, & Okesola, 2011). Galbreath (2002) described enterprise relationship management as a business strategy for value creation based on the leveraging of the network-enabled processes and activities to transform the relationships between the organization and all its internal and external constituencies in order to maximize current and future opportunities. The integration of enterprise relationships is at the core of the ERP II platform, in which the ERP system is integrated with systems in supply chain management (SCM), supplier relationship management (SRM), customer relationship management (CRM) and partner relationship management (PRM). Knowledge management (KM), which focuses on innovation and the management of enterprise knowledge assets of a firm, is the other side of the coin in value creation in the new economy. Knowledge management consists of processes in the discovery, capture, sharing and application of knowledge (Becerra- Fernandez, Gonzales, & Sabherwal, 2004). Mohamed and Fadlalla (2005) described that incorporating KM capabilities into ERP systems is a major driver behind ERP II. As companies collect huge amount of business information using digital technologies, transforming them into business intelligence (BI) to enhance business strategies and operations provides the necessary advantage to succeed in a competitive market. Operations of companies in the new economy can be characterized as virtual and real-time. Companies may leverage multiple business entities around the globe connected by computer networks to perform business operations around the clock, transcending business operations beyond the time and space confined by geographical and national boundaries. Porter (2001) described the latest stage in the evolution of technologies in business as the real-time optimization of the entire value chain. Real-time operations across the extended enterprise enabled by e-business technologies are at the core of ERP II as described in Chan (2010). Chan described a conceptual model for ERP II enabled by e-business technologies that integrates a firm s value chain to the value chains of its suppliers, customers and channel partners. The model provides an integrated e-business enabled platform for ERP, SCM, SRM, CRM, KM and BI as illustrated in Figure 1. With the emergence of ERP II in the early 2000s, are companies implementing and reaping the benefits of ERP II? The purpose of this research is to investigate the readiness of Jordanian Industrial companies for ERP II implementation. This research tests ERP II readiness in Jordanian industrial companies through an empirical study. Specifically, five areas that include existence, e-enablement, integration, KM support and BI support are studied through the testing of five hypotheses as described in section 2.2. Communications of the IIMA 2011 52 2011 Volume 11 Issue 2

Hypothesis 1.1 addresses ERP II readiness from the standpoint of whether ERP II components as described in Chan (2010) exist in these companies. Hypothesis 1.2 addresses ERP II readiness from the standpoint of real-time operations across the extended enterprise through the enablement by e-business technologies. Knowledge is a critical ingredient of value creation in the new economy and is considered as a key driver of ERP II. Hypothesis 1.4 addresses the ERP II readiness from the standpoint of knowledge enablement. Enterprise systems implementation has previously suffered high failure rates, 70 percent for ERP (Lewis 2001), and 55 to 75 percent for CRM according to the Meta Group (Johnson, 2004). Key factors contributing to the failure include the lack of enterprise-wide integration and analytics (Bannan, 2004; McKenzie, 2001). In practice, the multi-component ERP solution often does not meet critical requirements and costs more in terms of resources than originally planned (Daneva & Wieringa, 2008). Hypotheses 1.3 and 1.5 address ERP II readiness from the viewpoints of enterprise integration and business intelligence (analytics), respectively. Figure 1: A Conceptual Model for ERP II (Adopted from Chan 2010). The structure of this paper is organized as follows. Section 2 describes the research methodology, which includes the research hypotheses, sampling method, data collection instrument and statistical tools used in the study. Section 3 describes the results of the study, which include demographic data, descriptive statistics and results of hypothesis testing. Concluding remarks and direction for future research are provided in section 4. Communications of the IIMA 2011 53 2011 Volume 11 Issue 2

RESEARCH METHODOLOGY The current research aims to identify Jordanian industrial companies readiness for ERP II implementation. To achieve the study goal, researchers used Chan s (2010) conceptual model to distinguish components of ERP II and then explored the existence of each in the study sample. Study Model The sub-systems of ERP II consist of ERP, SCM, SRM, CRM, PRM, and KM, enabled by e- business, KM and BI (Chan, 2010). In this context, KM is considered an ERP II sub-system as well as an enabler to other ERP II sub-systems. A company s readiness to ERP II implementation was defined by exploring the existence and implementation degree of five variables as shown in Figure 2. They consist of the existence of ERP II sub-systems, e- enablement of ERP II sub-systems, integration between ERP II sub-systems, KM support of ERP II sub-systems, and BI support of ERP II sub-systems. Figure 2: ERP II Readiness Variables. Existence of ERP II Sub-systems E-enablement of ERP II Sub-systems Integration between ERP II Sub-systems ERP II Readiness KM support of ERP II Sub-systems BI support of ERP II Sub-systems Research Hypotheses The current study examines the following hypotheses in null form: H 0 1 : The Jordanian industrial companies are not ERP II ready. This hypothesis can be divided to the following null hypotheses: 1.1. The Jordanian industrial companies do not have all ERP II sub-systems. Communications of the IIMA 2011 54 2011 Volume 11 Issue 2

1.2. The Jordanian industrial companies do not e-enable all ERP II sub-systems. 1.3. The Jordanian industrial companies ERP is not integrated with the other ERP II subsystems. 1.4. The Jordanian industrial companies KM does not support the other ERP II sub-systems. 1.5. The Jordanian industrial companies BI does not support the other ERP II sub-systems. Sampling The population of the study consists of the Jordanian industrial companies that are listed in Amman Stock Exchange (ASE). Accordingly, one hundred and three Jordanian companies were selected from the industrial sector taking into the consideration the availability of IT departments in these companies. Only companies' headquarters were covered where the targeted respondents were expected to reside. The data is collected by using a self-administered questionnaire that measures the study model variables. Data Collection Instrument In the current research, data is collected using a self-administered questionnaire that is divided into the three main sections. The first section covers the respondents demographic characteristics. In the second section of the questionnaire, the respondents were asked to indicate the existence, e-enablement, KM support and BI support of ERP II sub-systems using fifty two questions distributed as follows. Enterprise Resource Planning (ERP) (Questions 1-4) Supply Chain (SCM) (Questions 5-16) Supplier Relationship (SRM) (Questions 17-32) Customer Relationship (CRM) (Questions 33-39) Partner Relationship (PRM) (Questions 40-47) Knowledge (KM) (Questions 48-52) The third section covers the ERP integration with the other sub-systems. The respondents were asked to indicate the systems that are integrated with the company s ERP system. In addition, they were asked to choose from a predefined list that includes SCM, SRM, CRM, PRM and KM. The researchers sent the questionnaire by mail followed by face to face interviews in order to maximize the response rate and answer any possible questoins about the questionnaire. One hundred three questionnaires were sent; fifty one were received in usable format, indicating a response rate of 49.5%. Statistical Tools In the current study, some of the measures of central tendency were not used because they were not valid for questions that use the nominal scale. Consequently, the mean was not calculated for questions using the nominal scale (e.g. exist, not exist). Furthermore, the variance measure was not used because it is calculated using squared distances from the mean (Zikmund, 2003). Frequency distribution is a summary table in which the data is arranged into convenientlyestablished, numerically-ordered class grouping or categories. Hence, frequency is considered a Communications of the IIMA 2011 55 2011 Volume 11 Issue 2

valid measurement for the nominal scale and was used in the current study. Due to the discrete nature of the collected data, the nominal scale qualitative responses were converted to numerical values through the following steps (Hayale & Abu-Khadra, 2006): Coding the nominal scales, where 0 = not exist and 1 = exist. Summing up of all question values for each variable. Dividing the previous step result by the total number of questions. The materiality weights for the study instrument questions were considered to be equal (Klapper & Love, 2002), because the materiality of each dimension is contingent upon a variety of internal and external factors related to each environment (Bowen, Cheung, & Rhode, 2007). Additionally, the researchers used the P value in order to test the sampling distribution normality using the following rule: If the number of success (X) and the number of failures are each at least five, the sampling distribution of proportion approximately follows a standardized normal distribution (Berenson, Levine, & Krehbiel, 2002). For the major and minor hypotheses, the researchers used the Z-test for proportion that pertains to the population proportion P percentage by calculating the sample proportion Ps. The values of this statistic were compared to the hypothesized value of the parameter P (defined norms) so that the decision can be made for each hypothesis. RESULTS This section is organized as follows: sub-section 3.1 discusses the demographic data, sub-section 3.2 contains descriptive statistics, sub-section 3.3 describes the study hypothesis testing and conclusions, and sub-section 3.4 describes the limitations of the study. The aspects in SCM and SRM are developed based on functions described in SAP (2011a, 2001b). The aspects in CRM and PRM are developed based on functions described in Gebert, Geib, Kolbe, and Riempp (2002), Bueren, Schierholz, Kolbe, and Brenner (2004) and Chan (2009). The aspects in KM are developed based on functions described in Becerra-Fernandez et al. (2004). Demographic Data In order to test the eligibility of respondents, knowledge and experience levels were examined in the descriptive statistics in the demographic section of the questionnaire. Table 1 shows that the majority of the respondents (~80%) have bachelor or master degrees, while approximately 16% of the respondents indicated that they have two year college degrees. Table 2 illustrates that the majority of the respondents (~51%) have four to seven years of experience, while 45% of the respondents have more than eight years in their fields. Communications of the IIMA 2011 56 2011 Volume 11 Issue 2

Table 1: Frequency Distribution of the Respondents Education Level. Education Level Frequency Percentage to Total Respondents* Two year College 8 15.68% Bachelor 29 56.86% Master 12 23.52% Ph.D. 0 0.0% Others 2 3.92% Total 51 100% *Results were rounded to two decimal places Table 2: Frequency Distribution of the Respondents Experience. Experience Level Frequency Percentage to Total Respondents One to three years 2 3.92% Four to less than seven years 26 50.98% Eight to less than eleven years 18 35.29% More than eleven years 5 9.80% Total 51 100% Overall, based on the demographic characteristics of the respondents, it can be concluded that the respondents to the questionnaire have an appropriate level of knowledge to participate in the study survey, which increases the credibility and reliability of their answers. The following sections focus on the statistical findings of the study. Descriptive Results of Analysis Enterprise Resource Planning (ERP): To explore the ERP dimension, respondents were asked to indicate the existence, e-enablement, KM support and BI integration for each ERP component (see Table 3). As expected, all respondents indicated that their companies have all the major aspects of ERP: sales and marketing, manufacturing and production, accounting and finance, and human resources. Moreover, results revealed a consistent level for e-enablement (86%-88%) and knowledge management (KM) support for their ERP systems (53%-57%). However, business intelligence (BI) integration with ERP systems scored 20% or less. Communications of the IIMA 2011 57 2011 Volume 11 Issue 2

Table 3: Enterprise Resource Planning (ERP) Frequencies. Aspect Sales & Marketing & Production Accounting & Finance Human Resources Existence E-enabled Enabled by KM % BI Integration % 51 100 45 88 29 57 10 20 51 100 45 88 28 55 9 18 51 100 44 86 27 53 8 16 51 100 44 86 27 53 8 16 Table 4: Supply Chain (SCM) Frequencies. Aspect Existence E-enabled Enabled by KM % BI Integration % Planning Demand Planning & 51 100 43 84 23 45 9 18 Forecasting Safety stock planning 51 100 43 84 23 45 9 18 Supply network planning 49 96 36 71 22 43 8 16 Distribution planning 49 96 34 67 20 39 7 14 Supply network collaboration 44 86 28 55 12 24 7 14 Execution Materials management 50 98 38 75 19 37 7 14 Manufacturing execution 51 100 33 65 19 37 7 14 Order promising 50 98 32 63 18 35 7 14 Transportation execution 44 86 27 53 11 22 7 14 Warehouse management 48 94 32 63 18 35 7 14 Visibility Design & Analytics Strategic supply chain design 46 90 32 63 11 22 7 14 Supply chain KPIs 46 90 28 55 11 22 7 14 Communications of the IIMA 2011 58 2011 Volume 11 Issue 2

Supply Chain (SCM):The descriptive statistics illustrated in Table 4 revealed a high percentage of SCM implementation; the lowest percentage of 86% was given to supply network collaboration and transportation execution. The highest implementation percentage of 100% was given to demand planning and forecasting and safety stock planning, which indicates a higher focus over the planning functions in SCM. SCM e-enablement received inconsistent results with a wider range of implementation (53%-84%). The highest percentage was given again to planning activities while the lowest was given to transportation execution. Furthermore, knowledge management support to SCM percentages was lower than the ERP results. The highest percentage of 45% was given to demand planning and forecasting and safety stock planning while the lowest percentage of 22% was given to transportation execution, strategic supply chain design and supply chain KPIs. As happened with ERP, business intelligence with SCM received low percentages of implementation by the respondents. Table 5: Supplier Relationship (SRM) Frequencies. Existence E-enabled Enabled by KM % BI Integration % Aspect Procure to pay Requisitioning 51 100 35 69 17 33 9 18 Order management 50 98 36 71 17 33 9 18 Receiving 50 98 35 69 17 33 8 16 Financial settlement 50 98 34 67 17 33 7 14 Catalog Master data consolidation 51 100 30 59 17 33 7 14 Centralized master data management Centralized Sourcing Supplier qualification 51 100 29 57 16 31 7 14 46 90 25 49 13 25 7 14 Supplier negotiation 45 88 25 49 12 24 7 14 Bid evaluation and awarding 48 94 22 43 16 31 7 14 Centralized Contract Contract creation 39 76 20 39 11 22 7 14 Contract execution Contract monitoring 38 75 19 37 11 22 7 14 32 63 19 37 11 22 7 14 Communications of the IIMA 2011 59 2011 Volume 11 Issue 2

Supplier Collaboration Document exchange Supplier portal management Supplier Evaluation Reporting and response monitoring Supplier development and performance management 51 100 31 61 16 31 7 14 44 86 26 51 11 22 7 14 41 80 24 47 7 14 7 14 36 71 25 49 7 14 7 14 Supplier Relationship (SRM): To explore the SRM dimension, the respondents were asked to indicate the existence, e-enablement, KM support and BI integration for each SRM major components (Table 5). Almost all of the respondents indicated that they have the aspects of procure-to-pay and catalog management. In addition, the respondents indicated a lower implementation level for centralized sourcing, supplier evaluation and supplier collaboration. Moreover, the results revealed the lowest implementation level for centralized contract management. In regard to e-enablement, SRM aspects are ordered as follows: procure-to-pay, catalog management, supplier collaboration, centralized sourcing, supplier evaluation and centralized contract management. At last, business intelligence received the lowest percentages by the respondents; all the SRM aspects, except requisitioning and order management, received approximately 14%. Customer Relationship (CRM): The descriptive statistics in Table 6 indicated a high percentage of CRM implementation (>90%) for marketing and sales functions, while service received 65%. The same story happened with e-enablement; marketing and sales received a moderate percentage (61%-63%), while service functions received 41% or less. KM support results were not encouraging; the highest scored implementation percentage was 33% for offer management, and the lowest was 22% for service management. Moreover, BI integration received the lowest percentages of implementation in the CRM group; most of the functions received a 14% except service activities that received a relatively higher implantation rate of 22% to 24%. Table 6: Customer Relationship (CRM) Frequencies. Aspect Marketing Marketing Resources & Campaign Existence E-enabled Enabled by KM % BI Integration % 46 90 31 61 14 27 7 14 Communications of the IIMA 2011 60 2011 Volume 11 Issue 2

Lead Sales Offer Contract Customer Order Service Service Inquiry and Complaint 46 90 31 61 14 27 7 14 49 96 32 63 17 33 7 14 46 90 31 61 16 31 7 14 49 96 32 63 16 31 7 14 33 65 20 39 11 22 12 24 33 65 21 41 12 24 11 22 Partner Relationship (PRM): The descriptive statistics for PRM were consistent with CRM; marketing and sales functions received higher existence rates compared to service functions with difference in some cases up to 31%. In addition, e-enablement results were consistent in general among the different functions of PRM. Finally, BI scored exactly 14% implementation rate for all of PRM functions. Table 7 illustrates the statistics for PRM. Table 7: Partner Relationship (PRM) Frequencies. Aspect Marketing Campaign Recruitment Lead Sales Referral Contract Partner/Customer Order Existence E-enabled Enabled by KM % BI Integration % 43 84 28 55 10 20 7 14 42 82 27 53 10 20 7 14 39 76 25 49 10 20 7 14 45 88 31 61 14 27 7 14 45 88 28 55 14 27 7 14 44 86 29 57 15 29 7 14 Communications of the IIMA 2011 61 2011 Volume 11 Issue 2

Service Service Inquiry and Complaint 32 63 23 45 9 18 7 14 29 57 18 35 9 18 7 14 Knowledge (KM): In the last section of the descriptive statistics, respondents were asked to indicate existence, e-enablement and BI integration for KM. Significant implementation percentages were reported by respondents (82% - 100%), with moderate level for e-enablement and significantly low level for BI integration. Table 8 illustrates the statistics for KM. Table 8: Knowledge (KM) Frequencies. Aspect Existence E-enabled BI Integration % Knowledge Capture 51 100 28 55 11 22 Knowledge Creation 47 92 27 53 11 22 Knowledge Sharing 44 86 26 51 11 22 Knowledge Storage 42 82 26 51 11 22 Knowledge Application & Integration 42 82 26 51 11 22 Study Hypothesis Testing and Conclusions The statistical result of the Z-test for proportion is used to test the study major and minor hypotheses. In using the Z-test statistical tool, the norm was defined to be 70%. The developed norms are used as cut points for minimum acceptable percentages, where the response is considered a success if its evaluation percentage exceeds the norm. The researchers tested for significant differences between applied percentages and this norm using the Z test for proportion. Based on the statistical findings in Table 9, the p-value appears to be less than 0.05 for ERP, SCM, SRM, and KM. The p-values for CRM and PRM are higher than 0.05, which imply that they fall in the acceptance area. Consequently, it was concluded that the Jordanian companies do not have all the ERP II subsystems. Table 9: ERP II Components. System Success Z value P value Decision ERP 51 4.675162 0.00000 R SCM 49 4.06403 0.00002 R SRM 45 2.841765 0.00224 R CRM 40 1.313935 0.09443 A PRM 41 1.619501 0.05267 A KM 42 1.925067 0.02711 R Communications of the IIMA 2011 62 2011 Volume 11 Issue 2

To test the second minor hypothesis, which examines the Jordanian companies e-enablement for ERP II, the Z-test for proportion was used. The p-values for SCM, SRM CRM, PRM and KM are higher than 0.05. The ERP p-value alone indicates hypothesis rejection. Accordingly, we conclude that the Jordanian companies do not e-enable all ERP II subsystems, see Table 10. Based on the statistical findings in Table 11, the researchers were not able to reject the third minor hypothesis. The p-value supports a conclusion that considers the Jordanian companies not having the integrated ERP II components. Table 10: E-enablement of ERP II Sub-systems. System Success Z value P value Decision ERP 44 2.536199 0.00560 R SCM 29-2.04729 0.97969 A SRM 21-4.49182 1.00000 A CRM 24-3.57512 0.99982 A PRM 21-4.49182 1.00000 A KM 26-2.96399 0.99848 A Table 11: ERP Integration with ERP II Sub-systems System Success Z value P value Decision ERP integration with other components 12-7.24192 1.00000 A Table 12 illustrates the statistical findings with regard to the forth minor hypothesis, which examines the KM support to ERP II subsystems. The p-value appears to be more than 0.05 for all of the hypothesis aspects. Therefore, the researchers conclude that the Jordanian companies KM systems do not support the other ERP II subsystems. Table 12: KM Support of ERP II Sub-systems. System Success Z value P value Decision ERP 27-2.65843 0.99607 A SCM 10-7.85305 1.00000 A SRM 10-7.85305 1.00000 A CRM 11-7.54748 1.00000 A PRM 9-8.15862 1.00000 A Finally, Table 13 shows the results regarding the last minor hypothesis, which measures the BI support of other ERP II subsystems. Again the p-values for ERP, SCM, CRM, SRM, PRM, and KM are higher than 0.05. Thus, the researchers did not reject the null hypothesis. Communications of the IIMA 2011 63 2011 Volume 11 Issue 2

Table 13: BI Integration with ERP II Sub-systems. System Success Z value P value Decision ERP 8-8.46418 1.00000 A SCM 7-8.76975 1.00000 A SRM 7-8.76975 1.00000 A CRM 7-8.76975 1.00000 A PRM 7-8.76975 1.00000 A KM 11-7.54748 1.00000 A Study Limitations As with all research, this study is subject to any number of limitations that might be explored in future research. A questionnaire survey was adopted in this study and the researchers were not able to question the respondents to ascertain in more details the exact nature of the responses. Therefore, extra care and caution is essential when interpreting questionnaire findings. In addition, due to time constraints and the availability of interviewees, not all respondents were interviewed. The current study is considered as exploratory. Consequently, future research work may explore different and more developed instruments which take into consideration cultural and environmental factors to enhance the results value. Despite the limitations that have been identified, this study has provided several important insights into issues relating to ERP II readiness in the Jordanian industrial companies. CONCLUSIONS The study results revealed that the Jordanian industrial companies have all of the ERP II components with the exception of CRM and PRM. The descriptive statistics also showed a significant implementation percentage drop in the service area for both of CRM and PRM. System integration across ERP II sub-systems poses major challenges in ERP II implementation. Despite the existence of most of the major components of ERP II system in the Jordanian industrial companies, they suffered from significant integration deficiency. The study revealed that no significant integration levels were found between ERP and SCM, SRM, CRM, PRM and KM. Additionally, only ERP was found to have enough e-enablement while the other ERP II components suffered from lower level of e-enablement. Despite the evidence of having KM systems in the Jordanian industrial companies, ERP II sub-systems did not have enough KM support, which indicates that KM was not deployed effectively in spite of their existence in these companies. The Jordanian companies showed good signs of using e-commerce activities, however coupled with poor level of BI integration. The BI intelligence integration scored the lowest level of existence, which indicates the lack of an enterprise analytic strategy. The findings of this study shall encourage the Jordanian industrial companies to review their IS environment to maximize their IT investment return. Further studies can investigate the factors that contribute to the lack of downstream relationship management towards customers and channel partners, and the lack of analytical capabilities in Jordanian industrial companies. At last, the researchers encourage a future research that extends the scope of this study to include Communications of the IIMA 2011 64 2011 Volume 11 Issue 2

the companies characteristics, environmental and cultural factors, and return on IT investment analysis on ERP II implementation. REFERENCES Bannan, K. J. (2004). As IT spending rallies, marketers revisit CRM. B to B, 89(1), 13. Beatty, R. C., & Williams C., D. (2006). ERP II: Best practices for successfully implementing an ERP upgrade. Communication of ACM, 49(3). doi: 10.1145/1118178.1118184 Becerra-Fernandez, I., Gonzalez, A., & Sabherwal, R. (2004). Knowledge management: Challenges, solutions, and technologies. Upper Saddle River, NJ: Prentice Hall. Berenson, M. L., Levine, D. M., & Krehbiel, T. C. (2002). Basic business statistics: Concepts and applications. Upper Saddle River, NJ: Prentice Hall. Bowen, P. L., Cheung, M. D., & Rohde, F. H. (2007). Enhancing IT governance practices: A model and case study of an organization s efforts. International Journal of Accounting Information Systems, 8(3), 191-221. Bueren, A., Schierholz, R., Kolbe, L., & Brenner, W. (2004). Customer knowledge management: Improving performance of customer relationship management with knowledge management. Proceedings of the 37 th Annual Hawaii International Conference on System Sciences (HICSS 04), Track 7, Volume 7, 70172.2. doi: 10.1109/HICSS.2004.1265416 Chan, J. O. (2009). Integrating knowledge management and relationship management in an enterprise environment. Communications of the International Information Association, 9(4), 37-52. Chan, J. O. (2010). E-business enabled ERP II architecture. Communications of the International Information Association, 10(1), 44-54. Daneva, M., & Wieringa, R. J. (2008). Cost estimation for cross-organizational ERP projects: Research perspectives. Software Quality Journal, 16(3), 459 481. doi: 10.1007/s11219-008-9045-8 Folorunso, O., Adewale, G., Ogunde, A. O., Okesola, J. O. (2011). Pinch analysis as a knowledge management tool for optimization in supply chain. Computer and Information Science, 4(1), 79-89. Galbreath, J. (2002). Success in the relationship age: Building quality relationship assets for market value creation. The TQM Magazine, 14(1), 8-24. doi: 10.1108/095447802104 13219 Communications of the IIMA 2011 65 2011 Volume 11 Issue 2

Gartner Group. (2000). ERP is dead: Long live ERP II. Gartner Group, 2000. Retrieved from http://www.sunlike.com/internet/onlineerp/images/long%20live%20erpii%20by% 20Gartner%20Group.pdf Gebert, H., Geib, M., Kolbe, L., & Riempp, G. (2002). Towards customer knowledge management: Integrating customer relationship management and knowledge management concepts. Proceedings of the 2 nd International Conference on Electronic Business (ICEB 2002), 296-298. Taipei, Taiwan. Hayale, T. H., & Abu-Khadra, H. A. (2006). Evaluation of the effectiveness of control systems in the computerized accounting information systems: An empirical research applied on Jordanian banking sector. Journal of Accounting Business &, 13, 39-68. Johnson, J. (2004). Making CRM technology work. British Journal of Administrative, 39, 22-23. Kang, S., Park, J. H., & Yang, H. D. (2008). ERP alignment for positive business performance: Evidence from Korea s ERP market. Journal of Computer Information Systems, 48(4), 25-38. Klapper, L. F., & Love, I. (2002). Corporate governance, investor protection, and performance in emerging markets, Journal of Corporate Finance, 10(5), 703-728. Lewis, B. (2001). The 70-percent failure. InfoWorld, 23(44), 50. McKenzie, J. (2001). Serving suggestions. Financial (CIMA), 26-27. Mohamed, M. (2002). Points of the triangle. Intelligent Enterprise, 5(14), 32-37. Retrieved from http://search.proquest.com/docview/200572738 Mohamed, M., & Fadlalla, A. (2005). ERP II: Harnessing ERP systems with knowledge management Capabilities. Journal of Knowledge Practice, 6, 1-13. Retrieved from http://www.tlainc.com/articl91.htm. Porter, M. E. (2001). Strategy and the internet. Harvard Business Review, 79(3), 62-78. SAP. (2011a). Features and functions of SAP SCM. Retrieved from http://www.sap.com/ solutions/business-suite/scm/featuresfunctions/planningandcollaboration/index.epx SAP. (2011b). Features & functions: Procurement software for your SRM system. Retrieved from http://www.sap.com/solutions/business-suite/srm/featuresfunctions/procurementsoftware/index.epx Turner, D., & Chung, S. H. (2005). Technological factors relevant to continuity on ERP for e- business platform: Integration, modularity, and flexibility. Journal of Internet Commerce, 4(4), 119-132. doi: 10.1300/J179v04n04_08 Communications of the IIMA 2011 66 2011 Volume 11 Issue 2

Zikmund, W. G. (2003). Business research methods (7 th ed.). Mason, OH: Thomson/South- Western. Communications of the IIMA 2011 67 2011 Volume 11 Issue 2

This Page Was Left Blank Intentionally. Communications of the IIMA 2011 68 2011 Volume 11 Issue 2