This paper examines Enterprise Resource Planning (ERP) and Material Requirements Planning (MRP) systems, comparing their scope, functionality, and practical application in organizational settings. It outlines the foundational characteristics of ERP as an enterprise-wide software solution and contrasts it with MRP's more limited, manufacturing-focused approach. The paper explores key differences in push versus pull production philosophies, data integrity requirements, inventory management, and implementation considerations. It also discusses how ERP systems support regulatory compliance frameworks such as IFRS, Sarbanes-Oxley, and Basel II, and how MRP systems have evolved over time to incorporate broader business processes.
An Enterprise Resource Planning (ERP) system refers to a system formulated for enterprise-wide resource management. ERP has a wide scope; previously it was confined to the manufacturing environment, but the domain of ERP is now based upon the fundamental operations of an organization, and its relevance is irrespective of the nature of activity practiced by that organization. ERP is practiced and conducted by "business, non-profit organizations, nongovernmental organizations, governments, and other large entities" (Thomas, 2002). A software package is required for the timely execution of the ERP system; this package must provide full functionality in a single solution, and from a technical perspective it should incorporate features relevant to payroll and accounting functions. The use of external interfaces is not required for ERP implementation, which has produced improved characteristics through standardization and lower maintenance costs (Thomas, 2002).
A key limitation of the Material Requirements Planning (MRP) system has been its dependence on data coherency. Flaws present in inventory data, the bill of materials, or the master production schedule will be reflected directly in the output. To avoid such failures, vendors adopting MRP demand a minimum of 96% data integrity. The MRP system also requires the user to identify the time it will take to establish production in a factory from the ordered component parts. MRP further assumes this establishment period as lead time, which carries the same quantitative significance for every item regardless of the quantity produced or the number of simultaneous operations conducted within the factory (Thomas, 2002).
In comparison, the ERP system has been able to organize inventory effectively and succeeds in identifying the requirements of individual factory units. The system further ensures that a medium of communication exists between factory units so that redistribution of components is achievable, which correspondingly serves "the overall enterprise" (Thomas, 2002). The MRP system requires that corresponding systems remain intact, effective, and efficient; it is expected to fail if it handles variety reduction and engineering in a manner that undermines product availability.
The push system is considered to be a system based on demand factors — that is, customer orders within both present and future scope. Under this approach, the demand factor is taken into account as the basis for material and capacity planning. MRP is based upon a similar methodology, in which parallel systems such as Just-in-Time (JIT) and Kanban are also exercised. The pull system, by contrast, is based upon the philosophy of a made-to-order situation, where the flow of material moves in a direction reverse to the flow of documents and other formalities. Real demand — that is, received orders — is taken into account under the pull system, whereas MRP is based upon the concept of expected orders.
"ERP implementation complexity and regulatory compliance"
"MRP's historical development and persistent weaknesses"
You’re 56% through this paper. Sign up to read the remaining 2 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.