This thesis deals with the analysis and design of business intelligence solution for the needs of reporting for Microsoft Dynamics AX 2012 platform. Solution includes development guidelines for possible development in future. In the first part of the thesis there is introduced ERP system MS Dynamics AX 2012 which serves as a data source for reports. The following sections analyze the data sources and the need for enterprise reporting. Significant part of thesis is the analysis and design of individual basic dimensions and indicators together with the proposal of data flows and architecture solution. In chapters 6-9 are described best practices for creating data warehouse through all the layers of development. In chapter 10 are unified guidelines for the development of different parts of solution such as dimensional OLAP cubes for case of additional customer requirements.

This diploma thesis analyzes the information system of FCC Environment CEE and is focused on a detection of risks and other imperfections of the system. The result of the thesis should be a proposal for a change which may lead to an improvement of the entire system and eventually to elimination of the discovered risks.

Historically, system integration of ERP system and other existing IT systems within anorganization has always been a complex challenge, both technically and organizationally. Inmany cases, the budget for system integration corresponds 30-40% of the whole IT budget.Since system integration accounts for a large part of the cost during acquisitions andimplementation of an ERP system, companies are interested in the challenges that exist duringsystem integration, to simplify the integration process and hence reduce the costs. Tounderstand the challenges, a case study at Company X has been performed. The ERP systeminvestigated in the case study is Microsoft Dynamics AX.The purpose with this study is to investigate challenges that exist in large organizations duringsystem integration of ERP system and other IT systems that exist in the organization andthereby understand how integration can be developed in a more efficient way.The study entails an extensive literature study and two rounds of data collection throughqualitative interviews.The results showed that the challenges that exist at Company X are mainly organizational.Technical challenges coexist but they have a much less significant impact than theorganizational challenges. This can be explained by that there has been a heavier focus onsolving the technical related problems and maybe to some extent neglected the impactorganizational problems can have on system integration. Possible actions includes centralstrategy concerning how to work with Dynamics AX, it’s growth and future initiatives,policies and framework regarding working methods, increased authority and decision rights tothe group working with AX as well as minimize customizations and own development.

Examensarbetet undersöker den nya versionen av affärssystemet Microsoft Dynamics AX R2 2012 och dess plattform Commerce Runtime och analyserar dessa ur perspektiven arkitektur och kommunikationsmöjligheter. Examensarbetet undersöker systemets arkitektur och implementerar tre metoder för att visa upp kommunikationen mellan komponenterna i systemet. Undersökningen avgränsar sig dock till de områden av systemet och plattformen som har med butikslösningen att göra. Undersökningen går hand i hand med implementationen. Implementeringen sker löpande under arbetet för att säkerställa att undersökningen stämmer. Rapporten beskriver tre olika kommunikationsmetoder. Synch Service synkroniserar Dynamics AX databas med Commerce Runtime databas med hjälp av Dynamics AX användargränssnitt. SQL-adapter används för att hämta den synkroniserade datan i Commerce Runtime databas. Real-Time Service anropar exponerade metoder i Dynamics AX från en extern klient. Utifrån utvärderingen så lämpar sig Synch Service bra till när mycket information ska uppdateras rutinmässigt. Real-Time Service lämpar sig när data ska hanteras på ett antal bestämda sätt och då beräkningar av data ska genomföras och lämna tillbaka ett svar som genererats dynamiskt. / The thesis examines the new version of the Enterprise Resource Planning system, Microsoft Dynamics AX R2 2012, along with its platform Commerce Runtime and analyze them from the perspectives of architecture and communication possibilities. The thesis is looking into the system architecture and implements three methods to demonstrate the communication between the system components. The study of the system architecture is limited to the areas of the system and platform that are connected to the Retail solution.The study goes hand in hand with the implementation. The implementation is being done alongside the study to ensure its correctness. The report describes three different methods of communication. Synch Service synchronizes the Dynamics AX database with the Commerce Runtime database. SQL-adapter is used to retrieve the synchronized data from the Commerce Runtime database. Real-Time Service calls the exposed methods in Dynamics AX from an external client. Based on the evaluation; Synch Service is useful when a lot of data is being updated routinely. Real-Time Service is useful when data is to be handled in a number of specific ways and when calculations of data are needed to return a dynamically generated response.

In recent years, Business Intelligence is one of the fastest growing software industry according to foreign analyzes. More and more companies realize the importance of tools for Business Intelligence and dashboarding. That is why I chose this topic for my thesis. The main part of this thesis focuses on study support for subject 4IT314 Enterprise Information Systems. This course teaches student how to work with the ERP system Microsoft Dynamics AX. The main shortage of this subject is the lack of feedback to students. Therefore it was decide to integrate BI tools that will be used for dashboarding over database of Microsoft Dynamics AX. In the theoretical part are explains the basic terms essential to understanding BI and dashboarding. On the basis of defined criteria was chose BI tool for integration in to the subject 4IT314. In the practical part of this thesis is described the implementation of this tool and created user documentation, which is used as study materials for students.

Utvecklingen inom informationssystem har lett till att allt fler verksamhet villdigitalisera deras arbetsprocesser. Det växande mobila användandet av EnterpriseResource Planning (ERP) på enheter såsom smartphones, tablets och handdatorer harlett till att verksamheter ställer större krav på sina system och leverantörer av dessa.Framtidens ERPsystemmåste fungera mobilt och underlätta arbetet för de anställdaistället för att vara ännu ett ITsystemsom ska lösa organisationens alla utmaningar.Denna fallstudie är gjord hos en grossistverksamhet i Skåne som var mitt iimplementationen av sitt ERPsystem,Microsoft Dynamics. Denna studie harundersökt hur arbetet med verksamhetens affärsprocesser såg ut före och underimplementationen av det nya systemet. Bakgrunden till fallstudien var att undersökaom det fanns korrelation mellan hur väl affärsprocesserna var evaluerade, anpassadeoch hur vällyckad verksamhetens ERPimplementationblev. Fallstudien villundersöka hur processmodellering och Business Process Management (BPM) kanstödja denna slags implementation av mobila ERPsystem.Verksamheten i studien är ett mellanstort säljochdistributionsföretag med kontor på4 svenska orter. Verksamheten påbörjade 2015 en digitalisering av helaorganisationen. ITsystemeti bestod då av flera olika system som anpassats underlängre tid för att integrera med varandra och dela information precis efterorganisationens önskan. Som en del av implementationen valde de att använda ettBusiness Process Modeling verktyg för att introducera och träna användarna avprocesserna i det nya systemet. Implementationsfasen i projektet började i februari2017 och i februari 2019 har verksamheten fortfarande inte fastställt ett Golivedatum.. Medeltiden för en ERPimplementationär 17,4 månader [5]. Då verksamhetenGolivedatum har flyttats räknas det nu som att verksamhetens implementation ärförsenade och över medeltiden.Arbetet med processerna före själva projektstart uppfattas som bristfälligt utifrån BPMdras slutsatsen att förseningen av “Go livedatumet”delvis beror det på att företagetoch organisationen inte har analyserat sina egna processer och har förlitat sig förmycket på att konsultbolaget och RapidValue BPM skulle sköta inlärning ochimplementationen. / The development in information systems has led to an increasing number ofbusinesses wishing to digitize their work processes. The growing mobile use ofEnterprise Resource Planning (ERP) systems on devices such as smartphones andtablets has led businesses to place greater demands on their information systems andsuppliers of these. ERP system in the future must be able to function mobile andfacilitate the work for the employees instead of being another IT system that will solvethe organisation's all challenges.This case study was made at a wholesale company in Skåne, which was in the midstof an ERP implementation with Microsoft Dynamics. This study has investigated howthe work with business processes looked before and during the implementation of thenew system. The background to the case study was to investigate whether there wereany correlation between how well the business processes were evaluated, adapted andhow successful the business's ERP implementation was. The case study aims toinvestigate how process modeling and Business Process Management (BPM) cansupport this kind of implementation of mobile ERP systems.The activity in the study is a mediumsizedsales and distribution company withoffices in 4 Swedish locations. In 2015, the business began digitizing the entireorganization. The IT system consisted of several different systems that had beenadapted over time to fit the needs of the organisation. As part of the implementation,they chose to use a Business Process Modeling tool to introduce the system and trainthe users of the processes in the new system. The implementation phase of the projectbegan in February 2017 and in February 2019 the business still has not set a Golivedate. The average time for an ERP implementation is 17.4 months [5]. Since theGolivedate business has been moved, it is now considered that the operation'simplementation is delayed and over the average time.The work on the processes before the actual start of the project is perceived asinadequate from BPM, the conclusion is drawn that the delay of the "Go live date" ispartly due to the fact that the company and the organization have not analyzed theirown processes and have relied too much on the consulting company and RapidValueBPM to handle learning and implementation.