Notes1
- 1. SAP Overview
- 2. SAP? • Company • ERP Software package – R/2 – R/3
- 3. Why ERP • Integration • Best business practices • Standardization
- 4. Why not ERP? • Complexity • Cost • Inflexibility
- 5. SAP R/3 System Business Modules Logistical Sales & Distribution Financial Accounting Financial Materials Mgmt. Controlling Production Fixed Assets Planning Mgmt. R/3 Client / Server Quality Mgmt. ABAP/4 Project System Plant Maintenance Workflow Human Industry Resources Solutions
- 6. R/3 System: Hardware/Software Views
- 7. Typical Client Server Architectures Presentation Application Database Central System Two - tier Distributed System Two - tier Client/Server Three - tier Client/Server Multi-layer Cooperative Client/Server
- 8. R/3 System Configurations SAP Central System 2-Tier Configuration 3-Tier Configuration Web-enabled Presentation Presentation Internet Transaction Service/Web Application Service Database, Application, Database and Database Presentation Application In a central R/3 System configuration, one host is responsible for all processing tasks.
- 9. R/3 System Configurations SAP Central Systems 2-Tier Configuration 3-Tier Configuration Web-enabled Presentation Presentation Internet Transaction Service/Web Application Service Database, Application, Database and Database Presentation Application Two‑ tier R/3 System configurations are usually implemented using special presentation servers that are responsible solely for formatting the graphical interface. Many R/3 System users use PCs with Microsoft Windows ‑installed, for example, as presentation servers.
- 10. R/3 System Configurations SAP Central Systems 2-Tier Configuration 3-Tier Configuration Web-enabled Presentation Presentation Internet Transaction Service/Web Application Service Database, Application, Database and Database Presentation Application An alternative two‑tier configuration is to install powerful desktop systems and to use these for presentation and applications (two‑tier client/server). This type of configuration is particularly useful for expensive applications (such as simulations) or for software developers.
- 11. R/3 System Configurations SAP Central Systems 2-Tier Configuration 3-Tier Configuration Web-enabled Presentation Presentation Internet Transaction Service/Web Application Service Database, Application, Database and Database Presentation Application In a three‑ tier configuration, you use your own host for the three tiers. Using data from the database server, several different application servers can operate at the same time. To ensure that the load on individual servers is as even as possible and to achieve optimal performance, you can use special application servers for individual application areas such as sales planning, distribution or financial accounting.
- 12. R/3 System Configurations SAP Central Systems 2-Tier Configuration 3-Tier Configuration Web-enabled Presentation Presentation Internet Transaction Service/Web Application Service Database, Application, Database and Database Presentation Application To web‑ enable the SAP Applications, a Web Server and an ITS (Internet Transaction Server) are needed. The web‑service and the services for the ITS can run on one server or on two dedicated servers. The presentation in this configuration is provided by an Internet Browser. The new SAP Web platform is NetWeaver.
- 13. Basis System: Three-Tier Computer Hierarchy Central Database (Storage of all data) Access to Dataase: (Read / Write data) Database Input / Output of data to users Processing of data Application using application logic Presentation of the processed data to Presentation the user
- 14. Client/Server Overview Server LAN/WAN TCP / IP Client
- 15. Client/Server Overview (Logical Structure) Server Data Storage Application Logic Client Presentation
- 16. What does an R/3 Database Contain? R/3 System database Client Client Client Customizing Objects Repository Objects Global Settings R © AG SAP
- 17. What is a Client? “A client is an autonomous unit in the R/3 System with regard to commercial law, organization, and data.” user r r ec Maste user a ords User uthori zation Client client- ng de omizi custom pendent C us t izing d ata n transa licatio cti maste on data Ap p r data R © SAP AG
- 18. Common Client Roles CUST Development & Configuring of client settings and Customizing creation of new functionality QTST Quality Assurance Functionality testing and verification of configuration Production Productive activities and business PROD data
- 19. Additional Client Roles SAND Sandbox Sampling of customizing transactions and settings TEST Test Testing of configuration settings with data TRNG Training End-user customer training environment PPRD Pre-production Configured environment for the load of legacy data prior to the start of productive activities
- 20. Sample SAP System Landscape Development Testing Production Database Servers Application Servers Presentation Servers
- 21. Object Migration Corrections and Transport Development QA Testing Production Program A Program A Program A Table A Table A Table A Screen A Screen A Screen A
- 22. Object Migration Corrections Development and QA Testing Transport Program A Program A Version 1 Version 1 ? Program A Program A Version 2 Version 2 ? Program A Program A Version 3 Version 3 Originals
- 23. Geography-based Clients America Client 010 Europe Client 020 Japan Client 030 R/3 Europe R/3 R/3 America Japan
- 24. Client Copies Configuration Development Quality Assurance Interface Testing User Training
- 25. ERP: Integration Integrate people, data and business processes within and between organizations. Collaboration, non-redundancy, consistency and internal process optimization.
- 26. Procurement Process Outline Agreement Purchase Scheduling Requisition Vendor Agreement Demand Accounts Purchase Payable Goods Receipt Order Invoice Verification & Inventory Mgmt.
- 27. Production Process Schedule/Release Goods Issue Shop Floor Order Settlement Goods Receipt
- 28. Sales Process — Trading Goods Customer Order Picking Packing Accounts Receivable Billing Goods Issue
- 29. Sales Process Finished Goods Availability Check Goods Issue Customer Order Final Payment Partial Payment Billing
- 30. Sales Process Finished Goods Availability Check - Insufficient - Independent Customer Order Demand Dependent MRP Run Demand Production Scheduling Purchasing
- 31. Process Flow Goods Issue Goods Production Receipt to Shop Floor Accounts Receivable Billing Goods Issue
- 33. Client • This is a numeric field. • This number defines a whole business entity.
- 34. User • Every SAP user has a user name. • Users of SAP system are client-specific, which means that having a user identification on one client will only allow access to that particular client.
- 35. Password Rules • Letters • Numbers • Easy to remember • 3-8 Characters long • No 3 Characters can be the same • Do not start with a ? or an ! • Do not use previous 5 passwords
- 36. Language • SAP supports multi-national character sets and languages on the same system, at the same time. • Default languages are English and German.
- 37. Field Types • There are three types of Entry Fields – Required – Default entry – Optional entry field
- 38. Sessions • An SAP session is a window in which the user may perform a particular task. • A User may have up to nine sessions open at one time.
- 39. SAP R/3 Resource Management: The Dispatcher Presentation SAP GUI Communications Application Dispatcher Work Work Work Buffers Process Process Process Data base
- 40. SAP R/3 Resource Management: Data Flow Presentation SAP GUI Terminal Process 1 7 Application 2 Request queues Dispatcher 3 6 SAP Memory Buffer Roll Work Process Page 4 5 Data base Relational database system
- 41. SAP R/3 Resource Management: Work Processes A B Message Dialog Update Sold to party: C100 Sold to party: C100 Item Material Qty Item Material Qty 10 6301 10 10 6301 10 20 6412 10 20 6412 10 30 1507 25 30 1507 25 Order Order Sold to party: C100 M Sold to party: C100 Item Material Qty Item Material Qty 10 6301 10 10 6301 10 20 6412 10 20 6412 10 30 1507 25 30 1507 25 Order Order Background Jobs Enqueue SAP Dispatcher C Gateway 1999 1 2 3 4 5 6 7 8 9 10 11 12 19 26 13 20 27 14 21 28 15 22 29 16 23 30 17 24 31 18 25 Spool R/3 G R/2
- 42. SAP R/3 Resource Management: Lock Management by the Enqueue Work Process Instance A Dispatcher Message Server Work Work Process Process Instance B Update Enqueue Dispatcher Lock table in Work Work Process Process main storage Update Enqueue
- 43. SAP R/3 Resource Management: R/3 Instance Database Instance Profiles Instance Message SAP (parameters) Server Gateway Dispatcher Back- Dialog .... Update Spool Enqueue ground SAP Buffers nce I nsta Start Central or Stop
- 44. SAP R/3 Resource Management: Distributed SAP R/3 Processing Instance 03 Instance 02 Dispatcher Dispatcher Back- Dialog Enqueue Enqueue Dialog ... ground Instance 01 Dispatcher Mess- Gate- age way Dialog Update Enqueue Spool
- 45. Reporting • Three basic steps to running a report – Access the report – Enter selection criteria – Execute the report
- 46. System Messages E - Error – An invalid entry has been made. – The cursor moves to the field where the error has occurred. W - Warning – A possible error has been made. –The user can continue without changing. I – Information – Feedback from the system.
- 47. Customizing - Modeling the Business – Organizational Structures in each module – Master Data - Customers, Materials, … – Rules - required entries, tolerances, …
- 48. Mapping – Assignment of organizational structures to reflect the enterprise model – Establishes integration among modules
Editor's Notes
- #21: SAP R/3 Technical Configuration An SAP R/3 System can consist of one or more instances (e.g. a central instance or a distributed SAP R/3 System). Multiple instances are represented by the configuration of a database server and one or more application servers. Only one database and dictionary will exist for an SAP R/3 System. Note: with R/4, you can have multiple database instances. To isolate each distinct phase of an implementation, a typical or recommended configuration for an SAP R/3 System implementation will consist of three separate systems: Development: for configuration of SAP applications with user specific data and user development. Quality Assurance Testing: to isolate development from final testing and user training for production. Production: of live business transactions and company data.