How-to Document
How to Create a Configuration Guide Using SAP Solution Manager
Target Audience
àônDÞÑ Technical consultants
àônDÞÑ Application consultants
CUSTOMER
àôn€û˚˚>{ûê‡7DÖ³Ý‘Q9»ö×dŒõYNÕ˚!!i·í&~Í˚íé›−bñoÅÓž~}eya…/�†»Uï“�/BF
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: http://service.sap.com/
solutionmanager Overview Media Library
How-to Documents .
The following table provides an overview of the most important document changes.
Version
Date
Description
1.00
1.05
2012-01-18
2013-05-13
Initial version
New sentence in section Create the Configuration Guide [page 19], step 4: Select a local
directory and ensure that the complete path name is not longer than 132 characters.
2/34
CUSTOMER
2013-05-13
Table of Contents
Chapter 1
How to Create a Configuration Guide Using SAP Solution
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2
Storyline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 4
4.1
4.2
4.3
4.4
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Implementation Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select the Scenarios to Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select the Configuration Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create the Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5
Adjustments to the Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter A
A.1
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2013-05-13
CUSTOMER
13
13
15
17
19
3/34
This page is left blank for documents
that are printed on both sides.
1
How to Create a Configuration Guide Using SAP Solution Manager
1 How to Create a Configuration Guide
Using SAP Solution Manager
This guide tells you how to create a Configuration Guide using SAP Solution Manager.
For background information about generating and adjusting a Configuration Guide, see the Adjustments
to the Configuration Guide section.
2013-05-13
CUSTOMER
5/34
This page is left blank for documents
that are printed on both sides.
2
Storyline
2 Storyline
NOTE
Highlighted sections are covered in this document.
The company Books & Journals intends to improve their customer interaction processes by introducing
SAP CRM 5.0. After evaluating various possible strategies, the company decides to use standardized SAP
business software for inbound telesales: this will meet most of their requirements.
To initiate the implementation process, the project manager creates an implementation project, CRM
Implementation, in the SAP Solution Manager system, in which he specifies the general project framework
data. In the blueprint phase, the implementation team defines and documents the planned processes
and functional enhancements. Starting from the Inbound Telesales with ERP Sales Order process from the
pool of SAP reference elements, the Business Process Repository, and adapting it to their companyspecific 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 is saved in the Interaction Center,
the system replicates it directly to SAP ECC (ERP Central Component). The process uses an Internet
Pricing and Configurator system (IPC) for pricing, and an SCM (Supply Chain Management)
installation to check availability. A BW installation is available for reporting. When introducing the
new process, Books & Journals decides to adopt SAP Solution Manager as their application management
platform, to minimize costs an ensure smooth operation.
Because the company also wants the enhanced modeling capabilities and graphical models (component
views) SAP provides, they decide to use ARIS for SAP NetWeaver, to download existing SAP Solution
Manager process models, and model their EPCs (event-driven process chains).
After the Business Blueprint is completed and documented, the implementation team
configures the solution scope in the configuration phase, using the IMG (Implementation
Guide). They document their customizing and create learning materials, to train the end users of the
systems. The project progress is continuously measured using SAP Solution Manager reporting
capabilities. A team of testers uses predefined test cases for manual and automatic testing (eCATTs and
CATTs), to ensure a smooth go live of the new process. You can define new tests in the extended SAP
Quality Center by HP. Questions and errors are handled inthe integrated service desk. Reporting
capabilities for the test status and results allow the project manager to monitor the test progress.
Before going live, SAP delivers an SAP GoingLive Check, to make sure that all business and technical
issues have been identified and solved. The results of this service are stored in the SAP Solution Manager.
2013-05-13
CUSTOMER
7/34
2
Storyline
The new SAP Support Collaboration functions allow Books & Journals to address, maintain and exchange
open issues (issue tracking) and tasks, and to get Expertise on Demand from SAP Support.
The handover to the operations phase is easy, because all information on processes, documentation
and connected systems is already available, and is transferred to the company’s production
environment, the Solution Directory.
The IT department monitors technical KPIs (key performance indicators) such as system configuration,
system performance and hardware capacity, with the EarlyWatch Alert service. The IT department
delivers service level reports to the application management and responsible administrators, regularly,
to ensure that all service level agreements, such as system availability, are fulfilled. The daily
administration of the new process is supported by the central system administration tool. It offers
predefined tasks, such as checking background jobs in SM37, with links to the satellite systems. The
tool logs when the tasks are completed.
The IT team sets up system monitoring to have the system inform them if a severe error occurs. When
an alert occurs, the system informs the administrator responsible by sending a message to a 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 the diagnostics in
SAP Solution Manager. SAP Support uses the diagnostics in SAP Solution Manager to perform root
cause analysis for instance threads and workload. The company’s support department can also use this
tool.
The support department also uses the service desk to track all incidents occurring in their SAP
applications.
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
business process monitoring. To reduce further TCO (total cost of ownership), management decides
to use the SAP Solution Manager, with its underlying SAP NetWeaver, as the central monitoring and
operations hub. Having implemented and successfully piloted inbound telesales for six months, top
management at Books & Journals is convinced of this process' business value. They release the budget to
roll out this process to decentralized interaction centers throughout Europe, the Americas and AsiaPacific. The template team copies the existing implementation project into a reference template project,
to reduce work. The team enhances the project by adding additional processes to manage campaigns.
They store the processes in templates, which serve as shipping units. The decentralized rollout projects
are based on these templates, facilitating implementation and reducing the effort and time it takes.
Due to the dynamic nature of business, the template team needs to change the process model over
time. When rolling out the changes to the different locations, SAP Solution Manager helps detect and
transfer the process deltas.
8/34
CUSTOMER
2013-05-13
2
Storyline
=Ú(Ü](ÐwÐPí‰ƒ«J&ê−òÎ„Business Blueprint Change
2013-05-13
CUSTOMER
9/34
This page is left blank for documents
that are printed on both sides.
3
Prerequisites
3 Prerequisites
You need basic knowledge of SAP Solution Manager. This can be obtained via:
‰±k½}˚ RKT Learning Maps
See http://service.sap.com/rkt-solman; for example with SAP Online Knowledge Product for
SAP Solution Manager 7.1: http://service.sap.com/~form/sapnet?_SHORTKEY=
01100035870000736990&.
‰±k½}˚ SAP Help Portal
See http://help.sap.com Application Lifecycle Management SAP Solution Manager , for example
SAP Solution Manager 7.1: http://help.sap.com/solutionmanager71.
‰±k½}˚ Master Guide
See http://service.sap.com/solutionmanager Planning, Installation, and Upgrade Guides ; for
example SAP Solution Manager 7.1: SAP Solution Manager 7.1 1 Planning Master Guide SAP Solution
Manager 7.1 .
2013-05-13
CUSTOMER
11/34
This page is left blank for documents
that are printed on both sides.
4
Procedure
4.1
Create Implementation Project
4 Procedure
The main steps are:
1. Create an implementation project (transaction code SOLAR_PROJECT_ADMIN).
2. Select the scenarios to configure (transaction code SOLAR01).
3. Select the configuration structures (transaction code SOLAR02).
4. Create your configuration guide.
4.1 Create Implementation Project
Procedure
1.
2.
3.
Log on to the SAP Solution Manager system with your user and password.
Choose transaction code SOLAR_PROJECT_ADMIN.
Create your project by choosing Create.
µ«‹ˆŁp‚ÌÔeGVıJ©P´¹ïéChoose Create
4.
5.
6.
In the dialog box, enter project name, e.g. MyProject.
Choose the type Implementation Project.
Continue by choosing Continue.
2013-05-13
CUSTOMER
13/34
4
Procedure
4.1
Create Implementation Project
›*ƒ“nÚÀ'ðåØ[ﬁD~È™LŁÚCreate Project
7.
8.
Enter a Title, e.g. My Demo Project, and choose the project language English.
Save your settings.
›*ƒ“nÚÀ'ðåØ[ﬁD~Ï™LŁÚSave Settings
9.
Confirm the dialog box for the KW context (for documents) by choosing Continue.
14/34
CUSTOMER
2013-05-13
4
Procedure
4.2
Select the Scenarios to Configure
!Óó⁄Gàq}}�yáƒ]xöqq8ûConfirm KW Context
10. Save your settings.
Result
You have now created a new implementation project.
4.2 Select the Scenarios to Configure
Procedure
1.
2.
3.
4.
5.
6.
Choose transaction SOLAR01.
Select your project.
Go to the Structure tab.
Select the source Business Process Repository.
In the Business Blueprint structure, mark Business Scenarios.
On the Structure tab, choose Value Help, to go to the business scenarios overview.
2013-05-13
CUSTOMER
15/34
4
Procedure
4.2
Select the Scenarios to Configure
“S°K³˛ołPl‘Þ•†J¥%h˘ﬁ˝ƒChoose Business Scenario
7.
Choose the scenario to configure, in this case PI (Process Integration).
“S°K³˛ołPl‘Þ•†J¥%i˘ﬁ˝ƒChoose Process Integration
8.
9.
Confirm.
The system checks your selection.
If the system determines that no logical component of the project can be assigned to a selected
product of the Business Process Repository, it shows the dialog box Assignment of Logical Components to
Products, with proposals of further logical components to add to your project. Confirm your changes
with Continue.
Save your settings.
16/34
CUSTOMER
2013-05-13
4
Procedure
4.3
Select the Configuration Structures
pCÀ÷¿Ú?5Å
7BÚ™€Ø˘Save Settings
Result
You have now selected the scenarios to configure.
4.3 Select the Configuration Structures
Procedure
1.
2.
3.
4.
5.
Choose transaction SOLAR02.
Select your project.
In your Configuration Structure, choose folder Configuration.
Go to Structure tab.
Choose button Change Configuration Structure.
pCÀ÷¿Ú?5Å
7BÛ™€Ø˘Change Configuration Structure
6.
On the Structure tab, choose Value Help, to go to the Configuration Elements overview.
2013-05-13
CUSTOMER
17/34
4
Procedure
4.3
Select the Configuration Structures
)Lý¬{I
ÚS€W}Kp‘A•ýŒ(`8ôOverview Configuration Elements
7.
Select the component, in this case, for Basic Configuration, SAP NetWeaver 7.1 PI.
)Lý¬{I
ÚS€W}Kp‘A•ýŠ(`8ôSelect Component
8.
Confirm.
The system checks your selection.
If the system determines that no logical component of the project can be assigned to a selected
product of the Business Process Repository, it shows the dialog box Assignment of Logical Components to
Products with proposals of further logical components to add to your project. Confirm your changes
with Continue.
9. Save your settings.
10. Deselect all Usage Types you do not need, in this case an additional Stand-Alone Engine, Usage
Type BI and Usage Type Mobile.
18/34
CUSTOMER
2013-05-13
4
Procedure
4.4
Create the Configuration Guide
·hQÊsaf⁄ÌsqıÇ)¼�¹Œr‚¶÷"Select Usage Types
11. Save your settings
Result
You have created your Configuration Structure.
4.4 Create the Configuration Guide
Procedure
1.
2.
3.
Choose transaction SOLAR02.
Select your project.
In the menu, choose Configuration Generate Configuration Guide .
·hQÊsaf⁄ÌsqıÇ)¼�¹Œs‚¶÷"Generate Configuration Guide
The dialog box Configuration Guide: Selection for Project MyProject appears.
2013-05-13
CUSTOMER
19/34
4
Procedure
4.4
Create the Configuration Guide
¬BŽ±¸ÁÁ{obÑÚüáC:höH×TConfiguration Guide Selection
4.
Specify what is to be in the configuration guide.
In the General tab, you can specify whether links to other projects or solutions are to be removed,
separately by projects and solutions. If you set the flag Original in Project/Solution, the objects are copied
into the configuration guide. If you set the flag Business Function Scope, business function information
which is assigned to the project is copied. The download directory is where the configuration guide
is to be stored. Select a local directory and ensure that the complete path name is not longer than
132 characters. The system also loads all documents which are to be put in the configuration guide,
in this directory.
In the Scope tab, you can specify which structure elements and documents are to be put in the
configuration guide. If you set the Only with Objects flag, only structure elements to which objects
are assigned, are copied. You can restrict the scope, e.g. to a logical component, project team
member, or documentation type. With Structure, you can call the dialog box Select Substructure, and
select structure elements.
CAUTION
The system only puts the documents of the structure elements which you have selected
explicitly, and of their substructure elements, in the configuration guide. The system assigns
only higher-level structure elements, not their documents (Quick Info Select Nodes
Automatically). To assign documents from higher-level structure elements, choose the higherlevel structure elements explicitly (Quick Info Select Nodes Manually).
20/34
CUSTOMER
2013-05-13
4
Procedure
4.4
Create the Configuration Guide
5.
In the Display Options tab, you can specify which structure element and document information
is to be copied into the configuration guide. Choose also display option IMG documentation.
Choose Execute.
The system tells you where on your PC it will store the Configuration Guide. If there are already
files in the selected download directory, the system warns that they would be deleted. You can
select a different download directory or continue.
Ok¦¦/ú›îÂ¤Ó−[žo�ŒEÉë¾¡Directory for Configuration Guide
6.
7.
To continue the creation of the configuration guide, choose Continue.
When all files have been downloaded, the system sends a message which specifies the download
directory again, and tells you what you have to do next.
2013-05-13
CUSTOMER
21/34
4
Procedure
4.4
Create the Configuration Guide
tš‘ßÓÃ×]ç¶uÒ«y<ÀèÛ=òCˇsConfiguration Guide Files Download
8.
Choose Continue.
If Microsoft Office Word is installed in the computer, it is called with the file solarconfig.doc.
Choose Enable Macros in Microsoft Office Word.
NOTE
The following figures can vary, depending on your version of Microsoft Office Word.
tš‘ßÓÃ×]ç¶uÒ«y<ÀèÛ=óCˇsEnable Macros
9.
In the menu, choose Tools Macro
22/34
Macros .
CUSTOMER
2013-05-13
4
Procedure
4.4
Create the Configuration Guide
Ô¾XH½qOQãêQõ}2P:éœ5ýsˇÏChoose Macros
10. Run the Microsoft Office Word Macro SAP_CONFIGURATION_GUIDE by choosing the button Run.
The macro creates the configuration guide for your project.
Ô¾XH½qOQãêQõ}2P:éœ4ýsˇÏRun the Macro
Your Configuration Guide is now generated. You can save it.
2013-05-13
CUSTOMER
23/34
4
Procedure
4.4
Create the Configuration Guide
*−\±Fßõ¦)nkÒ|⁄H}
ˆ˘>yGenerated Configuration Guide
24/34
CUSTOMER
2013-05-13
5
Adjustments to the Configuration Guide
5 Adjustments to the Configuration
Guide
This chapter tells how you can make adjustments to the layout and behavior of the template files for
creating the Configuration Guide.
The system uses the following three files to create the Configuration Guide:
Õ;kr@ï config.ini
Õ;kr@ï solarconfig.doc
Õ;kr@ï solarconfig.dot
You can adjust these files to your requirements, in the Customizing of SAP Solution Manager. Choose
the following path: SAP Solution Manager Technical Settings Document Management Generation of Documents
Adjust Template Files for Generation of Configuration Guide . Refer to the documentation of this customizing
step for further details.
Embedding files in the Configuration Guide
The following file types are embedded in the Configuration Guide:
Õ;kr@ï DOC: MS Word files
Õ;kr@ï RTF: MS Rich Text Format files
Õ;kr@ï TXT: Text files
Õ;kr@ï XLS: MS Excel files
Õ;kr@ï PPT: MS PowerPoint files
Õ;kr@ï VSD: MS Visio files
Õ;kr@ï HTM: (HTML) Hypertext Markup Language files
The corresponding programs must be installed on the front end computer. Otherwise, the system
creates hyperlinks to the files. The system creates hyperlinks to all other file types, for example PDF
files (Portable Document Format). For further details see SAP Note 777089.
When you generate a Configuration Guide and hyperlinks are inserted in the MS Excel files, not the
content of MS Ecxel documents, see SAP Note 1532866.
2013-05-13
CUSTOMER
25/34
This page is left blank for documents
that are printed on both sides.
A
Reference
A.1
The Main SAP Documentation Types
A Reference
A.1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software.
Cross-Phase Documentation
SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as
well as many glossary entries in English and German.
@5ŽÆ°K Target group:
@5ŽÆ°$ Relevant for all target groups
@5ŽÆ°K Current version:
@5ŽÆ°$ On SAP Help Portal at http://help.sap.com Glossary
@5ŽÆ°$ In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes.
@5ŽÆ°K Target group:
@5ŽÆ°$ Consultants
@5ŽÆ°$ System administrators
@5ŽÆ°$ Project teams for implementations or upgrades
@5ŽÆ°K Current version:
@5ŽÆ°$ On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels. A collective security guide is available for SAP NetWeaver. This document contains
general guidelines and suggestions. SAP applications have a security guide of their own.
@5ŽÆ°K Target group:
@5ŽÆ°$ System administrators
@5ŽÆ°$ Technology consultants
@5ŽÆ°$ Solution consultants
@5ŽÆ°K Current version:
@5ŽÆ°$ On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required installable
units for each business or IT scenario. It provides scenario-specific descriptions of preparation,
2013-05-13
CUSTOMER
27/34
A
Reference
A.1
The Main SAP Documentation Types
execution, and follow-up of an implementation. It also provides references to other documents, such
as installation guides, the technical infrastructure guide and SAP Notes.
4¡›Û>Á Target group:
4¡›Û>® Technology consultants
4¡›Û>® Project teams for implementations
4¡›Û>Á Current version:
4¡›Û>® On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking into
account the combinations of operating systems and databases. It does not describe any business-related
configuration.
4¡›Û>Á Target group:
4¡›Û>® Technology consultants
4¡›Û>® Project teams for implementations
4¡›Û>Á Current version:
4¡›Û>® On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes, and
implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
4¡›Û>Á Target group:
4¡›Û>® Technology consultants
4¡›Û>® Solution consultants
4¡›Û>® Project teams for implementations
4¡›Û>Á Current version:
4¡›Û>® In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The
Customizing activities and their documentation are structured from a functional perspective. (In order
to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,
which refers to the relevant Customizing activities in the individual SAP systems, is used.)
4¡›Û>Á Target group:
4¡›Û>® Solution consultants
4¡›Û>® Project teams for implementations or upgrades
4¡›Û>Á Current version:
4¡›Û>® In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers
28/34
CUSTOMER
2013-05-13
A
Reference
A.1
The Main SAP Documentation Types
users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup/restore, master data maintenance, transports, and tests.
]‚”¸Þi Target group:
]‚”¸Þ System administrators
]‚”¸Þi Current version:
]‚”¸Þ On SAP Service Marketplace at http://service.sap.com/instguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks.
]‚”¸Þi Target group:
]‚”¸Þ System administrators
]‚”¸Þ Technology consultants
]‚”¸Þ Solution consultants
]‚”¸Þi Current version:
]‚”¸Þ On SAP Service Marketplace at http://service.sap.com/instguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of
an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.
]‚”¸Þi Target group:
]‚”¸Þ Technology consultants
]‚”¸Þ Project teams for upgrades
]‚”¸Þi Current version:
]‚”¸Þ On SAP Service Marketplace at http://service.sap.com/instguides
The upgrade guide describes the technical upgrade of an installable unit, taking into account the
combinations of operating systems and databases. It does not describe any business-related
configuration.
]‚”¸Þi Target group:
]‚”¸Þ Technology consultants
]‚”¸Þ Project teams for upgrades
]‚”¸Þi Current version:
]‚”¸Þ On SAP Service Marketplace at http://service.sap.com/instguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release. Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG).
]‚”¸Þi Target group:
2013-05-13
CUSTOMER
29/34
A
Reference
A.1
The Main SAP Documentation Types
ŁÕ@ Consultants
ŁÕ@ Project teams for upgrades
ŁÕ/ Current version:
ŁÕ@ On SAP Service Marketplace at http://service.sap.com/releasenotes
ŁÕ@ In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
30/34
CUSTOMER
2013-05-13
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
2013-05-13
Emphasized words or expressions
Words or characters that you enter in the system exactly as they appear in the
documentation
Textual cross-references to an internet address
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
Hyperlink to an SAP Note, for example, SAP Note 123456
C¥mí|# Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
C¥mí|# Cross-references to other documentation or published works
C¥mí|# Output on the screen following a user action, for example, messages
C¥mí|# Source code or syntax quoted directly from a program
C¥mí|# File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
Keys on the keyboard
CUSTOMER
31/34
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2013 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 of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary.
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 in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.
Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/solutionmanager
32/34
CUSTOMER
2013-05-13
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2013 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.