tadm10_1 implementation y operation i

TADM10_1SAP NetWeaver AS

Implementation & OperationI

SAP NetWeaver

Date

Training Center

Instructors

Education Website

Instructor HandbookCourse Version: 72Course Duration: 10 Day(s)Material Number: 50106940Owner: Matthias Esch (D023033)

An SAP Compass course - use it to learn, reference it for work

Copyright

Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX,S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registeredtrademarks of Informix Software Incorporated.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, MultiWin and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, WorldWide Web Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAPEarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g201111162373

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2011 2011 SAP AG. All rights reserved. iii

About This Handbook TADM10_1

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructorspresentation.

iv 2011 SAP AG. All rights reserved. 2011

Contents

Course Overview ......................................................... viiCourse Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Unit 1: The Big Picture.................................................... 1

The SAP Software Portfolio .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3SAP NetWeaver.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SAP Release Strategy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Unit 2: Navigation........................................................ 41

Navigation in SAP Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Advanced Navigation in the SAP GUI... . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Appendix - Personalizing the User Interface ... . . . . . . . . . . . . . . . . . . . 79

Unit 3: The System Core ............................................... 87

Principal Architecture of the SAP NetWeaver AS ... . . . . . . . . . . . . . 90Logon Groups in AS ABAP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115AS ABAP Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Fundamental Concepts of Java ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162AS Java Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Java Cluster Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190The Internal Structure of the AS Java... . . . . . . . . . . . . . . . . . . . . . . . . . .199

Unit 4: Starting and Stopping SAP Systems ..................... 211

System Start: Process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214System Start: AS ABAP and AS ABAP+Java Process ... . . . . . .223System Start: AS Java ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Tools for Starting and Stopping SAP Systems ... . . . . . . . . . . . . . . . .238System Start: AS ABAP Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257Java Startup and Control Framework ... . . . . . . . . . . . . . . . . . . . . . . . . . .263Logs of the Start and Stop Processes of the AS Java ... . . . . . . .274Appendix: Downtime Management.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280

Unit 5: Introduction to System Configuration.................... 289

How the System Evaluates Its Parameters.. . . . . . . . . . . . . . . . . . . . . .291How to set Profile Parameters .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300Setting up Operation Modes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Administration and Configuration Tools of the AS Java... . . . . . .324

2011 2011 SAP AG. All rights reserved. v

Contents TADM10_1

General Configuration of the AS Java Cluster with the ConfigTool.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343

General Configuration of the AS Java Cluster with the VisualAdministrator.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363

Other Administration Tools.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380Selected Configurations... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394

Unit 6: Setting up SSL for AS Java ................................. 415

Setting up SSL ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416

Unit 7: Software Development in SAP Systems ................. 445

Data Structure of an SAP System and Software Logistics .. . . .448Accessing and Editing ABAP Repository Objects .. . . . . . . . . . . . . .462Importing Transport Requests.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .485Introduction to SAP NetWeaver Development Infrastructure

(NWDI).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .493

Glossary................................................................... 519

Index ....................................................................... 521

vi 2011 SAP AG. All rights reserved. 2011

Course OverviewCourse TADM10 is the foundation for various, further training courses forconsultants. After TADM10, you can continue your training either by takingcourse TADM12 to further expand your knowledge of SAP NetWeaver AS, or bytraining to become a (Technical) PI or Portal Consultant.

This training content is largely independent of the type of operating system anddatabase technology.

Like the other TADM courses, TADM10 comprises several individual courses (orparts thereof), which are arranged here in a way that will enable you to gain theknowledge you require as an SAP Technology Consultant as efficiently as possible.

Week 1 of course TADM10 is based on content taken from the followingcourses:

1. SAPTEC

2. ADM100

3. ADM200

Week 2 of course TADM10 is based on content taken from the followingcourses:

1. SAPTEC

2. ADM100

3. ADM102

4. ADM200

Target Audience

This course is intended for the following audiences:

SAP Technology Consultants (Associate Level)

Course Prerequisites

Required Knowledge

Basic knowledge of IT

Basic knowledge of operating systems and databases

Course Duration DetailsUnit 1: The Big PictureThe SAP Software Portfolio 60 MinutesSAP NetWeaver 20 Minutes

2011 2011 SAP AG. All rights reserved. vii

Course Overview TADM10_1

SAP Release Strategy 30 MinutesExercise 1: SAP Release Strategy 5 Minutes

Unit 2: NavigationNavigation in SAP Systems 40 MinutesExercise 2: Logon and Screen Design 10 MinutesAdvanced Navigation in the SAP GUI 45 MinutesExercise 3: Calling Functions 30 MinutesAppendix - Personalizing the User Interface 0 Minutes

Unit 3: The System CorePrincipal Architecture of the SAP NetWeaver AS 60 MinutesExercise 4: Structure of an Instance 15 MinutesLogon Groups in AS ABAP 20 MinutesExercise 5: Setting Up Logon Groups 10 MinutesAS ABAP Processes 80 MinutesExercise 6: Dialog Processing 5 MinutesExercise 7: Optional: Lock Management 10 MinutesExercise 8: Optional: Update Processing 5 MinutesExercise 9: Printing 10 MinutesExercise 10: Background Processing 10 MinutesFundamental Concepts of Java 25 MinutesAS Java Processes 60 MinutesJava Cluster Architecture 20 MinutesThe Internal Structure of the AS Java 15 Minutes

Unit 4: Starting and Stopping SAP SystemsSystem Start: Process 30 MinutesSystem Start: AS ABAP and AS ABAP+JavaProcess 30 Minutes

System Start: AS Java 10 MinutesTools for Starting and Stopping SAP Systems 30 MinutesExercise 11: Starting and Stopping the SAP System 15 MinutesSystem Start: AS ABAP Logs 30 MinutesJava Startup and Control Framework 35 MinutesExercise 12: Optional: Java Startup and ControlFramework 10 Minutes

Logs of the Start and Stop Processes of the AS Java 15 MinutesExercise 13: Logs of the Start and Stop Processesof SAP NetWeaver AS Java 10 Minutes

Appendix: Downtime Management 30 Minutes

Unit 5: Introduction to System ConfigurationHow the System Evaluates Its Parameters 40 MinutesExercise 14: Configuration of Profile Parameters 10 MinutesHow to set Profile Parameters 40 MinutesExercise 15: Maintaining the System Parameters 15 MinutesSetting up Operation Modes 40 Minutes

viii 2011 SAP AG. All rights reserved. 2011

TADM10_1 Course Overview

Exercise 16: Setting up Operation Modes 15 MinutesAdministration and Configuration Tools of the ASJava 50 MinutesExercise 17: Administration and Configuration Toolsof SAP NetWeaver AS Java 15 Minutes

General Configuration of the AS Java Cluster withthe Config Tool 90 MinutesExercise 18: General configuration of SAPNetWeaver AS Java with the Config Tool 25 Minutes

General Configuration of the AS Java Cluster withthe Visual Administrator 50 MinutesExercise 19: General Configuration of the SAPNetWeaver AS Java Cluster with the VisualAdministrator 20 Minutes

Other Administration Tools 40 MinutesExercise 20: Other Administration Tools 10 MinutesSelected Configurations 110 MinutesExercise 21: Selected Configuration 15 Minutes

Unit 6: Setting up SSL for AS JavaSetting up SSL 60 MinutesExercise 22: Setting up SSL 15 Minutes

Unit 7: Software Development in SAP SystemsData Structure of an SAP System and SoftwareLogistics 50 Minutes

Accessing and Editing ABAP Repository Objects 75 MinutesExercise 23: Accessing and Editing ABAPRepository Objects 30 Minutes

Importing Transport Requests 60 MinutesIntroduction to SAP NetWeaver DevelopmentInfrastructure (NWDI) 50 Minutes

Course GoalsThis course will prepare you to:

Work as an Associate Consultant (Junior Consultant) within the SAPtechnology environment

Configure and manage SAP NetWeaver AS ABAP

Configure and manage SAP NetWeaver AS Java

Course Objectives

After completing this course, you will be able to:

Process basic tasks within the technology environment of SAP systems

2011 2011 SAP AG. All rights reserved. ix


Caution: This instructor guide contains all information available as atDecember 2011.

To obtain the latest information, you must read the Add-OnInstructor Guides in Collection 72 for courses TADM10, SAPTEC,ADM100, ADM102, and ADM200, which are available athttp://service.sap.com/curr-adm. If there is no such document for aparticular course, the information contained in this Instructor Handbookis still valid.

In preparation for this course, you require the following documents, which areavailable at http://service.sap.com/curr-adm and supplement this InstructorHandbook:

1. The Training System Info document

This document provides general information about the layout of the trainingsystems and the password for the main user systemsetup. Use this user to setup the training systems through eCatt as described in the next document.

2. The System Setup Guide

This document describes in detail how, in just a few steps, you can usenumerous eCATT scripts to prepare all of your training systems for thistraining course for consultants.

3. The Add-On IG documents for all aforementioned contained separatecourses

Note that a separate Add-On IG document may exist for each containedcourse. If these documents exist, you must read them.

At the start of each unit in this training course, you will find an instructornote telling you which course originally provided the information nowcontained in that unit.

4. The Add-On IG document

If, after completing this Instructor Handbook, you require further informationabout teaching this training course, an Add-On IG will also be created forthis course and stored in the aforementioned location.

x 2011 SAP AG. All rights reserved. 2011

TADM10_1 Course Overview

Some additional information in relation to teaching TADM10 is provided below.

1. Take some time to discuss the content taken from course SAPTEC becausemost of the course participants will be using an SAP system for the first time.

Depending on the level of knowledge among participants, you may be ableto discuss the section on navigation more quickly.

Always discuss Unit 3 (The System Kernel) at length because all threelessons contain certification-relevant information. They introduce the basicconcepts of SAP technology, which are the key to understanding the rest ofthis training course.

Once again, take some time to discuss the unit on Software Development inSAP Systems because only some of the course participants will cover this inmore detail in course TADM12. Some participants will continue along thepath to becoming Portal Consultants or PI Technology Consultants and willobtain their first overview of general software logistics topics here.

Below you will find some recommendations in relation to the preparatory stepsfor teaching this course.

To be prepared as best as possible for teaching (whatever course), werecommend the following strategy:

4 weeks before the course: Contact your training department and make sure thatthe course will take place. They may not be able to give you final confirmationuntil two weeks before the course. Nevertheless, proceed with the preparatorysteps as if the course were going to take place. Also, make sure that you receive ahard copy of the Instructor Handbook for the course that you are about to teach.Carefully read the Add-On Instructor Notes available on SAP Service Marketplaceat /curr-adm as well as the documents listed above.

3 weeks before the course (at the latest!): Ask your training department to ordera preparation system for you, if needed. Since preparation systems are billedagainst the training department (for each week), it looks likely that you will get apreparation system for one week only. I recommend that you use this preparationsystem during the week before the course takes place. Preparation systems needto be ordered (at the latest!) by Thursday noon (WDF time) before the weekyou need them.

2 weeks before the course: You are still working on the course material, InstructorGuide, Add-On Instructor Guide, corresponding documentation, and so on.

1 week before the course: This week, you will have access to a "real" preparationsystem (if you ordered one two weeks earlier). If you have some final questionsin relation to the course, you can contact the owner of the course (whose contactdetails are provided in the Instructor Handbook for the course).

2011 2011 SAP AG. All rights reserved. xi


Caution: Additional instructor information is provided at the start ofthe relevant unit.

xii 2011 SAP AG. All rights reserved. 2011

Unit 11 The Big Picture

Note: TADM10: This unit is taken from course SAPTEC.

Below you will find the original instructor note for this unit in courseSAPTEC.

In this section, the participants should learn to evaluate how the primary coursefocus (SAP NetWeaver Application Server) relates to the rest of the SAPsolutions (SAP NetWeaver, SAP Business Suite,...).

Experience has shown that these topics are usually subject to frequent changessuch as renaming, and so on. It is not always easy for customers and SAPemployees alike to keep track of all changes. These materials were last updated inQ3 2011. You can use the following addresses to keep yourself uptodate:

https://service.sap.com/releasestrategy

http://smart.sap.corp:1080/smart

First of all, a lesson deals with the distinction between applications andcomponents. Here it should be made clear that a SAP application (previouslysolution) technically consists of several components (SAP systems). After that,it is pointed out that all SAP applications are based on the same technologyand integration platform: SAP NetWeaver. Do not deal with the individualSAP NetWeaver components in too much detail but make it clear that theSAP NetWeaver AS is a central part of almost every SAP system. That is, thefunctionality discussed in the course will usually be available in many SAPsystems in the company. In the last lesson of the unit, we will try to documentthe SAP release strategy in a customer course. We strongly recommend that theinstructor closely monitors updates or changes to the release strategy and mentionsthem in the course, if necessary.

Unit OverviewThis unit provides an overview of the SAP solutions first. You will then learnmore about SAPs release strategy. Finally, we will talk about the application andintegration platform SAP NetWeaver.

2011 2011 SAP AG. All rights reserved. 1

Unit 1: The Big Picture TADM10_1

Unit ObjectivesAfter completing this unit, you will be able to:

List the key components of the SAP solutions

Explain the differences between an application and a component

Explain the basic concept of SAP NetWeaver

Describe the central role played by the SAP NetWeaver Application Server

Describe the SAP software delivery process

Explain the SAP maintenance strategy

Find out when SAP software releases will become available

Unit ContentsLesson: The SAP Software Portfolio .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Lesson: SAP NetWeaver .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Lesson: SAP Release Strategy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Exercise 1: SAP Release Strategy... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35


TADM10_1 Lesson: The SAP Software Portfolio

Lesson:

2

The SAP Software PortfolioLesson Duration: 60 Minutes

Lesson OverviewThis unit provides an introduction to the structure of SAPs software solutions, atthe center of which is the SAP Business Suite.

Lesson ObjectivesAfter completing this lesson, you will be able to:



The aim of this introductory lesson is to provide participants with an overview ofthe SAP software portfolio. Some advantages are also introduced here. Make surethat, as part of this lesson, you show the participants the introduced areas on theSAP homepage: http://www.sap.com.

Note that the product coverage of this lesson is by far not complete: We omitted theSAP BusinessObjects portfolio as well as many smaller solutions and products.

Business ExampleYour company plans to introduce SAP software. You, as a member of the projectteam, need an overview of the entire SAP portfolio.

SAP Strategy at a GlanceThe overall goal for SAP is to deliver instant value to organizations and peopleeverywhere by expanding its solution portfolio with innovations that reach out tothe many people that need IT in their daily work and daily life, while maintainingmaximum consistency of data, processes, and applications. Therefore, SAPfocuses on the following key areas:



Figure 1: SAPs Key Areas

Scale the Customers Core Business (On Premise)

SAP plans to continue to evolve and strengthen its core business of providingsolutions for all industries and market segments. The offered solutions willscale the customers core business and deliver instant value to them. To easethe consumption of these solutions, they will be as preintegrated as possible andable to be implemented in a nondisruptive way, and they will be developed usingtimeless software principles such as decoupling, layering, componentization,abstraction, and design.

Via service-oriented architecture (SOA), other independent solutions will be ableto integrate consistently with the customers core business processes.

One major deliverable within this area, SAP Business Suite 7 software, is alreadyavailable, and more are planned to follow in the next years.

Innovate via Extensions (On Demand)

Besides offering solutions that scale the customers core business, SAP plans toprovide rapid innovations that deliver extended functionality for a specific lineof business.

These extensions will be delivered on demand. In this way, customers canconsume the innovations instantly without the need for on-site IT to manage theinfrastructure.

As these extensions will integrate smoothly with the customers core businessprocesses, customers will benefit from end-to-end business process integration.



Extend Our Customers Reach (On Device)

In addition, SAP intends to extend the customers reach by:

Enabling end users to consume SAP data and processes from differentdevices everywhere (SAP applications for mobile business)

Providing end users with information from both inside and outside theenterprise so that they can make decisions based on a broad array of dataaccording to their individual use case (analytical capabilities)

Helping end users to cooperate and optimize performance across a dynamicbusiness network of people (tools for collaboration)

Enabling partners, customers and end-users to extend the functionality ofSAP and build own user experiences.

Orchestration

To ensure that all these layers fit together perfectly, an orchestration layer thatworks across all applications within a customer landscape is required. Therefore,SAP plans to continue to invest in the areas of lifecycle management, masterdata management, and process orchestration. The goal is to reduce the costof ownership continuously and to help ensure data consistency and processmanagement across multiple layers of applications.

Offers for Companies of All SizesSAP offers a vast range of products for companies of all sizes. SAP has scalableproducts, ensuring that they can be adjusted to any size and adaptable to thecontinuously changing processes of a company.

Figure 2: Different Sizes Different Products

The following offerings are available to small and mid size business customers:



SAP Business One

SAP Business One is a comprehensive, integrated ERP application with aninterface similar to Windows, which has been developed specifically for small andmidsize companies. It distinguishes itself by simple navigation and expansionoptions, innovative Drag&Relate functions as well as integration with MicrosoftWord and Excel. The software enables you to uniformly manage the mostimportant business areas such as sales, distribution and finances with one single,integrated application. This enables SAP Business One to provide an up-to-dateoverview of your companys most important data at any time. This informationhelps you meet customer requirements even more quickly, which is an importantprerequisite for profitable growth.

SAP Business One is the ideal solution for small companies with up to 100employees who are looking for an affordable system that covers their coreprocesses (such as finance, sales, customer service and operations), thus ensuringsuccessful and profitable operations. The solution can be used as a local softwareor hosted by a partner with an average implementation time of less than twomonths. SAP Business One is sold exclusively through a global partner networkof currently 1,150 certified and experienced partners. They offer 24 hour support,which also covers the more than 550 enhancements from independent softwareproviders. SAP Business One is currently being used by more than 20,000customers in over 40 countries.

Hint: For more, see http://www.sap.com/solutions/sme/businessone.

Note that SAP Bussines One is not powered by SAP NetWeaver.

SAP Business ByDesign

SAP Business ByDesign is SAPs latest solution for small and midsize companieswith between 100 and 500 employees, who want to use an on-demand solution toimprove their core processes and at the same time benefit from lower entry andoperating costs. It is aimed, in particular, at midmarket companies who are notyet using integrated business software.

The solution combines the advantages of an integrated, end-to-end applicationwith the low risk potential and the low total operating costs of an on-demandsolution. An on-demand solution that distinguishes itself through integratedservice and support, adaptability and more user friendliness and also guaranteestransparency and the observation of legal requirements all this on the basis of anEnterprise SOA by design. SAP Business ByDesign is the most complete, fullyintegrated on-demand solution. More than a pure niche solution, it supports therequirements of midsize companies in all areas such as effective management



of finances, human resources, projects, production as well as supplier andcustomer relationship management and regional and local legal requirements,and compliance management as core design principles. It was not developedwith the traditional categories of business applications or customer relationshipmanagement and others. Instead, it was developed for business processes in theentire company with user interfaces that are customized to the user roles. SAPBusiness ByDesign offers end-to-end processes for the work center of the future.

Hint: For more, see http://www.sap.com/solutions/sme/businessbydesign.

Note that SAP Bussines ByDesign is powered by SAP NetWeaver, but notbased on the SAP Business Suite.

SAP Business All-in-One

All software has to be adapted to the specific company. A midsize company withfew employees and comparatively stable processes can use preconfigured SAPsystems. SAP All-in-One is the brand name for vertical (industry-specific orcountry-specific) applications that are based on the technology of SAP NetWeaverand were developed in conjunction with SAPs partners.

SAP Business All-in-One is the ideal solution for small and midsize companies(up to 2,500 employees) with very industry-specific requirements who haveseveral divisions and a mature IT infrastructure. The software lets you deploy coreenterprise resource planning (ERP), customer relationship management (CRM),and business intelligence functionality. It also allows you to leverage the bestpractices of industry leaders all at an affordable fixed price on a platform yourbusiness will not outgrow.

The solution can be used as a local software or hosted by a partner and it is basedon a variety of SAP products (with a focus on SAP ERP, SAP CRM and the SAPBusiness Objects Portfolio). It provides an industry-specific function portfoliobased on SAP Best Practices. SAP Business All-in-One is affordable and canbe planned and, thanks to preconfigured business scenarios and implementationaccelerators, it can be implemented quickly (8 to 16 weeks).

Today more than 13,000 small and midsize customers in more than 50 countriesrun SAP Business All-in-One. You can rest assured that SAP, as one of the worldsleading providers of business software, will be around for a long time to come.More than 1,000 SAP partners around the world deliver local implementation andcustomization support for SAP Business All-in-One, giving you access to expertassistance no matter where you are located.

Hint: For more, see http://www.sap.com/solutions/sme/businessallinone.



Note that SAP Bussines All-in-On is powered by SAP NetWeaver and basedon (SAP ERP and SAP CRM parts of) the SAP Business Suite and the SAPBusiness Objects Portfolio).

Profile of SAPs SME Solutions

The following table shows a comparison of SAPs offerings for small businessesand midsize companies:

SAP Business One SAP BusinessByDesign

SAP BusinessAll-in-One

Overview A single, integratedapplication tomanage an entirebusiness

Single, integratedbusinessmanagementsolution deliveredas software as aservice (SaaS)

A comprehensive,integrated industrysolution to power abusiness end to end

Best fit forcompaniesthat...

Have outgrownpackagedaccountingonlysoftware and needto replace multiple,nonintegratedapplications

Need to replacepoint solutions,manual processes,and spreadsheets

Have outgrownpoint solutions,legacy or customapplications,or current ERPsoftware

Have currentsolutions thatmay not meetindustry-specificrequirements or thatlack cross-borderfunctionality

Are experiencingincreasing businessprocess complexityand need systemsthat can scale tomeet growth plans

Companysize

Up to 100 100500 Up to 2,500



SAP Business One SAP BusinessByDesign


Availability Available in 40countries, 20languages

Available in theUnited States,Germany, France,the UnitedKingdom, China,and India

Available in 50countries

IT staff andcapabilities

Have limited oroutsourced ITresources

Have limited oroutsourced ITresources

Have in-house ITstaff

Deploy-ment model

On premise orhosted by partner

On demand On premise orhosted by partner

Implemen-tation time

Approximately 68weeks

Approximately 48weeks

Approximately816 weeks

SAP Business Suite in DetailThe SAP Business Suite is an extended family of business applications thatenables companies to manage their entire value chains. The included businessapplications provide users with consistent results throughout the entire companynetwork and give your company the flexibility it needs in todays dynamic marketsituations. The application consists of a number of different products that supportcross-company processes.

Hint: For more, see http://www.sap.com/solutions/business-suite.

SAPs software portfolio is constantly extended, optimized, and tailored to theneeds of the market and of customers. SAP has therefore, for example, developedmany industry-specific applications over the years. The topic of integratingdifferent business systems (even from different vendors and across companyboundaries) has become increasingly important recently. Products for small tomidsize businesses have also been added to SAPs family of software solutions.

The SAP Business Suite, a complete business software package that is uniqueworldwide, plays a central role. Many companies are already profiting from thecomprehensive and flexible business applications with highly evolved functions:complete integration, industry-typical functions, unlimited scalability and smoothcollaboration via the internet.



The SAP Business Suite provides:

A complete spectrum of business solutions

A technological infrastructure that combines openness and flexibility withmaturity and stability

Interfaces for integrating non-SAP products

Components that can be adapted to meet multiple business requirements

Numerous industry-specific functions

The next graphic illustrates the key components of the SAP Business Suite:

Figure 3: SAP Business Suite: Architecture

The components that make up SAP Business Suite are described in the followingsections.

Core Applications

The core applications of SAP Business Suite are a set of business applications thatsupport all the essential business processes of an enterprise. They are summarizedhere.

SAP ERP is a market-leading application for optimizing business and IT byreducing IT complexity, increasing adaptability, and delivering more IT valueat a lower cost than traditional enterprise resource planning (ERP) solutions.It supports mission-critical, end-to-end business processes for finance, humancapital management, asset management, sales, procurement, and other essentialcorporate functions. SAP ERP also supports industry-specific processes by



providing industry-specific business functions that can be activated selectivelyvia the switch framework, which keeps the application core stable and helps toensure maximum performance.

Hint: For more, see http://www.sap.com/solutions/business-suite/erp.

The SAP Customer Relationship Management (SAP CRM) applicationprovides a comprehensive platform for marketing, sales, and service professionalsto obtain complete customer intelligence that they can leverage to effectivelymanage customers and customer-related processes. SAP CRM enablesmultichannel customer interactions, including mobile smart phones, the internet,and social media, and also offers a dedicated communications infrastructure thathelps to connect all users anytime, anywhere.

Hint: For more, see http://www.sap.com/solutions/business-suite/crm.

The SAP Product Lifecycle Management (SAP PLM) application helpscompanies manage, track, and control all product-related information over thecomplete product and asset lifecycle as well as throughout the extended supplychain. SAP PLM facilitates creativity and frees the process of product innovationfrom organizational constraints.

Hint: For more, see http://www.sap.com/solutions/business-suite/plm.

The SAP Supplier Relationship Management (SAP SRM) application providesa procurement platform that helps organizations in all industries improve theircentralized sourcing and contract management and interact with suppliers throughmultiple channels. SAP SRM accelerates and optimizes the entire end-to-endprocure-to-pay process by supporting integrated processes and enforcing contractcompliance, resulting in realizable savings.

Hint: For more, see http://www.sap.com/solutions/business-suite/srm.

The SAP Supply Chain Management (SAP SCM) application allowscompanies to adapt their supply chain processes to an ever-changing competitiveenvironment. SAP SCM transforms traditional supply chains from linear,sequential processes into open, configurable, responsive supply networks inwhich customer-centric, demand-driven companies can sense and respond moreintelligently and more quickly to demand-and-supply dynamics across a globallydistributed environment.

Hint: For more, see http://www.sap.com/solutions/business-suite/scm.



Industry Applications

SAP addresses the requirements of specific business processes for many industriesby complementing the basic business processes common to all large enterprises.Support for these industry-specific processes is delivered as part of SAP ERPor as a separate industry application (for example, the SAP Dealer BusinessManagement application or the SAP Reinsurance Management application) thatintegrates with the other applications of SAP Business Suite. The architecture andbusiness functionality of the industry applications are a result of SAPs in-depthunderstanding of industry-specific business requirements and the resultingbusiness processes. SAP industry portfolios are continuously enhanced by addingnew applications that address the highly specialized business needs of customersin very targeted markets.

The following table lists the industry portfolio (as of Q3 2011):

Industry Sector Industry Portfolio

Discrete Industries SAP for Aerospace & DefenseSAP for AutomotiveSAP for Engineering, Construction & OperationsSAP for High TechSAP for Industrial Machinery & Components

Process Industries SAP for ChemicalsSAP for Life SciencesSAP for Mill ProductsSAP for MiningSAP for Oil & Gas

Consumer Industries SAP for Consumer ProductsSAP for RetailSAP for Wholesale Distribution

Service Industries SAP for MediaSAP for Professional ServicesSAP for TelecommunicationsSAP for Transportation & LogisticsSAP for Utilities

Public Services SAP for Defense & SecuritySAP for HealthcareSAP for Higher Education & ResearchSAP for Public Sector

Financial Services SAP for BankingSAP for Insurance



Supplementary Applications

Supplementary applications include applications that drive specialized businessprocesses common to a large number of industries. They deliver a short time tovalue, appeal to specialized business users, and offer a high degree of processflexibility. Supplementary applications include, for example, manufacturingapplications, SAP solutions for auto-ID and item serialization, and applications formobile business.

SAP NetWeaver

The SAP NetWeaver technology platform is the reliable, secure, and scalablefoundation to run business applications like SAP Business Suite and SAPBusinessObjects applications to help ensure that large enterprises canperform mission-critical business processes. As the technical foundation forservice-oriented architecture, SAP NetWeaver delivers a comprehensive setof middleware functions in a modular software environment with the aim ofreducing IT complexity and increasing business flexibility across heterogeneousIT landscapes. SAP NetWeaver provides IT organizations with the lowest cost ofoperation and best business availability for SAP applications across heterogeneousIT landscapes through unified lifecycle management, identity management, securecommunications, and end-to-end monitoring.

Enhancement Packages

Enhancement packages for innovation without disruption: SAP has a proven wayto continuously deliver innovation for SAP Business Suite and SAP NetWeaverwithout disruption. It comes in the form of enhancement packages that providecollections of new or improved business functions that companies can deployin a modular fashion and on their own timetable. The strategy of enhancementpackages enabling companies to take advantage of ongoing innovations whilekeeping their core software stable was introduced with the SAP ERP 6.0application and has been proven with several enhancement packages since 2006.

All core applications of SAP Business Suite are now enabled for continuousinnovation through enhancement packages. In the future, SAP intends to continueto deliver enhancement packages for the core applications, minimizing the needfor companies to engage in potentially disruptive upgrade projects.

SAP Licensing ModelSAP aims to offer software licenses that provide comprehensive solutions forbusiness scenarios. SAP has therefore grouped applications that support corebusiness processes into solution portfolios that serve the needs of customers in 24industries. Each application within a portfolio has a clear connection to one ormore business scenarios of the respective industry solution map provided by SAP.



Figure 4: SAP Licensing Model

SAP licenses its software through a combination of package licenses andnamed user licenses. Package licenses entitle a licensee to deploy and use thespecified software functionality, provided that the appropriate users accessingthe functionality are licensed as well. Every user accessing the package licenseneeds to have the appropriate named user license. SAP offers several usercategories that depend on the role of the individual user. Additionally, some SAPBusinessObjects solutions may be licensed flexibly based on number of users andother metrics dependent on the solution.

There are three main categories in SAPs license portfolio: SAP Business Suite(including industry portfolios, enterprise extensions, and enterprise foundation),SAP BusinessObjects solutions, and SAP NetWeaver. For each category, SAPoffers a set of package licenses that permit the use of the respective software.Note that the three main categories correspond to the main sections of SAPsprice list they do not necessarily correspond to the technical solution view. Forexample, a package license for SAP Business Suite may include use rights forapplication components that, from a technical solution perspective, are branded asSAP NetWeaver.



Context of Applications and ComponentsNumerous applications for business challenges are provided in the context ofthe SAP Business Suite. However, many applications have similar or identicalrequirements for business functions in subareas. Different applications thereforecontain similar (software) components in parts. A component is the smallest,separately producible, deliverable, installable, and maintainable software unit.

Components refer to, for example, an SAP ECC system, an SAP SCM system oralso an SAP NetWeaver Portal system. The graphic provides an overview ofthis hierarchy (components as building blocks of solutions) using the SAP SCMapplication as the example.

Figure 5: Applications and Components



Facilitated DiscussionHighlight the possibilities offered by SAP Business Suite.

Discussion QuestionsUse the following questions to engage the participants in the discussion. Feel freeto use your own additional questions.

Which of the opportunities offered by the SAP Business Suite will you actuallyuse in your company?



Lesson Summary

You should now be able to:



Related Information

For more information, see the following SAP internet sites. All of these sites arefreely available, a few require you to register free of charge.

Please draw the participants attention to the Web site of your local SAPsubsidiary, for example: http://www.sap.de.

SAP Global Homepage, http://www.sap.com

SAP Help Portal, http://help.sap.com

SAP Service Marketplace, https://service.sap.com

SAP Info, http://www.sap.info

SAP Insider Online, http://www.sapinsideronline.com



Lesson:

15

SAP NetWeaverLesson Duration: 20 Minutes

Lesson OverviewThis lesson explains the central role of the SAP NetWeaver Application Server inSAP NetWeaver.




This lesson is very important because it explains the SAP NetWeaver and SAPNetWeaver Application Server technology to the participants.

Business ExampleYou want to find out more about SAP NetWeaver and the role that the SAPNetWeaver Application Server (SAP NetWeaver AS) plays in SAP NetWeaver.

SAP NetWeaverThe SAP NetWeaver technology platform is the reliable, secure, and scalablefoundation to run business applications like SAP Business Suite and SAPBusinessObjects applications to help ensure that large enterprises canperform mission-critical business processes. As the technical foundation forservice-oriented architecture, SAP NetWeaver delivers a comprehensive setof middleware functions in a modular software environment with the aim ofreducing IT complexity and increasing business flexibility across heterogeneousIT landscapes. SAP NetWeaver provides IT organizations with the lowest cost ofoperation and best business availability for SAP applications across heterogeneousIT landscapes through unified lifecycle management, identity management, securecommunications, and end-to-end monitoring.

NetWeaver provides customers with a flexible way to integrate and extendbusiness processes that run across SAP, SAP -certified partner, and custom-builtapplications by delivering prebuilt integration content and enterprise services, withrapid deployment supported by model-driven tools. With support for businessprocess management, mission-critical business processes can be monitored for


TADM10_1 Lesson: SAP NetWeaver

efficiency, integrity, and security. Business users can also use SAP NetWeaverto define business rules to help ensure consistent processes across the businessnetwork.

SAP NetWeaver integrates and connects people, information and businessprocesses across technologies and companies. It enables companies to adjustto changes quickly. SAP NetWeaver ensures that a companys crucial businessprocesses are reliable, safe and scaleable. Furthermore, SAP NetWeaver enablescompanies to maximize the benefits from the current software and systems.Non-uniform integration technologies are consolidated and predefined businesscontent is provided thus reducing the amount of manual work required. SAPNetWeaver is based on a technology using industry standards and can be enhancedwith popular development tools.

IT Practices and IT Scenarios

Figure 6: SAP NetWeaver: Technoloy Map Edition 2010

With SAP NetWeaver 7.0, SAP departs from the layered structure of SAPNetWeaver and moves towards IT practices and scenarios.

To launch the interacive version, open SAP Developer Network, Quick Link/irj/sdn/nw-products and follow the link to the SAP NetWeaver Technology Map.

Note: Starting with SAP NetWeaver AS 7.1x, the IT scenarios werecompletly removed...



SAP NetWeaver enables you to implement IT processes in a range of solutionmethods, called IT practices. For each practice, SAP NetWeaver supports a rangeof key IT activities, which can be performed using the integrated components ofthe platform. The focus here is not on system and technological components buton the IT and business goals of the company. IT practices enable you to reach yourcompanys goals in individual and manageable projects, that is, in sequential stepsand according to their importance. IT practices refer to, for example, the increaseof user productivity through improved, cross-company collaboration, personalizedaccess to applications and data and optimized knowledge management. ITpractices show how SAP NetWeaver can be used to solve certain IT problemsby means of IT scenarios. For each IT practice, SAP NetWeaver suppliescorresponding IT scenarios, which act as implementation guides.

The aim of the IT scenarios is to help you as a customer, partner or serviceprovider with the installation, configuration and operation of SAP NetWeaver aswell as the operation of SAP applications, customer-specific applications and theimplementation of your defined IT scenarios.

SAP NetWeaver Layers and Key Capabilities

The correct term: The four SAP NetWeaver layers consist of central functions(such as the portal). Key components like the SAP NetWeaver Portal providethese central functions.

Note: All SAP NetWeaver component like the Portal, for example, havethe name SAP NetWeaver as the prefix since the SAP NetWeaver Release7.0. That is, the SAP Enterprise Portal is now called SAP NetWeaverPortal

SAP NetWeaver Component Previous Designation

SAP NetWeaver SAP Basis

SAP NetWeaver Application Server SAP Web Application Server

SAP NetWeaver Mobile SAP Mobile Infrastructure

SAP NetWeaver Portal SAP Enterprise Portal

SAP NetWeaver Business Intelligence*)

SAP Business Information Warehouse

SAP NetWeaver Process Integration SAP NetWeaver ExchangeInfrastructure

SAP NetWeaver CompositeApplication Framework

SAP Composite ApplicationFramework

*) renamed to SAP NetWeaver Business Warehouse in later releases arentwe funny?



Figure 7: SAP NetWeaver: Key Capabilities

People Integration

People Integration brings together the right functionality and the rightinformation to the right people.

Multi-channel access: SAP NetWeaver Mobile Provides afuture-proof mobile runtime environment based on open and flexibletechnology standards and a powerful development environment forbuilding integrated mobile solutions with native or browser-baseduser interfaces

Portal: SAP NetWeaver Portal Unifies critical information andapplications to give users role-based views that span the enterprise,enabling you to take full advantage of your information resources

Collaboration: With the collaboration capabilities, SAP NetWeaverallows communication and collaboration in the portal. This allows SAPNetWeaver to bring together members of project groups regardless oftime and of their geographic location. Users can use virtual rooms forcommon access and organization of documents, applications, and ideas.



Information Integration

Information integration provides your company with both structured andunstructured information that is consistent and accessible: Users haveconstant access to consistent information, no matter where it is stored.

Business Intelligence: SAP NetWeaver Business Warehouse Enablesyou to integrate data from across the enterprise and transform it intopractical, timely business information to drive sound decision making

Knowledge Management: With its Knowledge Managementcapabilities, SAP NetWeaver Portal provides a central, role-specificpoint of entry to unstructured information from various data sources.This unstructured information can exist in different formats such as textdocuments, presentations, or HTML files.

Master Data Management: SAP NetWeaver Master DataManagement Ensures cross-system data consistency and helpsintegrate business processes across the extended value chain

Process Integration

SAP NetWeaver Process Integration Delivers SOA-based technology thatsupports process-centric integration across the extended value chain

Integration Broker: With the Integration Broker, integrationknowledge is shipped in the form of pre-defined integration scenarios.Furthermore, the Integration Broker provides a set of integrated toolsfor creating and managing all integration-relevant information

Business Process Management: Provides tools to help you model,execute, and monitor business processes based on a single, consistentprocess model

Application Platform

The SAP NetWeaver Application Server provides a complete developmentinfrastructure on which you can develop, distribute, and executeplatform-independent, robust, and scalable Web services and businessapplications.

J2EE: Support for Java 2 Platform Enterprise Edition (J2EE) fordeveloping Java-based business applications

ABAP: ABAP is a programming language developed by SAP todevelop business applications.

DB and OS Abstraction: The SAP NetWeaver Application Serversupports a variety of databases and operating systems

Beyond these four layers and in parallel to them, SAP NetWeaver offers LifecycleManagement and the Composite Application Framework:



Lifecycle Management

Lifecycle Management supports design, development, deployment andchange management of the entire solution and thus meets the requirementsin the security, design and modeling, testing and systems environmentmanagement areas.

Composite Application Framework

The Composite Application Framework (CAF) is integrated into SAPNetWeaver and enables SAP and its partner to use tools, frameworks, rulesand methods to create new applications that are based on business processesacross function areas.

SAP NetWeaver Application Server (SAP NetWeaverAS)Almost every SAP system is based on SAP NetWeaver AS and uses it as theruntime environment. Together with the database, SAP NetWeaver AS is theapplication platform of SAP NetWeaver.

Figure 8: SAP NetWeaver AS as the Basis for SAP Systems



Figure 9: SAP NetWeaver Application Server

SAP NetWeaver AS is the logical result of the further development of theSAP Application Server Technology (previously: SAP Basis), whereby specialattention is paid to web-based applications.

SAP NetWeaver AS offers:

A reliable and extensively tested runtime environment, which has beendeveloped further continuously over more than ten years

A framework for executing complex business processes that meet the highestsecurity standards

A reliable and user-friendly development environment

Support for open standards, including HTTP, HTTPS, SMTP, WebDAV,SOAP, SSL, SSO, X.509, Unicode, HTML, XML and WML

High scalability

Support for different operating system and database platforms



Since the applications delivered by SAP do not always require both runtimeenvironments, that is, ABAP and Java, there are different installation options forSAP NetWeaver AS. These are:

SAP NetWeaver AS ABAP: Complete infrastructure in which ABAP-basedapplications can be developed and used.

SAP NetWeaver AS Java: Complete infrastructure in which J2EE-conformapplications can be developed and used.

SAP NetWeaver AS ABAP+Java (dual stack): Complete infrastructure inwhich ABAP-based and J2EE-based applications can be developed and used.

Note that future versions of SAP NetWeaver will not support dual stackinstallations, anymore.



Facilitated DiscussionThe discussion should illustrate the strengths and advantages of SAP NetWeaver.

Discussion QuestionsUse the following questions to engage the participants in the discussion. Feel freeto use your own additional questions.

Which advantages do SAP customers gain by using SAP NetWeaver?



Lesson Summary




Related Information

http://www.sap.com/netweaver

SAP Developer Network, Quick Link /irj/sdn/nw-products

SAP Developer Network, Quick Link /irj/sdn/nw-70, path IT Practices andIT Scenarios SAP NetWeaver 7.0



Lesson:

23

SAP Release StrategyLesson Duration: 30 Minutes

Lesson OverviewThis lesson explains what phases your SAP solution runs through over time untilthe next upgrade to a higher release as well as what maintenance duration isguaranteed for SAP products.





It should become clear to the participants how the SAP product they use willchange over time, whether through corrections/enhancements or through upgrades.SAP supports these processes in many ways, not least through the SAP SolutionManager.

Business ExampleYou want up-to-date information about the availability of releases of SAPsolutions, in order to be able to make a good decision with regard to the purchaseor upgrade of an SAP solution.

Availability and DeliveryThe SAP release and maintenance strategy determines the availability of new SAPsoftware releases (including releases or enhancement packages of SAP BusinessSuite, SAP NetWeaver, and the SAP BusinessObjects portfolio), the length andconditions of their maintenance, and the dependencies between individual releases.

Shipments of SAP releases and corresponding enhancement packages aregenerally introduced into the market in two (or three) shipment phases: (beta),restricted and unrestricted.


TADM10_1 Lesson: SAP Release Strategy

Figure 10: Phases of Software Delivery by SAP

Beta Shipment Phase

In some cases, a beta shipment may be offered prior to the restricted shipmentphase (before the release-to-customer date). Beta shipments may be used fortesting purposes only. They are not available for productive use.

Restricted Shipment Phase

New software releases are only available to a restricted number of customerswhose increase is controlled. The Release to Customer date marks the start ofthe restricted shipment phase.

During the restricted shipment phase, the new software release passes through astandardized process, the Ramp-Up. Characteristics of the ramp-up process are:

Ramp-up is the name for the market introduction process of new products ornew releases of SAP software.

The software can be used for a productive implementation.

During the ramp-up, the software is only available for a limited circle ofcustomers, customers apply to SAP to participate in a ramp-up.

The ramp-up serves to take customer wishes into consideration before therespective SAP software is generally available.

Participants in the ramp-up are given direct contact to the SAP developmentand are provided with wide support in implementing the SAP software.

A ramp-up usually takes about 6 months.

Note: For more information about the ramp-up, see SAP ServiceMarketplace, Quick Link /rampup.



Unrestricted Shipment Phase

With the successful conclusion of the SAP Ramp-Up program, the unrestrictedshipment phase of an SAP release begins on the default release date. After thedefault release date all customers can request the new software without restrictions.

The respective latest, generally available version of SAP software is called DefaultRelease. When SAP customers order software from SAP, they are usually giventhe current default release.

MaintenanceYour maintenance contract includes Support Packages, which are provided by SAPvia the SAP Service Marketplace. Support Packages solve (component-dependent)problems that can result when using the SAP software. SAP provides theseSupport Packages at certain intervals.

The SAP Maintenance Strategy

Figure 11: SAP Maintenance Strategy

Hint: The duration of mainstream maintenance might be different forselected software products from SAP. For example, some core applicationsof SAP Business Suite have a significantly increased duration ofmainstream maintenance.



A 512 maintenance strategy was introduced in 2004. It supported alignedmaintenance phases between SAP releases. In continuing to provide a strong,reliable support structure for some of the industrys leading solutions, SAPextended its 512 strategy to 7-2: seven years of mainstream maintenance, withan additional option for two years of extended maintenance.

We distinguish the following three phases of maintenance:

Mainstream maintenance

Mainstream maintenance starts from the "release to customer" date andgenerally ends after 7 years (covering the restricted and unrestricted shipmentphases).

Extended maintenance

Customers can extend the support period (in which corrections or legalchanges are taken into account) for an increased maintenance fee.

The scope of support for the entire extended maintenance period is similarto the scope of support provided during mainstream maintenance. SAPpublishes information on the availability and scope of extended maintenancein advance.

Customer-specific maintenance

From a certain point in time during the lifecycle of a release, this releaseis no longer adjusted to meet external requirements. Such requirementsare, for example, the implementation of legal changes or the support ofnew technologies. The time in question is marked by the end of extendedmaintenance or the end of mainstream maintenance, if no extendedmaintenance is offered. Customer-specific maintenance starts at this pointin time.

A release enters into customer-specific maintenance automatically. Thereis no need to apply for an additional contract. During this phase, customersreceive support services similar to those offered in the mainstreammaintenance phase, with some restrictions. For example, SAP does notdeliver new support packages or updates to cover legal changes, andtechnology updates are limited. Problem resolution is customer specific,which means customers are charged for solving problems not yet knownto SAP.



Do not discuss the maintenance fee percentages in detail as it is not required inthis technical course. For detailed information, customers should contact theSAP sales representatives.

The following SAP notes provide further information: 505060, 303751, and52505.

Note: See SAP Service Marketplace, Quick Link /maintenance foradditional information on the maintenance strategy. SAP Note 52505 dealsspecifically with the particularities of customer-specific maintenance.

UpgradeSAP provides upgrade paths for SAP releases and the corresponding contentreleases and provides access to upgrade procedures to the current release.Usually customers can upgrade directly from one release to any other subsequentSAP release as long as the releases are in the mainstream maintenance phase.Depending on technological constraints, an upgrade to a release that is severalreleases removed from a customers current release may have to be performedin more than one step.

To facilitate smooth upgrades, SAP provides a sufficient overlap of two successivereleases to make sure that the time in which customers may upgrade from onerelease to the next is at least one year for SAP releases. For content releases, theoverlap is at least six months. This helps ensure that the window customers haveto upgrade from one release to the next is sufficient.

Note: For more information on upgrade, see SAP Service Marketplace,Quick Link /upgrade.

History of Selected Software ComponentsThis section provides a bit of history of a few selected software components.

SAP is very good at confusing customers, for example, through constant renaming.This little section is supposed to get customers who are familiar with the namesof older software components, on the one hand. On the other hand, this sectionis a good transition to the topic as to how SAP actually supplies customers withapplications.

Discuss only the structure of the latest ECC or SAP NetWeaver systems in detailbecause the rest of the slide is pretty much self-explanatory. A too extensivehistory with all name changes over the last few years (for example mySAP.com mySAP Business Suite SAP Business Suite) can be rather confusing for



customers who do not know the history because they are just about to introducethe software. Seasoned SAP users or admins in contrast might find the overviewslide very helpful for understanding the contexts.

The following figure shows the historical development of

the basis technology (SAP Basis SAP Web AS SAP NetWeaver AS)

the core business functionality (SAP R/3 SAP R/3 Enterprise SAPECC)

Figure 12: Evolution of Basis and Business Functionality

Technical Basis (Application Server)

Back in the days when SAP basically offered two products (SAP R/2 and SAPR/3), the development of the (technical) basis was closely linked to applicationdevelopment. The release names of the SAP Basis corresponded to the SAP R/3version, for example, SAP Basis 4.0B was the technical basis for SAP R/3 4.0B.

Around the turn of the millennium, the SAP portfolio grew significantly, newproducts were created that required more frequent changes and enhancements ofthe SAP Basis than SAP R/3. This marks the transition from the classic SAP Basis(last version: SAP Basis 4.6D) to SAP Web Application Server (SAP Web AS).New internet technologies (Internet Communication Manager from SAP Web AS6.10 onwards) and the supplementing of the classical ABAP environment withJava/JEE (from SAP Web AS 6.20 onwards) were important milestones.



SAP Web AS 6.40 forms the technical basis (application platform) of SAPNetWeaver 2004. SAP NetWeaver offers extensive capabilities (such as BusinessWarehouse), which are all based on the application platform. From SAPNetWeaver 7.0 (previously: SAP NetWeaver 2004s) the names and releaseswere adapted further, so now SAP NetWeaver 7.0 is based on SAP NetWeaverApplication Server (SAP NetWeaver AS).

While the releases 7.1x and 7.20 of the SAP NetWeaver AS are used onlyfor certain usages (such as SAP NetWeaver Process Integration (PI) and SAPNetWeaver Composition Environment (CE)), SAP NetWeaver 7.3 is a fullshipment of the SAP NetWeaver technology stack.

Central ERP Functions

As already mentioned, in times of SAP R/3, the technical basis and applicationdevelopment were interlinked, up to and including SAP R/3 4.6C.

With SAP R/3 Enterprise (4.7), which is based on SAP Web AS 6.20, the conceptof SAP R/3 Enterprise Extensions was introduced.

A central application (previously: solution) of the SAP Business Suite is SAPERP for Enterprise Resource Planning. The central software component of SAPERP is SAP ERP Central Component (SAP ECC). SAP ECC 5.00 can thusbe considered the technical successor of SAP R/3 Enterprise and is based onan SAP Web AS 6.40. At the time of creating this documentation, the currentversion is SAP ERP 6.0 (previously: SAP ERP 2005), which also includes anSAP ECC 6.00 (that operates on the basis of SAP NetWeaver AS 7.00) and othercomponents. Functional enhancements for the different software components aremade available through enhancement packages.

SAP NetWeaver AS 7.1x or 7.20 are not used as the technical basis for an SAPECC system. Other SAP NetWeaver components, such as SAP NetWeaverProcess Integration (PI) and SAP NetWeaver Composition Environment (CE)require this SAP NetWeaver AS release level.



29 Exercise 1: SAP Release StrategyExercise Duration: 5 Minutes

Exercise ObjectivesAfter completing this exercise, you will be able to:

Access the SAP release strategy document

Business ExampleYou want to determine the end of extended maintenance for SAP EnhancementPackage 5 for SAP ERP 6.0.

Task: Maintenance InformationUse the SAP Service Marketplace to find the end of Extended Maintenance ofSAP enhancement package 5 for SAP ERP 6.0.

Hint: This exercise requires a registered user on the SAP ServiceMarketplace. If you dont have access to your S-user, please skipthis exercise.

If some or all of your students have no access to the SAP Service Marketplace,you may also run this exercise as an instructor demo.

1. When does Extended Maintenance for SAP Enhancement Package 5 forSAP ERP 6.0 end?



Solution 1: SAP Release Strategy

Task: Maintenance InformationUse the SAP Service Marketplace to find the end of Extended Maintenance ofSAP enhancement package 5 for SAP ERP 6.0.

Hint: This exercise requires a registered user on the SAP ServiceMarketplace. If you dont have access to your S-user, please skipthis exercise.

If some or all of your students have no access to the SAP Service Marketplace,you may also run this exercise as an instructor demo.

1. When does Extended Maintenance for SAP Enhancement Package 5 forSAP ERP 6.0 end?

a) Navigate to SAP Service Marketplace, Quick Link /releasestrategy(URL is https://service.sap.com/releasestrategy).

b) Open the document named SAPs Release Strategy for LargeEnterprises for all Major Releases from 2005 onward to be found underthe heading SAPs Release Strategy for Large Enterprises.

c) Within the document, search for SAP ERP. One of the hits will leadyou to the table giving the details for SAP ERP.

Result

Extended Maintenance for SAP Enhancement Package 5 for SAP ERP 6.0 willend 31. December 2017.



Lesson Summary





Related Information

SAP Service Marketplace, Quick Links

/releasestrategy

/rampup

/maintenance

/upgrade


Unit Summary TADM10_1

Unit SummaryYou should now be able to:









TADM10_1 Test Your Knowledge

33Test Your Knowledge

1. SAP guarantees certain maintenance periods for SAP NetWeaver-basedproducts. The mainstream maintenance can be extended by paying increasedmaintenance fees. For how many years does SAP maintain a product intotal, by default?


Test Your Knowledge TADM10_1

34Answers

1. SAP guarantees certain maintenance periods for SAP NetWeaver-basedproducts. The mainstream maintenance can be extended by paying increasedmaintenance fees. For how many years does SAP maintain a product intotal, by default?

Answer: The software product is maintained for a maximum of 9 years(7 + 2).


Unit 235 Navigation

Note: TADM10: This unit is taken from course SAPTEC.

Below you will find the original instructor note for this unit in courseSAPTEC.

Since many course participants will be seeing an SAP system for the first time, itis important that they all receive a good grounding in the basics that will enablethem to access system functions efficiently. You should pay particular attention tothe developers and system administrators during this unit. They are the ones whowill often need to call up functions that are unfamiliar to them in the course oftheir work. To find these functions, administrators will need to know how to usethe command field (for example, search_sap_menu) and table TSTCT.

Unit OverviewIn this unit you learn how to navigate in SAP systems using SAP GUI. You willalso learn how to personalize the SAP system and get help when you are workingin the SAP system.

Unit ObjectivesAfter completing this unit, you will be able to:

Log on to the system successfully

List some variants of the SAP GUI

Log off from the system successfully

Use various methods to start SAP system functions

Create a list of favorites

Use the help functions

Describe the standard menus System and Help.

Use different personalization options in the SAP system


Unit 2: Navigation TADM10_1

Unit ContentsLesson: Navigation in SAP Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Procedure: Changing the Initial Password ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Procedure: Changing the Changed Password Again.. . . . . . . . . . . . . . . . . . 51Procedure: Log off via the Menu Bar .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Exercise 2: Logon and Screen Design ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Lesson: Advanced Navigation in the SAP GUI ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Exercise 3: Calling Functions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Lesson: Appendix - Personalizing the User Interface... . . . . . . . . . . . . . . . . . . . . 79


TADM10_1 Lesson: Navigation in SAP Systems

Lesson:

36

Navigation in SAP SystemsLesson Duration: 40 Minutes

Lesson OverviewThis lesson provides an overview of the different navigation options in SAPsystems and you will learn basic navigation commands using the SAP GUI forWindows as the example.


Log on to the system successfully

List some variants of the SAP GUI

Log off from the system successfully

After completing this lesson, the participants should be able to log on to the systemwithout errors, name and use the basic elements of an SAP GUI screen and log offfrom the system correctly. Course ADM100 covers how to configure SAP Logon.

Business ExampleYou want to find out which options are generally available to your users to accessSAP systems.

Different User Interfaces in the SAP EnvironmentSAP Solutions use different types of runtime technology.

Many SAP systems are based on SAP NetWeaver Application Server ABAP (ASABAP), like SAP ECC, SAP CRM, SAP SCM etc., some SAP systems are basedon SAP NetWeaver Application Server Java (AS Java), like SAP NetWeaverPortal, SAP NetWeaver Process Integration, SAP NetWeaver CompositionEnvironment etc. and some solutions not based on SAP NetWeaver ApplicationServer, like SAP Business One, SAP Streamwork (offered as Software as aservice - SaaS), SAP Crystal Solution, SAP HANA and many more.

Note: Some SAP systems are based on AS ABAP + Java, for examplethe SAP Solution Manager.

Depending on what they are used for, these different system types use ratherdifferent user interfaces.

The following list names some frequently used access technologies, which endusers of these system (so not technicians) use frequently.



Examples of Different Access Technologies

SAP Product Typical Access Technology

SAP ERP (with SAPECC)

SAP GUI for Windows (GUI = Graphical UserInterface) or SAP GUI for HTML

SAP NetWeaver BI Browser-based interface (different browsers possible)

SAP BusinessByDesign

Browser-based interface (different browsers possible),Software offered as a service (SaaS)


SAP NetWeaver Business Client

Note: In this course we will focus on SAP NetWeaver and itstechnology.

Please note that the above list does not cover all SAP products are and that notall possible (!) access technologies are listed in all cases. For example, an SAPECC system can also be accessed by browser or using the SAP GUI for Java; SAPNetWeaver BI is also accessible by SAP GUI for Windows and so on.

The following display will be limited to the most popular access technology,the SAP GUI.

The presentation interface, SAP GUI (Graphical User Interface) enables the userto interact with SAP systems based on AS ABAP.

SAP GUI implements the graphical user interface using the functions provided bythe relevant presentation environment. SAP GUI is based on the Windows StyleGuide and is available for several platforms, providing the same functions foreach. There are different variants of SAP GUI, which can all be operated in thesame way, irrespective of the underlying platform.

The following types of SAP GUI are available:

SAP GUI for the Windows environment

SAP GUI for the Java environment

SAP GUI for HTML

Note: In the above list, the official terms of the SAP GUI are used; theseare only available in English. Colloquially, the following terms are usedsynonymously (in the same order): SAP GUI for Windows, SAP GUI forJava or Java GUI andWeb GUI. Please note that these are not the officialSAP terms but are used frequently nonetheless.

Caution: The above variants of the SAP GUI are suitable only forworking with SAP systems based on AS ABAP. SAP GUI for Javaoffers no access to SAP systems based on AS Java, its name refers to its



implementation technology: SAP GUI for Java has been implementedin Java and can therefore be used on front ends not running a Windowsoperation system (e.g. Mac OS X or Linux).

SAP applications based on AS Java are accessed using a browser.

SAP GUI for the Windows environment (abbreviated to SAP GUI for Windows)is the SAP GUI implementation in a Microsoft Windows environment. SAP GUIfor Windows is written in C or C++, runs on Windows-based platforms, andsupports all transactions in an SAP system.

The data flow between the presentation layer and the application layer does notconsist of prepared screens, but rather of logical, compact information aboutcontrol elements and user input (DIAG protocol). The volume of data transferredfor each screen change is generally a few KB. You can therefore also easilyconnect presentation servers over WANs.

SAP GUI for the Java Environment (abbreviated to: SAP GUI for Java) is writtenin Java and is the platform-independent implementation of SAP GUI. Like SAPGUI for the Windows environment, this GUI also uses the DIAG protocol, so thevolume of data transferred for each screen change is also generally only a few KBand you can easily connect presentation servers over WANs.

You can either install SAP GUI on the front end, or alternatively you can install iton a terminal server and access it using terminal clients.

SAP GUI for HTML requires the SAP Internet Transaction Server (ITS) that ispart of AS ABAP on the server side and a Web browser on the client side. TheSAP ITS provides the services needed for creating responses (within the SAPsystem) in HTML format. Those responses are transferred to the Web Server orWeb Client outside the SAP system, using the Internet Communication Managerof the AS ABAP. The primary advantage of the SAP GUI for HTML is the simplerinstallation on the front-end; a browser installation suffices.

The following figure shows the various alternatives and the flow of communicationwith the ABAP dispatcher / Internet Communication Manager (ICM).



Figure 13: Flavors of SAP GUI

Note: You can find further information on the various SAP GUIalternatives in the following SAP Notes:

SAP Note 66971: Supported SAP GUI platforms

SAP Note 314568: SAP GUI for HTML functionality / Limitations /Sp. Behaviour

SAP Note 146505: SAP GUI for the Java environment (PlatformIndependent GUI)

SAP Note 138869: SAP GUI on Windows Terminal Server (WTS)

Logging on to the SystemMost of the solutions shipped by SAP can be accessed using the SAP GUI (SAPGraphical User Interface). For the sake of simplicity, further descriptions refer tothe SAP GUI for the Windows environment.

SAP provides another program for starting the front end: SAP Logon. When youcall SAP Logon, it shows a list of SAP systems for which you can start the logonprocess. This list is taken from a file on the front end file saplogon.ini. This file isusually centrally preconfigured and provided for end users.

During logon, SAP Logon also enables logon load distribution using theresources available for the system selected.



Figure 14: The SAP Logon program

When logging on to an SAP system, you will be prompted to enter the user andpassword, among other things. If you have implemented a Single Sign-On (SSO)solution, you may not need to enter this information. When you log on, youalso select a certain client of the SAP system; this field is usually already filledappropriately.

Hint: A client usually represents a company in an SAP system. Thismeans that if an SAP system has several clients, then several companiescan be represented and simultaneously active in that system. The clienthas a corresponding key field in the tables of the database used by thatSAP system. When working in a client, you only have access to businessdata from the same client. Clients therefore correspond to independentbusiness entities.

When logging on, you can select a logon language supported by that system. SAPsystems can support a large number of languages, the minimum being Englishand one other selected language. The number of installed languages determineswhich languages your system supports.

On the logon screen, you also have the option of using the New passwordpushbutton to change your password, at the most once per day.

Your system administrator can add additional text to your logon screen.

To do so, follow the SAP Note 205487: Own text on SAPGui logon screen.

Note: SAP Notes contain detailed information on certain functions orcorrections for known errors in SAP products. You can access SAP Notesthrough, for example, the SAP Service Marketplace on the Internet, usinga valid user (S-user) and password: https://service.sap.com/notes.

In the course of one logon session to a system, you can work in severalmodi (processing windows of an SAP system) simultaneously. Your systemadministrator can use a system parameter to define how many modi are permissiblefor each logon to the SAP system.



For more details please see the SAP Note12466: Logon restrictions in R/3.

Parameter rdisp/max_alt_modes is used for this purpose.

Six windows are the default. The parameter cannot be set user-specifically butapplies for all users of the system or the logon instance.

Figure 15: The logon screen for an SAP system

The user data in SAP systems is called the user master record. User masterrecords are stored in the system by client. This means that you can only log on toclients where your user (master record) exists. If your user exists only for client100, you can successfully log on to client 100. If you can log on to more thanone client, then you have more than one user master record - these can allow fordifferent activities depending on the client you log on.

Multiple logons to SAP systems are logged. This is for reasons of both securityand licensing. If the same user logs on more than once, then for each subsequentlogon, the system displays a warning message that offers the user the followingthree options:

Close all existing session(s) and log on again

Keep existing session(s) open, and open an additional session (this isrecorded in the log).

Terminate this logon



The second option can be deactivated centrally and system-wide.

tadm10_1 implementation y operation i

Documents