 and welcome to this session in which we would look at the enterprise resource planning architecture. In the prior session we looked at what is an ERP system, what is an enterprise risk planning. So if you need to know what is ERP please look at the prior session and this session will focus on the architecture of an ERP system. There are two types of architecture for an ERP system or at least this is what's available now. So what is an architectural system for an ERP? Well it referred to the overall design and structure. Basically how is the ERP system designed? How is the software designed? It includes hardware, software, network component that make up that system and we have two types we have a client server and we have service oriented architecture. In this session I'm going to explain what a client server is it's usually called the three layer and I'm going to explain what a service oriented ERP is. Before we proceed any further I have a public announcement about my company farhatlectures.com. Farhat accounting lectures is a supplemental educational tool that's going to help you with your CPA exam preparation as well as your accounting courses. My CPA material is aligned with your CPA review course such as Becker, Roger, Wiley, Gleam, Miles. My accounting courses are aligned with your accounting courses broken down by chapter and topics. My resources consist of lectures, multiple choice questions, true false questions as well as exercises. Go ahead start your free trial today no obligation no credit card required. Let's start with the client server part one the architecture of an ERP typically include several layers usually three and those are the user interface now what is the user interface think about user interface one I am using right now a laptop I'm looking at my screen this is my user interface this is what I'm interfacing with with so those are the user interface simply put the user interface are you are utilized or used by the employees of the company or by customers for example you would log in through your user interface your laptop your desktop your iPad your tablet your iPhone to input an order this is what called a user interface and you'll put the order within the application of an ERP so this is one component of the ERP I don't mean component different business component one component means one part one piece of the ERP which is called the user interface and this is what you usually you and I as users see when we are dealing with an ERP system I'm pretty sure if you place an order of at Amazon when you look at the screen those are user interface and I'm going to talk a little bit more about them the second layer is called the business logic and the second layer would involve hardware CPUs things that's going to be processing think of it as the brain of the system basically the computer software that's running the logic it's called the business logic this is the second layer and the third layer it's called the data storage layer and this is the data storage layer and this is what I said it's a three layer one two and three now let's talk a little bit more in the tales about each layer separately starting with the user interface what is it the user interface provides the means the the way for users to interact with the system what could be a good example customer inputting the sales order on the website through an application server as again as I said it could be a tablet a phone so on and so forth and usually we have what's called graphical user interface going some of these systems are really nice and that makes a difference in the real world because most ERPs now are web-based so you want to look good this is your face to the customer and this is an important component of the ERP system even from a design perspective think about when you log in at a website does it look good when you place an order is it easy to use do the color matches so on and so forth then we have as I said the second layer is the business logic layers that contain the rules and the processes basically the application the software that's running the system that govern the system operation so keep on going with this example the customer input the sales order now the system create a sales order send it to the warehouse for shipping the shipping will send it to packaging they will ship it they will build the customer and what they would receive the payment so all of this all these steps are happening here the system is processing now they're not going they're not taking place all at the same time but the point is once you input the data then gets processed at this level and the third level we set the data the data storage does what it stores the data it stores the data in different places easy to use stored well connected with other applications so on and so forth now you could have many databases but all integrated organized and what this is a system like this what it what does it do because all integrated remember ERP is integrated it can scale the business so even though you are growing larger you are adding more services you need more for example now you accept the cryptocurrencies which is I don't care about cryptocurrencies and any RP you can have an application for that that's integrated with everything that's the whole purpose of an ERP system we could also have a ERP system in the cloud so the only thing at the at the client or at the company is the user interface and everything else these operation the engine and the database is on the cloud and we'll talk about the cloud application later on because we have to learn about cloud application so this is the client server part one in part two which is client server and once you understand what a client server is what does it look like for an ERP you have a good idea about the traditional ERP system when we say traditional it's not that old but now what we have is service oriented ERP which is basically mostly web based services the service oriented architecture or SOA is a design approach that organizes an ERP into a collection of independent modular services hold on a second didn't we aren't we going away that's the whole purpose of ERP is to stay away from independent modular services yes but those new independent modular services they can be easily combined into new functionality so this approach allow flexibility and scalability because they can be integrated real easily although they're independent but they're easily integrated and scalable so different services will be responsible for specific function function for example you can have one for data storage even within the system itself business logic and user interface but they are integrated they are integrated for example service responsible for managing inventory could be integrated with the service responsible for managing customer to create a new service that manages inventory and customer together so they're easily integratable so I'm not saying we're going back to independent functions but what I'm trying to say is the ERP system itself yes it is one system but but with the SOA the service oriented architect it can be broken down into small component so this allow better integration with other systems and technologies such as cloud services mobile services and over the internet thing especially over the internet everything now is over the internet so by breaking the system down into a collection of services you can easily now and be integrated with system and technology which could which could improve functionality and performance of the system now you could add any system you want to maybe have a better system that could integrate with your system real easily then you choose that better system and use it and this is what a service oriented ERP is what should you do now go to far hat lectures review mcqs that's going to help you either on your cpa exam cisa cma or if you're taking an accounting information system course good luck everyone study hard good luck and of course stay safe invest in your career