Enterprise resource planning
Enterprise resource planning (ERP) is the integrated management of main business processes, often in real time and mediated by software and technology.
≈ 19 min read
Enterprise resource planning. encyclopegia.org, snapshot enwiki-001378223632. /a/enterprise-resource-planning
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
Enterprise resource planning (ERP) is the integrated management of main business processes, often in real time and mediated by software and technology. ERP is usually referred to as a category of business management software—typically a suite of integrated applications—that an organization can use to collect, store, manage and interpret data from many business activities.
The finance module in particular is essential to a suite of applications meeting the definition of an ERP system. The finance module provides the system of record for the organisation; recording the commercial impact of the business operations in the General Ledger. ERP systems can be local-based or cloud-based.
Cloud-based applications have grown rapidly since the early 2010s due to the increased efficiencies arising from information being readily available from any location with Internet access. However, ERP differs from integrated business management systems by including planning all resources that are required in the future to meet business objectives.
This includes plans for getting suitable staff and manufacturing capabilities for future needs. ERP provides an integrated and continuously updated view of core business processes, typically using a shared database managed by a database management system.
ERP systems track business resources—cash, raw materials, production capacity—and the status of business commitments: orders, purchase orders, and payroll. The applications that make up the system share data across various departments (manufacturing, purchasing, sales, accounting, etc.) that provide the data.
ERP facilitates information flow between all business functions and manages connections to outside stakeholders. Estimates of the size of the global ERP market range between US$78 and US$81 billion in 2026. Though early ERP systems focused on large enterprises, smaller enterprises increasingly use ERP systems.
The ERP system integrates varied organizational systems and facilitates error-free transactions and production, thereby enhancing the organization's efficiency. However, developing an ERP system differs from traditional system development. ERP systems run on a variety of computer hardware and network configurations, typically using a database as an information repository.
Functional areas
An ERP system covers the following common functional areas. In many ERP systems, these are called and grouped together as ERP modules: Financial accounting: general ledger, fixed assets, payables including vouchering, matching and payment, receivables and collections, cash management, financial consolidation Management accounting: budgeting, costing, cost management, activity based costing, billing, invoicing (optional) Human resources: recruiting, training, rostering, payroll, benefits, retirement and pension plans, diversity management, retirement, separation Manufacturing: engineering, bill of materials, work orders, scheduling, capacity, workflow management, quality control, manufacturing process, manufacturing projects, manufacturing flow, product life cycle management Order processing: order to cash, order entry, credit checking, pricing, available to promise, inventory, shipping, sales analysis and reporting, sales commissioning Supply chain management: supply chain planning, supplier scheduling, product configurator, order to cash, purchasing, inventory, claim processing, warehousing (receiving, putaway, picking and packing) Project management: project planning, resource planning, project costing, work breakdown structure, billing, time and expense, performance units, activity management Customer relationship management (CRM): sales and marketing, commissions, service, customer contact, call center support CRM systems are not always considered part of ERP systems but rather business support systems (BSS) Supplier relationship management (SRM): suppliers, orders, payments.
Data services: various "self-service" interfaces for customers, suppliers or employees Management of school and educational institutes. Contract management: creating, monitoring, and managing contracts, reducing administrative burdens and minimising legal risks.
These modules often feature contract templates, electronic signature capabilities, automated alerts for contract milestones, and advanced search functionality.
Implementation
ERP's scope usually implies significant changes to staff work processes and practices. Generally, three types of services are available to help implement such changes: consulting, customization, and support. Implementation time depends on business size, number of modules, customization, the scope of process changes, and the readiness of the customer to take ownership for the project.
Modular ERP systems can be implemented in stages. The typical project for a large enterprise takes about 14 months and requires around 150 consultants. Small projects can require months; multinational and other large implementations can take years.
Customization can substantially increase implementation times. Besides that, information processing influences various business functions e.g. some large corporations like Walmart use a just in time inventory system. This reduces inventory storage and increases delivery efficiency, and requires up-to-date data.
Before 2014, Walmart used a system called Inforem developed by IBM to manage replenishment.
Process preparation
Implementing ERP typically requires changes in existing business processes. Poor understanding of needed process changes prior to starting implementation is a main reason for project failure. The difficulties could be related to the system, business process, infrastructure, training, or lack of motivation.
It is therefore crucial that organizations thoroughly analyze processes before they deploy an ERP software. Analysis can identify opportunities for process modernization. It also enables an assessment of the alignment of current processes with those provided by the ERP system.
Research indicates that risk of business process mismatch is decreased by: Linking current processes to the organization's strategy Analyzing the effectiveness of each process Understanding existing automated solutions ERP implementation is considerably more difficult (and politically charged) in decentralized organizations, because they often have different processes, business rules, data semantics, authorization hierarchies, and decision centers. This may require migrating some business units before others, delaying implementation to work through the necessary changes for each unit, possibly reducing integration (e.g., linking via master data management) or customizing the system to meet specific needs.
A potential disadvantage is that adopting "standard" processes can lead to a loss of competitive advantage. While this has happened, losses in one area are often offset by gains in other areas, increasing overall competitive advantage.
Configuration
Configuring an ERP system is largely a matter of balancing the way the organization wants the system to work, and the way the system is designed to work out of the box. ERP systems typically include many configurable settings that in effect modify system operations.
For example, in the ServiceNow platform, business rules can be written requiring the signature of a business owner within 2 weeks of a newly completed risk assessment. The tool can be configured to automatically email notifications to the business owner, and transition the risk assessment to various stages in the process depending on the owner's responses or lack thereof.
Customization
ERP systems are theoretically based on industry best practices, and their makers intend that organizations deploy them "as is". ERP vendors do offer customers configuration options that let organizations incorporate their own business rules, but gaps in features often remain even after configuration is complete.
ERP customers have several options to reconcile feature gaps, each with their own pros/cons. Technical solutions include rewriting part of the delivered software, writing a homegrown module to work within the ERP system, or interfacing to an external system.
These three options constitute varying degrees of system customization—with the first being the most invasive and costly to maintain. Alternatively, there are non-technical options such as changing business practices or organizational policies to better match the delivered ERP feature set.
Key differences between customization and configuration include: Customization is always optional, whereas the software must always be configured before use (e.g., setting up cost/profit center structures, organizational trees, purchase approval rules, etc.). The software is designed to handle various configurations and behaves predictably in any allowed configuration. The effect of configuration changes on system behavior and performance is predictable and is the responsibility of the ERP vendor.
The effect of customization is less predictable. It is the customer's responsibility, and increases testing requirements. Configuration changes survive upgrades to new software versions.
Some customizations (e.g., code that uses pre–defined "hooks" that are called before/after displaying data screens) survive upgrades, though they require retesting. Other customizations (e.g., those involving changes to fundamental data structures) are overwritten during upgrades and must be re-implemented.
Advantages of customization include: Improving user acceptance Potential to obtain competitive advantage vis-à-vis companies using only standard features. Customization's disadvantages include that it may: Increase time and resources required to implement and maintain Hinder seamless interfacing/integration between suppliers and customers due to the differences between systems Limit the company's ability to upgrade the ERP software in the future Create overreliance on customization, undermining the principles of ERP as a standardizing software platform
Data migration
Data migration is the process of moving, copying, and restructuring data from an existing system to an enterprise resource planning (ERP) system. It is a critical component of a successful implementation and requires thorough planning. However, because migration typically occurs near the end of the implementation process, it often receives inadequate attention.
The following steps can help structure an effective migration plan: Identify the data to be migrated. Determine the migration timing. Generate data migration templates for key data components Freeze the toolset.
Decide on the migration-related setup of key business accounts. Define data archiving policies and procedures. Often, data migration is incomplete because some of the data in the existing system is either incompatible or not needed in the new system.
As such, the existing system may need to be kept as an archived database to refer back to once the new ERP system is in place.
Extensions
ERP systems can be extended with third-party software, often via vendor-supplied interfaces. Extensions offer features such as: product data management product life cycle management customer relations management data mining e-procurement accounting management
Advantages
The most fundamental advantage of ERP is that the integration of a myriad of business processes saves time and expense. Management can make decisions faster and with fewer errors. Data becomes visible across the organization.
Tasks that benefit from this integration include: Sales forecasting, which allows inventory optimization. Chronological history of every transaction through relevant data compilation in every area of operation.
Order tracking, from acceptance through fulfillment Revenue tracking, from invoice through cash receipt Matching purchase orders (what was ordered), inventory receipts (what arrived), and costing (what the vendor invoiced) ERP systems centralize business data, which: Eliminates the need to synchronize changes between multiple systems—consolidation of finance, marketing, sales, human resource, and manufacturing applications Brings legitimacy and transparency to each bit of statistical data Facilitates standard product naming/coding Provides a comprehensive enterprise view (no "islands of information"), making real–time information available to management anywhere, anytime to make proper decisions Protects sensitive data by consolidating multiple security systems into a single structure
Benefits
ERP creates a more agile company that adapts better to change. It also makes a company more flexible and less rigidly structured so organization components operate more cohesively, enhancing the business—internally and externally. ERP can improve data security in a closed environment.
A common control system, such as the kind offered by ERP systems, allows organizations the ability to more easily ensure key company data is not compromised. This changes, however, with a more open environment, requiring further scrutiny of ERP security features and internal company policies regarding security. ERP provides increased opportunities for collaboration.
Data takes many forms in the modern enterprise, including documents, files, forms, audio and video, and emails. Often, each data medium has its own mechanism for allowing collaboration. ERP provides a collaborative platform that lets employees spend more time collaborating on content rather than mastering the learning curve of communicating in various formats across distributed systems.
ERP is enhanced decision-making capabilities. By consolidating data from various departments and functions into a single, unified platform, ERP systems provide decision-makers with real-time insights and comprehensive analytics.
This enables more informed and data-driven decision-making processes across the organization, leading to improved strategic planning, resource allocation, and overall business performance. Moreover, ERP systems facilitate better forecasting and trend analysis, helping businesses anticipate market changes, identify opportunities, and mitigate risks more effectively.
Disadvantages
Customization can be problematic. Compared to the best-of-breed approach, ERP can be seen as meeting an organization's lowest common denominator needs, forcing the organization to find workarounds to meet unique demands. Re-engineering business processes to fit the ERP system may damage competitiveness or divert focus from other critical activities.
ERP can cost more than less integrated or less comprehensive solutions. High ERP switching costs can increase the ERP vendor's negotiating power, which can increase support, maintenance, and upgrade expenses. Overcoming resistance to sharing sensitive information between departments can divert management attention.
Integration of truly independent businesses can create unnecessary dependencies. Extensive training requirements take resources from daily operations. Harmonization of ERP systems can be a mammoth task (especially for big companies) and requires a lot of time, planning, and money.
See also
List of ERP software packages Business process management Comparison of project management software
Bibliography
Henderson, Ian ERP from the Frontline MBE Making ERP Work Ram, Jiwat, and David Corkindale. "Developing a Framework for the Management of Critical Success Factors in Organisational Innovation Projects: A Case of Enterprise Resource Planning Systems."
Integrating Innovation: South Australian Entrepreneurship Systems and Strategies, edited by Göran Roos and Allan O'Connor, University of Adelaide Press, 2015, pp. 327–54, . Riposo, Jessie, Guy Weichenberg, Chelsea Kaihoi Duran, Bernard Fox, William Shelton, and Andreas Thorsen. "Organizational Change Management."
In Improving Air Force Enterprise Resource Planning-Enabled Business Transformation, 23–28. RAND Corporation, 2013. . Aronin, B. S., Bailey, J. W., Byun, J. S., Davis, G. A., Wolfe, C. L., Frazier, T. P., & Bronson, P. F. (2018).
ERP Systems in the DoD. In Global Combat Support System – Marine Corps: Root Cause Analysis (pp. 7–18). Institute for Defense Analyses. .
Ragowsky, Arik, and Toni M. Somers. "Special Section: Enterprise Resource Planning." Journal of Management Information Systems, vol. 19, no. 1, Taylor & Francis, Ltd., 2002, pp. 11–15, .
Liedtka, Jeanne, Andrew King, and Kevin Bennett."Rethinking Strategic Planning at SAP." In Solving Problems with Design Thinking: Ten Stories of What Works, 74–91. Columbia University Press, 2013. .
Morris, Michael G., and Viswanath Venkatesh. "Job Characteristics and Job Satisfaction: Understanding the Role of Enterprise Resource Planning System Implementation." MIS Quarterly, vol. 34, no. 1, Management Information Systems Research Center, University of Minnesota, 2010, pp. 143–61, .
Tsai, Bi-Huei, and Shin-Bin Chou. "Application of Multiple Output Data Envelopement Analysis in Interpreting Efficiency Improvement of Enterprise Resource Planning in Integrated Circuit Firms." The Journal of Developing Areas, vol. 49, no. 1, College of Business, Tennessee State University, 2015, pp. 285–304, . . . . . .
Tian, Feng, and Sean Xin Xu. "How Do Enterprise Resource Planning Systems Affect Firm Risk? Post-Implementation Impact."
MIS Quarterly, vol. 39, no. 1, Management Information Systems Research Center, University of Minnesota, 2015, pp. 39–60, . Ferratt, Thomas W., et al. "Achieving Success in Large Projects: Implications from a Study of ERP Implementations." Interfaces, vol. 36, no. 5, INFORMS, 2006, pp. 458–69, .
Karimi, Jahangir, Toni M. Somers, and Anol Bhattacherjee. "The Impact of ERP Implementation on Business Process Outcomes: A Factor-Based Study." Journal of Management Information Systems 24, no. 1 (2007): 101–34. .
Ranganathan, C., and Carol V. Brown. "ERP Investments and the Market Value of Firms: Toward an Understanding of Influential ERP Project Variables." Information Systems Research, vol. 17, no. 2, INFORMS, 2006, pp. 145–61, .
Benco, Daniel C., and Larry Prather. "Market Reaction to Announcements to Invest in ERP Systems." Quarterly Journal of Finance and Accounting, vol. 47, no. 4, University of Nebraska-Lincoln College of Business Administration, 2008, pp. 145–69, .
Stephenson, Stephen V., and Andrew P. Sage. "Information and knowledge perspectives in systems engineering and management for innovation and productivity through enterprise resource planning." Information Resources Management Journal 20, no. 2 (2007): 44+.
Gale Academic OneFile (accessed January 26, 2022). . McGaughey, Ronald E., and Angappa Gunasekaran. "Enterprise Resource Planning (ERP): past, present and future."
International Journal of Enterprise Information Systems 3, no. 3 (2007): 23+. Gale Academic OneFile (accessed January 26, 2022). . Cordova, Ronald S., Rolou Lyn R. Maata, Ferdinand J. Epoc, and Marwan Alshar'e. "Challenges and Opportunities of Using Blockchain in Supply Chain Management."
Global Business and Management Research: An International Journal 13, no. 3 (2021): 204+. Gale Academic OneFile (accessed January 26, 2022). . Muscatello, Joseph R., and Injazz J. Chen.
"Enterprise resource planning (ERP) implementations: theory and practice." International Journal of Enterprise Information Systems 4, no. 1 (2008): 63+. Gale Academic OneFile (accessed January 26, 2022). .
Muscatello, Joseph R., and Diane H. Parente. "Enterprise resource planning (ERP): a postimplementation cross-case analysis." Information Resources Management Journal 19, no. 3 (2006): 61+.
Gale Academic OneFile (accessed January 26, 2022). . Farzaneh, Mandana, Iman Raeesi Vanani, and Babak Sohrabi. "A survey study of influential factors in the implementation of enterprise resource planning systems."
International Journal of Enterprise Information Systems 9, no. 1 (2013): 76+. Gale Academic OneFile (accessed January 26, 2022). . AlMuhayfith, Sara, and Hani Shaiti.
"The Impact of Enterprise Resource Planning on Business Performance: With the Discussion on Its Relationship with Open Innovation." Journal of Open Innovation: Technology, Market, and Complexity 6, no. 3 (2020). Gale Academic OneFile (accessed January 26, 2022). .
Wenrich, Kristi I., and Norita Ahmad. "Lessons learned during a decade of ERP experience: a case study." International Journal of Enterprise Information Systems 5, no. 1 (2009): 55+.
Gale Academic OneFile (accessed January 26, 2022). . Subramanian, Girish H., and Christopher S. Hoffer. "An exploratory case study of enterprise resource planning implementation."
International Journal of Enterprise Information Systems 1, no. 1 (2005): 23+. Gale Academic OneFile (accessed January 26, 2022). . W. Yang, H. Liu and J. Shi, "The design of printing enterprise resources planning (ERP) software," 2010 2nd IEEE International Conference on Information Management and Engineering, 2010, pp. 151–154, .
Cronan, Timothy Paul, and David E. Douglas. "Assessing ERP learning (management, business process, and skills) and attitudes." Journal of Organizational and End User Computing, April–June 2013, 59+.
Gale Academic OneFile (accessed January 26, 2022). . Hayes, David C., James E. Hunton, and Jacqueline L. Reck. "Market Reaction to ERP Implementation Announcements."
Journal of Information Systems 15, no. 1 (2001): 3. Gale Academic OneFile (accessed January 26, 2022). . Alves, Maria do Ceu, and Sergio Ivo Amaral Matos.
"ERP adoption by public and private organizations--a comparative analysis of successful implementations." Journal of Business Economics and Management 14, no. 3 (2013): 500. Gale Academic OneFile (accessed January 26, 2022). .
Elsayed, N., Ammar, S., and Mardini, G. H., "The impact of ERP utilisation experience and segmental reporting on corporate performance in the UK context", Enterprise Information Systems, vol. 15, no. 1, pp. 61–86, 2021. . . Sutduean, J., Singsa, A., Sriyakul, T., and Jermsittiparsert, K., "Supply Chain Integration, Enterprise Resource Planning, and Organizational Performance: The Enterprise Resource Planning Implementation Approach", Journal of Computational and Theoretical Nanoscience, vol. 16, no. 7, pp. 2975–2981, 2019. . .
Alfaris, M. F., Edikuncoro, G. Y., Savitri, A. L., Yogiari, D., and Sulistio, J., "A Literature Review of Sustain Enterprise Resource Planning", in Materials Science and Engineering Conference Series, 2019, vol. 598, no. 1, p. 012128. . . G. Chattopadhyay, "Development of a learning package for interactive learning in enterprise resources planning (ERP)," 2004 IEEE International Engineering Management Conference (IEEE Cat.
No.04CH37574), 2004, pp. 848–850 Vol.2, . D. Reuther and G. Chattopadhyay, "Critical factors for enterprise resources planning system selection and implementation projects within small to medium enterprises," 2004 IEEE International Engineering Management Conference (IEEE Cat. No.04CH37574), 2004, pp. 851–855 Vol.2, .
Lv, T., Zhang, J., and Chen, Y., "Research of ERP Platform based on Cloud Computing", in Materials Science and Engineering Conference Series, 2018, vol. 394, no. 4, p. 042004. . . Hasan, N., Miah, S. J., Bao, Y., and Hoque, M. R., "Factors affecting post-implementation success of enterprise resource planning systems: a perspective of business process performance", Enterprise Information Systems, vol. 13, no. 9, pp. 1217–1244, 2019. . .
Sardjono, W., Sudirwan, J., Priatna, W., and Putra, G. R., "Application of factor analysis method to support the users acceptance model of ERP systems implementation", in Journal of Physics: Conference Series, 2021, vol. 1836, no. 1. . . Meiryani, Erick Fernando, Setiani Putri Hendratno, Kriswanto, and Septi Wifasari. 2021.
Enterprise Resource Planning Systems: The Business Backbone. 2021 The 5th International Conference on E-Commerce, E-Business and E-Government. Association for Computing Machinery, New York, NY, USA, 43–48.
T. Yang, J. Choi, Z. Xi, Y. Sun, C. Ouyang and Y. Huang, "Research of Enterprise Resource Planning in a Specific Enterprise," 2006 IEEE International Conference on Systems, Man and Cybernetics, 2006, pp. 418–422, . Komala, A. R. and Gunanda, I., "Development of Enterprise Resource Planning using Blockchain", in Materials Science and Engineering Conference Series, 2020, vol. 879, no. 1, p. 012141. . .
Tsai, W.-H., Lee, K.-C., Liu, J.-Y., Lin, S.-J., and Chou, Y.-W., "The influence of enterprise resource planning (ERP) systems' performance on earnings management", Enterprise Information Systems, vol. 6, no. 4, pp. 491–517, 2012. . . Kapulin, D. V., Russkikh, P. A., and Moor, I. A., "Integration capabilities of business process models and ERP-systems", in Journal of Physics: Conference Series, 2019, vol. 1333, no. 7. . .
Sebayang, P., Tarigan, Z. J. H., and Panjaitan, T. W. S., "ERP compatibility on business performance through the inventory system and internal integration", in Materials Science and Engineering Conference Series, 2021, vol. 1010, no. 1, p. 012008. . . August-Wilhelm Scheer and Frank Habermann. 2000.
Enterprise resource planning: making ERP a success. Communications of the ACM 43, 4 (April 2000), 57–61. Kuldeep Kumar and Jos van Hillegersberg.
2000. Enterprise resource planning: introduction. Communications of the ACM 43, 4 (April 2000), 22–26.
Text derived from https://en.wikipedia.org/w/index.php?oldid=1378223632 under CC BY-SA 4.0; modifications have been made.