SAP Solution Manager Operations PDF

60 6$3 6ROXWLRQ 0DQDJHU 2SHUDWLRQV
60
6$3 6ROXWLRQ 0DQDJHU 2SHUDWLRQV
SAP AG 2006
Software components used in the course 2006/Q62 Material number 50082608
' & (%$#""!

SAP AG 2005
&RS\ULJKW
1R SDUW RI WKLV SXEOLFDWLRQ PD\ EH UHSURGXFHG RU WUDQVPLWWHG LQ DQ\ IRUP RU IRU DQ\ SXUSRVH ZLWKRXW WKH H[SUHVV SHUPLVVLRQ RI 6$3 $* 7KH LQIRUPDWLRQ FRQWDLQHG KHUHLQ PD\ EH FKDQJHG ZLWKRXW SULRU QRWLFH
&RS\ULJKW 6$3 $* $OO ULJKWV UHVHUYHG
SAP AG 2006
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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.
&RXUVH 3UHUHTXLVLWHV
6$37(& $'0 6$3
5HFRPPHQGHG .QRZOHGJH
SAP AG 2006
7DUJHW $XGLHQFH
7HFKQLFDO &RQVXOWDQWV 'XUDWLRQ GD\V
6\VWHP $GPLQLVWUDWRUV
7KLV FRXUVH LV LQWHQGHG IRU WKH IROORZLQJ DXGLHQFHV
SAP AG 2006
8VHU QRWHV
These training materials are QRW D WHDFK\RXUVHOI SURJUDP. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information. There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.
&RXUVH 2YHUYLHZ
&RQWHQWV
Course Goals
SAP AG 2006
SAP AG
Course Objectives Course Content Course Overview Diagram Main Business Example
SM100
1-1
&RXUVH *RDOV
$IWHU FRPSOHWLQJ WKLV FRXUVH \RX ZLOO EH DEOH WR

Administer all necessary tools and features to know around the SAP Solution Manager Know all the basic functionalities of the SAP Solution Manager
SAP AG 2006
Conduct: ausfhren, durchfhren
SAP AG
SM100
1-2
Cw 5 &s&'Sv
&RXUVH &RQWHQW
1 8 U 5 8 C C ) d 1 # " & &!C rVDPF1 `fIeV! D
p T5 T i 5 I 1 @ " q 'Dutser%
8 5 1 1 a64 P) 15 v I y " q q &4SF&7&De D $5 d U T5 # " x q 'DDT fVF sS&e D 8 5 1 f'3VE e1 aId1V#F!2&Q& !sS! D I d T g T5 # " 5 d A C d5 C " s 2D'P$ ! D
(8CC DQDDP) I H E 8CA @"9 &&3GFDB! W U T5 # " R &VF& 'DS CC &&DDDDg d 1 # I 8 # " X 1 `fIeVcba`YS! p T5 T i 5 8 C C ) d 1 # " h !4B%DF31 `fIeV!
8 5 1 1 ) ( $ # " 76!4 320'&%!

SAP AG
SAP AG 2006
SM100
1-3
SAP AG
SM100
1-4
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
0 7 T 4 7 B B ( c 0 " % % B qUCIE0 YeHdU! C
i S4 S h 4 H 0 9 ! p &Ctsrdq$
7 4 0 0 `53 I( 04 u H x ! p p %3RE%6%Cd C #4 c T S4 " ! w p &CCS eUE rR%d C 7 4 0 e&2UD d0 `Hc0U"E 1%P% rR! C H c S f S4 " y 4 c @ B c4 B r 1C&I# ! C
'7BB CPCCI( H G D 7B@ 9! %%2FECA8 V T S4 " ! Q %UE% &CR BB %%CCCCf c 0 " H 7 " ! 0 YeHdUba`YXRW i S4 S h 4 7 B B ( c 0 " ! 3A$CE20 YeHdUg
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
2-1
2EMHFWLYHV 6ROXWLRQ 0DQDJHU 2YHUYLHZ
([SODLQ WKH JHQHUDO DQG UHOHDVH VWUDWHJ\ RI WKH 6$3 6ROXWLRQ 0DQDJHU
*HW DQ JHQHUDO RYHUYLHZ RI WKH 6$3 6ROXWLRQ 0DQDJHU IXQFWLRQDOLWLHV
'HVFULEH WKH DQGDYDQWDJH RI WKH 6$3 6ROXWLRQ 0DQDJHU
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR
SAP AG 2006
SAP AG
SM100
2-2
6$3 6ROXWLRQ 0DQDJHU 2YHUYLHZ

0RWLYDWLRQ 6XSSRUW IRU ,7,/ 3URFHVVHV $YDLODEOH )XQFWLRQDOLWLHV 5HOHDVH 6WUDWHJ\
SAP AG
SM100
2-3
&RQVLGHU &XVWRPHUV 6LWXDWLRQ RI 7RGD\

Global operations Heterogeneous solutions Business processes
'LIIHUHQW ORFDWLRQV 'LIIHUHQW FRXQWULHV 'LIIHUHQW ODQJXDJHV 'LIIHUHQW WLPH ]RQHV &HQWUDO YV GLVWULEXWHG
SAP AG 2006
Large companies today are facing a lot of new challenges in their system management, what is due to Global Operations Heterogeneous Solutions Integrated Business Processes The challenges in global operations are Different locations, countries, languages, time zones There is always a tradeoff between central and distributed solutions
SAP AG
SM100
2-4

Global operations Heterogeneous solutions
5LVN 5LVN 5LVN
Business processes
'LIIHUHQW DSSOLFDWLRQV 'LIIHUHQW WHFKQRORJLHV 'LIIHUHQW YHQGRUV 3RLQWWRSRLQW LQWHJUDWLRQ &XVWRPPDGH VROXWLRQV
'LIIHUHQW DSSOLFDWLRQV WHFKQRORJLHV DQG YHQGRUV

Who has the skills to understand and handle all the different technologies
3RLQWWRSRLQW LQWHJUDWLRQ
Who are the responsible persons for the increasing number of interfaces and do they know the business impact of their actions?
your solution is based upon
&XVWRPPDGH VROXWLRQV
Can you perform upgrades without endangering the stability of your solution?
SAP AG 2006
As a result of heterogeneous solutions in terms of different applications, technologies, vendors a lot of risks occur in the operation of these solutions: The skill profile for the staff is growing The number of interfaces is growing The customer specific parts of the solutions is growing
SAP AG
SM100
2-5
X ` 66
oo e `` 66ee ee q qr `~`~6z6zyy yy e{e{~u ~u 6~6~ rrrll tr tr ` r
oo oo rr XX l o~o~5`zy5XzXz{y e{ { oo&rr y q m& m
6& oo ll &l&l 3er3 r XX `` r e ee ee ee `` 6z6zyy 6{6{ ll q q { X~exexevv ùùenovovo`v`v`vtt t opopX~ 6 r ee r ee 6 r e X 5 56z6zyy e{e{ XqXqll o{o{evev56z6z6y6yexex6t6t`v`vww y t y5 t e w w3& 3&rr oo}3ll `{`veyey66omy omozee`yosos`xyy `t`~`~`v}Y|tt}| w qq `p`pv ùonon6t6n6nr&rms &ll }3 t m YYhhYYhh &&YY dd dd &&Cii ii %333333333feddedd ee&&&&YY&&YY 33335 & &g Ygg Yg d k& &j C % 3 3 3 3 3 3h 3hh 3gh 3gg g e f & & 3 3 3 3 5 d k j C % e 5 d k j d k jC % e e 5 hge g i hg &3h3g3Ye%g r i%h3gY&rY3 %r& 3 &333Y%ii ``r %3Y&rY3ii %r&gg 3 ii
Global operations Heterogeneous solutions
SAP AG
SAP AG 2006
Good business process management needs a concept. This concept should include:
Roles and responsibilities for all persons involved in the customers support and monitoring organization
Documentation of the core business processes including all relevant process steps, involved interfaces, business process owners, availability requirements, performance and throughput requirements, and functional dependencies
Procedures for business-process oriented monitoring, error handling, and escalation management for a companys core business processes
Techniques for integration management regarding interface operation and the interfaces impact on business processes to ensure data quality and consistency, interface security, and recovery reliability
Procedures for program scheduling management including the planning, controlling, and monitoring of all system and business-process related operational activities in a distributed system landscape
Methods for master data maintenance regarding the exchange of master data between different software components in a distributed system landscape
Procedures for data management and archiving to check for and correct data inconsistencies and to avoid unnecessary data growth
Definition of Service Level Reporting requirements
5LVN
Does your IT Department know how its daily work affects your business processes?
Do you know the responsible persons in case of problems?
Do you know which business process step runs on which system?
,QWHJUDWHG %XVLQHVV 3URFHVVHV
SM100
Business processes
2-6
0LVVLRQ 6WDWHPHQW
With SAP Solution Manager you can manage your SAP solution throughout the entire life cycle to ...
Ensure reliability
Increase Return on Investments
Reduce Total Cost of Ownership
SAP Solution Manager is delivered as part of your annual license fee!!! $QG KHUH LV KRZ \RX FDQ DFKLHYH WKH EHQHILWV
SAP AG 2006
SAP AG
SM100
2-7
6XSSRUW IRU ,7,/ 3URFHVVHV
0RWLYDWLRQ
6XSSRUW IRU ,7,/ 3URFHVVHV $YDLODEOH )XQFWLRQDOLWLHV 5HOHDVH 6WUDWHJ\
SAP AG 2006
SAP AG
SM100
2-8
&RPPRQ GH IDFWR 6WDQGDUGV IRU ,7 0DQDJHPHQW

,QIRUPDWLRQ 7HFKQRORJ\ ,QIUDVWUXFWXUH /LEUDU\
www.itsmf.com (for Germany www.itsmf.de)
02) 0LFURVRIW 2SHUDWLRQV )UDPHZRUN
www.microsoft.com/germany/ms/businessrategien/infrastruktur/sicherheit/mof.htm
35,1&( 35RMHFWV ,1 &RQWUROHG (QYLURQPHQWV
www.projectsmart.co.uk/prince2.html
SAP AG 2006
Even though ITIL is not yet a legal standard it has become a de facto standard for IT Service Management worldwide. ITIL is focused on processes in operations (Service and Support delivery). It describes on theoretical basis which processes and tasks are necessary. ITIL is not a software and not a part of SAP NetWeaver. ITIL consists of books that provide a description of the processes. Other de facto standards in similar areas are MOF and PRINCE2. MOF is to see as the interpretation of ITIL with help of Microsoft tools. ITIL should be seen as the theoretical frame, how to operate software and hardware landscapes. MOF is the ITIL fulfillment by Microsoft. MOF describes which Microsoft tools could be used in which ITIL process. In contrast to ITIL PRINCE2 is a de facto standard for the project management. PRINCE 2 could be used during implementation phase of projects. Many of our big customers consider and follow actively the ITIL standard. Due to this it might happen that they ask us for SAP tools to fulfill ITIL or even if SAPs Service and Support Consultants are ITIL certified. It is useful be aware at least of ITIL terminology and differences to the SAP internal use of certain terms. It is also important to share a high-level understanding of what ITIL is behind the scenes. To claim at our customers that we as representatives of SAP Active Global Support are aligned with ITIL, it is not a formal requirement to have every employee ITIL certified. Actually SAPs way of operating and supporting matches with the ITIL standard. Due to this we could use ITIL for our own purposes. One of the advantages of ITL is to have the same terms and a definition of the processes in service and support.
SAP AG
First developed by Central Computer and Telecommunications Agency (CCTA) in 1989. Most widely accepted approach to IT Service Management. Series of books giving best practice for Service Support and Delivery Processes.
Best practices in IT Service Management based on Microsoft technology.
Combines ITIL with specific guidelines for using Microsoft products and technologies.
UK de-facto standard for project management developed by the Government. Was re-launched in October 1996.
SM100
2-9
&RPELQLQJ :KDW DQG +RZ
:KDW
,7 ,QIUDVWUXFWXUH /LEUDU\
Process Descriptions Best practices and recommendations for implementations
+RZ
6$3 6ROXWLRQ 0DQDJHU
Process Execution Tool-set for use in IT implementation and operations
Developed with help of IT service specialists
What to consider in establishing and operating IT service management?
Based on more than 30 years experience in managing business applications
SAP AG 2006
ITIL provides best practice guidelines for service management. They describe the different processes in IT service management and what has to be considered in establishing and operating these services. SAP Solution Manager takes care of the execution of the services. It provides the tools required for running the services. The cooperation of ITIL and SAP Solution Manager is a meaningful combination of What has to be done (ITIL) and How can this be done (SAP Solution Manager) .
SAP AG
SM100
How to execute the processes by using tools in SAP Solution Manager?
2-10
,7,/ DQG 6$3 7RROV

,7,/ %DVLV )UDPHZRUN 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
This slide describes which ITIL processes are defined and which SAP tools the SAP Solution Manager is offering to follow this ITIL standard. ITIL consists at the moment of descriptions for Service Support, Support delivery and Application management. ITIL groups the process into Service Support and Service Delivery processes: Support are all processes which are necessary to operate a concrete software solution day to day. These are e.g. the Hot line which deals with incoming incidents. Delivery are all processes which are necessary to offer the service support. It is more the long term planning and improvement of the IT services. Service Desks is an exception within the ITIL processes. The service desk is to be seen as an function not as a process.
Very important terms within the processes are customer, provider, supplier and user. A customer is a recipient of a service. If you have in mind an outsourcer. The outsourcer would be the provider. He is responsible to fulfill the requirements of the customer. May be there exist underpinning contracts with a third party e.g. another Hardware provider. These partners are called supplier. The user is a person who uses the service on a daily basis.
SAP AG
SM100
' 7BB ( HG D 7B@ I2%FA9
(SAP Alert Monitoring RZ20)
7 4 0 0 ( 4 7 B B ( c 0 C6Y23 2IR E20 YeH2R"
7 4 0 D c 0 " B f e&CRP e0YeHdUCb"
S4 " u % rR2"
V $P &$" T S4
Reporting
c B 4 %# &d% Ce B H v 0 9 7 B @ 9 ' c 04 u 0 Y%&4 e72%AP 2$Y% Ce '7BB ( v0 c#f 7 cB RC odCs %3v eo$ ' 7 B B ( c S f S4 %PE% &d" ' 7 B B ( # H 0 CCE& `Y29 %CCE& e`cB ec '7BB ( # BS '7BB ( # BB ECIE F9 7 4 0 0 ( 7 c 04 0 e2& dsCeèc2Y29 '7BB ( 7B@ ECEf9
Message Handling Notes and SAP Note Assistant SAP Support Packages
Solution Management Assessment Solution Management Optimization EarlyWatch Alert / GoingLive
2-11
6HUYLFH 'HOLYHU\ ZLWK 6$3 6ROXWLRQ 0DQDJHU

,7 0DQDJHPHQW
Capacity data
EarlyWatch Alert, Quick Sizer

Change request
Change request
Service Desk Accounting
,7 ,QIUDVWUXFWXUH
SAP AG 2006
This slide shows the different ITIL processes from the Service Delivery area and the tools supported. Furthermore it shows the connection from the Service Delivery to the Service Support (the Change Management and Incident Management).
SAP AG
SM100
'7BB E( Ce
'7BB CC' # BS & eecB ecq

Solution Monitoring
SL and Solution Reporting
`}f &e 1 e%q} efI`
'7BB %%( c S f S4 CE% &CR" '7BB %%( # H 0 & `%29 %%( '7BB 7B@ CCA9
Performance and availability
%Ff 3 }}}}6
'7BB EC( #BB F9 '7BB CPCCI( c B CB `
2-12
6HUYLFH 6XSSRUW ZLWK 6$3 6ROXWLRQ 0DQDJHU

,7 (QG XVHU
Problems
Service Desk
Request for change Request for change
Incidents
Requests for change
Service Desk
Note Assistant, Change Request Management

Change authorization
Central system data and Customizing
Change authorization
Upgrade Managm. **
,7 ,QIUDVWUXFWXUH
SAP AG 2006
The change management component is new in the SAP Solution Manager 3.2, and is designed closely to support the ITIL scenario. The change management is responsible to make changes requested by problem management for solving problems. They need standardized methods to do the changes fast and controlled. Impacts because of the changes should be minimized. For each RfC (Request for change) a priority and a category is to be defined. The priority is again the sum of urgency and impact. The category depends on the necessary resources for implementing the changes. The change advisory board is the community which decides about major and immediate RfCs. It has to pay intention to the different views: Users, Customer, Technical view, business view. After the implementation of an RfC the change management has to review the results of the change. Does the change fulfill the request?
SAP AG
SM100
q
2-13
C%%
ECCf
%PCCI

Incidents, Service requests
f q 1 e%q} efI`
%%
% &
23R " C%E $ # ! %Ff 3 }}}}6
$SSOLFDWLRQ 0DQDJHPHQW ZLWK 6$3 6ROXWLRQ 0DQDJHU

Change Request Management
SAP Services Upgrade Management Change Management Optimization Projects
0RQLWRULQJ
Business Blueprint, Central System Data, Mapping of Business Processes to IT Landscape
Test Workbench Global Roll-Out Customizing Synchronization
SAP AG 2006
Diese Folie zeigt die verschiedenen ITIL Prozesse aus dem Bereich Application Management und durch welche Tools sie untersttzt werden. Weitere Infos zu den Prozessen und Tools sind im Word-Dokument zu finden.
SAP AG
'
System Monitoring Business Process Monitoring Central System Admin. EarlyWatch Alerts
Implementation of mySAP based on Business Processes Central Documentation of Implementation Project Setup Business Process Monitoring
SM100
d )(
" 0 '
2-14
" 1 2E #
}6%t} % `` 9C7 8 %Ff 3 }}}}6 5 & $%43 63
$YDLODEOH )XQFWLRQDOLWLHV
0RWLYDWLRQ
6XSSRUW IRU ,7,/ 3URFHVVHV $YDLODEOH )XQFWLRQDOLWLHV 5HOHDVH 6WUDWHJ\
SAP AG 2006
SAP AG
SM100
2-15
7HFKQLFDO 'HWDLOV 6$3 6ROXWLRQ 0DQDJHU

SAP AG 2006 2003
SAP Solution Manager, as part of SAP NetWeaver, serves as a central instance within the solution landscape to manage the complete solution. This includes applications developed by SAP, customer and 3rd-party applications based on SAP NetWeaver, as well as other applications. As central instance, SAP Solution Manager provides a variety of centralized services both for implementing and operating your SAP solutions. The advantages are that you have a central point of access, that you can do end-to-end process control, that you can ensure consistency within your landscape, and that dependencies between different components are taken into account.
SAP AG
SM100
U S R PI G E C A TG T(G QHFDB@
runs on SAP basis technology can service all SAP technologies integrates non-SAP products and
5
&50 $32
centralized:
Process description Documentation Testing Configuration and Customizing Note handling Monitoring Service delivery and execution Landscape definition
2-16
7KH 6$3 6ROXWLRQ 0DQDJHU $SSURDFK

7KH 6$3 6ROXWLRQ 0DQDJHU LV D QHZ W\SH RI DSSOLFDWLRQ ZKLFK
Contains best practices for implementation, operation and optimization of SAP solutions
Implement
Optimize
SAP AG 2006
The SAP Solution Manager is NOT positioned against existing knowledge management, solution management and other best-of-breed solutions. Our strategy is not to replace existing software products at customer sites, but to coexist and bring additional value to the customer. If a best-of-breed product is chosen because it offers more functionality in a specific area, we recommend to evaluate the SAP Solution Manager nevertheless. We think that the SAP Solution Manager offering is compelling because of its integrated, process- and life-cycle-oriented approach and should therefore be actively used at all customer sites.
SAP AG
SM100
6 2 !" ) d
e ( ' % Rd
' Rd
i i t yw uqxv i i t rp i g uqsq#hf
CC CCA
CCC a b$
Is delivered as part of your annual maintenance fee
%PCC %PI ( ` X T Y W
r d` X T cT
Takes a consistent business-process and phase-oriented approach End-to-end functionality for application management and continuous improvement Provides full life-cycle support and collaboration with SAP
2-17
6$3 6ROXWLRQ 0DQDJHU IRU P\6$3 (53

+RZ LV 6$3 6ROXWLRQ 0DQDJHU WHFKQLFDOO\ OLQNHG WR P\6$3 (53"
Installations and Upgrades to mySAP ERP ONLY possible if SAP Solution Manager is installed at customer site
:K\ 6$3 6ROXWLRQ 0DQDJHU IRU P\6$3 (53"
Optimal access to all support services Faster issue resolution through optimal collaboration with Active Global Support
Faster implementation and more efficient operation of mySAP ERP All available implementation and upgrade content included Optimal support of all operations, maintenance and improvement activities
6LJQLILFDQW UHGXFWLRQ RI 7&2 RI P\6$3 (53
SAP AG 2006
SAP AG
SM100
2-18
,PSOHPHQWLQJ 6$3 6ROXWLRQV 3URFHVV LQ 'HWDLO

C $% d e ((
,VVXH 7UDFNLQJ 0RQLWRULQJ 5HSRUWLQJ 5RDGPDSV
3URMHFW $GPLQLVWUDWLRQ
SAP AG 2006
Solution Manager for Implementation Procedure Model (Roadmaps) Focus: product-specific information; no project management Knowledge transfer to project team and technical implementation aspects are key elements Available services aligned with the Procedure Model
Implementation Content Business process repository as initial input for a process-driven design of a customer solution Initial focus: mySAP CRM and mySAP SCM implementations
Tools Basic ASAP tools (Blueprint and Master List functionality) Integrated use of customizing and test tools Focus: scoping, process-oriented configuration and testing, status and issue tracking
SAP AG
SM100
Ce!r%$(h % " 5 Cqd
6e d` 3 %( `
((% & d $" B E cCe! ' "
$ #e "
% B $ "
o " x0 `" 0

%T a `$(
$% R a &R %T " r(Y!Rd

'
2-19
6$3 6ROXWLRQ 0DQDJHU DV FHQWUDO FROODERUDWLRQ KXE

6$3 &XVWRPHU
Experts
SAP Solution Manager

Service Marketplace Knowledge
6HUYLFH ,QIUDVWUXFWXUH $SSOLFDWLRQ 0DQDJHPHQW
SAP AG 2006
Issues: Harmonize Visualization of System Landscapes in SLM and Solution Manager Scenarios are shipped via BPR/Service Marketplace and Master Component Repository Scenarios implemented are stored in Solution Manager and SLD Clarify relationship between Versions in Solution Manager and and Editions in Solution Builder (PPMS) Interfaces between Solution Manager and SLM have to be defined Define Use Cases
SAP AG
SM100
n q 22dee p p nq d o onnmee m m m $(gQQ Qll QkgQQ k g ddfj ssxQhii h f f f22dee d g
3%s%C&s E %r "
Ce$
6ROXWLRQ /DQGVFDSH
2-20
" 6$ ) Y
"
6$3 6ROXWLRQ 0DQDJHU 9DOXH 3URSRVLWLRQ

&ROODERUDWLRQ &XVWRPHU
7KH VXSSRUW KXE DQG WKH JDWHZD\ WR 6$3

SAP AG 2006
On the right-hand two-thirds of the slide you have a greyed-blue box representing the customer s environment. Their IT landscape contains the applications we d expect to see some SAP and some not. In the center of this landscape we have the core business processes that drive the company, and the IT group s charter to implement, operate, and continually optimize these processes, as well as the applications. The goals of the CIO are represented in black in this box efficiency, transparency, control, and flexibility. (These are the four core value props that SAP Solution Manager provides) That is, if a CIO could maximize these four goals then the chances of success in their mission would be significantly increased. Moving to the left, the customer s IT landscape is connected to the SAP Solution Manager. SAP Solution Manager is a unique solution stack which enables several of its integrated business processes to seamlessly interact with the customer s IT landscape (change management, service desk, etc). These business processes are core function within SAP Solution Manager and replace the customer s need to purchase, implement, and maintain separate software and hardware solutions that provide these functions. This is one very significant benefit that SAP Solution Manager brings the ability to replace several un-integrated tools with a single product which provides seamless integration, a single user interface (for ease of use), and which comes at no extra cost as a part of their SAP Standard Support. The importance of SAP Solution Manager in both cost and efficiency terms cannot be over-stated. However, there s an additional benefit with SAP Solution Manager, and that is its role as a gateway to SAP s Active Global Support (AGS) organization and the network of over 12,000 professionals we can call upon to assist our customers. Specifically (on the far left-hand of the slide), AGS is able to interact with a number of SAP organizations to ensure that our customers receive the right assistance at the right time. These organizations would include SAP Development, SAP Consulting, and so on. This unique solution stack logs the information AGS needs to address a customer s OSS issue, which in turn means we can respond faster and more accurately than otherwise. That is, SAP Solution Manager provides our customers with all the productivity and response time benefits of e-support as well as with the certainty that their needs and challenges are being dealt with by the most expert resource available.
SM100 2-21
SAP AG
&
CPC $% 3%`5 # TC&dd
| ~}|{ 9bv9vz
` % %v %t u
( 3R ((e" 0
{ | gz

} e h}R 8 }}}97 #w
}%e%%6C
| 99| {
y }% &sybx 63
w
o U & C
} tU( y % 3 CtU( y b`
& tU y b &o % 3}}
} & U e% &2hU
&}x U
} C U %}} X w U( 3C F(
w
6$3 6ROXWLRQ 0DQDJHU 6FHQDULRV

,PSOHPHQWDWLRQ RI 6$3 VROXWLRQV
SAP Methods & Tools Global rollout Customizing sync. E-learning mgmt. Test management
6ROXWLRQ PRQLWRULQJ
System monitoring EarlyWatch Alert Service level reporting Business process monitoring Central system administration
'HOLYHU\ RI 6$3 VHUYLFHV

Onsite/remote delivery SAP Safeguarding
&KDQJH UHTXHVW PDQDJHPHQW

Follows ITIL standards Maintenance processes
SAP AG 2006
SAP AG
SM100
{ | gz
SAP Methods & Tools E-learning mgmt. Test management
&RUH %XVLQHVV 3URFHVV
| ~}|{ 9bv9vz
8SJUDGH RI 6$3 VROXWLRQV
| v| gk{
6HUYLFH GHVN
Best Practices for messaging Solution Manager Diagnostics
2-22
6$3 6ROXWLRQ 0DQDJHU /LFHQVLQJ

*HQHUDO
All licenses to support customers own, licensed SAP systems are included in the standard maintenance fee, e.g. CRM, BI and KW licenses.
0RQLWRULQJ
Licenses to implement or monitor customers own non-SAP solutions are included in the standard maintenance fee as well
,PSOHPHQWDWLRQ
6HUYLFH 'HVN
Each user working on non-SAP messages needs an own professional user in the SAP Solution Manager system
SAP AG 2006
Details on licensing has to be clarified with your local account representative.
SAP AG
SM100
2-23
5HOHDVH 6WUDWHJ\
0RWLYDWLRQ
6XSSRUW IRU ,7,/ SURFHVVHV $YDLODEOH )XQFWLRQDOLWLHV 5HOHDVH 6WUDWHJ\
SAP AG 2006
SAP AG
SM100
2-24
(YROXWLRQ IURP $6$3 WR 6$3 6ROXWLRQ 0DQDJHU

$ `
Front-end to SAP Service Infrastructure Solution Implementation Service Desk, Monitoring & Distribution Upgrade Change Request Management Cooperation + Continuous Improvement Mitigate Risk Pro-active Monitoring Accelerate Optimize Implementations IT Support Manage Technical Change Optimize Collaboration with SAP Services
SAP AG 2006
SAP AG
SM100
% 4
Y %
% sT
c% %
% Y
2-25
C Y B $

!(
v 9
(9
vv
vv
9k9
vv
k9
22 n 29 nQQ9 2g nnQ s n9 22Q n2Qn n 29 nQ9
}%6} Uoje3} U
s
nu r )j # r )j r )j
}}6 RXj}6r R
sg
}X Uoj`3 U
222 n v n2!9 s2 nnQ s k 2$2Q
ggT n s 29 2 gk nQ2n n v 2
ggT n n s Q9 g Q sQ22 n v
}}o U6h`&} %R o %Roh`& F
sg
Qq j T )&x
SAP AG

SAP AG 2006
The Mainstream Maintenance of the SAP Solution Manager 4.0 is geared to the Extended Maintenance of the SAP NetWeaver 04 release.
SAP Solution Manager 3.2 will stay in mainstream maintenance until March 2009. Afterwards, it will move into customer-specific maintenance.
SAP Solution Manager 4.0 is focusing on optimizing support processes, collaboration, and implementing continuous improvement processes. The mass shipment of SAP Solution Manager 4.0 has started in April 2006.
5HOHDVH 6WUDWHJ\ DQG 0DLQWHQDQFH
SM100
2-26
5RDGPDS IRU 6$3 6XSSRUW ,QIUDVWUXFWXUH
SAP AG 2006
6$3 6ROXWLRQ 0DQDJHU This upcoming release will focus on three major aspects: Enhanced support of \RXU NH\ VXSSRUW SURFHVVHV The SAP Solution Manager 4.0 release will offer functionality to assist you with your major application management tasks. For example, it will allow you to implement support packages and SAP notes end-to-end. SAP Solution Manager 4.0 will provide functionality to automatically identify relevant patches, and document and manage their implementation, testing, and import to your production systems. &RQWLQXRXV LPSURYHPHQW services: The SAP Solution Manager has detailed information about your solution, such as key business processes and the SAP system landscapes. If your SAP competence center selects the new continuous improvement service offering, an appointed SAP contact will be named, and will actively work with you on a regular basis to solve your business-critical SAP issues. 7HFKQLFDO LQWHJUDWLRQ of Solution Manager Diagnostics into the SAP Solution Manager platform.
SAP AG

(4 '
s r s9 sj s r
SAP Solution Manager required for root cause analysis of all SAP solutions Corporate functionality only via SAP Solution Manager Mass shipment SAP Solution Manager 4.0 Start of Ramp-Up SAP Solution Manager 4.0
SAP Solution Manager 4.0
WebAS 7.00
Solution Manager Diagnostics required for root cause analysis of Java based SAP solutions Mass shipment SAP Solution Manager 3.2 mySAP ERP 2004 requires SAP Solution Manager Improved message entry process via SAP Support Portal Mass shipment Solution Manager Diagnostics
SAP Solution Manager 3.2

WebAS 6.20
Solution Manager Diagnostics

WebAS 6.40
SM100
2-27
6$3 6ROXWLRQ 0DQDJHU .H\ %HQHILWV

'HOLYHUHG DW QR DGGLWLRQDO FRVW ,QFUHDVLQJ UHOLDELOLW\ RI ,7 VROXWLRQ 5HGXFLQJ FRVW RI LPSOHPHQWDWLRQ RSHUDWLRQV DQG FKDQJH PDQDJHPHQW SURMHFWV $FFHOHUDWLQJ WLPH WR EHQHILW /HYHUDJLQJ H[LVWLQJ ,7 LQYHVWPHQWV $YDLODEOH IRU H[LVWLQJ 6$3 VROXWLRQV
SAP AG 2006
mySAP ERP 2004 is designed to meet todays changing demands on ERP. It enables new levels of business process and technology integration while laying the foundation for incremental evolution of your solution. Using the SAP Solution Manager along the lifecycle of your mySAP ERP solution leads to a IDVWHU LPSOHPHQWDWLRQ DQG PRUH HIILFLHQW RSHUDWLRQ by providing all implementation and upgrade content for commonly used standard processes. In addition, projects become more transparent by having the up-to-date central project documentation all in one place at any point in time. To ensure the availability of this application management platform, a SAP Solution Manager system (minimum requirement 3.1 SP20) is WHFKQLFDOO\ UHTXLUHG to perform any upgrade or installation of mySAP ERP 2004.
SAP AG
SM100
2-28
6XPPDU\
6$3 6ROXWLRQ 0DQDJHU HQVXUHV

7UDQVSDUHQF\ (IILFLHQF\ )OH[LELOLW\ &RQWURO
entire IT landscape SAP and non-SAP entire solution lifecycle gateway to SAP services aligned with SAPs best practices
tools, content, and services scenario driven
full integration
SAP AG 2006
These four points represent the core value proposition of SAP Solution manager. Transparency the ability for a CIOs solution lifecycle and IT landscape (SAP and non-SAP) to be made transparent through SAP Solution Managers functionality Efficiency a platform (SAP Solution Manager) which provides best-in-class best practices which promote efficiency and operational effectiveness, as well as providing a gateway to SAPs support. This gateway function is important because it leverages the EarlyWatch alerts which are automated, seamless health checks for the customers SAP landscape and core business processes. Flexibility the capability to utilize SAP Solution Manager in a number of different ways (use cases) to maximize its impact on the organization and minimize operating costs. Control this is a critical and elusive target for a CIO, and SAP Solution Manager is able to provide it because of its complete integration as well as the way in which it can automatically map and analyze the core business processes within the SAP application landscape. Inevitably, such a degree of control will lower the time it takes to achieve a return on the implementation of SAP Solution Manager.
SAP AG
SM100
2-29
6ROXWLRQ 0DQDJHU 2YHUYLHZ 8QLW 6XPPDU\
([SODLQ WKH JHQHUDO DQG UHOHDVH VWUDWHJ\ RI WKH 6$3 6ROXWLRQ 0DQDJHU
*HW DQ JHQHUDO RYHUYLHZ RI WKH 6$3 6ROXWLRQ 0DQDJHU IXQFWLRQDOLWLHV
'HVFULEH WKH DQGDYDQWDJH RI WKH 6$3 6ROXWLRQ 0DQDJHU
<RX VKRXOG QRZ EH DEOH WR
SAP AG 2006
SAP AG
SM100
2-30
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
3-1
2EMHFWLYHV 6HWWLQJ 8S 6ROXWLRQ /DQGVFDSHV
$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR 'HVFULEH WKH XVH RI 6/' DQG 706 /,6 6HWXS \RXU V\VWHPV LQ WUDQVDFWLRQ 606< *HQHUDWH WKH QHFHVVDU\ 5)& FRQQHFWLRQV 8VH WKH 6ROXWLRQ 'LUHFWRU\
6HWXS %XVLQHVV 3URFHVVHV 6ROXWLRQ $WWULEXWHV /RJLFDO &RPSRQHQWV
&UHDWLQJ 6ROXWLRQ /DQGVFDSHV
SAP AG 2006
SAP AG
SM100
3-2
6HWWLQJ XS 6ROXWLRQ /DQGVFDSHV

6$3 6ROXWLRQ 0DQDJHU LQ 6\VWHP /DQGVFDSH 6\VWHP /DQGVFDSH 7UDQVDFWLRQ 606< *HQHUDWH 5)&'HVWLQDWLRQV /RJLFDO &RPSRQHQWV %XVLQHVV 3URFHVVHV 6ROXWLRQ /DQGVFDSHV
6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-3
6\VWHP /DQGVFDSH 'LUHFWRU\ 6/' 6\VWHP /DQGVFDSH 'LUHFWRU\ 6/'
,W SURYLGHV LQIRUPDWLRQ WKDW LV UHTXLUHG IRU D YDULHW\ RI DSSOLFDWLRQV DQG SURFHVVHV

6RIWZDUH /LIHF\FOH 0DQDJHPHQW 6$3 ([FKDQJH ,QIUDVWUXFWXUH 6$3 1HW:HDYHU 'HYHORSPHQW ,QIUDVWUXFWXUH 6\VWHP 0DQDJHPHQW /DQGVFDSH UHODWHG VXSSRUW VHUYLFHV EDVHG RQ 6$3 6ROXWLRQ 0DQDJHU
$V 6\VWHP /DQGVFDSH 'LUHFWRU\ LV DOUHDG\ FRQWDLQHG LQ WKH LQVWDOODWLRQ RI HYHU\ 6$3 :HE $SSOLFDWLRQ 6HUYHU -DYD RU KLJKHU
,W LV FRPSOHWHO\ LPSOHPHQWHG ZLWK -DYD WHFKQRORJ\ DQG GHSOR\HG DV D -DYD FRPSRQHQW RQ WKH 6$3 :HE $SSOLFDWLRQ 6HUYHU
6\VWHP /DQGVFDSH 'LUHFWRU\ LV DQ 6$3 1HW:HDYHU FRPSRQHQW
SAP AG 2006
Todays system landscapes consist of multiple distributed software components with different platform dependencies, different interfaces, and different requirements placed on installation and change management. An overall concept is required that facilitates the implementation, upgrade, and maintenance of your system landscapes including the SAP NetWeaver system landscape you are installing. This is where 6\VWHP /DQGVFDSH 'LUHFWRU\ (SLD) comes into play. The most straightforward scenario is the use of a single SLD. However, depending on organizational, operational, or security reasons, it is also possible to have more than one SLD distributed over the system landscape. Automatic message forwarding as well as sophisticated data export and import functions are provided to support the operation of multiple SLDs.
SAP AG
SM100
3-4
6$3 6ROXWLRQ 0DQDJHU 6\VWHP /DQGVFDSH DQG 6/'

$OVR 6$3 6ROXWLRQ 0DQDJHU SURYLGHV D V\VWHP GDWD UHSRVLWRU\ 7UDQVDFWLRQ &RGH 606< %RWK V\VWHP GDWD UHSRVLWRULHV 606< DQG 6/' FDQ EH XVHG LQGHSHQGHQWO\ RI HDFK RWKHU 6\QFKURQL]DWLRQ SRLQWV H[LVW 606< FDQ UHDG GDWD IURP 6/' 7KH XVH RI WKHVH UHSRVLWRULHV GHSHQGV XSRQ FXUUHQW FXVWRPHUV ODQGVFDSH
,I WKHUH DUH RQO\ $%$3 FRPSRQHQWV LQ SODFH 6/' LV RSWLRQDO ,I WKHUH DUH DOVR -DYD FRPSRQHQWV LQ SODFH 6$3 1HW:HDYHU (QWHUSULVH 3RUWDO 6$3 1HW:HDYHU ([FKDQJH ,QIUDVWUXFWXUH HWF 6/' LV PDQGDWRU\
SAP AG 2006
You set-up the automatic data transfer from the Landscape Information System (LIS) and the System Landscape Directory (SLD), to get system data for the 6ROXWLRQ 0DQDJHU 6\VWHP /DQGVFDSH. automatically with this data. 3UHUHTXLVLWHV For using the /DQGVFDSH ,QIRUPDWLRQ 6\VWHP /,6: You have assigned the Solution Manager to a transport domain in the Transport Management System (STMS) Or you have specified the Solution Manager system as the new domain controller in the transport management system. The SAP Solution Manager can get server, database and system data
For using the 6\VWHP /DQGVFDSH 'LUHFWRU\ 6/': You have setup the System Landscape Directory (SLD).
SAP AG
SM100
3-5
(VWDEOLVK &RQQHFWLRQ IURP 6$3 6ROXWLRQ 0DQDJHU WR 6/'
SAP AG 2006
The Solution Manager system data should be saved in its SLD. 5HTXLUHPHQWV <RX KDYH LQVWDOOHG D 6ROXWLRQ 0DQDJHU 'RXEOH 6WDFN A connection to send system data to SLD is created automatically. To send data from SLD to ABAP you must start a server in Java. This server will wait for ABAP calls. For the communication between ABAP and Java the SAP Solution Manager needs the user SAPJSF. The user SAPJSF is assigned in the Visual Administrator. This User is used to read data from SLD. You have to activate an RFC connection (such as sapsldapi_J2E) in the Visual Administrator for SLD under -FR 5)& 3URYLGHU -> 5)& GHVWLQDWLRQ.
SAP AG
SM100
3-6
6HWXS 'DWD 7UDQVIHU 2SWLRQ

6ZLWFK WR 6/' DV V\VWHP GDWD UHSRVLWRU\
7R EH GHILQHG LQ WUDQVDFWLRQ 606<B6(783
SAP AG 2006
You should choose the System Landscape Directory (SLD) as the source for the data transfer, if SLD is set-up in your system landscape. The Landscape Information System (LIS) only gets data about system names, clients and software components in the systems, for systems in the transport domain. SLD gets server and database data independently of the transport domain. To access the 6\VWHP /DQGVFDSH 'LUHFWRU\ 6/': Choose (GLW ([SHUW 6HWWLQJV.
Specify the server from which SLD data is to be read, as 6/' +RVW. You can change the other options. You can also change these options when setting-up the System Landscape Directory. You can write data back into SLD by entering a value for :ULWH 'DWD %DFN LQWR 6/'. Choose &RQWLQXH.
For further information, see 6\VWHP /DQGVFDSH 'LUHFWRU\ in the SAP Library.
SAP AG
SM100
3-7
$XWRPDWLF 6\VWHP 'DWD &DSWXULQJ XVLQJ /,6706 RU 6/' /DQGVFDSH ,QIUDVWUXFWXUH 6HUYHU /,6 706
5HDGV WKH GDWD IURP WKH 7UDQVSRUW 0DQDJHPHQW V\VWHP ZKHUH DOO V\VWHPV LQFOXVLYH WKH 6$3 6ROXWLRQ 0DQDJHU EHORQJV WR ,V WKH FHQWUDO LQIRUPDWLRQ SURYLGHU LQ D V\VWHP ODQGVFDSH
6\VWHP /DQGVFDSH 'LUHFWRU\ 6/'
6/' VKRXOG EH XVHG LI 6$3 ([FKDQJH ,QIUDVWUXFWXUH ;, LV DOVR LQ XVH
&DQ UHJLVWHU DQ\ WKLUGSDUW\ SURGXFWV LQ WKH V\VWHP ODQGVFDSH
.HHSV LQIRUPDWLRQ DERXW DOO DYDLODEOH 6$3 SURGXFWV FRPSRQHQWV DQG YHUVLRQV
SAP AG 2006
Systems outside of LIS and SLD can not be imported automatically. If you have systems outside of LIS and SLD,
you will need to maintain the configuration manually. The job will check whether system data (client, application server or new system) has changed and updates this data in transaction SMSY.
SAP AG
SM100
3-8
:KLFK GDWD LV UHWULHYHG IURP /,6706 DQG IURP 6/'"

'DWD UHWULHYHG IURP /,6 )RU $%$3 V\VWHPV 'DWD UHWULHYHG IURP 6/' )RU $%$3 V\VWHPV
7KLV GDWD LV FROOHFWHG IRU DOO V\VWHPV HPEHGGHG LQWR WKH WUDQVSRUW GRPDLQ RI 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
The System Landscape Directory (SLD) contains two kinds of contents: the FRPSRQHQW LQIRUPDWLRQ and the ODQGVFDSH GHVFULSWLRQ: The ODQGVFDSH GHVFULSWLRQ provides an exact picture of installed landscape elements including the connections between the systems. The content of the landscape description is created during the landscape implementation and automatically maintained through the whole software life-cycle.
The FRPSRQHQW LQIRUPDWLRQ describes the building blocks of solutions and their possible combinations and dependencies. It describes the world of installable landscape elements. The various types of dependencies between building blocks play an important role in landscape implementation, change management and solution validation. The content of the component information is delivered by SAP and can be updated - for more information about updating the component information, see SAP Note 669669.
SAP AG
SM100
ECdCC% 34 c S c @ B B g B c g 0 ' 0 4 B v 0 B X%das3XiE ecc r% # c 04 4 S4 %% 3R&R" B @ 0 B 4 S4 reC37 r&R" ' # @ v 0 B rIYs% r%
)RU -DYD V\VWHPV
B B B v 0 4 S4 % B C2&R" ' # B v 0 B B B CrICRT B B 4 S4 r%2&R" reC37 r&R" B @ 0 B 4 S4 ' # @ v 0 B rIYs% r% ECdCC% 34 c S c @ B B g B c g X%das3XiE ecc r% f 0 ' 0 4 B v 0 B w w c B c %C%w b C & `C ' dv1 0eY%d3%6&&% eA9 04 B '4 0v c 4 S4 7 B r1%%( 4CCer$" ' H ' # ' B ' # C%er$"
3-9
2a0bdiC `cc 0 ' 4 B v 0 B w w w c B c rC e ' 0 v B '4 0v c Y4Y120 P32&`3r et9 4CC&CsI( S4 7 B 4 ' H ' # CC&%R" ' B ' # &%R"
6\VWHP /DQGVFDSH 'LUHFWRU\ &RQWHQW

7KUHH FDWHJRULHV &RPSRQHQW UHSRVLWRU\ &5 /DQGVFDSH GDWD /'
FOLHQWV VHUYHUV 3URGXFWV DQG VRIWZDUH FRPSRQHQWV 6\VWHPV DQG V\VWHP JURXSV
EXVLQHVV V\VWHPV
1DPH UHVHUYDWLRQ GDWD 15

PDQDJH QDPH UHVHUYDWLRQ IRU GHYHORSPHQW &,0 FODVV GHILQLWLRQV YLHZ DQG FKDQJH &,0 GDWD
SAP AG 2006
CR- is the component repository data. It includes the possible versions, support packages and its combinations for pre-selections. e.g. For product R/3 there are the allowed version 3.1, 4.0b. 4.0B, 4.0C,this would be CR. With help of CR content SAP avoid wrong or non existing LD data for SAP products. LD- these are the concrete descriptions of existing systems e.g. There is a R/3 System version 3.1 SID Support Package xxx NR- is important for development if you have reserved name spaces for developed objects. CIM-Common Information Model -> Skip to next slide
SAP AG
SM100
3-10
6\VWHP /DQGVFDSH 'LUHFWRU\ 6WDQGDUGV

&RPPRQ ,QIRUPDWLRQ 0RGHO &,0
&,0 LV D FRPPRQ GDWD PRGHO RI DQ LPSOHPHQWDWLRQ QHXWUDO VFKHPD IRU WKH GHVFULSWLRQ RI RYHUDOO LQIRUPDWLRQ LQ D QHWZRUNHQWHUSULVH HQYLURQPHQW ,V DQ ,PSOHPHQWDWLRQ RI WKH 'LVWULEXWHG 0DQDJHPHQW 7DVN )RUFH
V '07) :HE%DVHG (QWHUSULVH 0DQDJHPHQW :%(0 LQLWLDWLYH '07) DV WKH LQGXVWU\ RUJDQL]DWLRQ OHDGLQJ GHYHORSPHQW DGRSWLRQ DQG XQLILFDWLRQ RI PDQDJHPHQW VWDQGDUGV DQG LQLWLDWLYHV IRU GHVNWRS HQWHUSULVH DQG ,QWHUQHW HQYLURQPHQWV /DQGVFDSH 'HVFULSWLRQ DQG &RPSRQHQW ,QIRUPDWLRQ EDVHG RQ &RPPRQ ,QIRUPDWLRQ 0RGHO &,0 RI WKH '07)
SAP AG 2006
SLD is the SAP solution of a proposal by Distributed Management Task Force (DMTF). They founded an initiative called Web-Based Enterprise Management. SAP is in leadership at DMTF. The common Information Model is one outcome. It has become a de facto standard for describing and storing data on a system landscape. The System Landscape Directory bases on that CIM.
SAP AG
SM100
3-11
&HQWUDO 6/' IRU DOO 6$3 1HW:HDYHU $SSOLFDWLRQV

6/'
:HE '\QSUR
:HE '\QSUR
SAP AG 2006
&HQWUDO 6/' IRU $OO $SSOLFDWLRQV Simplicity is often the key to robust and easy to handle system landscapes. The use of only one central SLD for an entire system landscape is shown above. Possible SLD clients are the SAP Exchange Infrastructure (SAP XI), SAP Solution Manager, WebDynpro applications, and the SAP NetWeaver Development Infrastructure (NWDI). These systems may consist of several instances for development (Dev), quality assurance (QA), and production (Prod). Nevertheless, all instances are bound to one central SLD. This imposes high demands on the SLD regarding availability and stability. +LJK DYDLODELOLW\ concerning operation, maintenance, and upgrade of the SLD is crucial for clients that depend on SLD data.
SAP AG
SM100
errr`|r ~ z ~|{zxw v u }yyUt sq rr 3p
my2
sq rr 3p
NetWeaver Development Infrastructure
nl omk
ji 3h
`XR`|&} 6 | ~ sq rr dp nl omk nl 5ok ji dh ji 3h
+$ &OXVWHU
6/'
3-12

6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-13
7UDQVDFWLRQ 606< &UHDWLQJ 6HUYHU (QWULHV
SAP AG 2006
The system determines the displayed data automatically, if you have set-up automatic data capture for the system landscape. The system cannot determine all server data automatically, so you can complete it, e.g. with the frequency. You create attributes for servers, databases, systems, system components and main instances, to be able to assign additional properties to them, e.g. hardware attribute information or the person responsible for a system.
SAP AG
~ | | z z { }qÀd z yy} X| ye|3z z ~ ~|z |~ z % ~ } }AyF | | ~ { z { % z 6q&} ~

SM100 3-14
7UDQVDFWLRQ 606< &UHDWLQJ 'DWDEDVH (QWULHV
SAP AG 2006
3UHUHTXLVLWHV 3URFHGXUH
You are in the 6ROXWLRQ 0DQDJHU 6\VWHP /DQGVFDSH transaction SMSY). Select the landscape component 'DWDEDVHV, and choose &UHDWH in the context menu. Enter the required data. Choose attribute values from the possible entries help in the Other Attributes tab. Save the changes.
SAP AG
| }y|| ~ | | z z { A6}6yARy z A} X| ye|3z z ~ ~|z |~ z % ~ } }AyF | | ~ { z { % z 6q&} ~

SM100 3-15
7UDQVDFWLRQ 606< &UHDWLQJ 6\VWHP (QWULHV
SAP AG 2006
You create systems to be able to use them in Solution Manager projects. The system determines the displayed data automatically for ABAP-based SAP products, if you have setup automatic data capture for the system landscape. You can enhance this data or switch the data source to manual maintenance. For non-ABAP-based SAP products, and non-SAP-products, you must create systems yourself, to use them in your solution landscape in operational processing. You can also create systems under the guidance of assistants. To call the assistant, select the landscape component 6\VWHPV, and choose &UHDWH 1HZ 6\VWHP ZLWK $VVLVWDQWV, in the context menu.
SAP AG
~ | | z z { A6}6yARy z A} }X|} ~ z~ ~ Uq } %o3 ~ X| ~ R | ~ z t { | e ~ z } 6v | ~ { ~ ~ z v }3 | 6 ~~ v{ z % y%| }r } t

SM100 3-16

6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-17
3UHUHTXLVLWHV 6DWHOOLWH 6\VWHPV 3UHSDUDWLRQ

&KHFN 8VHU 3URILOHV LQ 6DWHOOLWH 6\VWHPV <RX UHTXLUH D XVHU LQ VDWHOOLWH V\VWHPV ZLWK DXWKRUL]DWLRQV IRU WKH IROORZLQJ IXQFWLRQV
*HQHUDWH 5)& FRQQHFWLRQV RI WKH 7UXVWHG W\SH DXWKRUL]DWLRQ REMHFW 6B5)&$&/ QRW SDUW RI 6$3B$// *HQHUDWH 5)& FRQQHFWLRQV DXWKRUL]DWLRQ REMHFW 6B5)&
7R EH DEOH WR JHQHUDWH DQG XVH 7UXVWHG 6\VWHPV WKH XVHU ,'V RI WKH WZR V\VWHPV PXVW EH WKH VDPH
(QVXUH WKDW WKH 6ROXWLRQ 0DQDJHU LV DEOH WR FROOHFW GDWD IRU 6ROXWLRQ 0RQLWRULQJ LQ WKH VDWHOOLWH V\VWHPV
6XSSRUW 6HUYLFHV UHTXLUH WKH DSSURSULDWH 67$3, LQ WKH VDWHOOLWH V\VWHP DV VSHFLILHG LQ QRWH
SAP AG 2006
SAP AG
SM100
3-18
*HQHUDWH 5)& 'HVWLQDWLRQV ,

5)& 'HVWLQDWLRQV ZLWKLQ WKH 6ROXWLRQ 0DQDJHU
60B6,'!&/17&OLHQW!B5($'
60B 60B6,'!&/17&OLHQW!B70: 60B6,'!&/17&OLHQW!B/2*21
5)& 'HVWLQDWLRQV LQ ERWK WKH 6$3 6ROXWLRQ 0DQJHU DQG LQ WKH 6DWHOOLWH 6\VWHP
60B6,'!&/17&OLHQW!B75867('
60B6,'!&/17&OLHQW!B%$&.
5)& 'HVWLQDWLRQ UHTXLUHG LQ WKH 6DWHOOLWH 6\VWHP RQO\
SAP AG 2006
From the System Landscape, transaction SMSY, select Landscape Components and in the tree Systems <Product> <SID> <Instance>. Go to the tab Clients, select the client and choose the Generate RFC Destinations button. A new screen Generate RFC Destinations will be displayed. Select the RFC Destinations to be created by marking the check boxes, and choose the User Option. You can generate RFCs automatically from transaction SMSY.
SAP AG
This RFC will be used to Read system data remote from transaction SMSY, to read the Data Collection method for System Monitoring. This RFC will be used for the Change Manager. This RFC will be used by the System Monitoring for accessing the Analysis Method.
This RFC will be used by the Customizing Synchronization functionality and by the System Monitoring for accessing the Analysis Method.
This RFC will be used to send Service Data and Support Desk messages from the Satellite system to the SAP Solution Manager system.
SM100
3-19
*HQHUDWH 5)& 'HVWLQDWLRQV ,,

7UDQVDFWLRQ 606< FDQ JHQHUDWH WKH IROORZLQJ 5)& FRPELQDWLRQV
2SWLRQ 60B6,'!&/17&OLHQW!B5($' DQG 60B6,'!&/17&OLHQW!B70: 60B6,'!&/17&OLHQW!B/2*21 SAP Solution Manager ? Satellite system SAP Solution Manager ? Satellite system In this combination the RFC *_Back will not be generated. If this is the selected scenario, then RFC destination SOLUTION_MANAGER must be created from the satellite system to the SAP Solution Manager system refer to the Related Content. 2SWLRQ 6,'!&/17&OLHQW!B5($' DQG 60B6,'!&/17&OLHQW!B70:
60B6,'!&/17&OLHQW!B75867('
60B6,'!&/17&OLHQW!B%$&.
SAP AG 2006
Choose the RFC connection type Trusted System for the SAP Solution Manager, whenever possible. This avoids having to logon again every time that you go to a component system when using the SAP Solution Manager.
You can specify a server group for load sharing, in the 5)& 'HVWLQDWLRQ $WWULEXWHV group box. If the specification of the message server is not sufficient to set-up an RFC connection in your network, or your network contains routers: Choose 5RXWLQJ ,QIRUPDWLRQ in the 5)& 'HVWLQDWLRQ $WWULEXWHV group box. The following dialog box displays the message server data. If you have not yet created the system message server as a server, it is created automatically and displayed at the left-hand side under /DQGVFDSH &RPSRQHQWV, when you restart the 6ROXWLRQ 0DQDJHU 6\VWHP /DQGVFDSH transaction. Specify any IP address. Specify the routing information for the direction 6ROXWLRQ 0DQDJHU ! 5RXWHU ! 6HUYHU, e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12 Specify the routing information for the direction 6HUYHU ! 5RXWHU ! 6ROXWLRQ 0DQDJHU , e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12
SAP AG
SAP Solution Manager ? Satellite system SAP Solution Manager ? Satellite System Satellite System ? SAP Solution Manager
Satellite System ? SAP Solution Manager
SM100
3-20
*HQHUDWH 5)& 'HVWLQDWLRQV ,,,

7KH IROORZLQJ RSWLRQV DUH DYDLODEOH WR FUHDWH XVHUV *HQHUDWH XVHU DQG SDVVZRUG *HQHUDWH XVHU VSHFLI\ SDVVZRUG LQ WKLV FDVH D QHZ ILHOG ZLOO EH RSHQ VR WKDW WKH SDVVZRUG FDQ EH W\SHG LQ 8VH H[LVWLQJ XVHU VSHFLI\ SDVVZRUG LQ WKLV FDVH \RX FDQ W\SH WKH XVHU DQG WKH SDVVZRUG 1RWH 7KHVH VWHSV DUH GHVFULEHG LQ WKH LQVWDOODWLRQ JXLGH
SAP AG 2006
$XWRPDWLF *HQHUDWLRQ RI 5)& 'HVWLQDWLRQV
The optional function for $XWRPDWLF *HQHUDWLRQ RI 5)& 'HVWLQDWLRQV requires the following Support Package levels in the satellite systems:
6RIWZDUH &RPSRQHQW 63
5HOHDVH
6.20 / 6.20 6.40 / 6.40
SAP_BASIS / SAP_ABA
SAP_BASIS / SAP_ABA
SP10
SP00
SAP AG
SM100
3-21
%DVLF &RQILJXUDWLRQ 5)& &RQQHFWLRQV WR 6$3
5)& &RQQHFWLRQV WR 6$3

7KH 5)& &RQQHFWLRQV
&KHFN LI ORDG GLVWULEXWLRQ JURXS LV VHW WR (:$

SAP-OSS (Send Message to SAP) SAP-OSS-LIST-O01 (Update Message from SAP)
&KHFN LI WKH 5)& &RQQHFWLRQ 6$3266 LV ZRUNLQJ SURSHUO\
will be created automatically by the system with a user which has been assigned previously.
3OHDVH UHIHU WR WKH ,0* SDWK

SAP Web Application Server | SAP Web Application Server | SAP Solution Manager| Basic Settings | SAP Solution Manager System | Connection to SAP | Assign user for forwarding Service Desk Message
SAP AG 2006
With transaction SM59 you can adjust the RFC connections. For further information on SAP R/3 Front-end connections, see SAP Notes: 33135, 766505, 24177 To forward Service Desk notifications and Issues to SAP, you need to assign a user to the SAPNet R/3 Front-end connection to SAP. $FWLYLWLHV
1. From the SAP Solution Manager (transaction SOLUTION_MANAGER), choose (GLW -> *OREDO 6HWWLQJV. 2. Choose 'LVSOD\ ! &KDQJH. 3. For SAP Service Marketplace, specify http://service.sap.com as the URL. 4. In the &RQQHFWLRQ WR 6$3 tab, specify SAPOSS as the RFC destination. Note that the entry is casesensitive. 5. For 8VHU IRUZDUGLQJ PHVVDJHV, enter a valid user and a password. This user will require all the authorizations for SAPNet R/3 Front-end for your customer number. 6. Save your changes.
The system automatically generates the following RFC destinations and assigns the S-User and password you specified: SAP-OSS, SAP-OSS-LIST-O01
SAP AG
SM100
3-22
*HQHUDWH ,QVWDOODWLRQ .H\ 7UDQVDFWLRQ 606<

'HWDLOV LQ 1RWH

SAP AG 2006
Goto Transaction SMSY. In order Choose from the Menu: Main Instance | Other Object Insert SID, Push Generate Installation/Upgrade Key Button In the next Pop-up insert system number and message server Push Generate Key Button
Details about the prerequisites can be found in note 811923.
SAP AG
SM100
3-23

6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-24
/RJLFDO &RPSRQHQWV LQ 6$3 6ROXWLRQ 0DQDJHU

<RX XVH ORJLFDO FRPSRQHQWV WR XQLTXHO\ LGHQWLI\ WKH FRPSRQHQW V\VWHPV VLQFH 6$3 6ROXWLRQ 0DQDJHU UHOHDVH
,Q WKH SURMHFW IRU %XVLQHVV %OXHSULQW &RQILJXUDWLRQ 7HVWLQJ &XVWRPL]LQJ 'LVWULEXWLRQ
,Q WKH 6$3 &KDQJH 5HTXHVW 0DQDJHPHQW
'XULQJ RSHUDWLRQ RI \RXU VROXWLRQ LQ 0RQLWRULQJ IRU V\VWHPV DQG EXVLQHVV SURFHVVHV
SAP AG 2006
Importance and Use of Logical Components The logical component is defined centrally in the SAP Solution manager system with specific logical systems assigned to development, quality assurance and production. The definition cannot be changed in the uses, i.e. in projects and solutions. You can assign several logical components to a project or solution. In the project, the logical component must be available to build the business process structure. For some functions in the implementation scenario, you can use the logical component information to logon directly to the component system. The logical components in the operations scenario provide the system information to the solution landscape. Only systems assigned to a logical component are available in the solution landscape.
SAP AG
SM100
3-25
/RJLFDO &RPSRQHQWV 6SHFLILFDWLRQ

$ ORJLFDO FRPSRQHQW LV DQ DGPLQLVWUDWLRQ XQLW ZKLFK XQLTXHO\ DVVLJQV ORJLFDO V\VWHPV WR V\VWHP UROHV IRU D SURGXFW WKURXJKRXW WKH V\VWHP ODQGVFDSH DQG DFURVV SURMHFWV
6$3 GHOLYHUV VRPH SUHGHILQHG ORJLFDO FRPSRQHQWV 7KH VWDQGDUG QDPH IRU 6$3 GHOLYHUHG ORJLFDO FRPSRQHQWV LV 6$3 &RPSRQHQW! HJ 6$3 6ROXWLRQ 0DQDJHU 6$3 1HWZHDYHU $SSOLFDWLRQ 6HUYHU 6$3 1HWZHDYHU %: VHUYHU
SAP AG 2006
Reasons for Logical Components The SAP Solution Manager is a scenario/process-oriented tool. To assign SAP systems to the business process, we need a more flexible object , which is the logical component. It decouples the systems from the business process. You can change systems without changing the business process structure. All the implementation activities, project administration, Business Blueprint and Configuration, were developed for this path. If the same content is required for the system landscape SAP R/3 for America, the implementation scenario of the SAP R/3 EMEA can be duplicated to SAP R/3 America, and only the logical component has to be replaced centrally. You can visualize the system landscape and its sequence, e.g., DEV > QA > PRD, using logical components. New system roles can be built (restricted to 10) according to the customer needs.
SAP AG
t| }} z %
/RJLFDO &RPSRQHQW
SM100 3-26
z~ | z }| ~ ~ R%e} 6Cv r 2
/RJLFDO &RPSRQHQWV LQ 606<

,Q WKH V\VWHP ODQGVFDSH WUDQVDFWLRQ 606< VHOHFW WKH YLHZ 6\VWHP *URXSV DQG /RJLFDO &RPSRQHQWV DQG WKH GHVLUHG ORJLFDO FRPSRQHQW LQ WKLV H[DPSOH ZH XVH WKH ORJLFDO FRPSRQHQW 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
There are several paths to create logical components, either when migrating solutions after an upgrade from SAP Solution Manager 3.1 to SAP Solution Manager 3.2, from the Project Administration or directly in the System Landscape. To create a logical component in the System Landscape, transaction SMSY proceed as follow: Choose System Groups and Logical Components 6HOHFW /RJLFDO FRPSRQHQWV 3URGXFW! Choose Create New Logical Component from the context menu. Enter the required data, choose a product, choose a main instance. Save the changes. Specify the use of the logical component: To use a logical component in system groups, i.e. in solution landscapes for operations, or in projects, set the Active flag in the right hand window. Set the Inactive flag to hide the logical component system-wide from the new uses possible entries help, but retain existing uses of the logical component.
Assign logical systems to the logical components for the various system roles, e.g. as development system, in the Current System Assignments tab.
SAP AG
SM100
3-27

6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-28
&UHDWLQJ D QHZ 6ROXWLRQ /DQGVFDSH
SAP AG 2006
You specify solutions, to use the SAP Solution Manager effectively. A solution contains systems in your system landscape, which you assign according to certain criteria, for example: It contains all systems used in the production processing in your system landscape, i.e. on which one or more of your most important business processes run. You can proactively monitor the business processes, business process steps, and interfaces of these systems (e.g. all production systems). It has a restricted view of the systems in your system landscape, e.g. for a business area.
SAP AG
SM100
3-29
2SHUDWLRQ 6HWXS 6ROXWLRQ /DQGVFDSH
SAP AG 2006
In the past some screen were partially confusing and not very intuitive. Using this screen for the operations setup
you have access to all relevant transaction such as transaction smsy to access the system maintenance or access to the Solution Directory, where you can define so called logical components and link them to the solution landscapes.
SAP AG
SM100
m C 3}% qy &} r C
6} %o% C &}% F}yyA 3
Rq 3 F}} RyX%

3-30
6HOI'LDJQRVLV IRU 6ROXWLRQ /DQGVFDSH

$ 6HOI'LDJQRVLV FDQ EH WULJJHG E\ FKRRVLQJ *RWR _ 6HOI 'LDJQRVLV IURP WKH PHQX LQ WUDQVDFWLRQ '6:3
SAP AG 2006
This function identifies SAP Solution Manager and solution landscape problems and takes appropriate action. 3UHUHTXLVLWHV You have created at least one solution. )HDWXUHV You can perform self diagnosis at various levels: For the SAP Solution Manager For the SAP Solution Manager DQG a solution
$FWLYLWLHV
Choose the transaction SOLUTION_MANAGER. You go to the SAP Solution Manager: Active Solutions screen. Proceed as follows as you require: To perform self diagnosis for the SAP Solution Manager continue from step 3. To perform self diagnosis for the SAP Solution Manager and a solution, choose the solution. Choose Goto Self Diagnosis. You get an overview of all self diagnosis logs in the system. Choose Message Long Text for the row to see the long text with further information for a diagnosis.
SAP AG
SM100
3-31
You can show or hide the messages by analysis types, with the pushbuttons in the legend. You can, for example, hide all analysis types which only display Information.
SAP AG
SM100
3-32
6ROXWLRQ 'LUHFWRU\ &RQFHSW

7KH 6ROXWLRQ 'LUHFWRU\ LV DQ LQWHUIDFH EHWZHHQ WKH FRQILJXUDWLRQ RI \RXU VROXWLRQV DQG SURGXFWLRQ SURFHVVLQJ &DOO WKH 6ROXWLRQ 'LUHFWRU\
)URP WUDQVDFWLRQ '6:3 " VHOHFW WKH SURSHU 6ROXWLRQ /DQGVFDSH " 2SHUDWLRQV 6HWXS " 6ROXWLRQ 0DLQWHQDQFH RU 7UDQVDFWLRQ 62/0$1B',5(&725< IRU DOO 6ROXWLRQ /DQGVFDSHV
SAP AG 2006
SAP AG
SM100
3-33
7&RGH VROPDQBGLUHFWRU\ $GG \RXU /RJLFDO &RPSRQHQWV
SAP AG 2006
Select the logical component(s) for your Solution Landscape from the pull-down menu The logical system where eCATT scripts and test cases will be stored is the Solution Manager by default. A different system can be selected using the pull-down menu. The advantage with using the Solution Manager is for central storage location for the eCATT scripts and test cases.
SAP AG
SM100
3-34
7&RGH VROPDQBGLUHFWRU\ &HQWUDO 6ROXWLRQ $WWULEXWHV

,Q WKH 6ROXWLRQ 'LUHFWRU\ LW LV SRVVLEOH WR VSHFLI\ FHQWUDO VROXWLRQ DWWULEXWHV DVVLJQ ORJLFDO FRPSRQHQWV DQG ORJLFDO V\VWHPV
SAP AG 2006
You can define, change and delete the system roles and logical components of your solution in the System Group tab as follows: 6SHFLI\ OHDGLQJ V\VWHP UROH QDYLJDWLRQ UROH The leading system role defines all systems in which the business processes run. $GG V\VWHP UROH DQG V\VWHP Choose other system roles if, for example, you want to monitor other systems than your production systems in the solution. You can define user system roles with Edit System Roles. &UHDWH ORJLFDO FRPSRQHQW Choose the possible entries help for the Logical Components column.
SAP AG
SM100
3-35
&HQWUDO 6ROXWLRQ 6HWWLQJV

,W LV SRVVLEOH FKDQJH 6ROXWLRQ 6HWWLQJV LQ WKH 6ROXWLRQ 'LUHFWRU\
SAP AG 2006
Specify the following settings for your solution, in the Solution Settings tab: Day of SAP EarlyWatch data download Choose Setup EWA, to: Deactivate automatic data download Not send the EWAs to SAP
Monitoring graphic refresh period Administration information Knowledge Warehouse Information (You can only display the Knowledge Warehouse information.) Document copy options Copy options Select document types
Central systems for test cases If you flag a central system as obligatory, you no longer need to assign logical components for the business scenarios, to the test cases, in the Test Cases tab.
SAP AG
SM100
3-36
'HVLJQ RI 6ROXWLRQ /DQGVFDSHV

$GPLQLVWUDWRUV ZKR KDYH WKH WDVN WR VHW XS WKH 6$3 6ROXWLRQ 0DQDJHU LQ D FRPSDQ\ KDYH WR GHFLGH DERXW WKH GHVLJQ RI VROXWLRQ ODQGVFDSHV ILUVW 5XOHV RI 7KXPE 6\VWHPV ZLWK ORJLFDO FRQQHFWLRQ RQ EXVLQHVV SURFHVV OHYHO LQ RQH V\VWHP ODQGVFDSH 0D[ V\VWHPV SHU ODQGVFDSH 2QO\ SURGXFWLRQ V\VWHPV LQ RQH ODQGVFDSH '(9 V\VWHPV LQ D VHSDUDWH ODQGVFDSH 4$6
6\VWHPV FDQ RFFXU LQ GLIIHUHQW ODQGVFDSHV HJ D FHQWUDO %: V\VWHP
SAP AG 2006
In early Support Package versions it is possible, that it is only allowed to add systems with the same system role to one system landscape.
SAP AG
SM100
3-37
7&RGH VROPDQBGLUHFWRU\ &RS\ %XVLQHVV 6FHQDULRV &RS\ VWUXFWXUH HOHPHQWV IURP

,PSOHPHQWDWLRQ 3URMHFWV 6ROXWLRQ 'LUHFWRU\
:KHQ VWUXFWXUH 3URMHFW LV VHOHFWHG \RX ZLOO EH SURPSWHG WR VHOHFW WKH 3URMHFW DQG WKH EXVLQHVV VFHQDULR SDUW RI WKLV SURMHFW
:LWK %XVLQHVV 3URFHVV 5HSRVLWRU\ \RX FDQ VHOHFW RQH RU PRUH WKH %XVLQHVV 3URFHVVHV GHOLYHUHG E\ 6$3
SAP AG 2006
In the Solution Directory Structure: Expand the Solution Directory Structure Click Business Scenarios Select the Structure tab Select the scenario source, such as Business Process Repository or Project from the Selection Help pull-down menu Position cursor in the Scenario Name column and use the pull-down menu to list the possible selections
SAP AG
SM100
y & Fr%y
}3} %
%XVLQHVV 3URFHVV 5HSRVLWRU\ %35
3-38

6ROXWLRQ 'LUHFWRU\
SAP AG
SM100
3-39
'HILQH %XVLQHVV 6FHQDULRV

7R GHILQH RZQ EXVLQHVV VFHQDULRV W\SH LQ WKH ILHOG 6FHQDULR 1DPH WKH EXVLQHVV VFHQDULR QDPH GHILQH WKH VWDWXV SODQQHG RU SURGXFWLYH DQG VDYH
7KH %XVLQHVV 6FHQDULR ZLOO EH FUHDWHG LQ WKH WUHH VWUXFWXUH 0DUN %XVLQHVV 3URFHVV LQ WKH WUHH HQWHU WKH EXVLQHVV SURFHVV QDPH LQ WKH ILHOG 3URFHVV QDPH HJ 602 'HPR %XVLQHVV 3URFHVV GHILQH VWDWXV DQG SURFHVV DYDLODELOLW\ DQG VDYH 7KH %XVLQHVV 3URFHVV ZLOO EH FUHDWHG LQ WKH WUHH VWUXFWXUH
SAP AG 2006
The status productive has to be chosen if the Business Process is used for the Operations Area (i.e. for Business Process Monitoring). The predefined content from the SAP can also be copied from the Business Process Repository at the business process and business process step levels. This is how you can leverage content for R/3, R/3 Enterprise, and mySAP ERP, for example.
SAP AG
SM100
3-40
'HILQLQJ WKH %XVLQHVV 3URFHVV 6WHSV

0DUN WKH QHZO\ FUHDWHG EXVLQHVV SURFHVV DQG W\SH LQ WKH EXVLQHVV SURFHVV VWHSV LQ WKH ILHOG 6WHS QDPH GHILQH ORJLFDO FRPSRQHQW DQG SURFHVVLQJ W\SH VXFK DV GLDORJ EDFNJURXQG RU GLDORJEDFNJURXQG
SAP AG 2006
To define new business processes you have the possibility to choose existing business processes from already defined projects existing business processes from the Solution Directory or new business processes from a business process repository
Using the last option you can benefit from a large list of SAP predefined business processes from the most common organizational areas, such as: Product Development and Introduction Sales Marketing Procurement Logistics Finance .
SAP AG
SM100
3-41
6ROXWLRQ 'LUHFWRU\ %XVLQHVV 3URFHVV *UDSKLFV
SAP AG 2006
After saving the newly created business process you can switch to the Graphic tab to already view and, if necessary, change the business process. You can redistribute single steps and/or define new interfaces with the create line option chosen by doing a right mouse click on the step where you want to create a new interface from.
SAP AG
SM100
}C %} C y t} qy }} & qAFA e }
yt% % %y & yq

3-42
6ROXWLRQ 'LUHFWRU\ %XVLQHVV 3URFHVV 0DLQWHQDQFH
SAP AG 2006
In order to create a new business process, or edit an existing one, choose Business Scenarios (If there is none, you can create one by entering its name in the Structure tab). At the child tree element Business Processes, you can create and maintain business processes. Process templates are available. For support the
2SHUDWLRQ 7HPSODWH is the most appropriate. Once you have updated the processes or steps, close the Solution Directory and go back to your original session, open another check and save it, and then open this check where you will see the updated data of the business processes.
SAP AG
SM100
EF%}X Ft& 6 `} }qFy d

3-43
'DWD %DVLV LQ 6$3 6ROXWLRQ 0DQDJHU 2SHUDWLRQV
SAP AG 2006
Here you can see how everything we have discussed is coming together: Starting on the left side with defining projects, using the business process repository and the operation templates Then you would proceed with defining your business processes, scenarios and the single steps This is then used and visible within the Solution Directory and assigned to the Solution Landscape In the back of these definitions within the Solution Directory you will find the logical components with its products, systems etc, maintained within the transaction SMSY
SAP AG
SM100
UC C&%$ qy6% y } d %
3-44
C2Ca % 2
}%
}%
6} %R
E% %CCP2 %Ù
F 3 &3e YeU
rR%%3RP%e%
%3RP%e%
C U%%Ce %yy }% % 6}X}
X }% %
8QLW 6XPPDU\
1RZ \RX DUH DEOH WR 'HVFULEH WKH XVH RI 6/' DQG 706 /,6 6HWXS \RXU V\VWHPV LQ WUDQVDFWLRQ 606< *HQHUDWH WKH QHFHVVDU\ 5)& FRQQHFWLRQV 8VH WKH 6ROXWLRQ 'LUHFWRU\
6HWXS %XVLQHVV 3URFHVVHV 6ROXWLRQ $WWULEXWHV /RJLFDO &RPSRQHQWV
&UHDWLQJ 6ROXWLRQ /DQGVFDSHV
SAP AG 2006
SAP AG
SM100
3-45
$GGLWLRQDO ,QIRUPDWLRQ
)RU PRUH LQIRUPDWLRQ UHIHU WR WKH 6$3 6HUYLFH 0DUNHWSODFH VHUYLFHVDSFRPVROXWLRQPDQDJHU 0RUH ,QIRUPDWLRQ DERXW 6/' VHUYLFHVDSFRPVOG
6HOI 6WXG\ /HDUQLQJ 0DSV IRU 6$3 6ROXWLRQ 0DQDJHU VHUYLFHVDSFRPUNWVROPDQ
SAP AG 2006
SAP AG
SM100
3-46
([HUFLVH
&KDSWHU 6ROXWLRQ /DQGVFDSHV
At the conclusion of this exercise, you will be able to: Create a solution landscape in the SAP Solution Manager Create a Business Process in the SAP Solution Manager Creating a solution landscape and a Business Process are the essential parts for using the Operations Part of the SAP Solution Manager.
In order to be able to setup a new solution, you have to define all required components first. 1-1 1-2 1-3 Right-click on 'DWDEDVHV and define a new database called '[[. Call transaction SMSY and define a new server GXPP\B[[ .
Right-click on 6\VWHPV and choose FUHDWH QHZ V\VWHP ZLWK DVVLVWDQW . Use the same SID as you have used for the database. The system data: 6$3 (&& Installation number: [[ System number: ECC Server: UHOHYDQW
Client:
Message Server: GXPP\B[[
Now we come to the next assistant who helps us to create and /or assign logical components to our newly created system. 1-4
Define a new logical component =B0\&RPSRQHQWB[[ with the role 3URGXFWLYH 6\VWHP and the client 100.
Create a solution landscape in the SAP Solution Manager called 60[[ and include the logical components for training systems 77 (SAP Solution Manager), 77 (SAP ECC), your own system '[[ (SAP ECC), &53 (CRM Server), and :06 (WMS) into the Solution Landscape. 2-1 Call Transaction DSWP and create a new solution. Enter the Solution name 60[[ . Assign the logical components in the Solution Landscape Maintenance to this solution landscape.
2-2
Change the 6ROXWLRQ 6HWWLQJV and setup EWA. Setup the monitoring refresh period to 10 minutes. Add yourself as a contact person for the solution.
SM100 3-47
SAP AG
In this exercise you create an own business scenario with two business processes. 3-1 3-2 3-3 Within the Solution Directory click on Business Scenarios. Create a new Business Scenario My Business Scenario xx with status Production . Choose a new business process Customer Order from the Business Process Repository with status Production and process availability of 7x24h . Create a new business process with the name My Little Process xx and define two own business process steps. Connect both systems with a synchronous line and assign some dialog transactions of your choice to the process steps.
,Q WKH 6$3 6ROXWLRQ 0DQDJHU V\VWHP 4 Optional Exercise: 4-1 Within the Solution Directory, where you have just created your business processes, click on the button Business Process Details to access the Business Process maintenance. In the first screen choose the checkbox Details , assign your own created business process to the organizational area Sales , save and open the next check. Steps through all open checks and fill out the required data as good as you can.
3OHDVH QRWLFH WKDW \RX ZRXOG UHTXLUH H[SHUW NQRZOHGJH LQ WKH 006' PRGXOH WR EH DEOH WR ILOO RXW HYHU\WKLQJ FRUUHFWO\ 7KLV RSWLRQDO H[HUFLVH VKRXOG MXVW KHOS \RX WR XQGHUVWDQG ZKDW QHHGV WR EH GRQH WR FRPSOHWHO\ GHILQH WKH EXVLQHVV SURFHVV
SAP AG
SM100
3-48
6ROXWLRQV
&KDSWHU 6ROXWLRQ /DQGVFDSHV
At the conclusion of this exercise, you will be able to: Create a solution landscape in the SAP Solution Manager Create a Business Process in the SAP Solution Manager Creating a solution landscape and a Business Process are the essential parts for using the Operations Part of the SAP Solution Manager.
In order to be able to setup a new solution, you have to define all required components first. 1-1 1-2 Call transaction 606< and right-click on 6HUYHU to create a new server GXPP\B[[ . Define freely the technical data. Save your settings.
1-3
Right-click on 6\VWHPV and choose create QHZ V\VWHP ZLWK DVVLVWDQW . Use the same SID as you have used for the database. Enter 'XPP\ 6\VWHP IRU *URXS [[ in the description field; choose 6$3 (&& as SAP Product with product version 6$3 (&& . Continue. On the next screen choose 5HOHYDQW next to the SAP ECC Server entry. Continue to the next screen. Choose system number , the GXPP\B[[ server as message server and [[ as installation number. Continue. Select $VVLJQ /RJLFDO &RPSRQHQWV , specify FOLHQW and continue. Choose &RPSOHWH to save your entries. Now we come to the next assistant who helps us to create and /or assign logical components to our newly created system.
Right-click on 'DWDEDVHV and define a new database called '[[, where xx stands for your group number. Define freely the technical data. Assign the previously defined server to this database. Save your settings.
1-4
Type in the field /RJLFDO &RPSRQHQW the new component =B0\&RPSRQHQWB[[ with the role 3URGXFWLYH 6\VWHP and the FOLHQW . Choose continue and complete to save your settings. Confirm the next screen with Yes to create this new logical component.
SAP AG
SM100
3-49
Create a solution landscape in the SAP Solution Manager called SM100-xx and include the logical components for training systems TT4 (SAP Solution Manager), TT5 (SAP R/3), CRP (CRM Server) and WMS (WMS) into the Solution Landscape. 2-1
Call Transaction '6:3 and choose 6ROXWLRQ 2YHUYLHZ . Click on QHZ to create a new solution. Enter the Solution name 60[[ with. Choose continue. On the following screen choose the link for 6ROXWLRQ /DQGVFDSH 0DLQWHQDQFH . Choose the tab 6\VWHP *URXS to assign the systems which you want to assign to this solution landscape. Select the following logical components: 6$3 (&& 6$3 (&& 6HUYHU =B0<&20321(17B[[ 6$3 &50 &50 6HUYHU &50 6(59(5 &53
2-2
6$3 6ROXWLRQ 0DQDJHU 6$3 6ROXWLRQ 0DQDJHU 6$3 6ROXWLRQ 0DQDJHU ZLWK 77 :06 =:06B:06
6$3 (&& 6$3 (&& 6HUYHU 6$3 (&& ZLWK 77
Save your system selection
Now choose the tab 6ROXWLRQ 6HWWLQJV . Change the monitoring refresh period to 10 minutes. Click on 6HWXS (:$. Deselect the checkboxes 6HQG WR 6$3 for all systems and confirm to activate the EWA processing for the selected systems. Use the &RQWDFWV button and insert your assigned SAP user name as contact person for this solution landscape. Save your settings.
In this exercise you create an own business scenario with two business processes. 3-1 Expand the Solution Directory Structure of your landscape and click on Business Scenarios. Change to the tab 6WUXFWXUH and enter the name of a new Business Scenario 0\ %XVLQHVV 6FHQDULR [[ with the status 3URGXFWLRQ . Save your settings. Expand on the left side your newly created Business scenario and click on %XVLQHVV 3URFHVVHV . On the tab 6WUXFWXUH choose the source %XVLQHVV 3URFHVV 5HSRVLWRU\ . Then use the F4 help within the field 3URFHVV 1DPH to choose the process. Navigate into the RUJDQL]DWLRQDO DUHD 6DOHV &XVWRPHU 2UGHU and select the checkbox 6$3 5 &. Confirm your selection, change the status to 3URGXFWLRQ and save. Expand on the left side the Business Processes and click on your newly created Business Process &XVWRPHU 2UGHU . Change the logical component for all business process steps to 6$3 (&& and save your changes. On the *UDSKLF tab you can see the newly created business process Back on the left hand Solution Structure click again on Business Processes and choose the 6WUXFWXUH tab on the work area at the right hand side. Enter into the next free line of the field SURFHVV QDPH the new name 0\ /LWWOH 3URFHVV [[ with the status 3URGXFWLRQ and save. In the navigation tree on the left click on the newly created process. Switch to the 6WUXFWXUH tab and enter the following step names and logical components:
3-2
3-3
SAP AG
SM100
3-50
6WHS 1DPH Create sales order Create sales order Create delivery Perform picking Send pick confirmation Post goods issue Create invoice
/RJLFDO &RPSRQHQW CRM SERVER SAP ECC SAP ECC ZWMS_WMS ZWMS_WMS SAP ECC SAP ECC
Save your settings and switch to the *UDSKLF tab. Do a right mouse click on the first step and choose &UHDWH /LQH 6\QFKURQRXVO\ . Drag the yellow dot to the following step to create an interface between these two steps. Proceed with all other steps the same way. Than save your settings. 2SWLRQDO ([HUFLVH 4-1 Within the Solution Directory, where you have just created your business processes, click on the button %XVLQHVV 3URFHVV 'HWDLOV to access the Business Process maintenance. In the first screen choose the checkbox 'HWDLOV , assign your own created business process to the RUJDQL]DWLRQDO DUHD 6DOHV , save and open the next check. Steps through all open checks and fill out the required data as good as you can.
3OHDVH QRWLFH WKDW \RX ZRXOG UHTXLUH H[SHUW NQRZOHGJH LQ WKH 006' PRGXOH WR EH DEOH WR ILOO RXW HYHU\WKLQJ FRUUHFWO\ 7KLV RSWLRQDO H[HUFLVH VKRXOG MXVW KHOS \RX WR XQGHUVWDQG ZKDW QHHGV WR EH GRQH WR FRPSOHWHO\ GHILQH WKH EXVLQHVV SURFHVV
SAP AG
SM100
3-51
SAP AG
SM100
3-52
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
4-1

6HUYLFH 'HVN 2YHUYLHZ DQG 3URFHVV &50 0DVWHU 'DWD $SSHQGL[ $GYDQFHG 6HUYLFH 'HVN
SAP AG
SM100
4-2
/HVVRQ 2EMHFWLYHV
'HVFULEH WKH 6HUYLFH 'HVN 3URFHVV
$IWHU FRPSOHWLQJ WKLV OHVVRQ \RX ZLOO EH DEOH WR
'HVFULEH WKH GLIIHUHQW HOHPHQWV RI WKH 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN
SAP AG 2006
SAP AG
SM100
4-3
6$3 6ROXWLRQ 0DQDJHU 6FHQDULRV 6HUYLFH 'HVN
SAP AG 2006
SAP AG
SM100
Onsite/remote delivery Issue Management
'HOLYHU\ RI 6$3 6HUYLFHV
&KDQJH 5HTXHVW 0DQDJHPHQW
5RRW &DXVH $QDO\VLV
Performance measurement Log files and dumps Traces Technical configuration management
SAP methods & tools E-learning mgmt. Test management
%86,1(66 352&(66(6
&25(
SAP methods & tools Global rollout Customizing sync. E-learning mgmt. Test management
6ROXWLRQ 0RQLWRULQJ
System monitoring Business process monitoring Central system administration Solution reporting Service Level reporting SAP EarlyWatch Alert
6HUYLFH 'HVN
Best Practices for messaging Integration of 3rdparty help desks
4-4
%HQHILWV RI WKH 6HUYLFH 'HVN

6HUYLFH 'HVN 2SHUDWLRQ
1RWLILFDWLRQ H[FKDQJH ZLWK 6$3
(VFDODWLRQ SURFHGXUHV DQG 6HUYLFH /HYHO 5HSRUWLQJ
3UREOHP UHVROXWLRQ ZLWK 6$3 1RWHV DQG 6ROXWLRQ 'DWD %DVH
$GYDQFHG GLVSDWFKLQJ DQG SURFHVVLQJ ZRUNIORZV
0RQLWRULQJ RI 6HUYLFH 'HVN QRWLILFDWLRQV
.QRZOHGJH 0DQDJHPHQW
&XVWRPHU VROXWLRQ GDWDEDVH
7UDQVLWLRQ WR FRPSOHWH 6HUYLFH 0DQDJHPHQW ZLWK P\6$3 &50 SRVVLEOH

&DOO FHQWHU LQWHJUDWLRQ *HQHUDO ,7 KHOSGHVN
6HUYLFH FRQWUDFWV FDSDFLW\ SODQQLQJ DQG ELOOLQJ

SAP AG 2006
SAP AG
SM100
4-5
8QLW 2EMHFWLYHV
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR 'HVFULEH KRZ WR FUHDWH D VXSSRUW GHVN PHVVDJH
'HVFULEH WKH SURFHVV RI VROYLQJ D VXSSRUW GHVN PHVVDJH
SAP AG 2006
SAP AG
SM100
4-6
tuxx %t ~ } |s z s u s t q&t33q|
RU
5 ` Y Yye n h yy 2Y
v ~| q| eq`w
qpjRU% i 3n lm j t f i o
v ~ | xt |s q| `6qAn% &z
(QG 8VHU
7KH 6XSSRUW 3URFHVV
6ROXWLRQ 6XSSRUW
v ~| q| `qeq s s ut qk|&hn
tuxx hht ~ } |s z x v uts net%&{yktwn3r
v ~ | xt |s q | q`wA%ey&z
YY Y2 6 5%
v ~ | x t |s w | q`wAqe&z
l i %kje f % e hg eR6 d
SAP AG
SAP AG 2006
In case the Solution Support cant find a solution the message can be forwarded to SAP.
&XVWRPHU
SM100
6$3 $FWLYH *OREDO 6XSSRUW
6$3 6HUYLFH 0DUNHWSODFH
6$3
4-7
6HUYLFH 'HVN 3URFHVV
&RQWHQW &UHDWLQJ D VXSSRUW GHVN PHVVDJH
6ROYLQJ D VXSSRUW GHVN PHVVDJH
SAP AG 2006
SAP AG
SM100
4-8
([FXUVXV :D\V WR &UHDWH D 6HUYLFH 'HVN 0HVVDJH
VHUYLFH GHVN PHVVDJH
7KLV H[FXUVXV H[SODLQV WKH GLIIHUHQW ZD\V WR FUHDWH D
+HOS FUHDWH VXSSRUW PHVVDJH IURP VDWHOOLWH V\VWHP
7UDQVDFWLRQ QRWLIBFUHDWH ,&66 ,& :HE&OLHQW DQG %63
SAP AG 2006
SAP AG
SM100
4-9
YY Y2 6 5%
5 ` Y Yye n h yy 2Y
p j j t f i qRU% i 3n lm o
(QG 8VHU
SAP AG
SAP AG 2006
End users inform the relevant support unit working in SAP Solution Manager.
7KH 6XSSRUW 3URFHVV
&XVWRPHU
6ROXWLRQ 6XSSRUW
SM100
4-10
&UHDWH 0HVVDJH
(DV\ FUHDWLRQ RI PHVVDJHV E\ HQG XVHUV IURP UHJXODU ZRUN DUHD -> Help -> Create Support Message Short text / long text / priority File attachments $XWRPDWLF FROOHFWLRQ RI PRVW LPSRUWDQW V\VWHP GDWD Transaction code / program ID Database version Support Package level (DV\ FUHDWLRQ RI PHVVDJHV ZLWK %63 DSSOLFDWLRQ &UHDWLRQ RI PHVVDJHV YLD DGGLWLRQDO LQSXW FKDQQHOV Key users can use SAP Solution Manager directly for message creation Call-center, e-mail, Internet Customer Self Service, etc.
SAP AG 2006
8VHU &UHDWH 0HVVDJH
6XSSRUW
6$3 6XSSRUW
SAP AG
SM100
4-11
SAP AG 2006
SAP AG
SM100
4-12
v ~| q| eq`w
(QG 8VHU
7KH 6XSSRUW 3URFHVV
6ROXWLRQ 6XSSRUW
RU
5 ` Y Yye n h yy 2Y
v ~ | xt |s q| `6qAn% &z
SAP AG
SAP AG 2006
Now the Solution Support takes care of your message.
&XVWRPHU
SM100
6$3
4-13
tuxx %t ~ } |s z s u s t q&t33q|
RU
5 ` Y Yye n h yy 2Y
v ~| q| eq`w
v ~ | xt |s q| `6qAn% &z
(QG 8VHU
7KH 6XSSRUW 3URFHVV
6ROXWLRQ 6XSSRUW
v ~ | xt |s q | q`wA%ey&z
YY Y2 6 5%
v ~ | x t |s w | q`wAqe&z
SAP AG
SAP AG 2006
&XVWRPHU
SM100
6$3
4-14
$QDO\]H 0HVVDJH
$XWRPDWLF DVVLJQPHQW RI VXSSRUW RUJDQL]DWLRQ Several support levels possible Identify existing service contract $VVLJQPHQW RI VXSSRUW HPSOR\HHV IRU SURFHVVLQJ Automated message assignment according to freely definable criteria Message assignment to processors work list Forwarding message to another processing group / processor Automatic notification of processor
8VHU &UHDWH 0HVVDJH
6XSSRUW $QDO\]H 0HVVDJH
6$3 6XSSRUW
SAP AG 2006
SAP AG
SM100
4-15
5HTXHVW ,QIRUPDWLRQ
)XUWKHU LQIRUPDWLRQ FDQ EH UHTXHVWHG IURP XVHU LI FROOHFWHG V\VWHP GDWD LV QRW VXIILFLHQW IRU SUREOHP UHVROXWLRQ E-mail, telephone 8VHU SURYLGHV DGGLWLRQDO LQIRUPDWLRQ Telephone SAP Solution Manager Internet Customer Self Service (CRM ICSS)
8VHU &UHDWH 0HVVDJH 5HTXHVW ,QIRUPDWLRQ
6XSSRUW $QDO\]H 0HVVDJH
6$3 6XSSRUW
SAP AG 2006
SAP AG
SM100
4-16
6HDUFK IRU 6ROXWLRQ

.QRZ KRZ RI LQWHUQDO VXSSRUW HPSOR\HHV ,QWHJUDWHG &XVWRPHU 6ROXWLRQ 'DWDEDVH Search for symptoms and solutions Fast solution of recurring problems Automatic documentation of problem solution Build up your own Q&A database 6$3 6HUYLFH 0DUNHWSODFH Trigger SAP Notes search directly in SAP Service Marketplace 8VHU &UHDWH 0HVVDJH 5HTXHVW ,QIRUPDWLRQ 6XSSRUW $QDO\]H 0HVVDJH 6HDUFK 6ROXWLRQ
6$3 6XSSRUW
SAP AG 2006
SAP AG
SM100
4-17
3URYLGH /RJRQ 'DWD

6HQG D PHVVDJH WR 6$3 Forward messages to SAP Support back office if your support organization cannot solve the problem Bi-directional interface for forwarding messages and receiving solutions No need to log on to SAPNet R/3 Frontend 3URYLGH ORJRQ GDWD maintain logon data in secure area
6XSSRUW $QDO\]H 0HVVDJH 6HDUFK 6ROXWLRQ +DQG RYHU WR 6$3 3URYLGH ORJRQ GDWD
6$3 6XSSRUW
5HTXHVW ORJRQ GDWD
SAP AG 2006
SAP AG
SM100
4-18
6ROXWLRQ 3URYLGHG E\ 6$3

5HFHLYH DQ DQVZHU IURP 6$3 Message processing by SAP Active Global Support Remote support integration
Application sharing between end-users, support employees and SAP Support back office experts Automatic transfer of changes to the message status Solution provided via SAP Notes
6$3 6XSSRUW
5HTXHVW ORJRQ GDWD 3URYLGH 6ROXWLRQ
SAP AG 2006
SAP AG
SM100
4-19
$SSO\ 6ROXWLRQ
1RWH LPSOHPHQWDWLRQ Automatic implementation of SAP Notes with SAP Notes Assistant 9HULI\ VROXWLRQ Testing Evaluation of responsible employee 6HQG VROXWLRQ WR HQGXVHU Using output functions of service process (print, mail, fax) or ICSS 7UDQVSRUW FKDQJHV WR WKH SURGXFWLYH HQYLURQPHQW Software change management (QWHU VROXWLRQ LQ VROXWLRQ GDWDEDVH
6XSSRUW $QDO\]H 0HVVDJH 6HDUFK 6ROXWLRQ +DQG RYHU WR 6$3 3URYLGH ORJRQ GDWD $SSO\ 6ROXWLRQ
6$3 6XSSRUW
SAP AG 2006
SAP AG
SM100
4-20
&ORVH DQG &RQILUP 0HVVDJH

&ORVH DQG FRQILUP PHVVDJH End-user tests solution The problem message is confirmed by the end-user
6$3 6XSSRUW
&ORVH 0HVVDJH
SAP AG 2006
$SSO\ 6ROXWLRQ
SAP AG
SM100
4-21
8QLW 6XPPDU\
'HVFULEH WKH SURFHVV RI VROYLQJ D VXSSRUW GHVN PHVVDJH
'HVFULEH KRZ WR FUHDWH D VXSSRUW GHVN PHVVDJH
$IWHU FRPSOHWLQJ WKLV XQLW \RX DUH QRZ DEOH WR
SAP AG 2006
SAP AG
SM100
4-22

SAP AG
SM100
4-23
8QLW 2EMHFWLYHV
'HVFULEH WKH UHOHYDQW &50 PDVWHU GDWD %XVLQHVV SDUWQHU ,%DVH 2UJDQL]DWLRQDO 'DWD
SAP AG 2006
SAP AG
SM100
4-24
2YHUYLHZ RI WKH UHOHYDQW &50 PDVWHU GDWD
,%DVH
2UJDQL]DWLRQDO 'DWD
%XVLQHVV 3DUWQHU
SAP AG 2006
SAP AG
SM100
4-25
P\6$3 &50 %XVLQHVV 3DUWQHU

%XVLQHVV 3DUWQHU 5HODWLRQVKLSV
SAP AG 2006
Business partners are at the center of business transactions, and thus, the center of business interest. All relevant information about a business partner must therefore be available quickly in a consolidated form. The customer therefore needs to have a central and comprehensive view of the business partner. A business partner can only be created once, regardless of the business transactions in which it participates. For example, if a company is both a customer and a vendor, the company is still one and the same business partner. However, a business partner can figure in a company in other ways. Depending on the specific business processes in which a business partner participates, the information required about the business partner may vary considerably. For example, for the goods delivery process, information on Incoterms and delivery conditions is required; whereas, for the sales order processing, information on delivery dates and payment conditions is necessary. A business partner can be in contact with other business partners. These relationships can be very different in nature (for example, a marriage, contact person, company relationships). The 6$3 %XVLQHVV 3DUWQHU provides functions that fulfill these business processes. A business partner is created only once in the system, but can take on several different roles. The different relationships between business partners can also be defined.
SAP AG
%U % %A
%t
CI2R
Y% %
1HXWUDO 3HUVRQV DQG RUJDQL]DWLRQV &URVVDSSOLFDWLRQ 2SHQ LQIUDVWUXFWXUH ,QWHJUDWLRQ WKURXJK RSHUDWLRQDO FRQFHSWV
(PSOR\HH
&UHGLWRU
%XVLQHVV 3DUWQHU
9HQGRU
0DQX IDFWXULQJ 3ODQW
SM100
4-26
3DUWQHU )XQFWLRQV IRU WKH 6HUYLFH 'HVN 0HVVDJH

In case of maintenance: who is the DGPLQLVWUDWRU of the system ? Which NH\ XVHU was reporting the problem?
Which FXVWRPHU is going to pay for the support service ?
Which employee of the support team is assigned as PHVVDJH SURFHVVRU?

SAP AG 2006
Which VXSSRUW WHDP is responsible for message processing?
For the support desk message, five partner functions are predefined (can be changed in the customizing and &50 %DVLF )XQFWLRQV 3DUWQHU 3URFHVVLQJ see Partner determination procedure 6/)1): 6ROG7R3DUW\ Stores the business partner customer. :KLFK FXVWRPHU LV JRLQJ WR SD\ IRU WKH VXSSRUW VHUYLFH" The partner function sold-to-party is obligatory and may not be deleted.
6/)1 6\VWHP $GPLQLVWUDWRU Stores the business partner ID of the system administrator ,Q FDVH RI PDLQWHQDQFH :KR LV WKH DGPLQLVWUDWRU RI WKH V\VWHP" 6/)1 .H\ 8VHU Stores the business partner ID of the key user (Which key user was reporting the problem?) 6/)1 6XSSRUW 7HDP Stores the business partner ID of the responsible org.unit :KLFK VXSSRUW WHDP LV UHVSRQVLEOH IRU PHVVDJH SURFHVVLQJ" 6/)1 0HVVDJH 3URFHVVRU Stores the business partner ID of the assigned employee :KLFK HPSOR\HH RI WKH VXSSRUW WHDP LV DVVLJQHG DV PHVVDJH SURFHVVRU"
SAP AG
SM100
4-27
0DLQWDLQ %XVLQHVV 3DUWQHU IRU WKH .H\ 8VHU
SAP AG 2006
The business partner for the KEY USER can be maintained in transaction BP. Choose the role General and maintain the Address (Address tab strip).
SAP AG
SM100
4-28
,%DVH
2UJDQL]DWLRQDO 'DWD
%XVLQHVV 3DUWQHU
SAP AG 2006
SAP AG
SM100
4-29
2UJDQL]DWLRQ 3RVVLELOLWLHV &50

$ SDUW RI DQ LQWHUQDWLRQDO RUJDQL]DWLRQ
SAP AG 2006
Organizational units for mySAP CRM Service have to be permitted for the 6HUYLFH scenario.
The 6HUYLFH 2UJDQL]DWLRQ indicator marks the selected organizational unit as a service organization. Organizational units that are responsible for executing services and that should be displayed in the resource planning tool have to be flagged as 6HUYLFH 7HDP.
You can assign a UHVRXUFH SODQQHU position to a service team using Goto 5HVRXUFH 3ODQQHU $VVLJQPHQW The system users or business partners assigned to this position are the resource planners who use the resource planning tool. The organizational unit appears under 0\ 6HUYLFH 7HDPV when the resource planner starts the resource planning tool.
SAP AG
SM100
R6 U6FR
RnF
{RU
R65 6en{
2FFF FU5 $$U5$ 22 22

4-30
U6RYU2F26 $22 22 22 22 Ik2R6Y tUU `FyeX F R`F5 d3{dkn $R6s R6F2U UAFU
%UHDNLQJ 'RZQ DQ 2UJDQL]DWLRQDO 8QLW

3RVLWLRQV DQG KROGHUV DVVLJQHG WR DQ RUJDQL]DWLRQDO XQLW
3RVLWLRQ
SAP AG 2006
2UJDQL]DWLRQDO 8QLW An Organizational Unit is an organizational object (object type key O) that is used to form the basis of an organizational plan. Organizational units are functional units of an enterprise. Depending on how task distribution is organized in an enterprise, organizational units can be, for example, departments, groups, or project teams. 3RVLWLRQ Position is an organizational object (object type key S) that shows the functional task distribution of individual items and their reporting structure in the organizational plan. In CRM, positions could be, for example, sales manager, sales representative, Interaction Center manager or Interaction Center agent. Holders (employees or CRM users) can be assigned to one or more positions. (PSOR\HH 8VHU Employees and users are persons assigned to a position. A person can be a CRM business partner with the role (PSOR\HH (object type key BP) or only a &50 8VHU (object type key US) that is assigned to a position in an organizational plan. By assigning an employee or a user to a position, you can show where an employee is assigned organizationally in a company (what his/her function is). Assigning an employee is recommended because an employee master contains more business data than a user. Transaction PPOMA_CRM
SAP AG
SM100
6kC
8VHU
C`6à%
(PSOR\HH
%t`C
3RVLWLRQ
{RU
4-31
*URXS %
R6 U6FR
$knY kXn %C&C 22
([DPSOH RI D 6LPSOH 2UJDQL]DWLRQDO 6WUXFWXUH
SAP AG 2006
Set up your whole organization structure within transaction PPOMA_CRM Create Organizational Units with incorporates and assign Business Partners to them
SAP AG
SM100
4-32
,%DVH
2UJDQL]DWLRQDO 'DWD
%XVLQHVV 3DUWQHU
SAP AG 2006
SAP AG
SM100
4-33
6ROXWLRQ /DQGVFDSH
6$3 6ROXWLRQ 0DQDJHU In what system did the problem originate? &50 $32
5
SAP AG 2006 2003
The SAP Solution Manager uses the IBase as an internal knowledge base for the Service Desk functionality. Systems are referenced as so called components with a support message
SAP AG
SM100
4-34
,QVWDOOHG %DVH 0DQDJHPHQW )HDWXUHV

*UDSKLFDO UHSUHVHQWDWLRQ RI SURGXFWV DQG LQVWDOODWLRQV
6FHQDULRV

5HSUHVHQWDWLRQ RI KLHUDUFKLFDO FRPSRQHQW VWUXFWXUH RU VHWXS RI GHYLFHV PDFKLQHU\ SURGXFWV DQG VR RQ GHOLYHUHG WR FXVWRPHU
2QH LQVWDOOHG EDVH SHU FXVWRPHU DOO FXVWRPHUV REMHFWV LQ RQH LQVWDOOHG EDVH
8VHG DV D UHIHUHQFH LQ VHUYLFH SURFHVVLQJ
2QH LQVWDOOHG EDVH SHU LWHP PDQ\ LQVWDOOHG EDVHV SHU FXVWRPHU
SAP AG 2006
Benefits of Installed Base Management for your customers: Your customers can reduce call times with immediate access to customer installation information during case logging. Your customers can directly reference multiple contracts, addresses, partners, and configurations.
Benefits of Installed Base Management for your company: Your company can give field service representatives the information necessary to anticipate requirements prior to arriving on site. Your company can facilitate product improvements and quality management by tracking services performed on products and installations.
SAP AG
SM100
4-35
,QVWDOOHG %DVH 6WUXFWXUH

+HDGHU
3DUWQHUV $GGUHVV 'RFXPHQWV 3DUWQHUV $GGUHVV 'RFXPHQWV &RPSRQHQWV
&DWHJRU\ ([WHUQDO ,' 'HVFULSWLRQ 6WDWXV V\VWHPXVHU $XWKRUL]DWLRQ *URXS
&RPSRQHQWV
3URGXFW 7H[W LWHP ,QVWDOOHG EDVH ,QGLYLGXDO REMHFW &XVWRPHUVSHFLILF W\SHV
SAP AG 2006
The number of installed base levels is unlimited. Partner, address, and other data are not transferred or inherited within the hierarchy (top-down). In the Interaction Center, this has the added advantage that when you search for an installed base using partner or address data, an installed base with all assigned components is displayed and is not just an installed base component. Within the Content Management service, you can assign documents of different types to an installed base or an installed base component. Customer-specific components require additional programming.
SAP AG
SM100
4-36
&KDQJH ,QVWDOOHG %DVH 6$3 6ROXWLRQ /DQGVFDSH
6WUXFWXUH 2YHUYLHZ
6WUXFWXULQJ WKH V\VWHPV WKURXJK DGGLWLRQDO WH[W FRPSRQHQWV
6XERUGLQDWH 6\VWHPV
SAP AG 2006
SAP AG
SM100
4-37
&50 0DVWHU 'DWD 8QLW 6XPPDU\
'HVFULEH WKH UHOHYDQW &50 PDVWHU GDWD 2UJDQL]DWLRQDO 'DWD ,%DVH %XVLQHVV SDUWQHU
<RX DUH QRZ DEOH WR
SAP AG 2006
SAP AG
SM100
4-38
'HPR
([HUFLVH
SAP AG 2006
SAP AG
SM100
4-39
/HVVRQ 6XPPDU\
'HVFULEH WKH GLIIHUHQW HOHPHQWV RI WKH 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN
SAP AG 2006
SAP AG
SM100
4-40

SAP AG
SM100
4-41
6HUYLFH &RQWUDFW
&RQWHQW 6HUYLFH &RQWUDFWV 6HUYLFH /HYHO $JUHHPHQWV
UG 3DUW\ ,QWHUIDFH
,& :HE&OLHQW ,& :HE&OLHQW (QGXVHU
6ROXWLRQ 'DWDEDVH
SAP AG 2006
SAP AG
SM100
4-42
:KDW LV D 6HUYLFH &RQWUDFW"

6HUYLFH &RQWUDFWV
/LVW WKH VHUYLFHV WKDW DUH FRYHUHG E\ WKH FRQWUDFW
6SHFLI\ VHUYLFH OHYHOV D FXVWRPHU LV HQWLWOHG WR
5HSUHVHQW ORQJWHUP VHUYLFH UHODWLRQVKLSV ZLWK FXVWRPHUV
'HWHUPLQHV WKH GHOLYHU\ RI FRQWUDFWEDVHG VHUYLFHV IRU HQVXUHG VHUYLFH KRXUV UHVSRQVH WLPH DQG VR RQ
6HUYLFH OHYHO RI FRQWUDFWHG VHUYLFHV VSHFLILHG RQ FRQWUDFW LWHP OHYHO
$OORZV HVFDODWLRQ SURFHGXUHV WR PRQLWRU FRPSOLDQFH RI VHUYLFH IXOILOOPHQW ZLWK 6/$ &RQWUROV WKH SULFLQJ RI VHUYLFHV DFFRUGLQJ WR FKRVHQ VHUYLFH OHYHO
SAP AG 2006
A VHUYLFH FRQWUDFW is a long-term agreement with business partners that specifies the services offered for that period. The service contract line item lists customer objects installed base, installed base components, and products that are covered by the contract line item. Service level agreements list the level of service a customer is entitled to and contain functions for monitoring compliance with those terms. A contract may include contract-specific price agreements that control not only what is covered by the contract but also what prices may be charged for any work covered by that contract. Benefits of service contracts for your customers: A truly differentiated service to optimize all customer experiences Accurate billing and reporting of services performed and SLAs met, allowing easier negotiations of renewals A flexible means of creating an environment to be covered under an agreement
Benefits of service contracts for your company: Ability to track all contract costs and revenues to maximize profitability Seamless integration with service fulfillment Out-of-the-box service level agreements (SLAs) delivered by SAP and an open, easy-to-enhance solution for additional, customer-specific SLAs
SAP AG
SM100
4-43
$YDLODELOLW\ 7LPH DQG 5HVSRQVH 7LPH ([DPSOH

6HUYLFH SURILOH 5HVSRQVH SURILOH DP SP SP SP KRXUV KRXUV KRXUV DP SP KRXUV KRXUV KRXUV
8am 12pm
0RQGD\
6pm
8am 12pm
7XHVGD\
6pm
time
1RWLILFDWLRQ UHFHLYHG
SAP AG 2006
In this example, the determined response times are displayed for a call received on Monday at 12 p.m. Service profile: 8a.m. - 12p.m. / 1p.m. - 5p.m. Response time - 8 hours: response by Tuesday 12 p.m. Response time - 4 hours: response by Monday 5 p.m. y Response time - 2 hours: response by Monday 3 p.m.
Service profile: 7a.m. - 7 p.m. Response time - 8 hours: response by Tuesday 8 a.m. Response time - 4 hours: response by Monday 4 p.m. Response time - 2 hours: response by Monday 2 p.m.
SAP AG
SM100
4-44
6ROXWLRQ 'DWDEDVH
UG 3DUW\ ,QWHUIDFH
6ROXWLRQ 'DWDEDVH
SAP AG 2006
SAP AG
SM100
4-45
v r q i p ib i 6q s 196(H94g U e %TCV 8 0 TS 7 R
v r q i p ib iw 6q s 696(H94g U r x 4Y(1db GHFE 6DBC1) (' 6@9 A & & $ 8 7 5 6 3 42
v r q i p ib i 6q s 9CCF4g w U r x t%T(yb
v u g ttU s r q i p ib i g e c b `X V 619H9WhfV d9aYWU
P qX12QqI17
0 & & $ $1) (' k% " #A!w

%XVLQHVV 3DUWQHU IURP OEDVH
U w Ce
e cb i n Vm e V y9jI9ac m V q 6Qr h r Ck6jb iCH99I h c l x b V p x c d rb i r q b d9Wf(Yr C6r fCD c g c b e e r d X V e X ec q
SAP AG
SAP AG 2006
6RIWZDUH $JHQW )UDPHZRUN 2YHUYLHZ
6RIWZDUH $JHQW )UDPHZRUN
6$3 6HUYLFH 3URFHVVHV
&RPSLOH
SM100
3ODQW ,QIR IURP (TXLSPHQW
4-46
6ROXWLRQ 'DWDEDVH
&RUSRUDWH UHSRVLWRU\ RI HQWHUSULVH NQRZOHGJH

3UREOHP -$ 2EMHFW '( 3UREOHP )5 6ROXWLRQ (6 6ROXWLRQ $WWDFKPHQWV 2EMHFW (1 &DWHJRUL]DWLRQ RI LQIRUPDWLRQ
,QGH[HG GDWDEVH IRU TXLFN UHWULHYDO 6HFXULW\ SURILOHV
SAP AG 2006
SAP AG
SM100
4-47
,&:HE&OLHQW
UG 3DUW\ ,QWHUIDFH
6ROXWLRQ 'DWDEDVH
SAP AG 2006
SAP AG
SM100
4-48
,QWHUDFWLRQ &HQWHU :HE &OLHQW

7KH ,QWHUDFWLRQ &HQWHU :HE &OLHQW LV XVHG DV D ZHEEDVHG 8, IRU WKH 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN ,W LV RIIHUHG DV DQ DOWHUQDWLYH 8, IRU WKH 6HUYLFH 'HVN PHVVDJH 6/)1 DV RI 6$3 6ROXWLRQ 0DQDJHU 5HOHDVH 63 7KH *8, WUDQVDFWLRQV ZLOO VWLOO EH DYDLODEOH IRU PHVVDJH FUHDWLRQ DQG SURFHVVLQJ ZHEEDVHG FUHDWLRQ RI 6HUYLFH 'HVN PHVVDJHV DOUHDG\ SRVVLEOH LQ 6$3 6ROXWLRQ 0DQDJHU ZLWK WUDQVDFWLRQ 127,)B&5($7(B%63 3UHFRQILJXUDWLRQ IRU WKH 6HUYLFH 'HVN PHVVDJH LV SURYLGHG LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
SAP AG
SM100
4-49
UG 3DUW\ ,QWHUIDFH
UG 3DUW\ ,QWHUIDFH
6ROXWLRQ 'DWDEDVH
SAP AG 2006
SAP AG
SM100
4-50
3DUWQHU ,QWHUIDFH WR 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN 6$3 6ROXWLRQ 0DQDJHU RIIHUV D ELGLUHFWLRQDO LQWHUIDFH WKDW HQDEOHV WKH H[FKDQJH RI PHVVDJHV EHWZHHQ 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN DQG WKLUG SDUW\ KHOS GHVN WRROV 6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN FDQ EH LQWHJUDWHG LQWR H[LVWLQJ KHOS GHVN DSSOLFDWLRQV 7KH LQWHUIDFH LV RSHQ DQG DQ\ SDUWQHU FDQ VXEVFULEH WR LW WKHUH LV QR SUHIHUUHG SDUWQHU WRRO ,W LV EDVHG XSRQ ZHE VHUYLFHV VLPSOH IOH[LEOH DQG SODWIRUP LQGHSHQGHQW DQG LV RIILFLDOO\ FHUWLILHG E\ 6$3
SAP AG 2006
SAP AG
SM100
4-51
,QWHJUDWH UG3DUW\ +HOS 'HVNV

%LGLUHFWLRQDO LQWHUIDFH IRU H[FKDQJH RI SUREOHP PHVVDJHV
2SHQ LQWHUIDFH LQGHSHQGHQW RI H[LVWLQJ UGSDUW\ KHOS GHVN DSSOLFDWLRQV %DVHG RQ :HE VHUYLFHV
o
SAP AG 2006
6$3 6XSSRUW 5)&
6$3 $SSOLFDWLRQ
Forwarding a massage into another help desk creates a corresponding message there. Each message has a uniquely identifiable connection to the message in the other help desk Only one of the messages can be processed at a time, i.e. one message takes the lead. Additional information (message texts) can be sent and received asynchronously Processing messages means that a message can be sent to and fro multiple times Closing a message triggers closing the corresponding message in the other help desk automatically. Other than that, there is no automatic synchronisation of message data between help desks As a matter of fact there is currently no standard for message exchange available that could be used
SAP AG
SM100
z }| {{z ~dkdyCy
qts
uvwqx
62$3+773
uvwqx
pqr
pqr
qts
z } |{{z ddd6y
z }| {{z dkyyCy
o o
6$3
$OLJQHG ZLWK H[LVWLQJ VWDQGDUGV IRU PHVVDJH H[FKDQJH HJ 62$3
&XVWRPHU
6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN
H[WHUQHU +HOS'HVN
5)&
4-52

SAP AG
SM100
4-53
SAP AG 2006
SAP AG
SM100
4-54
9~ F1RIYI
a
(QG 8VHU
7KH 6XSSRUW 3URFHVV
6ROXWLRQ 6XSSRUW
a6 !
F~ 9I1
RU
F ad| dy { z { z { y Dd kz z z{| | { d| dfyz ~
FF4R I 6 W9
a9 ~1
a6~91
z{| | { yy~k| yfz ~ { kY d{ 9 z
a6~11
9 F #9#F 4
SAP AG
SAP AG 2006
&XVWRPHU
SM100
6$3
4-55
+RZ WR &UHDWH D 6XSSRUW 0HVVDJH
SAP AG 2006
If there is a problem in the system, stay in the transaction or the window where the problem emerged. Go to the menu and choose +HOS &UHDWH 6XSSRUW 0HVVDJH An authorization check for users can be implemented with note 621927. File attachments can be added to the support desk message and later forwarded to SAP support. The SAP Solution Manager automatically collects the relevant data from the connected satellite system. Selected files and long texts can be changed with a BADI implementation. Please use the BADI SBCOS001 (SE18/SE19) with the interface method PREPARE_FEEDBACK_BO. There are the following other influencing parameters: R/3 components (changeable) Short text of the message (changeable) Message priority (changeable) PBO_TEXT(message long text as template for the user for creating a message) PAI_TEXT (additional HQKDQFHG text after creating the message).
Using note 630978, there is also an additional check for texts (for example, display long text) possible.
SAP AG
SM100
4-56
$WWDFKPHQW RI 'RFXPHQWV
SAP AG 2006
You can attach any document type to the support desk message.
SAP AG
SM100
4-57
6\VWHP (QYLURQPHQW
SAP AG 2006
When the message is created using +HOS &UHDWH 6XSSRUW 0HVVDJH, the system environment is automatically attached.
SAP AG
SM100
4-58
+RZ WR &UHDWH D 6XSSRUW 0HVVDJH
SAP AG 2006
Press the Send button to finish You will get the number of your Support Message that you have just created
SAP AG
SM100
4-59
2YHUYLHZ RI WKH 5HOHYDQW &50 0DVWHU 'DWD
SAP AG 2006
SAP AG
SM100
4-60
2SHQ WKH 6HUYLFH 0HVVDJH

'LIIHUHQW ZD\V WR VHOHFW RSHQ D VHUYLFH GHVN PHVVDJH '6:3 &50B'12B021,725
SAP AG 2006
Different ways to open a new message Solution Manager Transaction: DSWP Service Desk Transcaction Monitor -> CRM_DNO_MONITOR Global selection Using user specific variants
SAP AG
SM100
4-61
6$3 6ROXWLRQ 0DQDJHU 6XSSRUW 'HVN 0HVVDJH
SAP AG 2006
Transaction DSWP (Solution Manager) 6HUYLFH 'HVN 2SHUDWLRQV Service Desk Variant: Open Messages
SAP AG
SM100
4-62
7UDQVDFWLRQ 0RQLWRU
7UDQVDFWLRQ 0RQLWRU
SAP AG 2006
You can start the Transaction Monitor in the SAP menu using Service Transaction Monitor. Or with transaction: CRM_DNO_MONITOR
SAP AG
SM100
4-63
7UDQVDFWLRQ 0RQLWRU
SAP AG 2006
Here you can set some special settings. Select Get Variant and choose the according variant. The transaction monitor can be used to monitor SLA times. Also, layout variants can be individually customized.
SAP AG
SM100
4-64
6$3 6ROXWLRQ 0DQDJHU 6HUYLFH 'HVN 0HVVDJH
/RFDWRU
6HUYLFH 'HVN 0HVVDJH )DVW (QWU\ 6FUHHQ
SAP AG 2006
The /RFDWRU contains different functions that allow to search for transaction types, tasks or dates The Locator can be switched off in order to enlarge the screen for the message handling
SAP AG
SM100
4-65
)DVW (QWU\ 7UDQVDFWLRQ 'DWD
SAP AG 2006
Two different areas: Fast Entry and Transaction Data (contains more information)
SAP AG
SM100
4-66
0HVVDJH 3URFHVVRU
SAP AG 2006
These screenshots shows how you can choose a possible message processor using the F4 help. Choose the F4 help to search for possible message processors. Confirm the search using Enter. Alternative: Just enter the message processors last name or the business partner number
SAP AG
SM100
4-67
7UDQVDFWLRQ 'DWD 6$3 1RWHV
SAP AG 2006
The Transaction Data screen offers different tabs that provide individual functionality Go to the 6$3 1RWHV tab page and press the Search button
SAP AG
SM100
4-68
6$3 6HUYLFH 0DUNHWSODFH 6$3 1RWHV 6HDUFK
SAP AG 2006
You can search for relevant notes in the SAP Marketplace.
SAP AG
SM100
4-69
6$3 6HUYLFH 0DUNHWSODFH 6$3 1RWHV
SAP AG 2006
If you found a note concerning your problem you can attach the information directly to the message
SAP AG
SM100
4-70
'RZQORDG 6$3 1RWH WR 6HUYLFH 0HVVDJH

'RZQORDG 1RWH LQIRUPDWLRQ WR 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
Select the note you would like to attach to the Service Message and press the Transfer Data button. The note number and the description will be copied to the message.
SAP AG
SM100
4-71
,PSOHPHQW D 1RWH XVLQJ WKH 1RWH $VVLVWDQW
SAP AG 2006
If you want to automatically implement the selected note through the SAP Note Assistant (for example, in your development system to test the correction), you can choose 1RWH $VVLVWDQW
SAP AG
SM100
4-72
6ROXWLRQ 'DWDEDVH
SAP AG 2006
Maybe you find a solution in the internal solution database of the SAP Solution Manager. Move to the 6ROXWLRQ 'DWDEDVH tab page. Select 6HDUFK
SAP AG
SM100
4-73
6HDUFK ,QVLGH WKH 6ROXWLRQ 'DWDEDVH
SAP AG 2006
Define your search criteria (a short text of the support desk message is automatically copied) and choose (QWHU.
SAP AG
SM100
4-74
68VHU 0DLQWHQDQFH ,0*

7$ 6352 ,0* o 6$3 6ROXWLRQ 0DQDJHU o %DVLF 6HWWLQJV o 6$3 6ROXWLRQ 0DQDJHU 6\VWHP o $XWKRUL]DWLRQV8VHUV
SAP AG 2006
$VVLJQ 6XVHU IRU 6$3 6XSSRUW 3RUWDO IXQFWLRQDOLW\ For several use cases like e.g. sending Service Desk messages to SAP and for opening service connections it is necessary to assign a SAP Support Portal contact to solution manager users who will communicate with SAP Support Portal via Service Desk RFC-Destination. The contact you maintain corresponds to the S-user in SAP Support Portal without S. An S-User is a user ID for the SAP Support Portal. You request your user ID for the SAP Support Portal via ZZZVHUYLFHVDSFRP
$FWLYLWLHV
1. Enter a Solution Manager User in field "User". 2. Assign a SAP Support Portal contact (S-User without S) in field "Contact ". For S-user authorization requirements, see: Configuration Guide SAP Solution Manager 4.0.
SAP AG
SM100
4-75
0DLQWDLQ WKH 68VHU

0DLQWDLQ 8VHU DQG 68VHU QXPEHU WR IRUZDUG PHVVDJHV WR 6$3
SAP AG 2006
Insert the following data into one row: User: 6ROXWLRQ 0DQDJHU 8VHU Contact Person: 68VHU 1XPEHU
SAP AG
SM100
4-76
6HQG 0HVVDJH WR 6$3
SAP AG 2006
Return to the 2YHUYLHZ tab.
Switch to ,QIRUPDWLRQ IRU 6$3 Now enter the information directly or double-click on the textbox to enter the Text Editor
SAP AG
SM100
4-77
6HQG 0HVVDJH WR 6$3
SAP AG 2006
After entering the Information for SAP choose the Action Send Message to SAP from the Toolbox. Save the message.
SAP AG
SM100
4-78
6HQG 0HVVDJH WR 6$3
SAP AG 2006
You can see the referring SAPNet R/3 Frontend number and the changed message status.
SAP AG
SM100
4-79
6HFXUH $UHD ,QWHJUDWLRQ
SAP AG 2006
After sending the message to SAP you can maintain the Logon Data for your System via Action Choose the action Maintain SAP Logon Data from the Toolbox and Save the message
SAP AG
SM100
4-80
SAP AG 2006
Click on Display
SAP AG
SM100
4-81
SAP AG 2006
Choose the relevant System type
SAP AG
SM100
4-82
SAP AG 2006
Click on Create to enter the access data
SAP AG
SM100
4-83
SAP AG 2006
Fill in the required information
SAP AG
SM100
4-84
$QVZHU IURP 6$3
SAP AG 2006
Check manually for an update of your message at SAP
SAP AG
SM100
4-85
0HVVDJH 6WDWXV
SAP AG 2006
You can see that SAP Support has proposed an answer in the Message Status field. For automatic update, a batch job has to be defined (program RNOTIFUPDATE01).
SAP AG
SM100
4-86
&RQILUP 0HVVDJH
SAP AG 2006
After getting the answer from SAP you can confirm the Message to SAP Choose the action Confirm Message to SAP Save message
SAP AG
SM100
4-87
&RQILUPHG 0HVVDJH DW 6$3
SAP AG 2006
Move to the 6$3 $WWULEXWHV tab page. The status from the SAPNet R/3 Frontend message has changed.
SAP AG
SM100
4-88
&RPSOHWH WKH 0HVVDJH
SAP AG 2006
Now you can solve the problem and complete the message by changing the Status to Confirmed The message is completed.
SAP AG
SM100
4-89
$SSHQGL[ 0RQLWRULQJ
SAP AG 2006
SAP AG
SM100
4-90
6HUYLFH 'HVN 5HSRUWLQJ

7\SLFDO 4XHVWLRQV WR EH DQVZHUHG E\ 6HUYLFH 'HVN 5HSRUWLQJ +RZ PDQ\ LQFLGHQWV ZHUH UHSRUWHG"
)RU D JLYHQ WLPH LQWHUYDOO SHU RUJDQL]DWLRQ SHU 6$3 FRPSRQHQW
+RZ ORQJ GLG LW WDNH WR FRPSOHWH LQFLGHQWV"

+RZ PDQ\ ZHUH VROYHG ZLWK WKH LQWHUQDO VROXWLRQ GDWDEDVH" +RZ PDQ\ ZLWK 6$3 QRWHV" +RZ PDQ\ ZLWK KHOS IURP 6$3" 2YHUDOO DQG VSHFLILF
+RZ LV WKH VDWLVIDFWLRQ RI HQGXVHUV"
+RZ PDQ\ ZHUH FRQYHUWHG LQWR KRZ PDQ\ FKDQJH UHTXHVWV"
:KLFK LQFLGHQWV DUH LQ SURFHVVFRPSOHWHG "

%\ VHUYLFH GHVN HPSOR\HHRUJDQL]DWLRQ
SAP AG 2006
SAP AG
SM100
4-91
SAP AG 2006
Transaction DSWP Operations Solution Reporting Service Desk
SAP AG
SM100
4-92
$QDO\]H 6HUYLFH 'HVN 0HVVDJH
SAP AG 2006
Selection Screen
SAP AG
SM100
4-93

&RQWHQW 5HSRUWLQJ DERXW 6HUYLFH 'HVN 0HVVDJHV DVVLJQHG WR D VROXWLRQ
6\VWHP 'DWD 6\VWHP,%DVH ,QVWDOOWLRQ QXPEHU 7LPH ,QWHUYDO
$QDO\VLV 7\SH %XVLQHVV 3DUWQHU 6WDWXV 6ROXWLRQ ,QIRPDWLRQ
*URXSLQJ
0HVVDJH $WWULEXWHV 3ULRULW\ &DWHJRU\ &RPSRQHQW 6WDWXV

y 3HULRG :HHNO\ 0RQWKO\ $QQXDOO\ y 6WDWXV y &RPSRQHQW y &DWHJRU\
%XVLQHVV 3DUWQHU
SAP AG 2006
SAP AG
SM100
4-94
:KHUH WR )LQG WKH 7UDQVDFWLRQ 0RQLWRU
SAP AG 2006
You can start the Transaction Monitor in the SAP menu using 6HUYLFH 7UDQVDFWLRQ 0RQLWRU or choose transaction CRM_DNO_MONITOR.
SAP AG
SM100
4-95
7UDQVDFWLRQ 7\SHV
SAP AG 2006
You can use the User Variant function to maintain a variant U_ <username>. This variant is automatically included when calling the report transaction.
SAP AG
SM100
4-96
6HOHFWLRQ &ULWHULD 6XSHUYLVRU
SAP AG 2006
Mine: All my orders where Im assigned as processor My Departments: all orders, where I am or my colleagues of my organizational unit are assigned as message processor (inclusive mine!) My Colleagues: all orders, where the colleagues of my organizational unit are assigned as message processor (without mine)
SAP AG
SM100
4-97
6XSHUYLVRU LQ WKH 2UJDQL]DWLRQDO 6WUXFWXUH
SAP AG 2006
SAP AG
SM100
4-98
6HOHFWLRQ 9DULDQW 7UDQVDFWLRQ
SAP AG 2006
Save your variant in the Transaction Monitor Service Processes.
SAP AG
SM100
4-99
&UHDWLQJ SDUDPHWHU WUDQVDFWLRQ
SAP AG 2006
Via transaction PFCG you can create a role specific parameter transaction, and it will be automatically assigned to the role. Press the button Report Select ABAP report Report name: CRM_DNO_SERIVCE_MONITOR Variant: Your own defined variant optional: Skip selection screen
SAP AG
SM100
4-100
6HWWLQJV RI WKH %XVLQHVV 7UDQVDFWLRQV
SAP AG 2006
Select 6HWWLQJV.
SAP AG
SM100
4-101
6HWWLQJV
SAP AG 2006
Make sure that your user has the same settings as shown here and on the following worksheets.
SAP AG
SM100
4-102
6HWWLQJV
SAP AG 2006
A transaction type defines the characteristics and attributes of a business transaction (for example, sales order, service request, sales call), and specifies the control attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile). SLFN Service Desk Message SLFN Support Notification SLFV Service Desk Contract
SAP AG
SM100
4-103
'LVSOD\ 6HUYLFH 'HVN 0HVVDJH
SAP AG 2006
SAP AG
SM100
4-104
2SHQ D 6SHFLILF 0HVVDJH
SAP AG 2006
You can also access specific Service messages if you know their number. Choose 2SHQ and enter the message number.
SAP AG
SM100
4-105
$SSHQGL[ $GYDQFHG 6HUYLFH 'HVN
SAP AG 2006
SAP AG
SM100
4-106
&RQWUDFW 2YHUYLHZ 6FUHHQ
&RPSUHVV
+HDGHU 'DWD
,WHP 'DWD ([SDQG

SAP AG 2006
You can maintain the most important header and item data on the entry screen. With the buttons on the left, you can expand and compress the header and item data areas. There is a special CRM transaction type SLFV - Service Desk Contract already defined.
SAP AG
SM100
4-107
1HZ 8VHU ,QWHUIDFH ,QWHUDFWLRQ &HQWHU :HE &OLHQW
* available with Support Package Stack 6

SAP AG 2006
SAP AG
SM100
4-108
9~#FW 9 C 41 RF a tC H 6Ctf 6R F 9f aF H6 C FaF t FR 6 C 1 H Ha 4F 9 tW F 6 Y 96
SAP AG
SAP AG 2006
8VHU ,QWHUIDFH
SM100
4-109
9 F f
! a! 1
9C 96 T9 1 HT9 6 F F
D 1 9 1 WFF I 6 9 F9If

SAP AG
SAP AG 2006
8VHU ,QWHUIDFH
SM100
4-110
$SSHQGL[ ,QWHJUDWLRQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
SAP AG
SM100
4-111
+HOS ! &UHDWH 6XSSRUW 0HVVDJH

+HOS o &UHDWH 6XSSRUW 0HVVDJH
&RQWH[W 'DWD ZLOO EH GHOLYHUHG 6\VWHP YDULDEOHV &RPSRQHQW LV SUHDVVLJQHG GHSHQGV RQ WKH WUDQVDFWLRQ LQ ZKLFK WKH +HOS o &UHDWH 6XSSRUW 0HVVDJH ZDV H[HFXWHG $XWRPDWLF DVVLJQPHQW RI LQVWDOOHG EDVH FRPSRQHQW DQG EXVLQHVV SDUWQHUV $XWRPDWLF DVVLJQPHQW RI +RWOLQH 6XSSRUW VHUYLFH SURGXFW LQ WKH EDFNJURXQG 6$3 $WWULEXWHV 6$3 V\VWHP DQG GHWDLOV ILOOV DXWRPDWLFDOO\
SAP AG 2006
SAP AG
SM100
4-112
1RWLIBFUHDWH
7UDQVDFWLRQ QRWLIBFUHDWH
Simplified view to create a support request Direct assignment of PHVVDJH SURFHVVRU possible Direct assignment of the LQVWDOOHG EDVH FRPSRQHQW (with authorization concept) SAP Attributes will be read from SMSY transaction Possibility to hide not-wanted fields Automatic assignment of the +RWOLQH 6XSSRUW service product (in the background)
SAP AG 2006
SAP AG
SM100
4-113
,QWHUQHW &XVWRPHU 6HOI 6HUYLFH

,QWHUQHW &XVWRPHU 6HOI6HUYLFH
Self-Service for Solution Database
Own list of transactions can be displayed
No Context Data from SAP transaction
User required to submit Service Requests
SAP AG 2006
SAP AG
SM100
4-114
,QWHUDFWLRQ &HQWHU :HE &OLHQW
* Verfgbarkeit mit Support Package Stack 6

SAP AG 2006
SAP AG
SM100
4-115
SAP AG
SM100
4-116
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
5-1
7\SLFDO 4XHVWLRQV WR EH DQVZHUHG E\ &KDQJH 5HTXHVW 0DQDJHPHQW 5HSRUWLQJ
:KLFK FKDQJH UHTXHVWV DUH LQ SURFHVVFRPSOHWHG"

%\ VWDWXV W\SH QH[W VWHSV PDLQWHQDQFH ZLQGRZ 3HU RUJDQL]DWLRQ XVHU W\SH VWHS
+RZ ORQJ GR FKDQJH UHTXHVWV WDNH WR EH FRPSOHWHG" :KLFK WUDQVSRUWV EHORQJ WR ZKLFK FKDQJH UHTXHVW DQG YLFH YHUVD" :KDW LV WKH FXUUHQW WUDQVSRUW VWDWXV LQ ZKLFK V\VWHP" +RZ PDQ\ LQFLGHQWV WULJJHUHG D FKDQJH UHTXHVW"
3HU RUJDQL]DWLRQ 6$3 FRPSRQHQW
+RZ PDQ\ FKDQJH UHTXHVWV ZHUH GHFOLQHG"

3HU RUJDQL]DWLRQ XVHU W\SH E\ ZKRP DQG ZK\
SAP AG 2006
The Change Request Management processes extend the incident/problem message of SAP Solution Manager 7KH PDLQ IRFXV RI &KDQJH 5HTXHVW 0DQDJHPHQW LV WR JDLQ SURFHVV UHOLDELOLW\ DQG SURFHVV WUDQVSDUHQF\
Questions that can be answered by Change Request Management: Who changed which object, in which systems and when? Who requested/approved/developed/tested the change?
SAP AG
SM100
5-2
/HVVRQ 2EMHFWLYHV
'HILQH WKH &KDQJH 5HTXHVW 0DQDJHPHQW EXVLQHVV SURFHVV 'HVFULEH WKH YDULRXV HOHPHQWV RI &KDQJH 5HTXHVW 0DQDJHPHQW DV SDUW RI 6$3 6ROXWLRQ 0DQDJHU
$IWHU FRPSOHWLQJ WKLV OHVVRQ \RX ZLOO EH EH DEOH WR
([SODLQ KRZ WR XVH WKH 6$3 6ROXWLRQ 0DQDJHU V\VWHP IRU WKH &KDQJH 5HTXHVW 0DQDJHPHQW VFHQDULR
SAP AG 2006
SAP AG
SM100
5-3

2YHUYLHZ &KDQJH 5HTXHVW 0DQDJHPHQW 3URMHFWV DQG 5HOHDVH 0DQDJHPHQW 3URMHFWV DQG &KDQJH 5HTXHVWV 5HJXODU &RUUHFWLRQV 3URFHVV 8UJHQW &RUUHFWLRQV 3URFHVV
$GPLQLVWUDWLRQ DQG 7HVW 0HVVDJHV &KDQJH 5HTXHVW 5HSRUWLQJ $SSHQGL[
6HFXULW\ &RQFHSW DQG 2EMHFW /RFNLQJ 2XWORRN 8SFRPLQJ )HDWXUHV
SAP AG
SM100
5-4
8QLW 2EMHFWLYHV
([SODLQ WKH FRQFHSW RI WKH &KDQJH 5HTXHVW 0DQDJHPHQW
'HVFULEH WKH &KDQJH 5HTXHVW 0DQDJHPHQW VWRU\ OLQH
SAP AG 2006
SAP AG
SM100
5-5
6$3 6ROXWLRQ 0DQDJHU 6FHQDULRV &KDQJH 5HTXHVW 0DQDJHPHQW
SAP AG 2006
SAP AG
SM100
5RRW &DXVH $QDO\VLV
%86,1(66 352&(66(6
&25(
6ROXWLRQ 0RQLWRULQJ
6HUYLFH 'HVN
5-6

,7,/ 6FHQDULR &KDQJH 0DQDJHPHQW
SAP AG 2006
:KDW LV ,7,/" Acronym for the "IT Infrastructure Library" guidelines developed for the British government De-facto global standard in the area of service management Contains comprehensive publicly accessible documentation on the planning, provision and support of IT services Provides the basis for improvement of the use and effect of an operationally deployed IT infrastructure Describes the architecture for establishing and operating IT service management. The ITIL books are best practice guidelines for service management, with the guidelines describing what rather than how. Service management is tailored to the size, the internal culture and, above all, the requirements of the company. The impartial view of the external consultant may help to break away from the rigid structures.
SAP AG
SM100
B ' c d0 Y& E '
' 7BB C( 04 r&Ru ' B4 7 04 33Ru
7 6Y%
&KDQJH 0RQLWRULQJ
7 c `CB $u B 7 4 0 0 62& 2( 7 H 62 `cqx

5-7
i S D B ' c UEd0 Y&% ' 0 u B c B S &2r%d0 Y%eHC
B ' c d0 Yd a ' B B 4 0 @ H Cs20 2CY
B c d0 Y% Yv B A9 B B4 7 s20 3Y 2RD c B S 04 C3 E' 7BB ( 7B@ CCA9
7KUHH 7LHUV RI &KDQJH 5HTXHVW 0DQDJHPHQW

&KDQJH $GPLQ 3URMHFW 0DQDJHPHQW 3URMHFW 0DQDJHPHQW &KDQJH /RJLVWLFV &KDQJH &RQWURO DQG 5HFRUGLQJ
6WDWXV UHSRUWLQJ
SAP AG 2006
SAP AG
$SSURYDO ZRUNIORZ
%OXHSULQWLQJ DQG 6SHFLILFDWLRQ 7HVW PDQDJHPHQW
SM100
&KDQJH GRFXPHQWDWLRQ
3URMHFW 6FRSLQJ
&KDQJH UHTXHVW FDWHJRUL]DWLRQ
3URMHFW GRFXPHQWDWLRQ
e e
0DQDJHPHQW RI DOO FKDQJH UHTXHVWV
3URMHFW /DQGVFDSH 'HILQLWLRQ
3URMHFW &RQILJXUDWLRQ
e e e e e
6HDPOHVV LQWHJUDWLRQ LQWR 706 7UDQVSRUW VFKHGXOLQJ 7UDQVSRUW WUDFNLQJ
5-8
6WRU\ /LQH &KDQJH 5HTXHVW 0DQDJHPHQW

$Q HIIHFWLYH DSSOLFDWLRQ PDQDJHPHQW LV NH\ IRU FRPSDQLHV WR VWD\ DKHDG RI FRPSHWLWLRQ 6$3V VFRSH RI DSSOLFDWLRQ PDQDJHPHQW LQFOXGHV DOO W\SHV RI DSSOLFDWLRQ FKDQJHV
%XVLQHVV SURFHVV FKDQJHV LPSOHPHQWDWLRQ DQG XSJUDGH SURMHFWV 3HULRGLF PDLQWHQDQFH (PHUJHQF\ FRUUHFWLRQV
&KDQJH 5HTXHVW 0DQDJHPHQW VWUHQJWKHQV WKH VWUDWHJ\ RI 6$3 6ROXWLRQ 0DQDJHU DV 6$3V DSSOLFDWLRQ PDQDJHPHQW SODWIRUP ZKLFK
(QVXUHV UHOLDELOLW\ 5HGXFHV 7RWDO &RVW RI 2ZQHUVKLS DQG LQFUHDVHV 7RWDO 6ROXWLRQ 9DOXH
%ULGJHV WKH JDS EHWZHHQ EXVLQHVV UHTXLUHPHQWV DQG ,7 DGPLQLVWUDWLRQ
SAP AG 2006
SAP AG
SM100
5-9
&KDQJH 5HTXHVW 0DQDJHPHQW 5ROHV LQ D 1XWVKHOO

FUHDWHV DQ 6HUYLFH 0HVVDJH RU D &KDQJH 5HTXHVW GLUHFWO\ KDQGOHV WKH 6HUYLFH 0HVVDJH DQG FUHDWHV D &KDQJH 5HTXHVW FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH 6WHHULQJ &RPPLWWHH LQ WKH &KDQJH 0DQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH VHWV VWDWXV LQ WKH &KDQJH 'RFXPHQW WDNHV FDUH RI VRIWZDUH ORJLVWLFV
SAP AG 2006
SAP AG
# c ' C0 ad V T S4 %F% &CR" 4 0 B4 h 3&b 4 cS 20 %UT 47BB ( 7B@ t9 4 B 0 3Fx #4 0 S f2 A 7B@ t9 4 d%
4 0 H G 2r%dRD
SM100
5-10
8QLW 6XPPDU\

([SODLQ WKH FRQFHSW RI WKH &KDQJH 5HTXHVW 0DQDJHPHQW
'HVFULEH WKH &KDQJH 5HTXHVW 0DQDJHPHQW VWRU\ OLQH
SAP AG 2006
SAP AG
SM100
5-11

SAP AG
SM100
5-12
8QLW 2EMHFWLYHV

([SODLQ WKH HOHPHQWV RI D SURMHFW F\FOH
([SODLQ WKH XVH FDVH RI FKDQJH PDQDJHPHQW EDVHG RQ SURMHFW F\FOHV
([SODLQ WKH SKDVH VWUXFWXUH RI D SURMHFW F\FOH
SAP AG 2006
SAP AG
SM100
5-13
5HOHDVH 0DQDJHPHQW

Physical (development) systems Logical systems (clients) Transport Request
CTS project
Project cycle transaction
Project cycle task list
IMG project
F3URMHFWV
CTS project CTS project

Project created in cProjects
SAP Solution Manager project
IMG project
CTS project CTS project CTS project

SAP AG 2006
The Solution Manager project is represented as IMG projects in each satellite system and CTS project in each satellite system client. For each Solution Manager project a project cycle is beeing generated represented by a tasklist for managing the technical administration and a cycle transaction managing the organizational administration of the project cycle. Transport requests are only managed by the project cycle and the project assignment of each transport request is mandatory The Solution Manager project can be extended by cProjects for managing project phases and project tasks. cProjects allow the management of interproject dependencies.
SAP AG
SM100
5-14
6$3 6ROXWLRQ 0DQDJHU 3URMHFWV DQG 3URMHFW &\FOHV
F3URMHFW 6$3 6ROXWLRQ 0DQDJHU SURMHFW 3URMHFW F\FOH
SAP AG 2006
Each project cycle is controlled by its phases. Project phases are static and linked to each cycle Each project cycle phase offers certain functions in differ by the project type.
SAP AG
SM100
hvut jsn h l {i d%m ~

5-15
h v u t n q r zz m {kjAm rj{`hds qh zh o s%p%
hvutnrv {sspCssh }
|hvu l zy xzm y ksskh p`hR{em$ wx hvutnrqh on lhih ksj%Csppm kjg
&KDQJH 5HTXHVW 0DQDJHPHQW 5ROHV

FUHDWHV DQ VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH DQG VHWV LWV VWDWXV LQ WKH UHOHYDQW FKDQJH WUDQVDFWLRQ WDNHV FDUH RI VRIWZDUH ORJLVWLFV
SAP AG 2006
The role Change Manager is defined for managing project cycles. The role Developer is defined for doing changes in satellite systems. The role IT Operator is defined for managing imports.
SAP AG
# c ' C0 ad V T S4 %F% &CR" 4 0 B4 h 3&b 4 cS 20 %UT 47BB ( 7B@ t9 4 B 0 3Fx #4 0 S f2 A 7B@ t9 4 d%
4 H G d%dRD
SM100
5-16
&KDQJH 5HTXHVW 0DQDJHPHQW &\FOH 0DQDJHPHQW

SAP AG 2006
The project cycle is an abstraction layer that cannot be changed representing the fix phase structure of a cycle. The cycle tasklist is one representative of the cycle and represents the system landscape tracks with tasks to be used by an IT operator or IT administrator for managing project related IT activities, esp. imports. Custom tasklist templates with additional tasks can be created by customers. The cycle transaction represents the service request for managing the phase changes. Dokumentation, additional status, notification, electronic signatures etc. can be managed from within the cycle transaction. Phase shifts should be done from within the cycle transaction but not from within the cycle tasklist since additional activities and status can only be managed from within the service reqeust.
SAP AG
SM100
T
Cycle Task List
ev`rsp6urtk lh mrsm z m n v q zr l zr q
"
Project Cycle
5-17
T D q$u
4( 7BB 7B@ A9
Cycle Transaction
6WDWXV 6FKHPD RI D 6LQJOH 3URMHFW &\FOH

:LWKGUDZQ &UHDWHG ,Q 'HYHORSPHQW ZLWKRXW 5HOHDVH ,Q 'HYHORSPHQW ZLWK 5HOHDVH 7HVW (PHUJHQF\ &RUUHFWLRQ *R /LYH %HLQJ &RPSOHWHG
SAP AG 2006
&RPSOHWHG
SAP AG
SM100
5-18
5HOHDVH 0DQDJHPHQW ZLWK &KDQJH 5HTXHVW 0DQDJHPHQW 6$3 6ROXWLRQ 0DQDJHU SURMHFWV FDQ EH H[WHQGHG E\ DGGLQJ SURMHFW F\FOHV ZKLFK FRQWURO SURMHFW SKDVHV 3URMHFW SKDVHV GHWHUPLQH ZKHWKHU RU QRW WUDQVSRUW UHTXHVWV FDQ EH FUHDWHG UHOHDVHG RU LPSRUWHG 3URMHFW SKDVHV DUH YLVLEOH LQ WKH EOXHSULQW DQG FRQILJXUDWLRQ WUDQVDFWLRQV F3URMHFWV FDQ EH XVHG WR H[WHQG SURMHFW PDQDJHPHQW FDSDELOLWLHV DQG WR PDQDJH PXOWLSOH SKDVHVSHFLILF SURMHFWV
SAP AG 2006
This is the IT Infrastructure Library (ITIL) definition of release management. ITIL is the de-facto global standard for service management. For more information, go to www.itil.org
SAP AG
SM100
5-19
3URMHFW $GPLQLVWUDWLRQ DQG 3URMHFW &\FOHV
&\FOH 7DVN /LVW
&\FOH &50 7UDQVDFWLRQ
3URMHFW &\FOH
6\VWHP /DQGVFDSH 6\VWHPV /RJLFDO &RPSRQHQWV
3URMHFW $GPLQLVWUDWLRQ 3URMHFW /DQGVFDSH
SAP AG 2006
Project cycles can be created in SOLAR_PROJECT_ADMIN as of SAP Solution Manager 4.0 and in /TMWFLOW/CMSCONF as SAP Solution Manager 3.20 System Landscape can be maintained with transaction SMSY. Data retrieval for systems can be linked to LIS (TMS funktionality ) or SLD. Projekt Administration can be maintained with transaction SOLAR_PROJECT_ADMIN.
SAP AG
SM100
5-20
&RQVLVWHQF\ RI 3URMHFW &\FOHV :LWK ,PSRUW 3URMHFW
Project transport requests
SAP AG 2006
Regular corrections are exported as test transports. Test transports are performed as transports of copies.
Imports into test systems are performed by using the import method LPSRUW SURMHFW. (All project-related transport requests are imported in the sequence in which they are exported into the test system.) At the time of test confirmed status, all transport requests that belong to a regular correction are exported. No new transport requests can be created for that particular regular correction. ( new implementation of transaction type SDMI, named SDMJ will be released as of SP13 for SAP Solution Manager 3.20 and SP5 for SAP Solution Manager 4.0 )
SAP AG
SM100
q$ $
5-21
z r z Xh`s{hm qt
z r z phjkXhj6m q
8QLW 6XPPDU\
([SODLQ WKH XVH FDVH RI FKDQJH PDQDJHPHQW EDVHG RQ SURMHFW F\FOHV
([SODLQ WKH SKDVH VWUXFWXUH RI D SURMHFW F\FOH
([SODLQ WKH HOHPHQWV RI D SURMHFW F\FOH
SAP AG 2006
SAP AG
SM100
5-22

SAP AG
SM100
5-23
8QLW 2EMHFWLYHV
([SODLQ WKH UHOHYDQW FRQWURO LWHPV ZLWKLQ D FKDQJH UHTXHVWV 6XEMHFWV ,QVWDOOHG %DVH ,%DVH
'HVFULEH WKH SKDVH VHPDQWLFV RI LPSOHPHQWDWLRQ XSJUDGH WHPSODWH DQG PDLQWHQDQFH SURMHFW F\FOHV
SAP AG 2006
SAP AG
SM100
5-24
5HJXODU &RUUHFWLRQV LQ 3URMHFW &\FOHV

6$3 6ROXWLRQ 0DQDJHU &KDQJH 5HTXHVW 0DQDJHPHQW
'HYHORSPHQW
7HVW
3URGXFWLRQ
8SJUDGH (53
,PSOHPHQWDWLRQ 3URMHFW 0DUNHW &DPSDLJQ
0DLQWHQDQFH 3URMHFW )LQDQFH 6ROXWLRQ )LQDQFH 0DLQWHQDQFH &\FOHV
8UJHQW &RUUHFWLRQV
SAP AG 2006
Projects are defined by their release cycles. Any change related to a project moves synchronously from development through test to production or delivery. Projects within the Change Request Management context are implementation, upgrade, template projects. Implementation, upgrade, and template projects can be planned and controlled by cProjects project plans; change requests can be created and released by means of change transactions in the Service Desk. One implementation, upgrade, or template project is represented by one task list for managing flow consistency. cProjects allows resource management, time sheet management, and cost controlling, as well as program management. Technically, an implementation, upgrade, or template project is imported with one or more import projects. Maintenance cycles are phases within an ongoing maintenance project, which is intended to provide a stable production environment. One maintenance cycle is represented by a task list, which ensures a consistent change flow. Technically, a maintenance cycle is managed by one or more import projects. Urgent corrections are fast changes that have to be imported into the production environment as quickly as possible. Urgent corrections are represented by a task list, which ensures a consistent change flow. Technically, an urgent correction is managed by import subset and is automatically merged into the current open maintenance cycle.
SM100 5-25
SAP AG
&KDQJH 5HTXHVW 0DQDJHPHQW $UFKLWHFWXUH

6$3 6ROXWLRQ 0DQDJHU Physical (development) systems Logical systems (clients)
Change Transaction
Cycle Task List
Transport Transport Transport Request Request Request

CTS project
Change Request
Cycle Transaction
IMG project
F3URMHFWV

Solution Manager Project
IMG project

SAP AG 2006
The prerequisite for creating change request is the existence of a solution manager project with IMG project for satellite system(s) and CTS Project for development client(s). During approval the existance of a Project cycle including a cycle transaction and a cycle task list is checked.
SAP AG
SM100
5-26

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW LI QHFHVVDU\ FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH 6WHHULQJ &RPPLWWHH LQ WKH &KDQJH 0DQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV LW RYHU WR EH WHVWHG WHVWV D FKDQJH DQG VHWV LWV VWDWXV LQ WKH FKDQJH WUDQVDFWLRQ WDNHV FDUH RI WKH VRIWZDUH ORJLVWLFV VLGH RI LPSOHPHQWLQJ WKH FKDQJH
SAP AG 2006
SAP AG
C ad %F% &CR 3 b 2 %U t 3 F f2 A t d%
d%dR
SM100
5-27
,PSOHPHQWDWLRQ 8SJUDGH DQG 7HPSODWH 3URMHFWV

F3URMHFW 6$3 6ROXWLRQ 0DQDJHU 3URMHFW 3URMHFW 3KDVHV
Synchronizing
Synchronizing
Synchronizing
SAP AG 2006
For Implementation, Upgrade and Template Projects, regular corrections can be only approved during the project phase development w/o release and development w/ release.
SAP AG
SM100
h k i Xl%m ~
5-28
q r zz m &jk`hrm qh zh o sp6%
rv kjh }
|hvu l zy xzm y skjkh %ehdt`mR wx hvutnrqh on lhih sj%Cjpm kjg v q r zz jm &{`hdm z lh u p{
Change Transaction Project Phases
t ev`rsp6urtk lh mrsm z m n v q zr l zr q q$
uhh s{kk
&KDQJH 5HTXHVW 0DQDJHPHQW 5HJXODU &RUUHFWLRQ
Service Message
dCdR
Change Request
Ce2 %F%e&$
SAP AG
SAP AG 2006
SM100
5-29
0DLQWHQDQFH 3URMHFW &\FOH

F3URMHFW 6$3 6ROXWLRQ 0DQDJHU 3URMHFW 0DLQWHQDQFH 3URMHFW 0DLQWHQDQFH &\FOH 0&
Synchronization
Synchronization
Synchronization
SAP AG 2006
In a maintenance project regular corrections can be approved during all phases starting development w/o release up to Go-Live. Urgent Corrections in addition can be approved also during all phases starting development w/o release up to Go-Live.
SAP AG
SM100
h {i dm ~
5-30
q r zz m rj{`hdm qh zh o jspp
rv ksh }
| mqpkkkq Xw r hqhnh v q r z jm rs{`hXzm rqh z %
|hvu l zy xzm y {jksh `hRemR wx rqh on lhih jm p{Cg v q r z jm rs{`hXzm z lh pu {C
&KDQJH 5HTXHVW 0DQDJHPHQW 8UJHQW &RUUHFWLRQ

Service Message
SAP AG 2006
Different to regular corrections urgent corrections can be managed independent from each other and have their own task list that is being generated when an urgent correction is being approved.
SAP AG
SM100
t
Change Transaction
Task List
q$
Change Request
dCdR
5-31
uhh s{kk
Ce2 %F%e&$
8QLW 6XPPDU\
([SODLQ WKH UHOHYDQW FRQWURO LWHPV ZLWKLQ D FKDQJH UHTXHVWV 6XEMHFWV ,%DVH
'HVFULEH WKH SKDVH VHPDQWLFV RI LPSOHPHQWDWLRQ XSJUDGH WHPSODWH DQG PDLQWHQDQFH SURMHFW F\FOHV
SAP AG 2006
SAP AG
SM100
5-32

SAP AG
SM100
5-33
8QLW 2EMHFWLYHV
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR XQGHUVWDQG WKH IROORZLQJ FRQFHSWV
,QWHJUDWLRQ RI D UHJXODU FRUUHFWLRQ XVH FDVH LQWR WKH YDULRXV FRQFHSWV IRU PDQDJLQJ SURMHFW F\FOH SKDVHV
7UDQVSRUW FRQFHSW RI WKH UHJXODU FRUUHFWLRQ XVH FDVH
6HPDQWLFV RI UHJXODU FRUUHFWLRQV DQG KRZ WKH\ GLIIHU IURP XUJHQW FRUUHFWLRQV
SAP AG 2006
SAP AG
SM100
5-34

'HYHORSPHQW
7HVW
3URGXFWLRQ
8SJUDGH (53
8UJHQW &RUUHFWLRQV
SAP AG 2006
SM100 5-35
SAP AG

6$3 6ROXWLRQ 0DQDJHU Physical systems Logical systems (clients)
Regular Correction
Cycle Tasklist
'HYHORSPHQW
Transport Request
Change Request
Cycle Transaction
IMG project
CTS project
([SRUW WUDQVSRUW UHTXHVWV 21/<
7HVW
SAP AG 2006
A regular correction is beeing generated as a follow-up transaction by the approval activity. You can find a regular correction when selecting Change document in the easy web access or by starting CRM_DNO_MONITOR transaction and selecting transaction type SDMI. Regular Corrections are directly linked to a project cycle transaction and project cycle tasklist. From within a regular correction the creation of a transport request and transport task and the release of related transports are controlled by the Change request/regular correction. Imports are done by means of import projects from within the cycle tasklist.
SAP AG
SM100
5-36
&KDQJH 5HTXHVW 0DQDJHPHQW 3URMHFW &\FOH

Created Development Development Test Go-Live In Completion Cycle Transaction/ Tasklist Solution Manager Project
IMG project
CTS project
Transport Transport Request Transport Request Request
3URGXFWLRQ
,PSRUW &76 SURMHFW EXIIHU LQFOXGLQJ DOO UHJXODU DQG XUJHQW FRUUHFWLRQV
SAP AG 2006
Import into Production is controlled by the Cycle Tasklist and Cycle Transaction.
SAP AG
SM100
5-37
,PSOHPHQWDWLRQ 8SJUDGH DQG 7HPSODWH 3URMHFWV

Synchronizing
Synchronizing
Synchronizing
SAP AG 2006
For Implementation, Upgrade and Template Projects, regular corrections can be only approved during the project phase development w/o release and development w/ release.
SAP AG
SM100
h ki r%m ~ er{%jAC zmnh m

5-38
q r z m rs{`hXzm qh zh o k6 `rkjtC zmnh m
rv {sh } `rkjA zmnh m
|hvu l zy xzm y ksskh p`hR{em$exw rqh on lhih pm kjg v q r z jm &sk6hXzm z lh u k
0DLQWHQDQFH 3URMHFWV
Synchronizing
Synchronizing
Synchronizing
SAP AG 2006
For Maintenance Projects Regular Corrections can be approved during the phases Development w/o release up to Go-Life.
SAP AG
SM100
h ki r%m ~ er{%jAC zmnh m
q r z m rs{`hXzm qh zh o k6 `rkjtC zmnh m
rv {sh } `rkjA zmnh m
|hvu l zy xzm y ksskh p`hR{em$exw rqh on lhih pm kjg v q r z jm &sk6hXzm z lh u k
5-39

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW LI QHFHVVDU\ FDWHJRUL]HV DSSURYHV DQG PRQLWRUV FKDQJH UHTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH VHWV VWDWXV LQ WKH &KDQJH 'RFXPHQW WDNHV FDUH RI VRIWZDUH ORJLVWLFV
SAP AG 2006
The regular correction directly addresses developers, unit testers and IT operators for managing project imports
SAP AG
C ad %F% &CR 3 b 2 %U t 3 F f2 A t d%
d%dR
SM100
5-40
Regular Correction Project Phases
2& 1 d% d %R
Change Request
t ev`rsp6urtk lh mrsm z m n v q zr l zr q q$
uhh s{kk
Service Message
dCdR
Ce2 %F%e&$
SAP AG
SAP AG 2006
A regular Correction is directly linked to the cycle transaction and cycle tasklist.
SM100
5-41
&RQVLVWHQW 5HJXODU &RUUHFWLRQV LQ D 3URMHFW &\FOH
Regular Corrections Test Transports (Transport of Copies)
SAP AG 2006
Regular corrections are exported as test transports, which are performed as transports of copies. Imports into test systems are performed by using the import project method. (All project-related transport requests are imported in the same sequence in which they are exported into the test system.) At development close, all transport requests that belong to a regular correction are exported. No new transport requests can be created for the regular correction.
SAP AG
SM100
q$ $
5-42
6% j{X6 qt
p6j%CjkXj` q
F F F F F F F pC23R
U U U U F U U %R
F F F F U F F C R
U U U U U U d2
F F F F F F F %U e
F F F F F C3
F F F F U U U
d ` & 2 Y&5 %C3d %% &tIR &2 %rtIR d & 2 5%3Y2 YU
SAP AG
SAP AG 2006
6WDWXV WUDQVLWLRQ PDWUL[ IRU UHJXODU FRUUHFWLRQV LQ LPSOHPHQWDWLRQXSJUDGHWHPSODWH SURMHFWV
&RPELQDWLRQ RI SURMHFW SKDVH DQG UHJXODU FRUUHFWLRQ VWDWXV YDOXH
3URMHFW 3KDVHV DQG 5HJXODU &RUUHFWLRQV LQ 3URMHFWV
SM100
5-43
F F F F F F F pC23R
U U U U F U U %R
F F F F U F F C R
U U U U U U d2
F F F F F F F %U e
F F C3
F U U U U U U
d ` & 2 Y&5 %C3d %% &tIR &2 %rtIR d & 2 5%3Y2 YU
SAP AG
SAP AG 2006
6WDWXV WUDQVLWLRQ PDWUL[ IRU UHJXODU FRUUHFWLRQ LQ PDLQWHQDQFH SURMHFWV
&RPELQDWLRQ RI SURMHFW SKDVH DQG UHJXODU FRUUHFWLRQ VWDWXV YDOXH
3URMHFW 3KDVHV DQG 5HJXODU &RUUHFWLRQV LQ 0DLQWHQDQFH
SM100
5-44
8QLW 6XPPDU\
$IWHU FRPSOHWLQJ WKLV XQLW \RX DUH QRZ DEOH WR XQGHUVWDQG WKH IROORZLQJ FRQFHSWV
6HPDQWLFV RI UHJXODU FRUUHFWLRQV DQG KRZ WKH\ GLIIHU IURP XUJHQW FRUUHFWLRQV
,QWHJUDWLRQ RI D UHJXODU FRUUHFWLRQ XVH FDVH LQWR WKH YDULRXV FRQFHSWV IRU PDQDJLQJ SURMHFW F\FOH SKDVHV
7UDQVSRUW FRQFHSW RI WKH UHJXODU FRUUHFWLRQ XVH FDVH
SAP AG 2006
SAP AG
SM100
5-45

SAP AG
SM100
5-46
8QLW 2EMHFWLYHV
,QWHJUDWLRQ RI WKH XUJHQW FRUUHFWLRQ SURFHVV LQWR WKH SKDVH PDQDJHPHQW RI PDLQWHQDQFH F\FOHV
7UDQVSRUW FRQFHSW RI WKH XUJHQW FRUUHFWLRQ SURFHVV
6HPDQWLFV RI XUJHQW FRUUHFWLRQV
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR H[SODLQ
SAP AG 2006
SAP AG
SM100
5-47

Urgent Correction
Urgent Correction Tasklist Cycle Tasklist
'HYHORSPHQW
Transport Request
Change Request
IMG project
CTS project
Solution Manager Maintenance Project
7HVW
3URGXFWLRQ
,PSRUW XUJHQW FRUUHFWLRQ ,1 $'9$1&(
SAP AG 2006
When an urgent correction is being approved a single tasklist for each urgent correction is being generated. The urgent correction transaction allows to perform changes from development up to production in the context of a maintenance project cycle but individually.
SAP AG
SM100
5-48

'HYHORSPHQW
7HVW
3URGXFWLRQ
8SJUDGH (53
8UJHQW &RUUHFWLRQV
SAP AG 2006
SM100 5-49
SAP AG
e{%jAC % p{ e{%jAC `kjtC es%j
j rs{`X %
j rs{`X p {C { d rj{`d jspp ks

Synchronization Synchronization
{jks `ReR j p{C
SAP AG
SAP AG 2006
6ROXWLRQ 0DQDJHU 0DLQWHQDQFH 3URMHFWV DQG &\FOHV
6$3 6ROXWLRQ 0DQDJHU 3URMHFW 0DLQWHQDQFH 3URMHFW
F3URMHFW
0DLQWHQDQFH &\FOH
SM100
5-50

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW LI QHFHVVDU\ FDWHJRUL]HV DSSURYHV DQG PRQLWRUV FKDQJH UHTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH VHWV VWDWXV LQ WKH &KDQJH 'RFXPHQW WDNHV FDUH RI VRIWZDUH ORJLVWLFV
SAP AG 2006
SAP AG
G % ' E 7& FD C " 9 $ BA@ 87 6 & ' 1 54 32 0) ' % $ (& #" ! I & 4 BS G & 9 $ I R( QPH )

SM100
5-51

Service Message
Project Phases
SAP AG 2006
An urgent correction is represented by a singular task list that is created when an urgent correction is being generated during approval time. An urgent correction tasklist is being closed when the urgent correction is being closed. An urgent correction can be described as the smallest subproject of a broader maintenance project cycle.
SAP AG
SM100
e`sp6rt rs u
6 H
Change Transaction
Task List
e`sp6rt rs u
" $
D y"
7 ! 7
Change Request
7
5-52
w u xsvkkt
G &% ' E 7(D C " @9 $ BA8 6 & ' 1 (8 2 0) ' % $ & " ) pUi fsU gUe gU ef WV U XY hU Ù TU
aq ef r
ab q dc
&RQVLVWHQF\ LQ D 3URMHFW &\FOH
Regular corrections Urgent corrections Consolidated transport
SAP AG 2006
Urgent Corrections are imported with import subset in the sequence the transport requests are exported. Urgent Corrections are re-imported with import project of the project cycle
SAP AG
SM100
" $ I
5-53
eksp6
6 H
%66j%C`k%j`
D "
& & B B B B & j @ I & R7(R
& # & # I & % R
& # & # ) & Q)
& B & B # # # # & B & ' 5QD
& B B B B B & '5& %$#" 0
& B B B B B B & B $ & ' ' 7RkH
& #
9 % ' E & d Q& 0 9 $ Q8& e &9 @ R8fQ& G @ AD E ) & ' i g $ 855h#" 8(&'QAih#" & g $ 9 @ E & & f4d(& % lQB
SAP AG
SAP AG 2006
6WDWXV WUDQVLWLRQ PDWUL[ IRU XUJHQW FRUUHFWLRQV
&RPELQDWLRQ RI SURMHFW SKDVH DQG XUJHQW FRUUHFWLRQ VWDWXV YDOXH
3URMHFW 3KDVHV DQG 8UJHQW &RUUHFWLRQV LQ 0DLQWHQDQFH
SM100
5-54
8UJHQW &RUUHFWLRQV 3URFHVV 8QLW 6XPPDU\
7UDQVSRUW FRQFHSW RI WKH XUJHQW FRUUHFWLRQ SURFHVV
6HPDQWLFV RI XUJHQW FRUUHFWLRQV
$IWHU FRPSOHWLQJ WKLV XQLW \RX DUH QRZ DEOH WR H[SODLQ
,QWHJUDWLRQ RI WKH XUJHQW FRUUHFWLRQ SURFHVV LQWR WKH SKDVH PDQDJHPHQW RI PDLQWHQDQFH F\FOHV
SAP AG 2006
SAP AG
SM100
5-55

SAP AG
SM100
5-56
$GPLQLVWUDWLRQ DQG 7HVW 0HVVDJHV 8QLW 2EMHFWLYHV
,QWHJUDWLRQ RI WKH WHVW PHVVDJH SURFHVV LQWR WKH YDULRXV PDQDJHPHQW FRQFHSWV RI WKH SURMHFW F\FOH SKDVHV
6HPDQWLFV RI WKH DGPLQLVWUDWLRQ PHVVDJH DQG WKH WHVW PHVVDJH
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR XQGHUVWDQG WKH IROORZLQJ FRQFHSWV
SAP AG 2006
SAP AG
SM100
5-57
7HVW 0HVVDJH

Physical (development) systems Logical systems (clients)
Test Message
Cycle Task List

CTS project
Cycle Transaction
F3URMHFWV
IMG project

IMG project

SAP AG 2006
SAP AG
SM100
5-58
3URMHFW &\FOH
Synchronizing
Synchronizing
Synchronizing
SAP AG 2006
A test message allows to create and export a transport request within the test phase of a project cycle.
SAP AG
SM100
{ d
5-59
rj{`d jspp
ks
XjsF &s`{X { rmu spk{ss kk
{jks `ReR j p{C

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW LI QHFHVVDU\ FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH VHWV VWDWXV LQ WKH &KDQJH 'RFXPHQW WDNHV FDUH RI WKH VRIWZDUH ORJLVWLFV SDUW
SAP AG 2006
A test message is supposed to be created by a tester but only in the phase test of a certain project. The test phase represents the integration test phase within a project cycle. Corrections are therefore not directly linked to a change request but to the allover project cycle. The Change Manager or Quality Assurance Manager or Project Manager creates the ability to create test messages for a certain project when she/he switches a phase to TEST.
SAP AG

SM100
5-60
D y"
e`sp6rt rs u
6 H
) ' % $ & "
e`sp6rt rs u
" $ 7 ! 7
SAP AG
SAP AG 2006
Cycle Transaction
Test Massage
SM100
Project Phases Cycle Tasklist
5-61
ef gU pUi gUe fsU q hU aq ef r
dc
& B Hi n Hi n Hi n Hi n Hi n Hi n j @ I & dp7(4
& # Hi m Hi m Hi m Hi m Hi m Hi m I & % 4#
& B & B & B # & B & B & B ) & QQ)
& # & # & # & # & # & # & ' (QD
& B & B & B B & B & B & B ' % $ 5& #" 0
& B Hi n Hi n Hi n Hi n Hi n $ & ' ' 74kH
& B # # # # # #
9 % ' E & d oQ& 0 9 $ Q8& e 9 @ & l8f5& G @ AD E ) & ' i g $ 855h" 8(&'QAih" & g $ 8 9 @ E & & f4l(& % l5#
SAP AG
SAP AG 2006
6WDWXV WUDQVLWLRQ PDWUL[ IRU WHVW PHVVDJHV
&RPELQDWLRQ RI SURMHFW SKDVH DQG WHVW PHVVDJH VWDWXV YDOXH
3URMHFW 3KDVHV DQG 7HVW 0HVVDJHV LQ 3URMHFWV
SM100
5-62
$GPLQLVWUDWLRQ 0HVVDJH

Physical (development) systems Logical systems (clients)
Admin Message
Cycle Task List
Change Request
Cycle Transaction
F3URMHFWV
SAP AG 2006
SAP AG
SM100
5-63
$GPLQLVWUDWLRQ 0HVVDJHV LQ 3URMHFW &\FOHV

Synchronizing
Synchronizing
Synchronizing
SAP AG 2006
SAP AG
SM100
{ d
5-64
rj{`d jspp
ks
{jks `ReR j p{C 5q u

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW LI QHFHVVDU\ FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR EH WHVWHG WHVWV D FKDQJH DQG VHWV LWV VWDWXV LQ WKH FKDQJH WUDQVDFWLRQ WDNHV FDUH RI WKH VRIWZDUH ORJLVWLFV
SAP AG 2006
Administration messages must be approved by a change request different to test messages that are opened to be performed whenever a project cycle phase is being switched to test. Adminisration messages allow the documentation and test of administration changes in systems. The administration message is linked to the cycle tasklist and custom tasks can be added to the cycle tasklist template.
SAP AG

SM100
5-65
D y" & ' 1 (8 2 0) gU pUi gUe

Change Request
" $
7 ! 7
w u xsvkkt
&KDQJH 5HTXHVW 0DQDJHPHQW $GPLQLVWUDWLRQ 0HVVDJH
Service Message
7
Admin Message
Cycle Tasklist
6 H
G &% ' E 7(D C " @9 $ BA8 6 Ù
SAP AG
SAP AG 2006
SM100
Project Phases
5-66
ef hU aq ef r fsU q
dc
WV U XY ab
TU
& B Hi n Hi n Hi n Hi n Hi n & B j @ I & dp7(4
& # Hi m Hi m Hi m Hi m Hi m & # I & % 4#
& B # # # # # & B ) & QQ)
& # Hi r( Hi r( Hi r( Hi r( Hi r( & ' (QD
& B B B B B B & B ' % $ 5& #" 0
& B Hi n Hi n & B $ & ' ' 74kH
& B # # # # # #
9 % ' E & d oQ& 0 9 $ Q8& e 9 @ & l8f5& G @ AD E ) & ' i g $ 855h" 8(&'QAih" & g $ 8 9 @ E & & f4l(& % l5#
SAP AG
SAP AG 2006
6WDWXV WUDQVLWLRQ PDWUL[ IRU DGPLQLVWUDWLRQ PHVVDJHV
&RPELQDWLRQ RI SURMHFW SKDVH DQG DGPLQ PHVVDJH VWDWXV YDOXH
3URMHFW 3KDVHV DQG $GPLQLVWUDWLRQ 0HVVDJHV LQ 3URMHFWV
SM100
5-67
8QLW 6XPPDU\
,QWHJUDWLRQ RI WKH WHVW PHVVDJH SURFHVV LQWR WKH YDULRXV PDQDJHPHQW FRQFHSWV RI WKH SURMHFW F\FOH SKDVHV
6HPDQWLFV RI WKH DGPLQLVWUDWLRQ PHVVDJH DQG WKH WHVW PHVVDJH
SAP AG 2006
SAP AG
SM100
5-68

SAP AG
SM100
5-69
8QLW 2EMHFWLYHV
$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR XQGHUVWDQG WKH IROORZLQJ FRQFHSWV $XWKRUL]DWLRQ FRQFHSW RI &KDQJH 5HTXHVW 0DQDJHPHQW XVH FDVHV
&RQFHSW RI FURVVV\VWHP REMHFW ORFN DQG FULWLFDO REMHFW FKHFN
SAP AG 2006
SAP AG
SM100
5-70
&URVV 6\VWHP /RFN 0DQDJLQJ 3DUDOOHO 3URMHFWV

Cycle Cycle Transaction Transaction
Cycle Task List

CTS project
IMG project
F3URMHFWV

IMG project

SAP AG 2006
SAP AG
SM100
5-71
0DQDJLQJ 3DUDOOHO &KDQJHV LQ 0XOWLSOH 3URMHFWV

'HYHORSPHQW
7HVW
3URGXFWLRQ
,PSOHPHQWDWLRQ 3URMHFW 0DUNHW &DPSDLJQ ,PSOHPHQWDWLRQ 5HRUJ )LQDQFH
0DLQWHQDQFH 3URMHFW )LQDQFH DQG &XVWRPHU 5HODWLRQ 0DLQWHQDQFH &\FOHV
8UJHQW &RUUHFWLRQV
SAP AG 2006
Use Case: An implementation project (Market Campaign) is in development for 4 months. An implementation project (Re-org Finance) is in development for 3 months.
A maintenance project for finance and customer relationship management is ongoing, and actively supporting the production system with fixes and short-term functional extensions.
SAP AG
SM100
5-72
'RZQJUDGH 5LVN ZLWK 8UJHQW &RUUHFWLRQV
Urgent Corrections
SAP AG 2006
The locking of objects within an urgent correction prohibits an urgent correction to bypass another with the same object but a newer object version
SAP AG
SM100
" $
5-73
I
6 H

t x~~ } | z y xv ut prrwQ7{xrwms

t x~~ } | z y xv ut rn{{ms D "
'RZQJUDGH 5LVN ZLWK 5HJXODU &RUUHFWLRQV
Project1 Project2 Project3

SAP AG 2006
Regular corrections or project transports that share the same production system, but have different life cycles can include the same objects, but with different versions. Depending on the life cycle of parallel projects and on object conflicts, objects might be downgraded.
SAP AG
SM100
" $ I
5-74
t x~~ } | z y xv ut prrwQ7{xrwms 6 H
t x~~ } | z y xv ut rn{{ms D "

FUHDWHV D VHUYLFH PHVVDJH RU D FKDQJH UHTXHVW GLUHFWO\ KDQGOHV WKH VHUYLFH PHVVDJH DQG FUHDWHV D FKDQJH UHTXHVW FDWHJRUL]HV DSSURYHV DQG PRQLWRUV &KDQJH 5HTXHVWV LV WKH VWHHULQJ FRPPLWWHH LQ WKH FKDQJH PDQDJHPHQW SURFHVV LPSOHPHQWV D FKDQJH DQG KDQGV RYHU WR WKH 7HVWHU WHVWV D FKDQJH DQG VHWV VWDWXV LQ WKH FKDQJH WUDQVDFWLRQ WDNHV FDUH RI WKH VRIWZDUH ORJLVWLFV SDUW
SAP AG 2006
SAP AG

SM100
5-75
8QLW 6XPPDU\
&RQFHSW RI FURVVV\VWHP REMHFW ORFN DQG FULWLFDO REMHFW FKHFN
$XWKRUL]DWLRQ FRQFHSW RI &KDQJH 5HTXHVW 0DQDJHPHQW XVH FDVHV
SAP AG 2006
SAP AG
SM100
5-76

SAP AG
SM100
5-77
8QLW 2EMHFWLYHV
'HVFULEH WKH FDSDELOLWLHV RI FKDQJH UHTXHVW UHSRUWLQJ DQG KRZ WR FRQILJXUH FXVWRP UHSRUWV
([SODLQ WKH JHQHUDO RYHUYLHZ RI WKH FKDQJH UHTXHVW UHSRUWLQJ
SAP AG 2006
SAP AG
SM100
5-78
&KDQJH 5HTXHVW 0DQDJHPHQW 5HSRUWLQJ $VSHFWV

Change Transaction
Change Request Management Task List

CTS project Obj1 Obj2 Objm Objn
Change Request
Cycle Transaction
IMG project
CTS project
F3URMHFWV
Solution Manager Project IMG project
CTS project

SAP AG 2006
SAP AG
SM100
5-79
6HOHFWLQJ /LVW RI (YHQWV

5HVXOWV OLVW FDQ EH FRQILJXUHG DFFRUGLQJ WR WKH HQWULHV LQ WKH IROORZLQJ ILHOGV
*ULG ILHOGV
Header, Header, Project, and Task List Header, Project, Task List, and Transport Requests Header, Project, Task List, Transport Request, and Transport Objects SAP Notes and Support Packages Support Packages and Systems (plus any combination these choices)
/D\RXW +LWV
Any custom-defined layout
Maximum number of hits for the result list Default is 100 hits
4XHVWLRQV
How many hints(?), which layout, and which fields have to be selected?
SAP AG 2006
SAP AG
SM100
5-80
6HOHFWLQJ 7UDQVDFWLRQ 'DWD

7UDQVDFWLRQ GDWD LQFOXGHV DVSHFWV RI WKH F\FOH WUDQVDFWLRQ FKDQJH UHTXHVW DQG DOO FKDQJH WUDQVDFWLRQV
7UDQVDFWLRQ GDWD ILHOGV
Document identifier (number, date, transaction type, short text) External reference number Create and change dates User status and system status
2UJ8QLWV
Business partner number and function Reference object (such as IBase or product)
4XHVWLRQV
What is the status of regular and urgent corrections of a project cycle that have to be switched from the 'HYHORSPHQW ZLWK 5HOHDVH to the 7R %H 7HVWHG phase?
SAP AG 2006
SAP AG
SM100
5-81
6HOHFWLQJ 3URMHFW +HDGHU 'DWD

3URMHFW KHDGHU GDWD JURXSV WRJHWKHU SURMHFW DGPLQLVWUDWLRQ GDWD DQG WDVN OLVW GDWD
3URMHFW KHDGHU ILHOGV RI SURMHFW DGPLQLVWUDWLRQ
Project Header (ID, Type, Create, End Date) Logical Component Transport Track IMG and CTS Project
7DVN OLVW GDWD
All task lists and cycle task list Task list status and dates
4XHVWLRQV
Which change requests and change transactions exist, with which status, with how many transport requests, and which objects for a selected project?
SAP AG 2006
SAP AG
SM100
5-82
6HOHFWLQJ 6\VWHP 'DWD DQG 0DLQWHQDQFH 'DWD

6\VWHPV ZLWK FRPSRQHQWV DQG PDLQWHQDQFH YHUVLRQV FDQ EH VHOHFWHG
6\VWHP GDWD
Log. System, System Role, Component Type, Component Version
0DLQWHQDQFH GDWD
Support Packages SAP Notes and Note Corrections
4XHVWLRQV
Which component versions are available and in which systems? Which Support Packages or SAP Notes have been implemented, in which systems, and by whom?
SAP AG 2006
SAP AG
SM100
5-83
6HOHFWLQJ 7UDQVSRUW 5HTXHVWV DQG 2EMHFWV

7UDQVSRUW 5HTXHVWV ZLWK 7DVNV DQG 7UDQVSRUW 2EMHFWV
7UDQVSRUW 5HTXHVWV DQG 7UDQVSRUW 7DVNV
Transport Requests (Name, Type, Category, User, Change Date) Status
7UDQVSRUW 2EMHFWV

Object Name Package Name View Name Table Name Table Key
4XHVWLRQV
Which objects exist in which transport requests with which status and which project are they assigned to? Which systems are affected? Does a change request exist, and, if so, which status does it have?
SAP AG 2006
SAP AG
SM100
5-84
8QLW 6XPPDU\
'HVFULEH WKH FDSDELOLWLHV RI FKDQJH UHTXHVW UHSRUWLQJ DQG KRZ WR FRQILJXUH FXVWRP UHSRUWV
([SODLQ WKH JHQHUDO RYHUYLHZ RI WKH FKDQJH UHTXHVW UHSRUWLQJ
SAP AG 2006
SAP AG
SM100
5-85

SAP AG
SM100
5-86
8QLW 2EMHFWLYHV
'HSLFW WKH JHQHUDO RYHUYLHZ RI WKH &KDQJH 5HTXHVW 0DQDJHPHQW ZRUNIORZ ZLWKRXW WUDQVSRUW LQWHJUDWLRQ
'HSLFW WKH JHQHUDO RYHUYLHZ RI WKH -$9$ LQWHJUDWLRQ LQWR WKH &KDQJH 5HTXHVW 0DQDJHPHQW 3URFHVV
SAP AG 2006
SAP AG
SM100
5-87
&KDQJH 7UDQVSRUW &RQWURO ZLWK -$9$
-((
-((
7UDQVSRUW UHTXHVWV RQO\ LQFOXGH UHIHUHQFHV RI -$9$ SDFNDJHV LQWR WKH WUDQVSRUW GLUHFWRU\ 3DFNDJHV DUH ORFNHG LQ WUDQVSRUW UHTXHVWV XS WR H[SRUW RU XS WR JROLIH
SAP AG 2006
SAP AG
SM100
#
5-88
$%$3
8(88(((Q8l 42Q 85Q74( 5R85Q74l m(58
'(9
4$6 $%$3
&KDQJH 5HTXHVW 0DQDJHPHQW ZLWKRXW 7UDQVSRUW &RQWURO
Project Cycle
Cycle ID M00000061
Description TST_01
Status
Change Control
Source System TW1 000
Production System TW1 400
&KDQJH &RQWURO FDQ EH DFWLYDWHG RU GHDFWLYDWHG IRU HDFK ORJLFDO FRPSRQHQW 'HIDXOW ZLOO EH GHDFWLYH
SAP AG 2006
SAP AG
SM100
5-89
8QLW 6XPPDU\
'HSLFW WKH JHQHUDO RYHUYLHZ RI WKH &KDQJH 5HTXHVW 0DQDJHPHQW ZRUNIORZ ZLWKRXW WUDQVSRUW LQWHJUDWLRQ
'HSLFW WKH JHQHUDO RYHUYLHZ RI WKH -$9$ LQWHJUDWLRQ LQWR WKH &KDQJH 5HTXHVW 0DQDJHPHQW 3URFHVV
SAP AG 2006
SAP AG
SM100
5-90
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
6-1
2EMHFWLYHV 6\VWHP 0RQLWRULQJ
$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR 'HVFULEH WKH PDLQ PRQLWRULQJ IXQFWLRQDOLWLHV RI WKH &RPSXWHU &HQWHU 0DQDJHPHQW 6\VWHP &&06 'HFLGH ZKDW V\VWHP .3,V PD\ EH UHOHYDQW IRU V\VWHP PRQLWRULQJ LQ 6$3 V\VWHPV 'HYHORS D FRPSUHKHQVLYH PRQLWRULQJ FRQFHSW XVLQJ WKH IHDWXUHV RI WKH 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
SAP AG
SM100
6-2
6\VWHP 0RQLWRULQJ
0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU 6HWXS 6\VWHP 0RQLWRULQJ $OHUW +DQGOLQJ
SAP AG
SM100
6-3
6ROXWLRQ 0RQLWRULQJ /RQJWHUP DQG 5HDOWLPH 6ROXWLRQ 0RQLWRULQJ

&HQWUDO 6\VWHP $GPLQLVWUDWLRQ $GPLQLVWUDWLRQ RI UHJXODU WDVNV 6HUYLFH /HYHO 0DQDJHPHQW 3HULRGLF ORQJWHUP DQG FURVVV\VWHP UHSRUWLQJ LQFOXGLQJ EXVLQHVV SURFHVVHV EDVHG RQ 6$3 (DUO\:DWFK $OHUW
6\VWHP 0RQLWRULQJ 5HDOWLPH PRQLWRULQJ RI EXVLQHVV SURFHVVHV DQG V\VWHP FRPSRQHQWV EDVHG RQ WKH &&06 LQIUDVWUXFWXUH
%XVLQHVV 3URFHVV DQG ,QWHUIDFH 0RQLWRULQJ 0RQLWRULQJ IRU FRUH EXVLQHVV SURFHVVHV FRYHUV DOO WHFKQLFDO DQG EXVLQHVV DSSOLFDWLRQVSHFLILF IXQFWLRQV UHTXLUHG IRU D VPRRWK DQG UHOLDEOH IORZ RI EXVLQHVV SURFHVVHV
SAP AG 2006
This is an overview of the Solution Monitoring functionalities in the SAP Solution Manager. It offers an complete solution to monitor all relevant functions within your landscape: No matter if you have SAP or non-SAP systems!
SAP AG
SM100
6-4
3URDFWLYH 0RQLWRULQJ YV 5HDFWLYH 0RQLWRULQJ
3URDFWLYH 0RQLWRULQJ
3URDFWLYH 0RQLWRULQJ WULHV WR DYRLG FULWLFDO VLWXDWLRQV EHIRUH WKH\ RFFXU
! 7R SURFHVV WKH QHFHVVDU\ PRQLWRULQJ WDVNV ZRUN OLVWV DUH QHHGHG
5HDFWLYH 0RQLWRULQJ
5HDFWLYH 0RQLWRULQJ WULHV WR QRWLI\ WKH DGPLQLVWUDWRUV LQ FULWLFDO VLWXDWLRQV DV VRRQ DV SRVVLEOH
! (IILFLHQW QRWLILFDWLRQ PHFKDQLVPV DUH QHHGHG
SAP AG 2006
0RQLWRULQJ <RXU (QWLUH /DQGVFDSH The continually increasing number of IT solutions and components is a growing challenge for the administration team in a computer center. The number of components has increased from what was required with SAP R/3 (including SAP instances, database, hardware and operating system) to include an ever-growing range of technologies including products where SAP is a reseller and not a manufacturer. As a result of this development, computer center managers demand a monitoring method that is centralized (with all information in one tool), yet can be extended to cover new components.
Instead of classic system monitoring of individual system components, we now talk about VROXWLRQ PRQLWRULQJ, where entire business processes can be monitored as a whole across multiple components. This concept is realized through the following three monitoring sections within the SAP Solution Manager Business Process Monitoring System Monitoring Service Level Management
SAP AG
SM100
6-5
$OHUW 0RQLWRULQJ YV ([SHUW 0RQLWRULQJ
$OHUW 0RQLWRULQJ
$OHUW 0RQLWRULQJ LV XVLQJ SUHGHILQHG .H\ 3HUIRUPDQFH ,QGLFDWRUV .3, LQ RUGHU WR QRWLFH GHYLDWLRQV DV HDUO\ DV SRVVLEOH
! 'HILQLWLRQV RI .H\ 3HUIRUPDQFH ,QGLFDWRUV DQG WKHLU WKUHVKROGV DUH QHHGHG
([SHUW 0RQLWRULQJ
([SHUW 0RQLWRULQJ LV PDQXDO ZRUN
,GHQWLI\ SUREOHPV WKDW DUH EDVHG RQ ORQJUXQQLQJ WUHQGV
,GHQWLI\ LVVXHV WKDW DUH QRW FDSWXUHG YLD DOHUW PRQLWRULQJ
([SHUW 0RQLWRUV VKRXOG JLYH KLQWV IRU UHVROXWLRQ RI LGHQWLILHG SUREOHPV RU DUH WKH WRROV IRU UHVROXWLRQ RI SUREOHPV
! $GPLQLVWUDWRUV ZLWK H[SHUW NQRZOHGJH LQ GLIIHUHQW DUHDV QHHGHG
SAP AG 2006
The most difficult task in setting up a real good monitoring is to find suitable thresholds! SAP is trying to help the customers as good as they can with shipping default values and KPIs, but those still need to be adopted. This can only be defined with carefully watching the system and trying to find thresholds which are still acceptable, which means green, critical, which means turning to yellow and which are no longer acceptable RED! Expert monitoring can not be automated! This is manual work! But still, SAP is shipping a lot of trend analysis reports which help to identify potential problems.
SAP AG
SM100
6-6
0RQLWRULQJ LQ WKH 6RIWZDUH/LIHF\FOH
0RQLWRULQJ LQ GLIIHUHQW SKDVHV RI WKH VRIWZDUH OLIHF\FOH

$ GLIIHUHQW QXPEHU RI SUREOHPV RFFXU LQ GLIIHUHQW SKDVHV RI WKH VRIWZDUH OLIHF\FOH
7KH EXVLQHVV SURFHVVHV DUH FRQWLQXRXVO\ LPSURYLQJ RU FKDQJLQJ ! &RQWLQXRXV LPSURYHPHQW QRW RQO\ IRU WKH EXVLQHVV EXW DOVR IRU PRQLWRULQJ FRQFHSW DQG WKH WKUHVKROGV
7KH V\VWHP ZRUNORDG FKDQJHV ZLWK WKH EXVLQHVV
7KH GDWD YROXPH LQ WKH V\VWHP VWRUHG LV JURZLQJ FRQVWDQWO\
'LIIHUHQW WKUHVKROGV DUH UHOHYDQW LQ GLIIHUHQW SKDVHV HJ EHIRUH DQG DIWHU *RLQJ/LYH
SAP AG 2006
,QGLYLGXDOO\ &RQILJXUDEOH Threshold values, methods, detailed help, and monitor sets with monitors for all aspects of system management are predefined in the monitoring architecture and are available in every SAP system. You can also customize all settings to your own requirements and, for example, configure customerspecific monitors so that only the data about your system landscape that is relevant to your needs is displayed.
SAP AG
SM100
6-7
6HOHFWLRQ RI $OHUWV DQG &DOLEUDWLRQ RI $OHUWV

6HOHFWLRQ RI $OHUWV
:KDW DUH RQO\ ORQJ WHUP PHDVXUHV"
:KDW FDQ EHWWHU EH PRQLWRUHG PDQXDOO\ E\ H[SHUW PRQLWRULQJ"
,V WKH PRQLWRULQJ REMHFW UHOHYDQW IRU WKH DYDLODELOLW\ RI WKH V\VWHP RU WKH SHUIRUPDQFH VHFXULW\ RI WKH FRUH EXVLQHVV SURFHVV"
:KLFK DOHUWV DUH UHOHYDQW DQG ZKLFK DUH QRW UHOHYDQW IRU P\ V\VWHP ODQGVFDSH"
*RDOV RI $OHUW&DOLEUDWLRQ
6LQJOH DOHUWV VKRXOG QRW EH DFWLYDWHG WRR RIWHQ VHYHUDO WLPHV D GD\
SAP AG 2006
,Q QRUPDO RSHUDWLRQV DOO DOHUWV VKRXOG EH *5((1 DQG RQO\ DFWLYDWHG LQ H[FHSWLRQDO FDVHV
6\VWHP VSHFLILF GHILQLWLRQ RI WKUHVKROG YDOXHV
SAP AG
SM100
6-8
6\VWHP 0RQLWRULQJ
SAP AG
SM100
6-9
6HWWLQJ XS 6\VWHP 0RQLWRULQJ
SAP AG 2006
Use this section of the SAP Solution Manager to lay the foundation for setting up the correct procedures for monitoring your SAP solution. The recommended technique is to define an explicit monitoring concept for central system monitoring using the Computer Center Management System (CCMS) in conjunction with the SAP Solution Manager. This form of business process-oriented system monitoring, which starts with individual business processes and monitoring all operations-relevant system components, is known an inside-out approach. The complementary outside-in approach involves using tools from third-party manufacturers. To achieve comprehensive monitoring, SAP recommends using both approaches simultaneously.
SAP AG
SM100
w d vX Fu t g r q p j g d g m sff3hhAh3foFor%e6enXR l g rFU k hAh3ih 3fè& & m l k j g g d

6-10
&KRRVLQJ WKH 6\VWHPV IRU $FWLYDWLRQ
SAP AG 2006
$FWLYDWH 0RQLWRULQJ
3XUSRVH In this step you choose the SAP systems for which monitoring should be setup. 3URFHGXUH In the table, all systems with an SAP basis component are listed. If you want to setup monitoring for a system, flag the appropriate check box. %DFNJURXQG Since the CCMS architecture cannot handle two systems with identical SID, it is not possible to activate those systems at the same point in time.
SAP AG
SM100
6-11
&&06 &RQQHFWLYLW\ &KHFN
SAP AG 2006
&KHFN &&06 &RQQHFWLYLW\ 3XUSRVH To check the connectivity to the CCMS of the monitored systems. ,Q FDVH RI D UHG UDWLQJ SURFHHG DV IROORZV If no destinations are maintained: 1. Call transaction SMSY. 2. Choose under Systems the systems for that you want to create the RFC connections. 3. Choose Generate RFC connections in Tabstrip Clients. 4. Mark the checkbox Assign RFC Dest. for System Monitoring. 5. Save your changes. 6. After the generation of the RFC connections to all monitored systems return to this step Check CCMS connectivity and press the Refresh Button, if you did not restart the Setup System Monitoring after performing step 5.
For more detail information about CSMREG user and prerequisites for the System Monitoring see 6$3 1RWH
SAP AG
SM100
6-12
6HOHFWLQJ $OHUWV IRU 0RQLWRULQJ

8VH WKLV FKHFN WR DFWLYDWH RU GHDFWLYDWH DOHUWV GLVSOD\HG LQ WKH $OHUW *UDSKLF 6HOHFW DOO DOHUWV WKDW KDYH WR EH GLVSOD\HG LQ WKH $OHUW *UDSKLF E\ VHWWLQJ WKH
$FWLYH"
IODJ DQG SUHVV
6DYH

SAP AG 2006
Using the TID flag you can specify the thresholds for individual MTE (monitoring tree elements) objects e.g. for different hard disks.
SAP AG
SM100
6-13
6HWXS 6\VWHP 0RQLWRULQJ 3UHGHILQHG $OHUWV
SAP AG 2006
An alert must have a green checkmark status (accessible) in order to activate it. If the alert has a red or grey diamond status, they can not be activated since they are not accessible. Reason for that may be a MTE name mismatch or collectors not running in the system. On this screenshot you can see the table to change the threshold of the satellite system as described on the previous slide.
SAP AG
7 cv } | CB YCS YA { B Sy6Y23 C$IE0 YeH2R" 7 4 0 0 ( c 0 4 0v B B x B 2&zr%CS Yby 4 c v 4 &r tE6Y%3$u
B B f c 0 % y20 YeH2U" @ ' # #4 S 4 0 Ybe)r13C%2&v 4 c v 4 3v ~zC`&Ru

SM100 6-14
6HWXS 6\VWHP 0RQLWRULQJ 8VHU GHILQHG $OHUWV
SAP AG 2006
A number of predefined alerts for every system can be found in the Monitoring session. For every System, Instance, Server, Database, and other component the is the possibility to add User-defined alerts.
SAP AG
SM100
' # #4 S &%zr ePrr z6Y%XR 4 c v 4 4 @ ' B ( @ # 0 YEEC$2IYb2% 4 c 4 @ 0 H 0 4 4 0 v 5s%a &2se

6-15
)9DOXHKHOS IRU &RQWH[WV
SAP AG 2006
Select the F4 value help and select a CCMS context , which is just a specific group of CCMS nodes.
SAP AG
SM100
6-16
) KHOS IRU $OHUWV
SAP AG 2006
Any alert available in CCMS of the satellite system can be copied and monitored from Solution Manager. You may be required to do this fix pre-defined alerts that have a grey diamond status. This may be due to a MTE name difference for the alert in the Solution Manager and the satellite. In this case, you can access the CCMS on the satellite system as shown in this slide, find the needed alert and copy into the Solution Manager. Once this is done, simply activate it and save. Note that the alerts shown depend on which Context is selected, as shown in the previous slide.
SAP AG
SM100
6-17
*HW 07( 1DPH IURP 5= IRU 8VHU GHILQHG DOHUWV
SAP AG 2006
In this picture one method is shown to copy the MTE names from RZ20. Another method is, like shown in previous slides, to select first a CCMS context and then only select them from the F4-help.
SAP AG
SM100
9 f D 9 @ i ' B ( # 0 vqRFs5 s1EUdE9 `Cdqs bbR2Ir%B u f D 9 @ i ' B (

6-18
0 H x 4 04 u } 4 23vI rC2&Rhyr B w D ' 04v 4 c 0 0 @ Csg U)YYr IA9
6\VWHP 0RQLWRULQJ
SAP AG
SM100
6-19
6\VWHP 0RQLWRULQJ 6\VWHP 2YHUYLHZ
SAP AG 2006
When getting a red alert you simply have to click on the alert itself to navigate into a more detailed list of alerts, which shows exactly where the red alert comes from.
SAP AG
SM100
4 c 0 V c v b2C À9
6-20
6\VWHP 0RQLWRULQJ 5HVHW RI $OHUWV

)DGH2XW RI $OHUWV LQ &DVH RI 7HPSRUDU\ 3UREOHPV
SAP AG 2006
Sometimes you get alerts or warnings where you have already fixed the problem, but cannot restart the instance to make the changes effective, or the problems are just of a temporary nature. In such a case you can reset the alert for a certain time to only see new real alerts.
SAP AG
SM100
D 4 u UErR g
6-21
`cbbB 2&by& %i @ i 4 0v 0 B 0 H 0 # 4 c c " Ca0 sdzXr ~% RC p
6\VWHP 0RQLWRULQJ 5HVHW RI $OHUWV
SAP AG 2006
The Reset of Alerts feature allows you to ignore one or more alerts for a specified period of time. A practical use would be if you are doing a one-time workload event on the system, such as a data load, which you know would cause alerts to occur which arent really problems. You could use Reset of Alerts to define a window to ignore them.
SAP AG
SM100
savd%%F$2& 5C
6-22
6\VWHP 0RQLWRULQJ +DQGOLQJ $OHUWV
SAP AG 2006
This screen is still an overview of the alerts of your choice for this particular system, but sufficient as long as everything is green . If something turns to red you can click on the alert to navigate into a more detailed view for further analysis. With clicking on [MORE] you can open the history of alerts as shown on the next slide.
SAP AG
SM100
v&C ~ C2%%U
6-23
`CC% & d &CyCd& ~
r& tz1Xz 3% C%aCeCI
6\VWHP 0RQLWRULQJ +DQGOLQJ $OHUWV
SAP AG 2006
The confirmation of alerts does not delete this information, it is still available and accessible via the alert history in the transaction RZ20.
SAP AG
SM100
rr ts1Cz2 Y%P3e%2 rv ts
6-24
2SHQ $OHUWV $FFRUGLQJ )XQFWLRQDOLW\ LQ 5=

&OLFN WR GLVSOD\ RSHQ DOHUWV
SAP AG 2006
Clicking on open alerts shows you the thresholds, short text and number of alerts for each object to be monitored in an overview.
SAP AG
SM100
6-25
2SHQ $OHUWV $FFRUGLQJ )XQFWLRQDOLW\ LQ 5=
SAP AG 2006
Clicking on display alerts than summarizes all open alerts of all selected nodes. From here you can than complete the alerts, access the analysis tools or access the individual properties.
SAP AG
SM100
rC C e&%zb`yeihX s$ Ca3tC e
6-26
6ROXWLRQ 0RQLWRULQJ &URVV 6ROXWLRQ $OHUW /LVW

6ROXWLRQ 9DOXH
$OHUW
SAP AG 2006
The Alert Overview is new Functionality in SAP Solution Manager 4.0 It can be reached via transaction dswp | Goto | Alert Overview
SAP AG
SM100
6-27
6$3 6ROXWLRQ 0DQDJHU 3HUIRUPDQFH (VWLPDWLRQ

7KH PRVW FULWLFDO LQIOXHQFH IDFWRU LV WKH QXPEHU RI DOHUWV UHWULHYHG SHU UHIUHVK 7KH QXPEHU RI DOHUWV GHSHQGV RQ WKH QXPEHU RI PRQLWRUHG REMHFWV DQG WKH QXPEHU RI DOHUWV SHU REMHFW <RX FDQ HVWLPDWH WKH DOHUWV SHU UHIUHVK DV IROORZV
Estimate the number of 6$3 DSSOLFDWLRQ LQVWDQFHV that are included in a solution landscape. Multiply this number by . (The number of alerts per instances activated by default is 25.)
Rule of Thumb: 1RW PRUH WKDQ DOHUWV SHU UHIUHVK
Sum-up the number of alerts. This gives you the number of alerts retrieved per refresh.
Estimate the number of QRQ $%$3EDVHG LQVWDQFHV (ITS, IPC, BC, etc.) in the solution landscape. Multiply this number by . (The average number of alerts per instance activated by default is 5.)
Estimate the number of KRVWV in the solution landscape. Multiply this number by . (The number of alerts per host activated by default is 5.)
SAP AG 2006
The above calculation is a rule of thumb for one solution landscape. If there are a lot of systems to be monitored with the Solution Manager, which would exceed the 1000 alerts per refresh limit, then RZ20 in the Solution Manager should be used instead of the Alert Graphics, or a combination of the two methods could be used. There is also the option of using agent push technology, which is more efficient than the RFC pull technology. Example: 2 SAP Systems with in total 8 instances 8 x 25 = 200 3 x 5 = 15
All 8 instances installed on separate hosts 8 x 5 = 40 2 ITS instances + 1 Business Connector
WRWDO DOHUWV
SAP AG
SM100
6-28
6$3 6ROXWLRQ 0DQDJHU ,QWHJUDWLRQ 6FHQDULRV

6HQGLQJ 0RQLWRULQJ $OHUWV 9LD (0DLO
7KH 6$3 6ROXWLRQ 0DQDJHU SURYLGHV IXQFWLRQDOLW\ RI DXWRPDWLFDOO\ VHQGLQJ PRQLWRULQJ DOHUWV YLD WKH &&06 0RQLWRULQJ ,QIUDVWUXFWXUH )HDWXUHV RI $OHUW 0RQLWRULQJ
5HFHLYHU (0DLO $GGUHVV 3RVVLEOH RQ DQ\ &&06 DOHUW YLD $XWR5HDFWLRQ 0HWKRG
3UHUHTXLVLWH
(0DLO 6HQGLQJ LV FRQILJXUHG LQ 7UDQVDFWLRQ 6&27
SAP AG 2006
The used autoreaction-method is CCMS_OnAlert_Email, see also SAP note 176492.
SAP AG
SM100
5 R F q 5RFq U o d q Rs6odssF
` Ro rX hu d l w d d w e e u l ooUA 3j q U%q

6-29
d w e e u l RA 3j q R%q 3e$ ofe vfqI
t grq sotU%q e%3 feAo vs A3 n ~o
6q6e `~6 r h` i
ooAh&C%i A &f RF Ci
oir 6%fi o6 6 hIA% o tFf hAeo3 RFf
&fe$ n o2 `hCo hC
Satellite System
SAP AG

SAP AG 2006
Use Auto-reation method Serv_Desk_Mess_on_Alert for forwarding to Service Desk.
Usually messages are only send to the internal SAP Service Desk, which is part of the SAP Solution Manager. If a customer is already using a third-party support desk software, the messages from within SAP can also be forwarded to that solution!
6\VWHP 0RQLWRULQJ 6$3 6ROXWLRQ 0DQDJHU&&06 6WDQGDUG
&XVWRPHU
SM100
Solution Support
6-30
$XWR5HDFWLRQ 0HWKRG
SAP AG 2006
solman_serv_desk_mess_on_alert can automatically create a service desk message and forward the alert text to the SAP Solution Manager Service Desk using the RFC destination SLF_MSG_SUBMIT.
SAP AG
SM100
6-31
5)& 'HVWLQDWLRQ 6/)B06*B68%0,7
SAP AG 2006
To use this RFC destination you do not have to specify a target host. That way this RFC destination points to itself. The autoreaction method solman_serv_desk_mess_on_alert is than automatically using this RFC destination to send the alert information as service desk message to the Solution Manager Service Desk.
SAP AG
SM100
6-32
8QLW 6XPPDU\
<RX DUH QRZ DEOH WR 'HVFULEH WKH PDLQ PRQLWRULQJ IXQFWLRQDOLWLHV RI WKH &RPSXWHU &HQWHU 0DQDJHPHQW 6\VWHP &&06
'HYHORS D FRPSUHKHQVLYH PRQLWRULQJ FRQFHSW XVLQJ WKH IHDWXUHV RI WKH 6$3 6ROXWLRQ 0DQDJHU
'HFLGH ZKDW V\VWHP .3,V PD\ EH UHOHYDQW IRU V\VWHP PRQLWRULQJ LQ 6$3 V\VWHPV
SAP AG 2006
SAP AG
SM100
6-33
0RUH LQIRUPDWLRQ DERXW WKH &&06 PRQLWRULQJ LQIUDVWUXFWXUH VHUYLFHVDSFRPPRQLWRULQJ
&XVWRPHU WUDLQLQJV ZLWK DOO IHDWXUHV RI WKH &&06 PRQLWRULQJ LQIUDVWUXFWXUH $'0 $GYDQFHG 6$3 6\VWHP 0RQLWRULQJ $'0 $GYDQFHG 6$3 6\VWHP 0RQLWRULQJ XVLQJ &&06 ,,
SAP AG 2006
SAP AG
SM100
6-34
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV
SAP AG 2006
SAP AG
SM100
7-1
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
7-2
60 6ROXWLRQ 0DQDJHU 'LDJQRVWLFV
SAP AG
SM100
7-3
$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR 'HVFULEH WKH VWUDWHJ\ SRVVLELOLWLHV DQG IXQFWLRQDOLWLHV RI WKH 6ROXWLRQ 0DQDJHU 'LDJQRVWLFV
SAP AG 2006
SAP AG
SM100
7-4
6$3 6ROXWLRQ 0DQDJHPHQW 'LDJQRVWLFV 2EMHFWLYHV

SURYLGHV HIILFLHQW DQG VDIH URRW FDXVH DQDO\VLV RI LQFLGHQWV LQ FXVWRPHU VROXWLRQV SRZHUHG E\ 6$3 1HW:HDYHU 6\VWHP &RQILJXUDWLRQ ,VVXH $QDO\VLV 3HUIRUPDQFH RSWLPL]DWLRQ 6\VWHP DQG 3HUIRUPDQFH 0RQLWRULQJ
6L]LQJ
:RUNORDG GLVWULEXWLRQ DQG ORDG EDODQFLQJ ORDG WHVWLQJ
SAP AG 2006
A key requirement for efficient and safe support of IT solutions is the ability to perform root cause analysis with speed and efficiency. Solution Manager Diagnostics provides all functionality to centrally analyze and monitor a complete SAP NetWeaver system landscape. It also reduces the time needed to train a support consultant in root cause analysis for SAP NetWeaver.
SAP AG
SM100
7-5
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV 3RVLWLRQLQJ

62/87,21 0$1$*(5 ',$*1267,&6 SURYLGHV HIILFLHQW DQG VDIH URRW FDXVH DQDO\VLV RI LQFLGHQWV LQ FXVWRPHU VROXWLRQV SRZHUHG E\ 6$3 1HW:HDYHU
6$3 6833257 6$3 &86720(5
SAP AG 2006
A key requirement for efficient and safe support of IT solutions is the ability to perform root cause analysis with speed and efficiency. Solution Manager Diagnostics provides standardized tools for the support of customer solutions, including third-party components. Included in SAP Solution Manager, the tools enable a systematic and targeted localization of the root cause of IT problems. The centralized approach avoids that many experts have to search for possible root causes on all components involved, in most cases without success. With the possibilities of Solution Manager Diagnostics, your support organization can both save costs and accelerate the time required for problem resolution.
SAP AG
SM100
Available in one central console Standardized SAP best practices for diagnostics, integral part of SAP NetWeaver, and used by all SAP employees Uniform across components
5HGXFHG WLPH IRU URRW FDXVH DQDO\VLV
()),&,(17
1R FKDQJHV WR SURGXFWLRQ V\VWHPV

Runs in web browser and can be accessed via http connection, no native OS access necessary No access to SAP NetWeaver administration tools Enforced customer control for change management
6$)(
u d h l k f fbF
6ROXWLRQ /DQGVFDSH
7-6
ww~z }|{ `hfRvU6wd5w6hUXvf1k x e u t e s d p d m l k fd 2RrqRonbF ~} o~| h h 6jid$U$ g e d fdR$RaR2XU
hh d j j dR$R dy q2 hh d j j 2RR$ om
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV 2YHUYLHZ

6$3 6833257 6$3 &86720(5
SAP AG 2006
All tools are accessible via menu in a common GUI OS access on customer side is not necessary Installation and configuration of tools is not necessary Comparison of cluster wide settings is possible Possibility of remote load test Easy to use
SAP AG
SM100
u d h l k f fsF
d k l k $RRbF
e u t U6~$~ `hFfk e d s d p d q22$r$om
hd6jid$$R6 g h e d f$R$Ua U6~df
e d F2U l k bU e R hh d j j 2RR$ dy 5dq
efdU d l k bF e F hh d j j d$RR dy q2
7KLUG 3DUW\ 6RIWZDUH
h d 22Rt b h d j q2UR6tf$ l k sfoE
6ROXWLRQ /DQGVFDSH
7-7
%ioA~w6i 3F~rF 7 77H 2C$T ` % 3i~Aoi6 ~FXf~~e3ioA~ 7 B C`r4 o~%`riXF &X C~6~fX %o% # osaCfT cB 'H 6 wi%f o~ Xr iA two% o i%wiX~ei v B r%R" 7 770 Ce2Cf i`%e%w%ffi~ iièX w1%i~%q` i &2 ~%3i%A~ w3 ~~ 7 4 0 0 ( 4 H 0 2r $%3dC%$D c ' 0 r% Cq9 3~`%~~ w~w w$i X wA3 qw~ &F r`w r~i '4 0 2&v q V @ 9 B 7 0 D B4 H v 0 CtECCP6&4 $E$0 Y&7 Y2f9 ~i ii ~i~i~ & 3 e%iAq %ii i% 1 ~6iUeitU%~ 3 ~w~iq~r%w oi% o 7 0 D 7 B @ 9 4 B iv 0 e4 FCCts&IU" FRf %~U tbf& CE R D 0 C ' eX A % i%Rt & f ow i&F& F%wo%~tiq6~`%I iX~ Ci %~ c 3Yf9 B4 7 4 0 D B B f 0 6Y&RECC2e0Y6Hc U" h j e l e d d6d F$qe3XRF5U R q2 s h$5eF$Rd eRqf $ odR d e 20 YaC 9 ' H 0 h d 22Rt b e f~dRo 4 H 0 %3d%UD h d j q2UR6tf$ d R$Ud 'H aCfT e d fdU l k sfoE h h d6jid$RR6 g ecf 70 l k bF % ce a7 Y9 v 0 e qF e d f$R$Ua B B x &CT hh d j j d$RR Rd6F B B " &Coh dy q
6$3 6833257
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV )HDWXUHV DQG 3ULQFLSOHV
d d$RIk l k bU CCCf BB e0YeH2$" c 0
SAP AG
SAP AG 2006
SM100
6$3 &86720(5
7-8
%Rwo i2Iq Xw F f~6& V B " g r$PRC
%fèiI C 3 %R%R~beIF% ~6 oiii~w6 X wCFAF!tiR ~ X %fo6%wibf~ re~tiR % %Ri~ ti B4 7 V B " g &&23e31&da$C 6ir~rr~`&e r iCUF% ~ X wUe d ~ rX wfb XAw ~ rX wf1 oXAw V B " u x C" ICr$PRt
`d ~~iRA ri ~oeii6U ~~Ci`3e iUIR ~6~e 3 q6io% &ewo I~iq &` 3 ~ 3eioi~ Ù66w &ewoe % r25e % % ~ i~$ % RfowI~eC w ~it i# w ~A% F" U6 w6~~f ~A 04 # V B " g $T ICr$PR
U &i~ % V B " u x r$PoRo w6~~A`X wF iwwiA 3 C ~~beC d% ~3$% d%%d% d%%d% q~qU 3$%
SAP AG

SAP AG 2006
The slide shows all functionalities, which are included in the SAP Solution Manager Diagnostics.
The legend in the upper right corner shows, which technology for the according functionality is used.
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV 0RQLWRULQJ 6\VWHP
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV $UFKLWHFWXUH DQG )XQFWLRQV
SM100
7-9
6ROXWLRQ 0DQDJHU 'LDJQRVWLFV $W :RUN

/DQGVFDSH 1DYLJDWLRQ
'HWDLOHG 1DYLJDWLRQ
SAP AG 2006
The slide shows an example of a HTTP analysis, which can be used to find the root cause of a performance problem. In this example the large fraction of the Rendering Time points to a problem in the front-end (browser).
SAP AG
SM100
7-10
8QLW 6XPPDU\
<RX DUH QRZ DEOH WR 'HVFULEH WKH VWUDWHJ\ SRVVLELOLWLHV DQG IXQFWLRQDOLWLHV RI WKH 6ROXWLRQ 0DQDJHU 'LDJQRVWLFV
SAP AG 2006
SAP AG
SM100
7-11
SAP AG
SM100
7-12
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
8-1
60 (:$

(DUO\ZDWFK $OHUW 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1 DQG 'DWD &ROOHFWLRQ (DUO\:DWFK $OHUW (:$ 5HSRUWV $GGLWLRQDO )XQFWLRQDOLWLHV (DUO\:DWFK $OHUW 5HSRUWV IRU -DYD &RPSRQHQWV
SAP AG
SM100
8-2
:KDW LV WKH 6$3 (DUO\:DWFK $OHUW

:KDW LV WKH 6$3 (DUO\:DWFK $OHUW"
,PSRUWDQW V\VWHP GDWD LV WUDQVPLWWHG IURP WKH 6$3 FXVWRPHU V\VWHP WR 6$3 DW UHJXODU LQWHUYDOV YLD WKH UHPRWH FRQQHFWLRQ 7KH GDWD WUDQVIHUUHG LQFOXGHV RQO\ WHFKQLFDO GDWD ZLWK QRQ VHQVLWLYH FRQWHQW ZKLFK LV WUDQVSDUHQW DQG PDQDJHDEOH LQ WUDQVDFWLRQ 6'&&1 6$3 DQDO\]HV WKLV GDWD DQG SURYLGHV D FOHDU RYHUYLHZ RI WKH UHVXOWV LQ D UHSRUW ZKLFK FDQ EH GRZQORDGHG IURP 6$3 6ROXWLRQ 0DQDJHU .HHSLQJ WRWDO FRVW RI RZQHUVKLS ORZ DQG WKH SHUIRUPDQFH RI \RXU 6$3 VROXWLRQ KLJK LV D WUHPHQGRXV YDOXH WR \RXU EXVLQHVV D YDOXH GHOLYHUHG E\ 6$3 (DUO\:DWFK $OHUW
SAP AG 2006
SAP EarlyWatch Alert is an important part of making sure your core business processes work. It is a monitoring tool that monitors the essential administrative areas of SAP components and keeps you up to date on their performance and stability. SAP EarlyWatch Alert runs automatically to keep you informed, so you can react to issues proactively, before they become critical. SAP EarlyWatch Alert is most effective when activated for all SAP components in your solution. It is covered by your maintenance agreement with SAP so you can do so at no extra charge. The objectives of SAP EarlyWatch Alert are to: Prevent bottlenecks Identify potential problems at an early stage Provide regular and automatic monitoring of the performance of SAP components Provide regular and automatic monitoring of essential administrative areas of the SAP component Provide regular reports
SAP AG
SM100
8-3
([HFXWLYH 6XPPDU\ 6$3 (DUO\:DWFK $OHUW

7KH 6$3 (DUO\:DWFK $OHUW
3UHYHQWV ERWWOHQHFNV ,GHQWLILHV SRWHQWLDO SUREOHPV DW DQ HDUO\ VWDJH
0RQLWRUV WKH IROORZLQJ UHJXODUO\ DQG DXWRPDWLFDOO\
7KH YDOXH RI 6$3 (DUO\:DWFK $OHUW
7KH XQGHUO\LQJ FRQFHSW LV WR HQVXUH VPRRWK RSHUDWLRQ RI LQGLYLGXDO 6$3 V\VWHPV E\ NHHSLQJ \RX LQIRUPHG RI WKHLU VWDWXV DQG DOORZLQJ \RX WR WDNH DFWLRQ EHIRUH VHYHUH WHFKQLFDO SUREOHPV RFFXU
SAP AG 2006
5HGXFH 7&2 E\ NQRZLQJ ZKDW LV DIIHFWLQJ WKH SHUIRUPDQFH DQG VWDELOLW\ RI \RXU VROXWLRQ
Once activated for each component, SAP then recommends setting it to run on a weekly interval. Once the interval has been set, SAP EarlyWatch Alert runs automatically; each time producing a report. In evaluating SAP components, SAP EarlyWatch Alert monitors the following: General component status System configuration Hardware Performance development Average response times Current workload Critical error messages and process interruptions Database administration
In addition to giving you an overview of system performance, SAP EarlyWatch Alert data is an indispensable source of analytic data for the delivery of SAP Support Services, for example SAP Solution Management Assessment and SAP SQL Statement Optimization.
SAP AG
' # u v 0 B 4 B B4 ' B c E&%$" C&1CS Y%Y 6B C ' # u v 0 B '4 0v4 &Pt$" b%CE323&C@
Greatly minimize the risk of downtime
React to issues such as bottlenecks before they become critical Know what is affecting the performance and stability of your solution
SM100
8-4
1HZ 6$3 (DUO\:DWFK $OHUW 6WUDWHJ\

1HZ 6$3 (DUO\:DWFK $OHUW 6WUDWHJ\
)URP -DQXDU\ 6$3 ZLOO QR ORQJHU SURFHVV 6$3 (DUO\:DWFK $OHUW GDWD IURP ,'(6 GHPR V\VWHPV DQG GHYHORSPHQW V\VWHPV 7KH SURFHVVLQJ RI GDWD IURP WKHVH V\VWHPV PXVW EH KDQGOHG E\ 6$3 6ROXWLRQ 0DQDJHU <RX FDQ FKHFN \RXU V\VWHP W\SH LQ 6\VWHP 'DWD 0DLQWHQDQFH 4XLFN /LQN V\VWHPGDWD 3OHDVH DOVR REVHUYH WKH LQIRUPDWLRQ DERYH RQ DFWLYDWLQJ DQG GHDFWLYDWLQJ \RXU (:$V
SAP AG 2006
Due to system technical reasons, SAP strongly recommends to send SAP EarlyWatch Alert data at SAP by using Load Balancing in SAPNet-R/3 Frontend. Please check your RFC connections to SAP and ensure that they employ load balancing. To do so, follow the instructions contained in SAP Note 812386. For the SAP Solution Manager system please also refer toSAP Note 802659. Please note that the deactivation of the SAPNet R/3 Frontend on April 3, 2006 (quick link /supportapps) will have no influence on SAP EarlyWatch Alert data processing or the provision of remote services by SAP. Service connections, SAProuter connections, and RFC connections to SAP will remain unaffected. Further Information can be found on SAP Service Marketplace service.sap.com/ewa.
SAP AG
SM100
8-5
q z | z r sz| s qt e3jezwe3et qs|z y rvu ort rqp jlxpeswCo n m k i g i h g fd ljRA &e U% r| p &z r s| z| t z FAezwA&qo
|z y rvu ort rqp e{xpwelj`sCo
rs 6tl FezC5wp `~ |s ysz | vz |z |z z jetYeCj`
vwqp ewj{Aw&| rsqz y yptz rqz y ez }y
Ul`pr | | r s y r u &s ~p jxzlAw6pws r s| z q elrlr| }~
r&z F ejo |p tz s aFAje& r s v vz t p|
vwqp ewj{Aw&| rsqz y yptz rqz y ez }y `swF {%j rs qz
6DWHOOLWH 6\VWHP
0RQLWRULQJ ZLWK (DUO\:DWFK $OHUW (:$ DQG (DUO\:DWFK
&XVWRPHU
v z z | u |z z q s q r t z q q pt p z vst p s | s | jejdl ~p xttl p %w rs % q ~ wq tv A3j ~p
esll z wCo rsrt p
SAP AG

SAP AG 2006
3UHUHTXLVLWHV
The main prerequisites for using SAP EarlyWatch Alert are:
A remote connection between your SAP component and your SAP Solution Manager.
Your SAP System must be release 3.0D or higher
Implementation of SAP Note 91488.
The job SAP_COLLECTOR_FOR_PERMONITOR must be scheduled hourly. To verify this, call transaction SM37 in your system.
SM100
6$3 6XSSRUW
6$3
8-6
60 (:$

(DUO\ZDWFK $OHUW 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1 DQG 'DWD &ROOHFWLRQ (DUO\:DWFK $OHUW (:$ 5HSRUWV $GGLWLRQDO )XQFWLRQDOLWLHV (DUO\:DWFK $OHUW 5HSRUWV IRU -DYD &RPSRQHQWV
SAP AG
SM100
8-7
7KH 1HZ 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1

2YHUYLHZ 0DQDJHPHQW 6XPPDU\
%XVLQHVV 9DOXH%HQHILWV
SAP AG 2006
The new Service Data Control Center (transaction SDCCN) supersedes the old Service Data Control Center (transaction SDCC) that collected and managed performance data for analysis in SAP service sessions. The SDCCN Administration Tool allows you to build an overview of satellite systems running the Service Data Control Center that provide the SAP Solution Manager with data. You can use the SDCCN Administration tool to perform certain administration and monitoring functions on the Service Data Control Center in connected systems.
SAP AG
The Service Data Control Center (SDCC, new transaction SDCCN) supports the preparation and delivery of SAP service sessions, such as GoingLive and EarlyWatch Alert. It is intended primarily for SAP service engineers performing SAP service sessions, as well as for system administrators and other qualified customer employees working in their own SAP Solution Manager systems.
Supply multiple SAP Solution Manager systems with data. Centralized control from within one SAP Solution Manager Automate all the operations and processes needed to transfer performance data from the system(s) in which the data was collected to the system in which the data will be analyzed. Performance data can be analyzed in your SAP Solution Manager system or in a system at SAP. All the tasks performed are logged, which allows you to track the progress of each task. Data need not be collected again if usable current data is available This improves system performance. Integration with system landscape administration (transaction SMSY)
SM100
8-8
$FWLYDWLQJ WKH QHZ 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1
SAP AG 2006
Before you can work with the Service Data Control Center, it must first be activated. The Service Data Control Center will only need to be activated once after it has been installed. 3URFHGXUH You can activate the Service Data Control Center either from the SAP Solution Manager system or by using the built-in activation function in the local system. If you use the SAP Solution Manager system, you can activate the Service Data Control Center for each individual system or centrally for several systems.
SAP AG
SM100
g fd nd f f rjì&l g wi C6i&j&eg {6mjk %i nd g m m d d f d i f nd g m d i fd i 6irxml relAd d g i f d md d m j%UUlU Fqxmq3jlm

8-9
6'&&1 $FWLYDWLRQ UHVXOWV RQ WKH 6DWHOOLWH 6\VWHP
'XH WR WKH FHQWUDO DFWLYDWLRQ RI 6'&&1 \RX VKRXOG VHH D VLPLODU UHVXOW RQ WKH VDWHOOLWH V\VWHPV DV VKRZQ DERYH
SAP AG 2006
When the Service Data Control Center is activated, it performs the following actions: De-schedules AUTO_SESSION_MANAGER (ASM), the background job for the old Service Data Control Center. Checks whether Customizing settings exist If no Customizing settings exist, default values will be filled in automatically. If settings already exist, they will be left unchanged. Note that existing settings will not be overwritten. Creates the following two tasks (if they are not already available): 0DLQWHQDQFH 3DFNDJH WDVN Activates the task processor The task processor job checks whether tasks are available to be processed. To ensure the timely processing of all tasks the recommended frequency is hourly. Prompts you to create a new RFC destination (SDCC_OSS) to the SAPNet R/3 frontend (formerly called SAP OSS system). It is recommended that you set up a new RFC destination with the name SDCC_OSS. The Service Data Control Center uses this RFC destination to communicate with the SAPNet R/3 frontend. For this to work correctly, the original RFC destination SAPOSS must be working. The SAProuter string used for the SAPOSS destination will be used to set up the RFC destination SDCC_OSS. Locks the old Service Data Control Center (transaction SDCC). 6HUYLFH 3UHSDUDWLRQ &KHFN 57&&722/)
SAP AG
SM100
8-10
6HWWLQJ XS (DUO\ :DWFK $OHUW (:$
SAP AG 2006
1. You configure the SAP EarlyWatch Alert scheduling in the SAP Solution Manager. You have: scheduled the service sessions for your solution, in the SAP Solution Manager Solution Directory. The default value is 0RQGD\V You should retain this value. activated or deactivated the download of SAP EarlyWatch Alert data from the SAP Solution Data Manager for your solution systems.
2. You have activated the SAP EarlyWatch Alert monitoring for your solution systems. 3. Data collectors in the satellite systems aggregate analysis-relevant system and performance data weekly.
4. The system downloads this data to the SAP Solution Manager with the 6$3 6ROXWLRQ 'DWD 0DQDJHU (SDCCN). 5. The job SM:EXEC SERVICES triggers the processing of the data in a system session.
SAP AG
d m g 1wtrjU f d
SM100 8-11
6WDUWLQJ WKH (:$ 'DWD &ROOHFWLRQ PDQXDOO\
SAP AG 2006
*RDO You want to check the data download function when setting up SAP EarlyWatch Alert. You want to know the current status of your data, independently of the weekly reports.
SAP AG
SM100
8-12
3URFHGXUH 1. Choose the SAP EarlyWatch alert for a system. 2. You go to a screen in which the further procedure is explained. 3. Call the Service Data Control Center (transaction: SDCCN), in the relevant system, with the &DOO 6HUYLFH 'DWD &RQWURO &HQWHU pushbutton. You go to the Service Data Control Center of the selected satellite system. 4. Choose the &UHDWH 1HZ pushbutton in the Service Data Control Center. 5. Choose the 5HIUHVK 6HVVLRQV task. A dialog box appears. 6. To refresh the task immediately, choose 1RZ.
7. To schedule the task once, choose the Run 7DVN 2QFH pushbutton. 9. Confirm. You get a task number 10. Confirm. 11. Your task number appears in a row in the 7R 'R tab. 12. Select this row. 13. Choose (GLW 6WDUW 1RZ
8. Choose your Service Data Control Centre 7DUJHW 5)& 'HVWLQDWLRQ from the possible entries help.
14. Confirm. 15. You can monitor the job in the 7DVN /RJ tab. 16. Go back to the SAP Solution Manager system.
SAP AG
SM100
8-13
3URFHVVLQJ WKH (:$ 6HUYLFH LQ '6:3
SAP AG 2006
1. Refresh your data in the SAP Solution Manager. 2. Successful download is indicated by a symbol in the SAP Solution Manager overview. The alert data is then available in the SAP Solution Manager. 3. Choose the link to the SAP EarlyWatch Alert, to process your session data in the SAP Solution Manager. 4. Proceed as described. 5. You can start the background job yourself with 6WDUW 6HUYLFH 3URFHVVLQJ 5HVXOW You can see the status of the data for your systems in the SAP Solution Manager. The performance data is for the last complete week. All other data is from at least the date of the download. You can generate the SAP EarlyWatch Alert Report as an MS Word or HTML document, or display the session in SAP EarlyWatch Alert display mode.
SAP AG
SM100
nwR r Crtxqwq%j m k i g i h g fd m d d m k g i g i d d i m d g m f f leAlxmjjFxm fd xmlqj&F{l g 3 g m m i g f m md m g A %jls1w{3Fj m f nm m ljj %lm md n d f f X$3`dxij q v v z t p| z | z q le%rCdt e3jv r| r | z s q s q r p &`ss%tep ùw d di fig RwXXmk j1EA g
8-14
+DQGOLQJ (:$ 5HSRUWV
(:$ UHSRUW KDV EHHQ VHQW WR 6$3
*HQHUDWH WKH 06 :RUG 5HSRUW
2QFH WKH VHUYLFH SURFHVVLQJ KDV ILQLVKHG UXQQLQJ WKH EDFNJURXQG MRE 60(;(& 6(59,&(6 WKH (:$ UHSRUW VKRXOG VKRZ D FRORUHG UDWLQJ DQG FDQ EH UHYLHZHG
SAP AG 2006
The SAP EarlyWatch Report gives you detailed information about system status, performance, configuration, system operation, database administration and trends. You can generate an SAP EarlyWatch Alert report as: HTML document You can send the HTML report as an E-mail, to yourself and any number of other recipients ($GG 5HFLSLHQW pushbutton). You can only enter one recipient per row. MS Word document When you have generated the report, it appears as an attachment. You can send the document as an E-mail from MS Word.
SAP AG
SM100
8-15
5Ù2 FFsFdldXw$ ew$I RR$RR eU{U &Yq xY2$rd$FRtU6dxq djU2U6lddUR22R 2U$RR$F dU$RR eU{U 21ttt rxF2U6w$R`RRsFeFUj$6Rd RR$$ eU{U U6l$52FR FR6FRRRA 2RR`$Fe$qsd dRUR eU{U $2U6l$52FR 5ldFtd$R6RY152RUFd RUq eU{U
SAP AG
SAP AG 2006
3UHUHTXLVLWHV
$GGUHVV VSHFLDO FRQVLGHUDWLRQV IRU FHUWDLQ 6$3 FRPSRQHQWV IRU H[DPSOH 6$3 %: 6$3 $32 GDWDEDVH SODWIRUPV DQG 5 UHOHDVHV
)RU PRUH GHWDLOV UHIHU WR 6$3 1RWH
,PSRUWDQW 1RWHV 3OHDVH ILQG KHUH PRVW LPSRUWDQW QRWHV IRU VHUYLFH SUHSDUDWLRQ
SM100
8-16
60 (:$

(DUO\ZDWFK $OHUW &HQWUDO 6\VWHP 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1 DQG 2UGHULQJ DQG 0DQDJLQJ 6HUYLFHV 'DWD &ROOHFWLRQ 5HYLHZLQJ (DUO\:DWFK $OHUW (:$ 5HSRUWV $GGLWLRQDO )XQFWLRQDOLWLHV (DUO\:DWFK $OHUW 5HSRUWV IRU -DYD &RPSRQHQWV
$GPLQLVWUDWLRQ &6$
SAP AG
SM100
8-17
,QLWLDO 6LWXDWLRQ
7KHUH DUH VHYHUDO SRVVLELOLWLHV WR DFFHVV WKH (:$ UHSRUW
&OLFN RQ WKH 06 :RUG LFRQ WR JHQHUDWH D UHSRUW
&OLFN RQ WKH JODVVHV LQ $FWLYLWLHV WR DFFHVV WKH ZL]DUG
&OLFN RQ WKH K\SHUOLQN WR DFFHVV DQ +70/ EDVHG UHSRUW
7KH HQYHORSH VKRZV WKDW WKH (:$ UHSRUW LV DOUHDG\ VXEPLWWHG WR 6$3
SAP AG 2006
All EWA-enabled satellite systems connected to SAP Solution Manager send their EWA data to SAP once a month (every four weeks). This automatically keeps the system and software component data for your SAP systems that is stored in the SAP Support Portal (quick link /system-data) up-to-date. If the EWA data for an SAP production system is marked with a red light after evaluation, the EWA data is immediately sent to SAP for further analysis; if your alert is critical, you will then receive a call from SAP. To correctly set up SAP EarlyWatch Alerts for your SAP systems: 1. Activate the EWAs in SAP Solution Manager (see the SAP Solution Manager Configuration Guide). 2. Deactivate the EWAs at SAP (see SAP Note 207233 (section 1, point 5)).
SAP AG
SM100
8-18
$FFHVVLQJ DQ +70/ EDVHG UHSRUW
6HOHFW WKH UHSRUW W\SH ZLWK RU ZLWKRXW JUDSKLFV
SAP AG 2006
To create the report, SAP EarlyWatch Alert reads system data and analyzes it against set threshold values. Depending on the analysis, SAP EarlyWatch Alert issues a red, yellow, or green traffic light to indicate to what degree the threshold values are exceeded. The symbols are visible both in the report and as a graphic alert in the system monitoring area of the SAP Solution Manager.
SAP AG
SM100
8-19
6HQGLQJ WKH (:$ UHSRUW DV (0DLO
7KH UHSRUW FDQ DOVR EH VHQG DWWDFKHG WR DQ HPDLO WR DQ\ UHFLSLHQW
SAP AG 2006
In order to be able to send the EWA report via e-mail it is mandatory to setup SAPconnect using transaction SCOT. SAPconnect distinguishes between three different node types according to the type of connection with the SAP System: SMTP Nodes The connection between nodes of this type and the SAP System is based on the Internet mail protocol. There is one SMTP node in each client of an SAP System. This node is created automatically by the system, it cannot be deleted, and no more nodes of this type can be created. RFC Nodes The connection between nodes of this type and the SAP System is based on the SAP remote function call protocol. There can be any number of RFC nodes in each client of an SAP System. These nodes can be deleted and more nodes of this type can be created.
SAP AG
SM100
8-20
,QGHSWK DQDO\VLV RI WKH (:$ UHSRUW
&OLFN RQ WKH JODVVHV WR DFFHVV WKH ZL]DUG IRU IXUWKHU DQDO\VLV
SAP AG 2006
In evaluating SAP components, SAP EarlyWatch Alert monitors the following: General component status System configuration Hardware Performance development Average response times Current workload Critical error messages and process interruptions Database administration
SAP AG
SM100
8-21
*HQHUDWLQJ DQ (:$ 5HSRUW LQ 06 :RUG
0LFURVRIW 2IILFH - One of the following must be installed:
SAP AG 2006
In addition to these requirements, the macro security settings need to be adopted according to note 199123. If you use newer Word versions in Solution Manager (Operations) see note 489806
SAP AG
Microsoft Office 2000, Service Pack 1 (minimum requirement) or later Microsoft Office 2002 (Office XP)
SM100
8-22
6DYLQJ WKH (:$ :RUG 5HSRUW DV ORFDO ILOH

8VLQJ WKH RSWLRQ WR JHQHUDWH WKH (:$ UHSRUW DV 06 :RUG GRFXPHQW \RX FDQ VDYH DQG FROOHFW WKHVH UHSRUWV LQ \RXU ORFDO ILOH V\VWHP
SAP AG 2006
In evaluating SAP components, SAP EarlyWatch Alert monitors the following: General component status System configuration Hardware Performance development Average response times Current workload Critical error messages and process interruptions Database administration
SAP AG
SM100
8-23
6DPSOH 5HSRUW ZLWK ([SODQDWLRQ

7R KHOS \RX XQGHUVWDQG \RXU 6$3 (DUO\:DWFK $OHUW UHSRUW UHIHU WR WKH VDPSOH UHSRUW ,W LV ORFDWHG LQ WKH 6$3 6HUYLFH 0DUNHWSODFH DW ZZZVHUYLFHVDSFRPHZD 0HGLD /LEUDU\
SAP AG 2006
SAP EarlyWatch Alert will be performed at the customer site using the SAP Solution Manager; therefore it is mandatory for each customer to send the results of the SAP EarlyWatch Alert to SAP monthly. To facilitate the request of our customers, to have the SAP EarlyWatch Alert results of productive installations periodically validated by SAP, we will send a validated report back to the customer on a quarterly basis. In case of any critical alerts monitored by SAP EarlyWatch Alert the results will be send in addition to those periodical reports, to SAP. In case of vital alerts reported through SAP EarlyWatch Alert each productive installation is entitled to the max of two SAP EarlyWatch Checks performed by SAP. Additional SAP EarlyWatch Checks will be charged according to the standard price list.
SAP AG
SM100
8-24
60 (:$

(DUO\ZDWFK $OHUW &HQWUDO 6\VWHP 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1 DQG 2UGHULQJ DQG 0DQDJLQJ 6HUYLFHV 'DWD &ROOHFWLRQ 5HYLHZLQJ (DUO\:DWFK $OHUW (:$ 5HSRUWV $GGLWLRQDO )XQFWLRQDOLWLHV (DUO\:DWFK $OHUW 5HSRUWV IRU -DYD &RPSRQHQWV
$GPLQLVWUDWLRQ &6$
SAP AG
SM100
8-25
(:$ IRU -DYD

1HZ 6DWHOOLWH 6\VWHP DGGHG WR D 6ROXWLRQ /DQGVFDSH
$XWRPDWLFDOO\ VFKHGXOHG (:$ UHSRUW
Fx jXj $xFw n X1w gi f f f m d {wlj Ce6ire% nd g m
6RO0DQ
$%$3 6DWHOOLWH 6\VWHP (:$ LV SLFNHG XS E\ WKH 6'&&1 RI WKH 6DWHOOLWH 6\VWHP
SAP AG 2006
EWA for Java systems is currently in a pilot phase. It will be released with the note 976054. Note 976054 contains a setup instruction for EWA for non-ABAP-components. Technically the "Central SDCCN" of the Solution Manager is used for pure Java systems which do not have a own SDCCN. Double stack installations do not make use of the Central SDCCN, but use their local SDCCN to obtain the non-ABAP data that is collected by the Diagnostics part of the Solution Manager. When using pure java system, the data have to be send by ccms agents to an ABAP 640 system or higher. On this system the alerts will be visible within the CCMS. You then have to make both systems, the Java system and the ABAP 640 system, available in SMSY. Next you have to assign the java system as a system component which will then collect also the java data and show them in the EWA of the ABAP system. Therefore go to the main instance tab and set a java main instance to relevant and assign your java system. This is the old, available standard solution. At the moment SAP develops it also for java stand alone, which will probably be available with the new ST-SER.
SAP AG
SM100
! e$l" jA w
&&06 DJHQW GHOLYHUV GDWD IURP -DYD VWDFN WR &&06
x$wl`q 62 ' % xj4e% 30 %0I (&5 % &1 & 2 1 ) ' %
&HQWUDO 6'&&1 DFFHVV LWV RZQ &&06
,I -DYD RQO\
j ewwx %C
,I $%$3 VWDFN
,I GRXEOH 6WDFN (:$ LV SLFNHG XS E\ WKH 6'&&1 RI WKH 6DWHOOLWH 6\VWHP DQG DGGV -DYD GDWD IURP WKH DJHQW
! e%#w" j l
8-26
60 (:$

(DUO\ZDWFK $OHUW &HQWUDO 6\VWHP 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&1 DQG 2UGHULQJ DQG 0DQDJLQJ 6HUYLFHV 'DWD &ROOHFWLRQ
$GPLQLVWUDWLRQ &6$
5HYLHZLQJ (DUO\:DWFK $OHUW (:$ 5HSRUWV

(DUO\:DWFK $OHUW 5HSRUWV IRU -DYD &RPSRQHQWV $GGLWLRQDO )XQFWLRQDOLWLHV
SAP AG
SM100
8-27
&&06 0RQLWRULQJ RI (:$ $FWLYDWLRQ 7UDQVDFWLRQ '6:3 _ 2SHUDWLRQV 6HWXS _ 6ROXWLRQ 6HWWLQJV _ &&06 0RQLWRULQJ RI (:$
SAP AG 2006
6$3 6ROXWLRQ 0DQDJHU 0RQLWRULQJ This report allows you to activate monitoring for individual solutions. Monitoring objects will be created for each solution in the Solution Manager context.
&RQWHQW The following information is sent to the CCMS: Results of the EarlyWatch Alert service Results of the SL Reporting service Messages about downloads for EarlyWatch Alert services Status information about SAP Solution Manager jobs
SAP AG
SM100
8-28
8SGDWLQJ 6ROXWLRQ 0DQDJHU 7RROV ZLWK 57&&722/
SAP AG 2006
The RTCCTOOL SAP Servicetools Update is checking the availability of all tools required to perform SAP service sessions. You can start the report RTCCTOOL in transaction sa38 or from within SDCCN with creating a new task Service Preparation Check. To perform RTCCTOOL you need to have a correctly configured RFC destination SAPOSS to access sapserv3.
SAP AG
SM100
8-29
5HVXOW RI 57&&722/
SAP AG 2006
Please read the documentation on top of the result output and apply the recommendations as described there.
SAP AG
SM100
8-30
8QLW 6XPPDU\
<RX DUH QRZ DEOH WR
([SODLQ WKH 6ROXWLRQ 'LUHFWRU\
:RUN ZLWK VHUYLFHV LQ 6$3 6ROXWLRQ 0DQDJHU
*LYH DQ RYHUYLHZ RQ WKH IXQFWLRQDOLW\ RI 6$3 6ROXWLRQ 0DQDJHU LQ 2SHUDWLRQV
:RUN ZLWK WKH 6HUYLFH 'DWD &RQWURO &HQWHU 6'&&
SAP AG 2006
SAP AG
SM100
8-31
0RUH LQIRUPDWLRQ DERXW (:$ VHUYLFHVDSFRPHZD
)RU PRUH LQIRUPDWLRQ UHIHU WR WKH 6$3 6HUYLFH 0DUNHWSODFH VHUYLFHVDSFRPVROXWLRQPDQDJHU
6HOI 6WXG\ /HDUQLQJ 0DSV IRU 6$3 6ROXWLRQ 0DQDJHU VHUYLFHVDSFRPUNWVROPDQ
&OLFN 0HGLD /LEUDU\ 6DPSOH 5HSRUW ZLWK ([SODQDWLRQ
SAP AG 2006
SAP AG
SM100
8-32
$JHQGD
,QWURGXFWLRQ 6ROXWLRQ 0DQDJHU 2YHUYLHZ $GPLQLVWUDWLYH 7DVNV
6\VWHP 0RQLWRULQJ 6HUYLFH /HYHO 5HSRUWLQJ
,QVWDOODWLRQ
7HFKQLFDO &RQILJXUDWLRQ
6HUYLFH 'HVN DQG &KDQJH 0DQDJHPHQW
$SSHQGL[
SAP AG 2006
SAP AG
SM100
9-1
Bv 4 %r%&Ru
&RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
9-2
2EMHFWLYHV 6HUYLFH /HYHO 5HSRUWLQJ
$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR ([SODLQ WKH LPSRUWDQFH RI 6HUYLFH /HYHO 5HSRUWLQJ 8VH WKH 6HWXS 6HUYLFH /HYHO 5HSRUWLQJ 6HVVLRQ LQ 6$3 6ROXWLRQ 0DQDJHU 8VH WKH SRVW SURFHVVLQJ IRU 6HUYLFH /HYHO 5HSRUWV ,QFOXGH &3+ GDWD LQWR WKH 6/ 5HSRUWV 8VH WKH 6ROXWLRQ 5HSRUWLQJ
SAP AG 2006
SAP AG
SM100
9-3
6HUYLFH /HYHO 5HSRUWLQJ

$YDLODELOLW\ 5HSRUWLQJ 'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV &HQWUDO 3HUIRUPDQFH +LVWRU\ 6/5 6HWXS 6/ 5HSRUWLQJ 6HWXS 6/ 5HSRUWLQJ6HUYLFH /HYHO 5HSRUWV 3RVW 3URFHVVLQJ RI 6ROXWLRQ 5HSRUWLQJ
SAP AG
SM100
9-4
6HUYLFH /HYHO 0DQDJHPHQW 6HUYLFH /HYHO 0DQDJHPHQW

6HUYLFH /HYHO 0DQDJHPHQW PHDQV WR PHDVXUH VSHFLILF V\VWHP SDUDPHWHUV LQ DFFRUGDQFH ZLWK 6HUYLFH /HYHO $JUHHPHQWV EHWZHHQ WZR SDUWLHV RUJDQL]DWLRQDO XQLWV RU RUJDQL]DWLRQV LQYROYHG LQ WKH PDQDJHPHQW DQG RSHUDWLRQ RI D FXVWRPHUV 6$3 VROXWLRQ 7KH UHVXOWV VKRXOG EH UHSRUWHG RQ D UHJXODU EDVLV 6HUYLFH /HYHO 5HSRUWLQJ $ VXUYH\ RI WKH GLIIHUHQW SDUWLHV LQYROYHG LV QHFHVVDU\ WR HYDOXDWH SRVVLEOH FRPPXQLFDWLRQ DQG FRPSHWHQFH LVVXHV 7KH IROORZLQJ RUJDQL]DWLRQV PD\ SDUWLFLSDWH LQ D FXVWRPHU
V 6$3 SURMHFW
+DUGZDUH SDUWQHU &XVWRPHU KLPVHOI
2XWVRXUFLQJ SDUWQHU HJ IRU KDUGZDUH KRVWLQJ VXSSRUW HWF

SAP AG 2006
,PSOHPHQWDWLRQ SDUWQHU
6RIWZDUH SDUWQHU
6HUYLFH /HYHO 0DQDJHPHQW 7HDP Form an SLM team with the following members Team leader (may be one of the people mentioned below) Head of IT department Heads of each of the business departments for which service levels are to be defined (the business process owners)
,7 VWDII UHVSRQVLEOH IRU PDQDJLQJ DQG PRQLWRULQJ VHUYLFH OHYHOV 7KH WDVN RI WKH 6/0 WHDP LV WR Document the user requirements in a service level agreement (SLA) made between the Business Process Owners and the IT department Establish a regular schedule of service level reporting (SLR) for communicating ongoing levels of compliance with the SLA
SAP AG
SM100
9-5
6HUYLFH /HYHO 5HSRUWLQJ 6HUYLFH /HYHO 5HSRUWLQJ
6HUYLFH /HYHO 5HSRUWLQJ LV DQ LPSRUWDQW FRPPXQLFDWLRQ YHKLFOH EHWZHHQ WKH ,7 GHSDUWPHQW WKH XVHU FRPPXQLW\ DQG WKH OLQHV RI EXVLQHVV ,W VKRXOG EH YLHZHG DV D PHDQV IRU GHPRQVWUDWLQJ WKH YDOXH RI ,7 VHUYLFHV DQG DV D ZD\ WR SURPRWH WKH TXDOLW\ RI VHUYLFHV SURYLGHG E\ WKH ,7 GHSDUWPHQW
(Rick Sturm et al., Foundations of Service Level Management)
SAP AG 2006
The SL report is a condensed form of EarlyWatch Alert reports. Therefore, in large landscapes, the SL report accelerates and simplifies the process of finding important information. 9HULILFDWLRQ Monitor Achievement of Service Level Goals The service level agreement (SLA) provides a standard against which you can evaluate your service level reports, and thereby measure the success of your IT department in meeting its service level goals. To monitor achievement of your service level goals, check each SLR against the SLA. Schedule a meeting of the SL team the end of each quarter to evaluate the SL reports for that quarter and discuss strategy for maintaining or improving service levels.
SAP AG
SM100
9-6
([DPSOHV IRU .H\ 3HUIRUPDQFH ,QGLFDWRUV .3,V ([DPSOHV IRU .H\ 3HUIRUPDQFH ,QGLFDWRUV .3,V
%XVLQHVV .3,V
RI DOO RUGHUV SODFHG EHIRUH SP DUH GHOLYHUHG RQ WKH VDPH GD\ RI WKH WUXFNV OHDYH WKH ZDUHKRXVH EHIRUH SP
6KRXOG EH DOUHDG\ FRQVLGHUHG GXULQJ EXVLQHVV SURFHVV GHVLJQ
RI 9$ WUDQVDFWLRQV KDYH D UHVSRQVH WLPH OHVV WKDQ VHF UHTXLUHPHQW IRU WHOHVDOHV

7HFKQLFDO .3,V
&RXOG EH YHULILHG E\ WKH 6HUYLFH /HYHO 5HSRUWLQJ IXQFWLRQ RI WKH 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
'% IUHH VSDFH LV DOZD\V !
6\VWHP DYDLODELOLW\ !
H[FOXGLQJ SODQQHG GRZQWLPH RI WKH '% VL]H
One can differentiate between Business KPIs and Technical KPIs. Whereas the Business KPIs should already considered during business process design, the technical KPIs could be verified by the SL Reporting of the SAP Solution Manager.
SAP AG
SM100
9-7
6HUYLFH /HYHO 5HSRUWLQJ ZLWKLQ WKH 6ROXWLRQ 0DQDJHU 7DVN
&RPSUHKHQVLYH VHUYLFH OHYHO PDQDJHPHQW DQG UHSRUWLQJ WR DGPLQLVWUDWRUV DQG FXVWRPHUV
%HQHILWV 6XPPDUL]LQJ VHYHUDO (:$V LQ RQH UHSRUW $GGLWLRQDO GDWD WDUJHW YDOXHV DQG UDWLQJ SRVVLELOLWLHV 6XSSRUW RI VWUDWHJLF GHFLVLRQV 5HFRPPHQGDWLRQ RI RSWLPL]DWLRQV )ROORZXS RI 7DVNV
! (DVLQJ VHUYLFH OHYHO PDQDJHPHQW
SAP AG 2006
6HUYLFH /HYHO 5HSRUWLQJ Is based on EarlyWatch Alert knowledge engine Triggered regularly, for example once a week Several systems can be summarized in one automated report Is aimed at different areas of management (IT and application management) Evaluates key performance indicators (KPI) and derives recommendations like ordering standard SAP services or implementation of certain support packages and notes Generates preconfigured recommendations that can be individually tailored and extended Facilitates forecasting Is linked to relevant SAP services, such as GoingLive, SAP EarlyWatch or Solution Optimization Services
SAP AG
SM100
9-8
6HUYLFH /HYHO 5HSRUWLQJ %HQHILWV RI (:$ ,QWHJUDWLRQ $GGLWLRQDO IXQFWLRQDOLW\ UHJDUGLQJ (:$
7UDQVSRUWV REMHFWV SURJUDPV WDEOHV ! 7DE ( $YHUDJH UHVSRQVH WLPHV RI VHOIGHILQHG WUDQVDFWLRQV $JJUHJDWHG DOHUWV RXW RI %XVLQHVV 3URFHVV 0RQLWRULQJ EDFNJURXQG MRE UHSRUWLQJ SRVVLEOH 7UHQG DQDO\VLV UHJDUGLQJ
6\VWHP DFWLYLW\ 5HVSRQVH WLPH 6\VWHP RSHUDWLRQ +DUGZDUH &38 /RDG $SSOLFDWLRQ 6HUYHU DQG '% 6HUYHU
1HZV LQ 6$3 6ROXWLRQ 0DQDJHU
,QWHJUDWLRQ RI &HQWUDO 3HUIRUPDQFH +LVWRU\
SAP AG 2006
The EarlyWatch Alert (EWA) in the SAP Solution Manager has some additional functionalities compared to the standard EWA. These additional data can be integrates in the Service Level Reporting. In the SAP Solution Manager 4.0 there are some enhancements compared to previous versions. The biggest enhancement is the integration of the Central Performance History (CPH).
SAP AG
B '4 0v 4 B @ B c B j i u h 4 0v #4 0 f @ 0 ' g p 0 323rCC C31eCC dU31&2& gEY2Pser1q d B B r%C # 12P%&r3%C# PdC%s%3# 51s32RD c V i 0 B 0 H B B c @ 0 ' B 4 H 4 c @ 0 ( # 4 0
SM100 9-9
0DLQWHQDQFH RI WKUHVKROGV IRU LQGLYLGXDO .3,V 0RQWKO\ .3, 5HSRUWLQJ
4 c r @ B c4 B C3%%# 5C u d" 5 $ Y `2 5 5~ %5Y Y YY ~
7 4 0 0 ( ' # `23 d1kr%$"
7 4 0 0 q2r 2I( 04 u H %%3R%eqx B H 0 %Y q" 4 c c B 4 r tC% Y 5A9

7 4 0 e&2UD B ecr%UT
6DWHOOLWH 6\VWHPV
C6xt q~} %{ %x y | zy w v pu m p n C6nYo Cm t s r m r po n m Cqn5%C$l
dÀ | z y z z y z y ~}qXe6r~ w v pu m p n %6nYYeoCm t sr m r pon m %6nC$l
z } z z % eyr~~rr~`r~ |z | x ~ q FsU2 |z | y | rX gq &e ~y
SAP AG

SAP AG 2006
The Service Level Reporting is mainly build on information, which is coming from the EarlyWatch Alerts.
Secondly, also information from the CCMS is taken into account via the Business Processes.
0RQLWRULQJ DQG 6/ 5HSRUWLQJ 'DWD 6RXUFHV
SM100
9-10
e %~R y y zy y y %~R ` | % { | | e ~
C5 5
&XVWRPHU
e55 e `~`yz ~y % &~`g y | | z y
5 ~5eYY Y5 q%`yz y %e$ y | zyy
6HUYLFH /HYHO 0DQDJHPHQW
7 4 0 D c S f S4 `Y3U%P% rR" ' 4 7 c S f S4 EC&2%% rR"

C5 5
zy y} z y | ~2A~~~6
+HOS 'HVN
6\VWHP $GPLQLVWUDWLRQ 6WDNHKROGHUV DQG ,QWHUDFWLRQV
([SHUW 7HDPV
5 5~5 e ~U y y 6 |} y y ~U 6 x |z } y
y y U | z | re & y y U y z ~~d`yF`qCx
55
8VHU
,7 ,QIUDVWUXFWXUH
e6 6 `&
55~ `yR`6C~`yF6 z x z z
SAP AG

SAP AG 2006
System Administration is involved in Help Desk, Expert Team, and IT Infrastructure.
In general the are two involved parties in operations of an IT system, the customer (Business Process Owner) and the Solution Operation Organization. Between theses two parties a Service Level Agreement proved by Service Level Reporting should be in place.
In the Service Level Agreement the Service Goals for Help Desk and Expert Teams are defined.
The Help Desk is the first contact for the end users in case of problems. In case of problems the Expert Teams are informed to solve the problems.
SM100

9-11

'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV $YDLODELOLW\ 5HSRUWLQJ &HQWUDO 3HUIRUPDQFH +LVWRU\ 6HWXS 6/ 5HSRUWLQJ 6ROXWLRQ 5HSRUWLQJ 6/5
3RVW 3URFHVVLQJ RI 6HUYLFH /HYHO 5HSRUWV
SAP AG
SM100
9-12
:KDW LV $YDLODELOLW\" :KDW LV $YDLODELOLW\" 6RPH FXVWRPHU TXRWHV

7KH 6\VWHP LV DYDLODEOH ZKHQ WKH GDWDEDVH DQG WKH DSSOLFDWLRQ LQVWDQFH DUH XS DQG UXQQLQJ $YDLODELOLW\ LV ZKHQ , FDQ ORJRQ WR WKH V\VWHP 7KH V\VWHP LV DYDLODEOH ZKHQ , FDQ XVH LW $YDLODELOLW\ PHDQV WKDW , FDQ ZRUN DV XVXDO ! $ FRPPRQ XQGHUVWDQGLQJ RI DYDLODELOLW\ LV QHHGHG ! $ FRPPRQ XQGHUVWDQGLQJ IRU HYHU\ .3, LV QHHGHG
SAP AG 2006
Availability is selected as an example of a KPI. The contractual partners should have a common understanding of what they define in their Service Level Agreement.
SAP AG
SM100
9-13
+LJK $YDLODELOLW\ $YDLODELOLW\ 7LPHV

$YDLODELOLW \ 7LPH RI 8VDJH 'D\V
8SWLPH 'D\V 'D\V
'RZQWLPH +RXUV 0LQXWHV
SAP AG 2006
An availability of 95% means that the system is down for 18.25 days a year. An availability of 99% means that the system is down for 3.65 days a year. An availability of 99.999% means that the system is down for 5.256 minutes a year.
SAP AG
SM100
9-14
+LJK $YDLODELOLW\ &DXVHV IRU 'RZQWLPHV

8QSODQQHG 'RZQWLPHV 3ODQQHG 'RZQWLPHV
6\VWHP DQG LQIUDVWUXFWXUH PDLQWHQDQFH 3DWFKHV XSJUDGHV WUDQVSRUWV
Hardware, OS, environment failures, disaster impact to be avoided by HOLPLQDWLQJ 6LQJOH 3RLQWV RI )DLOXUH (SPOF) 80% of operator errors to be avoided by improved V\VWHP PDQDJHPHQW and with FKDQJH and SUREOHP PDQDJHPHQW SURFHVVHV
SAP AG 2006
When one talks about availability the planned downtimes should also be defined and explicitly excluded from the Service Level Agreement.
SAP AG
~ ~ q ~~ ~ è
SM100
5 ` ~

Y %&Y & 55
To be avoided with scalable components which enable rolling maintenance Improved upgrade processes Proven correction and transport system
9-15
+LJK $YDLODELOLW\ &RVWV RI 'RZQWLPHV

,QGXVWU\
)LQDQFH )LQDQFH 0HGLD 5HWDLO 5HWDLO 7UDQVSRUW
%URNHUDJH
&ULWLFDO %XVLQHVV 3URFHVV
$YHUDJH &RVWV RI +RXU 'RZQWLPH
86' 86' 86' 86' 86' 86'
&UHGLW &DUG 6DOHV $XWKRUL]DWLRQV
3D\ SHU 9LHZ 79 3D\ 79 79 +RPH 6KRSSLQJ &DWDORJ 6KRSSLQJ )OLJKW 5HVHUYDWLRQV
%XVLQHVV &RQWLQXLW\ 3ODQ

SAP AG 2006
In different industries the critical business processes might have different costs for downtimes.
SAP AG
SM100
y ~~q y z %q}x
9-16
'HWHUPLQH FULWLFDO EXVLQHVV SURFHVVHV &DOFXODWH FRVWV IRU GLIIHUHQW GXUDWLRQV RI GRZQWLPH 'HILQH WLPH WR UHFRYHU
&RVWV RI +LJK $YDLODELOLW\ 0HDVXUHV $YDLODELOLW\ &RVW &XUYH

(Source: Gartner Group)
5HGXQGDQW &RPSRQHQWV 'LVDVWHU 5HFRYHU\ 6LWH 6\VWHP 0DQDJHPHQW 7RROV ,7 6WDII &DSDFLW\ 3ODQQLQJ *XDUDQWHHG 6/$V 3URDFWLYH 6HUYLFHV
Cost
&RVWV
95% 98%
Availability
99,5%
99,9%
SAP AG 2006
High Availability is the requirement to maximize system availability from an end-users point of view. High Availability comprises much more than just a Highly Available Technical Infrastructure: Reducing planned downtimes for Backup, Updates, Patches, etc. Implement disaster recovery scenarios to minimize impacts of disasters improved Service Level Agreements!
Having a highly available Technical Infrastructure in place is crucial in order to reduce unplanned downtimes which can be caused by hardware crashes, application failures/crashes, operational mistakes, etc. From a technical infrastructure point of view, the architectural and technical single point of failures (SPOF) need to be identified and secured in an appropriate manner.
SAP AG
SM100
9-17
6\VWHP $YDLODELOLW\ 0DLQWDLQ 'HWDLOHG 7LPH 7DEOH

6HOHFW *HQHUDO 7LPH )UDPH LQ :HHN 7DEOH *HQHUDWH 7LPH 7DEOH 6HOHFW RU GHVHOHFW VSHFLILF WLPHV LQ WKH GHWDLOHG WLPH WDEOH
SAP AG 2006
Within the System Availability you have the possibility to maintain a time table which allows to define time windows where the availability is not measured. This is important since typically there are time windows for planned downtimes used for system maintenance tasks. Those time windows are than excluded from the 100% availability.
SAP AG
H G1 8 E D C $ A 9 131 31 ) '4F%5B@8 7655! 42! 0( & $ # ! '%"
SM100
9-18
$YDLODELOLW\ 0RQLWRULQJ 8VLQJ &&063,1* )HDWXUHV RI $YDLODELOLW\ 0RQLWRULQJ CCMSPING can check the availability of the application server. With this monitoring method, an application server is regarded as active, if the server is reported as active at the message server. Availability monitoring also displays the following performance attributes for monitored application servers (as of CCMSPING with release 6.20): Dialog Response Time Standardized dialog response time (as of Basis 4.5B) Number of Users Logged On
SAP AG 2006
Availability monitoring uses the alert and display functions of the monitoring architecture. However, for data collection (that is, to determine whether a remote system is active and available), availability monitoring uses the CCMS agent CCMSPING. This agent is a stand-alone program that runs outside the SAP system. By using an agent, you can efficiently monitor the availability of a large number of systems from a central location, without an inactive system causing an error in the display of the Alert Monitor. This method is extremely fast and suitable for monitoring hundreds of systems from a central CCMS Alert Monitor.
SAP AG
SM100
9-19
)XQFWLRQDO 3ULQFLSOH RI WKH $YDLODELOLW\ $JHQW )XQFWLRQDO 3ULQFLSOH RI WKH $YDLODELOLW\ $JHQW &&063,1*
e I f( '@" d $ 8 # 9 E c$ ) cba%%'`YQ E $ $ H ! # # $ q s W VU T Q I X6PSRPI
,QIRUPDWLRQ VHQW The system is available if the message server and at least one application server are available List of active application servers Underlying performance attributes of the active application server
SAP AG 2006
CCMSPING checks the availability of the application server at the message server of the corresponding system. With this monitoring method, an application server is regarded as active, if the server is reported as active at the message server. The monitoring also displays the following performance attributes for monitored application servers (as of CCMSPING with release status SAP Web AS 6.20): Dialog response time Number of users logged on Standardized dialog response time (as of SAP Basis 4.5B)
For additional information refer to the Availability Monitoring and Agent CCMSPING document at: http://service.sap.com/monitoring | Monitoring in Detail. It would make sense to install the CCMSPING Agent also on the host of the Central Monitoring System.
SAP AG
SM100
y % %~~s R |{
q | { ry % $ | } y t &~ u
&HQWUDO 0RQLWRULQJ 6\VWHP &(1
z y h g %~} phX~} i
9-20
*HQHULF 0HVVDJH DQG 5HTXHVW *HQHUDWRU *50* 3UREOHP 0RQLWRULQJ RI FRPSOH[ P\6$3 :HE 6FHQDULRV
GRMG consists of two parts, both of which are required for a functioning GRMG environment: *50* ,QIUDVWUXFWXUH The GRMG infrastructure is part of the monitoring architecture of the Computer Center Management System (CCMS). The task is to send a request (the GRMG request) to the GRMG application, to receive its response (the GRMG response) and to display this response in an Alert Monitor monitor. *50* $SSOLFDWLRQ The GRMG application performs the actual availability monitoring. From a technical point of view, this is a Java Server Page (JSP), a Servlet, or a Business Server Page in an SAP Web Application Server with a well-defined interface that is called by the GRMG infrastructure. GRMG request and GRMG response are messages in a well defined XML format.
SAP AG 2006
You can use the Generic Request and Message Generator (GRMG) to monitor the availability of technical components and entire business processes. GRMG is suitable both for technical monitoring and for application monitoring. The concept of monitoring the availability of monitored components can be describes as an agent concept. This means that the GRMG application can run separately from the components and applications that it is monitoring. This means that you can differentiate between the following situations, if an error occurs: The components monitored in the scenario are not available (component error). The scenario itself has errors, for example due to communication errors or an agent that is not running (scenario error).
SAP AG
SM100
9-21
$YDLODELOLW\ 0RQLWRULQJ 8VLQJ *50*

2YHUYLHZ RQ *50*,QIUDVWUXFWXUH
&HQWUDO 0RQLWRULQJ &RQVROH 6ROXWLRQ 0DQDJHU
6$3 :HE $6 GRMG Application 6$3 -(( (QJLQH
&&06 Request Response
GRMG Infrastructure
GRMG Application
2WKHU &RPSRQHQWV
6$3 6\VWHP GRMG Application 6$3 :HE $6

SAP AG 2006
/RFDO &&06
From a central monitoring system, you can monitor selected components of an SAP solution for their availability using GRMG, the Generic Request and Message Generator. GRMG consists of two parts: GRMG Framework (also called GRMG Infrastructure), which embedded in CCMS GRMG Application: LV D FDOODEOH MDYD DSSOLFDWLRQ ZKLFK KDV D ZHOOGHILQHG LQWHUIDFHV WR UHFHLYH *50* UHTXHVWV DQG WR VHQG *50* UHVSRQVHV *50* UHTXHVW DQG UHVSRQVH DUH VXSSOLHG LQ ;0/ GRFXPHQWV
Example: On SAP J2EE, the GRMG application is simply a .jar file which needs to be deployed. GRMG is suitable both for monitoring technical scenarios and web-based business scenarios. The GRMG availability monitoring uses the alert and display functions of the CCMS monitoring architecture to provide heartbeat information. The communication protocol used is HTTP-Post. GRMG monitoring works as follows: 1.An XML message request is sent to a target system by the GRMG infrastructure. 2. The GRMG application in the target system performs all the tests for the availability of the monitored components or business process steps. The results of these tests are collected in the GRMG application and combined into a GRMG response. 3. The GRMG response is sent back to the GRMG infrastructure and displayed in the Alert Monitor as heartbeat information there.
SAP AG
SM100
9-22
6HWXS 6/5HSRUW 6HOHFWLRQ RI $YDLODELOLW\ 7\SHV

6HOHFW GHVLUHG DYDLODELOLW\ W\SHV IRU UHSRUWLQJ
SAP AG 2006
7KH IROORZLQJ VWHSV DUH QHFHVVDU\ WR DFWLYDWH WKH &&06 3LQJEDVHG DYDLODELOLW\ UHSRUWLQJ 26 /HYHO Implement CCMS Ping agent. Download CCMAGENT.SAR from SAP Service Marketplace. Install and register agent CCMSPING on any host. &&06 Configure availability monitoring options. Activate availability types. Specify monitoring options. Specify MTE properties for Availability-MTEs. Define thresholds (optional), value smoothing, monitoring options. Activate Central Performance History (CPH) for Availability-MTEs. Define collection- and reorg. scheme. Assign Availability-MTEs to collection scheme.
SAP AG
H G1 8 E D C $ A 9 131 31 ) '4F%5B@8 7655! 42! 0( & $ # ! H G1 T Q I %%`'w5%6vSRPI
SM100
9-23
5HSRUW 2XWSXW IRU ,QGLYLGXDO 2EMHFWV K$YDLODELOLW\

6HUYLFH 5HSRUW
k i g f e d j @6'h`'s`sis ` "'
7DEOH IRUPDW RSWLRQDO
*UDSKLF IRUPDW RSWLRQDO

H G1 8 E D C $ A 9 131 31 ) 7@%bB8 6655! 7c! 0( & $ # ! H G1 T Q I '%" c%6vYPI
SAP AG 2006
$YDLODELOLW\ 7\SHV "System availability - ABAP stack" "System availability - JAVA stack" "Instance availability" "Instance logon availability" "Logon-group availability" 0HDVXUHPHQW 5HVROXWLRQ DQG $FFXUDF\ The availability information is derived from a CCMS ping agent. The highest measurement resolution is one sample per minute for system- and instance availabilities and one sample each five minutes for instance logon- and logon-group logon availabilities. In total there are 1440 or 288 availability probes per day. This results in an accuracy of approx. 0,07% or 0,35% for each day.
SAP AG
SM100
9 ! 3 "c5$ ) $ BuD 1 "c2FcH ( 3 G 8 ! H $ E H
$ d ! E $ B%@Yd 1 cP 8 A 8 G $ E y E D # 8 1 8 ! 8 %c@E 5cua`y 1 '# wxb
9-24
$YDLODELOLW\ )RUPDWV "24h-Availability" "24h-Availability, planned downtimes-adjusted" "Critical Uptime Availability" "Critical Uptime Availability, planned downtimes-adjusted" additional output: Detected downtimes, unplanned downtimes, planned downtimes 7HFKQLFDO 3UHUHTXLVLWHV CCMS ping agent running on any host CCMS Central Performance History configured to collect MTE-classes of context "Availability"
SAP AG
SM100
9-25

'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV $YDLODELOLW\ 5HSRUWLQJ &HQWUDO 3HUIRUPDQFH +LVWRU\ 6/5
6HWXS 6/ 5HSRUWLQJ 3RVW 3URFHVVLQJ RI 6HUYLFH /HYHO 5HSRUWV 6ROXWLRQ 5HSRUWLQJ
SAP AG
SM100
9-26
6/5
&3+ 6HWXS 6WHSV
&RQILJXUH &3+ RQ WKH PRQLWRULQJ V\VWHP
,GHQWLI\ 07(&ODVVHV RI WKH UHTXLUHG PRQLWRULQJ REMHFWV DQG DWWULEXWHV 2SWLRQDO &UHDWH D &3+ FROOHFWLRQ DQG UHRUJ VFKHPD $VVLJQ 07(&ODVVHV WR WKH FROOHFWLRQ DQG UHRUJ VFKHPD
&XVWRPL]H 6/56HWXS
2SWLRQDO 'HILQH RXWSXW JURXSV
,GHQWLI\ &&06SDWK RI WKH UHTXLUHG PRQLWRULQJ REMHFWV ,QVHUW WKH PRQLWRULQJ REMHFWV LQWR WKH 6/5VHWXS XVLQJ WKH &&06 SDWK 0DLQWDLQ LQGLYLGXDO DOHUW WKUHVKROGV DQG RXWSXW IRUPDWV
&3+ GDWD ZLOO EH FROOHFWHG DQG SUHIRUPDWWHG LQ WKH QH[W (:$ UXQ RI WKH VSHFLILHG VRXUFH V\VWHPV )LQDO SURFHVVLQJ RI WKH (:$ GDWD WDNHV SODFH GXULQJ QH[W 6/5 UXQ
SAP AG 2006
The new functionality is available as of Solution Manager 3.2 with the following Support Packages: Software component ST 320 - SP 11; ST 400 - SP 01 Software component ST-SER 676(5 BB 63 676(5 BB 63
Software component ST-PI (only UHOHYDQW LI Solution Manager LV XVHG DV Central Monitoring System (CEN)) 673, BB

673, BB
63 6$3 1RWH
63 6$3 1RWH
The minimum requirements for the satellite systems and CEN (if used) are described in SAP Note 905594. Minimum basis release for satellite systems with own CPH or CENs: SAP_BASIS 620 SP17 Relevant Notes: SAP Note 872569 - Central FAQ Note for setup and operation of SL-Reporting and CPH SAP Note 905594 - Description of technical prerequisites for implementation of the CPHfunctionality in the SLR SAP Note 899566 - Mandatory coding enhancements for ST-PI
SAP AG
SM100
9-27
7KUHH 0RQLWRULQJ 6FHQDULRV

d $ 8 # 9 2@"b E $ H ! G ! c2''2YQ G FD 1 6F 8 3 D
5)&
5HPRWH &3+
5)&
5)&
5HPRWH &3+ 6RO0DQ DV &(1
5)&
SAP AG 2006
In general there are three different scenarios supported to use CPH data in the Service Level Reporting: Local CPH The source system (satellite) reports its own performance data to its local CPH. The SAP Solution Manager retrieves CPH raw data directly from the satellite system. Remote CPH The source system (satellite) reports its performance data to a central monitoring system (CEN). The SAP Solution Manager retrieves CPH raw data from the CEN. The CEN doesnt need to be part of the solution landscape. The CEN can be on any of the other satellite systems of the solution landscape. Remote CPH using SAP Solution Manager as CEN The Solution Manager Systems acts additionally as CEN. The source system (satellite) reports its performance data to the SAP Solution Manager.
SAP AG
SM100
d $ 8 # 9 %b $ y E D "5F
d $ 8 # 9 '@"b $ y E D `wcFl
d $ 8 # 9 %"b $ y E D "5l
/RFDO &3+
d $ 8 # 9 V m 2x%"bnI $ 8 D d $ @2%bA
d $ 8 # 9 %"b E $ H ! G ! cc'cSQ G D 8 3 D F61 6Fb
d $ 8 # 9 %"b E $ H ! G ! c2''2YQ G FD 1 6Fl 8 3 D
9-28
3ULQFLSOH RI WKH &HQWUDO 3HUIRUPDQFH +LVWRU\ &3+
'HILQLWLRQ LQ 7UDQVDFWLRQ 5=1

6FKHGXOH SHULRGLF FROOHFWLRQ DQG DJJUHJDWLRQ MRE
0RQLWRULQJ 6HJPHQW
&3+
'HILQH ZKLFK GDWD VKRXOG EH FROOHFWHG
'HILQH KRZ ORQJ DQ DJJUHJDWH LQ D FHUWDLQ UHVROXWLRQ VKRXOG EH VWRUHG
SAP AG 2006
With the central performance history (Transaction RZ23N) it is possible to periodically collect data from the monitoring segments and put them into a central database.
SAP AG
SM100
9-29
$FWLYDWH WKH &HQWUDO 3HUIRUPDQFH +LVWRU\
$FWLYDWH WKH &HQWUDO 3HUIRUPDQFH +LVWRU\ 5=1

7ULJJHU EDFNJURXQG MREV +RZ ORQJ VKRXOG GDWD EH VWRUHG" +RZ VKRXOG GDWD EH DJJUHJDWHG" ! 'HILQH 5HRUJ 6FKHPHV :KLFK GDWD VKRXOG EH VWRUHG" ! $VVLJQ 5HRUJ 6FKHPHV WR 07( FODVVHV :KLFK GDWD VKRXOG EH SUHSDUHG H[WUDFWHG" ! 'HILQH 5=1 UHSRUW 'LVSOD\ RU H[WUDFW GDWD SHULRGLFDOO\ ! 5XQ 5=1 UHSRUW 3OXV PLQRU LPSRUWDQW DGGLWLRQDO WKLQJV
SAP AG 2006
3XUSRVH The Central Performance History (CPH) allows you to save performance values of the monitoring architecture long-term, and to output these values in reports to compare the current performance data with its earlier development. By default, performance values are only stored in the Alert Monitor for up to 24 hours, which is insufficient for many tasks, especially for the monitoring of Service Level Agreements (SLAs). You can store performance values for selected attributes of any systems in the CPH, and can freely define the storage period and granularity. The CPH should only exist on a central monitoring system (that is, the system in which the monitoring architecture is configured).
SAP AG
SM100
9-30
6/ 5HSRUWLQJ ,QWHJUDWLRQ RI &3+
$FWLYDWH GHDFWLYDWH WKH &3+ LQWHJUDWLRQ RQ WKH &KHFN *URXSV WDE 0RQLWRULQJ 2EMHFWV IURP &&06 &HQWUDO 3HUIRUPDQFH +LVWRU\
SAP AG 2006
In the Service Level Reporting, system indicators of a system can be included from the Solution Manager solution landscape, and can be documented in table and graphical format in cyclical reports. For this to happen, daily measurement readings are required for the desired indicator in the Central Performance History (CPH) of the CCMS. For more details read SAP Note 872569.
SAP AG
SM100
9-31
'HILQLWLRQ RI 0RQLWRULQJ 2EMHFWV IRU 6/5
6HOHFW REMHFW IRU UHSRUWLQJ
&KRRVH PRQLWRULQJ REMHFWV IURP )+HOS
SAP AG 2006
3XUSRVH This check enables you to include any kind of monitoring objects from the CCMS in your service level report. You can include any object that is available in either the CCMS of your Central Monitoring System (CEN) or in the CCMS of any of the SAP-based systems that are connected to this SAP Solution Manager system, or in the SAP Solution Manager system itself. You use this check to define the monitoring system and the CCMS paths of monitoring objects you want to include in your service level reporting.
SAP AG
SM100
9-32
'HILQLWLRQ RI 2XWSXW *URXSV IRU 6/5
SAP AG 2006
2XWSXW *URXS 'HILQLWLRQ
3XUSRVH This check enables you to summarize single CCMS monitoring object attributes as one common output list or graphic for the service level report. You use this check to specify an arbitrary amount of output groups and their characteristics. %DFNJURXQG For some CCMS monitoring objects it might be of interest to compare their measurement values at a common point in time to detect interrelationships. To do so, you can specify an arbitrary number of output groups and summarize up to 24 different attributes in one group. The assignment of attributes to groups can be made in the next check ("Output Group Assignment").
SAP AG
SM100
9-33
5HSRUW 2XWSXW IRU *URXSHG 2EMHFWV &XUUHQW 9DOXHV

6HUYLFH 5HSRUW
7DEOH IRUPDW RSWLRQDO
SAP AG 2006
This slide shows an example for Grouped Objects , where the single monitoring object can be compared in one table or graphic. The aggregation level is defined again on daily basis.
SAP AG
SM100
9 ! 3 lc75$ ) $ BuD 1 "2cu5H ( 3 G 8 ! H $ E H
*UDSKLF IRUPDW RSWLRQDO
$ d ! $ 1 8 A o%@E Yod cP 8 G $ E y E D # 8 1 8 ! 8 5E 5%bFay 1 '# `@
9-34
(UURU +DQGOLQJ
(UURU +DQGOLQJ IRU 6/5 &3+
6HUYLFH 5HSRUW
(UURUV GXULQJ 6/5 SURFHVVLQJ DUH LVVXHG LQ WKH ILQDO 6/5HSRUW (DFK HUURU FDUULHV DQ HUURU QXPEHU 3UREOHP GHVFULSWLRQV DQG VROXWLRQV FDQ EH ORRNHG XS LQ 6$3 1RWH
SAP AG 2006
Error No: 1 Reason: Indicator not maintained in the SLR Customizing (anymore). Solution: Maintain the corresponding attribute in the Setup SLR. Indicator is taken into account in the next SL-report.
Error No: 2 Reason: CPH was not read in the last EWA. Solution: Check whether the EWA is available for the source system. Check if the CPH reporting is activated in the SLR setup for the source system.
Error No: 3 Reason: There is no Customizing for the Evaluation of the CPH for the source system. Solution: Maintain Customizing for the source system in the Setup SLR.
Error No: 4 Reason: The requested indicator is not known in the CPH (any more). Solution: Configure indicator in the CPH.
Error No: 5 Reason: CPH does not contain any performance data for the requested indicator, or the performance data are not available in the day explosion. Solution: Check the CPH settings in the monitoring system.
SAP AG
SM100
9-35
Error No: 6 Reason: Function module is missing for the data collection. Solution: Message to SAP on component SV-SMG-MON-SLR.
Error No: 7 Reason: The Basis release of the monitoring system is lower than 6.20. Solution: Move the CPH to a monitoring system that has at least Basis 6.20.
SAP AG
SM100
9-36

'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV $YDLODELOLW\ 5HSRUWLQJ 6HWXS 6/ 5HSRUWLQJ 6ROXWLRQ 5HSRUWLQJ &HQWUDO 3HUIRUPDQFH +LVWRU\ 6/5
SAP AG
SM100
9-37
6HWXS 6HUYLFH /HYHO 5HSRUWLQJ 6HOHFW 6\VWHPV IRU 6/ 5HSRUW IURP 6ROXWLRQ /DQGVFDSH
6HOHFW 6\VWHPV IRU 6/ 5HSRUW IURP 6ROXWLRQ /DQGVFDSH
SAP AG 2006
Dependent what you create this SL Report for, you choose the systems you want to include. For each system an own sub-check is created with individual checks and alert limits for the system availability and system performance thresholds. In the next step you than choose one of the business processes as the basis for the SL report. For all single steps within the business process you have to define: Step name Transaction / Report / Query name System information Response time analysis (checkbox) Update Errors (checkbox) Query Analysis (checkbox)
When executing this report, the appropriate EWA Reports of these systems are analyzed in dependency of the SL report definition. No additional load is put on the backend systems!
SAP AG
SM100
9-38
6HWXS 6HUYLFH /HYHO 5HSRUWLQJ 6HOHFW 5HSRUW &RQWHQW IURP WKH (DUO\:DWFK $OHUW
6\VWHP &RQILJXUDWLRQ 6\VWHP $YDLODELOLW\ .H\ 3HUIRUPDQFH ,QGLFDWRUV 7UDQVDFWLRQV ZLWK WKH +LJKHVW 6\VWHP /RDG +LVWRU\ RI 5HVSRQVH 7LPHV 0D[LPXP 5HVRXUFH &RQVXPSWLRQ RI WKH +DUGZDUH $FFRXQWLQJ 3URILOH 7UHQG $QDO\VLV 'XPS 6WDWLVWLFV 8SGDWH (UURUV DQG ,QYROYHG 3URJUDPV7UDQVDFWLRQV 7UDQVDFWLRQDO 5)& (UURUV 7UDQVSRUWV
( p
SAP AG 2006
The listed chapters mainly taken from EarlyWatch Alert, therefore one can choose the chapters for the Service Level Report. If the functionality marked with * is not available follow note 540122.
SAP AG
w m & E ! & G ! 8 # t 1 r 3 31 vw2c25@u8 ss$ 52! 65! ) %XV q ! 8 D
p p p p p p p p p p p
SM100
9-39
6HWXS 6HUYLFH /HYHO 5HSRUWLQJ $GGLWLRQDO &XVWRPL]LQJ RI WKH 6/ 5HSRUWLQJ

6\VWHP $YDLODELOLW\ ZLWK GHWDLOHG WLPH WDEOH IRU DYDLODELOLW\ SODQQLQJ 6\VWHP 3HUIRUPDQFH 7KUHVKROGV $YHUDJH 'LDORJ 5HVSRQVH WLPH $YHUDJH '% 7LPH 'LDORJ 6HOHFW %XVLQHVV 3URFHVVHV IRU DQDO\VLV ZLWK 5HVSRQVH 7LPH $QDO\VLV 8SGDWH (UURUV %: 4XHU\ $QDO\VLV DQG $OHUW /LPLWV IRU 'LDORJ 7UDQVDFWLRQV 2WKHU YDOXHV SRVVLEOH LQ FRQMXQFWLRQ ZLWK %XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
Beyond the EarlyWatch Alert chapters, these three features are available in the Service Level Reporting. The fourth one is only available with the business process monitoring. Instead of selecting a business process from the Solution Directory it is also possible to add a business process definition here with steps like transactions, programs, or BW queries for analysis.
SAP AG
SM100
9-40
6HUYLFH /HYHO 5HSRUWLQJ &XVWRPL]LQJ RI .3, 7KUHVKROGV
SAP AG 2006
The possibility to customize own thresholds for some standard KPIs (System Target KPIs) is new in SAP Solution Manager 4.0. The threshold can only be set for Red alert, there is no yellow alert for this check.
SAP AG
SM100
9-41

'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV $YDLODELOLW\ 5HSRUWLQJ &HQWUDO 3HUIRUPDQFH +LVWRU\ 6HWXS 6/ 5HSRUWLQJ 6ROXWLRQ 5HSRUWLQJ 6/5
SAP AG
SM100
9-42
SAP AG 2006
Once the SL Report is defined and saved it is automatically scheduled on a weekly basis per default. Like on an EWA Report you now have the possibility to open the wizard, using the edit button, to post process the SL report result. Post processing means accessing the detailed view to analyze the problems more in detail and, if necessary, to define actions using the action list. In here you can specify who, what and when an action has to take place to fix the problem found.
SAP AG
SM100
| { 22lv uvY'sxu%c } ~ } { { { { } { | ~ } { | { z y 2'"% 5@2B%65"Rhcx
| { y b 5'"F F'"
9-43
6/ 5HSRUWLQJ 2XWSXW ([DPSOH , 7KH .H\ 3HUIRUPDQFH ,QGLFDWRUV

Active Users, Average Availability per Week, DB Request Time in Update Task, DB Size, Last month DB Growth Avg. Dialog Response Time, Avg. Database Response Time
SAP AG 2006
Based on those indicators a trend analysis can be generated, which shows trends like the database growth, performance values etc.
SAP AG
SM100
9-44
6/ 5HSRUWLQJ 2XWSXW ([DPSOH ,, 7UDQVSRUWV
7UDQVSRUWHG 7DEOHV
7UDQVSRUWHG 3URJUDPV
7UDQVSRUWHG 2EMHFWV
SAP AG 2006
As described on the previous page the import of new functionalities can be very critical regarding the system stability. Also this SL report helps you to analyze problems and to be able to see dependencies between events and problems in your system.
SAP AG
SM100
9-45
6$3 6ROXWLRQ 0DQDJHU ,QWHJUDWLRQ 6FHQDULRV 6HQGLQJ 6HUYLFH 5HSRUWV YLD (0DLO
6$3 6ROXWLRQ 0DQDJHU SURYLGHV D IXQFWLRQDOLW\ RI DXWRPDWLFDOO\ VHQGLQJ RI 6HUYLFH 5HSRUWV 7KLV LV HVSHFLDOO\ RI LQWHUHVW IRU (DUO\:DWFK $OHUW DQG 6HUYLFH /HYHO 5HSRUWV $XWRPDWLF 6HQGLQJ RI 6HUYLFH /HYHO 5HSRUWV 6HUYLFH /HYHO 5HSRUWV FDQ EH VHQW DXWRPDWLFDOO\ DIWHU JHQHUDWLRQ
)RUPDW &RPSUHVVHG +70/ &+0 5HFHLYHU /LVW RI (0DLO$GGUHVVHV 6HOHFW IURP PHQX (GLW $XWRPDWLF (0DLO 7UDQVPLVVLRQ
76%r`%R ` "'
SAP AG 2006
Instead of sending a report manually as described on the pages before, you can also send the reports automatically. The recipient list can be defined using the path specified above.
SAP AG
SM100
Xi5F
k j j i d g `ssl'g %% l"
9-46

'HVLJQ DQG $SSURYDO RI 6HUYLFH /HYHO $JUHHPHQWV $YDLODELOLW\ 5HSRUWLQJ &HQWUDO 3HUIRUPDQFH +LVWRU\ 6HWXS 6/ 5HSRUWLQJ 6/5
3RVW 3URFHVVLQJ RI 6HUYLFH /HYHO 5HSRUWV 6ROXWLRQ 5HSRUWLQJ
SAP AG
SM100
9-47
1HZ 6ROXWLRQ 5HSRUWLQJ 7DE LQ 6ROXWLRQ 0DQDJHU
1HZ UHSRUWLQJ IXQFWLRQDOLW\
6HUYLFH 5HSRUWLQJ &HQWUDO 6\VWHP $GPLQLVWUDWLRQ 5HSRUWLQJ $YDLODELOLW\ 5HSRUWLQJ 6HUYLFH 'HVN 5HSRUWLQJ &KDQJH 5HTXHVW 0DQDJHPHQW 5HSRUWLQJ ,VVXH DQG 7RS ,VVXH 5HSRUWLQJ
1HZ WDE IRU DOO VROXWLRQ UHSRUWLQJ IXQFWLRQDOLW\ H[FHSW IRU (DUO\:DWFK DQG 6HUYLFH /HYHO 5HSRUWLQJ
SAP AG 2006
The Solution Reporting functionality is new in SAP Solution Manager 4.0 and consists of the following sub-tabs: Services Administration Change Management Service Desk Issues and Top Issues
SAP AG
SM100
9-48
6ROXWLRQ 5HSRUWLQJ 7RROV

6HUYLFH 5HSRUWLQJ
6$3 (DUO\:DWFK $OHUW &RQWHQW 606< FRQWHQW 3URGXFW 'DWDEDVH &RPSRQHQWV 6\VWHP $WWULEXWHV
$GPLQLVWUDWLRQ 5HSRUWLQJ
&RQWHQW IRUP &HQWUDO 6\VWHP $GPLQLVWUDWLRQ 6HVVLRQ WDVNV 6\VWHP $YDLODELOLW\ IURP (:$ DQG PDLQWDLQHG E\ $GPLQLVWUDWRU
6HUYLFH 'HVN 0HVVDJHV
&KDQJH 0DQDJHPHQW 5HSRUWLQJ

&KDQJH 5HTXHVWV
,VVXH DQG 7RS ,VVXH 5HSRUWLQJ

,VVXHV DQG 7RS ,VVXHV
SAP AG 2006
The Solution Reporting Tools enable the user to report extensively on all relevant functionalities in the SAP Solution Manager 4.0.
SAP AG
SM100
9-49
h r % %% Pi @@i
7'ss'R @r
lu % Fu
' 4 'ps ir p'p6` @i`c
i x` c i i r @`s7`
% @s `r % ` ' ' i '
lu | } { %6@F'cl { } { ` c@cb | } { %6ww%5b { { { } { c%` c@5 | } { '4 @F%2l ~ @ 672u~ 6c%P } { F'5l2 uu P` i x ` sis ' ~ ~ { } { `c` c@cb ~ | 5%u u5 % Fu
i% ` s % ii
'h`4 0h
lu % Fu
6\VWHP
6ROXWLRQ 5HSRUWLQJ $UFKLWHFWXUH
4s% 'pu
SAP AG

SAP AG 2006
The above figure gives a detailed overview on all possible data flow in SAP Solution Manager (all functionalities marked with a thick border are new with SAP Solution Manager 4.0.
In general there are two possibilities to receive data from the satellite systems:
Collected EWA data (via SDCC)
Real-time Monitoring Data (via CCMS)
Both data can be collected and analyzed in the BI:
CCMS data has to be transferred via the Central Performance History (CPH)
The EWA data has to be transferred via the Solution Reporting functionality
6\VWHP Q
6\VWHP
&&060RQLWRULQJ,QIUDVWUXFWXUH
6ROXWLRQ 0DQDJHU 6\VWHP
SM100
,QWHJUDWHG %,
CPH-BWContent
EWA-BIContent
9-50
(:$ 5HSRUWLQJ ,Q 6$3 %XVLQHVV ,QWHOOLJHQFH %,

%HQHILWV
&XVWRPHUV ZLWK VSHFLILF UHSRUWLQJ QHHGV RU LQWHUHVW RQ KLVWRU\ DQG GHWDLOHG DQDO\VLV
6$3 (DUO\:DWFK $OHUW GDWD ZKLFK SURYLGHV D ODUJH GDWD SRRO RI .3,V DQG RWKHU LQIRUPDWLRQ DQG ZLOO FRPH WRJHWKHU ZLWK 6ROXWLRQ 0DQDJHU /DQGVFDSH 'DWD 606< LQ %, IRU PRUH WKDQ RQH V\VWHP
$YDLODELOLW\ RI GHWDLOHG LQIRUPDWLRQ DERXW V\VWHP SDUDPHWHUV DQG DSSOLFDWLRQ SDUDPHWHUV
3RVVLELOLW\ WR EXLOG RZQ UHSRUWLQJ LQ %, IRU PRUH WKDQ RQH V\VWHP IRU VHYHUDO .3,V DQG VHYHUDO WLPH LQWHUYDOV
SAP AG 2006
The data of the EarlyWatch Alert (EWA) can be forwarded to the Business Warehouse (BW), which is part of the Business Intelligence (BI) solution.
SAP AG
SM100
9-51
(:$ 'DWD ([WUDFWLRQ 6SHFLI\ 6RXUFH 6\VWHP
(:$ %, 'DWD 6HOHFWLRQ LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
The above screen for EWA data extraction can be reached via: Transaction DSWP | Operations | Solution Reporting | BI Data Collection | <Watch Symbol>. Via Maintain Parameter Set detailed settings can be made. With the help of these settings the according EWA data is put to the transparent BI transfer tables, from where the data can be collected from the BI.
SAP AG
SM100
9-52
(:$ 'DWD ([WUDFWLRQ )LOO 7UDQVIHU 7DEOHV
)LOO WUDQVSDUHQW WDEOHV IRU %, 5HSRUWLQJ
SAP AG 2006
The screen in the slide can be reached via the Maintain Parameter Set button from the previous slide. You can activate and deactivate specific EWA for transfer to the BI transfer table.
SAP AG
SM100
9-53
r 6r
w 0h 4% 2h w 6 i X 56 f $ 5 @ 1 6 `0 2is'0h { ~ ~ ~ '"22@` 6 4 r 2 6 w 4r iu2
i s i r i r c
u2 r"s% 2 r s s 4s ` " ! ul!" % r r ~ ~ y 5b
h w r h# u sb " r h iw6 s { %b
ii

r wi s l s
ui s ( & )'% 5
6s0
%2 i "$
2 3s" r
} { } { c@5
2 sF5s" iiFi 4w i" $ 4iX { 5FcY
( & )'% 7il6 71 { | ~ %5 u@@2u } } {
SAP AG
SAP AG 2006
This slide gives an overview on different KPIs, which are available in the EWA, and can therefore be transferred to the BI for further analysis.
6HOHFWHG .3,V IRU 6$3 %XVLQHVV ,QWHOOLJHQFH %, 5HSRUWLQJ
&ORVH WR .3,V ZLOO EH UHSRUWHG WR WKH %, V\VWHP
SM100
9-54
6HUYLFH 5HSRUWLQJ &RQWHQW

3HULRG 6\VWHP DQG 5HSRUWLQJ 2XWSXW VHOHFWLRQ 606< 'DWD 3URGXFW &RPSRQHQWV 'DWDEDVH DQG UHOHDVH 606< 6\VWHP $WWULEXWHV (:$ 'DWD 6\VWHP 'DWD 0RGXOHV 8VHUV 6WDWLVWLFV 1RWHV 3DUDPHWHUV 6HUYHU 'DWD +DUGZDUH &38 8WLOL]DWLRQ 0HPRU\ 8WLOL]DWLRQ 3HUIRUPDQFH 'DWD 7RS 7UDQVDFWLRQV :RUNORDG 7LPH 3URILOH 'DWDEDVH 'DWD 7RS *URZLQJ 7DEOHV '% 6L]H DQG *URZWK 2WKHU 6HUYLFHV *RLQJ/LYH 6/ 5HSRUWLQJ &HQWUDO 6\VWHP $GPLQLVWUDWLRQ
SAP AG 2006
In the Service Reporting data of Transaction SMSY and of EWA and other all services (like GoingLive, SL Reporting, etc.) can be combined.
SAP AG
SM100
9-55
6HUYLFH 5HSRUWLQJ 5HVXOWV

'HWDLOHG VHOHFWLRQ HJ FRPSDUH LPSOHPHQWHG 6$3 QRWHV DQG V\VWHP SDUDPHWHUV (:$ 9LHZHU 6HOHFWLRQ RI VHUYLFH GDWD $GG RU UHPRYH DQ\ VHUYLFH VHVVLRQ FRQWHQW
6ROXWLRQ 5HSRUWLQJ UHVXOW VFUHHQ )OH[LEOH OLVW GLVSOD\ $/9 (;&(/ GRZQ ORDG SRVVLEOH
SAP AG 2006
Perform the analysis. The analysis is presented in ALV grid format. You can adjust the layout to your requirements. If you want to save the analysis as a document in the SAP Solution Manager as a *.csv file, choose Export Table as Attachment. Go back to the initial screen. You can download the analysis to your local PC as an Excel file.
SAP AG
SM100
9-56
6HUYLFH 5HSRUWLQJ ([SRUWLQJ 5HVXOWV
([SRUW 7DEOH DV $WWDFKPHQW
SAP AG 2006
You can download the analysis to your local PC as an Excel file.
SAP AG
SM100
9-57
6XPPDU\ 6HUYLFH 5HSRUWLQJ %HQHILWV

%XVLQHVV 9DOXH%HQHILWV )OH[LEOH VHOHFWLRQ RI GDWD DOORZV WKH VXPPDU\ RI DOO UHOHYDQW VROXWLRQ V\VWHP DQG SURGXFW GDWD ZLWKLQ RQH OLVW
'RZQORDG WR 0LFURVRIW ([FHO DOORZV IDVW LQWHJUDWLRQ LQ VHOI GHILQHG 6HUYLFH /HYHO 5HSRUWV
'LVSOD\ RI VHOHFWHG GDWD LQ YDULDQWV DOORZ FOHDU LQIRUPDWLRQ IRU RWKHU XVHUV OLNH PDQDJHUV DQG VXSSRUW WHDP PHPEHUV
$OORZV ,7 DGPLQLVWUDWRUV D IDVW RYHUYLHZ UHJDUGLQJ FRPSRQHQW OHYHOV LPSOHPHQWHG QRWHV XVHUV DQG .3,V
SAP AG 2006
SAP AG
SM100
9-58
:KDW LV 6\VWHP $YDLODELOLW\ 5HSRUWLQJ"

$YDLODELOLW\ 5HSRUWLQJ OHWV \RX FUHDWH VWDQGDUGL]HG FXVWRP UHSRUWV UHJDUGLQJ WKH DYDLODELOLW\ RI VROXWLRQV DQG V\VWHPV
7KHUH LV QR DYDLODELOLW\ VROXWLRQ WR PHDVXUH WHFKQLFDO DQG IXQFWLRQDO
7KH UHVXOWV FDQ EH GLVSOD\HG LQ D OLVW YLHZ
<RX FDQ VHOHFW DQG DXWRPDWLFDOO\ LQVHUW WKH WHFKQLFDO DYDLODELOLW\ FKHFN IURP WKH 6$3 (DUO\:DWFK $OHUW VHUYLFH <RX FDQ DOVR H[SRUW WKH GDWD DQG SURFHVV LW LQ 0LFURVRIW ([FHO
7KH DYDLODELOLW\ UHSRUWLQJ VXSSRUWV \RX WR UHFRUG WKRVH DJUHHPHQWV LQ DQ HIILFLHQW ZD\
7KHUHIRUH DQ DGPLQLVWUDWRU W\SLFDOO\ KDV WR FRQWDFW LWV FXVWRPHUV WR FODULI\ WKRVH SUREOHPV
2QFH \RX KDYH FRQILJXUHG D UHSRUW \RX FDQ VDYH D YDULDQW LQ RUGHU WR UHJHQHUDWH WKH UHSRUW DW DQ\ WLPH RU UXQ LW LQ WKH EDWFK
SAP AG 2006
3UHUHTXLVLWH You have scheduled and performed at least one SAP EarlyWatch Alert, if you want to analyze the SAP EarlyWatch Alert availability data. Choose the parameters. Analysis of Analysis period Select analysis content 6\VWHP DYDLODELOLW\ IURP (DUO\:DWFK The system availability data from SAP EarlyWatch Alert is analyzed. 6\VWHP DYDLODELOLW\ PDLQWDLQHG E\ $GPLQLVWUDWRU If you want to analyze system availability data such as duration or reason for downtime, independently of the EarlyWatch Alert reports, choose (GLW 6\VWHP $YDLODELOLW\ You can add systems and maintain availability data for them.
SAP AG
SM100
9-59
6XPPDU\ 6\VWHP $YDLODELOLW\ 5HSRUWLQJ %HQHILWV

%XVLQHVV 9DOXH%HQHILWV )OH[LEOH VHOHFWLRQ RI GDWD DOORZV WKH VXPPDU\ RI DOO UHOHYDQW LQIRUPDWLRQ HJ SODQQHG GRZQWLPHV ZLWKLQ RQH OLVW
'RZQORDG WR 0LFURVRIW ([FHO DOORZV IDVW LQWHJUDWLRQ LQ VHOI GHILQHG 6HUYLFH /HYHO 5HSRUWV
6WDQGDUGL]HG GRFXPHQWDWLRQ RI DYDLODELOLW\ SUREOHPV DQG GRZQWLPHV
SAP AG 2006
SAP AG
SM100
9-60
&HQWUDO 6\VWHP $GPLQLVWUDWLRQ 5HSRUWLQJ

:LWK 6\VWHP $GPLQLVWUDWLRQ 5HSRUWLQJ \RX FDQ FUHDWH VWDQGDUGL]HG FXVWRP UHSRUWV UHJDUGLQJ WKH PDLQWHQDQFH RI 6$3 V\VWHPV 7KH UHSRUWLQJ LV EDVHG RQ WKH FHQWUDO V\VWHP DGPLQLVWUDWLRQ VHUYLFH VHVVLRQV RI \RXU VROXWLRQ 2QFH \RX KDYH FRQILJXUHG D UHSRUW \RX FDQ VDYH D YDULDQW LQ RUGHU WR UHJHQHUDWH WKH UHSRUW DW DQ\ WLPH .H\ FRQWHQW 3HULRG DQG 6\VWHP VHOHFWLRQ 6\VWHP $GPLQLVWUDWLRQ 5HSRUWLQJ 7DVNV IURP &HQWUDO 6\VWHP $GPLQLVWUDWLRQ 6HVVLRQ ZLWK DQG ZLWKRXW FRPPHQWV 'HWHUPLQH V\VWHPV DQG WLPH SHULRGV WR JHW D UHSRUW RQ WKH GHGLFDWHG /RJ%RRN HQWULHV
6\VWHP $YDLODELOLW\ 5HSRUWLQJ
0DLQWDLQHG 6\VWHP $YDLODELOLW\

SAP AG 2006
6\VWHP $YDLODELOLW\ IURP 6$3 (DUO\:DWFK $OHUW
$FWLYLWLHV Choose the transaction SOLUTION_MANAGER. Choose the 6\VWHP $GPLQLVWUDWLRQ 5HSRUWLQJ link. The report selection screen appears. Choose Solution 5HSRUWLQJ 6\VWHP $GPLQLVWUDWLRQ in 2SHUDWLRQV
Choose the parameters. Analysis of Analysis period Select analysis content
Perform the analysis. The analysis is presented in ALV grid format. You can adjust the layout to your requirements.
SAP AG
SM100
9-61
6HUYLFH 'HVN 5HSRUWLQJ 7\SLFDO 4XHVWLRQV

7\SLFDO 4XHVWLRQV WR EH DQVZHUHG E\ 6HUYLFH 'HVN 5HSRUWLQJ +RZ PDQ\ LQFLGHQWV ZHUH UHSRUWHG"
)RU D JLYHQ WLPH LQWHUYDOO SHU RUJDQL]DWLRQ SHU 6$3 FRPSRQHQW
+RZ ORQJ GLG LW WDNH WR FRPSOHWH LQFLGHQWV"

+RZ PDQ\ ZHUH VROYHG ZLWK WKH LQWHUQDO VROXWLRQ GDWDEDVH" +RZ PDQ\ ZLWK 6$3 QRWHV" +RZ PDQ\ ZLWK KHOS IURP 6$3" 2YHUDOO DQG VSHFLILF
+RZ PDQ\ ZHUH FRQYHUWHG LQWR KRZ PDQ\ FKDQJH UHTXHVWV"
:KLFK LQFLGHQWV DUH LQ SURFHVVFRPSOHWHG "

%\ VHUYLFH GHVN HPSOR\HHRUJDQL]DWLRQ
SAP AG 2006
SAP AG
SM100
9-62
&KDQJH 0DQDJHPHQW 5HSRUWLQJ 7\SLFDO 4XHVWLRQV

7\SLFDO 4XHVWLRQV WR EH DQVZHUHG E\ &KDQJH 5HTXHVW 0DQDJHPHQW 5HSRUWLQJ
:KLFK FKDQJH UHTXHVWV DUH LQ SURFHVVFRPSOHWHG " %\ VWDWXV W\SH QH[W VWHSV PDLQWHQDQFH ZLQGRZ +RZ ORQJ GR FKDQJH UHTXHVWV WDNH WR EH FRPSOHWHG" 3HU RUJDQL]DWLRQ XVHU W\SH VWHS :KLFK WUDQVSRUWV EHORQJ WR ZKLFK FKDQJH UHTXHVW DQG YLFH YHUVD" :KDW LV WKH FXUUHQW WUDQVSRUW VWDWXV LQ ZKLFK V\VWHP" +RZ PDQ\ LQFLGHQWV WULJJHUHG D FKDQJH UHTXHVW" 3HU RUJDQL]DWLRQ 6$3 FRPSRQHQW +RZ PDQ\ FKDQJH UHTXHVWV ZHUH GHFOLQHG" 3HU RUJDQL]DWLRQ XVHU W\SH E\ ZKRP DQG ZK\
SAP AG 2006
([DPSOH You want to analyze procedures for a solution and urgent corrections. You want to display procedure and project data. Choose +HDGHU DQG 3URMHFW in the /LVW RI DOO 5HVXOWV group box. Expand the 3URFHGXUH 'DWD tree and enter 6'+) in the 3URFHGXUH 7\SH field. The system checks whether there are procedures in the context of the specified solution, in which urgent corrections have been created. If so, the system shows the following information in a table: Procedure ID, Procedure description, Procedure type, Created on, System status, User status, Project name, Project type, Logical component, Project IMG, Transport path, CTS ID, Project status. Not all procedures contain data in all displayed areas. In this case, the columns are empty. You want to analyze procedures for a solution and transport request <SAPK123456>. You only want to display procedure information. Choose +HDGHU in the /LVW RI DOO 5HVXOWV group box. Expand the 7UDQVSRUW 5HTXHVWV tree, and enter the transport request in the 5HTXHVW7DVN field. The system checks whether there are procedures in the context of the specified solution, in which the transport request 6$3.! has been created. As there are no procedures in this context, the system sends the following message: Nothing found for the specified selection criteria.
SAP AG
SM100
9-63
8QLW 6XPPDU\
<RX DUH QRZ DEOH WR 'HVFULEH PDLQ IXQFWLRQDOLWLHV RI WKH 6HUYLFH /HYHO 5HSRUWLQJ 6HVVLRQ LQ 6$3 6ROXWLRQ 0DQDJHU
6HWXS WKH 6/ 5HSRUWLQJ
'HVFULEH DQG XVH WKH 6ROXWLRQ 5HSRUWLQJ SRVVLELOLWLHV LQ 6$3 6ROXWLRQ 0DQDJHU
&RPELQH 6/ 5HSRUWLQJ ZLWK IXQFWLRQDOLWLHV RI WKH &HQWUDO 3HUIRUPDQFH +LVWRU\ &3+
SAP AG 2006
SAP AG
SM100
9-64
6HOI 6WXG\ /HDUQLQJ 0DSV IRU 6$3 6ROXWLRQ 0DQDJHU VHUYLFHVDSFRPUNWVROPDQ )RU PRUH RQ &3+ DQG %, VHUYLFHVDSFRPPRQLWRQJ _ 0RQLWRULQJ LQ 'HWDLO _ ,QWHJUDWLRQ RI &3+ GDWD LQWR WKH %XVLQHVV :DUHKRXVH
0RUH LQIRUPDWLRQ WKH &3+ VHUYLFHVDSFRPPRQLWRULQJ _ 0HGLD /LEUDU\ _ 'RFXPHQWDWLRQ _ &HQWUDO 3HUIRUPDQFH +LVWRU\ RI WKH 0RQLWRULQJ $UFKLWHFWXUH
SAP AG 2006
SAP AG
SM100
9-65
SAP AG
SM100
9-66
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
10-1
2EMHFWLYHV 6HUYLFH 'HOLYHU\
$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR 'HVFULEH DQG XVH WKH &HQWUDO 6\VWHP $GPLQLVWUDWLRQ &6$ IXQFWLRQDOLW\ 2UGHU DQG PDQDJH 6$3 6HUYLFHV 'HVFULEH WKH 6LQJOH 3RLQW RI $FFHVV IXQFWLRQDOLWLHV
SAP AG 2006
SAP AG
SM100
10-2
60 6HUYLFH 'HOLYHU\

2YHUYLHZ &HQWUDO 6\VWHP $GPLQLVWUDWLRQ
2UGHULQJ DQG 0DQDJLQJ 6HUYLFHV 6LQJOH 3RLQW RI $FFHVV
SAP AG
SM100
10-3
6$3 6HUYLFH &KDQQHO
7KLV LV WKH FHQWUDO FRPPXQLFDWLRQ FKDQQHO WR 6$3 6HUYLFH DQG 6XSSRUW
SAP AG 2006
The SAP Service Channel displays all the Message Types that you have authorization to view. It is divided into the following folders, which each have different functions. ,QER[ -- The Inbox contains SAPs responses to your messages, which may require a reply from you or confirmation. The Inbox has separate folders for each Message Type. Sent Items -- Here, you will find messages that you have sent to SAP. You cannot delete individual messages. After SAP has replied, these messages will no longer be displayed in the Sent Items folder, but will appear in the Inbox. 'UDIWV -- This folder contains messages that you have not yet sent. These drafts can be finished and sent to SAP at a later stage. 2UGHU 7UDFNLQJ -- This folder shows the status of your orders: for example, order sent, order not yet sent, confirmed by SAP, successfully delivered. 6HDUFK 2SWLRQV -- The search options allow you to search for your companys messages. They are sorted according to the available Message Types. You can restrict searches for each Message Type by using different search criteria. 6HUYLFH &KDQQHO 6XEVWLWXWLRQ -- This folder does not contain messages. Here, you can maintain your own substitutes or accept requests to substitute for a colleague. Substitutes receive colleagues messages for a predefined period starting as soon as they accept a request to substitute for a colleague.
SAP AG
SM100
10-4
p t t ~ v o vt t z j l j k m t j j im | i t plm | i l zv l ~v dd yi rwwntntd |i nn%fwqn k|l % |j y qwwuj tfp nA3f yi
j t |v t k l tv l FnemYetqrm zjlvt s kpo hkm kji nfriqwd`lfCh g e fdRt 3 U% kv i 3q5t z k lv z tv m t F tn`td{t3h
vt s kpo hkm kji wudriqnnelfCh
kl w`mq {nFetCqi ey vl sl t v pt |v t v t t m 3Cwe| w
pj klzjt s simt qfi e|qnutqn3v kjt s wuwt xs
Rd6ik z v z kl s ko &vnl~q yi d6tnAfìffl } k lv z t %j e|q{An&v xy
k&ft Unh vi mt l faFAn& k l p pt m iv
pqjfi |eqnutqn3v klzjt s simt kjt s wuwt xs `ldF A kl zjt
l fqdn t fCh klkm i
SAP AG

SAP AG 2006
EWA reports are available in two report types:
HTML version
Can be set up for automatic email [ transaction SOLUTION_MANAGER, select a Solution Landscape >> Edit >> Automatic Email Transmission ]
For the graphics feature, IGS (Internet Graphics Service) must be available. Refer to SAP Notes 458731 and 454042.
Microsoft Word version
6DWHOOLWH 6\VWHP
0RQLWRULQJ ZLWK (DUO\:DWFK $OHUW (:$ DQG (DUO\:DWFK
&XVWRPHU
SM100
6$3 6XSSRUW
6$3
10-5
6$3 6ROXWLRQ 0DQDJHU 1HZ 6HUYLFH 3URFHGXUH

2OG 3URFHGXUH ZLWKRXW 6$3 6ROXWLRQ 0DQDJHU
1HZ 3URFHGXUH ZLWK 6$3 6ROXWLRQ 0DQDJHU DW FXVWRPHU VLWH
SAP AG 2006
In the past EarlyWatch Alert sessions were scheduled and triggered from SAP side. Using the SAP Solution Manager the control is moved to the customer side. Now the Solution Manager is scheduling and maintaining not just the EarlyWatch Alert sessions (EWA) but also all other service sessions. Each 4th week or in case of an red rated EWA report the session data are send automatically to SAP Active Global Support and evaluated there.
SAP AG
SM100
0 342UD 4 r%B&t9 g
10-6
`f % Cf `f % Cf B B &UT $" W
B B T B c i 0 rRaC0 bUT 0 D {&4 UR"
wqd r qC%
4 0 3RD B 4 &3A9
p g W Br%RT B BC0 csRT i0 p n`fqn$e n`fqn$e
6$3 6ROXWLRQ 0DQDJHU DV &ROODERUDWLRQ 3ODWIRUP

6$3 &XVWRPHU
6$3 &RQVXOWLQJ
SAP Service Marketplace
6ROXWLRQ /DQGVFDSH
.QRZ OHGJH ([SHUWV
$SSOLFDWLRQ 0DQDJHPHQW
6HUYLFH LQIUDVWUXFWXUH 6833257 25*$1,6$7,21 &&&
6$3 3DUWQHU
SAP AG 2006
The optimum collaboration between customers, partners, and SAP Global Service & Support is a key goal at SAP. To achieve this goal and improve support processes still further, the integration between the SAP Solution Manager and SAP Support Portal is being enhanced. SAP is continually improving the support processes and cooperation between customers, partners, and SAP Global Service & Support. The existing functionalities in CSS are being transferred to SAP Solution Manager and SAP Support Portal. The plan is to completely replace CSS, which was used by the system reseller partners and customers to process messages up to now, with the SAP Support Portal and SAP Solution Manager. Both of these have been tried and tested parts of SAPs support landscape for a long time.
SAP AG
SM100
10-7
60 6HUYLFH 'HOLYHU\

SAP AG
SM100
10-8
&HQWUDO 6\VWHP $GPLQLVWUDWLRQ

&HQWUDO 6\VWHP $GPLQLVWUDWLRQ SURYLGHV D FHQWUDO LQWHUIDFH IRU SHUIRUPLQJ D FROOHFWLRQ RI DGPLQLVWUDWLYH WDVNV WKDW DUH UHOHYDQW WR WKH GHILQHG VRIWZDUH FRPSRQHQWV 8VH WKH 6$3 6ROXWLRQ 0DQDJHU DV WKH WRRO WR SURYLGH
'ULOOGRZQ IXQFWLRQDOLW\ WR H[SHUW DGPLQLVWUDWLRQ WRROV FRYHULQJ WKH FRPSOHWH VROXWLRQ ODQGVFDSH $Q RYHUYLHZ RI UHFXUULQJ SHULRGLF DGPLQLVWUDWLRQ WDVNV
'RFXPHQWDWLRQ RI WDVNV
SAP AG 2006
Based on your defined software components, SAP Solution Manager provides a central interface to manage administrative tasks. SAP Solution Manager provides a collection of all administrative tasks that are relevant to your software components, including a detailed description of those tasks. You can schedule recurring tasks according to individual needs. Overdue tasks are displayed in the graphical portrayal of the solution landscape. You can launch the required tools directly from the SAP Solution Manager. Activities are listed after they are performed. Related results can be documented.
SAP AG
SM100
10-9
&HQWUDO 6\VWHP $GPLQLVWUDWLRQ 6HOI6HUYLFH
&OLFN WR VWDUW 6HOI6HUYLFH
SAP AG 2006
The Self Service Central System Administration helps you to define and perform administrative tasks.
SAP AG
SM100
10-10
5HDG ,QVWUXFWLRQV DQG 3HUIRUP 6HUYLFH
5HDG LQVWUXFWLRQV DQG SHUIRUP VHUYLFH
SAP AG 2006
Read the general instructions carefully and perform the checks.
SAP AG
SM100
10-11
3UHGHILQHG 3HULRGLF 7DVNV
3UHGHILQHG SHULRGLF WDVNV
SAP AG 2006
For each system defined in the Solution Manager Solution Repository, the administration tasks are predefined.
SAP AG
SM100
10-12
&RPSRQHQW6SHFLILF 7DVNV
&RPSRQHQWVSHFLILF DGPLQLVWUDWLRQ WDVNV IRU $/( &50 650 6&0 %, DQG ,76
SAP AG 2006
,QYROYHG &RPSRQHQWV
7DEOH In this table, specify the SAP component for which additional tasks will be created dynamically for the administration structure of this system. 1RWH Add one or more of the predefined SAP back-end system tasks to back-end systems. If you select Standalone Enterprise Portal Tasks, you cannot select any additional components. Standalone Enterprise Portal cannot be selected in mySAP Component systems.
SAP AG
SM100
10-13
6ROXWLRQ 0RQLWRULQJ $FFHVVLQJ WKH 7DVN /LVW
&OLFN RQ WKH LFRQ WR DFFHVV WKH WDVN OLVW
SAP AG 2006
You can see at the marked icon if there are any open tasks today. With clicking on the icon you can access the task list.
SAP AG
SM100
10-14
6ROXWLRQ 0RQLWRULQJ $FFHVVLQJ WKH 7DVN /LVW
2QO\ RSHQ WDVNV DUH GLVSOD\HG &OLFN RQ RQH RI WKH HQWULHV WR DFFHVV WKH ZL]DUG
SAP AG 2006
Now you should perform one task after another. Each task disappears, once it is done. Of course there is no real verification if you have performed the task correctly. It only checks if you have called the corresponding transaction at all, even without really analyzing something.
SAP AG
SM100
10-15
C8 70 cPe$E'P%3br bfC3C%$v Q ' 0 4 0 @ 4 i #4 B 7 cv " EB Y%$CW V B '4 0v4 u 3Y3r Cg 0 C3Ys %# % b5&C&d%p B B4 c B B @ 4 B "
SAP AG

SAP AG 2006
You can customize the frequency of the predefined administration tasks
,QIR Please check note 879319 if you get a short dump when calling the analysis transaction.
+DQGOLQJ 7DVNV
SM100
10-16
' c 04 v 0 4 2Y$e065C% ec{%Bb@Cs{ ' I20 0 bCsd0 B H ' 0 V 0 7 c B B H V 0 EePr3&Cr%bCsd0 0 0 7 c 4 0 @ 4 B H # `cC Y%' 30 E 2%&1 c B B 0 H B 7 7 c V4 0 i V B #
SAP AG
SAP AG 2006
Using the task log book an operator can log the problems he has found. This way you have a complete documentation of the tasks performed dependent on the configured frequency.
7DVN /RJ %RRN
SM100
10-17
&KHFN 8VHU 'HILQHG 7DVNV 0DVWHU

'HILQH LQ *URXSV RI 7DVNV 'HVFULSWLRQ $FWLRQ DQG $FWLRQ 7\SH 'HILQH LQ 8VHU 7DVNV 7DVN GHVFULSWLRQ DQG 7DVN *URXS *R WR WKH V\VWHP FKHFN 6HOHFW WDE 8VHU 'HILQHV 7DVN DQG VHOHFW GHILQLWLRQV IURP WKH OLVW 7DVN *URXS DSSHDUV LQ WKH 8VHU 'HILQHG 7DVN *URXS

SAP AG 2006
1.) + 2.) Select the check User Defined Task Master and complete required information under the two tabs, for example: Group Description Action Action Type Performance ST03N Transaction
Tasks in the Task Master are now available for the individual system. y2) Go to the top level of the system listed in the tree: Select the tab User Defined Tasks and enter a task from the Task Master using the pull-down menu. y3) Go to the bottom of the System tree to the check called User Defined Task Group to find your task(s).
SAP AG
SM100
10-18
&KHFN 7DVNV 9LHZ 0DVWHU

*LYH \RXU YLHZ D QDPH LQ 7DE /RJLFDO 8VHU 9LHZ 1DPHV 6HOHFW WKH WDVN W\SHV \RX ZDQW WR VHH LQ \RXU XVHU YLHZ LQ 7DE 8VHU 9LHZV *R WR &KHFN &KRRVH $GPLQLVWUDWLRQ DQG 0RQLWRULQJ :RUNDUHD DQG &KRRVH \RXU XVHU YLHZ

SAP AG 2006
Using the task view master an operator is able to specify his or her own selection of tasks shown in the wizard. Select the tab User Views. There are 9 user views reserved where you can assign the task types you want to display in the Administration Structure by using the dedicated view (e.g. Monthly Performed Tasks, Yearly Open Tasks and so on). After maintaining your user defined views, you can define logical names for these views on the tab Logical User View Names. If you do not define logical names, then the standard names are used automatically, for example, User View 1, User View 2. To select the different views (SAP Standard Views or User Defined Views) and to display the assigned tasks of them, go to check Choose Administration and Monitoring Workarea.
SAP AG
SM100
10-19
&RPSOHWH 6HVVLRQ DQG /HDYH
&RPSOHWH DOO RSHQ WDVNV DQG OHDYH
SAP AG 2006
For each system, you can define the administrative tasks and their frequency.
SAP AG
SM100
10-20
7DVN /RJ %RRN *HQHUDWH 5HSRUW
5HSRUWV FDQ EH JHQHUDWHG DV +70/ RU :RUG 5HSRUWV
SAP AG 2006
At the end of a week or month one can generate a HTML or MS Word report to proof the fulfilment of the tasks to the customer. You can choose 2 different kinds of report: 7DVN /RJ +LVWRU\ A complete list of all tasks performed inclusive the comments and the action list is shown. 7DVN 6HVVLRQ 5HSRUW: The configuration of the Central System Administration is shown in a report.
SAP AG
SM100
10-21
3DUDOOHO 0DLQWHQDQFH
*UDSKLFDO 'LVSOD\ RI 2SHQ 7DVNV
3DUDOOHO 0DLQWHQDQFH RI 6\VWHPV
SAP AG 2006
Refer to the section Roles for Session Types in the Solution Manager Configuration Guide for information on how to prevent unwanted configuration changes in a CSA session.
SAP AG
SM100
10-22
60 6HUYLFH 'HOLYHU\

SAP AG
SM100
10-23
,VVXH 0DQDJHPHQW LQ 6$3 6ROXWLRQ 0DQDJHU

7RS ,VVXHV GHVFULEH SUREOHPV LQ \RXU VROXWLRQ ODQGVFDSH IURP D PDQDJHPHQW SRLQW RI YLHZ WKH\ FDQ SRLQW WR FRUUHVSRQGLQJ LVVXHV ,VVXHV DUH WHFKQLFDO RU DGPLQLVWUDWLYH SUREOHPV LQ \RXU VROXWLRQ ODQGVFDSH WKDW DUH WRR FRPSOH[ IRU VLPSOH SUREOHP PHVVDJHV
$VVLJQ 7DVNV
&UHDWH ,VVXH
&UHDWH 6HUYLFHV
5HSRUWLQJ
6HQG 7RS ,VVXH WR 6$3

SAP AG 2006
,VVXH WUDFNLQJ is an interface between your support organization and SAP support. SAP support staff can coordinate the cooperation between you and SAP support, with this function, for example by proposing solutions for problems. With this function, you can monitor LVVXHV and top LVVXHV which have been identified in a business process or solution during production processing, and must be resolved. You can trace the entire lifecycle of your LVVXHV and their solutions.
SAP AG
SM100
10-24
,VVXH 7UDFNLQJ 7RS ,VVXH 'HWDLOV
$VVLJQ WDVNV WR LQWHUQDO HPSOR\HHV
$VVLJQ LVVXHV DQG VHOI VHUYLFHV
6HQG 7RS ,VVXHV WR 6$3
SAP AG 2006
3URFHVV )ORZ 1. You or SAP Support identify a problem in your solution which requires action (issue). 2. You or SAP Support create a new issue from a service, in the SAP Solution Manager Issue Tracking. The SAP Support enters a recommendation to SAP Support Services. 3. You contact SAP, and request a Support Service which solves it. The link between the issue and service is retained. 4. SAP support or the support team perform the service for your solution landscape at your site, or remotely. 5. While performing the service, SAP Support updates the problem information in the Issue Tracking. 6. You can analyze open issues. 7. Implement the recommendations for the problems. 8. Update the issue status in the SAP Solution Manager, and close it.
5HVXOW You can trace the entire lifecycle of a (top) issue, and all activities connected with it.
SAP AG
SM100
10-25
6HUYLFH 3ODQ
5HSOLFDWLRQ RI 6HUYLFH 3ODQ IURP 6$3 $FWLYH *OREDO 6XSSRUW LQWR FXVWRPHU 6$3 6ROXWLRQ 0DQDJHU 3ODQQLQJ EDVHG RQ 6HUYLFH 3ODQ
3ODQQHG 6HUYLFHV
5HODWHG LVVXHV
SAP AG 2006
The Service Plan functionality allows you to use the services to support your production processing. You can order services directly from the SAP Service Catalog. You can create your own services locally, to your requirements. The session details let you save session context information, assign service sessions directly to solutions and projects, and display documents
SAP AG
SM100
10-26
([SHUWLVH RQ 'HPDQG (R'

([SHUWLVH RQ 'HPDQG (R' LV RQO\ DYDLODEOH ZLWK 6$3 0D[$WWHQWLRQ 0RUH LQIRUPDWLRQ DYDLODEOH DW KWWSVHUYLFHVDSFRPHRG
$Q 6$3 ([SHUW FDQ EH UHTXHVWHG IRU DQ\ LVVXH
SAP AG 2006
You want to request an SAP expert, with an ([SHUWLVH RQ 'HPDQG message. An Expertise on Demand (EoD) request is an OSS message in the component ;;B5&B(2'B 3UHUHTXLVLWHV You have: A &RQWLQJHQW &RQWUDFW 1XPEHU for the Expertise on Demand (EoD) request. Created an issue.
The Expertise on Demand message number and the status appear in the issue list. You can: close the message with &RQILUP. trace the further message processing in expert mode, with 5HIUHVK. If SAP returns the message to you, you can answer it and return it to SAP.
SAP AG
SM100
10-27
6HUYLFH 2UGHU
&UHDWH /RFDO 6HUYLFH
2UGHU D 6HUYLFH YLD 6HUYLFH 0DUNHWSODFH
&UHDWH /RFDO 6HUYLFH HJ 6HOI6HUYLFH
&ROODERUDWLRQ ZLWK 6$3 6XSSRUW
SAP AG 2006
You want to order a Remote or Onsite Service from SAP. 3UHUHTXLVLWHV You have: created a solution. set-up a connection to the SAP Service Marketplace (Explorer)
3URFHGXUH
Choose the transaction 62/87,21B0$1$*(5
Choose 2UGHU 6HUYLFH IURP 6$3 You go to the Service Catalog. Choose the link to the service.
Choose 'HOLYHU\ RI 6$3 6HUYLFHV 6HUYLFH 3ODQ LQ 2SHUDWLRQV
The system goes to the catalog entry of the service, in the SAP Service Marketplace. Follow the procedure described in the SAP Service Marketplace.
5HVXOW You have requested the service. SAP will contact you to arrange the details.
SAP AG
SM100
10-28
/LVW RI 6HUYLFHV 2UGHU YLD 6HUYLFH 0DUNHWSODFH
SAP AG 2006
3URFHGXUH
Choose the transaction 62/87,21B0$1$*(5 Choose 2UGHU 6HUYLFH IURP 6$3 You go to the Service Catalog.
Choose 'HOLYHU\ RI 6$3 6HUYLFHV 6HUYLFH 3ODQ LQ 2SHUDWLRQV
Choose the link to the service. The system goes to the catalog entry of the service, in the SAP Service Marketplace. Follow the procedure described in the SAP Service Marketplace.
5HVXOW You have requested the service. SAP will contact you to arrange the details.
SAP AG
SM100
10-29
/LVW RI 6HUYLFHV &UHDWH /RFDOO\
SAP AG 2006
3URFHGXUH Choose the transaction SOLUTION_MANAGER. Choose &UHDWH /RFDO 6HUYLFH Choose Delivery of 6$3 6HUYLFHV 6HUYLFH 3ODQ LQ 2SHUDWLRQV You get a list of all possible services which you can perform yourself. Flag which services you want to create (and if necessary, for which systems). Choose the &UHDWH pushbutton. Choose the date to perform the service. The selected service appears in the sessions overview.
Once you have processed the session, you can create and save the service as a Word document, or view and save it as an HTML document.
SAP AG
SM100
10-30
60 6HUYLFH 'HOLYHU\

SAP AG
SM100
10-31
6LQJOH 3RLQW RI $FFHVV IRU 6XSSRUW SURFHVVHV

6HWXS 6HUYLFH &RQQHFWLRQV
'DWD 6\QFKURQL]DWLRQ ZLWK 6$3 6HUYLFH DQG 6XSSRUW 6\VWHPV
0DLQWDLQ 6HUYLFH &RQQHFWLRQV
0DLQWDLQ 6\VWHP DQG 6HUYHU 'DWD
2SHQ 6HUYLFH &RQQHFWLRQV
2SHQ 6\VWHPV YLD 6$3 6ROXWLRQ 0DQDJHU
2SHQ 6\VWHPV GLUHFWO\RQ GHPDQG
$FFHVV WR &XVWRPHU 6\VWHPV IRU 6$3 6XSSRUW

1DYLJDWH WR 6ROXWLRQ 0DQDJHU 'LDJQRVWLFV 1DYLJDWH WR 6\VWHPV GLUHFWO\
1DYLJDWH WR 6$3 6ROXWLRQ 0DQDJHU ZLWK 6ROXWLRQ &RQWH[W
SAP AG 2006
This function sets up service connections to SAP for the systems in your solution, using assistants. You can open a service connection for a specified time, so that SAP support staff can logon to your system. The Solution Manager exchanges data about service connections and systems with the SAP Support Portal. The 6HUYLFH &RQQHFWLRQ 2YHUYLHZ function in your Solution Manager system corresponds to the function which you can call in the SAP Support Portal, under http://service.sap.com/access-support.
SAP AG
SM100
10-32
$FFHVV WR 6HUYLFH &RQQHFWLRQV
SAP AG 2006
Service Connections in SAP Solution Manager will replace the functionality of "Service Connections" in SAPNET R/3 Frontend (transaction STSV in OSS). SAP Solution Manager will enable you to administer remote connections. It offers enhanced functionalities compared to the existing in SAPNet R/3 Frontend and SAP Support Portal that only offer basic functionality in this area. All existing service connection types are supported such as, R/3 Support, PC anywhere, HTTP- Connect URL Access. All existing connections are migrated from OSS automatically. You are about to see a series of screen shots that shows integration of Service Connections in SAP Solution Manager via transaction Solution_Manager: Entry Screen of Service Connections in transaction Solution_Manager Overview screen of Service Connections Create Setup Service Connection Screens Open/Change Service Connection Screens In this initial screen, a link for Service Connections is displayed in the Operations Setup area of transaction Solution_Manager
SAP AG
SM100
10-33
6HUYLFH &RQQHFWLRQ 2YHUYLHZ

&KDQJH 6HWXS IRU VHOHFWHG V\VWHP
6HOHFW 6\VWHP
SAP AG 2006
All systems that are assigned to a Solution are displayed in the overview of Service Connection screen. From here one can see system and service connections that have been setup. For example the highlighted system SAT has a connection of type R/3 Support. You also see the status of the connections. From this screen you can set up a new connection, change an existing connection, open a service connection or refuse access for selected system by using the relevant buttons. Multiple selection of connections and systems is supported for opening and closing.
SAP AG
SM100
10-34
'HILQH &RQQHFWLRQ 7\SH
6HOHFW &RQQHFWLRQ 7\SH
SAP AG 2006
System SAT was selected on the Service Connection Overview Screen and the button Create Setup was pressed. Following screen appeared with default values. A user only has to enter Service Connection Type by using the F4 to proceed to next step.
SAP AG
SM100
10-35
9HULI\ 6HUYHU OLVW
9HULI\ FRPSOHWHQHVV RI VHUYHU OLVW
SAP AG 2006
On the upcoming screen a list of all servers that are associated to the system is displayed just to check if your servers are maintained correctly in transaction SMSY. To proceed you can either click on the Next button or can directly click on the third step of Roadmap Control that is SAP Router.
SAP AG
SM100
10-36
0DLQWDLQ 6$3 5RXWHU 'DWD
6$3 5RXWHU WR 6$3
$GGLWLRQDO 6$3 5RXWHUV
SAP AG 2006
Here you can select the SAP Router that should be used for this system. If required you can add additional internal SAP Routers.
SAP AG
SM100
10-37
$VVLJQ &RQWDFWV
$VVLJQ &RQWDFW IURP 6$3 6HUYLFH 0DUNHWSODFH
SAP AG 2006
Now that the connection type and routers are defined, you add contacts for SAP on this screen by direct input or by using the value help for the Contact or Substitute input field. All other fields are filled automatically.
SAP AG
SM100
10-38
)LQLVK
SAP AG 2006
Finally FINISH step is reached where after clicking on Finish button, data is saved and synchronized with the SAP Service and Support systems. The new connection is ready for use.
SAP AG
SM100
10-39
2SHQ &ORVH FRQQHFWLRQV
6HOHFW V\VWHP DQG FRQQHFWLRQ W\SH
SAP AG 2006
So far a setup for service connection has been created. You will now see how an established connection can be opened or changed. On the upcoming screen a connection is selected and the button Open/Change will be clicked to perform the above mentioned task. The connections can belong to different systems and can have different types. You can select multiple lines with CTRL + Left mouse.
SAP AG
SM100
10-40
'HILQH 'HWDLOV
,QLWLDWH FRQWDFW WR 6$3 IURP FOLHQW 2SHQ IURP WR
&RQWDFW IRU WKLV VSHFLILF RSHQLQJ
SAP AG 2006
By default all input fields are filled. To avoid misunderstanding with SAP Support you may switch dates and times to the supporters time zone. Pushing Submit button will open the system immediately and the new status will be updated on Service Connection Overview screen.
SAP AG
SM100
10-41
8QLW 6XPPDU\
<RX DUH QRZ DEOH WR 'HVFULEH DQG XVH WKH &HQWUDO 6\VWHP $GPLQLVWUDWLRQ &6$ IXQFWLRQDOLW\
'HVFULEH WKH 6LQJOH 3RLQW RI $FFHVV IXQFWLRQDOLWLHV
2UGHU DQG PDQDJH 6$3 6HUYLFHV
SAP AG 2006
SAP AG
SM100
10-42
0RUH LQIRUPDWLRQ WKH DYDLODEOH 6$3 VHUYLFHV VHUYLFHVDSFRPVHUYLFHFDWDORJ
VHUYLFHVDSFRP VROXWLRQPDQDJHU 2SHUDWLRQV DQG 6HUYLFHV
SAP AG 2006
SAP AG
SM100
10-43
SAP AG
SM100
10-44
Bv 4 %r%&Ru
8QLW &RXUVH &RQWHQW
7 0 0 ( ' # " ! 654 3 21)&%$

SAP AG
SAP AG 2006
SM100
11-1
/HVVRQ 2EMHFWLYHV
8VH WKH EDVLF SURFHGXUHV WR VHW XS %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
8QGHUVWDQG WKH PHDQLQJ RI %XVLQHVV 3URFHVV 0RQLWRULQJ DV SDUW RI D %XVLQHVV ,QWHJUDWLRQ DQG $XWRPDWLRQ FRQFHSW
$IWHU FRPSOHWLQJ WKLV OHVVRQ \RX ZLOO EH DEOH WR
SAP AG 2006
SAP AG
SM100
11-2

%XVLQHVV 3URFHVV 0RQLWRULQJ 3URFHVV %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU $SSHQGL[ %XVLQHVV 3URFHVV 0RQLWRULQJ &RQFHSW 2YHUYLHZ
SAP AG
SM100
11-3
8QLW 2EMHFWLYHV
*LYH DQ 2YHUYLHZ DERXW %XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
SAP AG
SM100
11-4
SAP AG 2006
SAP AG
SM100
5RRW &DXVH $QDO\VLV
%86,1(66 352&(66(6
&25(
6$3 6ROXWLRQ 0DQDJHU 6FHQDULRV 6ROXWLRQ 0RQLWRULQJ %XVLQHVV 3URFHVV 0RQLWRULQJ
6ROXWLRQ 0RQLWRULQJ
6HUYLFH 'HVN
11-5
6ROXWLRQ 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU

(DUO\ :DWFK $OHUW DQG 6HUYLFH /HYHO 5HSRUWLQJ
:HHNO\ HYDOXDWLRQ RI V\VWHP VWDWXV DQG SHUIRUPDQFH :HHNO\ RU PRQWKO\ UHSRUWLQJ RQ 6/$V IRU WKH LQYROYHG V\VWHPV DQG EXVLQHVV SURFHVVHV 7HFKQLFDO UHDOWLPH PRQLWRULQJ RI V\VWHP FRPSRQHQWV EDVHG RQ WKH &&06 LQIUDVWUXFWXUH 6\VWHPUHODWHG WDVNV ZLWK LQWHJUDWHG DQG DXWRPDWHG ORJ 5HDOWLPH PRQLWRULQJ RI EXVLQHVV SURFHVVHV EDVHG RQ WKH &&06 LQIUDVWUXFWXUH &RYHUV DOO WHFKQLFDO DQG EXVLQHVV DSSOLFDWLRQ VSHFLILF IXQFWLRQV UHTXLUHG IRU D VPRRWK DQG UHOLDEOH IORZ RI EXVLQHVV SURFHVVHV
6\VWHP 0RQLWRULQJ DQG $GPLQLVWUDWLRQ
%XVLQHVV 3URFHVV DQG ,QWHUIDFH 0RQLWRULQJ
SAP AG 2006
SAP Solution Manager provides functionality for Solution Monitoring, both for Alert Monitoring (Keep the business running monitoring) and Reporting (Continuous improvement). System Monitoring and Business Process Monitoring provide Alert Monitoring functionalities, providing timely alerts if the operation of the solution (Business processes or systems) has been disrupted. Early Watch Alert (EWA) and Service Level Reporting (SLR) provide reporting functionality on a weekly (for SLR also on a monthly) basis covering the entire solution. This way, the fulfillment of Service Level Agreements can be monitored, as well the trend of the long term behavior of the solution. System Administration provides task alerting and task log book for system administrators, providing both guidelines for the daily administration tasks as well as the history of observed system behavior for long term trend analysis of the system behavior.
SAP AG
SM100
11-6
([DPSOH IRU %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
Monitoring alerts are immediately associated to the business process flow, so it is immediately clear for which business process step or interface the alert is relevant. System monitoring alerts are associated to the underlying systems, so an impact of a system on a business process becomes apparent.
SAP AG
SM100
11-7
mx P% d{ 5xCx 5 {m {x 5m m mY { tRm2 2Y m Y 5x
zy p p po {xejxs w tj h f d geRt 3 R
zylwow {gmxdv o p rjq p oj lj uj ts Uejnmki
ylwy gmm{Uv Xpx%m%$x rj xms zj}}sq y p o pw uj xx| eoFxm2x u y jy y r jz y r j $y tre$m q o p zs o x uj Xwxg ul ej |ow z r kxXp{y Cdmy eq
o pw|oy jy uj xgFxm poy r} k{y eR
r jz {y tg tUk25x tC u |ow y rwo w qo ùxejp xU{y x~w pw l z uoj vz o z w m ry j pwp r
ylwy v zj}}sq gmm{UxXpm%Ry g
q y pz j } } s tUj pU5Ctt{q w {$yk{{Rt~px%t{q u lw y v zj}}s |oy k{%q
6DWHOOLWH 6\VWHP
%XVLQHVV 3URFHVV 0RQLWRULQJ ZLWK 6$3 6ROXWLRQ 0DQDJHU
ylwy gmm{Uv pz j } } s q p w y t{2eyx{rz {y C2{y xms pz r p zj zyl z e rj x~xFC{gtl Xu r } u pz r r j j mw e{ xy Cm xt{
%30RQ LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG
SAP AG 2006
&XVWRPHU
SM100
6$3 6XSSRUW
6$3
11-8
8QLW 6XPPDU\
*LYH DQ 2YHUYLHZ DERXW %XVLQHVV 3URFHVV 0RQLWRULQJ
$IWHU FRPSOHWLQJ WKLV XQLW \RX VKRXOG QRZ EH DEOH WR
SAP AG 2006
SAP AG
SM100
11-9

%XVLQHVV 3URFHVV 0RQLWRULQJ 2YHUYLHZ %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU $SSHQGL[ %XVLQHVV 3URFHVV 0RQLWRULQJ &RQFHSW
SAP AG
SM100
11-10
8QLW 2EMHFWLYHV
([SODLQ WKH SURFHGXUH ZKHQ VHWWLQJ XS D %XVLQHVV 3URFHVV 0RQLWRULQJ FRQFHSW
SAP AG 2006
The setup of a Business Process Monitoring concept is independent of the tools that will be used for monitoring.
SAP AG
SM100
11-11
,QLWLDO &XVWRPHU 6LWXDWLRQ
&XVWRPHU
+HDGTXDUWHU
3URGXFWLRQ
'LVWULEXWRU
:DUHKRXVH
6XEFRQWUDFWRUV
SAP AG 2006
If a problem occurs in a complex solution landscape it is often unclear what impact the problem has on the core business processes.
SAP AG
SM100
C
11-12
6XSSOLHU
4XHVWLRQV &RQFHUQLQJ %XVLQHVV 3URFHVV 0RQLWRULQJ

+RZ RIWHQ GR , KDYH WR PRQLWRU" :KDW QHHGV WR EH PRQLWRUHG" :KRP GR , FRQWDFW LI , FDQW VROYH WKH SUREOHP"
:KDW GR , GR ZLWK D SUREOHP"
+RZ GR , PRQLWRU"
:KDW GRHV D SUREOHP PHDQ IRU WKH EXVLQHVV SURFHVV VWHS"
:KHQ DQG WR ZKRP GR , KDYH WR HVFDODWH WKH SUREOHP LI LW FDQW EH VROYHG"
SAP AG 2006
In order to identify which problems actually have an impact on the core business processes, a business process oriented monitoring has to be established.
SAP AG
SM100
11-13
6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ

%XVLQHVV 3URFHVV 0RQLWRULQJ &RQFHSW
%XVLQHVV 3URFHVV $QDO\VLV
%XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
SAP AG
SM100
11-14
,QLWLDO 6LWXDWLRQ
%XVLQHVV 3URFHVV 2ZQHUV
%XVLQHVV
$SSOLFDWLRQ 6XSSRUW EHIRUH *R/LYH

,PSOHPHQWDWLRQ
'HSDUWPHQWV
3URMHFW 7HDP
$SSOLFDWLRQ 6XSSRUW DIWHU *R/LYH"
,7 'HSDUWPHQW
7HFKQLFDO 6XSSRUW 6\VWHPV DQG %DVLVP\6$3 7HFKQRORJ\

SAP AG 2006
The ,PSOHPHQWDWLRQ 3URMHFW 7HDP usually provides the Application Support before the GoLive of a new software. This team normally knows about the business process, the technical details and dependencies like interface techniques (IDoc types, RFC queues, volumes to be processed) background jobs (reports, variants, business relevance of jobs, interdependencies) business process flow across the different system components, time critical paths in the business process
This way, they are able to ensure that by using the technical resources of the IT department the functional requirements of the Business Departments are met. Hence, the ,PSOHPHQWDWLRQ 3URMHFW 7HDP serves as a link between the Business Department and the IT Department. The main questions for the productive operation now are: Who will do the Application Support after the GoLive of the system (once the Implementation Project has been completed and the ,PSOHPHQWDWLRQ 3URMHFW 7HDP dissolved) ? How is the hand over of the Application Support at GoLive ensured?
The Application Support after the GoLive of the system may be provided by a dedicated $SSOLFDWLRQ 6XSSRUW 7HDP
SAP AG
SM100
11-15
&XVWRPHU 2UJDQL]DWLRQ ZLWK 5HOHYDQW 5ROHV

&XVWRPHU 2UJDQL]DWLRQ 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ
%XVLQHVV 'HSDUWPHQWV (QG 8VHUV .H\ 8VHUV %XVLQHVV 3URFHVV 2ZQHUV 7HFKQLFDO 6XSSRUW ,7 'HSDUWPHQW 6\VWHPV 6XSSRUW %DVLVP\6$3 7HFKQRORJ\ 6XSSRUW 6RIWZDUH &KDQJH 0DQDJHPHQW &KDQJHV WR %XVLQHVV 3URFHVVHV 'HYHORSPHQW 7DVNV $SSOLFDWLRQ 6XSSRUW $SSOLFDWLRQ 6XSSRUW %XVLQHVV 3URFHVV &KDPSLRQ 8VHU +HOS 'HVN /HYHO 6XSSRUW 'LVSDWFKLQJ
SAP AG 2006
The Application Support as link between IT Department and Business Department should be provided by the Solution Support Organization of the customer. There should be a Business Process Champion available in the Application Support that servers as the counterpart to the Business Process Owner in the Business Department. %XVLQHVV 3URFHVV 2ZQHU Person in the Business Department responsible for the functional flow of a business process and familiar with the business process and the corresponding business process steps.
%XVLQHVV 3URFHVV &KDPSLRQ
Person in the Solution Support Organization responsible for the support and the technical flow of a business process. Counterpart of and contact person for the Business Process Owner.
Parts of the Solution Support Organization can be outsourced or hosted by a third party company.
SAP AG
SM100
11-16
$SSOLFDWLRQ 6XSSRUW
5ROH
%XVLQHVV 3URFHVV 0DQDJHPHQW DQG 0RQLWRULQJ
Solution Support Organization
Business Process 1
Business Process Champion
Business Process 2
Business Process 3
Business Process 4
Software Change Management
Basis/mySAP Technology Support Systems Support (HW, OS, DB, Network, Frontends)
SAP AG 2006
SAP AG
User Help Desk
'HGLFDWHG WHDP LQ WKH FXVWRPHUV 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ ZLWK VLJQLILFDQW DSSOLFDWLRQ NQRZKRZ PLJKW EH DOVR D GLYLVLRQ RI WKH ,7 'HSDUWPHQW
5HVSRQVLELOLWLHV
%XVLQHVV 3URFHVV 0RQLWRULQJ LQFOXGLQJ WKH PRQLWRULQJ RI 3HUIRUPDQFH EDFNJURXQG MREV HUURU ORJV 3URJUDP 6FKHGXOLQJ 0DQDJHPHQW ,QWHUIDFH 0RQLWRULQJ IURP D IXQFWLRQDO YLHZSRLQW /HYHO 6XSSRUW
SM100
11-17

SAP AG 2006
SAP AG
SM100
11-18
,QLWLDO 6LWXDWLRQ
&XVWRPHU
+HDGTXDUWHU
3URGXFWLRQ
'LVWULEXWRU
:DUHKRXVH
6XEFRQWUDFWRUV
SAP AG 2006
In order to identify if a problem in the solution landscape affects the core business processes it is essential to know what these core business processes look like, what technical details are associated to the business processes and what business requirements concerning the execution of the business processes exist.
SAP AG
SM100
C
11-19
6XSSOLHU

7KH EXVLQHVV SURFHVV DQDO\VLV VKRXOG OHDG WR D GRFXPHQWDWLRQ WKDW KHOSV WR VXSSRUW WKH EXVLQHVV SURFHVV 7R DFKLHYH WKLV JHQHULF LQIRUPDWLRQ DQG DSSOLFDWLRQ VSHFLILF LQIRUPDWLRQ ERWK IRU WKH EXVLQHVV SURFHVV LQ JHQHUDO XQG IRU WKH VLQJOH EXVLQHVV SURFHVV VWHSV LV FROOHFWHG
Business Process Owner Process availability Volume information
Business requirements (time restrictions) Interfaces Technical Details
SAP AG 2006
The business processes of a company should determine how the involved systems should be supported. This way, you can ensure that every necessary aspect of the support is covered and that you dont waste your efforts doing support tasks that are not required. So when noting down the structure of the business process the intend is to document it in a way that the application flow is understandable and that the documentation helps you to identify the points where a business process might break down.
SAP AG
SM100
rRb%$P`
%$P`
*HQHULF ,QIRUPDWLRQ
$SSOLFDWLRQVSHFLILF ,QIRUPDWLRQ
Usage of critical functions such as variant configuration, batch determination etc.
rRs%%3Req %%3Req
Typical interfaces such as external tax software, WMS Specific functions such as rush orders
11-20
%XVLQHVV 3URFHVV $QDO\VLV ([DPSOH
Create Sales Order
Execution mode(s) Document volume (average number of documents, average number of line items per document) Time restrictions, peak time windows Tele sales or rush orders (delivery is created in combination with the sales order)?
Dialog transaction (VA01) Background job (RBDAPP01) ALE / EDI (IDocs) Batch input Direct input Custom transaction or program
Interface to CRM or SRM System Interface to external tax calculation software (e.g., for the US and Canada, Vertex) Interface to external credit card software
SAP AG 2006
For each business process step you need to gather the generic and application specific information. In our example, the sales order that was created on the CRM system is sent via an IDOC interface to the SAP R/3 system. There a respective sales order is created during the business process step Create Sales Order, using either dialog transaction VA01 or program RBDAPP01 as a background job. Normally, about 1000 sales orders with in average of 3 items per sales order are created per day.
SAP AG
SM100
{Bn2
0 5X~ %A

3x 3
t

&&Y&r& r ~62 &$ m'%t # xe "!g &3r53xg5g5 t ~xt`d Yemr5{kx g n 6t`d ~$
# 3
9 8
n g~xt`d
# 4 2 0 3x 7 ` g65316qttx)(
11-21

SAP AG 2006
SAP AG
SM100
11-22
%XVLQHVV 3URFHVV 0RQLWRULQJ 6FRSH

%XVLQHVV 3URFHVV 0RQLWRULQJ LQFOXGHV WKH VROXWLRQZLGH REVHUYDWLRQ RI
%XVLQHVV DSSOLFDWLRQ ORJV HJ DSSOLFDWLRQ ORJ GXH OLVW ORJ HWF .H\ 3HUIRUPDQFH ,QGLFDWRUV SHUIRUPDQFH WKURXJKSXW 3URJUDP VFKHGXOLQJ PDQDJHPHQW $EODXIVWHXHUXQJ
5HTXLUHG SHULRGLF PRQLWRULQJ WDVNV
7HFKQLFDO LQIUDVWUXFWXUH DQG FRPSRQHQWV ZKLFK DUH UHTXLUHG WR UXQ WKH EXVLQHVV SURFHVVHV
'DWD WUDQVIHU YLD LQWHUIDFHV EHWZHHQ VRIWZDUH FRPSRQHQWV
%XVLQHVV SURFHVV FRPSOHWLRQ
%XVLQHVV 3URFHVV 0RQLWRULQJ FRPSULVHV
7LJKW LQWHJUDWLRQ LQWR WKH FXVWRPHUV VROXWLRQ VXSSRUW RUJDQL]DWLRQ

SAP AG 2006
3UHFLVH GHILQLWLRQ RI FRQWDFW SHUVRQV DQG HVFDODWLRQ SDWKV
'HWDLOHG SURFHGXUHV IRU HUURU KDQGOLQJ DQG SUREOHP UHVROXWLRQ
The SAP Solution Manager is a tool to realize a Business Process Monitoring concept.
SAP AG
SM100
11-23
6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
The goal of Business Process Monitoring is the definition of the monitoring activities that are necessary to support the business process. These activities should be documented so that the different people know what they have to do in order to support the business process and in order to make sure that all parts of the business process are supported.
SAP AG
SM100
C D Yt 6`5& 2I
Application Support Background Job Monitoring Basis Monitoring Interface Monitoring
Q I R!
&23 dIERa& I H GE PU"!F
0 3x %0
# 6V
eV 6x 0
1`
X ! W U
&RP%e
11-24
% D YG CPe5 s d eY)Ur ir$
E G ! x G d Y%G % I G I 6i%3!% `Ca`èyPC!E C x I G d 231eUr v wC&d

C663 I G rf$
Crt u g CèY23 C2 s d `Y)Rr sr$
Gd %qBe I G 6pr %& YI c h iC&2

e fd
%C %6 Cg e 3 fd YI c a br2
C Pe5 1Ee s ! CGG CG PE
2 C 663 I E ' s x
sc
C6 G G I G P w r d
2 e23 2 r% & Ce R

D s P3 s c I d`Yd 6G G d Y
d P
2 %d`d I 3f$ PCG G I D CP3
2 Y%f s s c G x C %$r G d G C c I d Y%q!r`6G I G x G E 6 `)eC x G E ) PCC
G 2b s % 26r%Y$ C G
SAP AG
SAP AG 2006
Ideally, the Business Process Monitoring should be developed before the productive operation of the business process starts. This way, you can ensure that the knowledge of the implementation team regarding the monitoring can be used to its full extend and a handover is more feasible. Another advantage is that the monitoring itself can go live with the business process.
6WHSV WR 'HILQH DQG &UHDWH D %XVLQHVV 3URFHVV 0RQLWRULQJ &RQFHSW
3KDVHV RI D 6RIWZDUH ,PSOHPHQWDWLRQ 3URMHFW
SM100
11-25
6WHS ,GHQWLI\ &RUH %XVLQHVV 3URFHVVHV

Strategic Framework Technical Technical Cutover and and and Start Operations Integration of ImpleDesign Production mentation Operations and Continuous Improvement
Define and Implement Create the a Monitoring Monitoring Concept Concept
Start Monitoring
Change Management in Monitoring
)RFXV RQ WKH FXVWRPHUV FRUH RU FULWLFDO EXVLQHVV SURFHVVHV 'HWHUPLQH IRU HDFK EXVLQHVV SURFHVV
'HSHQGHQFLHV RQ RWKHU EXVLQHVV SURFHVVHV 3URFHVV DYDLODELOLW\ %XVLQHVV SURFHVV RZQHU %XVLQHVV UHTXLUHPHQWV
Step 1 Step 2 Step 3 Step 4 Step 5 Identify Identify Define Define error Define core process monitoring handling monitoring business steps objects procedures activities processes and and escainterfaces lation paths
SAP AG 2006
Of the business processes run by the customer choose those responsible for the bulk of income that will make the customer loose money if they stand still. From the application point of view you need to know who is the person responsible for the overall smooth functioning of the respective core business process. Further questions are: What is the business process supposed to do? Are there any business processes that are interlocked with this business process, e.g. do you have to wait for results from other business processes before going on? What are the times the business process needs to be available? Do you want to ensure 24x7 availability (e.g. telesales)? Are there any time constraints for the business process or steps of the business process? E.g. all trucks have to leave the plant by 16:00 to ensure next day delivery, therefore Print Invoice has to be completed by 15:00. What volumes of documents do you need to process per day / per hour? This is limited by the hardware resources as well as by the workload created on the system by other activities. What happens if the process dumps and needs to be restarted? Can it be restarted without further actions?
SAP AG
SM100
q V5 ( q
q % q p 'f ( q
g n
s }{~ qr |y pqy wx f o z{u tuv e v{ f %d Vww{|y qv t l B5%fg kj ih
{~ (|y q r ty{u q pf q f
d d qd f }{ y f d t
e f %d Vq f nj %%m
%%3R%Ce
3URFHVV WLPH FRQVWUDLQWV 'RFXPHQW YROXPH WR EH SURFHVVHG 3URFHVV UHVWDUW DELOLW\
11-26
6WHS D ,GHQWLI\ 3URFHVV 6WHSV

%XVLQHVV 3URFHVV ([DPSOH ,QWHUQHW 6DOHV
'HWHUPLQH IRU HDFK EXVLQHVV SURFHVV VWHS

3URFHVV VWHS WLPH FRQVWUDLQWV 'HSHQGHQFLHV RQ RWKHU SURFHVV VWHSV 5HODWHG LQWHUIDFHV
SAP AG 2006
([HFXWLRQ PRGH GLDORJ WUDQVDFWLRQ SURJUDP RU UHSRUW HWF 7KH FRUUHVSRQGLQJ VRIWZDUH FRPSRQHQW
The business process can be structured into several business process steps. Each process step needs to be analyzed thoroughly, concerning in what way the process step will be realized in the solution, what resources will be used and what requirements have to be met.
SAP AG
SM100
5
3x 3 t
t
1
&&&r3 X I ~xt`d &$ m'%t # t )R!g &&&533xg5g t 6t`d remr5mex n 6t`d ~$td
g n %6t`d
Start Monitoring
11-27
6WHS E ,GHQWLI\ ,QWHUIDFHV

'HWHUPLQH IRU HDFK LQWHUIDFH
'RFXPHQW YROXPH WR EH SURFHVVHG 7LPH FRQVWUDLQWV
,QWHUIDFH WHFKQLTXH XVHG 5)& $/( (', HWF ,QYROYHG PLGGOHZDUH LI DQ\
SAP AG 2006
Interfaces are a critical part of the solution. For all involved interfaces determine the technical properties and the requirements that have to be met.
SAP AG
SM100
5
3x 3 t
t
1
g n %6t`d
Start Monitoring
11-28
6WHS D 'HILQH 0RQLWRULQJ 2EMHFWV

'HILQH DSSURSULDWH PRQLWRULQJ REMHFWV IRU HDFK SURFHVV VWHS LQWHUIDFH

3HUIRUPDQFH DQG WKURXJKSXW GLDORJ WUDQVDFWLRQV 8SGDWH HUURUV $SSOLFDWLRQ ORJ GXH OLVW ORJV HUURU ORJV 3URJUDP 6FKHGXOLQJ 0DQDJHPHQW EDFNJURXQG MREV
SAP AG 2006
To simplify the monitoring of the business process, monitoring objects have to be defined for each process step or interface. According to these monitoring objects, monitoring tasks can be defined and assigned to the responsible monitoring teams. Monitoring objects should be defined according to the parts of the business process where something might go wrong and what symptoms would occur in case of problems. If for instance there is a problem with a material, the background job creating the deliveries might cancel but create also an entry in the application log. Therefore, in addition to the job, the application log should be monitored for critical entries.
SAP AG
SM100
5
3x 3 t
t
1
g n %6t`d
Start Monitoring
11-29
6WHS E $VVLJQ 0RQLWRULQJ 5HVSRQVLELOLWLHV

Start Monitoring
%DFNJURXQG -RE 0RQLWRULQJ %XVLQHVV 3URFHVV 0RQLWRULQJ %DVLVP\6$3 7HFKQRORJ\ 0RQLWRULQJ 6\VWHP 0RQLWRULQJ
SAP AG 2006
With specified monitoring objects, tools, and precise error handling procedures, the monitoring activities can be defined. These activities tell all involved persons exactly how they have to participate in the Business Process Monitoring. Monitoring Checklists help the Monitoring Teams to keep track of their duties. Business Process Monitoring can be set up in the SAP Solution Manager. For the business processes maintained in the SAP Solution Manager it is possible to define monitoring objects, error handling procedures, escalation paths and monitoring activities for each team of the Solution Support Organization. As part of the SMO Service for Business Process Management, Business Process Monitoring will be set up in the SAP Solution Manager for 1-2 core business processes.
SAP AG
SM100
x I E P ! P
I H r P&261b%F6q`
PCG !p() e6 CP s E c e C x E P yCR%e s s %" G G I 3Rr`! C C G x `235dPb2 Y%) `` I G I d geYYFap CC6CUr 2 Us s diyb2216 g I C G
CPgrP "E`7 c c r
,QWHUIDFH 0RQLWRULQJ
6t)"
(6`!
!!fp67 B 6
6`
)6!!%` )!V) ) ' %
p)!!6 )6)(! ) ' q 1
w!!6 16)p!)y ) 5 %
b!6!%` !Vy ) ' % 1
11-30
h a fB w
I I G I G &d3RU6UY76%" I e G P%$Efrq I I G d 3gd`dR2 F3CwXPU G G I G I G P%d gd'C`6 B$ td C G G x q!6CE Y6tUP$~ C 6`53 1E%da6q C G G x q6E2 Y`yUPtR6 I$n!!qgP yC2pB&q ! x e G 2& 22!)qX q6 )f6yFppFrc x
(6`! !!fp67 B 6 6`
) ' % )6!!%` )!V)
) ' q 1 p)!!6 )6)(!
) 5 % w!!6 16)p!)y
) ' % 1 b!6!%` !Vy
6t)"
SAP AG
Strategic Framework
SAP AG 2006
With the defined monitoring objects you can determine what tools should be used to carry out the respective monitoring tasks. Possible tools are SAP Monitoring Tools like the SAP Solution Manager, or third party products like Hardware Vendor Products for system monitoring.
Technical Technical Cutover and and and Start Operations Integration of ImpleDesign Production mentation
6WHS F ,GHQWLI\ 0RQLWRULQJ 7RROV
Start Monitoring
Operations and Continuous Improvement
%DVLVP\6$3 7HFKQRORJ\ 0RQLWRULQJ
%DFNJURXQG -RE 0RQLWRULQJ
,QWHUIDFH 0RQLWRULQJ
6\VWHP 0RQLWRULQJ
SM100
11-31
6WHS D 'HILQH (UURU +DQGOLQJ 3URFHGXUHV

'HILQH HUURU KDQGOLQJ SURFHGXUHV IRU HDFK PRQLWRULQJ REMHFW
:KDW KDV WR EH GRQH LQ FDVH RI DQ HUURU RU SUREOHP" )RU LQVWDQFH ZKDW KDV WR EH GRQH LQ FDVH RI DQ DERUWHG MRE" ,V LW SRVVLEOH WR UHVFKHGXOH WKH MRE LPPHGLDWHO\ RU WKH GD\ DIWHU RU FDQ , SURFHHG DQG VWDUW WKH GHSHQGHQW VXFFHHGLQJ MRE" :KR KDV WR EH FRQWDFWHG LQ FDVH RI DQ XQNQRZQ SUREOHP" 3UREOHP VROXWLRQ URDGPDSV
SAP AG 2006
For each monitoring object you need to know what has to be done in case of an error. For each possible error, ask : Does the error interrupt the business process flow? If it does, the error is critical. Then ask: Does the error result in data loss or inconsistency? What types of errors do occur? Are error handling procedures defined? Are the errors and their causes visible to end-users and system administrators? Are reporting strategies and escalation paths completely defined and published to all concerned parties? If such errors occur, are there alternative procedures or settings that enable users to avoid them? Are the roles and responsibilities clearly defined? Can steps be taken to prevent the error in future?
For each type of error, create a road map for analyzing and handling the error.
SAP AG
SM100
5
3x 3 t
t
1
g n %6t`d
Start Monitoring
11-32
6WHS E 'HILQH (VFDODWLRQ 3DWKV

Problem occurs
SAP Support Desk (Solution Manager)
SAP Support Desk Ownership of technical messages (Solution Manager) Solving of technical issues Search for SAP Notes Implementation of SAPNet Notes Maintenance of solution database SAP Support Desk (Solution Manager)
SAP AG 2006
It is possible that the end user encounters an unknown error or that one support level encounters a problem which it cant solve. In that case each person involved needs to know whom to contact for help. These communication paths need to be clearly defined, documented and the documentation should be centrally accessible.
SAP AG
SM100
(1"p61b!BVP(
Ownership of functional messages Reproduction in test system Solving of functional issues Search for SAP Notes Maintenance of solution database
1!!y p!)`
Logging problems into ticket system Completing initial message information Problem solving Search for SAP Notes Search for solutions in solution database Categorization of messages
SAP Support Desk (Solution Manager)
SAP Support Desk (Solution Manager) SAP Support Desk (Solution Manager)
16tq56 R1
Telephone Email Support Line Feedback
Start Monitoring
Solves Handling Problems Answers How to-Questions
1`Ry(6)
Rb
Face to face Telephone
"byR
Providing expert knowledge concerning the business process Solving of complex customizing problems Search for SAP Notes
11-33
6WHS D 'HILQH 0RQLWRULQJ $FWLYLWLHV

Start Monitoring
'HWHUPLQH WKH PRQLWRULQJ DFWLYLWLHV IRU HDFK PRQLWRULQJ REMHFW
,H PRQLWRULQJ REMHFW WLPH IUHTXHQF\ WRRO LQGLFDWLRQ HUURU KDQGOLQJ SURFHGXUH HVFDODWLRQ SDWK
P')6$ %6`!6 & & VV`)( P%q$ & P'`p% `'`$ `#6 ! ")` !!

:KDW KDV WR EH PRQLWRUHG E\ ZKRP ZKHQ KRZ RIWHQ ZLWK ZKLFK WRRO ZKDW LV WKH HUURU LQGLFDWLRQ ZKDW LV WKH HUURU KDQGOLQJ SURFHGXUH DQG ZKR PXVW EH FRQWDFWHG LQ FDVH RI DQ XQNQRZQ HUURU"
'HGLFDWHG 0RQLWRULQJ &KHFNOLVWV IRU WKH 0RQLWRULQJ 7HDPV

0 1' y rx
SAP AG 2006
With specified monitoring objects, tools, and precise error handling procedures, the monitoring activities can be defined. These activities tell all involved persons exactly how they have to participate in the Business Process Monitoring. Monitoring Checklists help the Monitoring Teams to keep track of their duties. Business Process Monitoring can be set up in the SAP Solution Manager. For the business processes maintained in the SAP Solution Manager it is possible to define monitoring objects, error handling procedures, escalation paths and monitoring activities for each team of the Solution Support Organization. As part of the SMO Service for Business Process Management, Business Process Monitoring will be set up in the SAP Solution Manager for 1-2 core business processes.
SAP AG
SM100
C C 3 5 C A 777c gvu
8 3 C A @ c "QI3 R 8 G gc
C C 3 e G 8 g7Uw
8 3 Igc
9 4 "gbF2 4 P A c P R e G
C C 3 e G 8 S 7UI3
D c 3 R A e G g"bEI"@
D e 3 8 8 giG
t s q Erp
3 H P C C 3 R 8 G 8 IEE7b'Ua8
3 D 4 S R G e D G Ug3 TQ7c
C A D P D C If7UYc 5 w e G 'h B'2
D c 3 R A e G gIfEQ"@
d H 4 G Bc 5
G 8 S R P C @ UTEQIEC
s `
P C V QIW6
!P%)i
9 4 I"@ 5 P 9 4 ""@ 5 P R P IYX
R S Qgg'QIe w D C 3 A 3 8 5
H 4 D G FEC 5 B7'@ 4 3 A
! V''!P 9 76 5 "'2 8 3 4 3
11-34
8QLW 2EMHFWLYHV
([SODLQ WKH SURFHGXUH ZKHQ VHWWLQJ XS D %XVLQHVV 3URFHVV 0RQLWRULQJ FRQFHSW
SAP AG 2006
SAP AG
SM100
11-35

SAP AG
SM100
11-36
8QLW 2EMHFWLYHV
8VH %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU DV DQ ,7 2SHUDWRU
8VH WKH VHWXS SURFHGXUH IRU %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU IRU WKH H[DPSOH RI XSGDWH HUURU PRQLWRULQJ
SAP AG 2006
SAP AG
SM100
11-37
%XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
Monitoring alerts are immediately associated to the business process flow, so it is immediately clear for which business process step or interface the alert is relevant. System monitoring alerts are associated to the underlying systems, so an impact of a system on a business process becomes apparent.
SAP AG
SM100
11-38
)XQFWLRQDO 6FRSH IRU $OHUWV ZLWKLQ %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
:KDW FDQ EH PRQLWRUHG E\ %XVLQHVV 3URFHVV 0RQLWRULQJ "

&URVV $SSOLFDWLRQ REMHFWV
%DFNJURXQG MREV 3HUIRUPDQFH RI GLDORJ WUDQVDFWLRQV 7UDQVDFWLRQ FRGH DQG IXQFWLRQ FRGH OHYHO 8SGDWH HUURUV 'RFXPHQW YROXPH EDVHG RQ 6$3 WDEOH VWDWLVWLFV $SSOLFDWLRQ ORJ $OO DOHUW LQIRUPDWLRQ YLD &&06 DOHUW LQIUDVWUXFWXUH
SAP AG 2006
$SSOLFDWLRQ VSHFLILF REMHFWV

(UURU ORJV HJ 6' 'XHOLVW $32 3ODQQLQJ (%3 SURFHVV DOHUWV 053 UXQWLPH VWDWLVWLFV :DUHKRXVH 0RQLWRU
,QWHUIDFH REMHFWV
$/( ,'RF DOHUW PRQLWRULQJ T5)& DOHUW PRQLWRULQJ
&XVWRPHU VSHFLILF REMHFWV

$OO DOHUW LQIRUPDWLRQ YLD &&06 DOHUW LQIUDVWUXFWXUH &XVWRPHU H[LW LQ $SSOLFDWLRQ 0RQLWRULQJ LQIUDVWUXFWXUH
SAP AG
SM100
11-39
3 bR 5 gQaQs D c A 8 n G
3 S 9 D 3 H P 8 G D C 3 e c 3 8 3 5 IEY7IUIU @ c bII7bEQG "Ivt 5 e G D C @ 3 e 4 n c
@ 3 D C G EQQS C 3 A C 5 C @ G G H G m G 777C QIIg#Fl 3 bR rEg'#73 5 p 3 C c G S C H 4 5 G IP v2
H G q D 5 q 3 A 2 EFC ov7c 5 4 4 uu H 5
3 S 9 D 3 H P 8 G D EQ'C 3 e c 3 8 3 5 7IUIU #@ c IE7gID 5 4 3 6 3 q e G
3 fR YQ'E73 5 p 3 C c G S C H 4 5 G "P v2
3 e c 3 8 3 5 77UU @ q D5 y C x @ 3 R 5 c G Eb8 '7e p H 5 5 T7c Qe w 3 bR 'rE'E3 5 p 3 C c G S C H 4 5 G IP v2
3 bR IiBQs 5 D c A 8 n G @ 3 D P 3 8 e C D c 3 R 5 q C G m G 7gUQfUgIfIS I"Ig#l 3 bR 'r7Q"73 5 p 3 C c G S C H 4 5 G IP v2 g e fd
@ 3 D P 3 8 e C R 3 5 3 E7IfQD T7c 5 4 @ c P C 8 3 @ 8 G D c 3 H 8 A G m G "bI"'#g"IQI7l j i kh
Send Urgent Order
([DPSOH IRU $SSOLFDWLRQ 6SHFLILF 0RQLWRULQJ 2EMHFWV %XVLQHVV .3,V
Create Picking Transfer Order (TO)
Confirm Picking TO (LT11)
@ 3 R b8 5 g'C c G e x
p H 5 5 T7c Qe w
C x
p H 5 5 w c 3 B7c Ie 'oIES x
@ 3 D P 3 8 e IbC x
p H 5 5 oc EIe 'w
C 5 8 3 73 a"6 5 QTEQQn gG 4 3 @ @ c A G D A c 3 S G G m G "g'#I7l
@ 3 D P 3 8 e C 5 8 3 U7gUQog3 iIE6 5 ""@ 4 3 @ c A G n D A G G m G I''#Ig#l
SAP AG

SAP AG 2006
The Business KPIs contain various application specific functionalities. Purpose of these functionalities is to monitor business process specific backlogs, throughputs etc. In the above example all monitoring objects in boxes are Business KPIs.
KPIs are dependant on the release of the ST-A/PI installed on the satellite system. For ST-A/PI01I there are KPIs available in the areas
Sales and Services
Warehouse Management
Inventory Management
Logistics Execution
Procurement
Manufacturing
Plant Maintenance
For detailed information about all available KPIs see http://service.sap.com/BPM
Perform Billing (VF04)
Post Goods Issue
Create Outbound Delivery (VL10A)
Create Sales Order
SM100
Perform Order Rescheduling (V_V2) Create Shipment (VT01N) In case of Discrepancies block Discrepancies on Bin in Storage Type 999 Confirm Picking TO with difference
11-40
7HFKQLFDO /DQGVFDSH IRU %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU

6$3 6ROXWLRQ 0DQDJHU 6\VWHP 67 676(5 67$3, 5)& 'HVWLQDWLRQ IRU 'DWD &ROOHFWLRQ 6DWHOOLWH 6\VWHP 673, 67$3,
5)& 'HVWLQDWLRQ IRU GLDORJ ORJRQ WR VDWHOOLWH V\VWHP
&&06
&&06
SAP AG 2006
For Business Process Monitoring in SAP Solution Manager only the add-ons ST, ST-SER and ST-A/PI are relevant. On the satellite system, the add-ons ST-PI and ST-A/PI have to be installed. Business Process Monitoring in SAP Solution Manager is based on CCMS (transaction RZ20). This means that with the setup of the monitoring so-called monitoring tree elements (MTEs) will be created. Both the CCMS on the SAP Solution Manager system and the satellite system are used.
SAP AG
SM100
11-41
&RPSXWLQJ &HQWHU 0DQDJHPHQW 6\VWHP &&06

~ 'y w|ax Fiwj x ~ } j y { z z y x v y v v i F'Fk #U)rj { x z j g
SAP AG 2006
For some monitoring objects the local RZ20 is used to collect the monitoring data, for some the central RZ20 on the SAP Solution Manager system is used. This means that during the activation of Business Process Monitoring MTEs will be created, depending on the monitoring object either in the CCMS of the Solution Manager system or the CCMS of the satellite system. Most monitoring functionalities use the CCMS of the SAP Solution Manager system. These include Application monitors Job monitoring Document volume monitoring Application log monitoring Due list log monitoring
Some monitoring functionalities use the CCMS of the satellite system. These include Dialog Performance Monitoring Update Error Monitoring Interface Monitoring Other CCMS Monitoring
SAP AG
SM100
e z v #rw#u#' x z z ri#y r v ")#we x v h r y x z z v x v h if#vwe
e be
e z v x #rfu#y
11-42
3 5 G 6 ge 'E7c
V 3 D P 3 77U8 h
n G 8 G D 8 4 9 4 3 2 D 8 P a"3 fYgP "F"UD l t s q p c 5 D e P C c P D 8 G IEr)'G iEg"8 Q' H7c 5a8D 5Qc'GfRf37ec"b'I"w G P R 8 G 8 3 C 3 H P C C 3 g"7EEgfR 8 G 8 8 3 c 5 D P e aIG 7"G 4 "P 4 4 5 8 3 D P R 8 G H 5 8 G 5 c G "P iI7b##afEc iaD IoR
~ x Fi##y rx ur { { } #Fu F#u'F'#F#"u fg { x y { x x y y v v i ~ ~ y ~ ~ y { ~ 'uf I'ww#w#~ ~ y { x v g x ~ y y x y y "iIr~ iFy FQ v# x z v y { x ~
8 3 @ "I8 x
V C 4 3 IP
V 3 D P 3 U78 h h
n G 8 G D 8 4 c 5 D a'"3 f)'G 7P 4 I7"P 4 3 e c
0RQLWRULQJ &RQILJXUDWLRQ
` 2 3 S 9 x E""p 8 G H 5 8 G 5 c G R e G 'Bc a'aD "ffIF2
3URFHVV 'HILQLWLRQ LQ 6ROXWLRQ 0DQDJHU
x y Fi|iFiU'vy r'"ufg ~ y v y x ~ x j ~ ~ y
~ y v y x { "FaiFiFF#Fy #uuix v ~ x ~ ~ ~ y ~ x y aiEwrx Fr vr { { { ~ ~
H G q c 5 D P "QoG 7ge 5 "f 4 S S
SAP AG
SAP AG 2006
$FWLYDWH 0RQLWRULQJ
0RQLWRULQJ 6HWXS 6WUDWHJ\
0DQXDO HQWU\
SM100
,PSOHPHQWDWLRQ 3URMHFW
11-43
6HWXS 3URFHGXUH %XVLQHVV 3URFHVV 0RQLWRULQJ LQ WKH 6$3 6ROXWLRQ 0DQDJHU
C 4 "7'2 5 P D 3
SAP AG 2006
SAP AG
H 5 8 G 5 c G 3 q D 3 C c aD Q'YbiE#t
g1')W W WW
Solution Manager:
1r"
3 D P 5 D e 76 igr
Solution Manager:
1r"
3 D P 8 3 c 7I7I3
W 11Q Wr"
Solution Manager:
8 3 H P c P c I"QgIYf'G 5 gA 'G gic 5 D 4 3 q D H 5 8 G 5 c G 3 e P 8 3 D c a'D ")o7"gc IFg3 S A D
c 5
Satellite System
R 3 D C QU79 D 5 4 U7P 3 4 3 D H 5 8 G 5 c G 3 e P 8 3 D c a'D ")o7"gc
H 5 5 R G D C Ec 7 #7gA
S A D IFg3
W 11Q Wr"
Solution Manager:
C C 3 e G 8 w C C 3 5 C A u 3 D P 3 WU'T7gc gvo77U8
H c 5 8 G 5 c G S A D a#aD I')oQF3
Solution Manager:
'f1 WE
D c 3 c G S R gI7QTG
4 P 5 H G q 3 D P 3 h "e Eo78
gg W 7
Solution Manager:
c G 5 gA G D 4
3 D P 3 g8
Solution Manager:
7rg gI
3 8 3 UIq
Create Solution Create Product, Server, Database and System Create RFC Destinations and Maintain SAP Server Names Create Logical Component Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
Define Solution Support Organization Choose Business Process and Process Steps to be monitored Define Monitoring Objects per Step Per Monitoring Object: Provide technical Details and Threshold Values for the Alerts. Assign Monitoring Transactions and Set up Monitoring Tasks. Set up Automatic Emails and Service Desk Messages Set up Interface Monitoring in the Satellite Systems Specify Interface Details Assign Monitoring Objects to the Interface Assign Analysis & Monitoring Tools and Set up Monitoring Tasks. Set up Automatic Emails and Service Desk Messages
Generate Monitoring Customizing Generate Local RFC Destination and set Data Collector Frequencies Activate Monitoring Observe Alerts Relative to the Business Process Check Detailed Alert Information and Check for Open Alerts Review Historic Alerts Analyze Problem in the Satellite System Create Service Desk Message Confirm Alerts for Solved Problems
SM100
11-44
y v ~ ~ y '##ku#Y u fF'y ~ y h y { y j z { v y F#} U v#uy F' urFiuFx y FFu z z v { x v x v { { x y z ~ ~ z v v 'r iFFuv'iv 'y { x v x y y x z v ~ y #'y Fu'u#y F#Qurx ury FUu'u" z y x v y { { z { ~ ~ y ~ I iFy FFuF''ui#f { x z v v y ~ v { y y x ~ v x v
~ y v ~ ~ y #F'##F)h ~ y y { F uFF|~ u' u Fy uv#v y j v z { v y { x v x v {
~ ~ v x Ev#a'1vx uvfj { { x y
x y "uv U'Fv FiF x v' vry '"#x u x { z { y x v z v { { v x x ~ } ~ y { x y v v i ivuu#Fw #)BfuQu"r|#fh { x z j g j ~ { z x y { y { y ~ "w ##vi'Urx w Fr { x v ~ v x { { { ~ ~
y { v '~ 'x y F|Fv y z v z ~ rFFuQu' x F' v'v ###uv v ur fd y y { y z ~ { x v ~ x {
~ x Fy F'vF' z v y x ~ y z v ru"u~ #'F vuF'iu ufg z ~ y x v z { v x y z v { y x y {
x y 1"#E'1x uwFg { { i y
y x j uiw|#"u fg ~ ~ y uy #"vu'u#vwF x ~ ~ ~ y ~ ~ y { ~ y y ~ '' urF} x Fr #Frx FF k'Fu y z ~ { z v { x { { { y ~ ~ ~ y { ~ y u#bfF#iEx urk"fh ~ x y { { i y { y
y { 'irx uw'|#uiw|#"u fg y x ~ y x j ~ ~ y ~ ~ y { ~ ##ubF#uf'u#b#Fu v ~ ~ y g ~ ~ y { ~ y ~
z #} u'Fuu y ~ iuFFvrr U~ F''y | v#"#'y #fh { x v x y y y v x { ~ ~ v ~ v x y { y
Q uv'rirvub|r #U)"fh { x v { v x j { x z j y { y
SAP AG
SAP AG 2006
6WHS LQ 5RDGPDS
The general procedure how to set up monitoring customizing does not depend on the monitoring types used. Therefore before focusing on the detailed monitoring functionalities, we focus on the procedure itself.
6HWXS 3URFHGXUH IRU %XVLQHVV 3URFHVV 0RQLWRULQJ &XVWRPL]LQJ
'HWDLOV
SM100
11-45
:KHUH WR VHW XS 0RQLWRULQJ &XVWRPL]LQJ
6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ
0RQLWRULQJ &XVWRPL]LQJ LV VHW XS LQ WKH 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ LQ DUHD 2SHUDWLRQV 6HWXS 6ROXWLRQ 0RQLWRULQJ %XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
Each user has to register before entering the 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ session for the first time. You will get a certification screen that requires you to enter your user credentials. This user registration is for documentation purposes only. No cross-checking takes place at this stage.
There is one 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ session per solution. Monitoring customizing for all business processes is maintained in this one session. The 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ session is available as soon as a logical component with a productive system has been assigned to the solution.
In the 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ session you have a session tree on the left hand side. On the right hand side you have two areas: The node description area and the area for data entry. The node description area contains a lot of detailed information about what has to be maintained to what purpose in the area for data entry and should always be your first point for consultation in case of questions and problems.
SAP AG
SM100
11-46
6HWXS 3URFHGXUH %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU

C 4 "7'2 5 P D 3
SAP AG 2006
SAP AG
H 5 8 G 5 c G 3 q D 3 C c a'D I')ogYQt
7'r w
Solution Manager:
W 1EYw"
3 D P 5 D e U7E6 g
Solution Manager:
W 1EYw"
U7"7"w
1b WEYw"
Solution Manager:
7 a Q'Yb7QUIg o"'
"IE7"fB ''7 Y
Q7 Ir
Satellite System
7 a Q'Yb7QUIg o"'
7 a' "#YoI7
7 TE
1b WEYw"
Solution Manager:
C C 3 e G 8 w C C 3 5 C A u 3 D P 3 g7g"'gc gvTU78
Solution Manager:
W W f WQ
D c 3 c G S R g"7#Q#G
4 P 5 H G q 3 D P 3 h "e '"Qog8
7171 W 7
Solution Manager:
' g 'bU7Ew
Solution Manager:
Wrg g"
3 8 3 gq
SM100
11-47
*HQHUDWH &XVWRPL]LQJ DQG $FWLYDWH

6WHS LQ 5RDGPDS
g"7"w
'HWDLOV
0RQLWRULQJ &XVWRPL]LQJ LV JHQHUDWHG IRU HDFK EXVLQHVV SURFHVV LQGLYLGXDOO\ 0RQLWRULQJ &XVWRPL]LQJ LV ZULWWHQ LQWR LQWHUQDO WDEOHV
SAP AG 2006
From a technical point of view is the monitoring customizing considered as master data. Thus, the customizing can NOT be transported between different SAP Solution Manager systems. Changes to the monitoring customizing that have not been generated are not considered when activating. Thus a change management for productive Business Process Monitoring is supported by the 2-step strategy for activation.
SAP AG
1R LQIRUPDWLRQ LV WUDQVIHUUHG WR &&06 DW WKLV SRLQW &XVWRPL]LQJ FDQ RQO\ JHQHUDWHG IRU EXVLQHVV SURFHVVHV PDUNHG DV SURGXFWLYH :KHQ \RX HQWHU WKH SDUW 2SHUDWLRQV RI \RXU VROXWLRQ DIWHU JHQHUDWLQJ PRQLWRULQJ FXVWRPL]LQJ IRU WKH ILUVW WLPH D %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ LV FUHDWHG IRU WKH UHVSHFWLYH EXVLQHVV SURFHVV 7KHUH LV RQH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ SHU EXVLQHVV SURFHVV 7KH PRVW FXUUHQW JHQHUDWHG FXVWRPL]LQJ LV FRQVLGHUHG IRU WKH DFWLYDWLRQ 07(V DUH FUHDWHG LQ &&06 ZLWK WKH $FWLYDWLRQ
SM100
11-48
:KHUH WR DFWLYDWH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ
,Q DUHD
2SHUDWLRQV
FKRRVH 6ROXWLRQ 0RQLWRULQJ %XVLQHVV 3URFHVV 0RQLWRULQJ
DQG FOLFN RQ WKH DOHUW LFRQ IRU WKH HQWLUH EXVLQHVV SURFHVV WR QDYLJDWH WR WKH PRQLWRULQJ VHVVLRQ
SAP AG 2006
The Business Process Monitoring is activated in the %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ. This session is available in the SAP Solution Manager only after the Customizing for the setup of the Business Process Monitoring has been generated.
While there is one 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ that includes all business processes there are several %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQV, one for each business process that is monitored.
SAP AG
SM100
11-49
6HWXS 3URFHGXUH %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU

"7'
SAP AG 2006
SAP AG
a' I')ogYQ
7'r w
Solution Manager:
W 1EYw"
Solution Manager:
W 1EYw"
7"7"
1b WEYw"
Solution Manager:
7 a Q'Yb7QUIg o"'
"IE7"fB ''7 Y
Q7 Ir
Satellite System
7 a Q'Yb7QUIg o"'
7 TE
1b WEYw"
Solution Manager:
g7g"'g gvTU7
Solution Manager:
W W f WQ
g"7#Q#u" '"Qog
7 a' "#YoI7
7171 W 7
Solution Manager:
' g 'bU7Ew
Solution Manager:
Wrg g"
SM100
11-50
)XQFWLRQDOLWLHV IRU %XVLQHVV 3URFHVV 0RQLWRULQJ

$XWRPDWLF HPDLO UHSRUWLQJ DQ DOHUW
,QWHJUDWHG RYHUYLHZ RI VWDWXV RI WKH HQWLUH VROXWLRQ VWDWXV IRU KDUGZDUH VRIWZDUH DQG EXVLQHVV SURFHVVHV LQ RQH VFUHHQ %XVLQHVV SURFHVV DOHUWV DVVRFLDWHG WR EXVLQHVV SURFHVV VWHSV 6\VWHP 0RQLWRULQJ DOHUWV DVVRFLDWHG WR XQGHUO\LQJ V\VWHPV
9LHZ RI RSHQ DOHUWV SUREOHPV ZKLFK KDYH QRW \HW EHHQ VROYHG &RQILUPDWLRQ RI DOHUWV WKDW KDYH EHHQ VROYHG
SAP AG 2006
Business Process Monitoring in SAP Solution Manager is integrated in several ways: If a business process has been implemented using SAP Solution Manager (i.e. the process description has been supplied in an implementation project ) you can use this process description as a basis for setting up Business Process Monitoring. In case of alerts, the monitoring employee can be notified via an automatic email. There is no need for him to constantly check the monitoring graphic in the solution manager to see if there is a problem. The real-time monitoring functionalities of Solution Manager are integrated with each other. The main monitoring graphic shows the overall status of the entire solution containing the hardware, the software components and the business processes.
SAP AG
SM100
11-51
)XQFWLRQDOLWLHV IRU %XVLQHVV 3URFHVV 0RQLWRULQJ

0DQXDO DQG DXWRPDWLF VHUYLFH GHVN PHVVDJHV IRU DOHUWV GLUHFW OLQN IURP WKH DOHUW KLVWRU\ RYHUYLHZ WR WKH VHUYLFH GHVN PHVVDJH
'LUHFW OLQN WR WUDQVDFWLRQV LQ WKH UHVSHFWLYH VDWHOOLWH V\VWHP WR DQDO\]H SUREOHP IXUWKHU 'LUHFW /LQN WR 85/V FRQWDLQLQJ KHOS PDQXDOV RUJDQL]DWLRQ FKDUWV RSHUDWLRQV KDQGERRNV HWF 7LJKWO\ LQWHJUDWHG LQWR VROXWLRQ VXSSRUW RUJDQL]DWLRQ E\ GRFXPHQWHG PRQLWRULQJ WDVNV DQG UHVSRQVLELOLWLHV
2SHQ&RQILUPHG DOHUWV LQWHJUDWHG LQWR 6HUYLFH /HYHO 5HSRUWLQJ
SAP AG 2006
Notification can also take place via automatic Service Desk messages in case of alerts. You can define how many alerts for one monitoring object should raise a message. For instance, you can define that only after a certain background job has been cancelled 4 times, a service desk message should be created. This service desk message can then be used to report the problem to the next support level. You can define links to any transaction in the monitored system. This way, the monitoring employee can access these systems for a problem analysis directly from Solution Manager. You can also define hyperlinks to access any kind of web site (for instance containing further business process information or error handling procedures). You can define monitoring tasks within SAP Solution Manager. This way, the monitoring employee always knows what his responsibilities are, what he has to do in case of problems and whom he should contact if he cant solve the problem. The alerts of Business process Monitoring are integrated into the Service Level Reporting of SAP Solution Manager. You can report over how many alerts have occurred and how many alerts have been solved in the reporting time span.
SAP AG
SM100
11-52
$OHUW +LHUDUFK\
0RQLWRULQJ LQ WKH 6$3 6ROXWLRQ 0DQDJHU LV UHDOL]HG YLD WKH GLVSOD\ RI DOHUWV 7KH IROORZLQJ DOHUWV DUH SRVVLEOH
KLJK $OHUW 9HU\ FULWLFDO VLWXDWLRQ 6WDWXV QRW GHILQHG &ULWLFDO VLWXDWLRQ :DUQLQJ &KHFNLQJ QHFHVVDU\ 2ND\ $FWLRQ UHTXLUHG $FWLRQ UHTXLUHG $QDO\VLV UHFRPPHQGHG 1R DFWLRQ UHTXLUHG
$OHUWV DUH XVXDOO\ FDOOHG E\ WKHLU FRORU LH JUHHQ \HOORZ JUD\ RU UHG DOHUW
SAP AG 2006
The alert definition inside the SAP Solution Manager is valid for all monitoring types. The rating enables focusing on critical systems, significant business processes, major process steps and interfaces. The alerts in the table are sorted by descending priority, meaning that an area containing green and yellow alerts will display a yellow summarization alert. Observe that a grey alert has a higher priority than a yellow alert!
SAP AG
3ULRULW\
ORZ
SM100
11-53
1RWLILFDWLRQ LQ &DVH RI $OHUW

iru f"uFf #v rFF "vik
SAP AG 2006
6XSSRUW (PSOR\HH
The support employee can be notified of automatically if an alert in the business process has occurred. Then, the support employee can check the alert in SAP Solution Manager.
SAP AG
SM100
iF FF
iF F|F
11-54
8VLQJ %XVLQHVV 3URFHVV 0RQLWRULQJ LQ WKH 6$3 6ROXWLRQ 0DQDJHU :KDW WR GR LI DQ DOHUW RFFXUUHG 'HWDLOV
2EVHUYH $OHUWV 5HODWLYH WR WKH %XVLQHVV 3URFHVV &KHFN 'HWDLOHG $OHUW ,QIRUPDWLRQ &KHFN IRU 2SHQ $OHUWV 5HYLHZ +LVWRULF $OHUWV $QDO\]H 3UREOHP LQ WKH 6DWHOOLWH 6\VWHP &UHDWH 6HUYLFH 'HVN 0HVVDJH &RQILUP $OHUWV IRU 6ROYHG 3UREOHPV
SAP AG 2006
:KLFK SDUW RI WKH EXVLQHVV SURFHVV LV DIIHFWHG E\ WKH SUREOHP" :KDW H[DFWO\ LV WKH SUREOHP ZKLFK MRE KDV FDQFHOOHG ZKLFK WUDQVDFWLRQ SHUIRUPV EDGO\" $UH WKHUH DQ\ SUREOHPV WKDW UHTXLUH XVHU LQWHUDFWLRQ RU KDV VRPHRQH DOUHDG\ VROYHG WKH SUREOHP" +DV WKH SUREOHP RFFXUUHG LQ WKH SDVW" :KDW LV WKH URRW FDXVH RI WKH SUREOHP" ,V LW SRVVLEOH IRU WKH ,72SHUDWRU WR VROYH WKH SUREOHP" ,I WKH SUREOHP FDQW EH VROYHG YLD WKH GHILQHG HUURU KDQGOLQJ SURFHGXUHV LW VKRXOG EH WUDQVIHUUHG WR WKH QH[W VXSSRUW OHYHO 2QFH WKH SUREOHP LV VROYHG WKH DOHUW VKRXOG EH PDUNHG DV VROYHG
SAP AG
SM100
11-55
)XUWKHU ,QIRUPDWLRQ DERXW %XVLQHVV 3URFHVV 0RQLWRULQJ
'RFXPHQWDWLRQ LV DYDLODEOH LQ TXLFNOLQN %30 LQ WKH 6$3 6HUYLFH 0DUNHWSODFH VHUYLFHVDSFRPESP
,PSRUWDQW GRFXPHQWV LQFOXGH
SAP AG 2006
There is a lot information available in the SAP Service Marketplace and in SAP Help on how to set up Business Process Monitoring in SAP Solution Manager. In Quicklink /BPM the starting documentation is the Business Process Monitoring Setup Roadmap. The roadmap details the methods used to set up Business Process Monitoring, detailing which tasks have to be executed in which order and in which part of SAP Solution Manager. It consists of about 40 MS PowerPoint Slides, linked by hyperlinks to allow better navigation. For the technical details about the various monitoring functionalities or the technical prerequisites for Business Process Monitoring you have to consult the Business Process Monitoring Setup Guide. This is a 80 page PDF document, covering all major monitoring functionalities in detail. All other monitoring functionalities are covered in detail in the Application Monitoring - Setup Guide. This is a continuously growing (because new monitoring functionalities are continuously developed) PDF document, detailing all of the application specific monitoring functionalities in Business Process Monitoring.
SAP AG
' & 1 v#w'F$ 4 " ' & 3v121Fr8FF wY7w6i#F v #vF 5
%XVLQHVV 3URFHVV 0RQLWRULQJ 6HWXS 5RDGPDS
' & 1 v#w'F$ " " ' F# ##u3r r ## Fvk2uf"# r "#'u)
$SSOLFDWLRQ 0RQLWRULQJ 6HWXS *XLGH
w#1 FFkr Y0f) urk(Fw& ' & ' $ " " vb% UF#r "F#r 1F'! v i#uuu Fif
%XVLQHVV 3URFHVV 0RQLWRULQJ 6HWXS *XLGH
SM100
11-56
8QLW 2EMHFWLYHV
8VH %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU DV DQ ,7 2SHUDWRU
8VH WKH VHWXS SURFHGXUH IRU %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU IRU WKH H[DPSOH RI XSGDWH HUURU PRQLWRULQJ
SAP AG 2006
SAP AG
SM100
11-57
/HVVRQ 6XPPDU\
8VH WKH EDVLF SURFHGXUHV WR VHW XS %XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
8QGHUVWDQG WKH PHDQLQJ RI %XVLQHVV 3URFHVV 0RQLWRULQJ DV SDUW RI D %XVLQHVV ,QWHJUDWLRQ DQG $XWRPDWLRQ FRQFHSW
SAP AG 2006
SAP AG
SM100
11-58

SAP AG
SM100
11-59
$SSHQGL[
SAP AG 2006
SAP AG
SM100
11-60
6RIWZDUH &KDQJH 0DQDJHPHQW

Business Process 1
Business Process 2
Business Process 3
Business Process 4
5ROH
User Help Desk
Application Support Basis/mySAP Technology Support Systems Support (HW, OS, DB, Network, Frontends)
5HVSRQVLELOLWLHV
'HGLFDWHG WHDP LQ WKH FXVWRPHUV 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ ZLWK GHYHORSPHQW DQG SURJUDPPLQJ VNLOOV PLJKW EH D GLYLVLRQ RI WKH ,7 'HSDUWPHQW RULJLQDWHG IURP WKH IRUPHU ,PSOHPHQWDWLRQ 3URMHFW 7HDP &XVWRPL]LQJ FKDQJHV
6RIWZDUH &KDQJH 0DQDJHPHQW
SAP AG 2006
SAP AG
G DS PH D QB U QDRGV UT DQRG EI FG EC B @A 9
&KDQJHV WR EXVLQHVV SURFHVVHV FRGLQJ 'HYHORSPHQW WDVNV SURJUDPPLQJ 6$3 1RWH LPSOHPHQWDWLRQ EDVLV DSSOLFDWLRQ 1HZ LPSOHPHQWDWLRQ RU PLJUDWLRQ SURMHFWV
3URMHFWV UHJDUGLQJ DQ\ NLQG RI FKDQJH PDQDJHPHQW
SM100
11-61
8VHU +HOS 'HVN

Business Process 1
Business Process 2
Business Process 3
Business Process 4
5ROH
W W
Software Change Management
/HYHO (QG8VHU 6XSSRUW

X X
Application Support Basis/mySAP Technology Support Systems Support (HW, OS, DB, Network, Frontends)
SAP AG 2006
SAP AG
d G`f ec b aG Y`GF
5HVSRQVLELOLWLHV
$XWRQRPRXV GLYLVLRQ ZLWKLQ WKH FXVWRPHUV 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ /HYHO 6XSSRUW 6$3 1RWH VHDUFK 8VLQJ D NLQG RI VROXWLRQ GDWDEDVH 3UREOHP GLVSDWFKLQJ
SM100
11-62
$SSOLFDWLRQ 6XSSRUW
Business Process 1
Business Process 2
Business Process 3
Business Process 4
5ROH
Software Change Management User Help Desk
%XVLQHVV 3URFHVV 0DQDJHPHQW DQG 0RQLWRULQJ
Basis/mySAP Technology Support Systems Support (HW, OS, DB, Network, Frontends)
5HVSRQVLELOLWLHV
'HGLFDWHG WHDP LQ WKH FXVWRPHUV 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ ZLWK VLJQLILFDQW DSSOLFDWLRQ NQRZKRZ PLJKW EH DOVR D GLYLVLRQ RI WKH ,7 'HSDUWPHQW %XVLQHVV 3URFHVV 0DQDJHPHQW LQFOXGLQJ WKH PRQLWRULQJ RI 3URJUDP 6FKHGXOLQJ 0DQDJHPHQW
h
3HUIRUPDQFH EDFNJURXQG MREV HUURU ORJV
SAP AG 2006
Application Support includes the monitoring of application relevant IDocs (as opposed to all IDocs) application relevant background jobs (as opposed to all background jobs) ...
SAP AG
9 FB scc@ UQ @ DBq r q cb pi c
,QWHUIDFH 0RQLWRULQJ IURP D IXQFWLRQDO YLHZSRLQW /HYHO 6XSSRUW
SM100
11-63
%DVLVP\6$3 7HFKQRORJ\ 6XSSRUW

Business Process 1
Business Process 2
Business Process 3
Business Process 4
5ROH
Software Change Management User Help Desk Application Support
%DVLVP\6$3 7HFKQRORJ\ 6XSSRUW 'LYLVLRQ RI WKH ,7 'HSDUWPHQW
Systems Support (HW, OS, DB, Network, Frontends)
3URJUDP 6FKHGXOLQJ 0DQDJHPHQW

h
,QWHUIDFH 0RQLWRULQJ IURP D WHFKQLFDO YLHZSRLQW

g
/HYHO 6XSSRUW
SAP AG 2006
Basis/mySAP technology Support includes the monitoring of basis relevant IDocs (as opposed to all IDocs) basis relevant background jobs (as opposed to all background jobs) ...
SAP AG
'feUpEF'eu' vi"!#vb#'uf x d & $ y uF'IF uv#ux & x 3%e& 4 'w8707' 4 8 & ' & $ $ & $ y " u x & u #F#'r#|FIi'63 rv3vwwv
B F scc@ T Ri @ GrPQ@b 9
kj i eT 9i IV h ` D`q g
5HVSRQVLELOLWLHV
$GPLQLVWUDWLRQ VXSSRUW DQG PRQLWRULQJ RI

3HUIRUPDQFH HUURU ORJV DQG PHPRU\ PDQDJHPHQW RI
SM100
11-64
6\VWHPV 6XSSRUW
Business Process 1
Business Process 2
Business Process 3
Business Process 4
5ROH
Software Change Management User Help Desk Application Support Basis/mySAP Technology Support
6\VWHPV 6XSSRUW +: 26 '% 1HWZRUN )URQWHQGV 'LYLVLRQ RI WKH ,7 'HSDUWPHQW
SAP AG 2006
SAP AG
QBGQr`s
@ g 9n F@ Ffnq E npGBC E nd Eo lam B F scc@ UU 9i`BGV 9`
5HVSRQVLELOLWLHV
$GPLQLVWUDWLRQ 6XSSRUW DQG 0RQLWRULQJ RI

6\VWHPVKDUGZDUH 'DWDEDVH 1HWZRUN 2SHUDWLQJ V\VWHP )URQWHQGV
([WHUQDO WRROV
/HYHO 6XSSRUW
SM100
11-65
%XVLQHVV 3URFHVV 2ZQHU %XVLQHVV 'HSDUWPHQW

Business Process 1 Business Process 2 Business Process 3 Business Process 4
5ROH
Software Change Management User Help Desk Application Support Basis/mySAP Technology Support
Systems Support (HW, OS, DB, Network, Frontends)
SAP AG 2006
SAP AG
xv v | yv y x}w | z{ tuv ~w
xv v| yv y x} w | z{ tuv ~w
xv v | yv y x} w w | z{ tuv ~
xv v| yv y x} w | z{ tuv ~w
5HVSRQVLEOH IRU WKH DSSOLFDWLRQ IORZ RI D EXVLQHVV SURFHVV
5HVSRQVLELOLWLHV
1RPLQDWHG IURPE\ WKH EXVLQHVV GHSDUWPHQW 6HUYH DV FRQWDFW IRU WKH $SSOLFDWLRQ 6XSSRUW
7KH EXVLQHVV GHSDUWPHQWV PXVW RSHUDWH WKH DSSOLFDWLRQ LQ DFFRUGDQFH ZLWK GHILQHG RSHUDWLQJ SURFHGXUHV
0DQDJLQJ TXDOLW\ DVVXUDQFH IRU WKH HQWLUH SURFHVV
$GMXVWLQJ WKH PRQLWRULQJ DQG HVFDODWLRQ PHDVXUHV IRU PRGLILFDWLRQV WR WKH SURFHVV &RRUGLQDWLQJ RI DOO SURFHVV DFWLYLWLHV LQ WKH V\VWHP 'HILQLQJ WKH HVFDODWLRQ SDWK IRU SUREOHP UHVROXWLRQ
0DLQWDLQLQJ WKH DSSOLFDWLRQ RULHQWHG SURFHVV GHVFULSWLRQ
SM100
11-66
$SSHQGL[
SAP AG 2006
SAP AG
SM100
11-67

'
Interface to CRM or SRM System Interface to external tax calculation software (e.g., for the US and Canada, Vertex) Interface to external credit card software
Create Sales Order
Execution mode(s) Document volume (average number of documents, average number of line items per document) Time restrictions, peak time windows
Dialog transaction (VA01) Background job (RBDAPP01)
ALE / EDI (IDocs) Batch input Direct input Tele sales or rush orders (delivery is created in combination with the Custom transaction or program sales order)?
SAP AG 2006
For each business process step you need to gather the generic and application specific information. In our example, the sales order that was created on the CRM system is sent via an IDOC interface to the SAP R/3 system. There a respective sales order is created during the business process step Create Sales Order , using either dialog transaction VA01 or program RBDAPP01 as a background job. Normally, about 1000 sales orders with in average of 3 items per sales order are created per day.
SAP AG
SM100
ev
ppT v
g g X T g 1h
IeEv
eW ! h X p8 I 4 0r & !eg g g X h X T8 v v X p8 W W W ! W h X
v h W
IIvUE7E v
v X p8 pU
' 4
11-68
$VVLJQ /RJLFDO &RPSRQHQWV WR WKH 6ROXWLRQ

%XVLQHVV 3URFHVVHV DUH H[HFXWHG RQ ORJLFDO FRPSRQHQWV %HIRUH \RX FDQ PDLQWDLQ D EXVLQHVV SURFHVV \RX WKHUHIRUH KDYH WR DVVLJQ WKH FRQFHUQHG ORJLFDO FRPSRQHQWV WR WKH VROXWLRQ ODQGVFDSH
&KRRVH QRGH VROXWLRQ QDPH!
$VVLJQ ORJLFDO FRPSRQHQWV LQ WDE 6\VWHP *URXS YLD YDOXH KHOS
SAP AG 2006
In node VROXWLRQ QDPH> you can also change the solution settings (tab Solution Settings ) like what day of the week the Early Watch Alert data is supposed to be processed and for what systems the EWA should be processed within this solution.
SAP AG
SM100
11-69
&KRRVH %XVLQHVV 6FHQDULR

$IWHU KDYLQJ DVVLJQHG WKH ORJLFDO FRPSRQHQWV PDLQWDLQ WKH EXVLQHVV VFHQDULR IRU WKH EXVLQHVV SURFHVV RI WKH VROXWLRQ &KRRVH QRGH VROXWLRQ QDPH! EXVLQHVV VFHQDULRV LQ WKH WUHH &UHDWH WKH EXVLQHVV VFHQDULR LQ WDE 6WUXFWXUH
&UHDWH %XVLQHVV 6FHQDULR
SAP AG 2006
You can only set the scenario to Production if all business processes of the scenario are in status Production .
SAP AG
SM100
11-70
&UHDWH %XVLQHVV 3URFHVV

)RU HDFK EXVLQHVV VFHQDULR FUHDWH WKH UHVSHFWLYH EXVLQHVV SURFHVVHV &KRRVH VROXWLRQ QDPH! %XVLQHVV 6FHQDULRV VFHQDULR QDPH! %XVLQHVV 3URFHVVHV LQ WKH WUHH DQG FUHDWH WKH EXVLQHVV SURFHVVHV LQ WDE 6WUXFWXUH
6HW VWDWXV WR 3URGXFWLRQ &UHDWH EXVLQHVV SURFHVVHV
SAP AG 2006
Set the status for the business process to Production if you want to monitor the business process. This is only possible if there is a production system assigned to the logical components the business process is using.
SAP AG
SM100
11-71
&RS\ %XVLQHVV 3URFHVV

<RX FDQ DOVR FRS\ EXVLQHVV SURFHVVHV PDLQWDLQHG LQ DQ\ LPSOHPHQWDWLRQ SURMHFW RI 6$3 6ROXWLRQ 0DQDJHU RU DQ\ RWKHU VROXWLRQ ,Q DGGLWLRQ WKH EXVLQHVV SURFHVV UHSRVLWRU\ SURYLGHV \RX ZLWK D WHPSODWH OLEUDU\ RI VWDQGDUG EXVLQHVV SURFHVVHV
SAP AG 2006
If no appropriate logical components have been assigned to the solution to fit the business process the system assigns these components automatically when saving the process. However, in this case it is not possible to choose between different logical components of the same product. In addition to business process steps, processing information like transactions or reports is copied if this information has been maintained in the original business process.
SAP AG
SM100
11-72
&UHDWH %XVLQHVV 3URFHVV 6WHSV

)RU HDFK EXVLQHVV SURFHVV FUHDWH WKH UHVSHFWLYH EXVLQHVV SURFHVV VWHSV DQG GHILQH RQ ZKDW ORJLFDO FRPSRQHQW WKH VWHS LV VXSSRVHG WR UXQ &KRRVH VROXWLRQ QDPH! %XVLQHVV 6FHQDULRV VFHQDULR QDPH! %XVLQHVV 3URFHVVHV SURFHVV QDPH! LQ WKH WUHH DQG FUHDWH WKH VWHSV LQ WDE 6WUXFWXUH &UHDWH EXVLQHVV SURFHVV VWHSV
$VVLJQ ORJLFDO FRPSRQHQW YLD YDOXH KHOS

SAP AG 2006
You can also assign processing types for the business process steps at this point. This information can you specify even more in detail (which program, which transaction) in the nodes for the respective business process steps. In order to set up Business Process Monitoring in the SAP Solution Manager you do not have to specify this information here.
SAP AG
SM100
11-73
$UUDQJH 3URFHVV *UDSKLF DQG &UHDWH 3URFHVV )ORZV

,Q WKH VDPH QRGH ZKHUH WKH EXVLQHVV SURFHVV VWHSV DUH FUHDWHG \RX FDQ GRFXPHQW WKH IORZ DQG FKDQJH WKH JUDSKLFDO OD\RXW RI WKH EXVLQHVV SURFHVV &KRRVH WDE *UDSKLF 5LJKW PRXVH FOLFN RQ WKH SUHFHGLQJ VWHS
&KDQJH JUDSKLFDO OD\RXW YLD GUDJ GURS
SAP AG 2006
Asynchronous line: Line leaves the box through the top or bottom of the box. Synchronous line: Line leaves the box through one of the sides.
SAP AG
SM100
11-74
6SHFLI\ 3URFHVVLQJ 'HWDLOV

,Q QRGH EXVLQHVV SURFHVV VWHS! LQ WDE 7UDQVDFWLRQV \RX FDQ DVVLJQ SURFHVVLQJ LQIRUPDWLRQ IRU WKH UHVSHFWLYH EXVLQHVV SURFHVV VWHS 7KLV LQFOXGHV UHSRUWV WUDQVDFWLRQV 85/V HWF
SAP AG 2006
You can use the information you have entered here later on as basis for Business Process Monitoring or Service Level Reporting in SAP Solution Manager.
SAP AG
SM100
11-75
$SSHQGL[
%XVLQHVV 3URFHVV 0RQLWRULQJ LQ 6$3 6ROXWLRQ 0DQDJHU
SAP AG 2006
SAP AG
SM100
11-76
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
SAP AG
SAP AG 2006
In order to later on assign persons to certain monitoring tasks you have to group these persons into teams first. You can create as many teams as you wish.
'HILQH 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ
7KH 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ LV GHILQHG LQ QRGH 6ROXWLRQ 6XSSRUW 2UJDQL]DWLRQ DQG WKH VXEQRGHV FUHDWHG IRU HDFK PRQLWRULQJ WHDP LQ WKH VHVVLRQ WUHH
SM100
6SHFLI\ WKH PRQLWRULQJ WHDPV ZKLFK WDNH SDUW LQ WKH %XVLQHVV 3URFHVV 0RQLWRULQJ FRQFHSW
11-77
$VVLJQ 0HPEHUV WR 6XSSRUW 7HDP

0HPEHUV IRU WKH WHDPV DQG WKH PRQLWRULQJ UROHV IRU WKH WHDPV DUH GHILQHG LQ QRGH 7HDP PRQLWRULQJ WHDP QDPH!
,Q WDE 7HDP 0HPEHUV DVVLJQ PHPEHUV WR WKH PRQLWRULQJ WHDP YLD WKH YDOXH KHOS
,Q WDE 0RQLWRULQJ 5ROHV VSHFLI\ WKH UROHV RI HDFK PRQLWRULQJ WHDP
SAP AG 2006
For the newly created teams you can assign team members. Observe that team members can only be assigned via the value help. In order to create new members of the support organization you have to go to the Solution Landscape Maintenance in the Operations Setup area of the SAP Solution Manager. This is covered in Level 1 of the E2E Training. For each team you can assign monitoring roles. All of this is for documentation purpose only.
SAP AG
SM100
11-78
&KRRVH %XVLQHVV 3URFHVV WR EH 0RQLWRUHG

,Q QRGH %XVLQHVV 3URFHVVHV FKRRVH ZKLFK RI WKH EXVLQHVV SURFHVVHV GRFXPHQWHG IRU WKH VROXWLRQ VKRXOG EH PRQLWRUHG
SAP AG 2006
SAP AG
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
)ODJ 0RQLWRULQJ
IRU WKH EXVLQHVV SURFHVVHV \RX ZDQW WR PRQLWRU
The business scenario has to be in status 3URGXFWLRQ before you can activate the monitoring for a process. If the flag 3ODQQHG for the business process is set this means that you can set up the monitoring customizing but you will not be able to really activate the monitoring to get alerts. So if you see this flag, go back to the 6ROXWLRQ /DQGVFDSH 0DLQWHQDQFH and change the settings for the business scenario. Details for this can be found in the 1st level of the E2E training. For each of the business processes maintained in the solution landscape you now have to specify if they or parts of them should be monitored.
SM100
11-79
&KRRVH %XVLQHVV 3URFHVV 6WHSV WR EH 0RQLWRUHG

)RU HDFK EXVLQHVV SURFHVV \RX FDQ QRZ FKRRVH ZKLFK EXVLQHVV SURFHVV VWHSV DUH VXSSRVHG WR EH PRQLWRUHG &KRRVH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! LQ WKH VHVVLRQ WUHH DQG PDUN WKH VWHSV LQ WDE 6WHSV RI %XVLQHVV 3URFHVV
&KRRVH WKH EXVLQHVV SURFHVV VWHSV WR EH PRQLWRUHG
&OLHQW LQIRUPDWLRQ
SAP AG 2006
You can choose any number of business process steps to be monitored. When you save, sub-nodes for the selected business process steps as well as for the maintenance of interfaces are created within the session.
Node %30RQ SURFHVV QDPH! contains also a tab where you can document the restart procedure for the business process.
SAP AG
SM100
11-80
'HILQH 0RQLWRULQJ 2EMHFWV SHU %XVLQHVV 3URFHVV 6WHS

&KRRVH IRU HDFK EXVLQHVV SURFHVV VWHS LQ QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! 6,'! ZKLFK DUHDV VKRXOG EH PRQLWRUHG WR HQVXUH WKH VPRRWK UXQQLQJ RI WKH EXVLQHVV SURFHVV
SAP AG 2006
SAP AG
!22 22 3 E! 3 E 2 8 ! E!EE E ! 2 !!22 ! 3 U!!p E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
&KRRVH WKH PRQLWRULQJ W\SHV UHOHYDQW IRU WKH EXVLQHVV SURFHVV VWHS
The monitoring type can contain more than one monitoring functionality.
Monitoring Type $SSOLFDWLRQ 0RQLWRU contains an ever growing number of monitoring objects, both cross application relevant (for instance monitoring of dialog performance on function code level) and application relevant (for instance MRP run monitor, warehouse monitor, APO Demand Planning log monitor etc.). When saving, the respective sub-nodes are created for the selected monitoring types.
SM100
11-81
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
SAP AG

SAP AG 2006
Technical details include name and scheduling information of background jobs, name of transactions that should be monitored, object and sub-object of the application log to be monitored etc.
Purpose of the technical information is to identify exactly the technical object that should be monitored.
3HU 0RQLWRULQJ 2EMHFW 3URYLGH 7HFKQLFDO 'HWDLOV
3URYLGH WHFKQLFDO GHWDLOV IRU HDFK PRQLWRULQJ W\SH LQ QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! PRQLWRULQJ W\SH! LQ WKH VHVVLRQ WUHH
SM100
3URYLGH WHFKQLFDO GHWDLOV
11-82
3HU 0RQLWRULQJ 2EMHFW 'HILQH 7KUHVKROGV

'HILQH WKUHVKROGV IRU WKH PRQLWRULQJ REMHFWV LQ WKH VXEQRGHV WR QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! PRQLWRULQJ W\SH! LQ WKH VHVVLRQ WUHH 'HILQH DOHUW WKUHVKROGV
SAP AG 2006
Depending on the monitoring type there are different nodes in the session tree where the alert thresholds can be defined. During the monitoring, alerts can have the statuses green, yellow and red (pretty much like a traffic light). Some alerts are status alerts. These alerts are raised if a certain status is reached for a technical object, for instance if a job cancels. For these, you dont have to specify thresholds but instead define which alert should be raised if the status is reached.
SAP AG
SM100
11-83
3HU 0RQLWRULQJ 2EMHFW $VVLJQ 0RQLWRULQJ 7UDQVDFWLRQV

,Q QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! 0RQLWRULQJ 7UDQVDFWLRQV \RX FDQ DVVLJQ WUDQVDFWLRQV WR WKH PRQLWRULQJ W\SH WKDW VKRXOG EH XVHG IRU WKH IXUWKHU DQDO\VLV RI SUREOHPV LQ FDVH RI DQ DOHUW
SAP AG 2006
SAP AG
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
$VVLJQ GHOHWH RU LQVHUW PRQLWRULQJ WUDQVDFWLRQV
The monitoring transactions defined here will appear as direct links from the SAP Solution Manager to the satellite system during the handling of the monitoring, enabling you to jump directly from an alert in the Solution Manager into the transaction in the respective satellite system. Monitoring transactions may include customer written transactions. In particular, there is no crosschecking if the entered transactions make sense for the respective monitoring type or if they exist at all. Transactions can be called on the satellite system or directly on the SAP Solution Manager system.
SM100
11-84
3HU 0RQLWRULQJ 2EMHFW $VVLJQ 0RQLWRULQJ 85/V

,Q QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! 0RQLWRULQJ 7UDQVDFWLRQV \RX FDQ DVVLJQ 85/V WR WKH PRQLWRULQJ W\SH WKDW VKRXOG EH XVHG IRU WKH IXUWKHU DQDO\VLV RI SUREOHPV LQ FDVH RI DQ DOHUW
SAP AG 2006
SAP AG
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
$VVLJQ GHOHWH RU LQVHUW 85/V IRU IXUWKHU DQDO\VLV
The URLs defined here will appear as direct links from the SAP Solution Manager to the Internet during the handling of the monitoring, enabling you to jump directly from an alert in the Solution Manager into the respective web page where further information regarding the monitoring object could be provided, i.e. further paths to analyze the problem or a knowledge database in the intranet where you can check for repetitive problems. As well as for the monitoring transactions, there is no cross-checking if the entered URLs make sense for the respective monitoring type or if they exist at all.
SM100
11-85
3HU 0RQLWRULQJ 2EMHFW 6HW XS 0RQLWRULQJ 7DVNV

1RGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! 0RQLWRULQJ $FWLYLWLHV SURYLGHV WKH SRVVLELOLW\ WR GHILQH DFWLYLWLHV VRUWHG E\ WKH PRQLWRULQJ REMHFWV WKDW KDYH WR EH FDUULHG RXW LQ WKH UHJXODU PRQLWRULQJ RI WKH EXVLQHVV SURFHVVHV
SAP AG 2006
SAP AG
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
With the persons you have assigned to monitoring teams during the definition of the solution support organization you now can define responsibles for the monitoring of the customized monitoring objects. You can specify what exactly each person has to do for monitoring and what has to be done with alerts. The monitoring activities you have defined here you can later on generate into a MSWord Report, detailing for each team which monitoring activities the respective team is responsible for.
SM100
11-86
6HW XS 0RQLWRULQJ $FWLYLWLHV

7KH IROORZLQJ LQIRUPDWLRQ FDQ EH PDLQWDLQHG
:KR LV VXSSRVHG WR PRQLWRU WHDP DQG SHUVRQ +RZ RIWHQ LV VXSSRVHG WR EH PRQLWRUHG VWDUWLQJ ZKHQ IUHTXHQF\ DQG VWDUW WLPH :KDW GRHV D SUREOHP LQGLFDWH SUREOHP LQGLFDWRUV :KDW KDV WR EH GRQH LQ FDVH RI D SUREOHP HUURU KDQGOLQJ :KR KDV WR EH FRQWDFWHG LI WKH SUREOHP FDQW EH VROYHG HVFDODWLRQ SDWK 'HILQH DQG GHVFULEH
WKH PRQLWRULQJ DFWLYLWLHV HUURU KDQGOLQJ UHVWDUW RI WKH VWHS DQG HVFDODWLRQ SDWKV
SAP AG 2006
In the table
0RQLWRULQJ $FWLYLWLHV
it is possible to specify: Monitoring Team: Use the value help. The teams provided there have to have been defined before in the check
. Person Resp.: Use the value help. The members of the monitoring teams have to have been specified before. Frequency: Use the value help to specify at what frequency the specific monitoring activity is required. Start Time: Specify at what time the required monitoring activity should start. Problem Indicator: Describe, in a few words, what indicates a problem or error. Error Handling: Briefly describe the way how to react in case of problems or errors, i.e. how to solve the problem/correct the error Escalation Path: Succinctly specify how to proceed, if the problem cannot be solved by the person responsible.
SAP AG
SM100
11-87
3HU 0RQLWRULQJ 2EMHFW &RQILJXUH $XWRPDWLF (PDLOV DQG 6HUYLFH 'HVN 0HVVDJHV <RX FDQ VHW XS QRWLILFDWLRQV HPDLOV RU 6HUYLFH 'HVN PHVVDJHV WR EH VHQW LQ FDVH RI DOHUWV LQ QRGH %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! 6WHS VWHS QDPH! 1RWLILFDWLRQV RI WKH VHVVLRQ WUHH 3UHUHTXLVLWHV IRU WKH QRWLILFDWLRQV WR ZRUN DUH $XWRPDWLF HPDLO
7UDQVDFWLRQ 6&27 KDV EHHQ VHW XS LQ FOLHQW RI WKH 6$3 6ROXWLRQ 0DQDJHU V\VWHP
SAP AG 2006
SAP AG
!!22 !2 E! 2 ! p2! E E 2 2 ! ! !!22 ! U! E 2! 2! ! 2 E2 2 % 2! 2! 2! !2 v ! E!
([LVWLQJ XVHU LQ FOLHQW RI WKH 6$3 6ROXWLRQ 0DQDJHU V\VWHP WKDW KDV D YDOLG HPDLO DGGUHVV DVVLJQHG
$XWRPDWLF 6HUYLFH 'HVN PHVVDJH
%XVLQHVV 3DUWQHUV LQ UROH 3HUVRQ DQG (PSOR\HH KDYH WR H[LVW IRU WKH UHVSHFWLYH LQVWDOOHG EDVH RQ 6$3 6ROXWLRQ 0DQDJHU
6HUYLFH 'HVN KDV EHHQ VHW XS LQ WKH 6$3 6ROXWLRQ 0DQDJHU
7KHVH SUHUHTXLVLWHV ZHUH PHQWLRQHG EHIRUH DV DGYDQFHG SUHUHTXLVLWHV IRU %XVLQHVV 3URFHVV 0RQLWRULQJ
You can also set up automatic notifications to be sent for the whole business process in node %XVLQHVV 3URFHVVHV %30RQ SURFHVV QDPH! %30RQ 1RWLILFDWLRQV Notifications set up here in this node will be overwritten if you specify different notification settings on business process step level. If you leave the settings on step level empty, the settings for the whole business process will be taken into account. Please observe that for SAP Office Notifications (meaning emails and SAP Office mails) each one alert triggers one notification, whilst for Service Desk messages you can specify which number of yellow or red alerts should trigger a message creation. The prerequisites are contained in lesson 3 of this unit as advanced prerequisites. The sending of notifications is triggered by the execution of certain coding which is executed periodically. Due to the period there can be a slight time difference between the occurrence of an alert and the notification being sent.
SM100
11-88
6HW XS $XWRPDWLF 1RWLILFDWLRQV

,Q WDE :RUNIORZ 1RWLILFDWLRQV \RX FDQ VHW XS DXWRPDWLF QRWLILFDWLRQV WR EH VHQW YLD 6$3 2IILFH 7KH UHFLSLHQW W\SH FDQ EH FKRVHQ YLD WKH YDOXH KHOS 3RVVLEOH DUH
(DFK DOHUW IRU WKH PRQLWRULQJ W\SH ZLOO WULJJHU D QRWLILFDWLRQ WR EH VHQW
b 03 2v) !8 !BIV t& 0aIByWPBx3 b ) w ) WIt R BBx3 w ) Iq R BB 2 R Wq w ) pWB R WU 3w v u h s r p i h f e c DBI9tqDgPd bXaB03B0Y ! R 'XD" H ` " 4 2 S S S ) 8 IT T3B!AQ3 R H #I1G ) 0C F WVCU 4 2 " DQP
SAP AG 2006
Email Address: Specify sender (user from client 000 with valid email address) Specify valid email address as recipient address Recipient type U
0RELOH 1XPEHU
6SHFLI\ VHQGHU XVHU IURP FOLHQW ZLWK YDOLG HPDLO DGGUHVV 6SHFLI\ WKH PRELOH QXPEHU DV IROORZV 606 5HFLSLHQW W\SH . Local SAP Office Mail Specify sender (user from client 000) Specify user name as recipient address Recipient type B
Remote SAP Office Mail Specify sender (user from client 000) Specify user name as recipient address Specify Target System ID and Target Client Specify Recipient type R
SAP AG
p3) !E8D753CBA3 8 6 4 2 " @ T3#) !985675310 8 4 2 " ) ( p3 p(

& " " '%$#!
SM100
11-89
6HW XS $XWRPDWLF 6HUYLFH 'HVN 0HVVDJHV

,Q WDE 6HUYLFH 'HVN 0HVVDJHV \RX FDQ VHW XS DXWRPDWLF PHVVDJHV WR EH VHQW WR WKH 6HUYLFH 'HVN RI WKH 6$3 6ROXWLRQ 0DQDJHU 6SHFLI\ WKH IROORZLQJ
ICX!
SAP AG 2006
Only if you want the messages to be sent automatically do you have to specify the reporter and the number of yellow and red alerts that should trigger the sending of the message. The text template is disregarded for automatic messages. For manually created messages the text template helps the you to provide the correct information to the service desk employee.
SAP AG
8 WVTI F I F &ÌA)WVP xP W!#WIx8 G ) 4 & BIIVA#!W Wt3yW3 ` ` G @ ` G 0WI#VW) C!C R R ` 8 H 4 BIYIBBy 2 8
SM100
%\ PDUNLQJ $XWRPDWLF WKH PHVVDJH ZLOO EH VHQW DXWRPDWLFDOO\ ,Q WKLV FDVH \RX QHHG WR VSHFLI\ ZKDW QXPEHU RI \HOORZ RU UHG DOHUWV VKRXOG WULJJHU WKH FUHDWLRQ RI D 6HUYLFH 'HVN PHVVDJH
11-90
$SSHQGL[
*HQHUDWH $FWLYDWH
SAP AG 2006
SAP AG
SM100
11-91
*HQHUDWH 0RQLWRULQJ &XVWRPL]LQJ

qgtaga3
SAP AG 2006
&KRRVH
*HQHUDWH &XVWRPL]LQJ
*HQHUDWLRQ LQIRUPDWLRQ LV GLVSOD\HG LQ WKLV DUHD
This is the very last step before activating the monitoring. The Customizing must be generated individually for each business process that is to be monitored. Once you generated the Customizing for a particular business process, a so-called Business Process Monitoring <business process name> Session will be created (i.e., you will get a single Business Process Monitoring Session per business process in the Operations section of the SAP Solution Manager). When Customizing is generated, generation information is displayed in table area of this check, including error messages (E) in case of a failed Customizing generation. The generation of the customizing takes place on the SAP Solution Manager system. During the generation of the customizing the following takes place: 1. The customizing information is written into tables in the SAP Solution Manager. 2. The Business Process Monitoring Session is created.
No data is passed to the satellite systems at this stage. Customizing can be generated only for business processes that have been set to productive. Otherwise the generation of the Customizing is just simulated. You can set the business process productive in the 2SHUDWLRQV 6HWXS section. Go to 6ROXWLRQ /DQGVFDSH 6ROXWLRQ /DQGVFDSH Maintenance, navigate to the scenario level and there choose
6HW WR SURGXFWLYH . The same should be done on business process level.
SAP AG
#g T
$IWHU WKH %XVLQHVV 3URFHVV 0RQLWRULQJ KDV EHHQ VHW XS WKH &XVWRPL]LQJ KDV WR EH JHQHUDWHG LQ RUGHU WR FUHDWH WKH %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ LQ WKH 6$3 6ROXWLRQ 0DQDJHU
SM100
11-92
'DWD &ROOHFWRU )UHTXHQFLHV
6SHFLI\ WKH PRQLWRULQJ LQWHUYDOV IRU WKH GLIIHUHQW PRQLWRULQJ W\SHV 7KH GLIIHUHQW PRQLWRULQJ W\SHV DUH PRQLWRUHG YLD GLIIHUHQW GDWD FROOHFWRUV <RX FDQ VSHFLI\ GLIIHUHQW PRQLWRULQJ LQWHUYDOV IRU WKH GLIIHUHQW W\SHV
SAP AG 2006
SAP AG
SM100
11-93
%XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ

qgtaga3
SAP AG 2006
The Business Process Monitoring is activated in the %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ. This session is available in the SAP Solution Manager only after the Customizing for the setup of the Business Process Monitoring has been generated.
While there is one 6HWXS %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ that includes all business processes there are several %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQV, one for each business process that is monitored.
SAP AG
#g T
,Q DUHD
2SHUDWLRQV
FKRRVH 6ROXWLRQ 0RQLWRULQJ %XVLQHVV 3URFHVV 0RQLWRULQJ
DQG FOLFN RQ WKH DOHUW LFRQ IRU WKH HQWLUH EXVLQHVV SURFHVV WR QDYLJDWH WR WKH PRQLWRULQJ VHVVLRQ
SM100
11-94

7KH VHVVLRQ WUHH RI WKH %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ FRQWDLQV MXVW WKH QRGH $FWLYDWLRQ ZKHQ QR PRQLWRULQJ LV DFWLYH 7KLV QRGH KDV VHYHUDO WDEOHV 3URWRFRO 0RQLWRULQJ 'DWD 5HWHQWLRQ 7LPHV $OHUW 0VJ /DQJXDJH 7LPH )UDPH -RE 0RQLWRULQJ 5HSRUW
SAP AG 2006
SAP AG
SM100
11-95
6HWWLQJV EHIRUH $FWLYDWLQJ WKH 0RQLWRULQJ
6HW WKH ODQJXDJH IRU WKH DOHUW PHVVDJHV
&KRRVH KRZ PDQ\ GD\V PRQLWRULQJ GDWD VKRXOG EH VWRUHG RQ WKH 6$3 6ROXWLRQ 0DQDJHU 6\VWHP DQG WKH DJJUHJDWLRQ SURFHGXUHV RI WKRVH GDWD
SAP AG 2006
Alerts for monitoring types will be stored in the Business Process Monitoring Session once the monitoring is activated. In order to minimize the amount of data that has to be held there you have to specify the storage time for the data in the session. Reorganization takes place automatically every time you enter the Business Process Monitoring Session. Aggregated alerts are not deleted since they are used for Service Level Reporting.
SAP AG
SM100
11-96
$FWLYDWH 0RQLWRULQJ
&KRRVH WR DFWLYDWH %XVLQHVV 3URFHVV 0RQLWRULQJ
SAP AG 2006
Before Business Process Monitoring can be performed it has to be activated in the SAP Solution Manager. Since separate %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQV exist for the different business processes the monitoring can be activate/deactivated separately for each business process. During the activation of the Business Process Monitoring the following takes place: 1. The customizing is transferred into the satellite systems. 2. Monitoring Tree Elements (MTEs) are created in the RZ20. 3. Data collectors are initialized and started.
SAP AG
SM100
11-97
$FWLYDWLRQ 3URWRFRO DQG 'HDFWLYDWLRQ

6XE QRGHV KDYH EHHQ FUHDWHG LQ WKH VHVVLRQ WUHH )RU EXVLQHVV SURFHVVHV ZLWK DFWLYDWHG PRQLWRULQJ \RX FDQ GHDFWLYDWH WKH PRQLWRULQJ KHUH
,GHDOO\ WKH SURWRFRO FRQWDLQV MXVW WKH LQIRUPDWLRQ DERXW ZKR ODVW DFWLYDWHG ZKHQ
SAP AG 2006
In case of error messages in the protocols for Generation or Activation check SAP Note 705569 for further details and explanations.
SAP AG
SM100
11-98
$SSHQGL[
8VH WKH 0RQLWRULQJ
SAP AG 2006
SAP AG
SM100
11-99
2EVHUYH $OHUWV 5HODWLYH WR WKH %XVLQHVV 3URFHVV

7KH DOHUWV IRU WKH EXVLQHVV SURFHVV FDQ EH DFFHVVHG LQ WKH 2SHUDWLRQV DUHD RI WKH 6$3 6ROXWLRQ 0DQDJHU
gqgg q%ggg g n k p g g o m k gyl#$g h i j g i qUa Q g a1hfd g e
SAP AG 2006
SAP AG
z 1qg $# i i #hW$g m 1 i tW5 g i h z e k p
g z t$1 i Wq1g i W e k p v k k x g i W9$qUa 3 9 yWr z x k
z k x w i k h{9Ey Wtt Q u s m v q i atg ft hr g i ttt Q EW#qg g ah j k ~ } g g 1hg fs g u g a Iqgqtr g i ttt Q | d k s m tfaEx t hr
<RX FDQ DFFHVV WKH DOHUWV YLD WKH PRQLWRULQJ JUDSKLF LQ DUHD ZKHQ \RX FOLFN RQ WKH %XVLQHVV 3URFHVV 1DPH 6XPPDUL]DWLRQ DOHUW IRU WKLV VSHFLILF EXVLQHVV SURFHVV
To access the monitoring graphic choose Solution Monitoring -> Business Process Monitoring in the Operations area. You can see the aggregated alert for the business process in the monitoring graphic. If you click on the name of the business process you' be brought to a more detailed graphic of the business process with ll the separate steps listed and the alerts aggregated for these steps. The graphical display screen has the advantage of also providing aggregated alerts for the hardware and the systems if system monitoring has been set up in the SAP Solution Manager.
SM100
11-100
2EVHUYH $OHUWV 5HODWLYH WR %XVLQHVV 3URFHVV 6WHSV
6XPPDUL]DWLRQ DOHUWV IRU DOO VRIWZDUH FRPSRQHQWV KDUGZDUH FRPSRQHQWV DQG EXVLQHVV SURFHVVHV $JJUHJDWHG 6\VWHP 0RQLWRULQJ DOHUW IRU VDWHOOLWH V\VWHP $JJUHJDWHG DOHUW IRU EXVLQHVV SURFHVV VWHS
SAP AG 2006
If you click on the alert symbol for an specific step, you will navigate to a more detailed graphic containing all the alerts corresponding to that business process step.
SAP AG
SM100
11-101
g z t$1 i Wq1g i W e k p v k k x g i W9$qUa 3 9 yWr z x k g g 1hg fs g u g a Iqgqtr z 1qg $# i i #hW$g m 1 i tW5 g i h z e k p g i ttt Q EW#qg g ah j k ~ } g i ttt Q | d k s m tfaEx t hr z k x w i k h{9Ey Wtt Q u s m v q i atg ft hr gqgg q%ggg g n k p g g o m k gyl#$g h i j g i qUa Q g a1hfd g e
SAP AG
SAP AG 2006
By clicking on an specific alert, you navigate to the Business Process Monitoring session, where you can see detailed historical information about this specific alert.
&KHFN 'HWDLOHG $OHUW ,QIRUPDWLRQ
7KH GHWDLOHG DOHUW LQIRUPDWLRQ IRU D EXVLQHVV SURFHVV VWHS LV DFFHVVLEOH YLD OHIW PRXVH FOLFN RQ WKH DJJUHJDWHG DOHUW IRU WKLV VWHS
SM100
'HWDLOHG $OHUWV IRU D VLQJOH EXVLQHVV SURFHVV VWHS
11-102
SAP AG
SAP AG 2006
&KHFN IRU 2SHQ $OHUWV
,Q WKH GHWDLOHG DOHUW YLHZ \RX FDQ FKHFN YLD RSHQ DOHUWV IRU SUREOHP VLWXDWLRQV WKDW KDYH QRW \HW EHHQ VROYHG
SM100
&KRRVH 2SHQ $OHUWV WR YLHZ \HW XQVROYHG DOHUW VLWXDWLRQV
11-103
'LVSOD\LQJ 2SHQ $OHUWV SHU %XVLQHVV 3URFHVV 6WHS
&KRRVH 2SHQ $OHUWV &KRRVH 2SHQ $OHUWV
2SHQ DOHUWV UHSUHVHQW SUREOHPV LQ WKH SDVW WKDW KDYH QRW \HW EHHQ VROYHG 7KH\ DUH RQO\ DFFHVVLEOH DW EXVLQHVV SURFHVV VWHS OHYHO
SAP AG 2006
The current status of an alert represents the alert status determined during the last run of the RZ20 data collector. If transaction VA01 has a green alert in the current status view the last collector run for this transaction has resulted in a green alert. This green alert, however, does not mean that the performance of this transaction has always been good in the past. The open alert view shows that there was a red alert for this transaction some time ago and that the performance of VA01 has since improved. The concept of current status / open alerts is part of RZ20. You can confirm open alerts to signify that the problem situation has been solved. This way you can ensure that the Open Alerts View always indicates whether or not there are alerts that require action.
SAP AG
SM100
11-104
SAP AG
SAP AG 2006
5HYLHZ +LVWRULF $OHUWV
7KH GHWDLOHG LQIRUPDWLRQ IRU WKH KLVWRULF DOHUWV LV DYDLODEOH LQ WKH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ
SM100
11-105
$FFHVVLQJ +LVWRULFDO $OHUW ,QIRUPDWLRQ

*UDSKLFDO 'LVSOD\ &OLFNLQJ RQ DQ DOHUW LFRQ EULQJV \RX WR D GHWDLOHG RYHUYLHZ RI WKH DOHUWV IRU WKH UHVSHFWLYH EXVLQHVV SURFHVV VWHS
b xy
&KRRVLQJ DQ DOHUW EULQJV \RX WR WKLV DOHUW LQ WKH %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ
SAP AG 2006
SAP AG
SM100
b VE
600
3 60W
11-106

'HWDLOHG ,QIRUPDWLRQ DERXW WKH DOHUW DQG WKH DOHUW KLVWRU\ LV GLVSOD\HG LQ WKH %XVLQHVV 3URFHVV 0RQLWRULQJ 6HVVLRQ )RU HDFK GHILQHG DOHUW DUH OLVWHG DOO DOHUWV WKDW RFFXUUHG ZKHQ GLG WKH DOHUWV RFFXU ZKDW WULJJHUHG WKH DOHUW )RU HYHU\ PRQLWRULQJ W\SH WKH VSHFLILHG PRQLWRULQJ WUDQVDFWLRQV DUH GLVSOD\HG DV GLUHFW OLQNV WR WKH UHVSHFWLYH VDWHOOLWH V\VWHP
SAP AG 2006
In general, you get entries into the alert table for every open alert. For each alert you get detailed information about when the alert occurred and what exact event triggered the alert, for instance, if a job starts later than defined in the start delay alert you will not only get the information that the job had failed to start at a certain time but also at what time the job did eventually start.
SAP AG
SM100
11-107
$OHUW ,QIRUPDWLRQ
7DEOH 2SHQ DQG &RQILUPHG $OHUWV
7DEOH
$OHUW &RQILJXUDWLRQ
2QO\ IRU %DFNJURXQG -RE 0RQLWRULQJ 7DEOH %J -RE 'HWDLOV
SAP AG 2006
Table Open and Confirmed Alerts Contains the list of alerts that have occurred in the past for this monitoring object Provides details about when the alerts have occurred and how much the thresholds have been exceeded. Shows which of those alerts have been confirmed and which alerts are still open The rating of the respective node in the session tree is determined by the highest open alert available for this monitoring object. This means that the rating for the node can be different from the current rating for this alert in the monitoring graphic.
Table Alert Configuration Shows the currently active customizing for this alert. This customizing can differ from the customizing visible in the Setup Business Process Monitoring session.
For background jobs only: Table Bg. Job Details Lists the setting for the background job that is monitored. These settings can differ from the settings visible in the Setup Business Process Monitoring session.
SAP AG
SM100
11-108
$FFHVV (UURU +DQGOLQJ 3URFHGXUHV DQG (VFDODWLRQ 3DWKV

(UURU +DQGOLQJ 3URFHGXUHV DQG (VFDODWLRQ 3DWKV DUH DYDLODEOH LQ QRGH PRQLWRULQJ W\SH!
SAP AG 2006
SAP AG
SM100
11-109
SAP AG
SAP AG 2006
Use the error handling procedures available in the SAP Solution Manager.
$QDO\]H 3UREOHP LQ WKH 6DWHOOLWH 6\VWHP
SM100
/LQN WR PRQLWRULQJ WUDQVDFWLRQV LQ WKH VDWHOOLWH V\VWHPV
11-110
$QDO\]H 3UREOHP LQ WKH 6DWHOOLWH 6\VWHP
$FFRUGLQJ WR WKH HUURU KDQGOLQJ SURFHGXUHV GHWHUPLQH WKH FDXVH DQG HIIHFW RI WKH SUREOHP DQG GHFLGH RQ KRZ WR VROYH WKH SUREOHP
SAP AG 2006
Use the error handling procedures available in the SAP Solution Manager.
SAP AG
SM100
11-111
$FFHVV )XUWKHU ,QIRUPDWLRQ
/LQN WR 85/
:LWK WKH 85/ \RX FDQ SURYLGH PRUH GHWDLOHG HUURU KDQGOLQJ SURFHGXUHV
SAP AG 2006
SAP AG
SM100
11-112
SAP AG
SAP AG 2006
&UHDWH 6HUYLFH 'HVN 0HVVDJH

0DUN DOHUWV UHOHYDQW IRU WKH 6HUYLFH 'HVN PHVVDJH
SM100

&KRRVH WR FUHDWH 6HUYLFH 'HVN PHVVDJH
11-113
6HUYLFH 'HVN 0HVVDJH

7KH QXPEHU RI WKH 6HUYLFH 'HVN PHVVDJH DV ZHOO DV LWV VWDWXV DUH GLVSOD\HG LQ WKH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ %\ GRXEOH FOLFNLQJ RQ WKH PHVVDJH QXPEHU \RX JHW GLUHFWO\ WR WKLV PHVVDJH LQ WKH 6HUYLFH 'HVN RI 6$3 6ROXWLRQ 0DQDJHU
'RXEOH FOLFN
SAP AG 2006
SAP AG
SM100
11-114
$1 i Wq1g i W g z e k p v k k x g i W9$qUa 3 9 yWr z x k g g 1hg fs g u g a Iqgqtr z 1qg $# i i #hW$g m 1 i tW5 g i h z e k p g i ttt Q EW#qg g ah j k ~ } g i ttt Q | d k s m tfaEx t hr z k x w i k h{9Ey Wtt Q u s m v q i atg ft hr gqgg q%ggg g n k p g g o m k gyl#$g h i j g i qUa Q g a1hfd g e
SAP AG
SAP AG 2006
You can confirm alerts individually by marking the alerts and choosing Confirm selected . It is also possible to mass confirm alerts (all yellow or all red) for a particular monitoring object.
&RQILUP $OHUWV IRU 6ROYHG 3UREOHPV
SM100
&KRRVH WR FRQILUP WKH DOHUWV
11-115
8VHU 6WDPS DQG &RPPHQWV IRU &RQILUPHG $OHUWV
%\ FRQILUPLQJ DOO UHG DOHUWV WKH VWDWXV RI WKH QRGH KDV FKDQJHG WR \HOORZ
<RX FDQ SURYLGH FRPPHQWV IRU WKH FRQILUPHG DOHUWV
7KH LQIRUPDWLRQ ZKLFK XVHU KDV FRQILUPHG WKH DOHUWV ZKHQ LV GLVSOD\HG
SAP AG 2006
The column Comment can also be used when no alerts have been confirmed. Here, you can for instance specify hints like waiting for feedback from development to tell other persons who also use the monitoring that the problem is already being taken care of.
SAP AG
SM100
11-116
&RQILUPLQJ $OHUWV LQ WKH 'HWDLOHG $OHUW 9LHZ
0DUN DOHUWV WKDW VKRXOG EH FRQILUPHG DQG FKRRVH &RQILUP
,Q DGGLWLRQ WR WKH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ DOHUWV FDQ EH FRQILUPHG LQ WKH 'HWDLOHG $OHUW 9LHZ RI WKH 0RQLWRULQJ *UDSKLF 7KH LQIRUPDWLRQ DERXW WKH FRQILUPHG DOHUWV LV UHSOLFDWHG LQWR WKH %XVLQHVV 3URFHVV 0RQLWRULQJ VHVVLRQ
SAP AG 2006
Due to technical restrictions in RZ20 the replication of the confirmed alerts only works if the actual alerts have been confirmed, not if just the parent MTE for the alerts has been confirmed. In the example of the above screenshot this means that if only the upper line VA01 (tt5tdc00_TT5_50)\DBRequestTime (1) [More] is confirmed in the graphic, no data will be replicated into the Business Process Monitoring session. To replicate, the line 1.538 msec > 1.200 msec Transact-spec. dialog resp. time exceeds threshold... to be confirmed as well.
SAP AG
SM100
11-117
SAP AG
SM100
11-118

SAP Solution Manager Operations PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Solution Manager Operations PDF

Uploaded by

Copyright:

Available Formats

60 6$3 6ROXWLRQ 0DQDJHU 2SHUDWLRQV

Software components used in the course 2006/Q62 Material number 50082608

' &         (%$#""! 

&RS\ULJKW  6$3 $* $OO ULJKWV UHVHUYHG

6$37(& $'0 6$3

7HFKQLFDO &RQVXOWDQWV 'XUDWLRQ  GD\V

7KLV FRXUVH LV LQWHQGHG IRU WKH IROORZLQJ DXGLHQFHV

$IWHU FRPSOHWLQJ WKLV FRXUVH \RX ZLOO EH DEOH WR

Conduct: ausfhren, durchfhren

   1 8  U 5 8 C C )  d 1 # "  & &!C rVDPF1 `fIeV! D

8 5 1  1 ) (   $ # "  76!4 320'&%! 

8QLW  &RXUVH &RQWHQW

   0 7  T 4 7 B B (  c 0 "  % % B qUCIE0 YeHdU!  C

7  0  0 ( '   # " !  654 3 21)&%$  

2EMHFWLYHV 6ROXWLRQ 0DQDJHU 2YHUYLHZ

*HW DQ JHQHUDO RYHUYLHZ RI WKH 6$3 6ROXWLRQ 0DQDJHU IXQFWLRQDOLWLHV

'HVFULEH WKH DQGDYDQWDJH RI WKH 6$3 6ROXWLRQ 0DQDJHU

$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR

6$3 6ROXWLRQ 0DQDJHU   2YHUYLHZ

&RQVLGHU &XVWRPHUV 6LWXDWLRQ RI 7RGD\

&RQVLGHU &XVWRPHUV 6LWXDWLRQ RI 7RGD\

'LIIHUHQW DSSOLFDWLRQV WHFKQRORJLHV DQG YHQGRUV

your solution is based upon

oo e `` 66ee ee q qr `~`~6z6zyy yy e{e{~u ~u 6~6~ rrrll tr tr ` r

oo oo rr XX l o~o~5`zy5XzXz{y e{ { oo&rr y q m& m

Definition of Service Level Reporting requirements

&RQVLGHU &XVWRPHUV 6LWXDWLRQ RI 7RGD\

Do you know the responsible persons in case of problems?

Do you know which business process step runs on which system?

,QWHJUDWHG %XVLQHVV 3URFHVVHV

Increase Return on Investments

Reduce Total Cost of Ownership

6XSSRUW IRU ,7,/ 3URFHVVHV

6XSSRUW IRU ,7,/ 3URFHVVHV $YDLODEOH )XQFWLRQDOLWLHV 5HOHDVH 6WUDWHJ\

&RPPRQ GH IDFWR 6WDQGDUGV IRU ,7 0DQDJHPHQW

www.itsmf.com (for Germany www.itsmf.de)

02) 0LFURVRIW 2SHUDWLRQV )UDPHZRUN

35,1&( 35RMHFWV ,1 &RQWUROHG (QYLURQPHQWV

Best practices in IT Service Management based on Microsoft technology.

&RPELQLQJ :KDW DQG +RZ

Developed with help of IT service specialists

What to consider in establishing and operating IT service management?

Based on more than 30 years experience in managing business applications

How to execute the processes by using tools in SAP Solution Manager?

,7,/ DQG 6$3 7RROV

 ' 7BB ( HG D 7B@ I2%FA9

(SAP Alert Monitoring RZ20)

7 4 0  0 ( 4 7 B B (  c 0 C6Y23 2IR E20 YeH2R"

7 4 0 D  c 0 " B f e&CRP e0YeHdUCb"

  S4 " u % rR2"

Solution Management Assessment Solution Management Optimization EarlyWatch Alert / GoingLive

6HUYLFH 'HOLYHU\ ZLWK 6$3 6ROXWLRQ 0DQDJHU

EarlyWatch Alert, Quick Sizer

Service Desk Accounting

 '7BB CC' #  BS & eecB ecq

SL and Solution Reporting

`}f &e 1 e%q} efI`

Performance and availability

 '7BB EC( #BB  F9  '7BB CPCCI( c B  CB `

6HUYLFH 6XSSRUW ZLWK 6$3 6ROXWLRQ 0DQDJHU

Requests for change

Note Assistant, Change Request Management

Central system data and Customizing

60 6$3 6ROXWLRQ 0DQDJHU 2SHUDWLRQV

' & (%$#""!

&RS\ULJKW 6$3 $* $OO ULJKWV UHVHUYHG

6$37(& $'0 6$3

7HFKQLFDO &RQVXOWDQWV 'XUDWLRQ GD\V

7KLV FRXUVH LV LQWHQGHG IRU WKH IROORZLQJ DXGLHQFHV

$IWHU FRPSOHWLQJ WKLV FRXUVH \RX ZLOO EH DEOH WR

1 8 U 5 8 C C ) d 1 # " & &!C rVDPF1 `fIeV! D

8 5 1 1 ) ( $ # " 76!4 320'&%!

8QLW &RXUVH &RQWHQW

0 7 T 4 7 B B ( c 0 " % % B qUCIE0 YeHdU! C

7 0 0 ( ' # " ! 654 3 21)&%$

*HW DQ JHQHUDO RYHUYLHZ RI WKH 6$3 6ROXWLRQ 0DQDJHU IXQFWLRQDOLWLHV

$IWHU FRPSOHWLQJ WKLV XQLW \RX ZLOO EH DEOH WR

6$3 6ROXWLRQ 0DQDJHU 2YHUYLHZ

'LIIHUHQW DSSOLFDWLRQV WHFKQRORJLHV DQG YHQGRUV

oo oo rr XX l o~o~5`zy5XzXz{y e{ { oo&rr y q m& m

,QWHJUDWHG %XVLQHVV 3URFHVVHV

35,1&( 35RMHFWV ,1 &RQWUROHG (QYLURQPHQWV

' 7BB ( HG D 7B@ I2%FA9

7 4 0 0 ( 4 7 B B ( c 0 C6Y23 2IR E20 YeH2R"

7 4 0 D c 0 " B f e&CRP e0YeHdUCb"

S4 " u % rR2"

'7BB CC' # BS & eecB ecq

`}f &e 1 e%q} efI`

'7BB EC( #BB F9 '7BB CPCCI( c B CB `

23R " C%E $ # ! %Ff 3 }}}}6

}6%t} % `` 9C7 8 %Ff 3 }}}}6 5 & $%43 63

,VVXH 7UDFNLQJ 0RQLWRULQJ 5HSRUWLQJ 5RDGPDSV

Ce!r%$(h % " 5 Cqd

((% & d $" B E cCe! ' "

$% R a &R %T " r(Y!Rd

3%s%C&s E %r "

CPC $% 3%`5 # TC&dd

} tU( y % 3 CtU( y b`

& tU y b &o % 3}}

} & U e% &2hU

6$3 6ROXWLRQ 0DQDJHU /LFHQVLQJ

22 n 29 nQQ9 2g nnQ s n9 22Q n2Qn n 29 nQ9

nu r )j # r )j r )j

222 n v n2!9 s2 nnQ s k 2$2Q

ggT n s 29 2 gk nQ2n n v 2

ggT n n s Q9 g Q sQ22 n v

}}o U6h`&} %R o %Roh`& F

Qq j T )&x

6$3 6ROXWLRQ 0DQDJHU .H\ %HQHILWV

6ROXWLRQ 0DQDJHU 2YHUYLHZ 8QLW 6XPPDU\

*HW DQ JHQHUDO RYHUYLHZ RI WKH 6$3 6ROXWLRQ 0DQDJHU IXQFWLRQDOLWLHV

<RX VKRXOG QRZ EH DEOH WR

8QLW &RXUVH &RQWHQW

0 7 T 4 7 B B ( c 0 " % % B qUCIE0 YeHdU! C

7 0 0 ( ' # " ! 654 3 21)&%$

,W SURYLGHV LQIRUPDWLRQ WKDW LV UHTXLUHG IRU D YDULHW\ RI DSSOLFDWLRQV DQG SURFHVVHV