Chapter 15 - ERP systems and e-commerce: Intra- and inter-enterprise modeling. One objective of this chapter is to compare the REA enterprise ontology with current developments in enterprise resource planning (ERP) systems and electronic commerce (e-commerce) in the context of the types of integration introduced in Chapter 1. The prospects for progress in using the REA enterprise ontology as a foundation for intra-enterprise systems (similar to ERP systems) and for inter-enterprise systems needed for seamless e-commerce are discussed. | Chapter 15 ERP Systems and E-Commerce: Intra- and Inter-Enterprise Modeling Chapter Learning Objectives Compare the goals of current enterprise resource planning (ERP) systems with those of the REA enterprise ontology Describe the needs for intra-enterprise and inter-enterprise system integration Identify information integration tools commonly used in practice (. electronic data interchange, extensible markup language, enterprise application integration software, and electronic business extensible markup language) for intra-enterprise and inter-enterprise information systems Discuss strengths and weaknesses of integration tools commonly used in practice for meeting intra-enterprise and inter-enterprise information integration needs Discuss strengths and weaknesses of the REA enterprise ontology as a foundation for meeting intra-enterprise and inter-enterprise information integration needs 15- Intra-Enterprise Systems: ERP and the REA Enterprise Ontology Enterprise Resource Planning (ERP) Systems Groups of software applications integrated to form enterprise-wide information systems SAP, Peoplesoft, and Oracle Applications are the top three ERP vendors Began as back-office applications Seen and used only by people within enterprises Bolt-on applications have allowed expansion to front office use Bolt-on applications are software programs that can be added to existing ERP applications Front-office systems are seen and interacted with by external partners such as customers and suppliers 15- Goals and Methods of ERP Software and the REA Enterprise Ontology Database Orientation Data must be stored at their most primitive levels, at least for a defined time period Data must be stored only once, in a way that all authorized decision makers can access the data Data must be stored to allow retrieval in various formats as needed for different purposes REA mandates database orientation Some ERP systems meet database orientation Some store the same information . | Chapter 15 ERP Systems and E-Commerce: Intra- and Inter-Enterprise Modeling Chapter Learning Objectives Compare the goals of current enterprise resource planning (ERP) systems with those of the REA enterprise ontology Describe the needs for intra-enterprise and inter-enterprise system integration Identify information integration tools commonly used in practice (. electronic data interchange, extensible markup language, enterprise application integration software, and electronic business extensible markup language) for intra-enterprise and inter-enterprise information systems Discuss strengths and weaknesses of integration tools commonly used in practice for meeting intra-enterprise and inter-enterprise information integration needs Discuss strengths and weaknesses of the REA enterprise ontology as a foundation for meeting intra-enterprise and inter-enterprise information integration needs 15- Intra-Enterprise Systems: ERP and the REA Enterprise Ontology Enterprise Resource .
