how to create conf guide

How to Create aConfiguration Guide UsingSAP Solution Manager

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare 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 aretrademarks 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 containedin this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth inthe express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” 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 not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hotlinks 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.

SAP Solution Manager “How-to” Guides are intended to

simplify the product implementation. While specific

product features and procedures typically are explained ina practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP Solution Manager.

Should you wish to receive additional information,clarification or support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally orgrossly negligent.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictableand severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

SAP AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

http://www.sap.com/

How to Create a Configuration Guide Using SAP Solution Manager

January, 2008 3

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear onthe screen. These include field

names, screen titles, pushbuttons aswell as menu names, paths and

options.Cross-references to other

documentation

Example text Emphasized words or phrases inbody text, titles of graphics and

tables

EXAMPLE TEXT Names of elements in the system.These include report names,

program names, transaction codes,table names, and individual key

words of a programming language,when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file anddirectory names and their paths,

messages, names of variables andparameters, source code as well asnames of installation, upgrade and

database tools.

Example text Exact user entry. These are words orcharacters that you enter in the

system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that you replacethese words and characters with

appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example,function keys (such as F2) or the

ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4 January, 2008

ContentsHow to Create a Configuration Guide Using SAP Solution Manager...................................................................... 5

1. Introduction........................................................................................................................................................... 5

3. Storyline................................................................................................................................................................. 5

4. Prerequisites .......................................................................................................................................................... 7

5. Procedure .............................................................................................................................................................. 85.1 Create Implementation Project ........................................................................................................................... 85.2 Select the Scenarios which to Configure............................................................................................................105.3 Select the Configuration Structures ...................................................................................................................115.4 Create the Configuration Guide.........................................................................................................................13


January, 2008 5

How to Create a Configuration Guide Using SAP SolutionManager

1. IntroductionThis how-to guides you through the main steps and activities to create a Configuration Guide using SAPSolution Manager.For more information about generating a Configuration Guide, see SAP Note 777089.

System Landscape this process is built in

SAP Solution Manager 7.0

3. Storyline

Highlighted sections are covered in this demo script.

The company "Books & Journals" intends to improve their customer interaction processes byintroducing mySAP CRM 5.0. Having evaluated various possibilities, the company decides to usestandardized SAP business software for inbound telesales: this will meet the majority of their requirements.

To initiate the implementation process, the project manager creates an implementation project called“CRM Implementation” in the SAP Solution Manager system. Here, they define the general projectframework data. In the blueprint phase, the implementation team defines and documents the plannedprocesses and possible functional enhancements. As a starting point, they choose the "Inbound Telesaleswith ERP Sales Order" process from the pool of SAP reference elements, the Business Process Repository,and adapt it to their company-specific needs.

The scenario of the new process is as follows: customers or prospects (consumers or enterprises)contact the Interaction Center and ask for information about products or services, before they place an order,or they inquire about the status of existing orders. When a sales order in the Interaction Center is saved, thesystem replicates it directly to SAP ECC (ERP Central Component). The process uses an Internet Pricingand Configurator system (IPC) for pricing, and an SCM (Supply Chain Management) installation for theavailability check. For reporting purposes, a BW installation is available. When introducing the new process,in order to minimize costs and ensure its smooth operation, “Books & Journals” decides to use SAP SolutionManager as their new application management platform.

Because the company also wants the enhanced modeling capabilities and graphical models (componentviews) SAP provides, they decide to use ARIS for SAP NetWeaver, to download existing SAP SolutionManager process models and model their EPCs (event-driven process chains).

After the Business Blueprint is completed and documented, the implementation team configures thesolution scope in the configuration phase, using IMG (Implementation Guide) links. They document theircustomizing and create related learning materials, to ensure proper training and use of the systems by theend user. The project progress is constantly measured using SAP Solution Manager reporting capabilities. Ateam of testers uses predefined test cases for manual and automatic testing (eCATTs and CATTs), toensure a smooth go live of the new process. You can define new tests in the extended solution for SAPQuality Center by HP. Questions and errors are handled by the integrated service desk. Reportingcapabilities for the test status and results allow the project manager to check on the test progress.

Before going live, SAP delivers an SAP GoingLive Check, to make sure that all business and technicalissues have been identified and solved. The results of this service are stored in the SAP Solution Manager.The new SAP Support Collaboration functions allow “Books & Journals” to address, maintain and exchangeopen issues (issue tracking) and tasks, and to get Expertise on Demand from SAP Support.


6 January, 2008

The handover to the regular operations phase is easy, because all information on processes,documentation and connected systems is already available, and is now transferred to the company’sproduction environment, the Solution Directory.

The IT department now monitors technical KPIs (key performance indicators) such as systemconfiguration, system performance and hardware capacity, with the EarlyWatch Alert service. To ensure thatall service level agreements, such as system availability, are fulfilled, the IT department delivers service levelreports to the application management and responsible administrators regularly. The daily administration ofthe new process is supported by the central system administration tool. It offers predefined tasks, such aschecking background jobs in SM37, with links to the satellite systems. The tool keeps a log of when the tasksare completed.

To have the system immediately inform them if a severe error occurs, the IT team sets up systemmonitoring. When an alert occurs, the system informs the administrator responsible by sending a message toa mobile telephone, or if the alert is of minor severity, the system generates a service desk ticket.Applications based on SAP Web AS Java components, such as the J2EE engine, are supported by using thediagnostics in SAP Solution Manager. SAP Support uses the diagnostics in SAP Solution Manager toperform root cause analysis for instance threads and workload. The company’s support department can alsouse this tool.

The support department also uses the service desk to track all incidents occurring in their SAPapplications.

The success of the project, and the efficient use of these basic SAP Solution Manager functions,convinced top management to also test other features, such as change request management and businessprocess monitoring. To reduce further TCO (total cost of ownership), management decides to use the SAPSolution Manager, with its underlying SAP NetWeaver, as a central monitoring and operations hub.

Having implemented and successfully piloted inbound telesales for half a year, top management at"Books & Journals" is convinced of this process' business value. They release the budget to roll out thisprocess to decentralized interaction centers throughout Europe, the Americas and Asia-Pacific. To reducework, the template team copies the existing implementation project into a reference template project. Theteam then enhances the project by adding additional processes to launch campaign management activities.They store the processes in templates, which serve as shipping units. The decentralized rollout projects arebased on these templates, facilitating and reducing implementation effort and time. Due to the dynamicnature of business, the template team needs to change the process model over time. When rolling out thechanges to the different locations, SAP Solution Manager provides assistance in detecting and transferringthe process deltas.


January, 2008 7

4. PrerequisitesBasic knowledge of SAP Solution Manager. This can be obtained via the RKT Learning Maps(www.service.sap.com/rkt-solman >> SAP Solution Manager 7.0 - Enhancement Package 1 (EHP1)).

http://www.service.sap.com/rkt-solman


8 January, 2008

5. ProcedureThe main steps are:1. Create an implementation project (transaction SOLAR_PROJECT_ADMIN).2. Select the scenarios which to configure (transaction SOLAR01).3. Select the configuration structures (transaction SOLAR02).4. Create your configuration guide.

5.1 Create Implementation Project1. Log on to the SAP Solution Manager system with your user and password.

transaction code SOLAR_PROJECT_ADMIN

2. Create your project by choosing Create.

3. In the dialogbox, enter project name, e.g. MyProject.4. Choose the type Implementation Project.

5. Continue by choosing .


January, 2008 9

6. Enter a Title, e.g. My Demo Project, and choose the project language English.

7. Save your settings.

8. Confirm the dialog box for the KW context (for documents) .


You have now created a new implementation project.


10 January, 2008

5.2 Select the Scenarios which to Configure1. Go to transaction SOLAR01.

transaction code SOLAR01

2. Make sure your project is selected.3. Go to the Structure tab.4. Make sure your source is Business Process Repository.5. In the Business Blueprint Structure mark Business Scenarios.6. On the Structure tab, choose Value Help, to go to the overview of all Business Scenarios.

7. Choose the scenario to configure, in this case PI (Process Integration).

8. Confirm .


January, 2008 11


You have now selected the scenarios to configure.

5.3 Select the Configuration Structures10. Go to transaction SOLAR02.


11. Make sure your project is selected.12. In your Configuration Structure, choose folder Configuration.13. Go to Structure tab.14. Choose button Change Configuration Structure.


12 January, 2008

15. On the Structure tab, choose Value Help, to go to the overview of all Configuration Elements.

16. Select the component, in this case, for Basic Configuration, SAP NetWeaver 7.01 PI.

17. Confirm .


January, 2008 13

18. Save .19. Deselect all Usage Types you do not need, in this case an additional Stand-Alone Engine, Usage Type

BI and Usage Type Mobile.

20. Save .

You have created your Configuration Structure.

5.4 Create the Configuration Guide21. Go to transaction SOLAR02.


22. Make sure your project is selected.23. In the menu, choose Generate Configuration Guide.


14 January, 2008

24. A dialog box appears.25. Select where to save the document (on the General tab) and display IMG documentation (on Display

Options tab).

26. Execute


January, 2008 15

27. The system tells you where on your PC it will store the Configuration Guide.

28. Continue .

29. The system tells you where it has stored the file and what you have to do next.

30. Continue .


16 January, 2008

31. Microsoft Office Word is opened. Choose the button Enable Macros.

32. In the menu, choose: Tools -> Macro -> Macros.

33. Run the Macro SAP_CONFIGURATION_GUIDE by choosing the button Run.


January, 2008 17

34. Your Configuration Guide is now generated. You can save it.

how to create conf guide

Documents