Day1

Expert Guided Implementation Basic Configuration of SAP Solution Manager

Day 1Konstantin Werthmann

© 2011 SAP AG. All rights reserved. 2

Day 1 Day 2 Day 3 Day 4 Day 5Empowering lessonSAP expert explains the planned Basic Configuration scenario, shows fulfillment of prerequisites and explains initial configuration steps of System Preparation(Web session, 1-2 h. in the morning)

Empowering lessonStep-by-step explanation for the remaining configuration steps of System Preparation(Web session, 1-2 h. in the morning)

Empowering lessonStep-by-step explanation for the configuration steps of Basic Configuration(Web session, 1-2 h. in the morning)

Empowering lessonStep-by-step explanation for the configuration steps of Managed System Configuration(Web session, 1-2 h. in the morning)

Empowering lessonSAP expert explains the remaining steps of Managed System Configuration and shows best practices for scenario usage(Web session, 1-2 h. in the morning)

Execution by customerCheck and fulfill prerequisites and perform initial configuration steps of System Preparation in own system backed by on-demand expertise(Remote support in the afternoon)

Execution by customerPerform the configuration steps of System Preparation in own system (Remote support in the afternoon)

Execution by customerPerform the configuration steps of Basic Configuration in own system(Remote support in the afternoon)

Execution by customerPerform the configuration steps of Managed System Configuration in own system(Remote support in the afternoon)

Execution by customerPerform the remaining steps of Managed System Configuration in own system(Remote support in the afternoon)

Goal of the day

Installed SAP Solution Manager is prepared for scenario configurationInitial configuration steps of System Preparation are completed

Goal of the day

The configuration steps of System Preparation are completed

Goal of the day

The configuration steps of Basic Configuration are completed

Goal of the day

The configuration steps of Managed System Configuration are completed

Goal of the day

The Managed System Configuration is completed

Final Goal

Scenario is ready for go-live

Expert Guided Implementation Schedule: Basic Configuration of SAP Solution Manager


Expert Guided Implementation“Training on the job” at its best

Training, practical experience, remote consulting

Day 1 Day 2 Day 3 Day 4 Day 5

SAP expert explains step-by-step configuration using training materials

Execution, 2-3 hours on the same day

Participants have direct access to an SAP expert who directly supports them remotely, if necessary, during the execution

Empowering, Web session, 1-2 hours each morning

Participants execute demonstrated steps within their own project, on their own SAP Solution Manager software

Expertise on demand, during execution


Phases - Expert Guided Implementation

Define the goal you would like to reach and plan the necessary project steps.

Review the expert guided implementation calendar to identify your topics and fitting time slots to receive SAP expert support for your planned execution steps.

Prepare the execution supported to your expert guided implementation. Fulfil the technical prerequisites and assign the right people with sufficient time to execution.

Execute the defined activities in the planned time frame. During this phase, the SAP expert is available to answer questions and to provide the necessary knowledge to ensure smooth execution.

Execute necessary follow up steps according to your project plan, like rollout of results from execution phase.

Plan Chose Follow upExecutePrepare

Each Expert Guided Implementation should be treated as a Project

The Project should have a clear outcome, a configured ALM scenario or the ability to deliver a self service report by the end of this Expert Guided Implementation


Ready, Set & Go!

Are you Ready?Do you have the correct authorizations?Do you have time allocated for this week?Do you the prerequisites complete?

Are you Set?…to participate in the empowering sessions each morning?…to configure your own Solution Manager each afternoon?…to provide feedback on your progress to the SAP Expert

Lets Go!

Options if not prepared for todayReschedule to the next EGI on the scheduleExecute preparation steps before attendance


Necessary prerequisites for Basic Configuration

Technical prerequisites

Installation of SAP Solution Manager 7.1 (Dual Stack) with at least SP03Connection between SAP Solution Manager and the SAP backbone via RFC SAPOSS S-User in SAP Marketplace with necessary authorizations for SAP Solution ManagerNetwork connection between SAP Solution Manager and the satellite systems which should be connected


FeedbackHelp us to help you…

For this Expert Guided Implementation we will collect the following feedback:

Daily Feedback during Expert Guided ImplementationTo measure your success each day following the morning

empowering stepsTo provide additional assistance if you’re facing issuesTo improve the quality, focus and pacing of the Expert Guided

Implementation

Follow-up Feedback after Expert Guided Implementation to check

If Expert Guided Implementation works for you?What could be improved?Does it provide additional Value?

Help us make your week a success and provide us with your feedback, it’s very important for us.


Expert Guided Implementation How to get help

How to get help

Customer SAP Expert

During the execution part you have direct access to the Expert via telephone number to solve questions quickly. Please ensure that the R/3 support and http connections are open and that we can logon to

your system.

+49 6227 [email protected]


1. Day oneExpert Guided Implementation MethodologyMotivationCheck of prerequisitesSystem Preparation (1)

2. Day twoSystem Preparation (2)

3. Day threeBasic Configuration

4. Day fourManaged System Configuration (1)

5. Day fiveManaged System Configuration (2)Best Practices

Agenda


SAP Solution Manager Platform for Application Lifecycle Management

SAP Solution Manager

Reduces risk and lowers TCOthrough standardized and integrated Application Lifecycle Management according to ITIL

Optimizes business benefitsthrough a comprehensive and integrated quality management process

Leverages built-in innovationby making innovation a non-event and protecting existing investments

SAP Solution Manager provides comprehensive capabilities and services for Application Lifecycle Management

for SAP and non-SAP applications

Require-ments

Design

Deploy

Build & Test

Optimize

Operate

ApplicationLifecycle

Management

© 2011 SAP AG. All rights reserved. 11This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

Template ManagementComparison & Adjustment for templateRoll-in changes from projects

Change Control ManagementQuality Gate Management to control changesChange Request Management process flexibility New Change and Transport System mechanism Configuration Validation and Change Analysis

Application Incident ManagementITIL IT Service Management alignedConfigurable web-client user interfaceAdditional Service document functions

Solution ImplementationNew Business Blueprint modeling capabilityEnd-to-End Business Function implementation process Project and Solution Reporting Enhancements

Business Process OperationsBPO Dashboards with Alert InboxBusiness Process Analytics Cross-database comparison Job Control and Schedule Management

Solution DocumentationExtended of Solution Documentation Assistant analysis scopeReverse Business Process DocumentationUpload interface to build an initial Business Blueprint structure

Maintenance ManagementMaintenance Optimizer for complicated landscapesSystem Recommendations

Test ManagementMore efficient test phase managementTest Automation Framework with 3rd party toolsTest Scope Identification & Optimization with BPCA

Upgrade ManagementIntegration of Upgrade Dependency Analyzer

Technical OperationsNew Technical Monitoring and Alerting infrastructure End User Experience MonitoringTechnical Administration and AnalyticsExtended Root Cause Analysis scope Data Volume Management work center

Custom Code ManagementLifecycle Management for custom code

Application Lifecycle Management An approach in six phases of ITIL application management


Application Lifecycle ManagementBusiness Process Repository

Motivation

Application Lifecycle Management Business Process Repository

Demonstrates the ALM standard processes coming with SAP Solution Manager

Allows to choose the right use cases or best practices fitting your needs

Helps to choose a combination of processes ensuring a smooth data flow without gaps

Supports configuration and implementation of ALM processes and SAP Solution

Manager capabilities


ALM BPR - Preview of current contentSMP alias /bpr

At service.sap.com/bpr Available implementation content Business Process Repository Solutions/Applications SAP Solution Manager <ALM Process> SAP Solution Manager 7.1 you will find a preview of the content currently available


ALM BPR - Scenario LevelALM Processes

ALM processes are mapped to scenarios in BPR, allowing more granular processes and process steps


ALM BPR - Scenario LevelLinked documentation

On scenario level you typically find the following documentation linked:Support standardsBest practice process documentTraining materialApplication help

Exceptions are Business Process Operations andTechnical Operations where you find those documents on process level

Scenario ’Solution Documentation’


ALM BPR - Process and Process Step Levels

On process level on tab ‘Graphic’ you find the graphical display of the process structure

On process step level you find:Detailed application help links listed in the order of the typical workflowTechnical objects supporting the process step (transactions, work centers)Configuration objects supporting processstep (documentation, IMG objects)

Configuration of Step ’Enter Working Time’

Graphic of Process ’Incident Management’


Check of prerequisites RFC Connections

For the communication of your Solution Manager withSAP Backbone please ensure that the followingprerequisites are fulfilled



Transaction SM59:You can check the connection to SAP with Utilities Test Authorization Test for the RFC SAPOSS in transaction SM59. This will do the connection test using the user and password that was assigned to the RFC.

The SAPOSS RFC should have theLogon Group EWA

The User / Password is alwaysOSS_RFC / CPIC



Transaction: OSS1If you have problems with the connection test of SAPOSS you can check and maintain settings for the connection in transaction OSS1. The RFC SAPOSS will be adapted automatically after change of configuration in OSS1.

You can find detailed information about the RFC connection SAPOSS in the SAP Note 812386


Check of prerequisitesS-User authorizations

URL: http://service.sap.com/user-admin

You can check the authorization objects of your Solution Manager S-User with the „Authorization reports“. Please ensure that your S-User has at least the marked authorization objects.


Check of prerequisites Installation / Upgrade post processing information

Please ensure that your SAP Solution Manager 7.1 is at SP3 or higher!

SAP Note 1483508 Solution Manager 7.1: Root Cause Analysis pre-requisites SAP Note 1478974 Diagnostics in SAP Solution Manager 7.1SAP Note 1612514 Solution Manager 7.1 SP Stack 3: recommended correctionsSAP Note 1582842 Profile parameters for Solution Manager 7.1

To display current Java component levels:Enter Solution Manager server and port in URL field: http://<server>:5xx00Click link System InformationLogin with user J2EE_ADMINClick all components link in upper right corner

The front end client that the configuration will be performed from needs to have Java installed. Otherwise, the configuration transaction SOLMAN_SETUP cannot be executed.


Check of prerequisites Client Copy

SAP delivers standard Solution Manager configuration in clients 000 and 001. Client 001 can be used for the productive Solution Manager client, but you can also create a new productive client in order to keep the master client original.

There is also a client needed for BW, which can be the same as the Solution Manager productive client or a separate client. See next slide for options.

To create a new client in the SAP Solution Manager perform the client copy using profile SAP_UCSV with 000 as the source client and 001 as the source client for users.

You can find information how to create anew client and do the client copy in the IMG(Implementation Guide - transaction SPRO)in the tree Cross-Scenario Settings

Client Copy


Check of prerequisites BW Client

Business Warehouse (BW) Strategy

SAP Netweaver Business Warehouse (BW) provides important reporting functions to the various SAP Solution Manager scenarios, such as Root Cause Analysis, IT performance reporting and change analytics. There are three major options to consider when planning your system landscape in regards to BW:

BW in the productive SAP Solution Manager clientIn this scenario BW is used in the same productive client as SAP Solution Manager. This option allows simpler configuration and isolates the BW activities conducted for solution life cycle management from the data on a production BW instance. This is SAP’s recommendation.

BW in a separate client on SAP Solution ManagerIn this scenario BW activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increases your administration effort. There is no technical benefit.

BW in a separate, non-productive BW systemIn this scenario, the BW activities are conducted in a separate, non-productive BW system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

Note: We do not recommend SAP Solution Manager data in a separate, productive BW system.

Please refer to SAP Note 1487626 for further information.


Check of prerequisites Client Copy – Convert UME

After you created a new productive client you need to convert the Java user store to the new productive ABAP client. This is needed if you want to use Root Cause Analysis.

You can find a detailed description in the IMG(Implementation Guide - transaction SPRO)in the tree Technical Settings Client Copy

Convert UME

Note that the Java engine will need to berestarted afterwards.


Check of prerequisites Client Settings

Some configuration steps make customizing changes in the productive client and the BW client. Therefore ensure the following client settings in transaction SCC4 during the configuration activities:


System Preparation (1)Steps in detail

System Preparation (1)

Create Users

Check Installation

Implement SAP Note


System Preparation (1)Demo environment

Overview of the demo environment that will be used this week:

SAP SolutionManager7.1 SP3

TAStastdc00

wdflbmt2284

SAP ERP 6.0 EHP5

TAEtaetdc00

wdflbmt2586

SAP NW 7.0 EHP2Enterprise

Portal

J2Eportal-tae

wdflbmt2621

Cloud Environment


System Preparation (1)SAP Solution Manager IMG

Transaction: SPRO

The IMG tree contains all Basic Configuration and scenario-specific settings for your Solution Manager.

The Collaboration scenario is completely covered with the Basic Configuration part.

Read the ‘Read Me’ file for important information.

AdvantagesAlways up to date implementation guidelineAutomated configuration wizards can be used


System Preparation (1)New guided setup wizard for Basic Configuration

This IMG text recommends the use of the automated setup transaction SOLMAN_SETUP. The transaction launches the HTTP screen shown below. Guided procedures for System Preparation, Basic Configuration and Managed System Configuration can be accessed from this screen. It provides one point of access for the complete configuration and easier navigation.



Transaction: SOLMAN_SETUP

If you start the transaction SOLMAN_SETUP for the first time, you will be asked to activate Web Dynpro Services to display the wizard in your browser screen.



The Overview link displays the available configuration, what remains to be done or requires refresh:


System Preparation (1)Steps in detail

The following steps will be performed:

Create UsersCreate dialog and system users for the Solution ManagerCreate a Business Partner for user SOLMAN_ADMIN

Check InstallationAutomatic installation check for configuration-relevant parts of the installation is performed

Implement SAP NoteDownload, import and post processing of the central correction note (CCN)

Overview – What will be done


System Preparation (1)Create Users

Overview – What will be done

User SOLMAN_ADMIN is created and the roles ZSAP_SOLMAN_ADMIN, ZSAP_SM_CONF_SEC are created and assigned along with additional role assignment for Work Centers and J2EE

A Business Partner of type Person will be created for the userThe two roles Business Partner (Gen) and Employee will be assigned to the user SOLMAN_ADMIN

User SMD_ADMIN is created to connect Diagnostic Agents to your Solution Manager system.

User SOLMAN_BTC is created to schedule jobs for background processing

User SM_EXTERN_WS is created for external web services communication between Diagnostics Agents and SAP Solution Manager.

User SM_INTERN_WS is created for internal web services communication between the ABAP and JAVA stack of SAP Solution Manager.

Business Partners will be used for Solution Manager scenarios likeIncident Management and Change Management


In case you have a Central User Administration (CUA) in place and your SAP Solution Manager or other systems (that are linked with SAP Solution Manager) are connected to it, you can adapt the CUA configuration so that technical users and dialog users (such as SOLMAN_ADMIN) can be automatically created with transaction SOLMAN_SETUP from SAP Solution Manager.

For details about how to configure CUA together with SAP Solution Manager, please refer to Security Guide chapter “Using Central User Administration“.

http://service.sap.com/instguides/SAP Components SAP Solution Manger Release <current release> Operations Security Guide SAP Solution Manager

<current release>




Enable the change mode and create the users (see next slide for details):



In case of dialog users, you have the following options:

Create a default user

Update the authorizations of an existing user automatically

Update the authorizations of an existing user manually



Check the “Status” column and the log area for warnings or errors:

Log off, then log on with user SOLMAN_ADMIN before proceeding to next step.


System Preparation (1)Check Installation

This is an automatic installation check for configuration-relevant parts of the installation in the following areas:

TMS configurationProfile parametersLicense keyDiagnostics prerequisites (according to SAP Note 1483508)System landscape parametersService connection

Overview – What will be done?


System Preparation (1)Check Installation

To run all the checks with execution status set to “Execute” select “Execute All”, otherwise select one or several rows and select “Execute Selected”. Check the results in “Status” column and in the log area:


System Preparation (1)Check Installation – TMS configuration

Check the TMS configurationIf the check is not successful, TMS is not yet configured and you should configure a transport domain controller for the Solution Manager system.

Verify the TMS configurationTo verify the configuration go to transaction STMS in Client 000 and you shouldsee the following dialog box if TMS is not yet configured:

For more information on configuring the transport domain, refer to the SAP Library under SAP NetWeaver Software Logistics Change and Transport System Transport Management System


System Preparation (1)Check Installation – Profile parameters

login/create_sso2_ticket = 2login/accept_sso2_ticket = 1icm/host_name_full = fully qualified server name(This parameter must be attributed to the fully qualified server name (for example, wdflbmt2284.wdf.sap.corp). The name must contain at least two periods. See also SAP Note 434918.)

icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600icm/server_port_1 = PROT=SMTP,PORT= <> 0 , for example, 25000login/no_automatic_user_sapstar = 0icm/conn_timeout, for example, 20000icm/keep_alive_timeout, for example, 240icm/server_port_< n >

Check profile parameters:The Solution Manager uses WebDynpro applications and Business Server Pages (BSP), which need profile parameters for Single Sign-On (SSO). This checks if the following parameters are maintained:

WebDynpro applications and Business Server Pages are used for easiernavigation and graphical screens in the ABAP world.


System Preparation (1)Check Installation – Profile parameters

Transaction RZ10 - Create the profile parameters in the instance profile:


System Preparation (1)Check Installation – License key

Check license key:This step checks if a valid license is installed on the Solution Manager

Transaction: SLICENSE Goto New Licenses (F9)

You can request a license key on the SAP Service Marketplace athttp://service.sap.com/licensekey. There is also more information available aboutthe license key there.


System Preparation (1)Check Installation – Diagnostics prerequisites

Check Diagnostics prerequisites:

This step checks if the Solution Manager system satisfies all theprerequisites for End-to-End Diagnostics.

Depending on the version of SAP Solution Manager and the version of themanaged system, a minimum version for different software components andthe corresponding correction notes are required.

Go to SAP Note 1483508 and refer to the area relevant for you SP levelof SAP Solution Manager. Check also SAP Note 1478974 - Diagnostics inSAP Solution Manager 7.1.


System Preparation (1)Check Installation - System landscape parameters

Check system landscape parameters:This step checks if the value Synchronize is set for the Cross-System Synchronization Settings field in SMSY. This setting allows the correspondingsystem data maintained in Solution Manager to be synchronized withSAP Support Portal.

For all systems the default value for Cross-System Setting will be Synchronize

Transaction: SMSYSet-up synchronizationglobally


System Preparation (1)Check Installation – Service connection

Check service connection:Checks if the RFC SAPOSS works and if the logon group is set to EWA

Transaction: SM59 ABAP Connections SAPOSS

This check should have been done already. If you have problems with SAPOSS, please refer to the relevant slide.


System Preparation (1)Implement SAP Note

Step1: Download the central correction note (CCN)

In this step, you download the central correction note (CCN).Choose Start Download.If a correction note exists, it is downloaded. The Implementation Status is set to Can be implemented. You can implement the corrections in the next step.Note: The system only verifies whether an updated central note exists. The linked notes are not updated automatically. To make sure that all notes are updated, start transaction SNOTE and choose Download Latest Version of SAP Note or Ctrl-Shift-F7 in the note browser.



Step 2: Implement the central correction note (CCN)

In this step, you implement the central correction note (CCN) manually.In the Implement SAP Note area, choose Start SAP Note Assistant. You can start transaction SNOTE manually.



To implement the CCN and the required notes in transaction SNOTE:1) Select the central note2) Click the Implement Note icon



3) A window appears prompting to load the collected notes. Select the checkmark to load them:

There may be multiple windows for Load the following SAP Notes into your system. Just click the green checkbox to continue.



4) A SAP Note queue with the notes to be imported is displayed. Click the Install button:



5) You may get one or several windows that list a note that requires manual activity. Be sure to read the note(s) for any required manual activity. Record these SAP Note numbers.

6) Click “Yes”



7) You may get windows such as the following: Click the green checkmark to continue:

8) When you get a prompt for a transportable workbench request, you can create one for the central note implementation and click the green checkmark to continue:



9) A list appears displaying the notes that will be implemented. Click the green checkmark to continue:



10) You will get a list of inactive objects to activate. Click the green checkmark to continue:



11) When the central note implementation completes, the implemented notes will be displayed under In Processing. There may also be some notes with status New. In this case you will need to review those notes to see what action is needed before they can be implemented singly with SNOTE.

Be sure to do the manual activities for any notes that were listed as such.



12) Go back to the SAP Solution Manager Configuration:

In the field Status, select Performed.



Step 3: Perform automatic post-processing of the central correction note (CCN)


Execution

Check Prerequisites

Check RFC connection “SAPOSS”

Check the authorization on SAP Service Marketplace for your Solution Manager S-User

Review Installation / Upgrade post processing information from mentioned SAP Notes

Client Copy / Convert UME / Client Settings


Create Users

Check Installation

Implement SAP Note

To be able to follow the session in the next days please make sure that you completed all tasks for today.


Outlook

Next steps - Day 2


Configure ABAP

Web Service Configuration

Prepare Landscape


Expert Guided Implementation How to get help

How to get help

Customer SAP Expert

During the execution part you have direct access to the Expert via telephone number to solve questions quickly. Please ensure that the R/3 support and http connections are open and that we can logon to

your system.

+49 6227 [email protected]

Thank You!

Please don’t forget to send us the daily feedback form.


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

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide 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 for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Day1

Documents

Transcript of Day1