ERP Foundations, Evolution and Strategic Role

Introduction

Enterprise resource planning (ERP) systems are among the most consequential information systems used by contemporary organizations. They coordinate transactions and information across functions such as finance, procurement, operations, sales, inventory, human resources, maintenance, and distribution. Their significance does not arise merely from software integration. ERP changes how work is structured, how data is defined, how decisions are made, and how organizational performance is governed.

For operations managers, ERP is particularly important because operational performance depends on the alignment of material flows, capacity, demand, suppliers, orders, people, and financial consequences. An ERP system provides a common informational infrastructure through which these elements can be represented and coordinated. However, ERP is not automatically beneficial. Poor process design, weak data governance, inappropriate customization, inadequate training, and unrealistic implementation expectations can make an ERP investment expensive and strategically harmful.

This chapter establishes the conceptual foundation for studying ERP. It explains the terminology and historical development of ERP, identifies its defining characteristics, distinguishes it from related system categories, and applies four complementary perspectives: business-process management, systems thinking, organizational fit, and information-systems success.

Learning Objectives

After completing this chapter, the reader should be able to:

1. Define ERP and distinguish its principal components and terminology.
2. Explain the historical progression from inventory control and MRP to contemporary ERP and cloud-based platforms.
3. Analyze the characteristics, benefits, risks, and strategic implications of ERP.
4. Distinguish ERP from legacy systems, best-of-breed applications, and enterprise platforms.
5. Apply process, systems, organizational-fit, and information-systems-success perspectives to ERP decisions.
6. Evaluate an ERP initiative using operational, organizational, governance, and strategic criteria.

1. What Is ERP?

ERP is an integrated information system that supports and coordinates a broad range of organizational processes through shared data, common transaction rules, and interconnected applications. The term may refer to the software product, the implementation project, or the organizational capability created by combining technology, processes, data, and people.

A useful conceptual definition is:

ERP is an enterprise-wide system of integrated applications and databases that records, processes, and communicates transactions across organizational functions using a coordinated data and process architecture.

This definition contains four important ideas.

Enterprise-wide scope. ERP normally crosses functional and sometimes legal, geographical, and organizational boundaries. It may support multiple plants, warehouses, subsidiaries, currencies, tax regimes, and languages.

Integration. A transaction in one area can affect other areas. For example, a confirmed customer order may create demand, influence availability information, generate a delivery requirement, produce a receivable, and contribute to revenue reporting.

Shared data. Functions use common master data and transaction data rather than maintaining isolated versions of customers, products, suppliers, or accounts.

Process orientation. ERP represents end-to-end processes such as procure-to-pay, order-to-cash, plan-to-produce, hire-to-retire, and record-to-report rather than only individual departments.

ERP should not be confused with automation in general. A spreadsheet that automates a calculation is an information tool, but it is not an ERP system. Similarly, an accounting package may be valuable without being enterprise-wide. ERP is distinguished by the breadth and integration of the organizational processes it supports.

Important ERP terminology

2. Historical Evolution of ERP

ERP emerged through several overlapping stages rather than through a single invention. Each stage reflected changes in manufacturing practice, computing technology, management theory, and competitive conditions.

2.1 Inventory control and early computerization

Early computerized systems focused on inventory records, payroll, general ledger processing, and order administration. These applications were often developed for a single department or business problem. They reduced clerical effort but commonly created separate files, duplicated data, and limited visibility across functions.

In a fragmented environment, the inventory department might maintain one product record, purchasing another, and finance a third. Differences in item descriptions, units of measure, or coding could produce reconciliation work and operational errors.

2.2 Material requirements planning

Material requirements planning (MRP) developed in manufacturing organizations to calculate what materials were needed, in what quantities, and at what times. MRP used three principal inputs:

• the master production schedule;
• the bill of materials; and
• inventory records, including on-hand balances and scheduled receipts.

MRP translated a production plan for finished goods into time-phased requirements for components and raw materials. Its logic was based on dependent demand: the demand for a component is derived from the planned production of its parent item.

A simplified net-requirement relationship is:

where NR_t is net requirement in period t, GR_t is gross requirement, SS is desired safety stock, OH_t is projected on-hand inventory, and SR_t is scheduled receipt available by that period. The relationship assumes that quantities are expressed in the same unit and that planned receipts and inventory status are known. It is a planning relationship, not a complete production schedule; lot-sizing, lead times, capacity, scrap, and supplier constraints must also be considered.

MRP improved material availability and reduced reliance on informal expediting. Nevertheless, early MRP systems often treated capacity, labor, and financial consequences inadequately.

2.3 Manufacturing resource planning

Manufacturing resource planning, commonly called MRP II, expanded MRP beyond materials. It incorporated capacity planning, shop-floor control, purchasing, forecasting, sales and operations planning, and financial feedback. The central idea was that manufacturing decisions should be connected to operational and financial plans.

MRP II represented an important movement from a materials calculation system toward an integrated management system. However, its original emphasis remained manufacturing, and many organizations continued to operate separate systems for distribution, human resources, customer management, and corporate finance.

2.4 Enterprise resource planning

During the late twentieth century, commercial software vendors developed broader packages integrating manufacturing with finance, distribution, procurement, human resources, and other functions. The term ERP became widely used to describe these enterprise-wide suites.

ERP adoption accelerated because organizations sought to:

• reduce redundant data entry;
• standardize processes across sites;
• improve reporting and control;
• support globalization and multiple legal entities;
• replace aging mainframe and departmental systems; and
• connect operations with suppliers and customers.

Implementations were frequently large, expensive, and disruptive. The dominant model involved licensed software installed on company-controlled infrastructure, substantial consulting support, and extensive organizational change.

2.5 Extended ERP and networked enterprises

ERP systems increasingly incorporated or connected to customer relationship management, supply-chain management, product lifecycle management, business intelligence, e-commerce, supplier portals, and transportation systems. The ERP core became part of a wider digital architecture rather than the entire information landscape.

This development also changed the meaning of integration. Integration no longer meant only that modules in one suite shared a database. It included APIs, event-driven interfaces, cloud services, data platforms, mobile applications, Internet of Things devices, and external business networks.

2.6 Cloud ERP and intelligent enterprise systems

Cloud ERP is delivered through provider-managed infrastructure and accessed through networks, usually under a subscription or service agreement. Cloud deployment can reduce the need for customer-managed hardware and may provide more frequent software updates. It can also create concerns about data residency, service continuity, vendor dependence, cybersecurity, integration, and the organization’s ability to control upgrade timing.

Contemporary ERP environments increasingly incorporate analytics, process mining, robotic process automation, machine learning, conversational interfaces, and generative artificial intelligence. These capabilities can help detect anomalies, forecast demand, summarize records, or recommend actions. They do not eliminate the need for accurate data, accountable decisions, process expertise, or internal controls. An algorithm trained on inconsistent master data may simply automate poor decisions more rapidly.

3. Core Characteristics of ERP

3.1 Integration and a common data model

ERP integration operates at several levels. Technical integration allows systems to exchange data. Semantic integration ensures that exchanged data has consistent meaning. Process integration coordinates activities across functions. Managerial integration enables leaders to view performance across organizational boundaries.

A common data model is essential. If one business unit defines a “completed order” as shipment and another defines it as invoicing, a consolidated performance report may be technically complete but conceptually misleading. Data governance must therefore address definitions, ownership, validation rules, change procedures, and accountability.

3.2 Transaction processing and traceability

ERP systems record high-volume transactions such as purchase orders, receipts, production confirmations, inventory movements, invoices, payments, and shipments. Properly designed transactions create an audit trail linking events, users, dates, quantities, and authorizations. This supports operational control, financial reporting, regulatory compliance, and investigation of exceptions.

3.3 Standardization and configuration

Commercial ERP packages embody assumptions about effective business processes. Organizations generally configure parameters—such as organizational units, approval limits, calendars, tax rules, planning policies, and valuation methods—rather than rewriting the software.

Standardization can reduce complexity and improve comparability. It may also suppress legitimate local requirements or valuable differentiating practices. The managerial question is not whether standardization is always good, but which processes should be standardized, where variation is necessary, and whether variation should be handled by configuration, extension, or a separate application.

3.4 Real-time or near-real-time information

ERP can make information available shortly after a transaction is entered. “Real time,” however, should be used carefully. Data may be delayed by batch interfaces, approval queues, synchronization failures, user behavior, or differing update schedules. Timeliness is a quality attribute, not a guarantee that every decision uses perfect current information.

3.5 Embedded controls

ERP supports controls such as segregation of duties, approval workflows, tolerance limits, duplicate-invoice checks, three-way matching, posting-period controls, and access logging. Controls are effective only when designed appropriately and monitored. A technically available control can be bypassed through excessive privileges, informal workarounds, shared accounts, or poor master-data practices.

4. ERP Compared with Related System Categories

ERP exists within an ecosystem of information systems. Understanding the boundaries prevents unrealistic expectations.

ERP and legacy systems

A legacy system is not necessarily obsolete or poor. It may be stable, efficient, and deeply aligned with critical operations. Its difficulties often arise from aging technology, scarce technical expertise, limited integration, poor documentation, or inability to support new regulatory and strategic needs. Replacement should therefore be based on business risk and capability gaps, not simply on age.

ERP and best-of-breed systems

Best-of-breed architecture selects specialized applications for functions such as advanced planning, warehouse management, maintenance, or human capital management. This approach may deliver superior functional depth, but integration must address data ownership, timing, error handling, process orchestration, and responsibility for conflicting records.

ERP and enterprise platforms

An enterprise platform is broader than an ERP application. It may provide identity management, integration services, workflow, analytics, development tools, data management, and application hosting. An ERP can run on or connect to such a platform, but a platform alone does not define accounting rules, inventory processes, procurement controls, or production planning logic.

5. ERP Through Four Analytical Perspectives

5.1 The process perspective

The process perspective views ERP as an enabler of cross-functional work. A process begins with a trigger, transforms inputs, produces outputs, and creates value for a customer or stakeholder. Functional departments are important, but the process perspective asks how work moves across them.

Examples include:

• Procure-to-pay: need identification, requisition, sourcing, purchase order, receipt, invoice verification, and payment.
• Order-to-cash: quotation or order, availability confirmation, fulfillment, shipment, invoicing, and collection.
• Plan-to-produce: demand planning, production planning, material staging, execution, confirmation, and inventory update.
• Record-to-report: transaction capture, period close, reconciliation, consolidation, and reporting.

ERP implementation should begin with process objectives and performance requirements, not with a module checklist. Relevant measures may include cycle time, schedule adherence, inventory accuracy, on-time delivery, invoice exception rate, forecast error, and working capital.

5.2 The systems perspective

Systems thinking emphasizes interdependence, feedback, boundaries, and emergent outcomes. ERP is a socio-technical system: its outcomes arise from the interaction of technology, people, structure, rules, data, suppliers, customers, and the external environment.

A local optimization can damage the whole system. For example, purchasing may obtain lower unit prices by ordering large quantities, while operations experiences excess inventory, storage costs, obsolescence, and reduced cash availability. ERP makes such connections more visible, but visibility does not automatically resolve conflicting objectives.

ERP also creates feedback loops. A sales forecast influences production planning; production plans influence procurement; procurement affects supplier performance and inventory; inventory availability affects customer service and future sales. Errors or delays can propagate through this network. Consequently, implementation should test not only individual transactions but also end-to-end scenarios and exception paths.

5.3 The organizational-fit perspective

The organizational-fit perspective asks whether the system’s structures and assumptions fit the organization’s strategy, processes, culture, governance, and institutional environment.

Fit can be assessed across several dimensions:

• Strategic fit: Does the system support the organization’s competitive priorities?
• Process fit: Do standard processes reflect required operating practices?
• Structural fit: Are responsibilities and decision rights compatible with the design?
• Cultural fit: Are users prepared to work with transparency, standardization, and formal controls?
• Technical fit: Can the architecture integrate with required technologies and data sources?
• Regulatory fit: Can the solution support tax, accounting, labor, privacy, industry, and reporting obligations?

Misfit can be handled through process redesign, configuration, controlled extension, organizational change, or selection of another solution. Customization is only one response and is often the most expensive to maintain.

5.4 The information-systems-success perspective

The DeLone and McLean information-systems-success model provides a useful evaluative lens. Its commonly discussed dimensions include system quality, information quality, service quality, use or intention to use, user satisfaction, and net benefits. The dimensions are interrelated rather than independent.

For ERP, system quality includes reliability, usability, performance, security, and maintainability. Information quality includes accuracy, completeness, relevance, consistency, and timeliness. Service quality includes implementation support, training, responsiveness, and problem resolution. Use must be interpreted carefully: mandatory use does not necessarily indicate acceptance. User satisfaction reflects perceived usefulness and experience. Net benefits include operational, managerial, financial, compliance, and strategic effects.

A successful ERP therefore cannot be judged only by whether it was installed on time or whether users log in. A system may be heavily used because it is compulsory while producing poor information and frustrating workarounds. Evaluation should combine adoption, quality, process performance, control effectiveness, and business outcomes.

6. Strategic Role and Sources of Value

ERP can create value through several mechanisms.

Coordination value arises when functions share timely information and act on consistent plans. Control value arises from authorization, auditability, and standardized rules. Information value arises when integrated data improves analysis and decision quality. Scale value arises when common processes and platforms reduce duplicated effort across sites. Learning value arises when performance data reveals bottlenecks, variation, and improvement opportunities.

ERP rarely creates sustained competitive advantage merely by possessing software that competitors can also buy. Strategic value depends on complementary capabilities: process knowledge, disciplined execution, data governance, managerial attention, skilled employees, supplier relationships, and the ability to convert information into action. In resource-based terms, the software may be widely available, while the organization-specific routines built around it are more difficult to imitate.

Potential benefits include:

• reduced duplicate data entry and reconciliation;
• improved inventory visibility and planning;
• faster financial close;
• improved order and delivery transparency;
• stronger compliance and auditability;
• better cross-site standardization; and
• improved basis for analytics and continuous improvement.

Potential costs include licensing or subscription fees, implementation services, infrastructure, data cleansing, training, process redesign, temporary productivity loss, integration, cybersecurity, and ongoing support. Benefits should therefore be expressed in operational and managerial terms rather than assumed from system installation.

7. Implementation and Governance Principles

ERP implementation is an organizational transformation project, not a simple software installation. Effective governance normally includes an executive sponsor, a cross-functional steering group, process owners, data owners, security and control specialists, technical architects, and informed user representatives.

Several principles are especially important:

1. Define the business case. Specify the problems to be solved, expected benefits, assumptions, costs, risks, and measures of success.
2. Design end-to-end processes. Avoid optimizing modules independently while leaving cross-functional failures unresolved.
3. Establish data ownership early. Identify who defines, approves, cleans, and monitors each critical data object.
4. Prefer fit-to-standard where appropriate. Customize only when the requirement is legally necessary, strategically differentiating, or economically justified.
5. Treat security and controls as design requirements. Do not postpone access roles, segregation of duties, privacy, and audit needs until the end.
6. Use realistic testing. Test normal flows, exceptions, reversals, partial deliveries, returns, failures, period close, and high-volume conditions.
7. Invest in change management. Explain the rationale, redesign roles, train users on business scenarios, and support adoption after go-live.
8. Plan the operating model. Define support, release management, incident management, integration monitoring, data governance, and continuous improvement.

8. Ethical, Governance, and Regulatory Issues

ERP systems concentrate sensitive information and decision authority. Ethical and governance issues include privacy, surveillance, discriminatory analytics, unauthorized access, manipulation of records, excessive employee monitoring, and opaque automated recommendations.

Organizations should apply data minimization, purpose limitation, access control, retention rules, secure authentication, logging, and appropriate transparency. Personal data should be processed lawfully and only for legitimate purposes. Financial and operational records require clear accountability and preservation of audit trails.

Artificial intelligence introduces additional concerns. AI-generated recommendations may be biased by historical data, may lack explainability, and may encourage automation bias—the tendency to accept system outputs without adequate review. Human accountability must remain clear, especially for decisions involving employment, safety, credit, regulatory reporting, or significant customer impact.

9. Illustrative Case: Meridian Components

Background

Meridian Components, a fictional mid-sized manufacturer, operates three plants and sells industrial assemblies in four countries. Its finance, purchasing, production, and sales departments use separate applications connected by spreadsheets and manually prepared files.

Problem

Inventory records differ across plants. Sales representatives promise delivery dates without reliable availability information. Purchasing orders materials using local spreadsheets, while finance spends much of each month reconciling receipts, invoices, and payments. Management cannot produce a consistent profitability report by product family.

The company initially proposes implementing an ERP system within nine months, with success defined as going live before the next financial year.

Analysis

Using the process perspective, the principal weaknesses are not confined to one department. They occur across order-to-cash, procure-to-pay, and plan-to-produce. Using the systems perspective, local purchasing efficiency may be creating enterprise-wide excess inventory, while inconsistent product definitions produce feedback errors in planning and reporting.

The organizational-fit analysis identifies different plant routings, local tax requirements, and legitimate product variations. A single standardized process is desirable for core controls, but not every local practice should be eliminated. The information-systems-success perspective adds requirements for data quality, user training, service support, and measurable benefits beyond technical deployment.

Approach and solution

Meridian establishes process owners and defines a common data dictionary for products, units of measure, suppliers, customers, and accounts. It cleanses material master data before migration and assigns data ownership to accountable business roles. The company adopts a standard procure-to-pay process, while configuring country-specific tax and reporting rules.

The implementation is staged. Finance and procurement are introduced first, followed by inventory and order management, then production planning. End-to-end testing includes partial shipments, returns, invoice discrepancies, production scrap, interplant transfers, and month-end close. A role-based access design separates requisition, purchasing, receipt, invoice approval, and payment responsibilities.

Meridian defines success measures including inventory-record accuracy, purchase-order cycle time, invoice exception rate, on-time delivery, financial-close duration, user adoption, and reporting consistency. It establishes a post-go-live support team rather than treating implementation completion as the end of the project.

Outcome

After stabilization, Meridian obtains a common view of inventory and open orders, reduces manual reconciliation, and improves visibility into production constraints. The company does not achieve every projected benefit immediately: planners require additional training, and two legacy shop-floor systems remain integrated with the ERP core. Nevertheless, governance and process ownership make improvement continuous rather than dependent on spreadsheets.

Learning points

The case demonstrates that ERP value is produced by coordinated changes in process, data, controls, technology, and behavior. A deadline-based definition of success would have obscured the more important questions: whether information is trustworthy, whether processes work end to end, and whether the organization can sustain the new operating model.

10. Contemporary Developments and Critical Issues

ERP is moving toward composable architectures in which organizations combine core ERP capabilities with specialized cloud applications and platform services. This can increase flexibility but also increases the importance of integration governance and clear ownership of data and processes.

Process mining can reconstruct actual process flows from event logs and compare them with intended designs. It is useful for identifying rework, bottlenecks, unauthorized variants, and compliance deviations. Its conclusions remain dependent on event-log completeness and correct interpretation.

Advanced analytics and AI can support demand sensing, predictive maintenance, cash forecasting, anomaly detection, and natural-language interaction. These applications should be evaluated through controlled pilots, explicit performance criteria, model monitoring, security assessment, and human review. Automation is most valuable when the underlying process is stable, data is trustworthy, and exceptions are understood.

A continuing critical issue is the tension between standardization and local responsiveness. Excessive variation undermines integration; excessive uniformity can damage operational effectiveness or violate local requirements. Mature ERP governance treats this as a design and decision-rights problem rather than assuming that either complete standardization or complete flexibility is universally correct.

Chapter Summary

ERP is an enterprise-wide, integrated information system that coordinates transactions, data, processes, and controls across organizational functions. It evolved from inventory control and MRP through MRP II and broad ERP suites to cloud-based and networked enterprise architectures.

The defining characteristics of ERP include shared data, process integration, transaction traceability, standardization, workflow, embedded controls, and enterprise-wide visibility. ERP differs from legacy systems, best-of-breed applications, and enterprise platforms in scope, integration logic, and architectural role.

ERP should be analyzed through complementary perspectives. The process perspective emphasizes end-to-end value creation; systems thinking emphasizes interdependence and feedback; organizational-fit analysis examines alignment with strategy, culture, structure, technology, and regulation; and the information-systems-success perspective evaluates system quality, information quality, service, use, satisfaction, and net benefits.

ERP can improve coordination, control, information quality, standardization, and decision-making, but benefits depend on complementary organizational capabilities. Implementation requires governance, data ownership, process design, security, testing, change management, and post-go-live support. Contemporary cloud, analytics, process-mining, and AI capabilities expand ERP’s potential while increasing concerns about privacy, cybersecurity, vendor dependence, explainability, and accountability.

Key Terms

ERP: An integrated enterprise information system supporting broad organizational processes through shared data and coordinated applications.

MRP: Material requirements planning for calculating time-phased component and material needs.

MRP II: Manufacturing resource planning, extending MRP to capacity, production, purchasing, and financial feedback.

Module: A functional component of an ERP suite.

Master data: Reusable data entities such as products, suppliers, customers, and accounts.

Transaction data: Records of specific business events.

Configuration: Setting software parameters without changing source code.

Customization: Code-based modification or extension of standard software.

Workflow: A controlled sequence of tasks, approvals, and decisions.

Data governance: Policies and responsibilities for data quality, security, ownership, and use.

Legacy system: An established system whose technology, integration, or support limitations may constrain current needs.

Best-of-breed system: A specialized application selected for strong functionality in a particular domain.

Enterprise platform: A broader technical foundation supporting applications, integration, data, identity, and services.

Process owner: The person accountable for the performance and design of an end-to-end process.

Organizational fit: The degree of alignment between a system and organizational strategy, structure, culture, processes, and environment.

Information quality: The accuracy, completeness, relevance, consistency, and timeliness of information.

Role-based access control: Restricting system access according to authorized organizational roles.

Process mining: Analysis of event logs to discover and evaluate actual process behavior.

Cloud ERP: ERP delivered through provider-managed infrastructure, commonly as a subscription service.

Review Questions

Short Answer Questions

1. Define ERP and identify its four central characteristics.
2. What is the difference between master data and transaction data?
3. How did MRP II extend the scope of MRP?
4. Why is ERP implementation considered a socio-technical change?
5. Name four dimensions in the information-systems-success perspective.

Long Answer Questions

1. Explain the historical evolution from inventory control to contemporary cloud ERP.
2. Compare ERP, legacy systems, best-of-breed applications, and enterprise platforms.
3. Discuss the strategic sources of ERP value and explain why software alone rarely creates sustained competitive advantage.
4. Analyze the tension between process standardization and local organizational requirements.
5. Explain how data governance, security, and change management influence ERP success.

Analytical / Application Questions

1. A manufacturer has accurate finance records but inconsistent inventory data across plants. Using the process, systems, and organizational-fit perspectives, diagnose the likely causes and propose an ERP preparation plan.
2. An organization wants to replace a stable legacy system solely because it is old. Develop a decision framework for determining whether replacement, integration, modernization, or retention is most appropriate.
3. Design a balanced ERP success scorecard containing at least one measure each for system quality, information quality, user adoption, process performance, control effectiveness, and strategic benefit. Explain why each measure is relevant.

Multiple Choice Questions with Answers

Question 1

Which characteristic most directly distinguishes ERP from a collection of departmental applications?

A. Use of computer hardware

B. Enterprise-wide integration through shared data and coordinated processes

C. Ability to produce printed reports

D. Use of numerical calculations

Correct Answer: B. Enterprise-wide integration through shared data and coordinated processes

Question 2

Which set contains the three principal inputs of traditional MRP?

A. Customer database, payroll file, and tax ledger

B. Master production schedule, bill of materials, and inventory records

C. Supplier contracts, bank statements, and sales commissions

D. Production sensors, social media, and employee surveys

Correct Answer: B. Master production schedule, bill of materials, and inventory records

Question 3

In the simplified net-requirement relationship, what does safety stock represent?

A. Inventory deliberately maintained as a protection against uncertainty

B. Inventory already consumed by production

C. A scheduled supplier receipt

D. The quantity of finished goods sold

Correct Answer: A. Inventory deliberately maintained as a protection against uncertainty

Question 4

Which statement best describes configuration in ERP?

A. Rewriting all standard source code

B. Selecting and setting system parameters to reflect organizational rules

C. Replacing the ERP database with spreadsheets

D. Removing internal controls from workflows

Correct Answer: B. Selecting and setting system parameters to reflect organizational rules

Question 5

What is a principal risk of a best-of-breed architecture?

A. It cannot support specialized functionality

B. It necessarily eliminates all process variation

C. It can create integration complexity and duplicated data

D. It cannot be connected to an ERP system

Correct Answer: C. It can create integration complexity and duplicated data

Question 6

Which perspective emphasizes feedback loops and unintended consequences across an organization?

A. Systems perspective

B. Purely financial perspective

C. Interface design perspective

D. Payroll perspective

Correct Answer: A. Systems perspective

Question 7

Which of the following is an example of information quality?

A. The accuracy and timeliness of inventory data

B. The color of an application icon

C. The age of a warehouse building

D. The number of office chairs

Correct Answer: A. The accuracy and timeliness of inventory data

Question 8

Why should ERP success not be measured only by whether the system went live on schedule?

A. Go-live dates are unrelated to technology

B. Technical deployment does not establish data quality, adoption, process performance, or business benefits

C. Users should never be trained before go-live

D. ERP systems do not support performance measurement

Correct Answer: B. Technical deployment does not establish data quality, adoption, process performance, or business benefits

Question 9

Which practice best supports segregation of duties in procure-to-pay?

A. Giving one user authority to requisition, receive, approve, and pay

B. Allowing shared user accounts for convenience

C. Separating requisition, purchasing, receipt, invoice approval, and payment responsibilities

D. Disabling audit logs

Correct Answer: C. Separating requisition, purchasing, receipt, invoice approval, and payment responsibilities

Question 10

What is the most appropriate approach to AI recommendations in ERP?

A. Accept every recommendation automatically

B. Use them without monitoring because ERP data is always unbiased

C. Evaluate them with quality criteria, monitoring, security controls, and human accountability

D. Avoid all analytics in enterprise systems

Correct Answer: C. Evaluate them with quality criteria, monitoring, security controls, and human accountability