ERP and Technology BDT - Lecture Style Format Sample

LEARNING OUTCOMES Describe the typical techniques of ERP management systems Define the functions of the typical techniques Describe steps and process of ERP Implementation BDT - Lecture Style Format Sample

CORE AND EXTENDED ERP COMPONENTS Core ERP component – traditional components included in most ERP systems and they primarily focus on internal operations Extended ERP component – extra components that meet the organizational needs not covered by the core components and primarily focus on external operations BDT - Lecture Style Format Sample

CORE AND EXTENDED ERP COMPONENTS BDT - Lecture Style Format Sample

CORE ERP COMPONENTS Three most common core ERP components Accounting and finance Production and materials management Human resource BDT - Lecture Style Format Sample

Accounting and Finance ERP Components Accounting and finance ERP component – manages accounting data and financial processes within the enterprise with functions such as general ledger, accounts payable, accounts receivable, budgeting, and asset management BDT - Lecture Style Format Sample

ERP VENDOR OVERVIEW SAP boasts 20,000 installations and 10 million users worldwide ERP solutions are growing because: ERP is a logical solution to the mess of incompatible applications that had sprung up in most businesses ERP addresses the need for global information sharing and reporting ERP is used to avoid the pain and expense of fixing legacy systems BDT - Lecture Style Format Sample

SAP User Interface The SAP R/3 system presents a Windows interface with several of the familiar Windows functions for screen manipulation. The apparent simplicity of the interface hides the power of the menus residing within the menu bar at the top of the screen. The initial screen shows a menu bar with the following selections BDT - Lecture Style Format Sample

SAP User Interface BDT - Lecture Style Format Sample

SAP User Interface The first level sub menus are listed below Office Workplace Telephone Integration Appointment Calendar Room Reservations Start Workflow Business Documents. BDT - Lecture Style Format Sample

SAP User Interface Logistics Materials Management Sales/distribution Logistics Execution Production Production-process Plant Maintenance Customer Service Quality Management Logis. controlling Project Management Environment Health & Safety Central Functions BDT - Lecture Style Format Sample

SAP User Interface Accounting Financial Accounting Treasury Controlling Enterprise Control Investmt Mgt. Project management Real Estate BDT - Lecture Style Format Sample

SAP User Interface Human Resources Managers Desktop Personnel admin. Time management Payroll Training and Event Management Organizational Management Travel Information system BDT - Lecture Style Format Sample

SAP User Interface Information Systems Executive Information Systems Logistics Accounting Human Resources Project System Ad Hoc Reports General Report System BDT - Lecture Style Format Sample

SAP User Interface Tools ABAP/4 Workbench Accelerated SAP Administration ALE Business Communication Business Documents Business Framework Business Workflow CCMS Web Development SAPScript Hypertext Find BDT - Lecture Style Format Sample

Quote-to-Cash

Requisition-to-Pay

Customer relations management

Partner Relations Management

Performance Analysis

Web Store

Client Server Architecture Client Server is a computing model in which the application processing load is distributed between a client computer and a server computer, which share information over a network. Typically the client is a PC running front end software that knows how to communicate with the server SAP : SAP gui ->R3->DB

Behind Client Server Processing can be improved because client and server share processing loads. Client - server computing says that the client has computing power that is not being used Fundamental idea is to break apart an application into components that can run on different platforms. Thin vs. Fat Clients A thin client has most of the functionality with server A fat client has most of the functionality with the client.

Three Tiered Architecture Three Tiered Architecture is an information model with distinct pieces -- client, applications services and data sources -- that can be distributed across a network Client Tier -- The user component displays information, processes, graphics, communications, keyboard input and local applications

Three Tiered Architecture Applications Service Tier -- A set of sharable multitasking components that interact with clients and the data tier. It provides the controlled view of the underlying data sources. Data Source Tier -- One or more sources of data such as mainframes, servers, databases, data warehouses, legacy applications etc.

Internet Computing Architecture Application 2 Tier X Database Application Server Application Browser Java Move from 2 tier two three tier architecture. Simplified Deployment Other advantages of this architecture become apparent when we look at application deployment. In client server environments, you would need to install the application on each desktop. If you add new users, you need to install the application. If you want to upgrade.... you need to install the application. If we’ve learned one thing from Y2K compliance, it’s that upgrading 100’s or 1000’s of desktops is a challenge best avoided. The true, three-tier architecture avoids this pitfall. By storing the application on the middle tier, the ICA requires you to upgrade only the servers. Clients upgrade themselves. As soon as the browser detects that a new application version exists, it’s downloaded automatically. Even some “web” tools use plug ins that load windows components as opposed to IC architecture. These can be as difficult to uninstall as typical windows applications. 3 Tier BDT - Lecture Style Format Sample

Networks LANs, WANs, Intranets, Extranets Bandwidth Standards Security Network Transmission Capability Standards TCP/IP Security E.g., Encryption

Databases and Data Warehouses Databases -- Numerous approaches including relational databases Relational DB is a set of related files that reference each other ERP are built on relational DBs and data source in three tier is typically relational Data warehouse is a DB for decision making, not transaction processing

Sales Order # Customer # Salesperson # ... Customer # Customer ... Lastname Salesperson # Last- ... name Sales Order # Customer # Salesperson # ... 0001 0001 0001 0001 O’Leary 0001 Jones

Software ERP have been developed for different operating systems UNIX, Windows Server, Linux, … MaC? Legacy Software Informally … software that has been in the company for a while. Generally, developed in house

Package Software In the same sense that personal computing software has moved toward a standard set of package options, corporate enterprise computing has also moved toward packages Package software is changing the nature of accounting, finance and IT departments No longer a matter of programming from scratch, instead need to understand processes

Outsourcing VS In-House Big players SAP (mySAP, R/3) Oracle (Business Suite) Baan PeopleSoft “As Is” vs. “To Be”

Implementation Strategies Process Mapping Generating process flows using the reference models as input tailored to project requirements System Implementation Customization and optimization of software Select Application SW link software applications that fulfill business process requirements Selected Business Processes Inventory of COTS software Selected matching selected processes e.g. Supply Chain Personnel Finance E-Commerce Manufacturing Distribution Sales Force Auto. Baseline SW for

Implementation Steps Project Preparation – implementation strategy, project team, system landscape, technical requirements, vendor selection Business Blueprint and Realization – technical design, development system, testing, production system installation Source: Accelerated SAP (ASAP) Method

Implementation Steps Final Preparation – operational system, data transfer, testing, help desk Go Live and Support – process monitoring, operational help desk, definition long-term release strategy

Ir. Ekananta Manalif, MM, MKom Resources Ir. Ekananta Manalif, MM, MKom Jurusan Sistem Informasi Universitas Bina Nusantara IRMC of National Defense University Daniel E. O’Leary University of Southern California www.richardbyrom.com