Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Welcome Welcome
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
We love to educate you ! Your Lecturers
Alexander Mors
Holger Jehle
Matthias Mohr
Dr. Holger Wittges
Valentin Nicolescu © Prof. Dr. H. Krcmar
1
Our Projects
© Prof. Dr. H. Krcmar
Using SAP ® Software in Education and Research - Stakeholders and Driving forces Enterprises / job market / business reality
Research Motivation
Job offers, Interest
Students
Research Community
Demand
Research Motivation
Lecturer / Researcher
SAP
Hardware Vendor
Support
HCC
Administrator Institution of Higher Education
Alliance of SAP, Hardware vendor, UCC
Hosting Complexity
© Prof. Dr. H. Krcmar
2
From ASP to ESP
© Prof. Dr. H. Krcmar
Software •
12 SAP R/3 Enterprise (Core 4.7 / Web AS 6.20 / EES 1.10)
•
25 SAP R/3 IDES Enterprise (Core 4.7 / Web AS 6.20 / EES 1.10)
•
1 SAP IS-Banking Release 4.6 C
•
3 SAP BW IDES (BW 3.1 / Web AS 6.20)
•
2 SAP Web AS 6.20
•
1 SAP Solution Manager 3.1
•
1 XI 3.0
•
1 Portal 6.0
© SAP AG
© SAP AG
status: 3/2005
© SAP AG
© Prof. Dr. H. Krcmar
3
Hardware •
42 Sun Fire V210 Server (1x1000 MHz UltraSPARC®-IIIi CPU / 1 GByte RAM)
•
3 Sun Fire V210 Server (2x1000 MHz UltraSPARC®-IIIi CPU / 2 GByte RAM) 2 Sun Fire V240 Server (1x1000 MHz UltraSPARC®-IIIi CPU / 512 MByte RAM) 96 Sun Fire B100S Blade Server (1x650 MHz-UltraSPARC®-IIi CPU / 2 GByte RAM) 6 Sun Fire B1600 Intelligent Shelves 25 StoreEdge 3310 SCSI Arrays with about 19 TByte diskspace Operating System Solaris 9 08/03
• • • • •
status: 7/2004 © Prof. Dr. H. Krcmar
Want to Work with us as Graduate Assistant ? • Extent: 8 h – 12h / week • Your tasks could be: • Pilot Projects, Installations, Application Support • Supporting and Preparing Lectures (SAP specific and general) • Surveys and interviews • …
© Prof. Dr. H. Krcmar
4
Different Views upon SAP = Course Roadmap End User „How will SAP support my tasks ?“
CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
V. Nicolescu
Technical Support „What infrastructure does SAP need ?“
H. Jehle
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
Monday, 21.03.2005
Syllabus - Monday
00.13.009A (Multimedia)
Dr. Wittges
Application Consultant „How to implement SAP ?“
09:00 – 09:15
Welcome
09:15 – 10:30
Status Quo Enterprise Software and SAP
10:30 – 10:45
Coffee Break
10:45 – 12:15
Overview & Implementing SAP Software in Organizations
12:15 – 13:15 13:15 – 14:00
Technical Infrastructure
14:00 – 15:00
Inside S AP: Technical Aspects
15:00 – 15:15
SAP Installation: Visitation
15:15 – 15:30
Coffee Break
15:30 – 17:00
Operating and Hosting SAP Software: The Case of SAP HCC at TU München
§ § § § § § §
Presentation of the Chair and the HCC Course Structure Course Hours, Final Test Overview Enterprise Software & ERP Systems SAP Solutions Market Overview Economic Aspects
§ SAP NetWeaver Concept § SAP Solution Map § Using Business Process Models to implement ERP Workflow within SAP Software § Case Study – Implementing SAP Software in Organizations
Wittges, Mohr, Nicolescu, Mors, Jehle Wittges
Wittges
Lunch Break § § § § § §
Hardware (products, vendors, costs) Sizing SAP Systems Architecture: CSA, Web AS Networking Storage SAP System Landscape
Jehle Mors
§ Visitation of the HCC Hardware
Jehle, Mors
§ Installation, Backup, IT-Security § Outsourcing and ASP § One Year HCC: Experiences
Nicolescu
© Prof. Dr. H. Krcmar
5
01.13.034 and 01.13.010
Tuesday, 2 2.03.2005
00.13.009A
Syllabus - Tuesday
09:00 – 09:30
Outlook: Level 2 Topics
09:30 – 11:00
The User’s View: Working with SAP Software in Business Life
11:00 – 11:15 11:15 – 12:15 12:15 – 13:1 5 13:15 – 14:45 14:45 – 15:00 15:00 – 16:00
§ Developping SAP Solutions § Using SAP Solutions in Business Life § Managing SAP Solutions § Integrating SAP Solutions § Using SAP Software § Coping with SAP’s Complexity § Training and Development for SAP Solutions
Wittges, Mohr, Nicolescu
Mohr
Coffee Break Working with SAP Software I: Navigating the SAP System
§ Hands-On: Navigation
Mohr, Nicolescu
§ Hands-On: R/3 Exercises (MM, SD, FI)
Mohr, Nicolescu
§ Multiple Choice and ShortAnswers
Mohr, Nicolescu
Lunch Break Working with SAP Software : Finance and Logistics using SAP R/3 Enterprise Coffee Break Final Test
© Prof. Dr. H. Krcmar
Course Information • Type: • Evaluation:
Voluntary Course Multiple Choice / Short-Answer Test
© Prof. Dr. H. Krcmar
6
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Status StatusQuo QuoEnterprise EnterpriseSoftware Softwareand andSAP SAP
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
7
Agenda 1. SAP: The Company and its Products 2. Enterprise Software Market Overview 3. Evaluation and Future Trends
© Prof. Dr. H. Krcmar
SAP SAP––The TheCompany Companyand andits its Products Products
Munich Technical University Chair for Information Systems © Prof. Dr. H. Krcmar
8
SAP® • Name of the company: Systeme, Anwendungen und Produkte (“systems, applications and products”) • Name of the software • SAP R/2 – Mainframe version • SAP R/3 – Client/Server version
© SAP AG
© Prof. Dr. H. Krcmar
SAP – Facts and Figures • • • • • •
Founded in 1972 by 5 former IBM employees Headquartered in Walldorf, Germany 31,582 employees 84,000 installations 24,450 customers 12 million users in more than 120 countries
Source: http://www.sap.com/germany/company/press/daten.aspx Access Date 19.01.2005
© Prof. Dr. H. Krcmar
9
SAP Worldwide Organized in 4 Operating Regions Europe Europe Austria
Norway
Belgium
Poland
Croatia Czech Republic
Portugal Romania
Australia
Korea
Brazil
Denmark
Russia
China
Malaysia
Canada
Finland
Chile
France
Slovak Republic Spain
Hong Kong India
New Zealand Philippines
Colombia
Germany
Sweden
Indonesia
Singapore
Mexico
Greece*
Switzerland
Japan
Thailand
U.S.A.
Hungary*
U.K.
Venezuela
Italy
America America Argentina
Asia Asia Pacific Pacific
Africa Africa // Middle Middle East East
Netherlands * Through Partners © SAP AG
Israel*
South Africa
Turkey*
Middle East*
© Prof. Dr. H. Krcmar
SAP Terms and Product Lines SAP R/3 and R/3 Enterprise
SAP NetWeaver
= core ERP system e.g. Materials Management, Sales, Finance, …
= application and integration platform, technological basis e.g. Portal, Data Warehouse, Exchange Infrastructure
Cross-industry solutions = solutions for all types of enterprises e.g. CRM, SRM, APO, SEM
Industry solutions (IS) = solutions for a specific industry e.g. Aerospace & Defense, Public sector, Healthcare, Retail, …
© Prof. Dr. H. Krcmar
10
R/3 core applications / solutions
Logistics MM
Financial Accounting
Sales & Distrib.. Distrib
Materials Manage-Manage PP ment Production Planning
QM Quality ManageManagement
PM
Accounting
FI
SD
CO Controlling
TR
R/3
Treasury
Client / Server ABAP/4
Plant MainteMaintenance HR Human Resources
PS Project System
WF Workflow
IS Industry Solution
Human Resources
Cross Applications © SAP AG © Prof. Dr. H. Krcmar
SAP Technology Environment in General Hardware
UNIX Systems Bull Digital HP
Operating Systems
Databases
Dialog SAP-GUI
IBM SNI SUN
AIX Reliant Digital UNIX UNIX (SINIX) HP-UX SOLARIS ADABAS D DB2 for AIX INFORMIX-OnLine ORACLE
Data General AT&T Bull/Zenith HP (Intel) IBM (Intel) Compaq ...
Sequent SNI Digital
Windows NT
ADABAS D MS SQL Server INFORMIX-OnLine ORACLE
Windows 3.1, Windows ‘95, Windows NT, OSF/Motif, Presentation Manager (PM), Macintosh
IBM AS/400
OS/400
DB2/400
Windows 95, Windows NT, PM
Languages ABAP/4, C, C+ +, HTML (Internet)
© SAP AG © Prof. Dr. H. Krcmar
11
Example: SAP Technology Environment Hardware
UNIX Systems IBM SNI Bull Digital SUN Opteron (e.g. SUN V40Z) HP
Operating AIX LINUX Systems Digital UNIX UNIX (SINIX) HP-UX
Databases
Dialog SAP-GUI
Data General AT&T Bull/Zenith HP (Intel) IBM (Intel) Compaq
Sequent SNI Digital
IBM AS/400
OS/400
Windows NT
SOLARIS
ADABAS D DB2 for AIX INFORMIX-OnLine ORACLE
ADABAS D MS SQL Server INFORMIX-OnLine ORACLE
DB2/400
Windows 95, Windows NT, PM
Win 3.1, Win 95, Win NT, Win XP, OSF/Motif, Presentation Manager (PM), Macintosh
Languages ABAP/4, C, C+ +, HTML (Internet)
© Prof. Dr. H. Krcmar
© SAP AG
Enterprise EnterpriseSoftware SoftwareMarket MarketOverview Overview
12
Selected ERP System Vendors For big companies
For medium-sized businesses
SAP
sage KHK
Siebel
Oracle (inkl. PeopleSoft und J.D. Edwards)
Microsoft Navision
BAAN (ssa global)
SAP Business One © Prof. Dr. H. Krcmar
Outlook: ERP Vendor Landscape Number of vendors will consolidate (see Peoplesoft acquisition) Large Corporations will be first Follow-up – opportunities with current customers next large market New products for mid-size companies and vertical industry segments will become widespread • Refinement in applications will continue • Reduction in complexity of implementation will help • Positioning as integration engines for best-of breed components for middleware vendors • • • •
© Prof. Dr. H. Krcmar
13
Why is SAP Software so Important ? • •
•
•
Forces a Consolidation of Diverse IS Systems Often results in a total change in Doing Business - Redesign Business Process Around the Information System Main Vehicle for Re-engineering Business Processes using Best Practices ERPs are described by Some as the Second Major Revolution in Computer History
© Prof. Dr. H. Krcmar
Why is SAP Software so Important ? /2 SAP Customers among the „Global 500“ (SAP Customers) (Global 500 companies)
Source: http://www.sap.com/germany/company/investor/pdf/FE-Dresdner_Bank_MUC.pdf, Access Date 19.01.2005 © Prof. Dr. H. Krcmar
14
Importance of SAP as a Company •
•
• •
One of the largest companies in the world: No. 5 according to sales volume (app. 8 billion $ in 2003) after IBM, Microsoft, EDS and Oracle 1)
• •
Fast growing company: CAGR Sales (10 yrs): 29% CAGR Op. Income (10 yrs.): 31% 2) Biggest Installed Based of Enterprise Software: 22,000 Customers 2) SAP is one of the world’s most popular brands: (Business Week) No. 35 among Top 100 2)
Very High Importance of R&D: 9,000 Developers 2) Market Share Leader: SAP’s Relative Market Share is about 54% (Oracle: 13%; Peoplesoft+JDEdwards: 12%; Microsoft: 11%; Siebel: 10%)2)
© SAP AG 1) 2)
Source: http://www.ftd.de/ub/di/1053857172853.html, Access Date 19.11.2003 Source: http://www.sap.com/germany/company/investor/pdf/FE-Dresdner_Bank_MUC.pdf, Access Date 19.01.2005 © Prof. Dr. H. Krcmar
Evaluation Evaluationand andFuture FutureTrends Trends
15
Advantages of SAP over other ERPs • Three Tier Client/Server System • Open System - Many O/S’s & DBMS’s • Differentiated Development, Test & Production Systems (SAP’s Landscape) • Embedded Version Control • Integrated Development & Implementation Tools • Sophisticated Management & Monitoring Environment
• Covers Many Business Functions • Strong Workflow Capabilities • Implemented in Many Large, High-Tech Firms • Impressive process and data documentation • Supported by most Major Hardware Vendors
Source: CSU Chico – SAP Lecture1_IntroR3 © Prof. Dr. H. Krcmar
The „shady side“ of SAP • Quite Expensive (see licensing model) • Very Complex • Demands Highly Trained Staff • Lengthy Implementation Time • May create internal conflicts in organizations • SAP rolls out new versions about every 6 months Source: CSU Chico – SAP Lecture1_IntroR3 © Prof. Dr. H. Krcmar
16
Excursus: SAP‘s Licensing Model • Main determinant: Named Users • • • • •
development- workbench user Operational user Information user Request- and-confirmuser Admin user
• HR user
Country specific markups
+ Named Users
+
Contract Price
=
Application Value
Supplementary products
• Standard Discounts
+
• 400,000 € - 700,000 €: 10 % • > 1,7 Mio: 50 %
Database Costs
=
Total Volume
=
Standard Discounts
Krcmar (2004) Informationsmanagement p. 142
© Prof. Dr. H. Krcmar
How Long Does SAP Implementation Take ?
• Large Organizations spend 2 to 3 years on their initial implementation • Value SAP approach promises a basic implementation in 6 to 9 months • Smaller organizations have implemented in 3 to 4 months • Must be prepared to implement
• Education and Training • Prepare organization for change Source: CSU Chico – SAP Lecture1_IntroR3
© Prof. Dr. H. Krcmar
17
Implementation: Involved Parties • • • •
• •
Consultants That Provide the Installation, Training & Configuration Services Individual Employees That Must Learn How to Adapt to New Ways of Doing Their Jobs Key Users In house implementation teams(usually MIS/CIS, Business Process experts and change control types that plan and execute implementations of SAP) SAP and in-house support teams that help trouble shoot problems and support installations. Hosting centers (Application Service Providers)
Source: CSU Chico – SAP Lecture1_IntroR3 © Prof. Dr. H. Krcmar
What is the Academic Role in This? • Show Students How Business Best Practices Operate in a REAL Environment • Use SAP to Demonstrate Concepts and Processes • Provide Students With High Demand Market Skills • More Closely Knit the College of Business Curriculum Together • Keep Faculty Current on Emerging Technologies Source: CSU Chico – SAP Lecture1_IntroR3 © Prof. Dr. H. Krcmar
18
ERP Forecast • Functionality • line between ERP and SCM/CRM continues to blur as vendors increase their functionality • Leading vendors will tighten up integration • Business process will take longer to change software
• Implementation • Rapid implementation will continue
• Architecture • Top tier application will be incorporating J2EE • ERP Suites continue to move to being based on increasingly fine-grained components à Enterprise Service Architecture (ESA)
© Prof. Dr. H. Krcmar
ERP Forecast – Standards • • • •
J2EE or .NET XML As complexity increases more standards will arise Process standards emerging
© Prof. Dr. H. Krcmar
19
30 Years in Enterprise Software
mySAP.com
mySAP Business Suite SAP NetWeaver ESA
One-StepBusiness
R/3
Client/Server
R/2
Mainframe
R/1 n n
n
0.3 mill. € Revenue 9 Employees
1972
5.1 mill. € Revenue n 60 Employees n 50 Customers in 2 Countries
1979
n n
424 mill. € Revenue n 3,200 Employees n 2,800 Customers in 35 Countries
1992
6,265 bill. € Revenue 25,000 Employees n 15,000 Customers in 120 Countries n
n
7.4 bill. € Revenue n 28,654 Employees n 19,300 Customers in 120+ Countries
1999/2000
2002/2003 © SAP AG
© SAP AG © Prof. Dr. H. Krcmar
Business drives Technology * New * Business Enabling Solution Technology
Year
Customer Need
1972
Real-time integrated business processes, R/1, R/2 lower TCO
ABAP
Scalable integrated business processes, SAP R/3, lower TCO SAP APO, SAP BW
R/3 Basis
1992
(Mainframe architecture)
(3-tier Client/Server architecture)
1999
Heterogeneous business processes, lower mySAP.com, mySAP Technology TCO mySAP EP, SAP (Internet architecture) XI
2003
Packaged composite business processes, SAP xApps lower TCO
SAP NetWeaver (Enterprise Services Architecture) © SAP AG
© Prof. Dr. H. Krcmar
20
The Opportunity of a Service-based Architecture Role-based User Interfaces
Composite Business Processes Service request
Price
ATP
Delivery delay
Focused Operational "Nodes"
© SAP AG © Prof. Dr. H. Krcmar
SAP NetWeaver™ •
Unifies and aligns people, information and business processes • Integrates across technologies and organizational boundaries • A safe choice with full .NET and J2EE interoperability
•
The business foundation for SAP and partners • Powers business-ready solutions that reduce custom integration • Its Enterprise Services Architecture increases business process flexibility
© SAP AG © Prof. Dr. H. Krcmar
21
SAP NetWeaver™: An answer to the integration challenge Document Mgmt
Document Mgmt Market Analysis
Call Center
Market Analysis
Call Center
SCM
ERP
SCM
ERP
e-Sales
Trading
Technical systems
E-Procurement
Technical systems
PLM © SAP AG
e-Sales
Trading
E-Procurement PLM
© Prof. Dr. H. Krcmar
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Overview Overviewand andImplementing Implementing SAP SAPSoftware Softwarein inOrganizations Organizations
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
22
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
Lecturer
Dr. Holger Wittges, Dipl.-Wirtsch.Inf Technische Universität München Lehrstuhl für Wirtschaftsinformatik - I17 HCC - SAP Hochschulkompetenzzentrum Boltzmannstr. 3 D-85748 Garching Tel. +49 (0)89 289-19540 Fax +49 (0)89 289-19533 E-Mail:
[email protected] Homepage: www.hcc.in.tum.de
© Prof. Dr. H. Krcmar
23
Agenda 1. 2. 3. 4.
Overview Enterprise Software & ERP Systems ImportantSAP Solutions SAP NetWeaver Using Business Process Models to implement ERP Workflow within SAP Software 5. SAP Solution Map 6. Case Study – Implementing SAP Software in Organizations
© Prof. Dr. H. Krcmar
1.1. Overview OverviewEnterprise EnterpriseSoftware Software&& ERP ERPSystems Systems
24
Definitions ERP •
„ERP (enterprise resource planning systems) comprises of a commercial software package that promises the seamless integration of all the information flowing through the company-financial, accounting, human resources, supply chain and customer information)“ (Davenport, 1998)
•
„ERP systems are configurable information systems packages that integrate information and information-based processes within and across functional areas in an organization“ (Kumar & Van Hillsgersberg, 2000) “One database, one application and a unified interface across the entire enterprise” (Tadjer, 1998) “ERP systems are computer-based systems designed to process an organization’s transactions and facilitate integrated and real-time planning, production, and customer response” (O’Leary, 2001)
• •
(Source : Rashid et al., 2000)
© Prof. Dr. H. Krcmar
ERP development 2000s
Extended ERP
1990s
Enterprise Resource Planning (ERP)
1980s
Manufacturing Resources Planning (MRPII)
1970s
Material Requirements Planning (MRP)
1960s
Inventory Control Packages
Quelle: Rashid et al. 2000
© Prof. Dr. H. Krcmar
25
Characteristics of Enterprise Software Criticality
high
Infrastructure Software
Business Software
Office Software
low
Adaptability © SAP AG
low
high © Prof. Dr. H. Krcmar
A Variety of Enterprise Applications • Customer Relationship Management • Enterprise Resource Planning • Supply Chain Management • E-Procurement & E-Markets • Data Warehousing and Analytics • Portals and Knowledge Management
Document Mgmt Market Analysis
Call Center
SCM
ERP
e-Sales
Trading
Technical systems
E-Procurement PLM
© SAP AG
© Prof. Dr. H. Krcmar
26
Anatomy of an Enterprise System (ERP I) Managers and Stakeholders
Reporting applications Financial applications
Sales and delivery applications
Customers
Sales force and customer service reps
Central database
Service applications Human resource management Applications Quelle: Davenport, 1998
Back-office Manufacturing applications Administrators and workers
Suppliers
Invetory and supply applications
Employees © Prof. Dr. H. Krcmar
Extended ERP • • • •
Service oriented architecture Integration of Middleware functionality Support of more then one central DB ERP II-System looks more like a open toolset rather than a closed solution
© Prof. Dr. H. Krcmar
27
ERP – Business View •
•
The integration of all computing within an organization such that: • all major business processes are encompassed and standardized and • all data is usable by all functional areas of the business Enterprise Resource Planning = ERP • Integrate many business functions into one seamless application • Usually are applications systems that run on top of a RDBMS • Replace 100s of legacy systems in organizations who use an ERP Source: CSU Chico
© Prof. Dr. H. Krcmar
ERP – Technical View • What are Enterprise Resource Planning (ERP) Systems? • Incredibly large, extensive software packages used to manage a firm’s business processes. • Standard software packages that must be configured to meet the needs of a company • Database programs with the following functions: - Input 28,610+ Tables in SAP - Storage/Retrieval - Manipulation - Output © Prof. Dr. H. Krcmar
28
ERP Suites • Core Applications • • • •
Financials Human Resources (HR) Manufacturing Project Management
• Extended ERP • • • • • • •
Business Intelligence Customer Relationship Management (CRM) Sales Force Automation (SFA) Supply Chain Management (SCM) E-Logistics E-Procurement Product Life-cycle Management (PLM)
• Internet Transformation for ERP • Portals • Exchanges – B2B • Mobile Access © Prof. Dr. H. Krcmar
ERP functions: examples Manufacturing
Financials Accounts payable
budgeting
Quality control
Production scheduling
Asset management
Shop floor execution
Accounts receivable
Demand forecasting
general ledger
Shop flow management
Bill of materials
Job cost accounting
Project Management Planning schedules
HR Tracking project cost Employee information
Contracts, resources © Prof. Dr. H. Krcmar
29
What is Enterprise Resource Planning ?
Executive IS
Strategic Information
Decision Support Managerial Information
Sales & Marketing
HR
Manufacturing
Procurement Accounting & Finance
Transaction Information
One Integrated Information System
© Prof. Dr. H. Krcmar
Advantages of ERP systems What benefit
How
Reliable information access
Common DBMS, consistent and accurate data, improved reports.
Avoid data and operations redundancy
Modules access same data from the central database, avoid multiple data input and update operations.
Delivery and cycle time reduction
Minimizes retrieving and reporting delays
Cost reduction
Time savings, improved control by enterprise-wide analysis of organizational decisions.
Easy adaptability
Changes in business processes easy to adapt and restructure
Improved scalability
Structured and modular design with “add-ons”
Improved maintenance
Vendor-supported long-term contract as part of the system procurement
Global outreach
Extended modules such as CRM and SCM
E-Commerce, e-business
Internet commerce, collaborative culture
Quelle: Rashid et al. 2000
© Prof. Dr. H. Krcmar
30
Disadvantages of ERP systems Disadvantages
How to overcome
Time-consuming
Minimize sensitive issues, internal politics and raise general consensus
Expensive
Cost may vary from thousands of dollars to millions. Business process reengineering cost may be extremely high.
Conformity of the modules
The architecture and components of the selected system should conform to the business processes, culture and strategic goals of the organization.
Vendor dependence
Single vendor vs. multi-vendor consideration, options for “best of breeds ”, long-term committed support.
Features and complexity
ERP systems may have to many features and modules so the user needs to consider carefully and implement the needful only.
Scalability and global outreach
Look for vendor investment in R&D, long-term commitment to product and services, consider Internet enabled systems.
Extended ERP capability
Consider middle-ware “add-on” facilities and extend modules such as CRM and SCM.
Quelle: Rashid et al. 2000
© Prof. Dr. H. Krcmar
2.2.Important ImportantSAP SAPSolutions Solutions
31
What is SAP R/3 ?
• SAP is an example of an ERP System • SAP R/3 • SAP’s Client Server version (Distributes process and presentation) • Based on R/2 (Mainframe version - centralization of data and process) • R/3 4.0: release (May 1998) distributes data, process, and presentation • R/3 4.7: first release, based on NetWeaver™ components
• mySAP ERP 2003 • mySAP ERP 2004 © Prof. Dr. H. Krcmar
mySAP ERP within mySAP Business Suite
© SAP AG © Prof. Dr. H. Krcmar
32
Architekture of mySAP ERP
© SAP AG © Prof. Dr. H. Krcmar
SAP Solutions • Online demo: • http://www.sap.com
© Prof. Dr. H. Krcmar
33
3.3.NetWeaver NetWeaver
SAP NetWeaver Platform
© SAP AG © Prof. Dr. H. Krcmar
34
SAP NetWeaver - Product Roadmap
© SAP AG
© Prof. Dr. H. Krcmar
4.4.Using UsingBusiness BusinessProcess ProcessModels Modelsto toimplement implement ERP ERPWorkflow Workflowwithin within SAP SAPSoftware Software
35
Using Business Process Models to implement ERP Workflow within SAP Software
• Business Process Models describe the business • Workflows describe the technical implementation of the BPM using high level Application components
© Prof. Dr. H. Krcmar
Today Change is to costly and slow
© SAP AG
© Prof. Dr. H. Krcmar
36
SAP Enterprise Services Architekture
© SAP AG
© Prof. Dr. H. Krcmar
Solution Map • „SAP's Solution Maps are well-defined tools that outline the scope of an organization's business. The Solution Maps also show how various processes are covered, including the processes that SAP and its partners support“ SAP
© Prof. Dr. H. Krcmar
37
5) 5)SAP SAPSolution SolutionMap Map
Solution Map NetWeaver Level 1
© Prof. Dr. H. Krcmar
38
Solution Map mySAP CRM Level 1
http://www.sap.com/solutions/businessmaps/DEE27EBB1D564D8C800231 FE6D54325D/index.aspx (18.1.2004)
© Prof. Dr. H. Krcmar
Solution Map mySAP CRM Level 2
© Prof. Dr. H. Krcmar
39
Questions
…? © Prof. Dr. H. Krcmar
6.6.Case CaseStudy Study––Implementing ImplementingSAP SAPSoftware Softwarein in Organizations Organizations
40
Implementing SAP Software in Organisations
• NIBCO‘S „BIG BANG“ Teaching Case from: C. Brown & I. Vessey, 2000, Indiana University.
© Prof. Dr. H. Krcmar
NIBCOS‘S „BIG BANG“ Project • • • • •
Project Goals Project Organization Project Timeline Project Tasks Discussion: Possible problems and how to avoid them
© Prof. Dr. H. Krcmar
41
Project Goals • Enable IT-support for the new supply chain and customerfacing strategies • Substitute a „patchwork of legacy systems and reporting tools“ with a new, integrated system for • ten plants and • four distribution centers
• go live without consultants on 30th of dec. 1997
© Prof. Dr. H. Krcmar
Project Organisation
• • • •
big bang approach „TIGER Triad“ -> Project Lead „TIGER Den“ -> Workplace Team size approx. 70 Members
© Prof. Dr. H. Krcmar
42
Project Timeline 01.08.1995 Start 14 months planning 30.09.1996 Kickoff 15 months to implement 30.12.1997 Go Live
© Prof. Dr. H. Krcmar
Project Tasks • Project Management • Define Business Responsibilities • • • •
Finance and Controlling Material Management/Production Planning Sales/Distribution Change Management
© Prof. Dr. H. Krcmar
43
Change Management Categories • • • • • • • •
New Automate Eliminate Transfer Risk Difficulty Relationships Other
© Prof. Dr. H. Krcmar
Discussion: Possible problems and how to avoid them
© Prof. Dr. H. Krcmar
44
Literatur • Carol, Vessey: „NIBCO‘S BIG BANG“, 2000, Indiana University. • Davenport: „Putting the Enterprise into the Enterprise System“, Harvard Business Review, 1998, p.121. • Rashid, Hossain, Patrick: „The Evolution of ERP Systems: A Historical Perspective“, Idea Group Publishing, 2000. • SAP: help.sap.com à online documentation.
© Prof. Dr. H. Krcmar
Business Businessand andTechnology TechnologyAspects AspectsofofSAP SAP
Technical TechnicalInfrastructure: Infrastructure: The TheCase Caseof ofSAP SAPHCC HCCat atTU TUMünchen München Introduction into hard- and softwareconfigurations for a SAP computing center
45
Lecturer
Dipl. Inf. Holger Jehle Technische Universität München Lehrstuhl für Wirtschaftsinformatik - I17 HCC - SAP Hochschulkompetenzzentrum Boltzmannstr. 3 D-85748 Garching Tel. +49 (0)89 289-19539 Fax +49 (0)89 289-19533 E-Mail:
[email protected] Homepage: www.hcc.in.tum.de
© Prof. Dr. H. Krcmar
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
46
Topics • Existing Installation • Inventory • Architecture • Performance Benchmarking
• Sizing • Requirements elicitation • Cost-Efficiency-Analysis • Side-Effects (Backup, License, Power, Cooling , Rooms)
© Prof. Dr. H. Krcmar
Hardware Inventory • • • • • • • •
2 Sun Fire V880 Server (8x1200 MHz UltraSPARC®-IIIi CPU / 16 GByte RAM, 210 GB HD RAID 1) 42 Sun Fire V210 Server (1x1000 MHz UltraSPARC®-IIIi CPU / 1 GByte RAM) 3 Sun Fire V210 Server (2x1000 MHz UltraSPARC®-IIIi CPU / 2 GByte RAM) 2 Sun Fire V240 Server (1x1000 MHz UltraSPARC®-IIIi CPU / 512 MByte RAM) 96 Sun Fire B100S Blade Server (1x650 MHz-UltraSPARC®-IIi CPU / 2 GByte RAM) 6 Sun Fire B1600 Intelligent Shelves 25 StoreEdge 3310 SCSI JBOD-Arrays with about 19 TByte diskspace Operating System Solaris 9 08/03 status: 2/2005
© Prof. Dr. H. Krcmar
47
Architecture 3-Tier-Layout
Database Server
2-Tier-Layout
Application Server
SAP GUI
DB / App-Server
SAP GUI SAP Systems © Prof. Dr. H. Krcmar
2 / 3 Tier Architecture • 3-Tier-Architecture: separate server systems (plural) • Specialization of systems - complementary hardware setup • Scalability: ability to add/switch application-servers on demand - increased availability à data center requirements
• 2-Tier-Architecture: one server (singular) • Smaller number of required systems - Administrative complexitiy, licensing, Infrastructure à smaller business demands
© Prof. Dr. H. Krcmar
48
Adaptive Computing (SAP)
Divide the IT-Infrastructure in 4 independant Blocks: • Computing: computing power provided by single nodes • Storage: dataspace to be used for computing tasks • direct-, network-attached-storage or storage area network
• Network: data interconnection between systems • Control: single-point of configuration / administration for most tasks
© Prof. Dr. H. Krcmar
Adaptive Computing
Services
Application Services à ECC 5.0
Control Instance
Virtualization Layer
IT infrastructure
Control
Network
Storage
Computing
© Prof. Dr. H. Krcmar
49
Adaptive Computing
• Dynamic allocation of services to hardware • Reconfigurable at runtime • Both high availability and high performance setup
• single point of administration / configuration for Adaptive Computing
© Prof. Dr. H. Krcmar
Benchmarking • Benchmarking: • Standardized software to evaluate whole systems - cooperation of operating system, compiler, cpu und periphery - synthetic testing: drhystone, whetstone: defined programs, defined output - application-like: SPEC-Suite (Standard Performance Evaluation Coorp.) - kernel-based-application: algorithm-kernels - LINPACK
© Prof. Dr. H. Krcmar
50
Monitoring / Benchmarking • Monitoring: • Measuring devices (hardware/software) and performance counters for single pieces of hardware àhints to figure out hardware-bottlenecks
• SAP-Benchmarking: • Average Response-Time for defined Transactions - compare 2- and 3-Tier-Layouts, adaptive if possible - peak-performance vs. continous load conditions
© Prof. Dr. H. Krcmar
SAP Benchmarking •
SAPS Definition: The SAP Application Performance Standard (SAPS) is a hardware independent unit, which describes the performance of a system configuration in the SAP environment. It is derived from the SD Standard Application benchmark, where 100 SAPS are defined as 2,000 fully business processed order line items per hour. In technical terms, this throughputis achieved by processing 6,000 dialog steps (screen changes), 2,000 postings per hour in the SD benchmark, or 2,400 SAP transactions. Fully business processed in the SD Standard Application Benchmark means the full business process of an order line item: creating the order, creating a delivery note for this order, displaying the order, changing the delivery, posting a goods issue, listing orders, and creating an invoice. Source: http://dev.mysql.com/doc/maxdb/benchmarks.html For more Information: http://www.sap.com /benchmark © Prof. Dr. H. Krcmar
51
Comparison of SAP Benchmarks • Application-benchmarking, real conditions • Influenced by lots of factors • Hardware: CPU, Cache, RAM, Storage, etc… • Operating System, system load, configuration
• Not directly convertable into well-known benchmark-values (e.g. MIPS) • Example values for known hardware configurations: • SUN Blade B100S: approx. 60 SAPS • V210: approx. 180-200 SAPS • V880: approx. 3300 SAPS • V40z: approx. 4400 SAPS
© Prof. Dr. H. Krcmar
• Peak-Load-Sizing • Average-Case-Sizing • Budget-oriented Sizing
load
Sizing 1,8 1,6 1,4 1,2 1 0,8 0,6 0,4 0,2 0
real peak average ?budget?
1
2
3
4
5
6
7
8
time t
• Balanced distribution of resources (CPU, Mem, Storage) • Optimization for demands • Scalability
© Prof. Dr. H. Krcmar
52
Sizing II - First-Brake values in expansion stages
costs
• Linear groth of costs up to specific level • Exorbitant higher costs for bigger installations: • network infrastructure • uninterrupted power supply • cooling system • installation area • administration office
linear real optimized
size
© Prof. Dr. H. Krcmar
SAP Quicksizer • Online tool to approximate demands for known services à http://service.sap.com/quicksizer
• Insert designated system properties like: • SAP product (FI, CO…) • No. of users, type of users, composition of usertypes
• Results as assistance for hardware aquisition • Needed SAPS • CPU, RAM, Storage sizing
© Prof. Dr. H. Krcmar
53
SAP Quicksizer – Input Values
Source: http://service.sap.com /quicksizer © Prof. Dr. H. Krcmar
SAP Quicksizer – result example
© Prof. Dr. H. Krcmar
54
Security
• Operating System • patches, configuration, policies
• SAP-Application • patches, configuration, policies
• Accessability • firewall, SAP-Router, dynamic source-IP‘s
© Prof. Dr. H. Krcmar
Bibliography • Mißbach et. al (2003): SAP Systembetrieb, Galileo Press Bonn • SAP Labs (2002): SAP Guide System Administration, Galileo Press Bonn • McFarland Metzger, Röhrs (2000): SAP R/3-Änderungsund Transportmanagement, Galileo Press Bonn • Rechenberg, Pomberger (2002): Informatik-Handbuch
© Prof. Dr. H. Krcmar
55
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Inside Inside SAP: SAP:Technical TechnicalAspects Aspects
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
Lecturer • Alexander Mors M.A. • Working at SAP HCC • Topics • • • •
UNIX/SAP operation Solution Manager Backup&recovery Monitoring
© Prof. Dr. H. Krcmar
56
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
Agenda 1. 2. 3. 4. 5.
Client/Server basics Possible SAP R/3 configurations Management of complex SAP system landscapes Interfaces in SAP Systems Overview of internal structure of SAP Software
© Prof. Dr. H. Krcmar
57
Client/Server: Basics Client
Client
...
Client
Client
Net
Server
© Prof. Dr. H. Krcmar
Sample: R/3 – Configuration PC
Notebook
Presentation Workstation
Application
WebServer
ApplicationServer
Browser Clients
ApplicationServer
DatabaseServer
Database © SAP AG
© Prof. Dr. H. Krcmar
58
Possible R/3 Client-Server-Configurations Central System
Presentation
2-Level Configuration WorkPC station Notebook
Notebook PC
Workstation
PC Notebook ApplicationServer ApplicationServer
Application
DatabaseClient Client Database Server Client ApplicationServer
3-Level Configuration
ApplicationServer DatabaseServer
DatabaseServer
© Prof. Dr. H. Krcmar © SAP AG
Client concept • SAP supports different clients • A Client is a organisation, like a company or one corporate group • This concept comes from history: in the early stages a group of companys shared one system.
Application data User data Client dependent customizing
© Prof. Dr. H. Krcmar
59
Data structure of SAP-Systems Client 900 Application data
Client dependent customizing
Client 901 Application data
User data
User data
Client dependent customizing Client independent customizing
Repository (tables, programms, functions-module …) Divided into development classes © Prof. Dr. H. Krcmar
Transportation in SAP
Development Development system system (DEV) (DEV)
quality qualityassurance assurance (QAS) (QAS)
Production Productionsystem system (PRD) (PRD)
• Typical 3-system-landscape with DEV, QAS und PRD • Transport of repository objects from DEV to QAS and check with in a realistic environment PRD • transfer order with all changed objects • distinction between workbench- and customizing-orders © Prof. Dr. H. Krcmar
60
Operation modes Operation mode: night
Operation mode: day Instance 1
Instance 1
Dispatcher D
D
D
B
Dispatcher B
D
D
B
B
Day:
Night:
Dialog processes
Background processes
Instance 2
B
Instance 2
Dispatcher
Dispatcher
D D D D B B
D D B B B B © Prof. Dr. H. Krcmar
Complex Landscape managed by SolutionManager
Quelle SAP
©SAP
© Prof. Dr. H. Krcmar
61
Services provided by SolutionManager
Quelle SAP
©SAP
© Prof. Dr. H. Krcmar
SAP MCOD
SAP MCOD Traditional system setup: n SAP systems, n Databases
SAP R/3
SAP R/3
RDBMS
RDBMS
SAP BW
Simplification using MCOD option: n SAP systems, 1 Database
RDBMS
SAP SEM RDBMS
SAP R/3
SAP BW
SAP R/3
SAP SEM
RDBMS SAP EBP
SAP EBP
RDBMS
© Prof. Dr. H. Krcmar
62
SAP NetWeaver™
©SAP © Prof. Dr. H. Krcmar
HTTP (S)
SMTP
Browser
SOAP/ XML
SAPWeb Web AS 6.20: Architecture andConnectivity Connectivity SAP AS 6.20: Architecture Connectivity Web AS 6.20:Platforms Architecture and SAPSAP Web AS 6.20: andand Connectivity
Internet Communication Manager SAP Web AS
RFC SAP J2EE Fast RFC Engine
ABAP
external systems, SAP GUI
DIAG SAP GUI
SAP DB Informix
Windows/AIX/Solaris/Linux/HP-UX OS/400
Operating System
OS/390
Database Server SAP DB Informix Microsoft SQL Server
Oracle DB2 (DB4, DB6)
Database System © Prof. Dr. H. Krcmar
63
SAP Web AS: Architecture and Connectivity
©SAP
© Prof. Dr. H. Krcmar
ICM Aufbau und Funktion
©SAP
© Prof. Dr. H. Krcmar
64
SAP J2EE Engine: Web Access Web Browser/ Web Server SAP Web Application Server
ICM
MS
Dispatcher
WP
Dispatcher
WP
Fast RFC, JCo
Server
Server
SAP J2EE Engine
© Prof. Dr. H. Krcmar
J2EE Engine As a system, the J2EE Engine consists of three logical layers: · Java Enterprise Runtime – comprises low-level subsystems that provide functions such as class loading, cluster communication, persistent configuration data management, and so on. · J2EE Engine Components – consists of interfaces, libraries and services components that provide various runtime functions and programming APIs. · Applications – refers to the applications that are deployed and run on the J2EE Engine. ©SAP © Prof. Dr. H. Krcmar
65
„Our“ R/3-Configuration ... presentation
presentation
presentation
...
presentation
SAPGuis at the PC-Lab
network
application
application
application
SAP R/3 Enterprise on OS Solaris 9 Database SAPDB 7.3
SUN Fire B100S Blade Server
SUN Fire V210 Server
DB
HCC TU München: http://www.hcc.in.tum.de
StorEdge 3310 SCSI Arrays
Data
© Prof. Dr. H. Krcmar
logical view ...
User 1
User 2
Presentation Presentationcomponent component ABAP ABAP Workbench Workbench
R/3 Basis System
R/3 R/3 Anwendung Anwendung11
...
R/3 R/3 Anwendung Anwendung22
Kernel Kerneland andbasic basicservices services Kernel Kerneland andbasic basicservices services Database © Prof. Dr. H. Krcmar © SAP AG
66
Program logic
Bild 1
Bild 2
Bild 3
Präsentationlayer
SAP GUI
Non activ
SAP GUI
Non activ
SAP GUI
Interaction with user
Non activ
Dialogue step
Non activ
Dialogue step
Non activ
processingof dialogue steps by the system
Applicationlayer
© Prof. Dr. H. Krcmar © SAP AG
Workload Statistics
Presentation Server
Wait time
Roll in
Load time
Application Server
Processing time
Network
Network
CPU time Database time
Database Server
© Prof. Dr. H. Krcmar
67
OpenSQLTM • Port from ABAP on all common databases Applikations-Server
Database server
ABAP ABAPInterpreter Interpreter Select Select**from from
SQL SQLdatabase database
DB DBInterface Interface Open OpenSQL SQL
Native NativeSQL SQL
DB DBdata data
DB DBdata data
Exec ExecSQL. SQL. Select… Select… End EndExec. Exec.
Native NativeSQL SQL
data
DB DBdata data © Prof. Dr. H. Krcmar
Why Use Table Buffers in SAP systems?
Application Server A ABAP/4 Program
SELECT * FROM T001 WHERE …
0,2 – 6 ms
Table Buffer
Database Interface 8 -600 ms DBMS
DBM S
Processes
Database Buffer
Database
© Prof. Dr. H. Krcmar
68
SAP Memory – System Point of View
Server Virtual memory Shared memory
Local memory
Roll buffer
SAP buffers (programs , tables)
SAP paging buffer
Extended memory (user contexts )
Heap memory (temporary)
Local memory
Local memory
Work process
Work process
…
Local memory
…
Work process
1:1
1:n SAP roll file
SAP paging file
© Prof. Dr. H. Krcmar
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Operating Operating and andHosting HostingSAP SAPSoftware: Software: The TheCase Caseof ofSAP SAPHCC HCCat atTU TUMünchen München
69
Lecturer
Dipl. oec. Valentin Nicolescu Technische Universität München Lehrstuhl für Wirtschaftsinformatik - I17 HCC - SAP Hochschulkompetenzzentrum Boltzmannstr. 3 D-85748 Garching Tel. +49 (0)89 289-19539 Fax +49 (0)89 289-19533 E-Mail:
[email protected] Homepage: www.hcc.in.tum.de
© Prof. Dr. H. Krcmar
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
70
Enterprise software (SAP) Database Operating system
Concepts
Software
Structure of this unit
Hardware
• Goals for this unit: • You get an impression of operating enterprise software in a computer center • You can identify important tasks of regular operation
© Prof. Dr. H. Krcmar
Topics in detail • Concepts: outsourcing, organization, technical change management, documentation • Hardware: Hardware replacement, network, high availability, adaptive infrastructure • Software: • Operating System: job scheduling, file space management • Database: backup, recovery, optimization • Enterprise software (SAP): Change managementin SAP, user administration, regular tasks, archiving, upgrade • In general: patching, monitoring
© Prof. Dr. H. Krcmar
71
Concepts • • • •
Outsourcing Organization Change Management Documentation
© Prof. Dr. H. Krcmar
Outsourcing • Transferring responsibilities for operating specific parts of a landscape to another company / department • Outsourcing tyes: • Comprehensive Outsourcing: Company sells IT-department • Insourcing: Company treats IT-department as a company in the company • Selective Outsourcing (typical): company „oursources“ specific part of landscape
• Difference between outsourcing of the hardware operation (computer center) und Application Service Providing (ASP): AS Providers care also about the software maintenance © Prof. Dr. H. Krcmar
72
Benefits of Outsourcing • Fix transparent costs • Synergy effects à lower price for services (the more homogeneous a landscape the more synergy) • ASP is specialized in specific domains • Support by full-time specialists SAP HCC TUM is an ASP for schools of higher education
© Prof. Dr. H. Krcmar
Organization of enterprise software operation
Enduser – Operation system Enduser - Network
SAP - Basis
Application logic Network
Helpdesk
Frontend
Enduser - Application
Application administration Database Server - Operation system Server - Hardware
© Prof. Dr. H. Krcmar
73
Organization at SAP HCC TUM Enduser - Application Enduser – Operation system
E2 E4
Enduser - Network Application logic Application administration Database
E3
Server - Operation system E1
Server - Hardware = employee responsible for this domain © Prof. Dr. H. Krcmar
Other organizational issues • Determine who is responsible for what domain (e.g. by a RACI-model) • Defining shifts: per day and per week • Preparing support guidelines for 1st and 2nd (and 3rd) level support (who, when, what …) • On-call duty for emergency cases • Spatial separation of critical components • Mechanical security (only admin staff can access servers) © Prof. Dr. H. Krcmar
74
Technical change management • Changes of any configuration element can lead to errors • To avoid such errors changes have to reviewed depending on their characteristics • Example classification for changes: • Routine change (mostly no review) • Normal change (normal review) • Project (multitude of changes)
• Generally at least 2 persons should review normal or bigger changes © Prof. Dr. H. Krcmar
Documentation 1. Documentation can serve for solving errors resulting from a change 2. Documentation for communication purposes:
Communication without documents
Communication with documents © Prof. Dr. H. Krcmar
75
Hardware • • • • •
Network Configuration Hardware replacement High availability Adaptive infrastructure
© Prof. Dr. H. Krcmar
Network • Maintenance tasks in network domain: • • • •
Assignment of MAC ID to Hostnames/IP-Adresses Monitoring access to servers from the outside Monitoring network load and paket corruption Monitoring Network File Services (NFS)
• Maintenance of 2 Networks architectures: • Data network • Administration network (console)
© Prof. Dr. H. Krcmar
76
Configuration • Configuration of Hardware realized by 2 components (comparable with BIOS at Home PC‘s) • Advanced lights out manager (ALOM) and the console (Solaris specific) • Access can be established even if servers are „down“ • ALOM: Basis controls of server: • „Really“ shutting down and starting server • Reading basic log files • …
• Console : • Installing server • Defining boot sequence • …
© Prof. Dr. H. Krcmar
Hardware Replacement • Sometimes defective devices have to be replaced (e.g. hard disks, server, memory …) • During replacement, operation of applications needs to be ensured • Operation during exchange realized by modular architecture of devices: • • • •
Harddisks are hot swapable Redundant power supplies are hot swapable MAC ID‘s can be changed (!) (Sun specific) …
© Prof. Dr. H. Krcmar
77
High availability (HA) • • • •
Some components need to be available at any cost (avoiding single points of failure = SPOF) At SAP HCC TUM the SAPRouter (central access point to all SAP Systems from outside) is high available In case of failure in one system of the failover cluster, the routing will be switched by IP-failover-mechanism Components like databases or complete ERP-Systems are also used with HA Frontend
Frontend
IP 123.456.789.012
Server active
IP 123.456.789.012
Failover
Server defective
Server in stand-by
Failover-Cluster
Server active
Failover-Cluster © Prof. Dr. H. Krcmar
Adaptive architecture • At work load peaks, the higher demand for computing power has to be satisfied (e.g. end-of-month account) • As load peaks often are not predictable, a flexible infrastructure with quick response times is needed • Solutions in the SAP environment: • Moving a application frome a server to a bigger one • Flexible assignment of servers to systems (at SAP HCC TUM: the „Blade Runner“)
© Prof. Dr. H. Krcmar
78
'
Adaptive architecture at SAP HCC TUM
© Prof. Dr. H. Krcmar
Software – Operating system • Job scheduling • File space management
© Prof. Dr. H. Krcmar
79
Job Scheduling • Regular tasks on operation system level need to be scheduled • Task examples: • • • •
Collecting monitoring data Transferring files (from one server to another) Triggering backups …
• In Unix jobs can be scheduled as cron jobs • In Windows jobs can be realized as tasks in system controls © Prof. Dr. H. Krcmar
File space management • Writing down a multitude of Log files, file space can grow short • If free file space is very low, applications can‘t start or stop correctly • Regularly monitoring and maintaining free file space is a crucial task • Amount of new log files per week can be up to 40 GB per system at SAP HCC TUM
© Prof. Dr. H. Krcmar
80
Software - Database • Backup • Recovery • Maintenance
© Prof. Dr. H. Krcmar
Backup of SAP systems • Recommended backup cycle: daily (real: weekly) • Distinction of 3 different backup types • Full backups • Incremental backups • Log files (logging all database changes)
• Recommended time to hold backups: • 1 month for all backups • 1 year for longterm archiving
• Size of backups at SAP HCC TUM: about 700 GB per day © Prof. Dr. H. Krcmar
81
SAP backups at SAP HCC TUM
SAP System 1 Local backup 1 GBit LAN
SAP System 2 Local backup machine
Tape library
Leibniz Rechenzentrum
SAP HCC TUM
SAP System n
© Prof. Dr. H. Krcmar
Recovery of backups Date:
21
22
23
24
t1
t2
25
26
Log Info
28
t3
21 .. .. 23
Data
27
t4
29
… t5
24 .. .. 27
Data
Log Info
DBM
© Prof. Dr. H. Krcmar
82
Database maintenance (SAP DB specific) • Cost based optimizer: • Access strategy for searches within database depend on: - Values in table columns - Available indices - Number of accesses • In a weekly optimization run, new access strategies are calculated for every database table if major changes in size or structure occured à resource costs of database access are minimized
• Consistency check: Checks wether database is in a structural consistent state © Prof. Dr. H. Krcmar
Software – Enterprise software (SAP) • • • • •
Change management in SAP User administration Regular tasks Archiving Upgrade
© Prof. Dr. H. Krcmar
83
SAP Change management - Transport system
Development Development System System(DEV) (DEV)
Quality Qualityassurance assurance System System(QAS) (QAS)
Productive Productive System System(PRD) (PRD)
• Changes are saved in transport requests that go from the DEV to the QAS system • Transport requests are saved as files when they are exported • Transport request can be imported into a system inidivually or all at STMS once © Prof. Dr. H. Krcmar
Approval of changes in SAP • Change requests from the DEV system need to be imported manually into the QAS system • Changes need to be approved in the quality assurance system • Approval sequence can be implemented by using the workflow engine (e.g. user à department manager à technical manager) • If one of the approver dimisses the change, the sequence is terminated and the change needs to be revised in the DEV system • In case of approval a change will be automatically transported into the productive system • Approval of changes helps to avoid „side effects“ of changes (e.g. developers could give themselves more rights in the productive system) © Prof. Dr. H. Krcmar
84
User administration • Authentifications and authorizations for users can be administrated locally or central in one SAP system for all other systems (central user administration = CUA) • CUA can be connected to a Lightweight Directory Access Protocol (LDAP) server • Based on LDAP server the authentification data can be accessed by other systems (also non-SAP) • SAP distinguishes among other the following user types: • Dialog user (normal user) • Communication user (only for communication between systems)
© Prof. Dr. H. Krcmar
Background jobs • •
Batch work processes can disburden dialog work processes by processing asynchronous performable tasks Types of jobs: • • • •
•
Archiving Clean-up of spool queues Delivery of workflow items, emails …
Characteristics of jobs: • Scheduling (periodic; event-driven: external event, predecessor job, change of operation mode) • Execution (ABAP-program, external command) • Variants (allow to run jobs with predefined parameters) • Status (scheduled, released, ready , active, canceled, finished) • Job class (A, B, C)
•
Class A jobs run in any case independent of work load resulting from other jobs SM37 © Prof. Dr. H. Krcmar
85
Archiving • Reasons for archiving : • Reduction of the required database space • Performance improvement • Legal regulation
• Archiving of all data for a specific business processes and ist documents as a consistent unit • Archiving is the only way to remove documents or other data from the system • Specific documents have to be kept for up to 10 years • Auditing acceptability needs to be respected (data can not be changed after archiving them) © Prof. Dr. H. Krcmar
Archiving Business Objects Offline storage
Files in file system Archiving objects
Archiving object SD_VBAK
SAP Business Object
Database
…
Order 6320
Table VBAK 6320 6321 …
Table VBUK 6320 6321 …
Order 6321
Table VBPA 6320 6321 …
© Prof. Dr. H. Krcmar
86
Upgrades • Upgrading a SAP system is a very sophisticated and risky project that needs detailed preparation • Technically seen, for a short period a shadow SAP system with the new release runs on the old system • During the upgrade own developments have to be transferred and adapted to the new system • The old system will be shutdown after the new system takes over all functions • Depending on system size and amount of own developments the upgrade takes from 12 hours to some days
© Prof. Dr. H. Krcmar
Software – In general • Patching • Monitoring
© Prof. Dr. H. Krcmar
87
Patching • • • • • • • • • •
SAP Notes + SAP Support packages SAP Add-Ons SAP Kernel patch SAP J2EE-Patches Database-Patch Database-Library-Patches Precompiler-Patches Solaris Patch ALOM-Patch OBP-Patch © Prof. Dr. H. Krcmar
Handling of SAP support packages • Support packages exist for the different components of an SAP System (e.g. in R/3 about 15 components) • Some support package levels have prerequisites in other components that need to be controlled • Support packages for different components can be imported together • During import of support packages no user may work on the system because active objects are replaced • Importing support packages in all SAP HCC TUM systems takes about one week (twice a year) © Prof. Dr. H. Krcmar
88
Handling of SAP Notes • Notes can be only of descriptive nature or contain ABAP code that can be applied • Notes with code fix problems before they are fixed in support packages (like hotfixes for windows) • Normally any change in SAP code (modification) needs a installation specific key for the changed object • Importing Notes avoids the need to request such a key (problems with modificated objects will not be solved by SAP support) SNOTE © Prof. Dr. H. Krcmar
Monitoring • Certain aspects can be monitored over all systems • Server specific data is collected by local agents • All collected data is saved in the central monitoring system for later analysis • For special alarms auto reaction methods can be assigned • For example automatic information by mail / SMS in case of: • • • •
Breakdown of a server Database errors Full file space … RZ23N © Prof. Dr. H. Krcmar
89
Monitoring - SAP Agents
SAP Instance Central Monitoring System
Dispatcher D
D
B
B
B
Local Monitoring
Central Monitoring SAP Agent Availability Ping Log Files
Shared Memory
© Prof. Dr. H. Krcmar
Bibliography • Mißbach et. al (2003): SAP Systembetrieb, Galileo Press Bonn • SAP Labs (2002): SAP Guide SystemAdminiatration, Galileo Press Bonn • McFarland Metzger, Röhrs (2000): SAP R/3-Aänderungsund Transportmanagement, Galileo Press Bonn
© Prof. Dr. H. Krcmar
90
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
The TheUser‘s User‘sView: View: Working with SAP Software Working with SAP Softwarein inBusiness BusinessLife Life
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
91
Challenge for SAP: Software Engineering @ SAP •
Volume of SAP business solutions* • • • • • • • • • •
•
101.373.064 lines of code 190.646 function modules 98.100 screens 33.786 database tables 32.001 programs (reports) 2500+ interfaces (http://ifr.sap.com) 48+ standalone components 10 operating systems supported 7 databases supported 28 languages
Distributed development • 7967 developers • 9 locations across the globe
•
Broad customer base • • • •
13 Mio end-user 60.100 installations 19.300 customers of all sizes 23 industries
Quelle: Kagermann, H. (2003): The Future of Enterprise Software.
*example based on SAP R/3 Enterprise data as of February 2003
© Prof. Dr. H. Krcmar
Enterprise Software is Complex ! Intransparency
• Many variables • Many states
• Not all necessary information available • Nebulous state of the systems
Amount Momentum
• Acting local may lead to global phenomena
Distant Effects
• Dependancies • Impacts
Enterprise Software Interconnected ness
Diversity of goals
• Changes without direct intervention of an actor
Pressure of time
• Implementation • Releases • Availability
• Many even contradictory goals • Vaguely defined goals • Unknown consequences
© Prof. Dr. H. Krcmar
92
Educating SAP • • • • • •
Trainings by SAP Education In-House Training Customer Competency centres (CCC) Key User Concept E-Learning Design Questions • Who must be trained ? • How much training, which topics/products ? • When to train ? Ongoing vs. continuous training © Prof. Dr. H. Krcmar
Example: Multi-Level Key User Concept
© Prof. Dr. H. Krcmar
93
Enterprise EnterpriseSoftware SoftwareininaaNutshell Nutshell
Hands HandsOn: On:Navigating Navigatingthe theSAP SAP &&Customer Order Management Customer Order Management
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
Different Views upon SAP = Course Roadmap CIO „Why deal with SAP ?“ M. Mohr Dr. Wittges
Dr. Wittges
Application Consultant „How to implement SAP ?“
H. Jehle
Technical Support „What infrastructure does SAP need ?“
End User „How will SAP support my tasks ?“
V. Nicolescu
Service Provider „How to operate and provide SAP Solutions ?“
Technical Consultant „How does SAP work ?“ A. Mors
© Prof. Dr. H. Krcmar
94
Agenda 1. Loggin in and Navigation 2. Exercise: Customer Order Management
© Prof. Dr. H. Krcmar
Loggin LogginIn Inand andNavigation Navigation
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
95
Logging On – SAP Gui
To log on to an R/3 system with the SAP Gui, you need the proprietary SAP Gui (Graphical User Interface) software loaded on your system and an internet connection
Internet Connection SAP System at HCC TU München
PC with SAP Gui
© Prof. Dr. H. Krcmar
Logon Pad
Text description Host name of SAP Server
SAP Router
R/3 System Selected
© Prof. Dr. H. Krcmar
96
Configured SAP Gui
Select System: double -click or Logon button
© Prof. Dr. H. Krcmar
Logging On
Enter Client Enter User (R/3 Account) Enter Password (R/3 Account)
© Prof. Dr. H. Krcmar
97
Password Change
On the first time logging in to a new account, you will have to change the password—try To remember your new Password WITHOUT WRITING IT DOWN!
© Prof. Dr. H. Krcmar
Logging in is easy ... • System: G36 • Client: 901 • User: USER-1-XX (XX from 01 to 20) • password: init à Please enter new password and REMEMBER!! Your password will be valid throughout the entire term!
© Prof. Dr. H. Krcmar
98
SAPGUI •
Screen Features • Title Bar • • • • •
•
Menu Bar Tool Bar Function keys Main body of screen Message line at bottom
Ways to Navigate SAP • Easy Access Menu • Favorites • Transaction codes
© Prof. Dr. H. Krcmar
Sales Salesand andDistribution Distribution --Customer CustomerOrder OrderManagement Management--
Technische Universität München Chair for Information Systems © Prof. Dr. H. Krcmar
99
Business Processes in COM Cycle
1. Pre-Sales Activities
2. Sales Order Processing
3. Inventory Sourcing
4. Delivery 6. Payment 5. Billing Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Customer Order Management Process The SAP R/3 application modules that support most of Customer Order Management processes are:
Sales & Distribution Materials Mgmt.
Materials Management Financial Accounting Controlling Production Planning
Controlling
Production Planning
Fixed Assets Mgmt.
R/3
• Sales and Distribution • • • •
Financial Accounting
Client / Server ABAP/4
Quality Mgmt. Plant Maintenance
Human Resources
Project System
Workflow
Industry Solutions
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
100
Organizational Elements in COM •
The Organizational Elements in Customer Order Management:
West
Company Code
East
Sales Organization
Division
Plant
Storage Location
Warehouse No.
Distribution Channel
Shipping Point
Dr. Raul Enciso, University of California
© Prof. Dr. H. Krcmar
Company Codes • A company code represents an independent accounting unit, for example, a company within a corporate group. • Balance sheets and Profit & Loss statements, required by law, are created at the company code level.
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
101
Sales Organizations • A sales organization: • Is responsible for distributing goods and services. • Is responsible for negotiating sales conditions. • Carries out each business transaction.
• Each sales organization is assigned to a company code and is responsible for sales in its country and sets its own distribution and pricing policies. MSI’s North American sales organizations are defined as: • US # 3000 • Canada # 4000
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Distribution Channels • •
•
Distribution channels are the means through which sales material reach the customer. Distribution channels can include: • Retail trade
• Tele-marketing
• Wholesale trade
• E-commerce
• Direct sales
• etc.
MSI distributes its products through retailers in the US and through direct sales in Canada. Sales Organization Sales Organization US 3000
Canada 4000
Distribution Channels
Distribution Channels
Retail Trade Retail Trade 03 03
Direct Sales Direct Sales 02 02
Dr. Raul Enciso, University of California
Motorcycle Shop 1400
Cycle Concepts © Prof. Dr. H. Krcmar 1300
102
Division • •
A division can be used to segment a business into product lines. In sales and distribution, the division allows you to make customerspecific agreements such as: • Partial deliveries Sales Organization
• Pricing agreements
US 3000
• Special payment terms
•
MSI has 2 divisions in the US which allows MSI to run different promotions for motorcycles and accessories.
Division Division
Division Division
02 02 Motorcycles Motorcycles
90 90 Accessories Accessories
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Sales Area •
A sales area is the combination of three elements: • Sales organizations • Distribution channels • Divisions (product- related)
• •
The sales area is used for reporting and pricing. MSI’s sales area structure for North America is: Sales Organization
3000 US
4000 Canada
Distribution Channel
03 Retail
02 Direct Sales
Division
02 Motorcycles
90 Accessories
02 Motorcycles
90 Accessories
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
103
Plant •
A plant is an organizational element within a company. A plant produces goods, renders services, or makes goods available for distribution.
•
A plant can be one of the following types of locations: • Manufacturing facility
• Regional sales office
• Warehouse distribution center
• Corporate headquarters
•
In the US, MSI has two plants that support the US sales organization.
•
Most of MSI’s products are manufactured and stored in plant 3000. Plant 3400 is available to meet demand for products in the area and serves other areas when needed. Plant 3400 Seattle
Plant 3000 New York
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Shipping Point • •
A shipping point is a fixed location that carries out shipping activities. Each delivery is processed by only one shipping point! MSI has shipping points, one for each plant location. For example, in the US: Plant 3400 Seattle
Plant 3000 New York
Shipping Point
Shipping Point
3400 Seattle
3000 New York
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
104
Master Data The following master data is used in the Customer Order Management cycle: • Customer master • Material master • Condition Pricing Records
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Master Data: Customer Master Customer Sales organization Distribution channel Division
Screen Views
Screen Views
Screen Views
C1 1000 12 00
General Generaldata data Address, Address,Control Controldata, data,Marketing, Marketing, Payment Paymentterms, terms,Unloading Unloadingpoints, points, Foreign Foreigntrade, trade,Contact Contactperson person Sales Salesarea area Sales, Sales,Shipping, Shipping,Billing, Billing,Output, Output, Partner Partnerfunctions functions
Valid Validfor forboth both accounting accountingand andsales sales
Valid Validfor forSales/Distribution Sales/Distribution Dependent Dependentupon: upon: -- Sales Salesorganization organization -- Distribution Distributionchannel channel -- Division Division
Company Companycode codedata data Account Accountmanagement, management,Payment Payment transactions, transactions,Correspondence, Correspondence, Insurance Insurance
© Prof. Dr. H. Krcmar Dr. Raul Enciso, University of California
Valid Validfor foraccounting accounting Dependent Dependentupon: upon: -- Company Companycode code
105
Material Master: Material Master • The material master contains all data required to define and Basic data Purchasing data manage material. Accounting data Sales data Manufacturing data • It integrates data from (etc.) engineering, manufacturing, sales and distribution, purchasing, accounting and other departments. • The material master is used as a source of data for sales order processing throughout the customer order management cycle. Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Material Master Primary Views: COM • • • • • •
Basic Data Material Resource Planning Stocks in Inventory Accounting Storage Warehouse Management
• • • • • •
Purchasing Sales Work Scheduling Quality Management Forecasting Classification
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
106
Condition Pricing Records • Pricing is carried out automatically in R/3 based on predefined prices, discounts, surcharges, freight and taxes. • These records are called condition records and are stored as SD master data
Conditions
Prices • • • •
Price list Material price Customer -specific Other
Discounts / surcharges • • • • • • •
Customer Material Price group Material pricing group Customer pricing group Customer / material Others
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Pre-Sales Activities Pre-Sales activities may include: • • • •
Mailing list Phone call records kept on the system Inquiries Quotations
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
107
Creating Sales Orders The Sales order contains the information necessary to process the Customer Order Management cycle. Order
Delivery
Invoice
Payments
Inventory Sourcing Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Sales Order Processing • Customers place orders with a customer service representative. • Standard orders normally contain: • • • •
Customer and item information Pricing for each item Delivery schedules and information Billing information
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
108
Inventory Sourcing • Inventory sourcing occurs when the order is created or changed (and again when the delivery process begins). • Inventory sourcing determines: • If the product is available (availability checking) • The date the product is confirmed for delivery • How the product will be supplied
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Delivery Creation
Order
Delivery
Invoice
Payments
Inventory Sourcing
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
109
Delivery Overview Within the delivery process the following steps are executed either automatically or manually. Completed Completed Sales Sales Order Order
Availability Availability Check Check
Delivery Delivery Document Document
Pick Pick (through (through aa transfer transfer order) order) & & Pack Pack
Post Post Goods Goods Issue Issue Update Update Inventory Inventory
Warehouse Shipping Shipping
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Deliveries and Shipments FI
WM MM
Sold to party: C100 Item Material Qty 10 6301 10 20 6412 10 30 1507 25
Packing List
Order
•
Upon the creation of the delivery, the customer request starts to be processed in the warehouse.
•
A cost of goods sold and inventory valuation posting is made in financial accounting when goods issue are processed integrating SD with MM and FI. Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
110
Issuing Invoices
Order
Delivery
Invoice
Payments
Inventory Sourcing
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Billing • Billing Supports: • Creating invoices for deliveries and services • Creating credit and debit memos on the basis of requests • Transferring posting data to financial accounting
• Invoicing usually occurs after the product has been shipped to the customer. Invoices • All the information entered for the sales and delivery documents are transferred to the invoice. Staffel Motorcycle Company One order of 16 motorcycles for the Sante Fe store, Price per bike $15,000 times 16 equals $240,000 price is equal to our discussion about the new Feldwebel Bike with 1600cc of horsepower.
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
111
Customer Payment
Order
Delivery
Invoice
Payments
Inventory Sourcing
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
Customer Payment • The final step of the Customer Order Management cycle. • The Customer Payment step includes: • Posting payments against invoices • Reconciling differences, if necessary
• The processing of the customer payment is done in accounts receivable against open items.
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
112
Summary of the Business Process Flow • • • •
Document represent transactions in the R/3 system. The transactions form a chain of related documents. The entire chain of documents creates a document flow. The system copies data from one document into another to reduce data entry and make problem resolution easier.
Order
Delivery
Invoice
Payments
Document Documentflow flowof ofaasales salesdoc. doc. . .. .. ... . .. .. .. .
Order Order Delivery Picking request, Delivery- -Picking request,Goods Goods request, request,Delivery Delivery . .. ..... Invoice Invoice . ....... Accounting Accounting
Dr. Raul Enciso, University of California © Prof. Dr. H. Krcmar
113
