Editing Enterprise resource planning (section)

==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 asset]]s, [[Accounts payable|payables]] including vouchering, matching and payment, [[Accounts receivable|receivables]] and collections, [[cash management]], [[Consolidation (business)|financial consolidation]]
* [[Management accounting]]: [[budgeting]], costing, [[cost management]], [[activity based costing]], billing, invoicing (optional)
* [[Human resources]]: [[Recruitment|recruiting]], [[training]], [[Schedule (workplace)|rostering]], [[payroll]], [[Employee benefit|benefits]], [[Pension|retirement and pension plans]], [[Diversity (business)|diversity management]], [[retirement]], [[Employee exit management|separation]]
* Manufacturing: [[engineering]], [[bill of materials]], work orders, [[scheduling]], [[capacity utilization|capacity]], [[workflow management system|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, [[Order picking|picking]] and [[Packaging and labeling|packing]])
* [[Project management]]: project planning, resource planning, project costing, [[work breakdown structure]], [[Invoice|billing]], time and expense, performance units, activity management
* Customer relationship management (CRM): sales and marketing, commissions, service, customer contact, [[call center]] support{{snd}}CRM systems are not always considered part of ERP systems but rather [[business support system]]s (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|Contract Management]]: creating, monitoring, and managing [[contract]]s, reducing administrative burdens and minimising [[legal risk]]s. These modules often feature contract templates, [[electronic signature]] capabilities, automated alerts for contract milestones, and advanced search functionality.

=== GRP – ERP use in government ===
Government resource planning (GRP) is the equivalent of an ERP for the [[public sector]] and an integrated office automation system for government bodies.<ref>{{Cite book |doi=10.1109/ICNDC.2010.42 |chapter=Design of E-Government Information Management Platform Based on SOA Framework |title=2010 First International Conference on Networking and Distributed Computing |year=2010 |last1=Yunliang |first1=Jiang |last2=Xiongtao |first2=Zhang |last3=Qing |first3=Shen |last4=Jing |first4=Fan |last5=Ning |first5=Zheng |pages=165–169 |isbn=978-1-4244-8382-2 |s2cid=17798379 }}</ref> The software structure, modularization, core algorithms and main interfaces do not differ from other ERPs, and ERP software suppliers manage to adapt their systems to government agencies.<ref>Allen, Kern and Havenhand (2000) "ERP Critical Success Factors: an exploration of the contextual factors in public sector institutions", Proceedings of the 35th Hawaii International Conference on System Sciences.</ref><ref>Chang, Gable, Smythe and Timbrell (2000) "A Delphi examination of public sector ERP implementation issues" Proceedings of ICIS.</ref><ref>{{cite journal | last1 = Ebrahim | first1 = Zakareya | last2 = Irani | first2 = Zahir | year = 2005 | title = E-government adoption: architecture and barriers | journal = Business Process Management Journal | volume =  11| issue = 5| pages =  589–611| doi = 10.1108/14637150510619902 | citeseerx =10.1.1.453.87}}</ref>

Both system implementations, in private and public organizations, are adopted to improve productivity and overall business performance in organizations, but comparisons (private vs. public) of implementations shows that the main factors influencing ERP implementation success in the public sector are cultural.<ref>Wingreen, Maryam  and Hritik (2014) "An Investigation into Enterprise Resource Planning Implementation Success: Evidence from Private and Public Sector Organizations", [http://aisel.aisnet.org/pacis2014/339 PACIS 2014/339].</ref><ref>{{cite arXiv | eprint=1207.2860 | author1=Shafqat Ali Shad | last2=Chen | first2=Enhong | author3=Faisal Malik Faisal Azeem | title=Enterprise Resource Planning - Real blessing or a Blessing in Disguise : An Exploration of the Contextual Factors in Public Sector | year=2012 | class=cs.CY }}</ref><ref>{{cite book | last1 = Coelho | first1 = Cunha | last2 = Meirelles | title = Proceedings of the 16th Annual International Conference on Digital Government Research | chapter = The client-consultant relationship in the implementation of ERP in government: Exploring the dynamic between power and knowledge | year = 2015 | page = 140 | doi = 10.1145/2757401.2757405 | isbn = 9781450336000 | s2cid = 13941079 }}</ref>