Internet Sales is used by many hundreds, maybe even thousands of companies. It is mostly used in a Business-to-Business scenario. Metso´s version of Internet Sales is 4.0, and its UI is generated with JSP technology, and its core is developed with Java [18].
The history of Internet Sales and its versions is presented below [19].
SAP Internet Sales 2.0x included B2B and B2C scenarios. CRM was supported as a backend system. This occurred around the year 2000. Web-based UI was generated automatically from the CRM system with ITS FlowLogic technology.
SAP Internet Sales 3.0 became an independent J2EE-based solution. It was still using CRM as the backend system so the catalog was also located in CRM. UI technology changed to Java Server Pages (JSP), which enables more efficient customizing to the UI.
Due the fact that many customers were not willing to use CRM as the backend system, Internet Sales 4.0 enabled also using SAP R/3 as the backend system.
SAP Internet Sales 5.0 introduced newsletters and campaigns. The next version was SAP CRM Web Channel 6.0 which enabled selling complex and packed products in the telecommunications industry. SAP CRM Web Channel 7.0 in-cluded loyalty management, which means that the user receives loyalty points when he creates new orders.
After CRM Web channel 7.0, the next version, released in 2012, was WCEM 1.0 (Web Channel Experience Management), which uses SAP R/3 or CRM as the backend sys-tem. This included a totally new UI, implemented with JSF and AJAX technology [20].
Also, some architectural changes were implemented. The application was modularized differently so that the logic layer could be re-used in all kinds of hardware (mobile phones, tablets, laptops etc.). The newest version of WCEM is 3.0 when writing this.
Figure 5.9 represents the architecture of WCEM 3.0, which is running on the same Web Application Server Java as Internet Sales 4.0. The biggest difference in an architectural sense compared to Internet Sales 4.0 is the use of MDM (Master Data Management) and SAP PI. MDM has the same role as TREx. It contains the products which will be shown to the user. MDM can also hold pictures of the product. MDM is faster than TREx and it provides a better browsing experience than TREx for the products in the catalog [19].
Product data is loaded from SAP R/3 into MDM using ALE Idocs and with SAP PI act-ing as a message hub between SAP R/3 and MDM [19]. ALE supports communication interfaces that allow connections from the SAP R/3 system to non-SAP systems. Idoc is
specified format, which is exchanged between two systems, which know how to inter-pret that data. ALE transfers Idocs. [21]
In Figure 5.9, MDM is located on the same server as WCEM, but it could be located on a separate server also. The architecture presented in Figure 5.9 is clearly a major change when compared to Metso´s current architecture. It requires several more components and servers – MDM and SAP PI. This requires effort and may require major monetary investments.
Figure 5.9: Architecture in WCEM 3.0 with the use of MDM.
There is also a possibility to install WCEM using TREx, as shown in Figure 5.10. This kind of WCEM 3.0 implementation involves the smallest monetary cost of the WCEM installations. Architecture presented in Figure 5.10 includes TREx which means that migrating to WCEM from Internet Sales 4.0 would be easier. This kind of set-up offers the benefits in better user experience in the user interface and the new features that WCEM offers.
Figure 5.10: Architecture in WCEM 3.0 with the use of TREx.
SAP AG has increased their efforts in developing web shop solutions containing good usability. Current SAP AG´s web technology trends seem to be towards HTML5, AJAX, and JSF. Also, one remarkable trend is SAP AG´s effort to develop not only browser applications, but also mobile applications.
WCEM 3.0 includes a lot of new functionalities which are not described in this thesis.
One example would be that in WCEM 3.0 the user is able to download orders in XML format and upload products in CSV format [22]. This speeds up the ordering process if there are many products in one order. Another example is that WCEM 3.0 contains probably better performance in the browser-side because it utilizes the latest technology.
Metso´s current Internet Sales 4.0 is not easy to use with mobile phones, so in that sense WCEM could be worth implementing, depending on what kinds of needs the end users have.
6 CONCLUSIONS
Metso´s Internet Sales solution consists of several components and concepts. Every component and concept has its justified role. This thesis provided the description of Internet Sales and its main concepts. Also, the overall architecture of Internet Sales and IPC was introduced.
It will be interesting to follow the development of SAP AG´s new web shop products.
The SAP R/3 system sets some limitations to the web shop – sales organizations, cus-tomers and, users must be linked to SAP R/3 models of them. In the future there proba-bly will not be any major changes to the key concepts of the new web shops, because the backend system restricts the data model. One might guess that only web technology changes and perhaps some minor architectural changes will occur in the future. WCEM 3.0 supports this assumption.
This thesis also shows that the architecture of Internet Sales is not perfect, but it is good enough to process daily transactions. More optimized architecture would be having only one backend system for all queries. Currently Internet Sales retrieves its data from the TREx database and the SAP R/3 system. Having many backend systems makes the sys-tems potentially inconsistent because they depend on each other.
The new products offered by SAP AG will offer technology for a multichannel solution, where the web shop could be accessed with different devices, like mobile phones, tab-lets and laptops. Metso´s current Internet Sales implementation does not support mobile devices so well. The mobile market is growing and perhaps Metso will consider updat-ing its web shop technology in the future. Currently, Internet Sales is up and runnupdat-ing, and it is successfully used all around the world.
BIBLIOGRAPHY
[1] Leon, A. 2007. Enterprise Resource Planning. Tata McGraw-Hill Education.
[2] Gupta, M., & Kohli, A. 2006. Enterprise resource planning systems and its implica-tions for operaimplica-tions function. Technovation 26.5. Pages 687-696.
[3] Kogent Learning Solutions. 2010. SAP ABAP questions and answers. Jones & Bart-lett Learning.
[4] Kogent Learning Solutions. 2011. SAP SD Handbook - An Overview of SAP Sales and Distribution. Jones & Bartlett Learning.
[5] Singh, A., & Wesson, J. 2009. Evaluation criteria for assessing the usability of ERP systems. In Proceedings of the 2009 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists. Pages 87-95.
[6] Kogent Learning Solutions. 2011. SAP R/3 Handbook 3rd edition. Jones & Bartlett Learning.
[9] Sincock, A. 2003. Enterprise Java for SAP. Apress.
[10] SAP Web Application Server with ABAP and Java
http://help.sap.com/saphelp_nw04/helpdata/en/53/97583c2439e66fe10000000a114084/
McGraw-Hill Osborne Media.
[14] O'Leary, D. 2000. Enterprise resource planning systems: systems, life cycle, elec-tronic commerce, and risk. Cambridge University Press.
[15] Organizational Structure: Corporate Group
http://help.sap.com/saphelp_470/helpdata/en/12/0841c9470311d1894a0000e8323352/c ontent.htm. Accessed 2.1.2013.
[16] Company code
http://help.sap.com/saphelp_erp60_sp/helpdata/en/e5/077a494acd11d182b90000e829fb fe/content.htm. Accessed 2.1.2013.
[17] Variant Configuration (LO-VC).
http://help.sap.com/printdocu/core/print46c/en/data/pdf/LOVC/LOVC.pdf. Accessed 3.1.2013.
[18] SAP E-Commerce 7.0 – Landscape, Basics and Concepts. 2008. SAP AG.
[19] Evolution of SAP´s E-Commerce solutions.
http://scn.sap.com/community/crm/web-channel/blog/2012/04/20/evolution-of-saps-ecommerce-solutions. Accessed 2.3.2013.
[20] Web Channel Experience Management - Advantage of using Java Server Faces http://scn.sap.com/community/crm/web-channel/blog/2012/05/18/web-channel-experience-management--jsf-adoption. Accessed 21.3.2013.
[21] What is EDI ,ALE and iDOC?
http://www.saptraininghub.com/what-is-edi-ale-and-idoc/ Accessed 20.3.2013.
[22] Web Channel Experience Management - What's New in Release 3.0?
http://help.sap.com/saphelp_wec300/helpdata/en/a9/7dfb1d25a5464eaeb354f7c4fe0add/
content.htm. Accessed 21.3.2013.