SAP Solution Manager - Freenagattaque.free.fr/CLEMENCE/Doc aide SAP/Solution_Manager_32_SP… ·...

SAP Solution Manager

Release 3 .2 SP06

SA

P S

OL

UT

ION

MA

NA

GE

R

SAP Online Help 08.04.2005

SAP Solution Manager 3.2 SP06 2

Copyright © Copyright 2004 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. Microsoft, Windows, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. 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 in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



SAP Solution Manager ............................................................................................................ 14 Projects ................................................................................................................................ 15

Roadmap.......................................................................................................................... 16 Roadmap Initial View .................................................................................................... 17 Roadmap Structure View.............................................................................................. 18

Project Roadmap ...................................................................................................... 19 Download Project Structure or Roadmap into MS Project........................................ 20 Creating Offline Variants ........................................................................................... 21

Project Preparation........................................................................................................... 22 Project Administration................................................................................................... 22

Project Types ............................................................................................................ 23 Quick Project Set-Up................................................................................................. 24 Create/Change Project.............................................................................................. 25

General Data ......................................................................................................... 26 Specify Scope........................................................................................................ 27 Project Team Members ......................................................................................... 29 System Landscape Tab......................................................................................... 30

Specify Project System Landscape ................................................................... 31 Assign Logical Components to the Project .................................................... 31 Generate/Assign IMG Projects....................................................................... 32 Specify System Landscape for Central Objects............................................. 34

System Landscape Check ................................................................................. 34 Create Transport Requests in the Component Systems ................................... 35

Templates Tab....................................................................................................... 36 Milestones Tab ...................................................................................................... 37 Organizational Units Tab....................................................................................... 38 Project Standards Tab........................................................................................... 38

Assigning and Creating Project Standards ........................................................ 40 Edit Document Templates.................................................................................. 41

Transport Requests ............................................................................................... 42 Changing URLs in the Solution Manager .............................................................. 44

Transporting Projects ................................................................................................ 44 Copy Projects............................................................................................................ 45 Deleting Projects ....................................................................................................... 45 Assign Authorization for Documents......................................................................... 46 Compare and Adjust with the Template/Source ....................................................... 47

Resolve Differences Between Source and Target ................................................ 49 Upgrade Component Systems.................................................................................. 50

Create Upgrade Project......................................................................................... 51



Create Upgrade Project View ............................................................................ 52 Transferring Project Data to SAP.............................................................................. 52

Set-up Project Data Transfer................................................................................. 53 Pass Project Data to SAP...................................................................................... 54

Migration of Data at Release Update from 2.20 to 3.10 ........................................... 55 Migrate Data from Release 2.20 to 3.10 ............................................................... 56 Set-Up System Landscape and Distribution after Migration ................................. 57 Set-Up Projects after Migration ............................................................................. 59

Solution Manager Project Overview.......................................................................... 59 Solution Manager System Landscape.......................................................................... 60

Set-Up Automatic System Landscape Data Capture................................................ 61 Automatic Data Capture ........................................................................................ 62 Manual Data Source Maintenance ........................................................................ 63

System Landscape Management ............................................................................. 63 Create and Assign Landscape Component Attributes .......................................... 64

Set-up Possible Entries Help for Landscape Component Attributes ................. 65 Edit Products, Product Assignment and Product Version ..................................... 66

Show/Hide products........................................................................................... 66 Create Non-SAP products ................................................................................. 67 Change Assignment of a System to a Product/Product Version ....................... 67

Create Server ........................................................................................................ 68 Create Databases.................................................................................................. 69 Create Systems ..................................................................................................... 69

Generate/Change RFC Connections................................................................. 71 Create Non-SAP Systems ................................................................................. 75 Change Assignment of a System to a Product/Product Version ....................... 76 Define and Edit System Roles ........................................................................... 77

Create System Components and Assign them to Systems .................................. 77 Logical component ................................................................................................ 78

Create/Change Logical Components................................................................. 80 Delete Landscape Elements.................................................................................. 81 Where-used list...................................................................................................... 82 Analyzing the System Landscape by Landscape Components ............................ 82 Landscape Component Graphic............................................................................ 83 Overviews.............................................................................................................. 84 Adaptive Computing Settings ................................................................................ 84 Generate Installation Key for SAP ECC................................................................ 86 Tips ........................................................................................................................ 86

Customizing ID Mapping Framework........................................................................ 87 Using the ID Mapping Framework with an Integration Server............................... 89



Setting-Up Customizing ID Mapping ..................................................................... 91 ID Mapping......................................................................................................... 92 ID Type............................................................................................................... 93 Global ID Type ................................................................................................... 94 Customizing ID Mapping.................................................................................... 95 Customizing ID Type Editor ............................................................................... 95 Global ID Type Editor......................................................................................... 96 Editing Business Systems.................................................................................. 97 Edit System Relationships ................................................................................. 98 Create a Type Group for an Integration Server ................................................. 99 Define ID Mapping ........................................................................................... 100

Define and Export ID Mapping ..................................................................... 101 ID Mapping Export for Several Type Groups ............................................... 102

Replicating ID Mappings.................................................................................. 102 Authorization for the ID Mapping Framework...................................................... 104

Using Templates......................................................................................................... 104 Create a Template Project ...................................................................................... 106 Create and Edit Project Structure ........................................................................... 108 Create and Assign Preconfiguration ....................................................................... 111 Templates Tab ........................................................................................................ 112 Transport Requests................................................................................................. 113 Compare and Adjust with the Template/Source ..................................................... 115

Resolve Differences Between Source and Target .............................................. 116 Global Rollout with a Template ............................................................................... 118

Example for a Global Rollout with a Template .................................................... 119 The Global Attribute in Global Rollout ................................................................. 120 Translate a Template........................................................................................... 121

SAP Solution Manager Roles ..................................................................................... 123 Project Authorization ............................................................................................... 123

Project Manager .................................................................................................. 124 Application Consultant......................................................................................... 125 Development Consultant ..................................................................................... 126 Technical Consultant ........................................................................................... 127

Operational Processing Authorizations................................................................... 128 Solution Directory Roles ...................................................................................... 128 Solution Monitoring Roles.................................................................................... 129 Service Desk Roles ............................................................................................. 132

Business Blueprint.......................................................................................................... 132 Business Blueprint in Projects .................................................................................... 134

Creating and Printing the Business Blueprint Document........................................ 135



Download Project Structure or Roadmap into MS Project...................................... 136 General Documentation Tab....................................................................................... 137 Project Documentation Tab ........................................................................................ 138 Structure Tab .............................................................................................................. 139

Create and Edit Project Structure ........................................................................... 140 Administration Tab...................................................................................................... 142 Transactions Tab ........................................................................................................ 144

Assigning Transactions to a Structure Element...................................................... 145 Messages Tab ............................................................................................................ 146

Create Message...................................................................................................... 147 Graphic Tab ................................................................................................................ 148

Create Scenario/Process Graphic .......................................................................... 148 Configuration .................................................................................................................. 150

Edit Cross-Scenario Configuration ............................................................................. 151 Create/Print Configuration Guide................................................................................ 152 General Documentation Tab....................................................................................... 153 Project Documentation Tab ........................................................................................ 154 Administration Tab...................................................................................................... 155 Configuration Tab ....................................................................................................... 156

Configure................................................................................................................. 157 Development Tab ....................................................................................................... 159 Test Cases Tab........................................................................................................... 160

Link Manual Test Case to Transactions/Reports .................................................... 161 Messages Tab ............................................................................................................ 161 Graphic Tab ................................................................................................................ 162

Creating Training Material and Learning Maps .............................................................. 163 Create End User Roles............................................................................................... 164

Create HR-Org. Object and Info Types................................................................... 165 Create HR-Org. Object............................................................................................ 165 Link Two HR-Org Objects ....................................................................................... 166 Assign User to an HR Org. Object .......................................................................... 166

Create Learning Material ............................................................................................ 167 Assign End User Roles............................................................................................... 167 Create Learning Map .................................................................................................. 168 Send Learning Map .................................................................................................... 170 Analyzing Learning Maps ........................................................................................... 171 Export Learning Map .................................................................................................. 172

Analyses ......................................................................................................................... 172 Business Blueprint ...................................................................................................... 173

Administration ......................................................................................................... 174



Assignments............................................................................................................ 177 Configuration............................................................................................................... 180

Administration ......................................................................................................... 180 Assignments............................................................................................................ 183 Cross-System IMG Analysis ................................................................................... 187 Problem Messages ................................................................................................. 189

Test Organization: Analysis with the Status Info System ........................................... 190 Test Organization: Analysis of Tests by Process ....................................................... 190 System Landscape ..................................................................................................... 191 Analyze Project ........................................................................................................... 192 Process Project Analyses Results .............................................................................. 193

Customizing Synchronization............................................................................................. 195 Prerequisites for Customizing Distribution and Customizing Scout ............................... 197 Customizing Distribution................................................................................................. 200

Quick Guide: Setting-Up Customizing Distribution..................................................... 202 Customizing Distribution ............................................................................................. 204 Synchronization Object............................................................................................... 206

Display Synchronization Object Definition .............................................................. 207 Assign Transport Requests to Source and Target Systems ...................................... 208 Synchronization Group Editor..................................................................................... 210

Synchronization Group for Stand-Alone HR ........................................................... 211 Using Synchronization Groups for Stand-Alone HR ........................................... 212

Create Synchronization Group................................................................................ 213 Specify Filter Conditions ......................................................................................... 215

Types of Customizing Distribution .............................................................................. 216 Initial Distribution..................................................................................................... 216 Setup Automatic Customizing Distribution.............................................................. 217 Distribute Individual Transport Manually................................................................. 219

Logging Customizing Distribution ............................................................................... 220 Display Trace of Incoming Distribution Requests ................................................... 221 Analysing Customizing Distribution......................................................................... 222 Automatic Redistribution after Errors ...................................................................... 223 Display Customizing Distribution Logs.................................................................... 223 Delete Customizing Distribution Logs ..................................................................... 225

Expert Customizing Distribution.................................................................................. 225 Distributing Languages ........................................................................................... 226 Expert Settings........................................................................................................ 227 Customizing Distribution Lock Logic ....................................................................... 228 Local Locks for Customizing Objects...................................................................... 228

Customizing Scout.......................................................................................................... 230



Load Object Lists ........................................................................................................ 231 Compare Customizing ................................................................................................ 232 Display Last Comparison............................................................................................ 234 Change Processing Status of a Comparison Object .................................................. 235

Create and Load Synchronization Objectssapurl_link_0005_0007_0014 ..................... 236 Synchronization Object Specification Tool ................................................................. 238

Specify RFC Destinations ....................................................................................... 240 Edit Synchronization Object .................................................................................... 240 Restrict Synchronization Object Release................................................................ 243 Check Synchronization Object ................................................................................ 245 Specify Filter Conditions for Source and Target Objects........................................ 245

Suitable Objects for the Customizing Synchronization .................................................. 246 Test Organization............................................................................................................... 247

Test Plan Management .................................................................................................. 248 Create Test Plan for a Project .................................................................................... 249 Change Test Plan for a Project................................................................................... 250 Change Project Test Plan Attributes .......................................................................... 251 Transport Test Plan .................................................................................................... 252 Create Test Package for Projects in Solution Manager ............................................. 252 Assign Test Package to a Tester................................................................................ 253

Analyze Status................................................................................................................ 254 Test Plan Problem Overview.......................................................................................... 256

Solution Monitoring ............................................................................................................ 257 Solution Directory ........................................................................................................... 258

Create Solution ........................................................................................................... 259 Create and Delete Logical Components..................................................................... 260 Assign Solution Attributes........................................................................................... 261 Copy Business Scenarios........................................................................................... 262

Solution Directory Copy Scenarios ......................................................................... 264 System graphic ........................................................................................................... 266 Server Graphic............................................................................................................ 267

Manage Solution............................................................................................................. 268 Navigation in Operational Processing ........................................................................ 268 Overview of Active Solutions ...................................................................................... 270 Copy Solutions............................................................................................................ 272 Edit Solutions.............................................................................................................. 272

Project Overview ..................................................................................................... 273 Activate and Deactivate Solutions .............................................................................. 274 Delete Solution............................................................................................................ 275 SAP Solution Manager Self Diagnosis ....................................................................... 275



Using SAP EarlyWatch Alert .......................................................................................... 276 SAP EarlyWatch Alert................................................................................................. 277

Perform SAP EarlyWatch Alert Download Manually............................................... 278 Create SAP EarlyWatch Alert Report, Display Details, Send E-mail...................... 280 Save, Activate and Archive SAP EarlyWatch Alert ................................................. 281

Using Service Level Reporting ....................................................................................... 282 Service Level Reporting.............................................................................................. 284

Set-Up Service Level Reporting.............................................................................. 284 Service Level Reporting Change Mode............................................................... 285 Maintain General Settings ................................................................................... 286 Specify Systems for Service Level Report .......................................................... 287 Select Business Processes for the Service Level Report ................................... 288 Select Business Processes from the Business Process Monitoring ................... 289 Process Service Level Report Data Manually ..................................................... 289

Create Service Level Report ................................................................................... 290 Save, Retrieve and Archive Service Level Report .................................................. 291 Process Service Level Report Session................................................................... 292

System Monitoring.......................................................................................................... 293 System Monitoring Change Mode .............................................................................. 294 CCMS and SAP Solution Manager............................................................................. 295 Set-Up System Monitoring.......................................................................................... 297

Select Active Systems............................................................................................. 297 Check RFC Connection for System Monitoring ...................................................... 298 Set-Up System-Specific Checks ............................................................................. 298 Copy Customizing ................................................................................................... 299 Insert Additional Hardware Components ................................................................ 300 Insert Software Components................................................................................... 301

Display Alert................................................................................................................ 301 Reset Alert .................................................................................................................. 302 Define User Alerts....................................................................................................... 303

Central System Administration ....................................................................................... 304 Set-Up Central System Administration ....................................................................... 305

Central System Administration: Seesion Change Mode......................................... 305 Choose Administration and Monitoring Work Area................................................. 307 Task View Master.................................................................................................... 308 Report Content........................................................................................................ 308 Copy Default Settings ............................................................................................. 309 Check RFC Connection .......................................................................................... 310 Customizing Task Log Book and Task Log History ................................................ 311 Specify System Data and Initially Set-Up Tasks..................................................... 311



Set-up Report Cover Page...................................................................................... 312 Create User-Specific Tasks ........................................................................................ 312 Process Open Tasks .................................................................................................. 314

Using Business Process Monitoring............................................................................... 316 Business Process Monitoring ..................................................................................... 317

Session Change Modes .......................................................................................... 318 CCMS and SAP Solution Manager ......................................................................... 320 Specify New Business Process .............................................................................. 322

Select Business Processes ................................................................................. 322 Specify Business Process ................................................................................... 323 Specify Business Process ................................................................................... 324 Set-Up Contact Data ........................................................................................... 324

Set-Up Business Process Monitoring ..................................................................... 324 Define Solution Support Organization ................................................................. 325 Select Business Processes ................................................................................. 326 Business Process Monitoring <Business Process> ............................................ 327 Subcheck: Message Control Templates.............................................................. 327 Subcheck: Set-Up Process Step Monitoring ....................................................... 328 Subcheck: Generate Monitoring Customizing..................................................... 329 Frequency of Data Collection .............................................................................. 329 Set-Up Local RFC Connections .......................................................................... 330 Set-Up Interface Monitor Objects ........................................................................ 330

Business Process Monitoring Session.................................................................... 333 General Settings.................................................................................................. 333 Activate/Deactivate Business Process Monitoring .............................................. 334 Display Alert Information ..................................................................................... 335

Display Alert ............................................................................................................ 335 Confirm Alerts.......................................................................................................... 336

Service Desk ...................................................................................................................... 337 Using the Service Desk .................................................................................................. 338 Set-Up Message Creation via Web Browser.................................................................. 339 Process Messages in the Service Desk......................................................................... 340 Find Solution for Support Message................................................................................ 341 Forward Support Message to SAP................................................................................. 342

Change Request Management .......................................................................................... 343 Roles in Change Request Management ........................................................................ 344

Service Desk Roles .................................................................................................... 344 Schedule Manager Roles ........................................................................................... 344 Satellite System Roles................................................................................................ 345 Authorizations ............................................................................................................. 347



Central Configuration Tool of Change Request Management ....................................... 348 Scheduling the Data Collector .................................................................................... 349 Displaying and Configuring Distribution Routes ......................................................... 349 Activating Project Status Switches ............................................................................. 353 System Change Option............................................................................................... 353 Project Interdependencies .......................................................................................... 355

Scheduling Tool of Change Request Management ....................................................... 355 Creating a Maintenance Cycle.................................................................................... 356 Status Administration of Task Lists for Maintenance Cycles...................................... 358 Urgent Corrections...................................................................................................... 359 Scheduling the Automatic Import of Urgent Corrections ............................................ 360 Resetting Unsuccessful Corrections........................................................................... 361 Changing the Status of Maintenance Cycles.............................................................. 361 Analyzing Maintenance Cycles and Urgent Corrections ............................................ 363

Using Project Logistics ................................................................................................... 366 Using the Scheduling Function................................................................................... 367 Using the Tracking Function ....................................................................................... 367 Using the Planning Function....................................................................................... 368 Using the Project Monitor ........................................................................................... 368 Using the Project Structure Function.......................................................................... 369 Activating CTS Status Switches ................................................................................. 369 Displaying/Changing System Change Options........................................................... 370

Change Tracking in Change Request Management ...................................................... 370 Tracking Changes for One Project ............................................................................. 371 Displaying Information About Transport Requests in One System ............................ 373 Comparing Transport Requests in Two Systems....................................................... 374 Tracking Transport Requests Across a Transport Route ........................................... 375

Change Transactions in Change Request Management ............................................... 375 Workflow for Maintenance Cycles .............................................................................. 376 Workflow for Regular Corrections............................................................................... 377 Workflow for Urgent Corrections................................................................................. 378 Making User Settings for Change Request Management .......................................... 379 Transaction Codes for Worklists in Change Request Management........................... 380 Creating a Change Request ....................................................................................... 380 Approving a Change Request..................................................................................... 381 Rejecting a Change Request...................................................................................... 382 Making a Regular Correction in a Development System............................................ 382 Making an Urgent Correction in a Development System ........................................... 383 Testing an Urgent Correction...................................................................................... 385 Importing an Urgent Correction into a Production System ......................................... 386



Completing an Urgent Correction ............................................................................... 387 Urgent Corrections: Troubleshooting.......................................................................... 387




Purpose The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.

Features Implementation of the mySAP Business Suite

• All phases of the implementation project (Business Blueprint [page 132], Configuration [page 150]) are performed centrally in the Solution-Manager system.

• Central project documentation repository in the Solution Manager

• Integrated Project Administration [page 22] allows you to manage planning schedules, human resources and other project data.

Customizing Synchronization

• The Customizing Scout [page 230], with which you can compare customizing in various SAP components, e.g. SAP R/3 with SAP MDM

• The Customizing Distribution [page 200], with which you can synchronize customizing in various mySAP components.

Test

• You can use the Test Workbench to organize [page 247] and perform tests at the end of a project phase.

• Reuse of the project structure for process-oriented tests

Global rollout

Integrated authoring environment, with which customers and partners can create their own templates [page 104], which they can reuse in subsidiaries, e.g. in a global rollout [page 118]

E-Learning management

Creation of training material and learning maps [page 163] (computer-supported self-tuition courses) to train end users after the implementation of new functions

Solution Monitoring

• Central System Administration [page 304]

• Analyze your system landscape with Service Level Reporting [page 282]

• System monitoring [page 293] in real time

• Business process monitoring [page 316]

Services

Access to programs and Services [external link], which help you to monitor and optimize the performance and availability of your system landscapes, and minimize your operational system risks

Service Desk

Solution support [page 337] with workflow to create and handle problem messages



Change Management

Management of change requests, with workflow for the monitoring and audit of changes and transports in your system landscape, with the Change Request Management [page 343].

See also:

• Projects [page 15]

• Solution Monitoring [page 257]

Projects

Purpose Using the SAP Solution Manager for evaluation and implementation (implementation project)

You can use the SAP Solution Manager to evaluate and implement your solution.

Using the SAP Solution Manager to create preconfigured content (templates)

You create a solution with the SAP Solution Manager, which serves as a template for your implementation project. The solution contains a package of reusable preconfigured content (documentation, preconfiguration, and test cases). The following section only describes the typical process flow of an implementation project. See Using a Template [page 104] for more information on creating preconfigured content and templates.

Process Flow ...

1. The Roadmaps [page 16] contain information and procedures for all phases of your project.

In the SAP Solution Manager, you use the functionality of the Knowledge Warehouse that is delivered with the SAP Web Application Server. The SAP Solution Manager will also work if you have already installed a version of the Knowledge Warehouse. However, this is not a prerequisite for use of the SAP Solution Manager.

2. Your work with the SAP Solution Manager really begins after the evaluation phase. The first step is to define your project in the Solution Manager:

a. You enter administrative data in the Project Administration [page 22] transaction, for example, details of project dates and resources.

b. Specify the Project Scope [page 27].

c. Define the System Landscape [page 31] for the implementation of your solution.

3. You define a Business Blueprint [page 132] by documenting the organizational units, master data, business scenarios and business processes you require for the implementation of your solution. During the Business Blueprint definition, you read the documentation supplied by SAP and partners, create your own project documentation, and assign individual process steps to transactions.

4. From the Solution Manager, Configure [page 150]your business scenarios in the development systems.

5. You check the test cases delivered with your solution and assign further Test cases [page 160] to processes and process steps.



6. You perform consistency checks for the customizing of your business processes mit dem Customizing Scout [page 230], i.e. you check whether the Customizing is the same in the various application components. You synchronize customizing with the Customizing Distribution [page 200].

7. You can organize tests [page 247]. You can reuse the test cases selected during configuration.

8. You create training material and learning maps [page 163] (computer-supported self-learning courses) to train the end users.

• You can analyze your project [page 172] at any time, to determine its status and the progress made in testing or configuration.

• You can show and hide tabs in the Business Blueprint and the Configuration, in the user settings.

Roadmap

Purpose The Roadmaps are part of the SAP Solution Manager. They contain the standard SAP implementation methodology and cover the most important aspects and phases of a mySAP.com implementation. The Roadmaps provide links to accelerators and tools which perform project tasks.

Integration If you have assigned a Roadmap to your project in the Project Administration [page 27], the milestones of the selected Roadmap are displayed in the Milestones [page 37] tab in the Project Administration.

Features

View without project link If you have not yet defined a project in the SAP Solution Manager, or your project is not yet assigned to a Roadmap, the Solution Manager offers you a selection of Roadmaps without project link, when you first call it.

To go from a Roadmap with project link to a Roadmap without project link, choose Other Project → No Project and choose a Roadmap.

Roadmaps without project link are display-only.

You can:

• Navigate in the structure

• Search for entries in the Roadmap structure

• Display assigned documents and accelerators

• Milestones identify the project phases

• Service packs identify links to the SAP Service Marketplace with information about suitable SAP services

• Filter the Roadmap structure by roles, topics or flavors

• Print documents or structures with their documents



• Download the Roadmap as offline (HTML) version [page 21]

View with project link Other Project goes to the Roadmap which was assigned to your project in the Project Administration.

If you use a Roadmap in your implementation project, you can use the following functions as well as the Roadmap without project link functions:

• Assign keywords for the Roadmap structure elements

• Assign a status for the Roadmap structure elements

• Assign project team members to structure elements

• Filter the Roadmap structure by keywords and project team members assigned

• Create project-specific notes for the Roadmap structure elements

• Create project documentation

• Create messages [page 161]

• Download the Roadmap into MS Project to create a project plan [page 136]

Restrictions You cannot change the structure of the Roadmap.

Roadmap Initial View

Definition The initial view of the Roadmap is a simplified overview of the project steps required in a mySAP Implementation.

Use The initial view shows the project team members the Roadmap steps relevant for their project. There are links to the substructures of the Roadmap structure view.

Structure

PhasesThe first level of the Roadmap structure, the Roadmap phases, are arranged horizontally.

Work area The work area is structured, and contains links to work packages, activities and tasks in the structure view of the Roadmap. Select a link to go to the structure view of the Roadmap in the same session. You can display the Roadmap and documents. Back takes you back to the initial view.

Status The system can also display the processing status, and the status of the messages of the steps or their substeps.

Integration Filters which you use in the Roadmap structure view, have no effect in the initial view of the Roadmap.



Roadmap Structure View

Definition The structure view is a complete view of the Roadmap.

Structure

Project area The left-hand screen area contains the structure of the Roadmap with attributes. The structure comprises the following elements:

• Phase (level 1) The Roadmap comprises phases which each represent a major part of the implementation project.

• Work package (level 2) Each phase of the Roadmap contains work packages to accomplish the objectives of the phase. Work packages contain activities and tasks.

• Activity(level 3) Each work package comprises activities. Activities contain tasks to be performed by one or more project team members to achieve the specified objectives. This level contains accelerators, i.e. documents, templates and guidelines which help you to implement a mySAP solution.

• Task (level 4) Each activity comprises several tasks. The Roadmap documents describe in detail the steps required to carry out a task. The tasks are performed by project team members. This level also contains accelerators for the implementation of the mySAP solution.

View area A description of the structure element selected in the project area is displayed at the top right-hand side of the screen.

Filter functionsThe filter function restricts or expands the structure view and the initial view of a Roadmap, by roles, subject areas and flavors.

If the attributes which SAP assigned to an accelerator do not match your filter conditions, the accelerator is hidden. You can display the attributes of an accelerator by double-clicking on the Attributes icon in the Accelerator tab.

You can additionally restrict or extend the view of a Roadmap with a project link, by the status of the structure elements and the keywords which you have assigned.

Extended search function You can list the following information below a structure step, with Goto:

• Accelerator

• Notes

• Messages

• Project documentation



User interface settings • Specify whether you enter the Roadmap via the structure view or the initial view, in

Settings → User-Specific.

• You can show or hide the structure (Work Breakdown Structure (WBS)) numbering with Roadmap → Show or Hide WBS Numbering.

Project Roadmap

Use You use a project roadmap in an implementation project to document the progress of the project, and to provide and distribute information to the project team.

Prerequisites You have created a project [page 25] in the Project Administration, and assigned a roadmap to the project.

Features

Accelerator tab The system lists Accelerators [external link], e.g. Word documents, Powerpoint presentations and transactions, in the accelerator tab. Double-click on the accelerator to call it.

You can display a list of accelerators assigned to each structure step. Choose Goto → Accelerators.

Status/Notes tab • You can make notes about structure elements, in the Status/Notes tab. The system

saves your entries automatically when you leave the tab.

• To change the status of a structure step, choose the status symbol in front of the structure step or set the status with the pushbutton on the Status/Notes tab.

The status is passed upwards in the structure. If you change the status which was passed upwards, for a higher-level structure step, in the structure, the system flags the status of this structure step as set manually, with an icon. You can reset the status of the structure step to the inherited status with the Status pushbutton.

Project Team Members tab You can assign structure elements to the Project Team Members [page 29] which you have put in your project, in the Project Administration, in the Project Team Members tab.

Messages tab You can create and send messages in the Messages tab. See the Messages [page 161] tab for further information.

Project Documentation tab • You can insert documents, transactions and URL links, and assign structure steps, with

pushbuttons.

• Double-click on the assigned elements to display or run them.



Keywords tab You can assign the project-specific keywords, which you assigned to your project in the Keywords subtab of the Project Standards [page 38] tab in the Project Administration, to each structure step, in the Keywords tab. These keywords help you to find structure elements during Project analysis [page 172].

You can pass on the keyword(s) which you have assigned to a structure step, downwards in the structure, with the Make Mass Changes pushbutton in the Keywords tab. You can delete these keywords passed on to the lower-level structure steps, with the Delete Entry pushbutton.

Download Project Structure or Roadmap into MS Project

Use You download the project structure or a roadmap into MS Project to plan your project using the data in the project structure or roadmap.

Prerequisites MS Project is installed on your local computer.

You have also created a project structure in the Business Blueprint phase or called a roadmap. You are in the Business Blueprint transaction or the structure view of a roadmap.

You have created at least one structure element with data, at the lowest level, under each structure element in the Business Blueprint, so that the data is displayed correctly in MS Project.

Procedure ...

1. If you are in the Business Blueprint transaction, choose Business Blueprint → Download to MS Project.

If you are in the structure view of a roadmap, choose Roadmap → Download → MS Project Version.

2. Choose a folder for the file, in the following dialog box, and change the file name if required.

3. Save.

4. Confirm the following system message with Continue.

Result The project structure or the roadmap is generated as an .mpx file and displayed in MS Project. You can now save the file in .mpp format and edit it.

Make the following settings in MS Project, so that it displays all required fields after you have downloaded a roadmap or a project structure: ...

1. Define a user display table with View → Table → Other Tables... → New.

2. Create one or more of the following fields for the display table, as required:

Fields generated by SAP



Field Meaning

Unique ID Sequential number in MS Project

Text1 SAP GUID of structure element

Name Name of structure element

Outline Level Outline level of structure element

Priority Priority of structure element

Milestone Milestone flag in the Roadmap

Text2 Status of structure element

% Complete

Baseline Start

Baseline Finish

Baseline Duration

Actual Start

Actual Finish

Actual Duration

Remaining Duration

Resource Names Project Team Members

Creating Offline Variants

Use You can create an offline version of the Roadmap documentation, download it to your laptop and read it offline.

You can thus read documents independently of an SAP system.

Procedure ...

1. Select Roadmap → Download → HTML Version.

2. Choose documentation types (for example, Accelerator) in the dialog box. They are displayed as tabs in the initial screen of your offline version.

3. Choose the Create Shortcut checkbox.

4. Confirm the proposed directory, or specify another, in the Directory dialog box.

2. and 3. are optional. 4. is mandatory.

5. Choose Continue to generate the HTML version.

Result The offline version is saved on your local hard disk. You can now see the contents of the Roadmap in your laptop, independently of your SAP systems.



Project Preparation

Purpose You perform all central activities in the project preparation transaction in order to:

• Structure and organize a project

Project Administration [page 22] in the Solution Manager supports you during project preparation and enables you to carry out all administrative tasks relevant for the entire project.

• Create and manage the System Landscape [page 60] for your project

Project Administration

Purpose You perform all central project administration tasks, in the Solution Manager project administration (transaction SOLAR_PROJECT_ADMIN). You perform the Business Blueprint and configuration in the projects which you create in the project administration.

Features Functional scope of project administration

• Function • Navigation • What you need to know

Create Projects [page 25] Initial screen of transaction SOLAR_PROJECT_ADMIN

There is a web-based assistent to create projects quickly [page 24], as well as the project administration.

Determining general data at the beginning and at the end of the project

General Data [page 26] tab Optional

Defining the project language General Data [page 26] tab Obligatory

Project language cannot be changed later

Define project scope, put templates in project

Scope [page 27] tab Optional

Assigning project members Project Team Members [page 29] tab

Optional

Defining project standards (status values, documentation types, keywords)

Project Standards [page 38] tab

Optional

Defining the system landscape for your project

System Landscape [page 30] tab

Obligatory for subsequent navigation in component systems

Distribution of IMG projects into the component systems

System Landscape tab → IMG Projects subtab

Obligatory for configuration of component systems



Project transport details Transport Requests [page 113] tab

Only in template projects

Obligatory for template projects whose templates are to be used in other systems

Create, release, transport templates

Templates [page 112] tab Only in template projects

Create transport requests in component systems [page 35]

System Landscape tab → IMG Projects subtab

Obligatory for configuration and customizing distribution

Any existing projects are automatically displayed in the Solution Manager Project Overview [page 59].

Project Types

Definition The project types delivered with the SAP Solution Manager allow you to differentiate between different types of projects. You can use the SAP Solution Manager to create the following projects:

• Implementation Project

Implementation project based on a selection of business processes in a mySAP landscape.

There are three ways of performing an implementation project:

� Create a project structure based on one or more user or partner scenarios as a template

� Create a project structure based on an existing production solution landscape

� Create a completely new project structure

The structure of an implementation project cannot be reused by other projects.

• Template Project

A project to create a template.

You can base your solution on SAP, partner or global templates. When creating a template you can:

� Change and add documentation

� Define and add preconfigured elements such as BC Sets, test cases, or IMG activities

� Edit the delivered scenario structure(s)

You can reuse the structure of a template project in other projects, independently of the template project in which it was created. Template projects are especially suited to SAP partner solutions or global rollout.

• Upgrade Project

A project to upgrade existing systems.

In an upgrade project you can:

� Upgrade customizing: Upgrade existing functions

and/or



� Delta customizing: Copy additional functions

• Optimization project

A project to optimize the flow of business processes, or the use of a software solution.

You can use optimization projects, for example, in SAP Services.

• Safeguarding project

A project to resolve a critical situation in the implementation or use of an SAP solution.

Safeguarding projects show the reasons for a critical situation and coordinate the steps required to resolve the problems.

Integration The project type you select for your project determines the edit options available to you in the project phases (Business Blueprint, Realization).

Quick Project Set-Up

Use This function creates Solution Manager projects quickly. A web-based wizard leads you through the project creation steps.

You use this function, for example, if you are using the Solution Manager for the first time, or if you do not yet have any experience with customizing or Solution Manager project management.

The Quick Project Set-Up can create projects independently of a concrete system landscape.

Integration You edit the implementation project further in the Business Blueprint and create a project structure based on the selected templates and solutions.

The quick project set-up does not require an existing system landscape. You can, for example, create a project and begin the Business Blueprint phase before the system landscape is ready.

To process your project further in the Configuration phase, set-up your system landscape and put the component systems to which you want to go, into the project system landscape, in the Project Administration.

Prerequisites You have the role project leader (SAP_SOLAR_PM).

Features • Create an implementation project

• Specify the header data

• Select templates on which to base your project

• Selection solutions from the business process and szenario repository (Business Process Repository)

• Select products and product versions

• Select scenarios from the templates and solutions



Activities ...

1. Choose Quick Project Setup: (transaction AI_SPS) from your SAP Easy Access role menu.

2. A wizard leads you through the project set-up steps.

Create/Change Project

Prerequisites You need the authorizations described in Authorization Concept [page 123] to create projects in the SAP Solution Manager.

You are in the initial screen of the Project Administration transaction in the SAP Solution Manager.

Procedure ...

� Choose Project → Create.

1. Enter a project name in the Create Project dialog box, and choose Continue.

The project name may contain a combination of letters and numbers up to 10 characters in length.

2. Select a Project Type.

See Project Types [page 23] for an overview of the different project types and their use.

You cannot change the project type later, in the same project. To change the project type, e.g. if you have created an implementation project, but realize that you want to create templates with it, copy the project [page 45], and change the project type of the new project.

3. You can assign a solution landscape to the project.

If you create your project structure in the Business Blueprint phase, you can later put structure elements from the selected solution landscape in your project structure.

4. Choose Continue.

You go to the Maintain Project screen.

5. Enter a meaningful project name and language.

6. Save the header data for your project.

7. Enter a name for the enhancement context in which the project documents are to be saved in the SAP Knowledge Warehouse, in the next dialog box.

8. Choose Continue.

9. For a template project, enter a package in which the project structure is to be saved, in the dialog box that appears.

The system copies the package specified here into the Transport Requests tab and uses it by default for subsequent changes to the scope or the project structure in the Business Blueprint. If you want to avoid this package being used later by default, delete it from the Transport Requests tab.

See Transport Requests [page 113] for further information.



10. Save your entries.

Result The saved project is put in the SAP Solution Manager project overview. You can now specify header data for the project:

• General Data

• Scope

• Project Team Members

• System Landscape

• Project standards (status values, keywords, document types)

• Milestones

• Organizational Units

• Templates (only for template projects)

• Transport requests (only for template projects)

• To change the header data for the project, select Project → Change. You cannot change the project language after you have saved the header data for your project.

• You can distribute project header data changes to the component system project IMGs with Edit → Distribute Project Header Data.

General Data

Use You enter the administrative data for your project on the General Data tab.

Prerequisite You have defined the following header data in the Solution Manager Project Administration transaction:

• Project

• Project type

You are in the Project Administration transaction in change mode.

Features You can enter the following data on the General Data tab:

• Project leader

� Type of leader, e.g. customer or system house (VAR/CBS)

� Customer person responsible

You can use the possible entries help to change the default user.

� Consultant person responsible



When a project team member creates a new project, the system displays his user name in the Person Responsible field.

The person responsible must be in the SAP system user administration. You can display information about the persons responsible, e.g. OSS user and e-Mail address, with Details.

• Project language

The project language makes all language-dependent information for this language (project documentation and status information) available to all project members, independently of their logon language. You can only change documentation in the project language.

The project structure is created in the specified project language.

You cannot change the project language later.

• Project description

You can upload or create a document, e.g. a project charter.

• Status

You can set the default values for the status on the Project Standards tab.

• Plan data

You can enter the dates for the planned project start and finish and the work required in person days (PD), in this tab.

• Actual data

This tab allows you to enter the dates of the actual project start and finish and the actual work carried out in person days (PD).

The planned and actual data comprise the timespan of the entire project. Any dates specified for process steps, in the Business Blueprint or Realization phases, must lie within this timespan.

The remaining work required is calculated from the difference between the planned data and the actual data and generated as a percentage in the Completed field. You can manually change the remaining work entry at any time.

Specify Scope

Use Select a Roadmap which your project team members will use. The system displays this Roadmap by default, when the Roadmap transaction is called later for your project.

Specify which templates you put in your project. This puts the structure of the templates, and their assignments, in your project.

Prerequisites You are in the Project Administration transaction in change mode.



Procedure ... ...

1. You can choose a Roadmap in the Roadmap Selection tab.

2. Select the templates that you want to implement your project or create your template, in the Template Selection tab.

The system lists all templates to which at least one scenario and a template ID have been assigned, with the naming convention <template ID> - <template name>, e.g. ZBANK – Banking Europe.

Templates may have been created in the current Solution Manager system, or another system, e.g. a company headquarters can create a template in a Global Rollout [page 118], and import it into the systems of its subsidiaries.

The logical components or the product version which have been assigned to the template can differ from the system landscape of your current project.

3. To adjust the logical components and the product versions from the template to your current system landschaft:

a. Choose the template.

b. Save your entries.

c. Choose the logical component which you use in your current project, or create a new logical component, from the possible entries help in the following dialog box.

d. You can change the product version.

e. Copy your changes with Continue.

4. You can restrict the countries for which your project is valid, on the Country Selection tab. Use the arrows to copy the relevant countries from the Possible Countries table into the Selected Countries table.

You can restrict the extent to which project members are able to work on the Business Blueprint on the Scope tab:

Lock in Business Blueprint:

� Structure processing:

You can no longer extend or restrict the scope of the project structure.

� Edit structure, changes to documents in the Administration tab:

• You can no longer extend or restrict the scope of the project structure.

• You can no longer change Blueprint-relevant project documentation;


Result If you have assigned a Roadmap to your project, you can put information about your project, e.g. the status of project steps or messages, in this Roadmap with Project Link [page 19].

You have selected the templates upon which the Business Blueprint is to be based. The structures of the templates, and the assignments to the template structure, are put in your project structure.



Project Team Members

Use You use this tab to create and update the list of team members for your project. Any number of project team members can be assigned to each project. The project leader makes this assignment in the project administration transaction.

You can use users defined in user administration and generic users (users not created in the user administration) for your user assignments. To check whether the project members listed on this tab are already present in the user administration of your SAP System, choose the Check against user master record button. Team members who are not SAP users are highlighted in the list.


Integration Members of staff assigned to the project on this tab are displayed in a selection list when you enter task-specific administrative data on the Administration tabs in the following project phases or transactions:

Members of staff assigned to the project on this tab are displayed in a selection list when you enter task-specific administrative data on the Administration tabs in the following project phases or transactions:

• Roadmap: Project Team Members tab

• Business Blueprint: Administration tab

• Configuration: Administration, Configuration and Development tabs

Activities ... ...

1. Enter the name of a project member in the Project Member column. You can use the possible entries help to find and assign employees you have already entered in user administration.

You can also assign employees to the project directly after you have entered them in user administration. To go to the user maintenance transaction, double-click on the name of an employee, or choose the User Administration button. The extent to which you can call up the user maintenance transaction and change user data is dependent on your project role and the corresponding authorization profile.

2. You can enter a description of the project member in the Name/Description field. This field is only available for internal project use. You can use it, e.g. to document the assignment of a tem member to a subproject or a project group. If the user is recognized in the SAP System, the user name appears here by default.

3. You can specify the names and details of the SAP partners who are involved in the project.



System Landscape Tab

Use You define the system landscape for your project in this tab.

Integration The following functions are available, depending on the system landscape you define:

• Navigation to business content in the component systems

You can go from Business Blueprint [page 134], Configuration [page 150] or Testing [page 247] in the Solution Manager, to the other logical systems, for example, to demo or development systems, to examine their business content (transactions, BC Sets, CATTs, programs, etc.). You can select the logical system in each phase from the System Role.

Choose RFC connection type Trusted System to make logon to the component systems easier. Logon to component systems is then automatic.

Prerequisites for this Trusted System connection:

• The same user is used in the Solution Manager system and the target component system

• The user has authorization for the authorization object S_RFCACL

For further information, see Generate RFC Connections [page 71].

• Generate IMG projects in the component systems and distribute central project data

• Comparison and distribution of customizing in the local systems

You are in the customizing client of your SAP R/3 system and want to configure a business process. You have to synchronize the customizing with the customizing of another SAP component. You can compare the customizing using the Customizing Scout [page 230] in the SAP Solution Manager. You can also automatically adjust this customizing with the Customizing Distribution [page 200]. The system landscape defined in project administration shows the Customizing Scout in which logical systems the customizing is to be compared.

• Generate a business process graphic

You can generate graphics at scenario and process level that show in which logical components the processes of a scenario or the process steps of a process run.

Activities ...

1. Define the System Landscape [page 31] for your project.

2. Check your System Landscape [page 34].

3. You can create transport requests in the component systems [page 35] for a template project.



Specify Project System Landscape

Use You must define the system landscape for your project, before you can access the component systems in subsequent project phases.

Prerequisites You have created a project.

Procedure ...

1. Specify logical components in the System Landscape Maintenance (SMSY).

From Release 3.20, you can only assign logical systems to the logical components in the System Landscape Maintenance, not in the Project Administration.

You go to the system landscape maintenance from the project administration, with Goto → System Landscape → Edit Logical Components [page 80], or from the Systems subtab of the System Landscape tab, by double-click on an existing logical component.

2. Assign [page 31] the logical component to your project, in the Systems subtab, in the System Landscape tab, in the Project Administration.

3. To be able to navigate in the configuration in the component systems, generate [page 32] new IMG projects in the component systems, in the IMG Projects tab, or assign existing IMG projects to the project.

4. Specify the System landscape for central objects [page 34].

5. If your project is an upgrade project, create IMG views in the component systems [page 52].

Assign Logical Components to the Project

Use A logical component is an administration unit which uniquely assigns logical systems to system roles for a product, throughout the system landscape and across projects.

Prerequisites You have specified logical components [page 80] in the system landscape maintenance (SMSY).

Procedure ...

To be able to call the functions in the table, you are in the project administration in the change mode of the project, in the Systems subtab of the System Landscape tab.

Systems tab

Function Navigation What you need to know

Copy logical components from the scenarios which you have assigned to the project in the

→ Scenario selection



Scope tab → Template Selection tab

Assignment of logical components to the project

→ Possible entries help in the Logical Components column

The system copies the logical components, their Products/Main Instances and the highest Product Version.

Create a new logical component

→ Possible entries help in the Logical Components → Create New Components column

or

Goto → System Landscape → Edit Logical Components

You go to the system landscape maintenance (SMSY).

Change an existing logical component

Double-click on the logical component

You go to the system landscape maintenance.

See Create Logical Components [page 80] for further information.

Replace a logical component with another in the entire project structure

→ Replace Log. Component

Change the system roles, their sequence, and the assignment of system roles to project phases

→ System role assignment You can also change the test system selected, at any time, in the Test Organization

Create user system roles and delete system roles for your project

→ System Role Assignment → System Roles

You cannot delete system roles which are used in your system landscape

The systems which you specify in the logical components for the system roles, are used by default in the following project phases:

Use of systems

System role Phase

Evaluation Business Blueprint

Development Realization

Quality assurance Test

Generate/Assign IMG Projects

Use You generate the IMG projects in the component systems, to be able to go to the IMGs in the component systems, in the configuration.

When you generate the IMG projects, you distribute the following central project data into the component systems:



• Project standards:

� Status values which do not yet exist in the component system

� Keywords

• Project Team Members

• Country selection

Prerequisite You have assigned logical components to the project in the System Landscape tab. You now see the associated IMG projects, in the IMG Projects tab, i.e. all subprojects in the component systems which belong to your Solution Manager project.

Procedure

Generate IMG projects in the component systems

The green and red traffic lights indicate whether Project IMGs have already been generated and distributed.

• Red (dot): Project does not yet exist

• Green (square): Project exists in the specified logical components and the assigned logical systems.

To generate and distribute a project: ... ...

1. Choose the system role for IMG Projects.

2. Select the IMG project and Create IMG Project.

The generation and distribution is started in the component systems.

When the Project IMGs are generated in the component systems, everything is initially set in scope.

As soon as the project exists, the green traffic light symbol appears. You also get a system message in the component system as soon as generation is finished.

3. To go to the project IMG later and regenerate, select the subproject and Change.

You go to the header data of the project.

Assign existing IMG project To assign another IMG project from the component system instead of the default IMG project: ...

1. Select an IMG project.

2. Choose Replace.

3. Confirm the confirmation prompt.

4. Choose an IMG project from the list, and confirm the selection.

5. You can create a transport request in the subsequent dialog box. You can assign tasks in this request to other project team members.

6. Choose Continue to save your entries.

The newly-assigned IMG project appears on the IMG Projects tab.



Result You have distributed the project data into the component systems, and can now navigate in the component systems, in the configuration.

Specify System Landscape for Central Objects

Use If you specify a system landscape for central objects, you can define a central repository for objects such as manual test cases, external applications and eCATT test configurations, with it. You have, for example, a central system for the eCATT test development, and want to save manual test cases and external applications in a central system as well, instead of in various component systems.

The central system for eCATT test configurations or for manual test cases and external applications, can be the SAP Solution Manager system, or other central systems which the SAP Solution Manager accesses by RFC.

Prerequisites If you do not want to use the SAP Solution Manager system, you have created an RFC destination to the central systems which you want to use. You are in the des SAP Solution Manager Project Administration, and are editing a project.

Procedure ...

1. Choose the System Landscape tab.

2. Choose the subtab Central Objects.

3. Aassign a logical system to the object type eCATT Test Configuration or Manual Testfall and External Application.

4. If you want to force all project team members to put the objects in the central systems only, set the Use is Obligatory flag.

Result When project team members create or assign test cases of type eCATT, manual test case or external application, to the project structure, in the Test Cases tab, in the Configuration transaction, without specifying a component, they are automatically put in the central systems. The same appllies to the assignment of eCATT test configurations in the Configuration tab.

System Landscape Check

Use This function checks the consistency of the system landscape of a project. It ensures that you can navigate among the component systems in the system landscape.

Integration You can check the system landscape in the Business Blueprint, Configuration or Test Plan Management, in the Project Administration.



Prerequisites You have created a project and its system landscape in the Project Administration.

Features The system landscape check checks:

• have logical components been specified for the project?

• are the logical components and the logical system based on the same product version (release)?

• are the releases and the Support Package statuses of the logical systems sufficient to be able to navigate in the component systems with the SAP Solution Manager?

• do the logical systems have RFC connections?

• do the RFC connections work?

Only the systems for which the check generated an information or error message are displayed.

Create Transport Requests in the Component Systems

Use You create customizing and workbench transport requests in the component systems, from the SAP Solution Manager system, and assign tasks to project team members in them. This is the prerequisite for you or project team members to activate BC Sets, run CATTs, import Add-On transport requests and edit customizing, in the implementation guide (IMG), in the Configuration [page 156] transaction.

Existing transport requests are a prerequisite for the Customizing Distribution [page 200]. All project team members whose customizing changes are to be distributed, must have a task in the transport requests.

Prerequisites You have created a project [page 25] in the Project Administration, defined a system landscape [page 31] for it, and saved. You are in edit mode for this project.

You have the authorization S_CTS_ADMI for all component systems in which you want to create transport requests.

Procedure ... ...

1. Go to the System Landscape tab.

2. Choose the IMG Projects subtab.

3. Click on the title of the IMG project for a component system, for example an SAP R/3.

If there is not yet a project IMG in the component system, the system tells you in a dialog box that a transport request has been created under your user name in the component system. Proceed as follows:

a. Create tasks for your project team members in this transport request.

b. Choose Continue.

You go to the Project Administration in the component system. Continue from step 4.



If there is already a project IMG in the component system, you go to the component system project administration.

4. Switch to editing mode.

5. Select the Transport Requests tab.

If the CTS functionality has not yet been activated, the system shows the pushbutton Activate CTS Functionality in the tab.

6. Choose the Activate CTS Functionality pushbutton, if it is shown.

7. Choose the Assigned CTS Requests pushbutton.

8. Create a customizing and workbench request, if there are no appropriate existing ones.

9. Create tasks in the requests for all required team members.

10. Save your entries and go back.

11. Repeat the procedure for all other systems in the IMG Projects tab.

Result The transport request created is automatically offered to all project team members with tasks in the CTS requests, when they activate BC Sets, run CATTs, import Add-On transport requests, and change customizing in the component systems.

You can use the transport requests created for Customizing Distribution.

Templates Tab

Use You manage your templates in this tab. You release finished templates, and transport them. You create new versions of templates, and archive old versions.

Integration By default, templates which you are editing are invisible system-wide. To make a template visible system-wide, change its visibility to Public. You can put a public template in the scope of any project, system-wide.

Prerequisites You are in vour template project in the Project Administration.

Features

Create and change templates You create new templates and change existing ones with pushbuttons.

Supporting global rollout If you activate the global rollout functionality, you can lock your templates completely or partially against changes in the subsidiaries, in the Business Blueprint.

For further information, see Global rollout with a Template [page 118] in the Define Template in the Company Headquarters section.

Publish a template You publish a completed template system-wide with the Change Visibility pushbutton.



If you change the visibility of a template from Private to Public, the system updates the system landscape data of the template. The template is visible system-wide in the Scope tab in the Project Administration. The visibility status is displayed by an icon in the Templates tab.

Transport You transport the template with the Deliver pushbutton using the template collector.

The template collector leads you through the template transport steps. Choose an existing transport request of type Transport Copies in the template collector, or create a new one. Release this transport request in the Transport Organizer.

Create a new version You create a new version of a public template with the Increase Version Counter pushbutton, to preserve the status of the old template and proceed with the new version.

Archiving When you create a new version of a template, you can archive the old version, to be able to compare different versions later.

Display job log You can call the logs of the release background jobs (template_ship) and archiving (template_archive) with the Call Job Log pushbutton. ...

Result You have released your template for reuse. You can now reuse the template in the same Solution Manager system, transport it in your system landscape, or deliver it to your subsidiaries, to harmonize processes, customizing and other system settings company-wide.

See also:

Global Rollout with a Template [page 118]

Milestones Tab

Use You monitor the project progress according to the milestones defined in the Roadmap and in the project, in the Milestones tab.

Integration If you have selected a Roadmap for your project in the Roadmap tab, the system lists the milestones in the selected Roadmap in the Milestones tab. You can add to the milestones in the Roadmap, but not change them.

Features • You can define milestones yourself.

• You can enter the following data for self-defined and Roadmap milestones:

� Planned start

� Planned end

� Actual start

� Actual end



Organizational Units Tab

Use Enter data on this tab about organizational units which you use in your project.

Integration This tab contains organizational unit data. You cannot analyze this data in the Project Analysis.

Features You can enter organizational unit data, including function, country and time zone.

Project Standards Tab

Use Standard values for status, keywords and documentation types for your project are all set in the same way in the project administration transaction. If no values have yet been assigned to a project, the project administrator can use the project template, which contains project-independent status values, keywords and documentation types.

The values in the project template are available to all projects of a project type. The project administrator decides which values should be used and assigns values to the project from the project template.

A project template, which already contains status, keyword and documentation type values, is assigned to each project type. You can adapt the project template to suit your project requirements.

Integration The values specified in the Project Standards tab are the default values in the following tabs, in the Project Administration, Roadmap, Business Blueprint and Configuration:

• Project Administration:

� General Data (status values)

• Business Blueprint, Configuration, Roadmap

� Proj. Documentation (documentation types, keywords and status values)

• Business Blueprint and Configuration

� Administration (status values and keywords)

� only for template projects: General Documentation (documentation type, keywords and status values)

• Configuration

� Development (status values)

� Configuration (status values)

• Roadmap



� Keywords (status values)

Prerequisites The project member responsible for creating and changing status values, keywords and documentation types must have the corresponding project role and the S_PROJECTS authorization.

You are in the Project Administration transaction in change mode.

Features There are three subtabs on the Project Standards tab:

• Status

• Keywords

• Documentation types

Status Values tab Status values provide you with information on the status of your project. Status values consist of a ten-character status ID and a description of the status. Status IDs should be meaningful.

The following status values are delivered:

Delivered status values

Status Description Effect

01 Open None

02 In progress None

03 Finished No more changes can be made in the Administration tab

04 Not relevant None

All new values appear in the Unused Status Values list and can be assigned to the project. You can search for status values in the Project Analysis [page 172] transaction.

Keywords tab You can define keywords for your project, which you can search for later in the Project Analysis [page 172] transaction. Keywords should be concise.

The keywords are the default values for the classification of documents in the General Documentation and Project Documentation tabs (General Documentation or Project Documentation tabs → Attributes pushbutton → Attributes tab → Classification).

Documentation Types tab You can document the implementation and creation of templates in all types of projects, with various documentation types. You can use the various documentation types delivered by SAP as templates to structure your project documentation. You can also create your own documentation types for:

• Minutes or decisions

• Business Blueprints

• Problem or error messages

Each documentation type has a unique ID. There are two types of project documentation:

• Project-specific documentation

This documentation type is only valid in the project to which it is assigned.



• Cross-project documentation

You can identify this documentation type by the Global Doc. indicator. The indicator is available for all projects and appears automatically in the Project Documentation Types list on the Documentation Types tab.

You can create project documentation templates for each documentation type. Proceed as described in Editing Document Templates [page 41].

You can analyze documentation types for the Business Blueprint in the Project Analysis [page 172] transaction.

Assigning and Creating Project Standards

Prerequisites You have the authorization S_PROJECTS to create or change status values, keywords and documentation types. You are in the project administration transaction in change mode and have selected the Project Standards tab.

Procedure

Assigning existing project standards to your project Scenario A:

The Unused Status Values/Documentation Types or Keywords list already contains default values. ... ...

1. Select the entries in the Unused Status Values/Documentation Types and Keyword Catalog tables that you want to assign to your project.

2. Assign the selected entries to the Project Status Values/Keywords/Documentation Types list with the Assign pushbutton.

To prevent listed entries being available in the project, you can put them back in the list of unused values, with the Delete icon.

3. Specify whether the keywords are available in the project structure, the Roadmap or for documents, by setting or deleting the flags in the Project Structure, Roadmap and Documents columns at the left-hand side. The flag is set by default.

4. Save your assignments.

Creating project standards Scenario B:

The Unused Status Values/Documentation Types or Keywords list does not yet contain default values. ...

1. Choose Project Template.

The dialog box contains standard lists of status values, keywords and documentation types that have been defined and are valid for the whole project administration transaction.

2. If there are already entries in the Project Administration Status Values/Keywords/Documentation Types list, select entries and copy them into the Project Status Values/Keywords/ Documentation Types list, with Page Left.

If there are no entries in the project template yet:

a. Make new entries in the right-hand list.



If you define new documentation types, you can give them additional attributes, for example, multiple use, or file extension.

See Editing Document Templates [page 41] for further information.

b. Copy the entries into the list at the left-hand side.

3. Save your selection.

You can now assign the standard values to your project as described in scenario A above.

Edit Document Templates

Use It is possible to create a template for project documentation on the Documentation Types tab. The template allows you to define the appearance and format of your documentation.

You can create and edit document templates for all project types.

Prerequisites You are in the initial screen of the Project Administration.

Procedure ...

1. You can go to the project template change mode in two ways:

� If you want create cross-project document templates, choose Goto → Project Template → <Project Type> in the initial screen of the Project Administration.

� To create both cross-project project-specific document templates:

i. Select the project and choose Change Project.

ii. Choose the Project Standards tab → Documentation Types tab.

iii. Choose Project Template.

You go to the project template change mode.

2. Specify a documentation type name and ID in the field in the right-hand list which is ready for input, in the Documentation Types tab.

3. You can assign other attributes to the documentation type:

� Global Doc.:

Set this flag if you want to reuse a documentation type in other projects.

� Several Documents Allowed:

Set this flag to enable multiple assignment of a documentation type to elements in your project structure.

This allows you to add, for example, several documents of the type Microsoft Word documentation, to one element.

� File Extension:

If you want to use an editor other than the text editor to create or change the document template, enter the corresponding file extension here, for example, PPT for Microsoft PowerPoint. The text editor opens by default if you do not define a file extension.



� Blueprint-Relevant:

Documents of a documentation type for which you set the Blueprint-Relevant flag, are put in the Blueprint.

For example, if you do not want to put logs in the Blueprint by default, reset the Blueprint-Relevant flag for this documentation type.

4. Select the documentation type of the template you want to change.

5. Choose an edit function, e.g. Create with Editor or Import, if you want to to upload a locally-created template from a directory, with the Document Template pushbutton.

6. Edit the document template.

7. Set the status of the new or changed document template to Released, with the pushbutton.

You can only use released document templates in your project. Only released document templates are displayed in the selection help in the Solution Manager, e.g. in the Business Blueprint.

If there are several versions of a document template, the system displays the most recently released version in the selection help.

You can display a history of the released versions, and details of the document template with the Detail View pushbutton .


Result You have created document templates for the various documentation types in your project. Choose the documentation types which you want to use in your project (see Project Standards tab [page 38]).

You use these document templates to create new documents during the Business Blueprint and Realization.

Transport Requests

Use The SAP Solution Manager contains transport functionality for template projects:

Templates transported for template projects contain the following elements:

• Project structure (positioned structure items)

• Assignments of business content made in the Business Blueprint and Realization, for example, BC Sets, transactions, or test cases.

Objects such as BC Sets or CATTs, which you have created in the component systems from the Solution Manager, are not transported with the template. To transport these objects from the component systems, for example to the subsidiaries of a company, proceed as described under Global Rollout with a Template [page 118].




Procedure You can supervise change requests concerning your project in the project administration transaction. You can access the following functions for the current client on the Transport Request tab:

• Activate Change and Transport System (CTS) functionality

Activating the CTS functionality allows you to create change requests. After activation of the CTS functionality, the button text changes to Display CTS Project Data. As soon as the CTS project is completed, the button text changes to Reactivate CTS Functionality.

• Assigned CTS Requests

Select this button to go to the an overview of the request in the Transport Organizer. Here you can create orders for a project.

• CTS Project Piece List

The project piece list remains unchanged. Once the project is complete, you can export the entire piece list.

• CTS Project Status Switch

Choose this button to set the project status switch.

• Complete CTS Project…

Select this button to close your project. You can reactivate it later.

Packages for objects

The project structure and its assignments (business content) are assigned to the package you enter here. Any later changes made to the project structure, for example, to the project scope, or the Business Blueprint, are automatically assigned to this package. You are only required to enter the corresponding transport request.

If you don't enter a package on the Transport Request tab, you will be asked to enter a package every time you save.

Note for project assignment

The automatic assignment of transport requests to a project is not supported. You can, however, carry out assignments for documentation purposes. Assigning your project to a transport request ensures that all changes made in the Business Blueprint or during configuration are recorded in the transport request. Before you can assign your project, you have to activate the CTS functionality. See the Activate CTS Functionality section above for information on how to activate the CTS functionality.

To assign your project: ...

1. Call up the Transport Organizer.

2. Call up the request to which the items in your project have been assigned.

3. Select the request.

4. Select Request/Task → Display.

5. Go to the Properties tab.

6. Switch to change mode.

7. Enter the name of your project in the Project field. The description of the project appears automatically when you save.

8. Save your entries. You have now established the project assignment.



For more detailed information on the Change and Transport System (CTS) and Customizing projects, see Using Projects to Control Transports [external link].

Changing URLs in the Solution Manager

Use This program changes character strings in web links (URLs) which you have inserted in the Solution Manager Gen. Documentation, Project Documentation or Configuration tabs. You use the Change URLs in the Solution Manager program, for example to change the directory name or file server in all URLs at the same time, because the file server has moved.

You should change all static server and directory names in URLs into variables with the Change URLs in the Solution Manager program. You define the variables for web links (URLs) centrally in SAP Web Application Server customizing, under System Administration → Replace Variable in Web Addresses (URLs).

Features The program Change URLs in the Solution Manager (SOLAR_DOC_URL_CHANGE) replaces character strings in web links (URLs) in an SAP Solution Manager project.

Activities ...

1. Run the program SOLAR_DOC_URL_CHANGE.

2. Enter data as required.

Only specify complete URLs, because the program can only replace complete URLs.

3. Save the changes.

Transporting Projects

Use You can transport projects between systems.

All project data which was created in the Solution Manager systems is transported:

• Header data (general data, scope)

• Project-specific information such as project documentation, and project team member and status assignments

• Cross-project information, e.g. general documentation

• Project structure and its assignments

Objects from the component systems which have been assigned to the project structure, and objects which were created by the Solution Manger in the



component systems, are not automatically transported with a project. Transport these objects between the component systems in their own transport requests [page 104].

Prerequisite You are in the initial screen of the project administration transaction.

Procedure 1. Select the project in the project overview.

2. Choose the Transport Project pushbutton or Project → Transport.

3. Specify the transport scope in the following dialog box. To transport the project without project documentation, reset the With Notes flag. The project documentation is transported by default.

4. Specify a transport request or create a new one.

5. Save your entries. ...

Copy Projects

Prerequisites You are in the initial screen of the project administration transaction.

Procedure ...

1. Select the project you want to copy.

2. Choose Project → Copy.

3. Specify a name for the target project.

You can see which project names have already been assigned in your Solution Manager system, in the possible entries help.

4. You can change the project type.

5. Enter a project name.

6. To not copy project data, project documentation or test cases into the new project, reset the flags. By default, all flags are set.

7. Choose Execute.

The system copies the project.

Deleting Projects You are in the initial screen of the project administration transaction.

Procedure ...

1. Select the project you want to delete.

2. Choose Project → Delete.



3. Choose whether you also want to delete the associated project documentation, in the following dialog box.

• The associated project documentation is only deleted if the project documentation deletion flag is set. Otherwise only the project is deleted, without its documentation.

• Documents which are used in other projects cannot be deleted.

• The folder in the Solution Manager Knowledge Warehouse containing the project documentation can only be deleted when it is empty.

The system deletes the documents in the background. The background job log lists all documents which could not be deleted, and the projects in which they are used.

If the system could not delete documents:

a. Delete all links to these documents in other projects.

b. Run the background job again in the transaction SM37.

4. Confirm the system message asking whether you want to delete the project with Yes.

Assign Authorization for Documents

Use You can control the access rights to documents in the project by assigning authorizations for groups of documents, e.g. you can specify that only the project management can change documentation templates.

Prerequisites

The system saves Solution Manager project documents in Knowledge Warehouse folders. Access to Knowledge Warehouse folders is controlled by the authorization object S_IWB, which is in the roles SAP_SOL_KW_ALL and SAP_SOL_KW_DIS, and in the Solution Manager Composite Rolles [page 123].

You have role (transaction PFCG) and user maintenance authorization.

Procedure

Activate authorization check You only need to activate the authorization check if projects were created in your Solution Manager system before Support Package ST 310 SP11. The authorization check is automatically active if your Solution Manager system only contains projects which were created after importing this Support Packages, or in higher Solution Manager versions.

To activate the authorization check for documents in your Solution Manager, run the report SOLAR_FOLDER_CHECK_AND_CREATE once.

The Knowledge Warehouse authorization check is based on folder groups. The report creates a folder group with the same name for each project folder. When you activate the authorization check, the system automatically creates a folder group with the same name for each folder in all new projects.



There are the following folder groups as well as the project folder groups:

• TEMPLATES: Controls access to documentation templates

• SOLAR00: Controls access to documents which were created in the General Documentation tab

Adjust and assign roles ...

1. Copy the roles SAP_SOL_KW_ALL and SAP_SOL_KW_DIS in the Role Maintenance (transaction PFCG).

2. Assign the ID of your project in the copied role in the field Folder Group.

3. Choose the authorization for your project in the field Activity.

Do not change the default values in the field Area.

4. Remove the authorization object S_IWB from the composite roles of the Solution Manager.

5. Assign the changed individual roles to the project team members.

See also:

Authorizations [page 123]

Compare and Adjust with the Template/Source

Use This function compares the structure and the objects assigned to your Solution Manager project with its source, e.g. a template or the Business Process Repository (BPR). If the source has changed, you can copy the changes and improve the process structure and the assigned objects.

Integration You can copy structures and the objects assigned to them, e.g. documentation and IMG objects from a template or the Business Process Repository, into your project. For further information about the copy function, see Resolve Differences between Source and Target [page 116].

After you have copied elements from the source into your project, the source can change, e.g. because the template has been adjusted to a new program version, errors have been corrected in the template, or a new version of the BPR scenario has been delivered.

Compare the version of the copied elements in your project with the source which you have copied, in a background job, with the function Compare and Adjust. The system automatically uses the newest version of the source for the comparison. You can choose another version as the source of the comparison when you define your project system landscape in the Project Administration (transaction SOLAR_PROJECT_ADMIN).

You can copy the changes which this background job has identified, into your project, in the Business Blueprint (SOLAR01) and in the Configuration (SOLAR02).

Prerequisites You have copies structures into your project from one of the following sources:



• the repository for business processes and scenarios delivered by SAP (Business Process Repository (BPR))

• a template

• another project structure from the possible entries help in the Structure tab in the Business Blueprint (SOLAR01)

• an entire project, using the copy function in the Project Administration

Features • Compare structures which were copied up to and including Solution Manager Version

2.20.

• Compare and Adjust all objects in the following tabs:

� General Documentation

� Structure

� Transactions

� Configuration

� Development

� Test Cases

• Compare and Adjust changes to URLs in the Transactions tab. The system does not flag changes to other objects in the Transactions tab, e.g. changes to BC Sets and documents, and updates of CATTs/eCATTS.

• Copy new or changed elements from the source into your project

• Copy deletions in the source into your project

Activities ...

1. Choose Goto → Compare and Adjust (transaction SA_PROJECT_UPGRADE) in the initial screen of the Project Administration, to compare your project with the source.

2. The Compare and Adjust function:

� compares your project structure and its elements with their source, e.g. templates, the BPR or other projects.

� flags the structure elements of the target which have changed since you copied them into your project, with a red icon, in your project structure and the tabs in the transactions SOLAR01 and SOLAR02.

� flags the structure elements which have not changed, with a green icon, in the transactions SOLAR01 and SOLAR02.

To hide the change icons in the transactions SOLAR01 und SOLAR02, reset the Adjustment Mode flag in your user settings.

3. The system creates a log, which you can display in the transaction SM37. The log shows errors which occurred in the comparison, and the number of differences found in your project.

4. The Adjust to the Original pushbutton in the transactions SOLAR01 and SOLAR02:

� displays the differences between source and target

� selects new or changed elements in the source, and copies them into your project

� selects deletions in the source, and copies them into your project



• The Finished pushbutton changes an icon from red to green. The structure node is only also set to green if all tabs have been set to green.

• If the structure node has not yet been set to green, the left-hand side of the Compare and Adjustment dialog box screen can show differences for tabs which have already been set to green. If you perform the function Compare and Adjust at this stage, the tab gets a red icon again.

• The Compare and Adjust pushbutton is active as soon as a structure node has been copied from another structure node in the same Solution Manager system.

For comparisons with templates, you must first perform the function Compare and Adjust, and then choose the Adjust to Original pushbutton in a tab.

Resolve Differences Between Source and Target

Use This function copies changes to structures and structure elements which you have, for example, copied from a template or the Business Process Repository (BPR) into your Solution Manager project, into your Solution Manager project.

Prerequisites • You have set the Adjust Mode flag in your user settings, so that the status icons are

displayed in front of the structure elements and in the tabs, after the comparison in the transactions SOLAR01 and SOLAR02.

• You have selected the Adjust to Original pushbutton in a tab in the transaction SOLAR01 or SOLAR02.

• You have performed the function Compare and Adjust (SA_PROJECT_UPGRADE) to compare changes in templates with your project.

Features • List of entries in the current tab in your Solution Manager project

• List of corresponding entries of the new version of the source node, with status

• Copy all or selected changes and deletions in the source, into your project

To replace an entire substructure in your project, for example a complete scenario with the substructure which has changed in the source, for example a template:

• Delete the substructure in your project.

• For a comparison with a template, perform the function Compare and Adjust first. Choose the Compare with Original pushbutton in the Structure tab at the level above the deleted structure.

The system shows the deletion in the right-hand side of the Compare and Adjust dialog box.

• Copy the new entry into your project.



• The system displays the additional pushbutton Finished in the Compare and Adjust dialog box, for all structure elements and tabs whose source has changed. You can set the red icons, which show changes, to green, with the Finished pushbutton, whether or not you have copied the changes into your project.

Before you can set the red icon in front of a structure element in your project to green, you must have set the red icon to green for this structure element in all tabs in the transactions SOLAR01 and SOLAR02. You can hide user settings tabs.

Example You want to compare elements in a template with your project. Only copy one change at a time to be able to monitor the changes in your project: ...

1. Copy a new BC Set from the template in the Configuration tab, into your project, in the Compare and Adjust dialog box. Activate the BC Set in your project because it contains important changes.

2. Copy a new IMG activity from the template into your project. Check it in the IMG and delete it from the Configuration tab because it is not relevant for your process. Choose the Finished pushbutton in the Compare and Adjust dialog box in the Configuration tab, to indicate that no further comparison is required.

3. Repeat these steps until you have checked all new data.

Upgrade Component Systems

Use When you have technically upgraded the component systems, you upgrade your business scenarios with the Solution Manager.

Prerequisites The upgrade target release is at least Web AS Release 6.20 SP41.

You have technically upgraded the component systems.

Procedure ...

1. Create an Upgrade Project in the Project Administration [page 51].

2. Create a project structure in the Business Blueprint [external link].

3. Determine the upgrade-relevant IMG activities in your project structure:

a:

If no IMG activities are assigned to the project structure, continue from 4.

b:

If IMG activities are already assigned to the project structure, you can:

� To compare the IMG activities in the project with those in the view, and flag matching IMG activities in the project structure as upgrade-relevant (Upgrade flag), distribute the Upgrade flag:

i. Select an IMG project for your project, in the IMG Projects tab in der Project Administration.

ii. Choose Distribute Upgrade Flag.



The system flags the upgrade-relevant IMG activities in the Configuration, in the Upgrade Flag column, in the Configuration tab.

� To determine the upgrade-relevant IMG activities in the project view, which are already in your upgrade project, compare the project with its project view:

...

i. Choose the Assignment of IMG Objects in Project Views analysis, in the Project Analysis (SOLAR_EVAL).

ii. Specify the project and view which you want to compare.

iii. Choose Execute.

The system displays the result in the project structure. You cannot copy the result into the Configuration automatically.

iv. Aassign the displayed IMG activities to the project structure, in the transaction Configuration.

4. Determine the upgrade-relevant IMG activities in your project view, which are not in your upgrade project. These IMG activities may be relevant for your upgrade project:

a. Compare with Views in the Project Analysis.

b. Assign the missing IMG activities to the project structure, in the Configuration transaction.

You can define upgrade-relevance keywords in the Project Administration, assign them in the configuration structure elements, and filter by them in the project structure, e.g. keyword "Upgrade Phase 1".

5. Configure [page 157] upgrade-relevant IMG activities.

6. Test [page 247] your changes.

7. Delete the old logical component from your project, in the Systems subtab of the System Landscape tab, in the Project Administration.

See also:

To systematically upgrade in the Upgrade Roadmap: Accelerator Upgrade Projects with the SAP Solution Manager - Guidelines

Create Upgrade Project

Procedure ...

1. Create a project of type Upgrade Project in the Solution Manager Project Administration, or copy an existing project, and change the project type in Upgrade Project.

The system assigns the current Upgrade Roadmap to the project, automatically.

2. Create the following logical components in the Solution Manager System Landscape (SMSY):

� If there are no logical components:

� A logical component for the old component which is to be upgraded

� A logical component for the target component



� If there are logical components, e.g. from earlier projects: Create a logical component for the target component.

3. Insert the relevant systems in the system role development system, into the logical components.

4. Assign logical components to the upgrade project, in the Systems subtab of the System Landscape tab.

5. Create IMG projects in the component systems, in the IMG Projects tab.

6. Create an Upgrade View for these IMG Projects [page 52].

7. If there were already logical components in your upgrade project in step 2, e.g. from earlier projects: Replace the old logical component with the new one (with the target release), with Replace Log. Component, in the Systems subtab in the System Landscape tab, in the Project Administration.

Create Upgrade Project View Create views of the IMG projects in the upgraded component systems, in an upgrade project, to specify the scope of the customizing activities required in the component systems. ...

1. Select the IMG project in the IMG Projects tab.

2. Choose Create Views.

You go to the component system.

3. Specify a view name.

4. Set the Release Customizing flag.

5. Specify under Release Customizing, how detailed the view is to be.

6. Choose the From and To releases of the components.

See View: Create Release Customizing [external link] for further information.

7. Choose Save in View Data.

8. Generate the view.

9. Save your changes and choose Back.

You go back to the Solution Manager Project Administration.

The traffic light in the View column in the IMG Projects tab in the Project Administration, turns green.

Transferring Project Data to SAP

Use You pass project data from Solution Manager ramp-up projects to SAP for analysis. The data is saved in a project database at SAP. This data allows SAP to support you optimally in the ramp-up phase.

Prerequisites SAP has created a project corresponding to your ramp-up project, in the SAP project database CPI, and released your project. When the project has been created, you have received the name, and a unique authentification key for, the CPI project.



Activities ...

1. Set-up the project data transfer.

2. Transfer the data to SAP [page 54].

Set-up Project Data Transfer

Procedure

Install SAP Cryptolib You need the SAP Cryptolib to encode the data transferred to SAP. ...

1. Install SAP Cryptolib:

a. Download the SAP Cryptolib for your operating system from the Service Marketplace (www.service.sap.com/swcenter → Download → SAP Cryptographic Software).

b. Install the SAP Cryptolib [external link] with the Trust-Manager (transaction STRUST). For further information, see Trust Manager [external link] (transaction STRUST → Help → Application Help → Trust Manager.

For further information about installing the SAP Cryptolib choose Help → Application Help → Trust Manager → Example → Configure SAP Web AS for the SSL Support in the transaction STRUST.

Changes in the Trust Manager only take effect when the application server or the IC Monitor are restarted (step 2).

2. To restart the ICM Monitor, choose Administration → ICM → Soft End, in the ICM Monitor transaction (SMICM).

You can check whether the ICM Monitor has been restarted, with the Refresh pushbutton.

The system shows the inactive PSE folder, SSL server and SSL client (default) in the left-hand screen area in the Trust Manager. Inactive folders are flagged with a red cross.

3. Set-up the PSE for the SSL client (default):

a. Select the SSL client folder (default) and choose Create in the context menu.

b. Confirm the following dialog box.

The new PSE is displayed below the PSE folder.

4. Import the client certificate into the SSL Client (Default) folder:

a. Logon to the SAP Service Marketplace with the Internet Explorer.

b. Double-click on the lock icon in the browser status bar at the bottom right.

The system displays the certificate in a dialog box.

c. Download the SSL client certificate from the Details tab.

d. Import this certificate with Certificate → Import in the Trust Manager (transaction STRUST).

5. Set-up the PSE for the SSL server:



a. Select the SSL Server folder, and choose Create in the context menu.

b. Confirm the following dialog box.

The new PSE is displayed below the PSE folder.

6. To restart the ICM Monitor, choose Administration → ICM → Soft End, in the ICM Monitor transaction (SMICM).

You can check whether the ICM Monitor has been restarted, with the Refresh pushbutton.

7. Specify the proxy settings:

a. Run the program RSPROJECT_SET_CPI_URL.

b. Enter the required data and choose Execute.

You only need to specify the port if you have no proxy.

Specify the URL service.sap.com/; do not specify a log (e.g. http).

Check SAP Cryptolib Installation ...

1. Run the program SSF02

2. Set the Get Version flag.

3. Choose Execute.

The system shows the current version of SAP Cryptolib.

Error-handling If you specified the CPI project ID and/or the authentification ID incorrectly, you can correct it with the program RSPROJECT_CHANGE_CPIS_AUTH. The system copies the specified values in the program Transfer Data to SAP (RSPROJECT_CPI) and sets these fields to not ready for input.

Result You have satisfied the prerequisites for transferring project data to SAP.

See also:

• SAP Trust Center Services: www.service.sap.com/tcs

• SAP note 510007 for setting-up SSL on the Web Application Server

Pass Project Data to SAP

Use You pass project data from Solution Manager ramp-up projects to SAP for analysis. The data is saved in a project database at SAP. This data allows SAP to support you optimally in the ramp-up phase.

Prerequisites SAP has created a project corresponding to your ramp-up project, in the SAP project database CPI, and released your project. When the project has been created, you have received the name, and a unique authentification key for, the CPI project.

Procedure ...

1. Run the program RSPROJECT_CPI.



2. Enter the data required under Logon.

When you have sent the data, these fields are no longer ready for input.

3. Enter the data required under Project.

4. Specify the contact persons under Contacts. To ensure that the specified names can be checked at SAP, specify the e-mail address, and any OSS user.

If the SAP implementation is performed by a partner or at a partner site, specify as SAP project leader an SAP contact person who is responsible for the corresponding CPI project.

5. If the SAP implementation is performed by a partner, enter the required data under Partner. The specified partner must be registered at SAP for the data to be passed.

6. Enter the planned and current dates of your project phases under Work Plan.

For the Business Blueprint and Realization phases, the system copies any data from the root nodes of the structures. You can enter the data in these phases in the Administration tab.

7. If you see a general project risk, you can transmit it with a comment to SAP under Risk Status.

8. Specify the application component of the solution which you are implementing.

9. The system lists all scenarios which your project contains, under Scenarios. When you have created some scenarios, you can assign an SAP standard scenario to them, to categorize it. Only then can you send a status and a comment for this scenario to SAP.

The system sends the structure node texts for processes and process steps, as well as the scenarios, to SAP. The system sends no data which is assigned to the structure nodes. You can display the structure nodes which were sent, with the Project Scope pushbutton.

10. You can send user documents to SAP, as well as the system data, under Documentation. Select the field Send, to send the document and other data to SAP.

The system notes the paths to the specified documents, so that you can send a newer version of the document by choosing Send again.

11. Choose List → Send or the Send pushbutton, to send the project data to SAP. Enter a valid SAP Service Marketplace user and the password, in the following dialog box. The data is saved in the SAP project database, with this user as the last changer.

Migration of Data at Release Update from 2.20 to 3.10

Use A conventional upgrade is not possible from Release 2.20 to Release 3.10 because the Solution Manager system architecture changed between these releases. Perform a new installation and migrate your existing data from 2.20 to 3.10 with the transaction Solution Manager Migration (SOLAR_MIGRATION). This transaction automatically exports your projects , documentation, system landscape data and Customizing Synchronization data from the lower release, and imports it into the higher release.

Prerequisites • You have setup the target system as the target for transports in the Transport

Management System. You can specify the same system as source and target system, e.g. the system ABC as target system for the same system ABC.



• You have the role SAP_SOLAR_MIGRATION in the releases 2.20 and 3.10.

Features • Automatic export of the following data from the release Solution Manager 2.20:

� Projects:

� Header and administration data

� Project structure with assignments

� Assignments of roadmaps to projects

� Project documentation and general documentation: Settings, documents and folders in the Knowledge Warehouse which is integrated in the Solution Manager

� Test plans with test cases and test packages

The assignment of testers to test packages is not migrated.

� Basic settings for logical components for the Solution Manager Implementation

� System landscape data

� Customizing Synchronization data

� Synchronization groups for Customizing Synchronization

• Change the original system of object directory entries with a transport. You need this function if you install Release 3.10 in a different logical system from Release 2.20.

• Import the data into the release Solution Manager 3.10.

• Migration log

Activities ...

1. Migrate the Data from Release 2.20 to 3.10 [page 56].

2. Set-up the migrated Solution Manager system landscape and the Customizing Distribution in Release 3.10 [page 57].

3. Set-up the migrated projects in Release 3.10 [page 59]. ...

See also:

• SAP Solution Manager Migration Guide

• SAP Solution Manager Installation Guide

Migrate Data from Release 2.20 to 3.10

Prerequisites You have released all open transport requests in the source release 2.20.

Procedure If you have several Solution Manager systems in your system landscape, e.g. as development system, quality assurance system and production system, migrate each Solution Manager system separately: ...



1. Export the data from source release 2.20:

a. Run the transaction Solution Manager Migration (SOLAR_MIGRATION) in release 2.20 and make the required entries.

Only the projects which you select explicitly are migrated.

b. The system captures the selected data and saves it as follows:

� System landscape data in XML format in the specified directory

� Change documents as text files

� Test notes in XML format

� Other data in transport requests of type „Transport Copies“ in the transport directory of the Transport Management System in the export system

� If the target and source releases are installed in different systems, and you want to change the original system of objects from source release 2.20 to target release 3.10, a relocation transport, which changes the object directory entries of these objects, is created. The object directory entries of the objects whose original system is not the source Release 2.20, are not changed.

c. The system creates a control file with information about the exported data, in the specified directory, for the import.

d. The system creates a migration log. You can call this migration log in the initial screen of the Solution Manager Migration transaction.

2. Install the new Release 3.10. For further information, see the SAP Solution Manager Installation Guide.

3. Import the data exported from Release 2.20 into Release 3.10:

a. Run the transaction Solution Manager Migration in Release 3.10.

b. Specify the directory of the exported data.

c. The system checks whether the control file with the information about the exported data exists.

d. The system imports the files and the transport requests with the exported data, into Release 3.10.

e. The system makes a data import entry in the migration log.

If the migration fails, e.g. because you do not have the required authorization, run the transaction Solution Manager Migration again to migrate the data correctly. Changes which you have made in the meantime to imported projects in the target release, are lost when you import again.

Result • Set-up the system landscape and Customizing Distribution again [page 57].

• Set-up the migrated projects in the new system [page 59].

Set-Up System Landscape and Distribution after



Migration

Use To be able to use the Solution Manager system landscape and the Customizing Distribution after the import of migration data into Release 3.10:

• System landscape: Adjust the Trusted System connections between the new Solution Manager system and the satellite systems

• Customizing Distribution: Delete the no longer required distributions, and download the list of synchronization objects.

Prerequisites • You have the role SAP_SOLAR_MIGRATION.

• You have authorization for transaction SCDT_SETUP, to set-up the Customizing Distribution. The Application Consultant role contains these authorizations.

• You have migrated the data from Release 2.20 into Release 3.10 with the transaction Solution Manager Migration (SOLAR_MIGRATION).

• You have selected the data export option Customizing Distribution in the transaction Solution Manager Migration, to migrate all existing distributions from the old Solution Manager system into the new one, (SOLAR_MIGRATION).

• The system landscape data has been imported into the new system.

Procedure

Generate Trusted System RFC connections from the new SAP Solution Manager system to the satellite systems ...

1. Set-up the following authorizations:

a. Create a user SOLMAN<SidCli>, where <Sid> is the system ID and <Cli> is the client in the old Solution Manager system, in all clients of the new Solution Manager systems which you want to use.

Assign the authorization S_RFCACL for all satellite systems, and S_RFC, to the user SOLMAN<SidCli>.

b. Assign the authorizations S_RFCACL and S_RFC to the benutzer SOLMAN<SidCli> in the target clients of the satellite systems for all clients which you use in the new Solution Manger system.

c. Change the user SOLMAN<SidCli> in the satellite systems into a dialog user.

d. Ensure that all users in the target clients of all satellite systems have the authorizations for all clients which you use in the new Solution Manager system (authorization S_RFCACL).

2. Generate the Trusted System connections:

a. Run the program SMSY_REGENERATE_ALL_DESTS in each client of your new Solution Manager system.

This program generates all Trusted System connections.

b. If you are prompted to logon to the new Solution Manager system, logon with the user SOLMAN<SidCli>.

Set-up Customizing Distribution in the new system ...

1. Delete the distributions which you no longer need in the new system, in the Customizing Distribution set-up (transaction SCDT_SETUP).



2. Download the list of synchronization objects for all software products which you use in the Customizing Distribution, with Goto → Load Object List, in the transaction SCDT_SETUP.

3. To activate the distributions which you need in the new system, double-click on them and save them from the detail screen. You only need to activate one distribution per project.

4. Schedule the background jobs for Timed Distribution and Automatic Redistribution after Errors.

Set-Up Projects after Migration

Use To be able to use your old Release 2.20 projects after migration, you must perform some manual post-processing of the imported projects in Release 3.10.

Prerequisites • The system landscape data has been imported.

• You have defined the transport landscape for the packages containing your templates.

Procedure ...

1. To copy changes to the product definitions which were delivered with Release 3.10, into the logical components, run the program SOLAR_SCDTLOGCMP_MIGRATION.

2. If you use template projects:

i. To activate the CTS functionality for the imported template projects, call each template project in the project administration, and choose the Activate CTS Functionality pushbutton in the Transport Requests tab.

ii. To adjust templates from template projects to the changes in Release 3.10, run the program RSPROJECT_TEMPL_MIGRATION_310 after each new import of Solution Manager projects.

iii. If you had imported templates which were created in an other system, into your old 2.20 system, import them into your new 3.10 system as well.

3. Assign test packages to testers.

4. To assign its team member to the project again, run the program RS_GET_BACK_MIGRATED_RESOURCES for each imported project.

Result You have performed all post-processing required after the migration. You can now use the projects and templates which you had imported from your 2.20 system, in your 3.10 system.

Solution Manager Project Overview

Use The Solution Manager project overview gives you an overview of your implementation and template projects, and information about the projects, e.g. their status.



Integration You can go from the Solution Manager project overview to all transactions which you need to perform an implementation or template project, via links.

Features • Display the implementation and template projects

• Display the following project data:

� Plan data

� Actual data

• Display the project-specific Roadmap with milestones, status, plan data and actual data, if a Roadmap has been assigned to your project in the Scope tab, in the Project Administration [page 27]

• Display the scenarios of a project

• Display the component views of scenarios and processes

Solution Manager System Landscape

UseYou create and manage the system landscape centrally in the Solution Manager, to use it in your implementation and template projects, to monitor change requests (Change Management), in the Customizing Synchronization (Customizing Scout, Customizing Distribution) and in operational processing (Solution Monitoring, Services, Support Desk).

IntegrationThe SAP Solution Manager is based on the system landscape. A correctly maintained system landscape is a prerequisite for the Solution Manager functions:

• Generate Project IMGs in the Project Administration

• Go to the component systems in the Configuration phase

• Customizing Synchronization (Customizing Scout, Customizing Distribution, Synchronization Group Editor)

• System roles in Change Management

• Maintain the solution landscapes for the operational processing of your solutions

Features• Create landscape components (servers, databases, systems, system components)

• Define non-SAP products for use in the system landscape maintenance

• ABAP main instance reads and saves data automatically

• Overview of system groups

• Generate RFC destinations for the component systems; RFC connection errors are logged

• Manual data capture, e.g. for servers, non-ABAP systems and planned systems

• Graphical display

� Landscape components (servers, databases, system)



� Assignment of attributes to landscape components

• Analyzing the System Landscape by Landscape Components

Set-Up Automatic System Landscape Data Capture

Use 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 Solution Manager System Landscape.

The SAP Solution Manager can get server, database and system data automatically with this data.

Prerequisites • For using the Landscape Information System (LIS):

� You have assigned the Solution Manager to a transport domain in the Transport Management System [external link] (STMS)

� Or you have specified the Solution Manager system as the new domain controller in the transport management system.

• For using the System Landscape Directory (SLD):

You have setup the System Landscape Directory (SLD).

Procedure ... ...

1. Choose the transaction Setup System Landscape (SMSY_SETUP).

2. Choose the source for the automatic data transfer.

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.

3. To access the System Landscape Directory (SLD):

a. Choose Edit → Expert Settings.

b. Specify the server from which SLD data is to be read, as SLD Host.

c. You can change the other options.

You can also change these options when setting-up the System Landscape Directory.

d. You can write data back into SLD by entering a value for Write Data Back into SLD.

e. Choose Continue.

For further information, see System Landscape Directory in the SAP Library.

4. Choose Schedule Automatic Data Transfer.



5. Enter the start time in the following screen. You can choose whether you want the job to run once, or periodically.

You should schedule the job daily.

For further information, see Automatic Data Capture [page 62].


The system copies your data into the initial screen. The system logs each data transfer. You can call the logs in the Set-Up System Landscape (SMSY_SETUP) and Solution Manager System Landscape (SMSY) transactions with Logs → Update Logs.

• To delete data transfer logs:

• Choose Logs → Update Logs → Delete in the Set-Up System Landscape (SMSY_SETUP) or Solution Manager System Landscape (SMSY) transactions.

• Choose options. A log expires after 14 days (Expiry Date group box).

• Choose Execute.

Result You have set-up data transfer to automatically get system data for further use in the Solution Manager system landscape. After data collection, the automatically identifiable systems and servers in the Solution Manager System Landscape are visible.

Automatic Data Capture

Editing automatically captured data You cannot edit all data manually in servers, databases and systems whose data sources were determined automatically, not manually. You can neither delete automatically captured landscape elements nor change the associated automatically captured data. You can add to this data.

You can set the data source to manual maintenance [page 63] to be able to edit all data in this landscape element manually.

Updating automatically captured data You can choose whether the system automatically overwrites manually entered data, or prompts you when more recent data exists. In the latter case, the last person to change the data which is to be updated receives an express mail. The old data is flagged with an exclamation mark in the Solution Manager system landscape. You can compare the data and copy the current values.



Manual Data Source Maintenance

Use You cannot edit all data manually in servers, databases and systems which were determined automatically. You can set the data source to manual maintenance, to be able to edit all data in this landscape element manually.

You should only set the data source to manual maintenance if the automatically captured description does not match the actual definiton of the landscape component. This can, for example, be the case if a system temporarily has an additional server, which is recognized by the automatic data capture, but should not be in the system description because it is only temporary.

Prerequisite You are in the Solution Manager System Landscape (SMSY).

Procedure ...

1. Choose Landscape Components → Other Object, or

2. Choose the landscape component from the possible entries help, or enter the name of the landscape component.

3. Choose the Set Data Source to Manual Input pushbutton.


System Landscape Management

Purpose This process fulfills the prerequisites for using the SAP Solution Manager.

Prerequisites • You need authorization for the authorization object S_SMSYEDIT to create the Solution

Manager system landscape.

• To create system components, you need authorization for the authorization object S_SMSYSYST.

• You have the Authorizations [page 71] required to be able to define RFC connections in the Solution Manager and satellite systems.

Process Flow ...

1. You setup automatic data capture for the system landscape [page 61], to read server, database and system data automatically from the System Landscape Directory or the Landscape Information System.

2. You define your system landscape in the Solution Manager System Landscape (transaction SMSY):

a. Create systems, or adjust the data for automatically determined systems. The following system details are required, to be able to generate RFC connections to this system:



� Message server

� Installation number

b. You generate RFC connections to your systems or assign existing RFC connections to them.

c. Put related systems in logical components, e.g. the evalution, development and test systems for a product, for an implementation project.

Result You have setup the system landscape for the SAP Solution Manager.

You then create an implementation project, use the Customizing Synchronization, manage change requests (Change Management), or create solutions for operational processing in the transaction SOLUTION_MANAGER.

Assign the logical components to projects or solutions.

Create and Assign Landscape Component Attributes

Use 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.

Prerequisites You are in the Solution Manager System Landscape transaction (SMSY).

Procedure

Define Landscape Component Attributes ...

1. Choose Utilities → Attribute Definitions.


3. Choose New Entries.

4. Assign an attribute key in the customer namespace, i.e. beginning with Y or Z.

5. Enter the required data.

6. Specify the landscape component for which the attribute is to apply.

7. Set-up possible entries help for the landscape component attribute values [page 65].


The system displays the newly-defined attributes of the landscape components, in the Other Attributes tab.

Assign values to the attributes of a landscape component ...

1. Choose a landscape component.

2. Choose a value for the attribute from the possible entries help for the Attribute Value column in the Other Attributes tab.




Result You can display the assignment of attributes to landscape components, graphically, in the overview tree, under Overviews [page 84].

Set-up Possible Entries Help for Landscape Component Attributes

Use You can use existing possible entries help in your system for user-defined attributes. You can, for example, set-up a list of your system administrators as possible entries help for the attribute „Person Responsible“, which you have defined.

You can set-up possible entries help for an attribute by specifying an existing values table or search help when you define the attribute. You can also define all the possible entries yourself.

When a user calls the possible entries help, the system first checks whether a value table and/or search help was specified when the attribute was defined. If so, the possible entries are the entries in the value table or search help.

If no value table or search help was specified, the system fills the possible entries help with the values specified individually in the attribute definition. If no values were specified, there is no possible entries help.


You have defined at least one landscape component attribute.

Procedure ...

1. Choose Utilities → Attribute Definitions.


3. Choose an attribute.

4. To use existing value tables and search help, you can either:

a. Enter a table name in the Value Table field,

b. Enter a field name from this table in the Values Field field.

or ...

a. Specify a search help in the Search Help Name field.

b. Specify the return parameter for this search help in the Search Help Field field.

If you only specify the search help name, the system shows the first parameter of the search help in the search help.

5. To define the possible entries help values for an attribute yourself:

a. Choose Possible Entries Help in the dialog structure.

b. Choose New Entries.

c. Enter the required data.



The system also shows text which you enter in the Description column in the attribute possible entries help. This text is language-dependent.


Edit Products, Product Assignment and Product Version


Procedure You can:

• Show/Hide a Product System-Wide [page 66]

• Create a Non-SAP-Product [page 67]

• Change the Assignment of a System to a Product [page 76]

• Change the Product Version of a System [page 76]

Show/Hide products SAP products are displayed in the left-hand screen area, according to the system settings.

You should have your system administration hide products which you do not use in your system landscape, system-wide. These products are hidden from all product selection possible entries help in the entire Solution Manager. You can choose to display or hide system-wide hidden products, in the Solution Manager System Landscape user-specific filter settings.

To display or hide products:

• To show or hide products system-wide:

� ...

a. Choose Utilities → System Settings → Product Selection tab.

b. Switch to change mode.

c. Choose the products by setting the flag in the Active column.

d. Save your selection.

• You can show or hide products in your personal view with Utilities → User-Specific Filter → Products tab.

If you choose All Products, the system ignores the selection made under System Settings, and displays all existing products.



You can display details of the version of SAP products by double-clicking on the product version. They include details of the product components.

Create Non-SAP products You can only create non-SAP products yourself. ... ...

1. Select the landscape component General Product Definitions and choose Create in the context menu, or Other Object → Product → Create.

2. Enter the data required, in the following dialog box.


The system shows the new product in the left-hand screen area.

4. Specify the product key and the product versions in the Product Versions tab, to define versions of the new product.


The system automatically assigns a sequence to the product versions. You can change this sequence with the arrow keys.

The system automaticaaly assigns a main instance to the product, in the Components tab.

6. You can change the main instances of the new product in the Components tab.


8. Set the Active flag for your product, to be able to use it to define your system landscape.

To flag a product as Active:

� at least one product version is defined, as described under 4.

� at least one main instance is assigned to the product, as described under 5-6.

You can only use active products to define your system landscape. Inactive products are hidden from all product selection possible entries help in the entire Solution Manager.

The system puts these entries in the system settings, where you can show or hide products.

Change Assignment of a System to a Product/Product Version After an upgrade of manually created systems which are not updated automatically, you can assign another product or product version to a system, e.g. you change the system product assignment when you upgrade from R/3 4.6C to R/3 Enterprise 4.7.

Automatically determined systems can appear more than once as landscape components, if their components cannot automatically be assigned uniquely to



one product, e.g. the automatic data determination cannot decide uniquely whether SAP APO or SAP BW is installed in a system. In this case, the system appears under both SAP APO and SAP BW in the Solution Manager System Landscape. Flag one product as leading. (4).

...

1. Choose Other Object.

2. Specify the system.

3. Choose the Installed Product Versions pushbutton.

4. Choose the new product data from the possible entries help.

or

If the new product/product version is not in the possible entries help, set the Free Product/Product Version Selection flag, and enter the product data.

or

If an automatically-determined system is assigned to several products, set the Leading Product Version flag for one product.

5. Save your entries and choose Continue.

The system is displayed in the new position among the landscape components at the left-hand side.

6. If the system instances have already been maintained for another product, you can copy the instances for the new system:

a. Select the main instance of the product in the overview tree, and go to the Instances tab.

b. Choose Copy Instances .

c. Choose an instance.


Create Server

Use The system determines the displayed data automatically, if you have set-up automatic data capture for the system landscape [page 61]. The system cannot determine all server data automatically, so you can complete it, e.g. with the frequency.


Procedure ...

If you use routers, or you must specify the Distributed Name Service name (DNS name) to generate an RFC connection, in your network, proceed as follows:

• Create the message server for a satellite system, as server, in the Solution Manager System Landscape.

• Specify the routing information for this server.

The routing information is required to generate RFC connections.



• Create the system and specify this server as message server.

For further information, see Generate RFC Connections [page 71].

1. Select the landscape component Server, and choose Create in the context menu.


3. Specify any routing information.

4. Choose attribute values from the possible entries help in the Other Attributes tab [page 64].


Create Databases


Procedure ...

1. Select the landscape component Databases, and choose Create in the context menu.


3. Choose attribute values from the possible entries help in the Other Attributes tab [page 64].


Create Systems

Use 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 [page 61]. You can enhance this data or die switch the data source to manual maintenance [page 63].

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.


Procedure

Create Systems ...

1. Select the landscape component Systems, and choose Create in the context menu.

2. Enter the system ID as the system name, in the following dialog box. If there are other systems with the same name in your system landscape, enhance the system names, to distinguish them, e.g. system AAA_1 and system AAA_2.

3. Choose a product and a product version from the possible entries help.




The Solution Manager displays the relevant main instances below the system, in the overview tree. For a new system, the Solution Manager derives the relevant main instance from the selected product.

5. Select the system, and you can flag another ABAP-based main instance as Relevant, or set the Relevant flag for several non-ABAP main instances, in the Main Instance Selection tab.

• Only relevant main instances can be displayed in operational processing in your solution landscape.

• You can only assign system components to the relevant main instances.

• You cannot delete the Relevant flag if the system is used in a logical component, to avoid inconsistencies in the solution landscape.

6. You can assign system components to the relevant main instance, e.g. an ITS, in the Main Instances Selection tab:

i. Set the System Component Assignment flag for the relevant main instances.

ii. Choose you the system component from the possible entries help

iii. You can create new system components [page 77] with Create System Component.

7. You can specify further information about the system.

You can flag a system as Planned or Productive. You can, for example, reset the Production flag for a copy of a production system in a backup system landscape.


Specify ABAP-based main instances for SAP products

There must be one relevant ABAP main instance per system for ABAP-based SAP products. If there are more than one ABAP main instances for this product, one ABAP main instance is automatically flagged as Relevant when the system is created. You can change this automatic selection. The system copies the selected main instances into the left-hand screen area.

...

1. Select the ABAP main instance in the left-hand screen area below the system to be defined, and enter the installation number in the Header Data tab. Entry of the remaining data is optional.

2. Specify the system number and the message server in the Header Data tab, to be able to generate RFC connections for this system.

3. Create the clients for the selected main instance, in the Clients tab.

4. Enter a client number.

5. You can enter a name for the client.

6. You can choose a role from the possible entries help.

7. Specify a logical system.


9. There are two ways of getting RFC connections for clients:

� Assign existing RFC connections to the client:

i. Choose a client in the Clients tab.



ii. Choose Assign and Check RFC Destinations.

iii. Choose an existing RFC connection from the possible entries help for the RFC connection types.

iv. Set the Assign RFC Dest. For System Monitoring flag, to reuse the RFC destinations in this client for central system monitoring. You only need to assign this flag for one client per system.

v. Save your selection.

� Generate the RFC connections [page 71] again for the clients.

You cannot generate RFC connections for Planned systems.

You can also perform this step later.

10. You can specify the instances in the Instances tab. The possible entries help contains the servers which you defined previously in the landscape component Server.

11. You can display details of the installed software components, and specify/change their Support Package status, in the Software Components tab.


If there is a read RFC connection for at least one client, you can refresh the system data with the Read System Data Remote pushbutton. The SAP Solution Manager requires up-to-date system data, to be able to read, e.g. information about imported Support Packages. You can set-up automatic system data refresh when you Generate the RFC Connection [page 71].

Specify main instance of non-ABAP SAP and non-SAP products ...

1. Select the system for which you want to specify main instances, and set the Relevant flag for the relevant main instances, in the Main Instance Selection tab.

The system copies the selected main instances into the left-hand screen area, under the system.

2. Select the main instance and enter the required data at the right-hand side of the screen.


Generate/Change RFC Connections

Use RFC connections to the component systems are a prerequisite for the following Solution Manager functions:

• Generate Project IMGs in the Project Administration

• Go to the component systems in the Configuration phase

• Customizing Synchronization (Synchronization Group Editor, Customizing Scout, Customizing Distribution)

• Read system data via the Service Data Control Center

• Monitor change requests (Change Management)



You can only generate RFC connections for ABAP-based main instances.

Prerequisites • You are authorized to logon to the target system and create a user there. You are also

authorized to create RFC connections of type Trusted System connection, in the local and target systems, if required.

• The satellite systems are reachable.

• The message servers are reachable under the name and system number specified in the Header Data tab.

• If you use routers, or you must specify the Distributed Name Service name (DNS name) to generate an RFC connection, in your network, the generation of RFC connections has the following prerequisites:

� You have created the satellite system message server as a server, in the Solution Manager system landscape, and specified routing information for it.

� You have specified this server as the message server when you created its system.

• You are in the Solution Manager System Landscape transaction, and have saved your last change.

• The system for which you want to generate RFC destinations, is not flagged as Planned.

Generate RFC destinations ... ...

1. Choose the ABAP-based main instance of the system for which you want to generate RFC connections, in the left-hand frame.


3. Choose a client in the Clients tab.

4. Choose Generate RFC Destinations.

5. Choose the type(s) of the RFC connections in the following dialog box.

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.

The system shows the details of the RFC connection to be generated, at the bottom of the screen.

6. Choose the user options. If, for example, you use the central user management, you can assign existing users in the component system.

7. You can specify a server group for load sharing, in the RFC Destination Attributes group box.

8. If the specification of the message server is not sufficient to set-up an RFC connection in your network, or your network contains routers:

a. Choose Routing Information in the RFC Destination Attributes 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 Landscape Components, when you restart the Solution Manager System Landscape transaction.

b. Specify any IP address.



c. Specify the routing information for the direction Solution Manager -> Router -> Server, e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12

d. Specify the routing information for the direction Server -> Router -> Solution Manager , e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12

The Solution Manager System Landscape calls information to generate RFC connections in the following sequence:

• Routing information (e.g. /H/1.2.3.4/H/5.6.7.8/) If this is not available:

• Server IP address If this is not available:

• Server name

e. Save your entries.

9. Remote read is the default for system data, because the SAP Solution Manager requires current system data, for example, to read the data of imported Support Packages. You should not reset the flag in the Actions after Generation group box.

10. Set the Assign RFC Dest. For System Monitoring flag to use the RFC destinations which you generate in the Solution Manager System Landscape in central system monitoring (transaction RZ21) and in the Solution Manager for operating your solution landscape. You only need to set this flag for one client per system.

The system enters the RFC destination data in the overview of the monitored remote SAP systems, in central system monitoring (transaction RZ21) → Techn. Infrastructure → Display Topology.

11. Choose Generate RFC Destinations.

You go to logon screens for each of the systems involved, consecutively, depending on the connection type selected.

12. Logon to the systems.

The system generates a log with information about the checks made, and all messages sent while making the connection.

13. If generation errors occur:

a. The message long texts contain details of the errors.

b. Resolve the errors, if possible. Click on the RFC connection in the Generate RFC Destinations dialog box, or double-click on the RFC connection in the Clients tab, to go to the detail view of the RFC connection in the Edit RFC Destinations transaction. You can test the RFC connection there, and make any changes. For further information, see the Resolve RFC Generation Errors section.

c. Repeat the generation if necessary, by deleting the old RFC connection and generating again.

14. Go back.

The system shows the RFC connections generated, on the Clients tab.



Refresh RFC destinations

You cannot overwrite existing RFC connections from the Solution Manager. To regenerate existing RFC connections, delete them first manually with Cleanup RFC Destinations, and create them again.

Cleanup RFC Connections ...

1. Select a client for a main instance, in the Client tab.

2. Choose Clean-Up RFC Destinations.

3. Check whether the correct RFC connection from the Solution Manager to the satellite system is shown at the top of the screen.

4. To refresh the data display, choose Read Informationen (<system>).

5. Make changes to the RFC connection.

You should use one user for all RFC connections.

6. To delete RFC connections to the satellite system, choose the RFC connection by double-click. You go to the transaction Edit RFC Destination (SM59) in the satellite system.

Change RFC Destination Assignment You can assign existing RFC destinations to a client with the Assign and Check RFC Destinations pushbutton.

Delete RFC destinations

Delete Row only deletes the selected row in the Clients tab, it does not delete the RFC connection to a system.

To delete existing RFC connections, choose the RFC connections by double-click in the Clients tab, or selectt them and choose Clean-Up RFC Destinations.

For further information about deleting RFC connections, see Edit RFC Destinations in the SAP Library.

RFC generation error handling • The generation of the RFC connection can fail because the user specified in the

Generate RFC Destinations dialog box already exists in the target system, and cannot be created again. You can solve the problem as follows:

� If this user is not otherwise used, you can delete it in the target system, and regenerate the RFC destination.

� Change the user to be created, in the Generate RFC Destinations dialog box, and regenerate the RFC destination.

� If you know the password, or can change it, delete the RFC destination, and regenerate it with the user option Use Existing User, Specify Password.

• The Support Package status in the component systems must be sufficient. The error log long text tells you the required Support Package status.

• The generated user may not have all necessary authorization in the target system. The generation log indicates this. Assign the required authorization to the generated user in the target system, manually.



Result The system shows the RFC connections generated, on the Clients tab.

Give the users which RFC connections to the component systems want to use, the appropriate authorization in the component systems and in the Solution Manager system. Recreate the authorization profile, if necessary. For further information about the authorization objects and profiles required, see:

• the SAP Solution Manager configuration guide

• System settings for Customizing Distribution and Scout [page 197], for customizing synchronization.

Create Non-SAP Systems

Use You create systems in which non-SAP products are installed, yourself, to be able to monitor these systems in operational processing.

Procedure ...

1. Create the non-SAP product [page 67], which runs in the system which you want to create.

Flag this product as Active. Only active products can be used to define systems.

2. Create a system.

a. Choose Landscape Components → Systems in the overview tree.

b. Choose Create System from the context menu.

c. Enter the system ID as the system name, in the following dialog box.

d. Choose the product which you created in step 1, from the possible entries help, and choose a product version.


The system is displayed at the left-hand side of the screen , under Landscape Components → Systems, below its non-SAP product.

f. Set the Relevant flag in the Main Instance Selection tab for a main instance, to be able to display and use it in operational processing in your solution landscape.

The system copies the selected main instances into the left-hand screen area, under the system.

g. You can add further information about the system (see Create Systems [page 69])

h. Select the relevant main instance(s) at the left-hand side of the screen, and enter the required data at the right-hand side of the screen.

i. Save your entries.



Result You have created a system in which a non-SAP product runs. You have satisfied the prerequisite to be able to monitor this system in operational processing.

Change Assignment of a System to a Product/Product Version After an upgrade of manually created systems which are not updated automatically, you can assign another product or product version to a system, e.g. you change the system product assignment when you upgrade from R/3 4.6C to R/3 Enterprise 4.7.

Automatically determined systems can appear more than once as landscape components, if their components cannot automatically be assigned uniquely to one product, e.g. the automatic data determination cannot decide uniquely whether SAP APO or SAP BW is installed in a system. In this case, the system appears under both SAP APO and SAP BW in the Solution Manager System Landscape. Flag one product as leading. (4).

...

1. Choose Other Object.

2. Specify the system.

3. Choose the Installed Product Versions pushbutton.

4. Choose the new product data from the possible entries help.

or

If the new product/product version is not in the possible entries help, set the Free Product/Product Version Selection flag, and enter the product data.

or

If an automatically-determined system is assigned to several products, set the Leading Product Version flag for one product.

5. Save your entries and choose Continue.

The system is displayed in the new position among the landscape components at the left-hand side.

6. If the system instances have already been maintained for another product, you can copy the instances for the new system:

a. Select the main instance of the product in the overview tree, and go to the Instances tab.

b. Choose Copy Instances .

c. Choose an instance.




Define and Edit System Roles

Use You can define ten user system roles in addition to the existing system roles. The system flags SAP and user system roles with icons.

Procedure

Define/Change System Roles Choose Utilities → System Settings → System Roles tab, to change user-defined system roles or define new system roles. You can change system role types or their sequence for the SAP Change Manager, e.g. as subsequent system in a transport path.

The new/changed system roles are displayed in the Project Administration → System Landscape tab → Systems tab, and in all role selection possible entries help in the Solution Manager, except: The unchanged system roles from the client definition are displayed in the role selection possible entries help for ABAP-based main instances in the Clients tab in the Solution Manager System Landscape.

Delete system roles

If your user-defined system roles are used in your system landscape, you can change their names, but not delete them.

You can neither change nor delete SAP system roles.

Transport System Roles You can transport system roles with the Transport pushbutton.

Create System Components and Assign them to Systems

Use A system component, e.g. a TREX, can belong to various systems. In the SAP Solution Manager, you specify the data for a system component once, independently of a specific system. You then assign the system component to the systems which use it.

The system component types are currently (SAP can extend the list):

• ITS

• Java system

• TREX

Procedure

Create system component ...

1. Choose Landscape Components → System Components in the overview tree.

2. Choose Create New System Component from the context menu.

3. Enter a name.



4. Choose a Type.


6. Enter the required data in the Header Data and Instances tabs in the right-hand window.

7. In the Software Component tab, you can:

� Select installed software components from the possible entries help

� Copy software components from a main instance of a product with From Main Instance

� Specify software component patch level

8. You can enter values for the attributes which you have defined, in the Attributes tab.


Assign system component to a system ...

1. Choose Landscape Components → Systems → <Product> → <System> → Main Instance Selection tab, in the overview tree.

2. Set the System Component Assignment flag for the relevant main instances.

3. Choose you the system component from the possible entries help


Logical component

Definition A logical component is an administrative entity which assigns logical systems, in the entire system landscape and across projects, to the following:

• a main instance of a product with a product version, e.g. the main instance CRM Server of the product SAP CRM with the product version 4.0.

• the system roles or phases in a project, e.g. the system role development system for the configuration.

Use You use logical components to uniquely identify the component systems:

• In the project for Business Blueprint, Configuration, Testing, Customizing Distribution

You use logical components in the Business Blueprint, even if you have not yet setup systems. These logical components are place holders for the systems later.

• During operation of your solution in Monitoring for systems and business processes

• In Change Request Management

You can change the logical systems in a logical component centrally, e.g. if your tests systems change or when upgrading a logical system. You can reuse logical components, e. g. in several projects, or im operational processing, after an implementation project.

Structure The logical systems in a logical componente are usually connected by transport paths.

System roles



System role Use

Evaluation system Business Blueprint

Development system Configuration, Upgrade

Quality assurance system Test

Production system Leading system role in operational processing for system and business process monitoring. Early Watch Alerts are possible for all system roles

Training system Training

Example Logical components in project

Logische Komponente Z_ECC_MyProject

Logical component

Z_SCM_MyProject

(SAP SCM 4.1)

Prioject phase: System/Client

Configuration: ABD/400

Test: ABT/400

Production: ABP/400


Configuration: CDD/300

Test: CDT/300

Production: CDP/300


Configuration: EFD/400

Test: EFT/400

Production: EFP/400

Logical component

Z_CRM_MyProject

(SAP CRM 4.0)

Logical component

Z_ECC_MyProject

(SAP ECC 6.0)

Business process

Logical components in a solution



A solution comprises… …

… Logical component 1, which contains:

… Logical component 2, which contains:

Logical System D

Logicalsystem A

logicalsystem B

logical system C

PR2

PR1 TE1 DE1

Create/Change Logical Components

Use You use logical components [page 78]:

• In the project for Business Blueprint, Configuration, Testing, Customizing Distribution

• During operation of your solution in Monitoring for systems and business processes

• In Change Request Management

Prerequisites • You have assigned the systems to products which you want to use in logical

components.

• You have flagged at least one main instance per system as relevant. You can only then use this system in a logical component.

Procedure

Create Logical Components SAP delivers some predefined logical components. To create a new logical component: ...

1. Choose System Groups and Logical Components → Logical Components → <Product>, in the overview tree.

2. Choose Create New Logical Component from the context menu.


4. Choose a product.

You can create a new product in the screen Create Logical Components.



5. Choose a main instance.


Change logical component ...

1. 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.

2. You can change the product version in the Current System Assignments tab.

3. Assign logical systems to the logical components for the various system roles, e.g. as development system, in the Current System Assignments tab.

In the Current System Assignments tab, you can:

• Consistency Check: System assignment consistency check

• If Change Request Management is configured: Transport Routes: Display the transport routes in which the systems are.

• Where-Used List: Display the system groups in which the logical component is already used, e.g. display the projects which use it.

You can go to the use from the list of uses, to delete it if required.

• System Roles: Change system roles or their sequence, type system roles for the Change Request Management [page 343], e.g. as Subsequent System in a transport route.


Result • Logical components in projects:

Assign the logical components to a project [page 31], in the Project Administration → System Landscape tab → Systems subtab, to be able to navigate within a project in the component systems.

• Operational logical components:

To monitor systems and business processes, Assign the logical components to a solution [page 260].

Delete Landscape Elements

You should create a where-used list [page 82] before you delete systems, servers or databases.

...

1. You cannot delete an object you are editing, if you are in change mode. Go to display mode.

� Choose Landscape Components → Other Object…

2. Search for the landscape element to be deleted, in the possible entries help.



3. Choose Delete.


The landscape element and all its uses are deleted.

Where-used list

Use Before deleting landscape elements, create a where-used list, to delete uses, if necessary.

Features ...

Where-used list

Landscape element Use

Servers Systems in which the server is used as a server or database server

Database Systems

System Logical component

System groups

System componentt Systems

Products Logical component

Systems

System groups

Logical component System groups

Solutions

Projects

All uses of systems in system group are displayed in the where-used list. The following system group, which are hidden in the Solution Manager System Landscape landscape components, are displayed in the where-used list, flagged as Inactive:

• System group of solutions which have been deactivated for operative processing in a solution landscape

• System group for completed projects, i.e. projects to which the status Completed has been assigned in the Project Administration

Activities Call the where-used list:

• in the context menu of a landscape element

or

• with Other Object...

Analyzing the System Landscape by Landscape



Components

Use This function provides a tabular overview of your system landscape.

Features

Selection • Servers

• Databases

• Systems

• System components

Default variants • You can create your own default variants of the report, i.e. the selection rules.

• You can create default variants of the layouts in the SAP List Viewer (ALV), i.e. the results display.

You should create several layouts for each type of landscape component in the ALV Grid Control. For example, for systems to display all R/3 systems in your system landscape or the Support Package statuses.

A layout restricts the output view: It may not show which you have selected in the selection screen, because their columns are hidden in the current output layout. Do not make a restricted layout the default display for all users.

Output The system displays the analysis with the SAP List Viewer (ALV) [external link]. You can print, filter, or sort the analysis, or export it into a spreadsheet such as MS Excel, with the SAP List Viewer.

Activities Call the system landscape analysis with Utilities -> Analyses.

Landscape Component Graphic

Use You can graphically display details of the following landscape elements in your system landscape:

• Servers

• Databases

• Systems



Features • Graphical overview of all information about the landscape components in the tab

• Navigation in the details by click

Activities Go to the landscape component graphic with Switch Display.

Overviews

Use This function shows the assignment of attributes to the following landscape components, graphically.

• Servers

• Databases

• Systems

Prerequisites You have created and assigned attributes for landscape components [page 64].

Features Graphical overview of landscape components and their attributes. You cannot make changes

Activities Go to the overview with Overviews → <Landscape Component> → <Attribute>.

Example You have created the location and the person responsible attributes of a system. You can now see in the overview, which systems belong to a location or person.

Adaptive Computing Settings

Use Adaptive Computing controls the load of your servers by assigning servers to systems dynamically.

You set-up Adaptive Computing in the Solution Manager after the Adaptive Computing Controller, the Adaptive Computing control console, has registered in the Solution Manager.

Prerequisites You have installed SAP NetWeaver and the Adaptive Computing Controller has registered in the Solution Manager. For further information, see the Adaptive Computing installation guide, under www.service.sap.com\instguides.

Adaptive Computing is only visible in the Solution Manager System Landscape (SMSY) if you have installed it.



Procedure ...

1. Call the Solution Manager System Landscape (transaction SMSY).

2. Specify the Adaptive Computing networks:

a. Choose Adaptive Computing → Computer Pools List, in the overview tree.


c. Choose New Entries.

d. Enter the network data.

e. Save your entries and go back.

3. Create computer pools:

a. Choose Adaptive Computing → Networks, in the overview tree.


c. Choose New Entries.

d. Enter the required data.

e. Save your entries and go back.

4. Add servers to the dynamically-assignable servers:

a. Go to the server in the overview tree, via Landscape Components → Servers.

b. Set the Managed by Adaptive Computing flag in the Server Description tab.

c. To assign the server to a computer pool, choose a computer pool from the possible entries help.

d. Enter the required data in the AC Port Definitions tab.


5. Change the settings of the systems to which you want to assign servers dynamically, as follows:

a. Go to the system in the overview tree with Landscape Components → Systems → <system product>.

b. Set the Adaptive Enabled flag for the system in the Header Data tab.

The Adaptive Computing tab appears.

c. Specify the minimum and maximum number of hosts which you want to assign dynamically, in the Adaptive Computing tab.

d. Assign a computer pool in the Computer Pool column.


f. Go to the detail view of the main instance by double-clicking on it.

g. Choose the change icon next to the server to be changed, in the Server tab.

h. Enter the server data.

i. Save your entries.

Result You can now control the load of your servers dynamically.

You call the dynamic server assignment (Adaptive Computing) with Adaptive Computing → Adaptive Computing Controller in the overview tree in the Solution Manager System Landscape (transaction SMSY).



Generate Installation Key for SAP ECC

Use To install, or upgrade to, SAP ECC from Release 5.0, you need an installation key.

Procedure

SAP Solution Manager System ...

1. Call the System Landscape Maintenance (transaction SMSY) in your Solution Manager system.

2. Create your SAP ECC System in the system landschape:

a. Select the landscape component Systems, and choose Create New System, in the context menu.

b. Enter the system ID as the system, in the following dialog box.

c. Choose the product SAP ECC, and the product version SAP ECC 5.0 or higher, from the possible entries help. Save.

d. Complete the system data, as far as possible.


3. Generate the key:

a. Choose System Landscape → Other Object....

b. Set the System flag, and choose the system awhich is to be installed or upgraded, from the possible entries help. If you have created a system in the SAP Solution Manager, in the previous step, choose it.

c. Choose Generate Installation/Upgrade Key.

d. Enter the required data and choose Generate Key.

The system displays the key.

Installation/upgrade tool Specify this key in the installation or upgrade tool.

Tips Search Search for system units which are not visible in the left-hand side of the screen, with Landscape Components → Other Object...

Plan system landscape You can flag all servers, databases and systems as Only Planned. You can then document the system landscape completely, at once, before all system components have actually been technically installed.

Deactivate Progress Indicator Sie can deactivate the progress indicator, which is displayed by default in the status bar at the bottom of the screen, to improve performance: ...

1. Choose Goto → Set-Up System Landscape Maintenance → Edit → Expert Settings.



2. Specify any value for the option Deactivate Progress Indicator, e.g. ‚X’.

3. Choose Continue.

Customizing ID Mapping Framework

PurposeYou use the Customizing ID Mapping Framework in the SAP Solution Manager to exchange messages between un-harmonized systems. In un-harmonized systems, different IDs represent the same entity. ...

You want to exchange messages between un-harmonized systems via an integration server. This integration server is a component of the SAP Exchange Infrastructure (SAP XI). The integration server contains an ID mapping database, which assigns different IDs in different systems to each other. IDs are assigned to each other when they represent the same entity in different systems. The messages also refer to the customizing when exchanging messages with the integration server. The mapping needs to know which customizing IDs in a system correspond to which IDs in other systems.

The Customizing ID Mapping Framework lets you specify this information.

Customizing ID Mapping Framework: Overview

System BSystem A

Marital Status

ID TextLE SingleVH MarriedVW WidowedGS Divorced

ID Text01 Single02 Married03 Widowed04 Divorced

Marital Status


Type SystemR3MS ABuPaMS B

Global ID type Marital Status

Integration Server

ID Mappings

A B Text01 LE Single02 VH Married03 VW Widowed04 GS Divorced

ID Mapping editor

System A Syste m B... ..... . .. .

ID Mappings

R3MS 01 BuPaMS LER3MS 02 BuPaMS VHR3MS 03 BuPaMS VWR3MS 04 BuPaMS GS

System A System B

Message

Name: SmithStatus: 02...

Message

Name: SmithStatus: VH...Mapping

Service



Implementation The Customizing ID Mapping Framework is intended for IT experts, system administrators and consultants who set-up a system landscape in a project. You can use the Customizing ID Mapping Framework in the implementation project, to configure and connect un-harmonize systems.

The SAP Exchange Infrastructure 2.0 configuration guide contains further information about the SAP Exchange Infrastructure configuration, under www.service.sap.com/instguides → SAP Exchange Infrastructure.

Integration

Integration serverThe Customizing ID Mapping Framework uses the SAP Exchange Infrastructure integration server.

• ID mapping definitions from the SAP Solution Manager are replicated in the corresponding integration server (development, quality assurance and production systems).

• You must put ID types [page 93] which you want use, and which are defined in the SAP Solution Manager, in the integration server in XSL format. Either use integration server tools, or edit the XSLs manually with an editor.

If you use Master Data Management (SAP MDM), you can use its XSL creation tool. For further information about master data management, see SAP NetWeaver → SAP Master Data Management in the SAP Library, and www.service.sap.com/instguides → Installation and Upgrade Guides → SAP MDM in the master data management configuration guide.

Distinction from SAP CRM Content IntegratorIn contrast to the Content Integrator, the ID mapping can assign equivalent objects to each other for all customizing objects. The Content Integrator assigns master data to each other. For further information about the Content Integrator, see SAP Content Integrator in the SAP Library.

FeaturesYou can create ID types [page 93] and global ID types [page 94] with the Customizing ID Mapping Framework. You can also use ID types which SAP delivers with the SAP Solution Manager (Add-On ST).

You can set-up the Customizing ID Mapping Framework for the application, with an integration server:

• You can connect the integration server for the ID mapping to the SAP Solution Manager.

• You can define which customizing ID types are to be exchanged between which systems, via which integration servers.

• You can define ID mappings and replicate them in the appropriate integration servers.

Customizing ID Mapping Framework: Definition of ID mappings and replication to an integration server



Integration ServerSAP Solution Manager

Global ID type Marital Status ID Mappings

System B

LE

VE

...

System A

01

02

...

B

LE

VE

...

A

01

02

...

Text

Single

Married

...

System

A

B

...

Type

R3MS

BuPaMS

...ID Mapping Editor

System landscape

System A

System B

Integration Server

All Customizing ID Mapping Framework settings are client-specific, except for ID types and global ID types, which are cross-client.

RestrictionsThe Customizing ID Mapping Framework is for customizing only; it cannot map master data and other objects.

If you use one integration server for each of the development, quality assurance and production system landscapes, you may have to create the ID mappings for each system landscape separately.

The Customizing ID Mapping Framework is not integrated with the Customizing Distribution [page 200].

Do not combine Customizing Distribution and the Customizing ID Mapping Framework for a customizing object and its system. This can cause data inconsistencies. Customizing Distribution and the Customizing ID Mapping Framework are both components of the SAP Solution Manager, but they are not integrated with each other. You can either distribute a customizing object between two systems with the Customizing Distribution, or set-up ID mapping.

Using the ID Mapping Framework with an



Integration Server

Purpose You want to exchange messages between un-harmonized systems, via an integration server. You have saved identical customizing in different systems, under different IDs, in your system landscape. You want to exchange messages which refer to customizing with different IDs, but which identify the same entity, between systems, in an Integration Server. You require ID Mapping for this.

ID Mapping allows you to exchange messages between un-harmonized systems, without having to reconcile the IDs in customizing and all applications in master data.

How the integration server uses the ID Mapping Framework information to exchange data, is described below. For further information about setting-up the ID Mapping Framework, see Setting-Up the Customizing ID Mapping Framework [page 91].

Process Flow Data exchange via the integration server with ID mapping

System B

System A

Marital Status

Marital Status

Integration Server

ID MappingsMessage

Name: SmithStatus: VH...

Mapping Service

ID

01

Text

Single

02

...

Married

...

ID

LE

Text

Single

VH

...

Married

...System B

LE

VE

...

System A

01

02

...Message

Name: SmithStatus: 02...

...

1. System A sends a message which refers to customizing, to the integration server to pass on to system B. The message contains customizing IDs, which refer to entities in customizing.

2. The integration server translates the message into an appropriate format for the receiving system B. At the same time, the Integration Server converts the customizing IDs for the receiving system, with the ID mapping.

3. The integration server forwards the message to system B.



4. System B receives and processes the message further. As the customizing ID has been converted correctly by the integration server, system B can also read and interpret the customizing reference in the message correctly.

Example ...

1. An SAP R/3 development system sends a request, which refers to customizing for marital status, to the integration server, for forwarding to an SAP CRM development system.

2. The integration server converts the request into a suitable format for the receiving SAP CRM system. At the same time, the integration server converts the customizing IDs for marital status into suitable IDs for the SAP CRM system, with the ID mapping.

3. The integration server forwards the message to the SAP CRM system.

4. The SAP CRM system receives and processes the message further. As the marital status customizing ID has been converted correctly by the integration server, the SAP CRM system can also read and interpret the marital status reference in the request correctly.

Setting-Up Customizing ID Mapping

Purpose This process sets up your systems so that you can define ID mappings and use them to exchange data with an integration server, or with the Customizing Distribution.

Prerequisites You are authorized to use the Customizing ID Mapping Framework [page 104].

Process Flow ...

1. Copy the system landscape [page 60] defined in the System Landscape Directory, into the SAP Solution Manager. Follow the SAP Solution Manager installation guide, and the instructions under Set-Up Automatic Data Capture for System Landscape [page 61].

2. You connect the integration server to the SAP Solution Managers in your system landscape in which ID mapping is to be performed. Create RFC connections in the system landscape maintenance [page 63] or the RFC Destination Maintenance (SM59), for business systems or the integration server

For further information about connecting the systems for the Customizing ID Mapping Framework, see under Creating a Destination to the Integration Server for Maintaining the Value Mapping Table in the Configuration Guide: SAP Exchange Infrastructure 2.0 under http://www.service.sap.com/instguides → SAP Exchange Infrastructure.

3. Start the Customizing ID Mapping [page 95] with the transaction SCIDM_CONFIG.

4. You can specify other non-ABAP business systems in the Business Systems [page 97] editing, flag Integration Servers, and create other RFC destinations.

5. You create ID types with the Customizing ID Type Editor [page 95].

6. You can create global ID types with the Global ID Type Editor [page 96].

7. Create type groups [page 99], which create a relationship between customizing ID types, business systems, and an integration server:

� business systems



� equivalent ID types, which are not harmonized between the business systems

� integration server, via which the business systems exchange messages

You can base the type groups on global customizing ID types.

8. Define ID mappings [page 100].

9. Export the ID mappings into the integration server.

Result The system can also perform ID mapping in the message conversion in the integration server.

ID Mapping

Definition Assignment of keys in one system to keys in another system.

Use You can use the ID Mapping when different systems are involved in business process, and have different keys for equivalent objects. Data must be modelled so that, for example, postings can be copied from SAP R/3 into an SAP CRM correctly. The ID Mappings allow the IDs to be related when messages are exchanged between the systems.

Integration

Differentiation from Customizing Distribution and Synchronization Objects ID Mappings assign keys to each other. Synchronization object definitions in the Customizing Distribution only map structures.

Do not combine Customizing Distribution and the Customizing ID Mapping Framework for a customizing object and its system. This can cause data inconsistencies. Customizing Distribution and the Customizing ID Mapping Framework are both components of the SAP Solution Manager, but they are not integrated with each other. You can either distribute a customizing object between two systems with the Customizing Distribution, or set-up ID mapping.

Example You define the ID type Marital Status, to describe the structure of the IDs which contain marital statuses.

System AAA, ID type: Marital status

Key/ID Text

01 Single

02 Married

03 Widowed

04 Divorced

... ...



System BBB, ID type: Marital status

Key/ID Text

LE Single

VH Married

VW Widowed

GS Divorced

... ...

Use this ID type to define the following ID Mappings:

ID Mapping for ID type Marital status

System AAA System BBB

01 LE

02 VH

03 VW

04 GS

ID Type

Definition Technical display of the structure of a key (ID) in a component or system.

Use ID types describe the structure of an ID, and in which customizing objects it is used.

The ID mappings [page 100] are based on the ID types.

Structure An ID type contains the following information:

• the structure of the ID

• field length(s)

• the customizing object in the system in which the ID is used

• use of the ID in other customizing objects

• SAP Exchange Infrastructure (XI) Interface Repository (IFR) namespace

An ID type is not an IFR object. The IFR namespace is only for documentation purposes and for the authorization check. You can set-up the authorization so that a user can only edit ID types from a specified namespace.

You specify the use of the ID in other customizing objects, so that when you create a type group, a check can be made whether the Customizing-Distribution



[page 200] is already set-up for this object. For further information, see the Restrictions in Customizing ID Mapping Framework [page 87].

ID types are lockable logical transport objects, of type SCI1 in the transaction SOBJ.

Integration Different ID types which are equivalent, and can be in various components, are put in the same global ID type [page 94].

Example The customizing ID type R3MaritalStatusID contains information about marital statuses in an SAP R/3 system. The ID type was based on the field FAMST in the customizing object V_T502T. The definition on R3MaritalStatusID contains an overview of all customizing objects in which this ID is also used.

Global ID Type

Definition Class of equivalent, but not identical ID types [page 93], which can be in several components or systems.

Use You can base type groups [page 99] on global ID types.

Structure Different ID types which are equivalent, and can be in various components, are put in the same class.

Global ID types are lockable logical transport objects, of type SCI2 in the transaction SOBJ.

A global ID type is not an IFR object. The IFR namespace is only for documentation purposes and for the authorization check. You can set-up the authorization so that a user can only edit ID types from a specified namespace.

Example Global customizing ID type: Marital status

Customizing ID Type Software Component

BuPaMaritalStatusID SAP_ABA

R3MaritalStatusID SAP_APPL

The global customizing ID type Marital Status comprises the two equivalent customizing ID types BuPaMaritalStatusID and R3MaritalStatusID. BuPaMaritalStatusID is in the software component SAP_ABA, R3MaritalStatusID in SAP_APPL.



Customizing ID Mapping

Use This is the central starting point for setting-up and defining customizing ID mapping. You can define:

• ID types and global ID types

• business systems or integration servers in which the ID mapping is to be performed

• type groups which relate customizing ID types and business systems

• ID mappings


Activities ...

1. Call the Customizing ID Mapping Framework with the transaction code SCIDM_CONFIG.

2. The system displays an initial screen from which you can go to all transactions in the Customizing ID Mapping Framework.

Customizing ID Type Editor

Use This function creates and edits customizing ID types [page 93]. SAP provides a set of predefined customizing ID types.

Integration The Customizing ID Type Editor is part of the Customizing ID Mapping Framework.


Features With the editor, you can:

• create

• display

• change

• or delete customizing ID types.

You can also specify whether it is a structured or simple ID type.

Activities ...

1. Specify a technical name, a description and an Interface Repository (IFR) namespace, in the component SAP XI.

2. For an ID type which is based on a customizing object in an ABAP system, specify the customizing object.



The ID type value sets are read from the system via the customizing object when you define ID mappings [page 100].

3. You specify other uses of the ID in other customizing objects. The specifiication of other uses is important because the Customizing ID Mapping Framework checks whether a customizing object is already used in the Customizing Distribution for the same system. In this case, you cannot use it in the Customizing ID Mapping Framework. Conversely, the Customizing Distribution checks whether objects are already used in the Customizing ID Mapping Framework for the same systems.

4. Specify the lengths of the ID fields. This is important because the integration server saves the IDs in an unstructured field.

Global ID Type Editor

Use This function displays global ID types [page 94] delivered by SAP, and can create and edit user global ID types. SAP provides a set of predefined global ID types.

Integration You use global customizing ID types for equivalent, but not identical ID types [page 93], which can be in several components or systems. Global customizing ID types specify which ID types are equivalent.

You can base a type group [page 99] on a global customizing ID type. They are not necessarily for creating type groups, they can document the relationship of customizing ID types.

Prerequisites You have created the required ID types.

You are authorized to use the Customizing ID Mapping Framework [page 104].

Features With the editor, you can:

• create

• display

• change

• or delete global ID types.



Editing Business Systems

Use This function displays the systems in the SAP Solution Manager system landscape maintenance [page 63]. The systems are flagged in the SAP Exchange Infrastructure as "Business Systems". This function also flags business systems as integration servers.

Displaying and creating the business systems, and flagging the integration server, are preparatory steps to be able to define the ID mappings [page 100] which are required for this Integration Server, later. The integration server RFC destinations are used later, to export ID mapping definitions to the integration servers.

Integration If you have flagged systems as integration servers, you can create type groups [page 99] for them.

Prerequisites You have defined business systems in the connected SAP Solution Manager system System Landscape Directory (SLD), and copied the data from the SLD into the SAP Solution Manager system landscape.

The SAP Solution Manager installation guide contains further information about the System Landscape Directory and setting up the SAP Solution Manager system landscape.

You have created RFC read destinations in the system landscape maintenance, for normal business systems.

You have created an RFC destination for the Customizing Synchronization or for the Solution Manager, in the system landscape maintenance, for integration servers. You have saved the user and password for the RFC destinations you have created, or created Trusted System connections, so that no logon screen appears. This is important because some Customizing ID Mapping Framework system activities, such as exporting ID mappings to the integration server, run in the background. You have also ensured that the saved user and Trusted System connection logon users have authorization for the authorization object S_RFC for the function group SKMP. The SAP Exchange Infrastructure 2.0 configuration guide contains further information about the integration server RFC destinations, under http://www.service.sap.com/instguides → SAP Exchange Infrastructure.

Features All business systems in the SAP Solution Manager system landscape are displayed.

You can now:

• Flag business systems as integration servers

• Assign RFC destinations for ABAP-based business systems

• Specify an RFC destination for an integration server or business system, manually, if no RFC destination can be specified in the Solution Manager system landscape, or another RFC destination is to be used

• Add non-ABAP-based systems manually, because they are not copied automatically from the SLD



In this way, you can also use non-SAP-systems in the Customizing ID Mapping Framework.

Edit System Relationships

Use Maintain system relationships to specify the prerequisite for the replication of ID mappings. Specify business systems with a specified system use, e.g. development, quality assurance or production, for each integration server. Assign the business systems to the integration server with which they exchange data.

Prerequisites Integration servers for which system relationships are to be maintained, have been flagged as integration servers, as described under Edit Business Systems [page 97]. The business systems to be assigned have been put in the business systems overview.

Features You can edit system relationships in two ways:

• System relationships for simple system landscapes: All business systems in a system use for which data is to be exchanged by ID mappings are collected under Standard Relationships.

• System relationship for more complex (branching) system landscapes: You can specify the source and target integration servers in cases in which one source business system serves several target business systems, in addition to the Standard Assignments, with Extended Assignments.

The systems involved in the data exchange are listed in the corresponding columns. The corresponding business systems accross system uses, are displayed row by row.

Assign the same system type accross system uses to the same rows.

Example 1: Incorrect assignment of business systems to rows (in red)

Integration Server

FKTstDev FKTstQual FKTstPrd

FKTstDev_R3 FKTstQual_R3 FKTstPrd_MDM

FKTstDev_MDM FKTstQual_MDM FKstPrd_R3

Business Systems

FKTstDev_CRM FKTstQual_CRM FKstPrd_CRM

Example 2: Correct assignment of business systems to rows

Integration Server

FKTstDev FKTstQual FKTstPrd

Business Systems

FKTstDev_R3 FKTstQual_R3 FKTstPrd_R 3



FKTstDev_MDM FKTstQual_MDM FKstPrd_MDM

FKTstDev_CRM FKTstQual_CRM FKstPrd_CRM

Activities ...

1. Choose Goto → System Relationships.

2. To edit the business systems which are to exchange data via a specified integration server, flag it in the list of integration servers in the Standard Relationships tab, and add or delete business systems.

You can only add business systems which have not already been assigned to other integration servers. You can display up to 10 such system relationship next to each other. To maintain more system relationships, delete a displayed system combination by deleting the flag in the integration server. This flag only affects the display.

3. To enter more business systems in addition to the standard relationships, because they are also served from the same source, assignm it in the Extended Assignments tab.

You can only enter new business systems, you cannot delete existing standard assignments.

Create a Type Group for an Integration Server

Use This function links customizing ID types to their system landscape (including the integration server). ID types and business systems belong in the same type group if:

• the business systems exchange messages

• these messages contain the appropriate customizing ID types [page 93]

• the customizing ID types are equivalent, but not harmonized in these systems

Equivalent ID types are put in the same type group, i.e. the type group defines the scope of one ID mapping.

The combination of an ID type and a business system can only be in one type group for an integration server.

Integration When you have created type groups for an integration server, you can define ID Mapping [page 100] for this type group and the integration server.

Prerequisites You have defined ID types and possibly global ID types, and Business Systems [page 97], and flagged integration servers.

Activities ...

1. Choose an integration server, for which you want create a type group.



2. Specify an existing customizing ID type, or copy one from a global customizing ID type.

Example ...

1. Choose the integration server IntServerDev, for which you want to define a customizing ID mapping.

2. Specify a technical name for the type group: gruppe_familienstand.

3. Insert the customizing ID types BuPaMaritalStatusID and R3MaritalStatusID from the global ID type Familienstand.

4. Assign the appropriate business systems to the customizing ID types.

Define ID Mapping

Use This function assigns different IDs from different systems, to each other. IDs are assigned to each other when they represent the same entity in different systems. The Customizing ID Mapping Framework sends this information to an integration server, which uses the mapping information to forward messages.

Prerequisites You have defined Business Systems [page 97] and created type groups for relevant integration servers [page 99].

Features The system displays all integration servers, with their type groups. The Customizing ID Mapping Framework checks the ID types and systems of a selected type group. It checks in particular, whether the systems can be reached by RFC and whether the customizing objects, on which the ID types are based, exist. If errors are found, a log is displayed.

You can:

• read all IDs in a business system for a customizing ID type

• read and display ID texts from the systems

• assign the IDs read to each other by Drag & Drop

• create value sets for customizing objects from non-ABAP systems, manually

• search for identical IDs

• search for the mapping to which an ID is assigned

• change the processing status of the type groups.

• personalize the ID mapping display

• export ID mappings to an integration server

• switch between displaying the ID mappings which are active in the integration server, and those which have been changed locally in the Solution Manager

• delete all IDs of an ID type from the ID mappings

• delete ID mappings for a type group from an integration server.



If the ID mappings have been deleted from the integration server, the ID mapping for the corresponding messages do not work in the integration server until new ID mappings have been exported.

• display the export and deletion logs

Define and Export ID Mapping

Prerequisites You have edited business systems [page 97] and created type groups [page 99]. You are authorized to use the Customizing ID Mapping Framework [page 104].

You are in the Customizing ID Mapping Framework [page 95].

Procedure

Define ID mapping ...

1. Choose ID Mapping Definition.

The system displays an overview of all existing integration servers and their type groups.

2. Choose a type group at the left-hand side of the screen.

The Customizing ID Mapping Framework checks the ID types and systems of the type group. It checks in particular, whether the systems can be reached by RFC and whether the customizing objects, on which the ID types are based, exist. If errors are found, a log is displayed.

3. If a log of the checks is displayed, go back.

4. You can switch from display to edit mode.

5. Choose a customizing ID type at the right-hand side of the screen and choose Display IDs from System.

6. When you have selected the first customizing ID type, choose all IDs and copy them into the ID mappings list by Drag & Drop.

7. Repeat for all the other customizing ID types:

� Choose IDs and assign them to the existing IDs in the list by Drag & Drop.

� Put equivalent IDs in the same row, each row represents an ID mapping [page 92].

When you define ID mapping for harmonized or partially harmonized systems, you can display identical IDs with Select Identical IDs and assign them automatically with Assign IDs → Assign Identical IDs.

All customizing ID types have a status between New and Deleted. The F1 help explains the meaning of the status values.

8. To assign IDs from customizing objects from non-ABAP systems, choose Create Value Set Manually, und assign the manually-created IDs.


Export ID Mapping ...



1. Choose a type group.

2. Choose Export to Integration Server.

3. Choose whether you want to export in dialog or in the background, in the following dialog box.

4. If you export in the background, enter the required data in the following dialog boxes.

The system exports the selected type groups to the integration server. The processing status changes to Completed.

Result The ID mappings are in the integration server and can be used there to convert messages.

ID Mapping Export for Several Type Groups

Use In the ID mapping definition, you can export the ID mapping data selectively for only one specified type group. This function can export the ID mappings for several type groups to a target integration server at the same time.

Prerequisites The ID mappings to be exported for type groups have been specified, as described under ID Mapping Definition [page 100].

Activities ...

1. Choose Goto → Export ID Mapping or the ID Mapping Export pushbutton in the initial screen.

2. Choose the target integration server to which the ID mapping data is to be exported.

3. Choose one or more type groups for the export.

4. Check the selection.

5. Start the export with Export.

6. Schedule the background job. You can only export in the background because of the possible quantity of data.

You can display or delete the logs with Utilities → Display Export Logs or Delete Export Logs.

Replicating ID Mappings

Use The replication of ID mappings lets you reuse ID mappings in other integration servers.

Prerequisites You have exported the ID mappings to be replicated with their type groups, so that they have the status Active.



You have maintained the System Relationships [page 98].

Features The replication can:

• Adjust type groups for the target in the SAP Solution Manager

• Replicate ID mappings for the target in the SAP Solution Manager

• Start the ID mapping export from the SAP Solution Manager into the target integration server

The selection details give an overview of the customizing ID types and business systems in the type group.

Activities ...

1. Choose Goto → Replicate ID Mapping or the Replicate ID Mapping pushbutton in the initial screen.

2. Choose the source and target integration server for the replication.

3. Specify the ID mappings to be replicated by selecting their type groups.

4. Specify the replication actions:

� Adjust type groups: If the type group is not yet in the target, it is created. If the type group already exists, it is enhanced according to the defined system relationships, if there are inconsistencies with the source. Type groups are not deleted.

� ID mapping: Replication of ID mapping

If there are already ID mappings in the target, all old ID mappings are deleted and flagged as such in the status, if you replicate again. The replicated ID mappings are added to the deleted ones and have the status New.

5. Check with the corresponding icon whether you have all required authorizations for the replication, and whether the replication can be performed according to the defined system relationships.

6. Specify whether you want to to export the mapping data to the target integration server after the replication. If so, the job for the selected event must run in the background.

The export replaces the old ID mapping data in the target integration server with the new ID mapping data. This can temporarily disturb the data transfer with the integration server.

7. Choose Replicate.

8. The replicated type group(s) are in the type group overview for the selected target integration server.

You can display or delete the logs with Utilities → Display Replication Logs or Delete Replication Logs.



Authorization for the ID Mapping Framework Authorization objects and their functions

Authorization Object Function

S_SCIDMREP Create/display/change (global) ID types

S_SCIDMCFG Display/edit business systems

Define type groups

Adjust type groups in the replication

S_SCIDMASG Assign ID types and business systems to a type group

Adjust type groups in the replication

S_SCIDMMAP Define ID mapping and export to integration server

Replicate ID mapping

Using Templates

Purpose This process describes the use of a template. You can use templates:

• As a customer:

� You create a template and use it in one or more implementation projects as the basis of the Business Blueprint.

� You create a template in a system and transport it into other systems as the basis for the Business Blueprint of a project, e.g. in a Global Rollout [page 118].

• As a partner:

You can create templates and deliver them as partner templates for customer projects.

You can base new templates on any other template, whether delivered by SAP or created yourself.

Prerequisites You have setup your system landscape [page 60].

For further information about restrictions in the use of templates and template projects, see the SAP note 603336.

Process Flow

Define a template ...

1. Create a project of type Template Project in the Solution Manager Project Administration.



Assign a name in the customer namespace to your templates. We recommend the namespace /…/. You should only use one namespace for the objects in a project.

2. You can base your new template on an existing template in the Scope tab in the Project Administration.

3. Create a project structure in the Business Blueprint transaction, and assign transactions, URLs and documentation to structure elements.

4. To reuse documents in other projects, assign them in the Gen. Documentation tab.

The Project Documentation tab is only part of the current project, and not part of the template. Documents in the Project Documentation tab are not put in the template, and can therefore not be reused in other projects.

5. Assign, for example, BC Sets, IMG activities and test cases, to project structure elements, in the Configuration transaction.

Other objects are created in the component systems by the Solution Manager. These include BC Sets, user transactions, programs and CATTs. Proceed as follows in the component systems:

• Create a transportable package with transport recording, for each template and logical system.

Assign names in the /.../ namespace, if it exists. Use the same namespace when naming your packages.

• Create a separate package and a separate transport request for objects which are to be used in several templates.

• Assign the objects to the package as they are created.

• Create a transport request for each template and logical system, and record the objects in them, so that you can transport them into the correct component systems later.

6. Create one or more templates in this template project, in the Templates [page 112] tab in the Project Administration.

7. Assign templates to the scenarios with the possible entries help in the Structure tab in the Business Blueprint transaction, to copy the scenario structures into your template. You can assign several templates per scenario.

8. Set the visibility of the template in the Project Administration to Public in the Templates tab, to make them visible system-wide.

9. Deliver your template in the Templates tab in the Project Administration.

This is not necessary if you reuse the template in the Solution Manger in which you created it.

10. Create a new version of the template in the Project Administration, to further develop it.

Reusing a template in the same Solution Manager system Public templates are visible system-wide and can be used in any project system-wide (see the Templates [page 112] tab). ...

1. Create a project in the Project Administration of the Solution Manager in which the template was created.



2. Proceed as described in steps 4-6 of the Performing an Implementation Project with the Template in the Target System section.

Reusing a template in another Solution Manager system For example, you send the template and its objects into another system, in a global rollout, as the template for the Business Blueprint of a project there.

Transport a template into another system landscape ...

1. Send the objects, e.g. BC Sets or CATTs, which you have created in the source Solution Manager component systems, to the target Solution Manager component systems, e.g. from the headquarters component systems to the subsidiary component systems, in a global rollout:

a. Analyze your project in the source Solution Manager, and specify the object types which you created in the component systems, and the components which you use, for the configuration and test case assignments in the template project.

b. Test the template in a test system:

i. Transport the transport requests from the component systems into a test system, in which the same products and product versions are installed as in the target component systems.

ii. To test whether the objects have been assigned to the project structure, choose the transaction Business Blueprint (SOLAR01) → Environment → Refresh Buffer in the test system. The system lists assignment errors in an error log.

c. If the test is successful, send the transport requests from the test system to the target component systems.

2. Release the transport with the template and send it into the target system.

Performing an implementation project in the target system with the template ...

1. Import the transport with the template into the target Solution Manager system.

2. Import component system requests for the template, into the component systems.

3. Create an implementation project in the target system Project Administration.

4. Search for the template or templates which you want to implement, in the Template Selection tab in the Project Administration.

5. Select the scenarios which were created in the source system for this template, in the Template Selection tab in the Project Administration.

The system copies the structure and the assignments from your templates, in the Business Blueprint and Configuration transactions.

6. Perform the configuration in the target Solution Manager component systems.

7. If the template has changed, compare the new version of the template with the project structure and the assigned objects of your target system, and copy the changes if required [page 115].

Create a Template Project

Use Choose project type ‘Template’ when you want to create a new template for other projects. Creating a new project structure and assigning business content, for example,



preconfiguration and documentation, to the structure, are central steps in the process of creating a template.

Prerequisites • You require change authorization in the project administration transaction in the SAP

Solution Manager (SOLAR_PROJECT_ADMIN). This authorization is in the Project Leader Role [page 124] (SAP_SOLAR_PM).

• You have created transportable packages in the Solution Manager and component systems.

• To be able to transport the templates separately into other systems, e.g. to subsidiaries in a global rollout, you have satisfied the following prerequisites in the Solution Manager system and in the component systems:

...

a. You have created a transportable package with transport recording, for each template and logical system.

Assign names in the /.../ namespace, if it exists. Use the same namespace when naming your packages.

b. You have created a separate package and a separate transport request for objects which are to be used in several templates.

Assign the objects to the package as they are created.

c. You have created a transport request for each template and logical system.

Record the objects in the transport request, so that you can transport them into the correct target systems later.

• You have activated the recording of objects in transport requests in the component system clients, to be able to create objects such as BC Sets or CATTs in the component systems accessed by the Solution Manager.

Procedure ...

1. Start the project administration transaction in the SAP Solution Manager.

2. Choose the Create Project icon or Project -> Create from the menu.

3. Enter a project name, and select and confirm Template Project.

4. Edit the following tabs:

Tab Actions

General Data [page 26]

Check the entries in the Person Responsible and the Project Language fields and change if necessary. Note: You cannot change the project language at a later date.

Templates [page 112]

Create a template. The structures, assignments, products, etc. of your template project are put in the template, and it is sent to the subsidiaries when it is released by the head office, or reused in the same system.

Assign a code in the Templates column, and the template name in the Name column.

When the templates have been imported into the subsidiaries, all templates to which at least one scenario has been assigned, are displayed in the Template Selection tab, with the naming convention <code> - <template name>, e.g. ZBANK - BANKING.

To lock the template completely or partially against changes in the subsidiaries for a global rollout, select Global Rollout Functionality is Active in the



Templates tab.

See Global Rollout with a Template [page 118].

Scope [page 27] Choose one or more templates if you want to base your template on existing templates.

Make no selection if you want to create a new template.

System Landscape [page 31]

Define the required system landscape.

Project Standards [page 38]

Define the default status values, keywords, and documentation types for your template.

5. Save the project.

6. Specify the context for your documentation in the Knowledge Warehouse, in the following dialog box.

The document context of a project controls whether documents can be edited by more than one project. If you change a document in a different context from that in which it was created, the system copies the document into the new context.

You should use the same context in all projects except template projects, and control access with authorizations.

Use a separate context for template projects. You can:

• Choose an existing namespace prefix (/.../) in the possible entries help for the Enhancement field, and complete it after the second slash.

• Specify a new namespace prefix in the Enhancement field. The system creates this name prefix with the specified enhancement release. The namespace must:

• have a valid licence in this system

• have the role P (production)

• be changeable in this system

• Create a new release for an existing enhancement. There are no release restrictions.

7. Specify a transportable package, or create one, in the following dialog screen.

8. Choose Continue.

Result You have created a template project. You can work on your template in the Business Blueprint transaction.

Create and Edit Project Structure

Use The project structure displays all of the master data, organizational units, business scenarios, business processes, and process steps belonging to your template. To create a project structure:



• Add new business scenarios, business processes, process steps, master data, and organizational units

• Select predefined business scenarios, business processes, process steps, master data and organizational units, which are delivered by SAP with the Business Process Repository.

• Select processes from a production solution landscape.

Prerequisites You have created a project [page 25] in the Project Administration. If you want to use processes from a production solution landscape which you have created in the SAP Solution Manager Operations, you have selected this solution landscape in the System Landscape [page 30] tab in the Project Administration.

You are in the Business Blueprint transaction.

Procedure

Adding structure elements ... ...

1. Put the cursor on an Organizational Units, Master Data or Business Scenarios structure element.

2. Position the cursor on an empty row in the list displayed for the structure element.

3. Choose the Structure tab [page 139].

4. Specify from where you want to copy existing structure elements into your project, in the possible entries help:

� to select scenarios, processes or process steps already predefined by SAP, choose Business Process Repository under Selection Help.

� to select scenarios, processes or process steps from an existing project, choose Projects under Possible Entries Help .

� to copy processes from a production solution landscape which you have created in the SAP Solution Manager Operations, choose Solution Landscape under Selection Help.

The system only offers the option Solution Landscape in the possible entries help, if you have specified a solution landscape in the Solution Landscape subtab in the System Landscape tab, in the Project Administration.

5. Choose an element from the possible entries help.

If you have chosen a structure element from the Business Process Repository, the system specifies its components. The original name of the structure element is displayed in the Name in Business Process Repository column.

6. If you want to create a new structure element, specify its title. Specify a logical component for master data, organizational units, and process steps.


The system copies the entries into the structure and saves them. The possible entries help selection is saved, and displayed again in the next session.

8. Choose the structure element Business Processes or structure elements of the type Process, and proceed as described in step 1.

Move structure elements...

1. Go to the element in the structure which you want to move.

2. Click on the folder icon in front of the structure element, and move it to the new position by Drag&Drop.



3. Save. ...

Start the Business Blueprint transaction.

Mark a structure element. Drag the marked structure element to the new position in the structure and drop it.

You can only move structure elements on the same level; e.g. process steps only at process step level.

You can also change the sequence in the Structure tab.

Assign templates to the scenarios You must assign a template to a scenario in template projects, to copy the structure of the scenario into the template. Only templates which have been assigned to at least one scenario can be reused later.

1. Select the structure element Business Scenarios in the structure.

2. Choose the Structure tab.

3. Choose one or more templates for the scenarios, from the possible entries help.


The system copies general master data and organizational units, i.e. master data and organizational units at the highest structure level, into all templates assigned in the Structure tab.

The system displays the assigned templates system-wide, in the Template Selection tab in the Project Administration. You can now Reuse these Templates System-Wide, in any Project [page 104].

Assign Global Attribute If you have set the Global Rollout Functionality is Active flag in template projects in the Templates tab in the Project Administration, you can assign values for the Global attribute to the structure elements, in the Structure tab in the Business Blueprint. These values determine whether and how the structure element can be changed when the template is reused. For further information, see The Global Attribute in Global Rollout [page 120] and the Global attribute F1 help.

Result You have created a project structure. You can now:

• Rename structure elements

• Delete structure elements

• Remove structure elements from the scope, by deselecting them in the structure (only implementation projects)

• Assign contents to individual structure elements in your structure, for example documentation and transactions.

See also:Assigning Transactions to a Process Step [page 145]

Project Documentation Tab [page 154]

•



Create and Assign Preconfiguration

UseYou can use the Konfiguration tab to assign preconfiguration in the form of BC Sets, CATTs or eCATT test configurations, to structure elements, or assign transactions or programs to IMG activities. You can create a template either with preconfiguration or with IMG activities, in a template project, which is then used in a Global Rollout Project of a company. You can also use these assignments to be able to trace your IMG activities, and the transactions and programs used during the configuration in an implementation project, later.

PrerequisitesYou have called the Configuration transaction and chosen the Configuration tab.

Procedure

Aassign existing preconfiguration, transactions or rReports ...

1. Go to the structure element to which you want to assign preconfiguration, in the project structure.

2. Choose BC Set, CATT, eCATT Test Configuration, Transaction, Program or Add-On Transport Request, in the Type column.

3. If it is not a process step, enter a component from the possible entries help in the Component field.

4. Make an entry in the Object column, or choose from the possible entries help for the Object field.


The assigned objects are in the component systems. You can also save objects of type eCATT Test Configuration only, centrally, in a specially nominated system. For further information, see the Test Cases Tab [page 160].

Assign IMG objects ...

1. Go to the structure element in the reference structure to which you want to assign an IMG object.

2. Choose IMG Object in the Type field.

3. If it is not a process step, enter a component from the possible entries help in the Component field.

4. Call the possible entries help for the Object field. You go to the Implementation Guide (IMG) of the selected component system.

5. Choose one or more IMG object nodes and choose Select.

6. Choose Copy Selected Nodes.

You have now assigned an IMG object to a structure element. The system goes back to the Configuration tab and fills in the Object and Description columns.

Create and assign preconfiguration...

1. Go to the structure element to which you want to assign preconfiguration, in the project structure.

2. Choose a Type.



3. To create a new BC Set, CATT or eCATT test configuration from the Configuration tab, enter a name in the Object field and choose Create.

4. You go to one of the following transactions, depending on the object type:

� BC Set: BC Set Maintenance

� eCATT Test Configuration: Test Configuration (eCATT tool)

� CATT: Change test case.

5. Enter the data required to create a new BC Set, eCATT test configuration or CATT.

See also:

• Create Business Configuration Sets [external link]

• Create/Edit Test cases [page 160]

• Create eCATT Objects [external link]

For further information about using BC Sets, see Business Configuration Sets [external link] in the SAP Library. For further information about using CATT and eCATT, see Test Workbench [external link] in the SAP Library.

Templates Tab

Use You manage your templates in this tab. You release finished templates, and transport them. You create new versions of templates, and archive old versions.

Integration By default, templates which you are editing are invisible system-wide. To make a template visible system-wide, change its visibility to Public. You can put a public template in the scope of any project, system-wide.

Prerequisites You are in vour template project in the Project Administration.

Features

Create and change templates You create new templates and change existing ones with pushbuttons.

Supporting global rollout If you activate the global rollout functionality, you can lock your templates completely or partially against changes in the subsidiaries, in the Business Blueprint.

For further information, see Global rollout with a Template [page 118] in the Define Template in the Company Headquarters section.

Publish a template You publish a completed template system-wide with the Change Visibility pushbutton.

If you change the visibility of a template from Private to Public, the system updates the system landscape data of the template. The template is visible system-wide in the Scope tab in the Project Administration. The visibility status is displayed by an icon in the Templates tab.



Transport You transport the template with the Deliver pushbutton using the template collector.

The template collector leads you through the template transport steps. Choose an existing transport request of type Transport Copies in the template collector, or create a new one. Release this transport request in the Transport Organizer.

Create a new version You create a new version of a public template with the Increase Version Counter pushbutton, to preserve the status of the old template and proceed with the new version.

Archiving When you create a new version of a template, you can archive the old version, to be able to compare different versions later.

Display job log You can call the logs of the release background jobs (template_ship) and archiving (template_archive) with the Call Job Log pushbutton. ...

Result You have released your template for reuse. You can now reuse the template in the same Solution Manager system, transport it in your system landscape, or deliver it to your subsidiaries, to harmonize processes, customizing and other system settings company-wide.

See also:

Global Rollout with a Template [page 118]

Transport Requests

Use The SAP Solution Manager contains transport functionality for template projects:

Templates transported for template projects contain the following elements:

• Project structure (positioned structure items)

• Assignments of business content made in the Business Blueprint and Realization, for example, BC Sets, transactions, or test cases.

Objects such as BC Sets or CATTs, which you have created in the component systems from the Solution Manager, are not transported with the template. To transport these objects from the component systems, for example to the subsidiaries of a company, proceed as described under Global Rollout with a Template [page 118].


Procedure You can supervise change requests concerning your project in the project administration transaction. You can access the following functions for the current client on the Transport Request tab:



• Activate Change and Transport System (CTS) functionality

Activating the CTS functionality allows you to create change requests. After activation of the CTS functionality, the button text changes to Display CTS Project Data. As soon as the CTS project is completed, the button text changes to Reactivate CTS Functionality.

• Assigned CTS Requests

Select this button to go to the an overview of the request in the Transport Organizer. Here you can create orders for a project.

• CTS Project Piece List

The project piece list remains unchanged. Once the project is complete, you can export the entire piece list.

• CTS Project Status Switch

Choose this button to set the project status switch.

• Complete CTS Project…

Select this button to close your project. You can reactivate it later.

Packages for objects

The project structure and its assignments (business content) are assigned to the package you enter here. Any later changes made to the project structure, for example, to the project scope, or the Business Blueprint, are automatically assigned to this package. You are only required to enter the corresponding transport request.

If you don't enter a package on the Transport Request tab, you will be asked to enter a package every time you save.

Note for project assignment

The automatic assignment of transport requests to a project is not supported. You can, however, carry out assignments for documentation purposes. Assigning your project to a transport request ensures that all changes made in the Business Blueprint or during configuration are recorded in the transport request. Before you can assign your project, you have to activate the CTS functionality. See the Activate CTS Functionality section above for information on how to activate the CTS functionality.

To assign your project: ...

1. Call up the Transport Organizer.

2. Call up the request to which the items in your project have been assigned.

3. Select the request.

4. Select Request/Task → Display.

5. Go to the Properties tab.


7. Enter the name of your project in the Project field. The description of the project appears automatically when you save.

8. Save your entries. You have now established the project assignment.

For more detailed information on the Change and Transport System (CTS) and Customizing projects, see Using Projects to Control Transports [external link].



Compare and Adjust with the Template/Source

Use This function compares the structure and the objects assigned to your Solution Manager project with its source, e.g. a template or the Business Process Repository (BPR). If the source has changed, you can copy the changes and improve the process structure and the assigned objects.

Integration You can copy structures and the objects assigned to them, e.g. documentation and IMG objects from a template or the Business Process Repository, into your project. For further information about the copy function, see Resolve Differences between Source and Target [page 116].

After you have copied elements from the source into your project, the source can change, e.g. because the template has been adjusted to a new program version, errors have been corrected in the template, or a new version of the BPR scenario has been delivered.

Compare the version of the copied elements in your project with the source which you have copied, in a background job, with the function Compare and Adjust. The system automatically uses the newest version of the source for the comparison. You can choose another version as the source of the comparison when you define your project system landscape in the Project Administration (transaction SOLAR_PROJECT_ADMIN).

You can copy the changes which this background job has identified, into your project, in the Business Blueprint (SOLAR01) and in the Configuration (SOLAR02).

Prerequisites You have copies structures into your project from one of the following sources:

• the repository for business processes and scenarios delivered by SAP (Business Process Repository (BPR))

• a template

• another project structure from the possible entries help in the Structure tab in the Business Blueprint (SOLAR01)

• an entire project, using the copy function in the Project Administration

Features • Compare structures which were copied up to and including Solution Manager Version

2.20.

• Compare and Adjust all objects in the following tabs:

� General Documentation

� Structure

� Transactions

� Configuration

� Development

� Test Cases

• Compare and Adjust changes to URLs in the Transactions tab. The system does not flag changes to other objects in the Transactions tab, e.g. changes to BC Sets and documents, and updates of CATTs/eCATTS.

• Copy new or changed elements from the source into your project



• Copy deletions in the source into your project

Activities ...

1. Choose Goto → Compare and Adjust (transaction SA_PROJECT_UPGRADE) in the initial screen of the Project Administration, to compare your project with the source.

2. The Compare and Adjust function:

� compares your project structure and its elements with their source, e.g. templates, the BPR or other projects.

� flags the structure elements of the target which have changed since you copied them into your project, with a red icon, in your project structure and the tabs in the transactions SOLAR01 and SOLAR02.

� flags the structure elements which have not changed, with a green icon, in the transactions SOLAR01 and SOLAR02.

To hide the change icons in the transactions SOLAR01 und SOLAR02, reset the Adjustment Mode flag in your user settings.

3. The system creates a log, which you can display in the transaction SM37. The log shows errors which occurred in the comparison, and the number of differences found in your project.

4. The Adjust to the Original pushbutton in the transactions SOLAR01 and SOLAR02:

� displays the differences between source and target

� selects new or changed elements in the source, and copies them into your project

� selects deletions in the source, and copies them into your project

• The Finished pushbutton changes an icon from red to green. The structure node is only also set to green if all tabs have been set to green.

• If the structure node has not yet been set to green, the left-hand side of the Compare and Adjustment dialog box screen can show differences for tabs which have already been set to green. If you perform the function Compare and Adjust at this stage, the tab gets a red icon again.

• The Compare and Adjust pushbutton is active as soon as a structure node has been copied from another structure node in the same Solution Manager system.

For comparisons with templates, you must first perform the function Compare and Adjust, and then choose the Adjust to Original pushbutton in a tab.

Resolve Differences Between Source and Target

Use This function copies changes to structures and structure elements which you have, for example, copied from a template or the Business Process Repository (BPR) into your Solution Manager project, into your Solution Manager project.



Prerequisites • You have set the Adjust Mode flag in your user settings, so that the status icons are

displayed in front of the structure elements and in the tabs, after the comparison in the transactions SOLAR01 and SOLAR02.

• You have selected the Adjust to Original pushbutton in a tab in the transaction SOLAR01 or SOLAR02.

• You have performed the function Compare and Adjust (SA_PROJECT_UPGRADE) to compare changes in templates with your project.

Features • List of entries in the current tab in your Solution Manager project

• List of corresponding entries of the new version of the source node, with status

• Copy all or selected changes and deletions in the source, into your project

To replace an entire substructure in your project, for example a complete scenario with the substructure which has changed in the source, for example a template:

• Delete the substructure in your project.

• For a comparison with a template, perform the function Compare and Adjust first. Choose the Compare with Original pushbutton in the Structure tab at the level above the deleted structure.

The system shows the deletion in the right-hand side of the Compare and Adjust dialog box.

• Copy the new entry into your project.

• The system displays the additional pushbutton Finished in the Compare and Adjust dialog box, for all structure elements and tabs whose source has changed. You can set the red icons, which show changes, to green, with the Finished pushbutton, whether or not you have copied the changes into your project.

Before you can set the red icon in front of a structure element in your project to green, you must have set the red icon to green for this structure element in all tabs in the transactions SOLAR01 and SOLAR02. You can hide user settings tabs.

Example You want to compare elements in a template with your project. Only copy one change at a time to be able to monitor the changes in your project: ...

1. Copy a new BC Set from the template in the Configuration tab, into your project, in the Compare and Adjust dialog box. Activate the BC Set in your project because it contains important changes.

2. Copy a new IMG activity from the template into your project. Check it in the IMG and delete it from the Configuration tab because it is not relevant for your process. Choose the Finished pushbutton in the Compare and Adjust dialog box in the Configuration tab, to indicate that no further comparison is required.

3. Repeat these steps until you have checked all new data.



Global Rollout with a Template

Purpose In a global rollout you define one or more templates containing scenarios, Blueprint documents and configuration, at head office.

You can decide which parts of the template are relevant to the subsidiaries, and whether, or to what extent, they can change the template in their rollout projects.

You transport the centrally defined template to the subsidiaries. They use the template in an implementation project to implement solutions, following your guidelines.

Prerequisites You have created a template project in the Project Administration.

You have assigned a transportable package and a transport request of type 'Workbench Request' to this template project.

Process Flow ... ...

Defining a template in the company headquarters 1. You create one or more templates in your template project, in the company

headquarters Project Administration.

2. Set the Global Rollout Functionality is Active flag in the Templates tab in the Project Administration.

This means that the subsidiaries can change structures and business content from this template, within limits, in their local rollout project.

3. Assign values in the structure element Global Attribute column, in the Structure tab in the Business Blueprint, to specify whether each structure element is to be obligatory, changeable, or not changeable for the subsidiaries. For further information about the effects of the attribute value on a structure element at the subsidiaries, see Global Attribute in Global Rollout [page 120].

4. To pass on the Global attribute to the subnodes of a structure element, select it in the Structure tab in the Business Blueprint, and choose Pass On Global Attribute.

To prevent inheritance of the Global attribute, choose the empty row from the possible entries help for the Global Attribute column, at scenario level.

5. Perform the activities required in the Business Blueprint phase, e.g. assign transactions and general documentation.

6. Perform the activities required in the Configuration phase, e.g. assign Business Configuration Sets.

7. If you want to implement the template in subsidiaries which have a different project language from that in the headquarters template project, translate the template [page 121].

8. Deliver the template.

Import the template into the subsidiaries ...

1. Send the objects which you have created in the company headquarters component systems in the Solution Manager, to the subsidiaries’ component systems (see Transport a Template to Another System Landscape in unter Using a Template [page 104]).



2. Send the template to the subsidiaries.

3. Import the template in the subsidiaries (see Importing the Template into the Target Systems in using a template [page 104]).

4. If the template has changed, compare the new version of the template with the project structure and the assigned objects of your target system, and copy the changes if required [page 115].

Result You have centrally created and successfully implemented a template for the uniform configuration of head office and subsidiaries.

Example for a Global Rollout with a Template

Prerequisites The subsidiaries of a company include banks and insurance companies.

Process Flow ...

1. The head office creates the templates ZBANK and ZINS in its template project, and assigns them to the following scenarios:

Template project in the head office

� Customer Service Classic Banking (ZBANK)

� Customer Service Insurances (ZINS)

� Field Service and Dispatching (ZINS)

� Sales Planning Classic Banking (ZBANK)

� Sales Planning Insurances (ZINS)

� MSS: Salary Adaption Planning (ZBANK, ZINS)

The scenario MSS: Salary Adaption Planning is to be implemented identically in all subsidiaries, so both templates are assigned to this scenario.

2. The templates and their objects, e.g. BC Sets and test cases, are imported into the subsidiaries’ systems.

3. The subsidiaries choose the scenarios relevant for them, in their implementation projects, and assign the template which they received from the head office, to it:

a. Implementation project Bank 1 gets template ZBANK



� MSS: Salary Adaption Planning (ZBANK)

b. Implementation project Bank 2 gets template ZBANK



� MSS: Salary Adaption Planning (ZBANK)

c. Implementation project Insurance 1 gets template ZINS

� Customer Service Insurances (ZINS)



� Field Service and Dispatching (ZINS)

� Sales Planning Insurances (ZINS)

� MSS: Salary Adaption Planning (ZINS)

The Global Attribute in Global Rollout The value you give to the global attribute of a structure element can lock it against changes, or allow it to be changed completely or partially by subsidiaries.

The following table shows how the values of the Global attribute (transaction Business Blueprint → Structure tab) which you assign to a structure element in the head office, affect the behavior of the structure element in the subsidiaries.

The F1 help for the Global attribute contains further information about its value.

The Global Attribute in Global Rollout

Global attribute value

Select/deselect structure elements

Structure Change Sequence/ Cut/Paste

General documentation

Project Documentation

Global Not allowed No changes allowed

No changes allowed

Display **) Blueprint-relevant: Display

Not-Blueprint-relevant: Full authorization

**)

Complete Standard

Not allowed Can be enhanced

Same authorization check as in the Structure * tab)

Display Blueprint-relevant: Can be enhanced

Not-Blueprint-relevant: Full authorization

Partial Standard

Allowed Can be enhanced


Display Full authorization

Harmonized Allowed Can be enhanced



Local Allowed Can be enhanced



Initial Allowed Full authorization

Full authorization


*) The system checks the same authorizations as for deleting structure elements from the template, for cut or change the sequence in the structure. You can only delete structure elements with the role Project Leader [page 124] (SAP_SOLAR_PM).



**) When a template is put in a project, the system copies blueprint-relevant documentation from the General Documentation tab to the Project Documentation tab, so that it can be put in the Business Blueprint Document.

The Global Attribute in Global Rollout (Continued)

Global attribute value

Transactions Configuration

Development Test Cases Messages

Global Execute,

Select/Deselect not allowed

Display, Activate

Display, Execute

Can be enhanced

Full authorization

Complete Standard

Can be enhanced Can be enhanced

Can be enhanced

Can be enhanced

Full authorization

Partial Standard

Full authorization Full authorization

Full authorization

Full authorization

Full authorization

Harmonized Full authorization Full authorization

Full authorization

Full authorization

Full authorization

Local Full authorization Full authorization

Full authorization

Full authorization

Full authorization

Initial Full authorization Full authorization

Full authorization

Full authorization

Full authorization

Delete elements from a template Only the Project Leader has full authorization to change and delete elements from the template. You need authorization for authorization object S_PROJ_GEN, with the value GLOB in the field PROJ_FUNC, to delete structure elements from a template. This authorization is in the role Project Leader [page 124] (SAP_SOLAR_PM).

The project team members can delete the following elements from the template:

• Elements with the attribute values Global or Complete Standard:

No element can be deleted from a template.

• Elements with the attribute values Partial Standard, Harmonized or Local:

� You can delete assignments from the template after confirmation prompt.

� Project team members cannot delete structure elements.

Translate a Template

Purpose The project structure and the dokuments in a project are always displayed in the project language, which you specify when you create the project, and can only be changed in this language.

If you create a template in a project language in the company headquarters, and want to to make it available in the subsidiary in another project language, translate it first in the company headquarters, and then deliver it to the subsidiary.



When you translate a template, the translation is only visible in the target language in the target project for which you have specified the target language as the project language, not in the source project. If a document is not available in the desired language, it is displayed in the original language.

The company headquarters creates the source project in the project language English, and translated the templates in it into Japanese.

The Japanese subsidiary creates the target project in the project language Japanese. After the subsidiary has copied the templates into the target project, the templates and their documents are available in the target project in Japanese.

Translation environment Project structure, document name

The project structure, the document name and names of URLs, files, etc. which you have entered in the tabs, are translated in the Translation transaction SE63 [external link].

You can also translate the project structure without document names and names of URLs, in the Business Blueprint (transaction SOLAR01) Goto → Translation.

Knowlege Warehouse documents

Knowlege Warehouse documents are translated with the Knowlege Warehouse translation function [external link] (transaction SI80). The system puts all documents which were created in the General Documentation and Configuration tabs in the source project, in the Knowledge Warehouse in the project context, in the folder SOLAR00. You should create a unique context for each project.

Project structure assignments

You do not need to translate the names of transactions, IMG objects and programs which you have assigned to the project structure. This names and their translations are automatically copied from the component systems when you deliver a template.

Prerequisites • You have created a template.

• You have Set-Up the Translation Environment [external link] in the translation system.

You translate in the system from which you export the collective request with the entire template. This can be a development system, or a consolidation or translation system. All language entries are only transported in this collective request for the template.

Process Flow ...

1. Translate the project structure and document names:

a. To translate the project structure only, select a structure element in the Business Blueprint (transaction SOLAR01) and choose Goto → Translation.

b. To translate the project structure and document, URL and file names:

i. Assign the package or packages in the project to the translator in your translation system [external link].

ii. Generate Worklists [external link] for the packages in the project.

iii. The translator translates [external link] the packages which are assigned to him.



2. The translator translates the Knowlege Warehouse documents [external link] in the project context in the folder SOLAR00.

3. You release the template in the project administration and deliver it.

4. Whenever you change the project structure and/or the documentation in a translated template, in the company headquarters, translate the changes in the company headquarters before delivering to the subsidiaries.

If you have translated the template, you must translate every change, otherwise the changes are not visible in the project language of the subsidiaries.

SAP Solution Manager Roles

Authorization Concept • Project Authorizations [page 123]

The following composite roles contain the authorizations required for the tasks to be performed in a project:

� Project Leader [page 124]

� Application Consultant [page 125]

� Development Consultant [page 126]

� Technical Consultant [page 127]

• Production Authorizations [page 128]

Production authorizations are in individual roles for the functions:

� Solution Directory [page 258]

� Solution Monitoring [page 129]

� Service Data Control Center [external link]

� Service Desk [page 132]

Use Adjust the SAP Solution Manager roles to your requirements.

Project Authorization

Roles The roles in the SAP Solution Manager are composite roles, which contain individual roles, which in turn contain authorizations for individual functions, e.g. for the Business Blueprint.

The following composite roles contain the central authorizations which they require for projects, and can be tailored to suit individual projects:

• Project leaders [page 124] [SAP_SOL_PM_COMP] are responsible for organizing and planning the project, and monitoring costs and deadlines.



• Application consultants [page 125] consultants [SAP_SOL_AC_COMP] are responsible for business content and the documentation of operational activities. This collective role has limited authorization and is intended for project members who need to be adjusted individually.

• Development consultants [page 126] [SAP_SOL_BC_COMP] are responsible for the development of customer-specific programs and authorizations.

• Technical consultants [page 127] [SAP_SOL_TC_COMP] are responsible for installing systems and providing technical support to users.

• Display user/Read only [SAP_SOL_RO_COMP]: contains SAP Solution Manager display/read only authorization.

See also:

• Solution Manager Roles Overview [external link]

• Overview of Roles and Profiles in Satellite Systems [external link]

• SAP Solution Manager 3.2 Configuration Guide

• SAP note 625773 (Roles in the Solution Manager)

• SAP note 803142 (Roles in Satellite Systems)

Project Manager Technical name: SAP_SOL_PM_COMP

Tasks Project managers are responsible for the realization of the desired project results and the daily management of the project. They anticipate deviations from the project direction and carry out the necessary corrective measures immediately. Project managers should also understand the integration of the business processes within the enterprise.

Project managers are also members of the steering committee. They have decision-making authority in matters concerning the program and budget. He forwards strategic questions to the sponsor in order to make joint decisions.

Activities in SAP Solution Manager The main responsibilities of the project manager include:

• Organizing the entire project

• Developing strategies and procedures for an efficient SAP implementation

• Developing and maintaining the time schedule for the implementation project

• Finalizing and managing the project scope, budget and deadlines in accordance with the approved plans

• Assigning and managing resources

• Monitoring project progress on a weekly basis

• Carrying out evaluations and analyses

• Carrying out a formal review at the end of each phase

• Clarifying open issues in good time

• Reporting regularly to the review committee on the progress and status of the project

• Representing the project internally and externally



• Giving status updates to the whole project team

Project managers can also copy content from a ValueSAP Edition 2 project into an SAP Solution Manager project. See the migration tool documentation.

Notes on Tailoring If you require additional authorization, you can use the role SAP_BC_CUS_ADMIN: It contains authorization for the administration of customizing projects in the component systems.

The SAP Solution Manager configuration guide contains further information about authorizations in the component systems.

Integration The project manager defines the content and the time frame of an implementation project, manages resources and monitors project progress. The application consultant reports to him and supports him in an administrative function.

Application Consultant Technical name: SAP_SOL_AC_COMP

Tasks Application consultants are responsible for making sure that the Business Blueprint and software configuration are tailored to the business processes and that analysis and report requirements are fulfilled. They use their knowledge of proven business procedures to support them in these tasks. Application consultants also function as advisers and work closely with the rest of the project team.

They also work in close cooperation with legacy system experts, when extraction of legacy data is necessary.

Activities in SAP Solution Manager

The main responsibilities of the application consultant include:

• Supporting definition and modeling of business processes

• Checking how the business model works with the SAP products

• Configuring the software to suit the required business processes and to meet analysis and report requirements

• Determining the global and local standardization requirements

• Determining requirements for organizational change in the enterprise

• Supporting knowledge transfer to other project team members

• Supporting organization and performance of tests

• Defining requirements for authorization profiles and access authorizations

• Analyzing statistical performance and passing on recommendations for improvement to support

• Creating and developing data solutions and strategies to meet the requirements of the corresponding SAP component (for example, APO, BW, CRM)

• Creating end user training materials for the new functions



The application consultant is not responsible for:

• The technical implementation of the solution

• The programming of interfaces and other developments

• Recurring problems with the quality of data (problems with data quality should be passed on to the project manager)

Notes on Tailoring This role only contains basic functions. The following roles are available for additional authorizations:

• SAP_BC_CUS_CUSTOMIZER contains authorizations for working with IMG activities.

The following role is useful for the application components:

• SAP_BC_CUS_CUSTOMIZER

Integration Application consultants are responsible for the development of business content and the documentation of operative activities in accordance with the appropriate standards. The development consultant develops customer-specific programs and their authorizations.

Development Consultant Technical name: SAP_SOL_BC_COMP

Tasks Development consultants work with the project manager and the application consultant on the planning and organization of the authorization concept. They also perform developmental tasks and customer-specific developments.

Activities in SAP Solution Manager The main responsibilities of the development consultant include:

• Organizing authorizations

• Developing ABAP programs, for example, interfaces, forms, or modifications

• Working with the ABAP Workbench

Notes on Tailoring The following roles are available for additional authorizations:

• SAP_BC_DWB_ABAPDEVELOPER contains authorization for implementing new applications and enhancements and for changing and modifying standard applications using the tools and services provided in the ABAP Workbench.

• SAP_BC_TRANSPORT_ADMINISTRATOR contains all authorizations for the Change and Transport System

Integration Development consultants work for the project manager and the application consultant and carry out programming tasks, in contrast to technical consultants who act as system administrators and are responsible for installing systems and providing technical support to users.



Technical Consultant Technical name: SAP_SOL_TC_COMP

Tasks Technical consultants plan the technical requirements for a project with the project manager and the manager of the technical team and then carry out the required technical tasks in the system.

Depending on the scope and complexity of the implementation, technical consultants may work in several areas, for example, system administration, database administration, network administration, operating system administration, development of cross-application components, or ABAP development.

For international projects, technical consultants also manage consultancy in the following areas:

• Country-specific business requirements and country-specific SAP software requirements

• Language-specific or codepage-specific requirements

• Time-zone issues

Activities in SAP Solution Manager The main responsibilities of the technical consultant include:

• Setting up and installing the system landscape

• Managing the system landscape and the corresponding transport landscape

• Providing support and advice in all technical questions during an implementation project

• Giving daily updates on the technical direction of the project including communicating deviations in the project

• Developing and realizing the Cutover Plan before going live

• Communicating effectively with the business process team

• Transferring knowledge effectively to employees in system administration

In order to be able to carry out these tasks, the technical consultant should meet the following requirements:

• A sound knowledge in the areas of databases, networks, programming and Internet technology

• A sound knowledge of the SAP solutions

Notes on Tailoring The following roles are available for additional authorizations:

• SAP_BC_RRR_SAA_ADMIN provides the authorization for executing all the tasks in the System Administration Assistant.

Integration The technical consultant acts as a system administrator and is responsible for installing systems and providing technical support to users, in contrast to the basis consultant who works under the instruction of the project manager and the application consultant and carries out programming tasks.



Operational Processing Authorizations

Definition The authorization concept for the SAP Solution Manager Operations contains individual roles for specified areas of the SAP Solution Manager Operations. Show specified views of the characteristic tasks in operations.

Use The roles in the SAP Solution Manager Operations are individual roles which contain the authorizations for individual functions and business roles. The individual roles are classified into:

Solution Monitoring [page 129]

Change Request Management [page 344]

Service Data Control Center [external link]

Service Desk [page 132]

Solution Directory [page 128]

sapurl_link_0013_0005_0007

Cf.:

• Solution Manager Roles Overview [external link]

• Overview of Roles and Profiles in Satellite Systems [external link]

• SAP Solution Manager 3.2 Configuration Guide

• SAP note 625773 (Roles in the Solution Manager)

• SAP note 803142 (Roles in Satellite Systems)

Solution Directory Roles Technical name:

• SAP_SOLMAN_DIRECTORY_EDIT

Definition The Solution Directory [page 258] authorization concept contains individual roles which display or edit Solution Directory objects.

Activities Use these individual roles to create, edit or display business process scenarios, business processes, etc., in the Solution Directory:

• Create, Edit, Display: [SAP_SOLMAN_DIRECTORY_EDIT]

Integration Use the individual Solution Monitoring [page 129] role SAP_SV_SOLUTION_MONITORING_DISP to display the Solution Directory and sessions in Solution Monitoring.



Solution Monitoring Roles

Tasks Authorizations specified for the Solution Monitoring in the SAP Solution Manager:

• for the Solution Monitoring sessions, classified by the areas Operations Setup and Operations

Operations Setup

� All sessions in Operations Setup [SAP_SETUP_DSWP]

� Service Level Reporting [page 282] [SAP_SETUP_DSWP_SLR]

� System Monitoring [page 293] [SAP_SETUP_DSWP_SM]

� Central System Administration [page 304] [SAP_SETUP_DSWP_CSA]

� Business Process Monitoring [page 316] [SAP_SETUP_DSWP_SM]

Operations

� All sessions in Operations [SAP_OP_DSWP]

� EarlyWatch Alert [page 276] [SAP_OP_DSWP_EWA]

� Service Level Reporting [SAP_OP_DSWP_SLR]

� System Monitoring [SAP_OP_DSWP_SM]

� Central System Administration [SAP_OP_DSWP_CSA]

� Business Process Monitoring [SAP_OP_DSWP_BPM]

•

• general individual role to display all sessions

� Display all Sessions [SAP_SV_SOLUTION_MANAGER_DISP]

•

• general individual role to edit all sessions

� Edit all Sessions [SAP_SV_SOLUTION_MANAGER]

�

Activities Authorizations are assigned to the roles. Specify user access to the session. The following authorizations are available for your project:

A The user with the role has full authorization for the transaction or session.

D The user with the role can call the transaction or session in display mode.

N The user with the role has no authorization for the transaction or session.

Operations Setup session authorizations



Individual role Service Level Reporting

System Monitoring

Central Administration

Business Process Monitoring

SAP_SETUP_DSWP

A A A A

SAP_SETUP_DSWP_SLR

A N N N

SAP_SETUP_DSWP_SM

N A N N

SAP_SETUP_DSWP_CSA

N N A (1) N

SAP_SETUP_DSWP_BPM

N N N A (2)

Operations session authorizations

Individual role Early Watch Alert

Service Level Reporting

System Monitoring



SAP_OP_DSWP A A A A A

SAP_OP_DSWP_EWA A (3) N N N N

SAP_OP_DSWP_SLR D (4) A N N N

SAP_OP_DSWP_SM N N A N N

SAP_OP_DSWP_CSA N N N A (1) N

SAP_OP_DSWP_BPM N N N N A (2)

Notes:

� (1): You need the authorization object S_SAA_ADMI for the Operations Setup session. With this authorization, you can set-up the Central System Administration.

� (2): Activate the SETUP Business Process Monitoring session customizing, in the business process MONITORING session.

� (3): The role contains authorizations for the SAP Solution Data Manager EarlyWatch Alert.

� (4): The role contains SAP Solution Data Manager display authorizations, to check the data.

SAP_SV_SOLUTION_MANAGER_DISP session authorization

Individual role Early Watch Alert


System Monitoring



SAP_SV_SOLUTION_ MANAGER_DISP

D D D D D



SAP_SV_SOLUTION_MANAGER session authorization

• ndividual role

• arly Watch Alert

• ervice Level Reporting

• ystem Monitoring

• entral Administration

• usiness Process Monitoring

• AP_SV_SOLUTION_ MANAGER

• • • • •

The individual role SAP_SV_SOLUTION_MANAGER_DISP displays areas:

� Change Request Management

� Service Desk

� SAP Solution Data Manager

� Solution Directory (authorization object: AI_SOL_DIR)

The individual role SAP_SV_SOLUTION_MANAGER contains full authorization for the transactions:

� SOLUTION_MANAGER

� SDCCN (SAP Solution Data Manager)

Notes on Tailoring You can use and combine the individual Solution Monitoring roles individually, according to your requirements.

Special authorizations for specific checks in individual sessions, are described in the online documentation of the sessions:

Cf.:

� Set-Up Central System Administration

� Using Business Process Monitoring

Integration If you need authorization for the following areas in addition to SAP Solution Manager Solution Monitoring authorizations:

• Change Request Management

• Service Desk

• SAP Solution Data Manager

• Solution Directory

use the individual roles with the specific authorization.



Service Desk Roles

Tasks The authorization concept for the Service Desk contains roles for specified groups of persons who perform specified tasks.

Activities

Roles

Persons Role Meaning

Administrator SAP_SUPPDESK_ADMIN Configuration of the Service Desk. This role contains the authorizations for the roles:

SAP_SUPPDESK_PROCESS

SAP_SUPPDESK_DISPLAY

SAP_SUPPDESK_CREATE

Message

processor

SAP_SUPPDESK_PROCESS

This role contains the authorizations for the message processing.

Display SAP_SUPPDESK_DISPLAY

This role only displays messages.

Creator of support messages

SAP_SUPPDESK_CREATE

This role allows satellite system and SAP Solution Manager users to create messages.

All users who send messages to the central SAP Solution Manager System via RFC connection, need the authorization object S_RFC.

Business Blueprint

Use This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects [page 134], you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP Systems.

The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.

Integration You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.



• When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.

• You can also display and edit the project documentation from the Business Blueprint phase, during configuration.

• You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.

Prerequisites You have created a project of type implementation, template, or upgrade, in the project administration.

Features Scope of the transaction Business Bueprint

Function Tab

Create a project structure Structure [page 139]

Display the following documentation:

Documentation delivered by SAP, e.g. scenario descriptions

Documentats from templates, e.g. from template projects

To be able to edit general documentation, copy it to the Project Documentation tab.

General Documentation [page 153]

Assign documents to structure elements

Create, Change, Upload user documents

Project Documentation [page 154]

Input administration data, e.g. project status, team members assigned, planned and actual resources

Administration [page 155]

Assign transactions and programs to structure elements

Transactions [page 144]

Create, Display and Edit messages Messages [page 161]

Display and Create a process graphic

Create a process graphic

Graphic [page 162]

Where-used list:

Use in user project

Use in other projects

Go to use by double-click

General Documentation


Transactions

General Functions

Function Navigation

Change the sequence, hide or show tabs Settings → User-Specific



Translate project structure

For further information about translating document names for URLs, in your project, see Translating a Template [page 121]

Goto → Translation

Create/print a Business Blueprint document Business Blueprint → Create Blueprint Document

Assign Document Authorizations [page 46] Assign authorizations in the Role (PFCG) and User Maintenance.

Activities ...

1. Create a Blueprint structure in the Structure tab, using predefined substructures.

2. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.

3. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.

4. Create project documentation to save in the Business Blueprint, in the Project Documentation tab.

5. Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.

6. Print the Business Blueprint document.

7. When the Business Blueprint is complete, you can start to set up the development system landscape.

Result You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.

Business Blueprint in Projects

Definition A Business Blueprint documents the business process requirements of a company. In collaborative business processes, several companies are involved.

Use The Business Blueprint gives you a general idea of how your business processes could be mapped in one or more SAP Systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of an SAP solution implementation.

Structure A Business Blueprint compises the following structure elements in a hierarchy:

• Organizational Units

• Master data

• Business scenarios



• Business processes

• Process steps

You assign content, for example, project documentation, Business Configuration Sets, or transactions to individual structure elements, in the SAP Solution Manager.

You can also create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.

Integration The Business Blueprint is the prerequisite in the Solution Manager for configuration and test organization:

• Configuration:

You configure your business processes with reference to the Business Blueprint project structure. You can also display and edit the project documentation from the Business Blueprint phase.

• Test Organization:

You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions which you assign in Business Blueprint process steps, are put in test plans when you generate them. You can run these transactions as function tests, to test the transactions.

Creating and Printing the Business Blueprint Document

Use Once you have created your Business Blueprint (project structure, documentation, transaction assignments), you can print out the Business Blueprint document for approval or further use.

You can choose between general and project documentation for a template project. You can integrate general documentation into the Business Blueprints, for example to deliver it in a global rollout.

You can only put the project documentation in the Business Blueprint document for the other project types.

Procedure ...

1. Start the Business Blueprint transaction.

2. Select Business Blueprint → Create Blueprint Document.

3. Choose what is to be in the Business Blueprint document, and what is to be printed:

General tab:

� In a template project: General or project documentation

� Scenario or business process graphics (from Graphic tab)

Scope tab

� Selection from project structure



The system only puts structure elements in the Business Blueprint document which you have selected explicitly, or their sub-structure elements. The system selects higher-level structure elements, but does not automatically put them in the Business Blueprint document. Choose them explicitly.

� Selection from documents, e.g. only documents to which you have assigned a keyword

Display Options tab

� Details of structure elements and documents, e.g. document name and person responsible

� Link to reused document or repeated use of it in the same Blueprint document

4. Choose Execute.

5. Your text-processing program starts.

6. You can print the Business Blueprint document with the print function in your text processing program. You can save the document on your local directory with the save function in your text processing program.

7. Close the text-processing program.

You can use the upload function on the Project Documentation [page 154] tab to edit the Business Blueprint document further or publish it for users in the Solution Manager. Set the document to Not Business Blueprint Relevant to ensure that it is not included in the next Business Blueprint document.

Download Project Structure or Roadmap into MS Project

Use You download the project structure or a roadmap into MS Project to plan your project using the data in the project structure or roadmap.

Prerequisites MS Project is installed on your local computer.

You have also created a project structure in the Business Blueprint phase or called a roadmap. You are in the Business Blueprint transaction or the structure view of a roadmap.

You have created at least one structure element with data, at the lowest level, under each structure element in the Business Blueprint, so that the data is displayed correctly in MS Project.

Procedure ...

1. If you are in the Business Blueprint transaction, choose Business Blueprint → Download to MS Project.

If you are in the structure view of a roadmap, choose Roadmap → Download → MS Project Version.



2. Choose a folder for the file, in the following dialog box, and change the file name if required.

3. Save.

4. Confirm the following system message with Continue.

Result The project structure or the roadmap is generated as an .mpx file and displayed in MS Project. You can now save the file in .mpp format and edit it.

Make the following settings in MS Project, so that it displays all required fields after you have downloaded a roadmap or a project structure: ...

1. Define a user display table with View → Table → Other Tables... → New.

2. Create one or more of the following fields for the display table, as required:

Fields generated by SAP

Field Meaning

Unique ID Sequential number in MS Project

Text1 SAP GUID of structure element

Name Name of structure element

Outline Level Outline level of structure element

Priority Priority of structure element

Milestone Milestone flag in the Roadmap

Text2 Status of structure element

% Complete

Baseline Start

Baseline Finish

Baseline Duration

Actual Start

Actual Finish

Actual Duration

Remaining Duration

Resource Names Project Team Members

General Documentation Tab

Use This tab shows documents which were delivered by SAP, or are part of a template, e.g. scenario descriptions. In a template project, you can save documents which you want to reuse in a template in other projects, in this tab.



Specify under Settings → User Specific whether to display the documentation on the General Documentation tab or in a separate window.

You can also specify which data you want to save.

If you choose Save Automatically, data will be saved automatically when you change the structure element.

If you do not select Save Automatically, the data is buffered when you change tabs, but is only saved to the database when you choose Save.

Integration The documents delivered by SAP are stored in the Knowledge Warehouse, which is available to you after installing and seting up the SAP Solution Manager.

Features This tab contains the same functionality for Template projects as the Project Documentation [page 154] tab. Documents in the Gen. Documentation tab are part of the template in the template project, and can, for example, be delivered to subsidiaries, in a Global Rollout [page 118].

The functionality for Implementation projects is limited on this tab. You can display, export, and sort documents. You can copy general documents into your project documentation for editing and use, with Copy to Project Documentation Tab. You can check to which other structure elements a document is assigned with Where-Used List.

The documentation of the default transactions in template and implementation projects is displayed at process step level. (You must have installed the SAP Library to have access to the application help for the transaction in the component systems).

Activities To copy a document from the General Documentation into the Project Documentation tab: ...

1. Choose one or more documents by clicking on their rows.

2. Choose Copy to Project Documentation Tab.

3. Enter a valid documentation type for each document in the following dialog box.

You define the valid documentation types for your project in the Implementation Project Administration transaction on the Project Standards [page 38] tab.

4. Choose Copy. The selected documents are copied to the Project Documentation tab, where you can edit them. Changes made to the copied documents do not affect on the original texts.

Project Documentation Tab

Use You assign project-specific documents to the project structure, and create new project documentation, in this tab.

Documents in the Project Documentation tab are not put in the template in a template project. If you want to deliver documents as part of a template, assign them in the General Documentation tab [page 153].



Integration The documents are saved in the Knowledge Warehouse and are available to you in the SAP Solution Manager. The system puts the documents in the context in the Knowledge Warehouse, which you specified when you created the project.

To put a document in the Business Blueprint document, flag it as 'Blueprint-Relevant' in the documentes attributes. The order in which you create documents determines the order in which they are printed in the Business Blueprint document.

Prerequisites You have added your documentation types to the delivered documentation types, if necessary, in the Project Standards [page 38] tab in the Project Administration.

Features With Insert Document, you can:

• Create new documents

You assign a document type to all documents you create. A document template is called, depending on the document type. You can only use document types that either have a document template or a file name extension supported by the SAP Solution Manager. If a document type has no template or file name extension, the text editor is started.

• Link to documents whose originals are assigned to other structure elements in the Solution Manager.

• Copy documents whose originals are assigned to other structure elements in the SAP Solution Manager, and that you can change independently of the original document.

• Upload a file

• Link to a web site

To delete project documentation or the assignment of documentation to a structure element, choose Delete. For documents created as a link to another document, both the row in the table and the link are deleted. If the document to be deleted is the only instance of this document, the document owner (author) is authorized to delete it.

Choose Where-Used List to find out at which structure elements a document is used. You can also export documents.

With Attributes, you can:

• in the History tab:

� display the change history of a document

� filter by document status

� display the versions of a document

• in the Link tab: link to other documents

Structure Tab

Use In this tab, you can create or change a project structure containing your organizational units, master data, business scenarios, processes, and process steps in a hierarchy.



Integration The project structure is reused by the Configuration and Test Plan Administration functions.

Features In the Structure tab you can:

• Add new organizational units, master data, scenarios, business processes and process steps to the project structure

• Delete structure elements which you defined with the SAP Solution Manager Operations, from a project or solution landscape, or choose them from the Business Process Repository and put them in your project structure

The Business Process Repository is a structured set of all structure elements preconfigured by SAP, that you can reuse.

• Adjust the names of structure element customer-specifically

• Delete structure element which you created, from the project structure

• Move structure elements


Create and Edit Project Structure

Use The project structure displays all of the master data, organizational units, business scenarios, business processes, and process steps belonging to your template. To create a project structure:

• Add new business scenarios, business processes, process steps, master data, and organizational units

• Select predefined business scenarios, business processes, process steps, master data and organizational units, which are delivered by SAP with the Business Process Repository.

• Select processes from a production solution landscape.

Prerequisites You have created a project [page 25] in the Project Administration. If you want to use processes from a production solution landscape which you have created in the SAP Solution Manager Operations, you have selected this solution landscape in the System Landscape [page 30] tab in the Project Administration.

You are in the Business Blueprint transaction.

Procedure

Adding structure elements ... ...

1. Put the cursor on an Organizational Units, Master Data or Business Scenarios structure element.

2. Position the cursor on an empty row in the list displayed for the structure element.

3. Choose the Structure tab [page 139].



4. Specify from where you want to copy existing structure elements into your project, in the possible entries help:

� to select scenarios, processes or process steps already predefined by SAP, choose Business Process Repository under Selection Help.

� to select scenarios, processes or process steps from an existing project, choose Projects under Possible Entries Help .

� to copy processes from a production solution landscape which you have created in the SAP Solution Manager Operations, choose Solution Landscape under Selection Help.

The system only offers the option Solution Landscape in the possible entries help, if you have specified a solution landscape in the Solution Landscape subtab in the System Landscape tab, in the Project Administration.

5. Choose an element from the possible entries help.

If you have chosen a structure element from the Business Process Repository, the system specifies its components. The original name of the structure element is displayed in the Name in Business Process Repository column.

6. If you want to create a new structure element, specify its title. Specify a logical component for master data, organizational units, and process steps.


The system copies the entries into the structure and saves them. The possible entries help selection is saved, and displayed again in the next session.

8. Choose the structure element Business Processes or structure elements of the type Process, and proceed as described in step 1.

Move structure elements...

1. Go to the element in the structure which you want to move.

2. Click on the folder icon in front of the structure element, and move it to the new position by Drag&Drop.

3. Save. ...

Start the Business Blueprint transaction.

Mark a structure element. Drag the marked structure element to the new position in the structure and drop it.


You can also change the sequence in the Structure tab.

Assign templates to the scenarios You must assign a template to a scenario in template projects, to copy the structure of the scenario into the template. Only templates which have been assigned to at least one scenario can be reused later.

1. Select the structure element Business Scenarios in the structure.

2. Choose the Structure tab.

3. Choose one or more templates for the scenarios, from the possible entries help.


The system copies general master data and organizational units, i.e. master data and organizational units at the highest structure level, into all templates assigned in the Structure tab.



The system displays the assigned templates system-wide, in the Template Selection tab in the Project Administration. You can now Reuse these Templates System-Wide, in any Project [page 104].

Assign Global Attribute If you have set the Global Rollout Functionality is Active flag in template projects in the Templates tab in the Project Administration, you can assign values for the Global attribute to the structure elements, in the Structure tab in the Business Blueprint. These values determine whether and how the structure element can be changed when the template is reused. For further information, see The Global Attribute in Global Rollout [page 120] and the Global attribute F1 help.

Result You have created a project structure. You can now:

• Rename structure elements

• Delete structure elements

• Remove structure elements from the scope, by deselecting them in the structure (only implementation projects)

• Assign contents to individual structure elements in your structure, for example documentation and transactions.

See also:Assigning Transactions to a Process Step [page 145]

Project Documentation Tab [page 154]

•

Administration Tab

Use You can use the Administration tab to enter current project data for each structure element in the project structure.

You can record the following project data:

• Status

• Plan data

� Start

� End

� Working Days (in man days - MD)

• Actual data

� Start

� End


� Remaining resources (work required)

• Assigned Project Members



• Name/Description

Data entered only applies for the current project phase.

A structure element in the Business Blueprint phase has the status Completed, after all activities in this phase for this structure element have been completed. The status of this structure element returns to Open in the realization phase.

Integration You can analyze the administrative data for your project for each project phase, in Project Analyses [page 172].

Prerequisites You have checked the status in the project preparation when defining the Project Standards [page 38]. You have entered all employees assigned to the project during Project Preparation [page 22]. The values you have specified are displayed as default values in the Administration tab.

The functions available on the Administration tab depend on the authorizations in the project role assigned to a project member.

Features

Status You can enter the status value manually, or select a value from the proposal list.

Dates You can enter the planned and actual dates manually or select the date from the calendar. An error message appears if you enter dates outside the project period. For further information, see General Data [page 26].

Work resources You must enter the planned, actual and remaining work required manually.

Project team members You can assign the project team members, whom you have put in the project team member list in the Project Team Member [page 29] tab in the Project Administration, to the tasks, in the Business Blueprint and Realization phases.

Keywords You can assign the keywords which you have defined in the Project Standards [page 38] tab in the Project Administration, to the structure elements.

Mass changes Changes to project data is not automatically bequeathed to lower-level structure elements, by default. You can bequeath changes and deletions of project team members and keywords to all lower-level structure elements, with the Mass Changes pushbutton.

Passing data on to subitems This function passes the status and plan data to all subordinate structure elements.



History This function records changes to data on the Administration tab. The change record is logged only after you have saved your changes.

Transactions Tab

Use You can assign transactions, programs and other objects to process steps, in the Transactions tab. This determines the process step for the SAP System.

Integration The selected transactions are proposed as test cases in the SAP Solution Manager test organization, when you generate a test plan.

Prerequisites In order to be able to assign transactions to process steps, you have to Define a System Landscape [page 31] in the project administration transaction.

Features

Assigning transactions, programs, and other objects to a process step and performing it You can assign the following objects to process steps:

• CRM BSP applications

• Transactions

• Programs

If the system exists, you can even assign transactions and programs which do not yet exist. This can be useful if you want to input all information about a project step now, but implement these transactions or programs later. Confirm the assignment confirmation prompt.

• Predefined URLs from directory

You can assign URL objects that you have predefined in the Object Navigator (transaction SE80). For further information, see Including Other Objects [external link].

• Web address or file

• You can insert Internet/Intranet links by entering a descriptive text and the web address. You can also insert URL addresses with variable parts [external link].

Define the value of the variables in Web addresses for your system, under System Administration → Replacing Variables in Web Addresses (URLs), in the SAP Web Application Server customizing.

You can, for example, replace a variable in URLs by the address of your ITS server.



SAP note 541309 explains the meaning of the variables used in the SAP Solution Manager.

• You can change strings in URLs for your entire project, with the program Change URLs in the Solution Manager [page 44], e.g. because the fileserver has moved and you now want to change the directory name or fileserver in all affected URLs.

You can specify a file name if the browser you are using supports the application.

You can start or open existing transactions, programs or other objects, in a new session, by double-click.

You can call the online documentation of transactions and programs in the SAP Library.

Setting transactions, programs, and other objects in or out of scope To put an object in the project scope, select the checkbox in the In Scope column. Deselect the checkbox in the In Scope column, to remove transactions that are no longer required, from the project scope.

Specify a default transaction You can specify the object whose function is to be performed when you choose the Execute symbol for a process step, by setting the checkbox in the Default column. If you do not set a default, the Execute symbol will start the first object in the list on the tab.

Template The Template flag indicates that an object is in a Template [page 104] which is reused in your project. The flag is not set for items you have added in your implementation project.

Assigning Transactions to a Structure Element

Use You can assign transactions, programs, or other objects to a structure element, in the Transactions tab. This enables you to access and execute these transactions, programs, and objects. These are also the default objects when you create a test plan in the realization phase.

You can also assign a default transaction for a structure element on the Transactions tab. To call the default transaction, choose the Execute symbol next to the structure element in the reference structure.

Prerequisites You are in the Business Blueprint or Realization transaction.

Procedure ... ...

1. Put the cursor on a scenario, process or process step.

2. Choose the Transactions tab.

3. Choose Transaction or Program in the Type column.

4. Enter the transaction or program ID in the Object column.

The system automatically fills the Name, Type and Logical Component fields.



If the system does not automatically enter a name for the assignment, and <Name Not Found> is in the Name column, call the insertion of assignment names manually:

Choose Environment → Refresh Assignment Texts.

When the system has refreshed the assignment texts, it opens a new session and displays a log.

5. If you have chosen the type Web address or file, enter a descriptive text and an object name, for example a file name or URL.

6. If you have chosen the type predefined URL, choose a URL in the following dialog box.

7. Enter further objects if required.

8. Select a default transaction.

This determines which transaction runs when you choose the Execute icon next to the process step title in the reference structure.


The newly-assigned object is automatically put in the project scope, i.e. the checkbox in the In Scope column is selected.

Messages Tab

Use You can create and display messages on the Messages tab. Create a message if you encounter errors in the project documentation, configuration, or processing of test cases in the Business Blueprint [page 132] or Configuration [page 150] transactions.

Integration If a basis system is set-up as the message system for your Solution Manager, process messages for which you are the processor, with the transaction DNOTIFWL.

If a basis system is set-up as the message system for your Solution Manager, process messages with the Service Desk [page 337].

You can search for or process messages in the SAP Solution Manager project analysis. Project analysis allows you to search for and process Messages [page 189].

Features You can:

• Display or change messages

• Create messages

• Attach documents to messages

The message will be forwarded to your message collection system and processed.



You can adjust the possible entries help for the Component field in a message, to your requirements, in customizing. Choose SAP Solution Manager → Define SAP Solution Manager Message Types in SAP Solution Manager customizing, and add new components in the existing message type slf1.

Create Message

Use You create a message to document problems which occurred when creating the Business Blueprint or in the Configuration.

Prerequisites You have called the Business Blueprint [page 132] or Configuration [page 150] transaction.

Procedure ...

1. Go to the structure element in the project structure for which you want to create or change a message.

2. Choose the Messages tab.

The system displays a list of all existing messages.

3. Choose the Create pushbutton.

The system displays a dialog window in which you can enter your data.

4. Enter a component, a priority, a processor, a short text and a message text. Use the user names in the SAP System for the processor.

You can adjust the possible entries help for the Component field to your requirements, in customizing. Choose SAP Solution Manager → Define SAP Solution Manager Message Types in SAP Solution Manager customizing, and add new components in the existing message type slf1.

5. You can also select a component from the application hierarchy, under SAP Components.

You can use the component later to sort your messages, or convert the message into a message to SAP.

6. If you want to add a file to the message, choose the Attachments tab, and upload a file.


Result You have created a message. The message can now be processed in the message processing system.

You can change existing messages by choosing Display in the Message tab, and switching to change mode in the following dialog screen.



Graphic Tab

Use You can display a graphic in the Graphic tab at scenario and process level, which answers the following questions visually:

• Which processes comprise the scenario, or which process steps comprise the process?

• In which logical components do the processes or process steps run?

• Which non-SAP products can be used?

• What dependencies are there between the processes or process steps (predecessor-successor relationships)?

• Which business partners are involved in the scenario or process?

• Which transactions, documentation, configuration objects or messages are assigned to the scenario, process or process step?

Prerequisites • Local availibility of Internet Explorer (5.5 or higher).

• ActiveX controls are active in your browser.

• To change the process graphic, you are in the Graphic tab in the Business Blueprint project phase. In the Configuration project phase, the graphic is display only.

• To display transactions, messages, configuration objects and documentation, activate the appropriate settings under Icons in Component View under Settings → User-Specific.

Features • Display process graphic

• Create a Process Graphic [page 148]

• Export process graphic to Micrrosoft Word or Powerpoint

• Navigation in the graphic:

� Top down: From scenarios to processes by double-click on an element in the text box

� Bottom up: From processes to scenarios with the One Level Higher arrow

• Display transactions, messages, configuration objects and documentation (project documentation and general documentation) in the graphic, and go to the document by mouse click.

Create Scenario/Process Graphic

Use The system shows processes, process steps and their components as process or scenario graphics, in the Graphic tab. You can adjust these graphics to your requirements, to show the actual process flow in your company.



Prerequisites You have created a project structure in the Business Blueprint.

Procedure To call the functions in the following table, choose the transaction Business Blueprint.

Create new graphic elements


Create business partner Goto → Graphic Elements → Business Partner tab → New Entry

Create free components Goto → Graphic Elements → Free Components tab → New Entry

Enter numbers from 000-255 (RGB color values) in the Colors box, to specify the color of the free components.

Transport business partners and free components into other systems

Goto → Graphic Elements → Put Elements in Transport Request

To call the functions in the following table, choose the transaction Business Blueprint.

Create Graphic


Insert Business Partner Context menu outside another element → Insert Business Partner

Insert Components Context menu in a business process or outside another element → Insert Free Components

The system puts components, processes and process steps in the project structure

Insert Free Components, e.g. for non-SAP applications

Context menu in a business process or outside another element → Insert Free Components

Insert Process Steps Context menu in a component → Insert Process Step

Insert Free Elements, e.g. for process steps, to improve the legibility of the graphic

Context menu → Insert Free Element

The system only shows free elements in the graphic, and does not put them in die project structure.

Delete graphic element ...

Select the graphic element.

Choose Delete in the context menu.

Move graphic element Drag & Drop

Change font type and size → Attributes

Change height of a component lane

Select the element and drag the component lane to the new height, with the left-hand



mouse key pressed.

Change the size of a graphic element

...

Select the graphic element.

Position the cursor in a square.

Drag the square to the new size, with the left-hand mouse key pressed.

Create connecting lines for process (step)

In the context menu of the source element (process or process step) → Create Line (Synchronous/Asynchronous) → In the context menu of the target element → Draw Line

or

Drag the yellow dot (the start of a line) to the target element, with the left-hand mouse key pressed

Scenario/Process flow

Synchronous:

The previous process(step) waits for the end of the following process(step)

Asynchronous:

The related process steps run consecutively.

Change position, e.g. center Context menu of a graphic element → Attributes

Result You can print the graphic with a pushbutton in the Graphic tab, or export it to Microsoft Powerpoint or Word.

Configuration

Use This project step configures the process requirements specified in the Business Blueprint phase, in the system.

If you use objects from the Business Process Repository in your structures, they may already be assigned to transactions and BC Sets. If you create structures without Business Process Repository objects, you can assign transactions in the Business Blueprint transaction. You can assign BC Sets, IMG objects and test cases in the Configuration transaction.

Prerequisites You have selected scenarios and processes, or created your own processes using the Business Process Repository, in the Business Blueprint phase.

You are now in the Realization phase and have called the Configuration transaction.

Features This project task comprises the following steps:

• Assign Transactions/Programs [page 145]

You can call assigned transactions, add new ones or remove superfluous ones from the project scope, in the Transactions tab.

• Assign/Edit BC Sets [page 157]



You can assign BC Sets to project steps, display the contents of the assigned BC Sets and delete superfluous BC Sets from the project scope, in the Configuration tab.

You can activate one BC Set or all BC Sets assigned to a process.

You can create new BC Sets for project or company-specific settings, which you e.g. want to use in a group rollout or to create your own solution, in the application system, and assign them in the Solution Manager.

• Assign/Edit IMG [page 157]

You can assign IMG objects to the project steps. You can display and edit these settings, and the settings made by BC Sets, in the IMG.

• Edit Test Cases [page 160]

You can make initial function tests after the configuration. You can also run CATTs to see how a transaction works. You can also create test cases.

• You document the settings relevant for the configuration along the project structure, in the Project Documentation [page 154] tab or in the IMG.

• Create/change problem messages in the Messages Tab [page 161]

Activities ...

1. Cross-Scenario Configuration [page 151]:

a. Create a configuration structure for the basic settings of your solutions, e.g. for SAP CRM 3.1, under Configuration in the business process structure.

b. Configure these basic settings.

2. Configure your business scenarios under Business Scenarios in the business process structure, e.g. for the scenario E-Selling.

Edit Cross-Scenario Configuration

Use You make the cross-process basic settings for a solution in the cross-scenario configuration, before you implement scenarios for it.

Integration You first make the cross-scenario configuration under Configuration in the business process structure, in the transaction configuration (SOLAR02). Then make the scenario and process-specific configuration under Business Scenarios in the business process structure.

Features • Selection of existing configuration structures from the Business Process Repository

(repository of scenarios and business processes delivered by SAP)

• Create a configuration structure

• Change configuration elements

• Assign objects to the configuration elements, e.g. IMG objects and documents

• Perform cross-scenario configuration for your solutions

• Print the configuration structures, including assigned documents, as configuration guide



Activities 3. Call the transaction Configuration (SOLAR02) and go to your project.

4. Select Configuration in the business process structure.

5. Choose Change Configuration Structure in the Strukture tab.

6. Create the configuration structure:

� To copy an existing configuration structure from the Business Process Repository, choose configuration elements in the Configuration Element column in the possible entries help.

Filter

• You can filter the configuration structures in the configuration structure selection possible entries help, by the industries selected in the Industry Selection subtab in the Scope tab in the Project Administration.

• You can filter the configuration structures by the scenarios selected under Edit → Recalculate Scope, in the Business Blueprint

� To create your own configuration structure, enter a name for the configuration element in the Configuration Element column. Configuration structures can have any number of levels.

7. Assign logical components to the configuration structures in the following dialog box.

8. You can change the configuration structures and elements.

9. Go Back.

10. Assign objects, e.g. IMG objects to the configuration structures.

11. To lock the configuration elements for dependent implementation projects in a template project against changes, assign values for the global attribute to the configuration elements, in the Structure tab.

12. You can create a configuration guide document for the configuration structure with Configuration → Config. Guide.

13. Perform the cross-scenario configuration.

Create/Print Configuration Guide ...

1. Start the Configuration transaction.

2. Choose Configuration → Create Configuration Guide.

3. Choose what is to be in the configuration guide:

� Selection from project structure

The system only puts structure elements in the configuration guide which you have selected explicitly, or their sub-structure elements. The system selects higher-level structure elements, but does not automatically put them in the configuration guide. Choose them explicitly.

� Selection from documents, e.g. only documents to which you have assigned a keyword



� Display options: You can, for example, decide whether the IMG documentation is to be included.

4. Choose Execute.

5. Your text-processing program starts.

6. Print or save the configuration guide locally in your text processing program.

7. Close the text-processing program.

You can now upload the configuration guide to the Project Documentation tab.

General Documentation Tab

Use This tab shows documents which were delivered by SAP, or are part of a template, e.g. scenario descriptions. In a template project, you can save documents which you want to reuse in a template in other projects, in this tab.

Specify under Settings → User Specific whether to display the documentation on the General Documentation tab or in a separate window.

You can also specify which data you want to save.

If you choose Save Automatically, data will be saved automatically when you change the structure element.

If you do not select Save Automatically, the data is buffered when you change tabs, but is only saved to the database when you choose Save.

Integration The documents delivered by SAP are stored in the Knowledge Warehouse, which is available to you after installing and seting up the SAP Solution Manager.

Features This tab contains the same functionality for Template projects as the Project Documentation [page 154] tab. Documents in the Gen. Documentation tab are part of the template in the template project, and can, for example, be delivered to subsidiaries, in a Global Rollout [page 118].

The functionality for Implementation projects is limited on this tab. You can display, export, and sort documents. You can copy general documents into your project documentation for editing and use, with Copy to Project Documentation Tab. You can check to which other structure elements a document is assigned with Where-Used List.

The documentation of the default transactions in template and implementation projects is displayed at process step level. (You must have installed the SAP Library to have access to the application help for the transaction in the component systems).

Activities To copy a document from the General Documentation into the Project Documentation tab: ...

1. Choose one or more documents by clicking on their rows.

2. Choose Copy to Project Documentation Tab.

3. Enter a valid documentation type for each document in the following dialog box.



You define the valid documentation types for your project in the Implementation Project Administration transaction on the Project Standards [page 38] tab.

4. Choose Copy. The selected documents are copied to the Project Documentation tab, where you can edit them. Changes made to the copied documents do not affect on the original texts.

Project Documentation Tab

Use You assign project-specific documents to the project structure, and create new project documentation, in this tab.

Documents in the Project Documentation tab are not put in the template in a template project. If you want to deliver documents as part of a template, assign them in the General Documentation tab [page 153].

Integration The documents are saved in the Knowledge Warehouse and are available to you in the SAP Solution Manager. The system puts the documents in the context in the Knowledge Warehouse, which you specified when you created the project.

To put a document in the Business Blueprint document, flag it as 'Blueprint-Relevant' in the documentes attributes. The order in which you create documents determines the order in which they are printed in the Business Blueprint document.

Prerequisites You have added your documentation types to the delivered documentation types, if necessary, in the Project Standards [page 38] tab in the Project Administration.

Features With Insert Document, you can:

• Create new documents

You assign a document type to all documents you create. A document template is called, depending on the document type. You can only use document types that either have a document template or a file name extension supported by the SAP Solution Manager. If a document type has no template or file name extension, the text editor is started.

• Link to documents whose originals are assigned to other structure elements in the Solution Manager.

• Copy documents whose originals are assigned to other structure elements in the SAP Solution Manager, and that you can change independently of the original document.

• Upload a file

• Link to a web site

To delete project documentation or the assignment of documentation to a structure element, choose Delete. For documents created as a link to another document, both the row in the table and the link are deleted. If the document to be deleted is the only instance of this document, the document owner (author) is authorized to delete it.

Choose Where-Used List to find out at which structure elements a document is used. You can also export documents.

With Attributes, you can:



• in the History tab:

� display the change history of a document

� filter by document status

� display the versions of a document

• in the Link tab: link to other documents

Administration Tab

Use You can use the Administration tab to enter current project data for each structure element in the project structure.

You can record the following project data:

• Status

• Plan data

� Start

� End


• Actual data

� Start

� End


� Remaining resources (work required)

• Assigned Project Members

• Name/Description

Data entered only applies for the current project phase.

A structure element in the Business Blueprint phase has the status Completed, after all activities in this phase for this structure element have been completed. The status of this structure element returns to Open in the realization phase.

Integration You can analyze the administrative data for your project for each project phase, in Project Analyses [page 172].

Prerequisites You have checked the status in the project preparation when defining the Project Standards [page 38]. You have entered all employees assigned to the project during Project Preparation [page 22]. The values you have specified are displayed as default values in the Administration tab.

The functions available on the Administration tab depend on the authorizations in the project role assigned to a project member.



Features

Status You can enter the status value manually, or select a value from the proposal list.

Dates You can enter the planned and actual dates manually or select the date from the calendar. An error message appears if you enter dates outside the project period. For further information, see General Data [page 26].

Work resources You must enter the planned, actual and remaining work required manually.

Project team members You can assign the project team members, whom you have put in the project team member list in the Project Team Member [page 29] tab in the Project Administration, to the tasks, in the Business Blueprint and Realization phases.

Keywords You can assign the keywords which you have defined in the Project Standards [page 38] tab in the Project Administration, to the structure elements.

Mass changes Changes to project data is not automatically bequeathed to lower-level structure elements, by default. You can bequeath changes and deletions of project team members and keywords to all lower-level structure elements, with the Mass Changes pushbutton.

Passing data on to subitems This function passes the status and plan data to all subordinate structure elements.

History This function records changes to data on the Administration tab. The change record is logged only after you have saved your changes.

Configuration Tab

Use You can access the various customizing tools to make system settings or store preconfiguration, from the Configuration tab.

You can create project templates and enhance them with preconfiguration and your own documentation.

Integration The Configuration tab is the central starting point for making system settings for your implementation project. You can go to the transactions for editing BC Sets or importing Add-Ons, the Implementation Guide, and CATT and eCATT maintenance. You can also enter all transactions and programs here, which you need to configure the solution in your project.



Prerequisites You have created a project [page 25] and defined a system landscape [page 31] for the project in the Project Administration transaction. You have created project IMGs and transport requests in the system landscape component systems [page 35], in the Project Administration.

You have created a scenario structure for your project in the Business Blueprint [page 132] transaction.

Features • You can create new BC Sets, assign them to the structure, view the contents of the

assigned BC Sets, and delete the assignments of BC Sets that are no longer required, from the project, in the application systems.

• You can activate one or more assigned BC Sets. The status of activated BC Sets is shown in the tab. You can view the activation log.

• You can display and edit the settings in the application system Implementation Guide (IMG). You can also assign IMG activities to structure elements.

• You can assign CATTs and eCATT configurations to structure elements, and call them. You can record settings and import preconfiguration with CATT and eCATT functions.

• You can create and run eCATTS. The execution status of the eCATTS is displayed in the tab. You can view the error logs.

• You can assign transactions and programs which you need to configure your application systems, to structure elements, and call them.

• You can call the online documentation of transactions and programs in the SAP Library.

• You can document individual configuration steps. You can assign existing documentation and create new documentation.

• You can also import customizing contained in the Add-On transports into your system.

• You can specify the processing status and the person responsible for each object that you have assigned.

Configure

Use You want configure the component systems in your system landscape by:

• importing BC Sets, CATTs and eCATT test configurations

• editing IMG activities

• importing Add-On transport requests

• running transactions or programs (reports).

Prerequisites You have called the Configuration transaction and chosen the Configuration tab. If you want to import and transport preconfiguration, you have created a sustomizing request and a workbench request in the Project Administration of the systems.



Procedure

Import preconfiguration into component systems

Activate BC Sets ...

1. To activate a BC Set, choose Configure on the Configuration tab. You can activate several BC Sets in different component systems at the same time.

2. Choose Start Data Transfer in the Data Comparison and Transfer dialog box.

The Status field shows the current status of the BC Set activation. The system logs the BC Set activation.

Release transport request ...

1. To release transport requests, select the transport request in the Configuration tab and choose Configure. You go to the Add-On Installation Tool transaction. When you have imported the Add-Ons, their customizing content is written into the workbench request subsequent for further transport.

2. Choose Back to return to the Configuration tab.

See SAP Add-On Installation Tool [external link] for further information.

ConfigurnCATT and eCATT test ...

To configure a CATT or eCATT test, choose Configure on the Configuration tab. After configurng CATT and eCATT tests, the system displays the log. You can configure several CATT or eCATT tests per component system at the same time.

Edit IMG object ...

1. To edit an IMG object, double-click on the Object column.

You go to Execute Project in the component system Implementation Guide (IMG). You can now examine and modify configuration imported by activating the BC Sets.

2. Edit the IMG activity.

3. Save the status and the documentation of your customizing settings.

4. Save your entries and choose Back to return to the Configuration tab.

See Assign IMG Documentation [external link] for further information.

Edit documentation ...

1. Choose Document in the Type field.

2. Enter the document title and select the documentation type and source for the document, in the Add Object dialog box.

You can link to or copy an existing Solution Manager document, upload a local document, or link to a URL.

3. To create a document, specify its title and type. The system starts the editor in a new window.

4. You can change the status or the person responsible for a document with Attributes.

See the Project Documentation [page 154] tab for more information.

Display/change administration information • Choose the person responsible for a configuration step from the possible entries help

for the Person Responsible field. The system displays the list of project team members whom you specified in the Project Administration [page 25].



• To change the processing status of a configuration step, call the possible entries help for the Processing Status field. The system displays the list of the statuses which you specified in the Project Administration [page 25].

Insert rows To insert rows, select a row and choose Insert Several Rows. The system moves the row above the selected one upwards, and hides all other rows. This table rows are not deleted. To show the hidden table rows, choose Enter.

Insert assignment names The system usually inserts a name for assignments to a structure element, e.g. for transactions and IMG objects, automatically.

If the system does not automatically enter a name for the assignment, and <Name Not Found> is in the Name column, call the insertion of assignment names manually:

Choose Environment → Refresh Assignment Texts.

When the system has refreshed the assignment texts, it opens a new session and displays a log.

Result You have made system settings for your implementation project.

You can test your settings in the Test Cases [page 160] tab or plan and perform larger tests using the Test Workbench [external link].

See also:

Create and Assign Preconfiguration [page 111]

Development Tab

Use You can put your own developments and modifications in your implementation project for central access, in the Development tab. You specify the developments and modifications which you have made in your implementation project.

Prerequisites You have created a project in the Project Administration [page 22] and defined its System Landscape [page 60].

You have created a scenario structure for your project in the Business Blueprint [page 134] transaction.

You have authorization for the authorization object AI_SA_TAB. The fields must have the following values: Tab in SAP Solution Manager (Tabname) = DEV, Activity (ACTVT) = 02.

Features • You can assign packages, programs, transactions, Internet services, BSP applications

and BSP extensions to the structure elements.

• You can go to workbench objects (packages, programs, transactions, Internet services, BSP applications and BSP extensions) in the satellite systems.



• You can assign transport requests to the structure elements in the Development tab, for example to to put the modifications in a transport request into your implementation project. You can go to the transport requests in the satellite systems.

• You can specify the processing status and the person responsible for an assignment.

Example ...

1. You have modified a customizing object so that current settings are possible in your system, and written this change into a transport request.

2. You assign this transport request in the Development tab, to document the modification.

3. If this modification is overwritten by importing a Support Package, repeat the modification with the assigned transport request.

Test Cases Tab

Use You can assign test cases, scenarios, processs or process steps, in this tab. The test cases assigned here can be the default values for a project when you Create Test Plans [page 249].

Features

Assign new or existing test cases to a scenario structure In this tab you assign test cases, scenarios, processs or process steps, which you want to use later for a process-oriented test. You can assign existing test cases or create new ones. You can create, change and display the following test case types:

• Manual test cases, e.g. MS Word documents, web links (URL).

You have the same options as in the Project Documentation [page 154] tab.

You can assign the following test case description attributes:

• Display the test case description change history in the History tab

• Link to other existing documents which belong to the test case description, in the Links tab

• Manual test cases in SAPscript

• External applications, e.g. third-party test tools with certified interface

• Automatic test cases of type CATT or eCATT test configuration

• Function module tests

You can use a where-used list to see to which structure element a test case is assigned. Proceed analogously to Create Where-Used List in the Transactions [external link] tab.

Saving test cases For test cases of type CATT, or function module tests, choose a component: These test cases are then saved in the associated component system.



You can also save manual test cases in SAPscript, external applications or eCATT test configurations in a central system, instead of a component system. You define systems for such "central objects" [page 34] in the Project administration [page 22]. If such a central system is defined, choose no components in the Test Cases tab. The test cases are automatically saved in the central system.

Manual test cases in MS Word format are saved in the Solution Manager Knowledge Warehouse.

Link manual test cases to a transaction or a program If a manual test case describes testing a transaction or a program, you can link it to the diesen link it to the transaction [page 161]. The tester can then read the test case description and call the transaction directly from his worklist, in the Test [external link] transaction.

Other functions • You can display the descriptions of test cases and run automatic test cases of type

CATT and eCATT, individually or collectively.

• You can display the test case error logs.

For further information about creating test cases and the Test Workbench, see the Test Workbench [external link] component in the SAP Library.

Link Manual Test Case to Transactions/Reports ...

1. Assign transactions or reports to the project structure, in the Transactions tab in the Configuration transaction.

2. Create a manual test case in the Test Cases tab.

3. Choose a transaction or report for this manual test case, from the possible entries help for the Test Object column.

The system shows you the transactions or reports which you have assigned in the Transactions tab.


Messages Tab

Use You can create and display messages on the Messages tab. Create a message if you encounter errors in the project documentation, configuration, or processing of test cases in the Business Blueprint [page 132] or Configuration [page 150] transactions.

Integration If a basis system is set-up as the message system for your Solution Manager, process messages for which you are the processor, with the transaction DNOTIFWL.

If a basis system is set-up as the message system for your Solution Manager, process messages with the Service Desk [page 337].



You can search for or process messages in the SAP Solution Manager project analysis. Project analysis allows you to search for and process Messages [page 189].

Features You can:

• Display or change messages

• Create messages

• Attach documents to messages

The message will be forwarded to your message collection system and processed.

You can adjust the possible entries help for the Component field in a message, to your requirements, in customizing. Choose SAP Solution Manager → Define SAP Solution Manager Message Types in SAP Solution Manager customizing, and add new components in the existing message type slf1.

Graphic Tab

Use You can display a graphic in the Graphic tab at scenario and process level, which answers the following questions visually:

• Which processes comprise the scenario, or which process steps comprise the process?

• In which logical components do the processes or process steps run?

• Which non-SAP products can be used?

• What dependencies are there between the processes or process steps (predecessor-successor relationships)?

• Which business partners are involved in the scenario or process?

• Which transactions, documentation, configuration objects or messages are assigned to the scenario, process or process step?


• ActiveX controls are active in your browser.

• To change the process graphic, you are in the Graphic tab in the Business Blueprint project phase. In the Configuration project phase, the graphic is display only.

• To display transactions, messages, configuration objects and documentation, activate the appropriate settings under Icons in Component View under Settings → User-Specific.

Features • Display process graphic

• Create a Process Graphic [page 148]



• Export process graphic to Micrrosoft Word or Powerpoint

• Navigation in the graphic:

� Top down: From scenarios to processes by double-click on an element in the text box

� Bottom up: From processes to scenarios with the One Level Higher arrow

• Display transactions, messages, configuration objects and documentation (project documentation and general documentation) in the graphic, and go to the document by mouse click.

Creating Training Material and Learning Maps

Purpose When new solutions and functions are implemented, the end users must be trained in the new functions which they will use. You generate learning maps for the end user tasks, e.g. for the new functions which the purchaser in your company will use, with the Solution Manager, from the existing project structure. A learning map is the structured table of contents of a computer-supported self-learning training course, which presents brief information about the learning units, and links to the training material, in HTML format. You can put E-Learning materials, e.g. SAP Tutors, in the self-learning courses.

Prerequisites You have created a project structure in the Business Blueprint phase.

You have authorization for the transaction Configuration or the role Application Consultant or Project Leader.

There is a link, via which you can order a free, unrestricted license for the SAP Tutor and access to Best Practice documents for end user training, under Operations → Software Change Management → Upgrade → Best Practice Documents, in the transaction SOLUTION_MANAGER.

Process Flow ...

1. If there is no appropriate role, define roles [page 164] for the user groups to whom you want to send the learning maps later, e.g. purchaser or accountant.

2. During the realization phase, you assign training material to the structure elements, in the transaction Configuration in your project [page 167], e.g. E-Learning material such as SAPTutors, presentations or test cases.

3. Assign these roles to the structure elements, in the transaction Configuration, to be able to filter the project structure by user groups (roles), for which specified training units are relevant.

4. After testing your project, create learning units from the project structure and its assigned learning material, and generate Learning Maps [page 168] in HTML format for the various user groups (roles) outof it, in the transaction Learning Maps Management.

5. Send [page 170] a link to the learning map to the end user.

6. The end users work through the learning units on their own.

7. The end users assess the learning units and the learning map.

8. Analyze the end user assessments.



Result You can download the learning map from the Solution Manager, to edit it with other tools, or publish it.

Create End User Roles

Use You want to send the learning map to a group of users with the same business role, e.g. to all accountants in your company, or to the purchasing department. The Solution Manager uses the end user business roles Job [external link] and Organizational Unit [external link] from HR. If these business roles are not defined, create them.

• The Solution Manager uses the following HR organization model object types:

• Position

• Organizational unit

• Position

• User

A user, e.g. the SAP user MAYER is usually assigned to a position, e.g. the position "Marketing Department Leader". The position can be assigned to an organizational unit (e.g. "Marketing") or a job ("Department Leader"). You maintain the HR organization model objects and their links to each other, with the transaction Maintain Objects (PP01).

• The Solution Manager uses the current plan version, i.e. the currently valid organizational structure of your company.

• The CRM organizational units are the same as HR.

Prerequisites You need authorization for the authorization object PLOGU, to be able to create roles. For further information, see Web Application Server → Business Management → Organizational Plan → Organizational Management, in the SAP Library.

Procedure

If you have a central HR system, you should create the roles there and distribute them into the Solution Manager system. For further information, see Distributing the HR Org. Model [external link].

...

1. Create a job, e.g. Department Leader.

See Create HR-Org. Object [page 165] for further information.

2. Create a position, e.g. Marketing Department Leader.

3. To assign the job to the position, Create a link between the two objects [page 166], e.g. position „Department Leader“ describes the job „Marketing Department Leader“.

4. You can create an organizational unit, e.g. Worldwide Marketing.



5. Assign positions to the organizational unit, e.g. „Marketing Department Leader“ leads the organizational unit „Worldwide Marketing“.

6. Assign users to the position or the organizational unit [page 166].

The learning map is later sent to the E-Mail address in the address data of these users.

7. Distribute the HR-Org. Objects [external link] into your Solution Manager system.

If the predefined HR-Org. object types, e.g. position, and info types, e.g. links, are not sufficient, you can also Create HR-Org. Object Types and Info Types [page 165].

Result You can now create your project structure and assign [page 167] organizational units as end user roles, in the Configuration transaction in the Solution Manager.

Create HR-Org. Object and Info Types

Use If the predefined HR-Org. object types, e.g. position, and info types, e.g. links, are not sufficient, you can also create object and info types.

Procedure 8. Create HR-Org object types in the transaction OOOT.

9. Create info types in the transaction OOIT.

For further information, see Personnel Management → Organization Management → Basic Settings → Enhanced Data Modelling, in the HR IMG, and Organizational Management [external link]

Create HR-Org. Object ...

1. Choose Environment → Maintain Organizational Units, in the transaction Configuration (SOLAR02).

You go to the transaction Maintain Objects (PP01).

2. Choose the object type.

3. Delete the object ID if it has a value.

4. Check the object validity period.

5. Choose the info type Object in the Active tab.

6. Choose Create.

7. Enter an abbreviation and a description in the following screen.




Link Two HR-Org Objects ...

1. Choose an object type in the transaction Maintain Objects (PP01).

2. Delete the object ID if it has a value.

3. Select the info type Links.

4. Choose Create.

5. Choose the Type of the Linked Object.

6. Choose the ID of the Linked Object.

7. Choose the Link Type/Link.


You can also create links between HR-Org. objects in the transaction Change Structure (PPSM). You can:

• Analysis path OFFICE

The analysis path determines which links between objects are analyzed. If the analysis path OFFICE exists, the Solution Manager uses it by default to send a learning map, to determine the users assigned to an HR-Org. object.

• New analysis path

• To specify a new analysis, create the new analysis path in the customizing transaction OOAW. To hide links between objects in the HR-Org. model structure display, which do not interest you, set the Skip flag.

• To use the new analysis path in the Solution Manager, put it in the table SAROLECUST in the Solution Manager system.

• You can display the analysis path as a graphic, in the transaction PPSM.

For further information, see Personnel Management → Organization Management → Basic Settings → Enhanced Data Modelling, in the HR IMG, and the HR Organizational Management online documentation.

Assign User to an HR Org. Object ...

1. Choose the HR Org. object to which you want to assign a user, e.g. the position "Accountant" in transaction PP01.

2. Choose the info type Links in the Active tab.

3. Choose Create.

4. Choose the link type, e.g. A 008 (Occupant) for the position "Accountant".

5. Choose User as the type of the linked object.

6. Choose the user name as the ID of the linked object.




Alternatively, you can also edit existing HR Org. objects in the transaction Change Organization and Occupant (PPOME).

...

Create Learning Material

Use You create new learning material, or assign existing learning material to your project structure, to generate a learning map from the project structure.

Prerequisites You are in the Configuration (SOLAR02) transaction in your project.

Procedure ...

1. Go to the Learning Material tab.

2. Select a structure element.

3. Proceed as described in Project Documentation Tab [page 154]. You have the same options in the Learning Material as in the Project Documentation [page 154] tab. You can also:

� Create and assign SAP Tutors

� Specify document details which are displayed in the learning map:

i. Specify the time required to work through a learning unit, in the Time Required in Min. field in the Document tab in the learning materials attributes.

ii. Specify the contents of the learning learning materials attributes in the Comment tab.


Result You have created learning material for your project. Now Assign End User Roles to the Project Structure [page 167].

Assign End User Roles

Use To be able to filter the training material by user groups for whom certain topics are relevant, when you create a learning map, assign these user groups (end user roles) to the project structure.

Prerequisite You have created end user roles and/or distributed them in the Solution Manager system [page 164].



Double-click on the Name field goes from the End User Roles tab to the Maintain Object transaction (PP01), in which you can create end user roles.

Procedure ...

1. Go to the End User Roles tab.

2. Select a structure element.

3. Choose the end user role type, e.g. job and organizational unit, from the possible entries help. The possible entries help shows all roles which were created in the Maintain Object transaction (PP01) or distributed from the central HR system in the Solution Manager system.

4. Choose the end user role, e.g. accountant, from the possible entries help.


Result You can now Create a Learning Map [page 168] from the project structure.

Create Learning Map

Use You generate computer-supported self-learning courses for the end user tasks, e.g. for the new functions which the purchaser in your company will use, with the Solution Manager, from the existing project structure or a solution. You can send the self-learning courses to the end users, as a learning map, in HTML format, when they are ready.

Prerequisites • You have Assigned Training Materials [page 167] to a solution, in the project structure

Configuration or in production processing.

• You have Assigned End User Roles [page 167] in the project structure configuration or in production processing, to be able to filter the project or solution structure by end user roles.

• You have the role SAP_SOL_TRAINING_EDIT. This role is in the Project Leader and Application Consultant roles.

Procedure Structure of the Learning Map



HeaderLinks

Chapter

Title

Learningunit

Description

Document Document attribute

...

Create learning map 1. Call the Training Material Management transaction (SOLAR_LEARNING_MAP).

2. Choose Create.

3. Enter a title.

4. Specify with Select From Solution/Projeckt, whether you want to create the Learning Map from a project or a solution.

5. Choose the project or solution.

Change Learning Map ...

1. Create the learning map header:

a. Select the Learning Map Header node in the structure tree in the left-hand screen area.

b. Enter a description in the text field in the top right screen area.

c. To put further information in the learning map header, select the header node and choose a function from the context menu. Enter the data required, in the right-hand screen area.

You can put the following information in the header of a learning map:

� Logo, e.g. a picture which you use for all learning maps

� Link, e.g. the URL of your learning unit FAQs intranet page

� Link to your support desk

2. Create chapters:

a. Select the top node of the learning map structure in the structure tree in the left-hand screen area.

b. Choose Create Chapter from the context menu.

c. Enter a title for the structuring node, in the top right screen area.

d. Enter a description in the text field in the top right screen area.

Chapters are structuring nodes only, they contain no learning material. You can only assign learning material to learning units.

3. Create learning units below the chapter:

� Create new learning units



i. Select a chapter in the structure tree in the left screen area.

ii. Choose Create Unit from the context menu.

iii. Enter the data required, in the top right-hand screen area.

� Reuse project structure:

� ...

iv. Select a scenario or process in the project structure in the lower right-hand pane.

v. Drag & Drop it into a chapter of the Learning Map structure in the left-hand pane.

The system puts the structure element with the assigned documents in the Learning Map structure, as a learning unit.

4. Assign learning material to the learning units:

a. You can filter the project structure by the end user roles which you have assigned to the project structure in the End User Roles tab in the Configuration, with the Filter by Roles pushbutton.

b. Select the learning material in the project structure in the bottom right screen area, and Drag & Drop it in the learning unit into the learning map structure in the left screen area.

You can only create [page 167] new learning material in the Configuration transaction. You can only assign existing learning material to the learning map structure in the Learning Maps Management.


Display Learning Map in HTML format You can display the learning map in HTML format with the Open in Browser pushbutton.

Result You have created a computer-supported self-learning course (learning map). You can now send it to the end users [page 170].

Send Learning Map

Procedure

Send Learning Map ...

1. Choose the Send Learning Map pushbutton.

2. Choose the end user roles to which you want to send the learning map. You can restrict the selection.

3. Create an E-Mail in your E-Mail program with the E-Mail pushbutton.

The system copies a text template with a link to the learning map, into the clipboard. The system opens your local E-Mail program.

4. Copy the text template into the E-Mail.

5. Send the E-Mail with your E-Mail program



Create E-Mail text template The system uses the text template SA_LEARNING_MAP_DEPLOY_MAIL which is delivered by SAP, as the text template for the E-Mail to send the learning map, unless there is a customer template Z_LEARNING_MAP_DEPLOY_MAIL. ...

1. To create a text template Mail to send the learning map, create the Text in Dialog Z_LEARNING_MAP_DEPLOY_MAIL in the document maintenance (transaction SE61).

2. Edit the text. You can:

� Copy the SAP text template SA_LEARNING_MAP_DEPLOY_MAIL to Z_LEARNING_MAP_DEPLOY_MAIL and then change it

� Translate your text template


The system now automatically uses your customer template as the text template for the E-Mail to send the learning map.

Result The end users work through the learning material and assess it. You analyze the assessments [page 171].

The learning map is in the web server part of the Solution Manager system. End users do not need their own Solution Manager system users to be able to call the learning map, because the web server provides an anonymous display user. The end user assessments are saved anonymously.

Analyzing Learning Maps

Use When the end users have used the training materials which you created for them, they can evaluate the training materials anonymously. You can display the results of this evaluation in the Learning Maps Management.

Prerequisites You have created a learning map.

Features

Output • Number of times the learning map was called

• Individual evaluations

• Average evaluations

• Feedback about individual learning units and the entire learning map; detail display of feedback via icon

Activities You call the evaluation with the Analysis pushbutton in the Learning Maps Management.



Export Learning Map

Use To process a Solution Manager learning map further with the SAP Learning Solution or another e-Learning management tool, export it from the Solution Manager in the exchange format for computer-based learning objects, Sharable Content Object Reference Model (SCORM). After the export, you can also publish the contents of a Solution Manager learning map in an environment in which the users haven no access to the Solution Manager as web server, e.g. for users outside your company firewall.

Prerequisites You are in the initial screen of the learning map authoring environment, or have called a learning map.

Procedure ...

1. Choose Learning Map → Export in SCORM Format.

2. Specify a local directory for the export.

Result To see the exported learning map, open the SCORM main file imsmanifest.xml in the local directory, with a SCORM-capable program.

For further information about Sharable Content Object Reference Model (SCORM), see SAP note 821567.

Analyses

Use You can save information about a project per phase or project activity, e.g. status, deadlines or team members. Analyses are based on this information. The more detailed information you have recorded, the more analysis options you have. You can analyze either one project or several projects at the same time, depending on the selected project type.

Features The Solution Manager analyses comprise the following reports:

• Business Blueprint:

� Administration: Analysis of administration information, classified in general status analysis, and worklists which can be assigned to one or more project team members. In worklist analyses you can analyze specified data, such as the status or the planned end date.

� Assignments: Analysis of the assignments in the project structure. This can be documentation (general or project documentation) and transactions which were already delivered, or have been added during the project.

• Configuration:

The analysis is analogous to the Business Blueprint phase. You can also analyze the assignments of configuration objects (e.g. BC Sets, CATTs, IMG activities), test cases and problem messages. You can also make cross-system project IMG analyses, i.e. locally in the component systems.



• Test Organization: Analysis of test plans (individually or collectively)

• System landscape: Analysis of the logical components which are used in a project

• Change recording

• Learning Map: Analyze the feedback which users have given to a learning map (computer-supported self-learning course)

The analysis and analysis results display options are very flexible. You can use selection criteria to restrict the scope of the analysis, and specify how the results of the analysis are to be presented. You can create standard analyses and save them as selection variants, for the program types in the Business Blueprint, and Configuration phases.

You can perform the following analyses, depending on the selection criteria:

• Project information:

status information and documentation type analyses

• Progress monitoring,

for example by combining various status information (for example, project team members and a particular status) or by aggregating the project information

• General analyses,

for example daily analyses

You can restrict the analyses to one or more projects (depending on the project type).

You can call the displayed elements of the project structure or IMG activities directly from the output.

The output displays all information or contents, not only the project structure elements which satisfy the selection criteria, for completeness. So if you analyze the project team member Meier, you are also shown project team member Schulze, if he is also assigned to the element. If you do not specify selection criteria, all data in this project is analyzed.

Activities You can go to the analysis in two ways:

• cross-project and phase: Call the transaction Solution Manager: Analysis (SOLAR_EVAL).

• phase-specific: You can perform phase-specific analyses for a selected project in the Business Blueprint and the configuration. Choose Environment → Project Analyses and a program type.

Business Blueprint

Use The project analysis is based on selected information which you can save for the elements of your project structure in the Administration and Structure tabs.

You can analyze data for a single project or for several projects, depending on the scope of your project or the purpose of your analysis.

The specified selection criteria are evaluated in combination.

You can go to the Business Blueprint project analysis in two ways:



• cross-project and phase: ...

a. Call the transaction Project Analysis.

b. Choose Business Blueprint in the structure tree.

• phase-specific: You can perform phase-specific analyses for the selected project in the Business Blueprint (SOLAR01). Choose the Environment → Project Analysis menu.

To get administrative information about the project choose the Administration submenu, to check assignments choose the Assignments submenu.

Administration

Use The programs listed under Administration analyze administrative data. As well as general status analysis, you can analyze the worklists of one or more project team members, with special emphasis on the status and planned end. The Scope section list the analyses performed by each program.

Note the following differences, depending on the project analysis entry point:

Phase-specific Cross-phase

Entry via Menu: Environment → Project Analysis → Administration

Transaction: Project Analysis → Business Blueprint or Configuration → Administration

cope of Analysis Current project,

Logged-on user (project team member)

Selected projects,

One or more project team members

Features

General status analysis

Selection criteria You can analyze one or more projects by the following criteria:

Selection criteria Meaning

Project structure Selection of substructures or structure elements to be reported

Logical component Analysis of the logical components at the following structure levels:

Organizational Units

Master data

Business processes (for individual process steps)

Project Team Members Specify one or more project team members

Deadlines Project deadlines:



Planned start

Baseline Finish

Actual start

Actual end

Work resources Planned resources

Current resources

Remaining resources (difference between planned and current resources)

Status Status

Percentage complete

Keywords Keywords which you defined in the project administration and assigned in the project structure

Example The following project analysis scenarios are possible:

• Planned elements without actual data

The system analyzes all elements of the project structure for which the planned project start falls within the period you specified for Planned Start and for which no actual activity data yet exists.

Analysis criteria: Project number(s), Planned start period, Current resources = initial (no values), Remaining resources = initial (no values)

• Incomplete elements

The system analyzes all elements of the project structure for which the planned project end falls within the period you specified for Planned End and which are not yet 100% completed.

Analysis criteria: Project number(s), Planned End period, Percentage complete < 100.

• All started elements

The system analyzes all elements of the project structure for which the actual project start (from the actual data of the activity data) falls within the period you specified for Project Start and for which the actual project end is still open.

Analysis criteria: Project number(s), Project start, Project end = initial (no value)

• All completed elements

The system analyzes all activities for which the actual project end (from the actual status information data) falls within the specified analysis period.

Analysis criteria: Project number(s), Actual End period

• Individual analyses

You can perform individual analyses, as well as the analysis scenarios above, and define them as your default analyses. To be able to compare individual values in the analysis result to each other, you can calculate column totals.

For example, you are implementing several projects and find that the planned resources calculated are incorrect and that you will probably need more time.

To check the relationship between planned and current resources, you analyze all elements or activities that are not yet 100% complete. Then you calculate the total for the Planned Resources, Current Resources and Remaining Resources columns on the basis of the analysis result.



Analysis criteria: Project number(s), Planned resources, Current resources, Remaining resources, Percentage complete < 100.

(My) Worklist Display all structure elements which have been assigned to one or more project team members as the person responsible

Selection criteria Phase-specific entry

No selection criteria. The analysis is made in the project context with the logged-on user

Cross-phase entry

• Project: Project to be analyzed

• Project team member: One or more project team members whose worklist is to be found

Output Project structure with status, team member and logical component

(My) Worklist by status Display all structure elements which have been assigned to one or more project team members as the person responsible, with their status


Status: Status values to be analyzed. The analysis is made in the project context with the logged-on user.

Cross-phase entry



• Status: Status values to be analyzed

Output Project structure with status, team member and planned end date

(My) Worklist by planned end date Display all structure elements with their planned end date, i.e. the date on which processing by this project team member is planned to be completed


Planned end: Planned end of processing

The analysis is made in the project context with the logged-on user.

Cross-phase entry






Output Project structure with planned end, status, team member and remaining resources required

For further information about using the results list, see:

Process Project Analyses Results [page 193]

Assignments

Use All reference structures must contain blueprint-specific and configuration-relevant assignments at the structure elements. The reference structure only provides an element-specific view of the existing assignments. Assignment reporting provides a higher-level view.

You can make the following assignment analyses:

In the Business Blueprint phase:

• Documentation (general and project documentation)

• Transactions in implementation and template project

In the Configuration phase:

In addition to the assignments in the Business Blueprint phase:

• Configuration objects (IMG activities, BC Sets, CATTs, configuration-relevant documentation)

• Development objects (function module, transaction, program, package)

• Test cases in implementation and template project

• Problem messages in Issue Management

The analyses that can be performed on the assignment objects are listed in the Scope section.

Note the following differences, depending on the reporting entry point:


Entry via Menu: Environment → Project Analysis → Assignments

Transaction: Project Analysis → Business Blueprint or Configuration → Assignments

Scope of Analysis For current project (you can overwrite the default value)


Selected projects,


Features

Cross-report selection criteria These are the selection criteria which are in all assignment reports:

Selection




Project You must specify a project for cross-phase entry;

optional for phase-specific entry (current project is default)

System role BC Set activation status values are system-role-specific. Choose the system role for which the activation status is to be checked.

This is, depending on the configuration, the role Development/Customizing.


Logical component (not for documentation and problem messages)

Analysis of the logical components at the following structure levels:


Master data


Project Team Members Specify one or more project team members.

Keywords (not for transactions and problem messages)

Keywords which you defined in the project administration and assigned in the project structure

Documentation

Selection


Object attributes Enter the attribute as it is in the Gen. Documentation, Project Documentation or Configuration (Documentation) tab. Author: Last changed by.

Select tab



Configuration documentation

Test case descriptions

Training material

Analysis can be restricted to documents delivered/created in the template, or project-specific documentation

Output

Project structure with object (name/document title), document type, author, status and document type

Transactions

Selection


Object attributes Enter attributes as in the Transactions tab.



Template selection Templates which were created in a template project; only for Transactions in Template Project

Other transaction selections

Standard transaction or non-standard transaction

You can restrict the analysis to standard transactions or non-standard transactions, as classified in the Business Blueprint phase.

If you analyze a particular transaction and do not know whether it is defined as standard, make no selection here. Both alternatives are analyzed.

Transaction in scope or not (only for implementation project)

Restriction of analysis by implementation project scope

From template or added in project (only for implementation project)

Analysis of transactions which originally came from a template or analysis of transactions only added in the implementation project

Output

Project structure with object type, object, name, in scope, standard, template, project team members.

If a transaction in the project scope is flagged as default transaction or comes from a template, it is flagged with an "X".

Configuration objects

Selection


Object attributes Entry of attributes as in the Configuration tab.

Output

Project structure with object, logical component, name, status, project team members

Development objects

Selection

Selection critieria Meaning

Object attributes Entry of attributes as in the Development tab.

Output


Assigning test cases

Selection


Object attributes Enter attributes as in the Test Cases tab; test objects and test object type.

Other test case selections Analysis of test cases which originally came




from a template or analysis of test cases only added in the implementation project


Output

Project structure with project type, object, name, status, project team members

Analyzing test cases status

Selection




Output

Test case status analysis list

• Double-click on the status goes to a selection of test packages for the test case. You can now go to the test packages whose statuses were summarized in the status analysis, in the testing (STWB_WORK).

• Double-click on the test case name goes to the test case.

• Double-click on the structure element goes to the Test Cases tab of the structure element configuration (SOLAR02).



Configuration

Use You can analyze the data created in the Configuration phase analogously to the description for the Business Blueprint [page 173] phase.

Administration

Use The programs listed under Administration analyze administrative data. As well as general status analysis, you can analyze the worklists of one or more project team members, with special emphasis on the status and planned end. The Scope section list the analyses performed by each program.



Note the following differences, depending on the project analysis entry point:


Entry via Menu: Environment → Project Analysis → Administration

Transaction: Project Analysis → Business Blueprint or Configuration → Administration

Scope of Analysis Current project,

Logged-on user (project team member)

Selected projects,


Features

General status analysis




Logical component Analysis of the logical components at the following structure levels:


Master data



Deadlines Project deadlines:

Planned start

Baseline Finish

Actual start

Actual end


Current resources

Remaining resources (difference between planned and current resources)

Status Status

Percentage complete


Example The following project analysis scenarios are possible:

• Planned elements without actual data



The system analyzes all elements of the project structure for which the planned project start falls within the period you specified for Planned Start and for which no actual activity data yet exists.


• Incomplete elements

The system analyzes all elements of the project structure for which the planned project end falls within the period you specified for Planned End and which are not yet 100% completed.


• All started elements

The system analyzes all elements of the project structure for which the actual project start (from the actual data of the activity data) falls within the period you specified for Project Start and for which the actual project end is still open.

Analysis criteria: Project number(s), Project start, Project end = initial (no value)

• All completed elements


Analysis criteria: Project number(s), Actual End period




To check the relationship between planned and current resources, you analyze all elements or activities that are not yet 100% complete. Then you calculate the total for the Planned Resources, Current Resources and Remaining Resources columns on the basis of the analysis result.


(My) Worklist Display all structure elements which have been assigned to one or more project team members as the person responsible


No selection criteria. The analysis is made in the project context with the logged-on user

Cross-phase entry



Output Project structure with status, team member and logical component

(My) Worklist by status



Display all structure elements which have been assigned to one or more project team members as the person responsible, with their status


Status: Status values to be analyzed. The analysis is made in the project context with the logged-on user.

Cross-phase entry




Output Project structure with status, team member and planned end date

(My) Worklist by planned end date Display all structure elements with their planned end date, i.e. the date on which processing by this project team member is planned to be completed


Planned end: Planned end of processing

The analysis is made in the project context with the logged-on user.

Cross-phase entry




Output Project structure with planned end, status, team member and remaining resources required



Assignments

Use All reference structures must contain blueprint-specific and configuration-relevant assignments at the structure elements. The reference structure only provides an element-specific view of the existing assignments. Assignment reporting provides a higher-level view.

You can make the following assignment analyses:

In the Business Blueprint phase:

• Documentation (general and project documentation)



• Transactions in implementation and template project

In the Configuration phase:

In addition to the assignments in the Business Blueprint phase:

• Configuration objects (IMG activities, BC Sets, CATTs, configuration-relevant documentation)

• Development objects (function module, transaction, program, package)

• Test cases in implementation and template project

• Problem messages in Issue Management

The analyses that can be performed on the assignment objects are listed in the Scope section.

Note the following differences, depending on the reporting entry point:


Entry via Menu: Environment → Project Analysis → Assignments

Transaction: Project Analysis → Business Blueprint or Configuration → Assignments

Scope of Analysis For current project (you can overwrite the default value)


Selected projects,


Features

Cross-report selection criteria These are the selection criteria which are in all assignment reports:

Selection


Project You must specify a project for cross-phase entry;

optional for phase-specific entry (current project is default)

System role BC Set activation status values are system-role-specific. Choose the system role for which the activation status is to be checked.

This is, depending on the configuration, the role Development/Customizing.


Logical component (not for documentation and problem messages)

Analysis of the logical components at the following structure levels:


Master data




Project Team Members Specify one or more project team members.

Keywords (not for transactions and problem messages)

Keywords which you defined in the project administration and assigned in the project structure

Documentation

Selection


Object attributes Enter the attribute as it is in the Gen. Documentation, Project Documentation or Configuration (Documentation) tab. Author: Last changed by.

Select tab



Configuration documentation

Test case descriptions

Training material

Analysis can be restricted to documents delivered/created in the template, or project-specific documentation

Output

Project structure with object (name/document title), document type, author, status and document type

Transactions

Selection


Object attributes Enter attributes as in the Transactions tab.

Template selection Templates which were created in a template project; only for Transactions in Template Project

Other transaction selections

Standard transaction or non-standard transaction

You can restrict the analysis to standard transactions or non-standard transactions, as classified in the Business Blueprint phase.

If you analyze a particular transaction and do not know whether it is defined as standard, make no selection here. Both alternatives are analyzed.

Transaction in scope or not (only for implementation project)

Restriction of analysis by implementation project scope


Analysis of transactions which originally came from a template or analysis of transactions only added in the implementation project

Output

Project structure with object type, object, name, in scope, standard, template, project team members.



If a transaction in the project scope is flagged as default transaction or comes from a template, it is flagged with an "X".

Configuration objects

Selection


Object attributes Entry of attributes as in the Configuration tab.

Output


Development objects

Selection

Selection critieria Meaning

Object attributes Entry of attributes as in the Development tab.

Output


Assigning test cases

Selection



Other test case selections


Analysis of test cases which originally came from a template or analysis of test cases only added in the implementation project


Output

Project structure with project type, object, name, status, project team members

Analyzing test cases status

Selection




Output

Test case status analysis list



• Double-click on the status goes to a selection of test packages for the test case. You can now go to the test packages whose statuses were summarized in the status analysis, in the testing (STWB_WORK).

• Double-click on the test case name goes to the test case.

• Double-click on the structure element goes to the Test Cases tab of the structure element configuration (SOLAR02).



Cross-System IMG Analysis

Use Project analysis is based on the information that you can record for each activity in the customizing (IMG) project. We refer to "IMG activities", but you can also record and analyze status information for project IMG structure nodes.

You can analyze data for a single project or for several projects, depending on the scope of your project or the purpose of your analysis.

To go to the customizing project analysis: ...

1. Call the transaction Project Analysis.

2. Choose Cross-System IMG Analysis, or an existing variant, in the structure tree.

You can also analyze your customizing project in the project administration. ...

1. Select a project in the project overview.

2. Choose Goto → Project Analysis.

3. Choose IMG or an existing variant in the structure tree.

Features



General project data IMG structure node text

Resources Project manager

Project team members

Keywords Keywords

Status Status

Percentage complete

Deadlines Planned start

Baseline Finish

Project start



Project end


Current resources

Remaining resources (work required)

Documentation Documentation types

Memo text Memo

Management data Created on

Created by

Last changed on

Last changed by

The following project analysis scenarios are possible:

• Planned activities without actual data

The system analyzes all activities whose planned start falls within the period you specified for Planned Start and for which no actual status information yet exists.


• Activities not yet completed

The system analyzes all activities for which the planned project end falls within the period you specified for Planned End, and which are not yet 100% complete.


• All activities started

The system analyzes all activities for which the actual project start (from the actual status information data) falls within the period you specified for Project Start, and for which the actual project end is still open.

Analysis criteria: Project number(s), Project start period, Project end = initial (no value)

• All completed activities


Analysis criteria: Project number(s), Project End period




To check the relation of the planned resources to the current resources, you analyze all activities that are not yet 100% complete. Then you calculate the total for the Planned Resources, Current Resources and Remaining Resources columns on the basis of the analysis result.




Problem Messages

Use You can run a report about problem messages created, and monitor their status. You can for example cover the following use scenarios:

• Analysis of all problem messages with the status Open

• Analysis of problem messages created by a specified user, e.g. yourself

• Check the processing status of all messages with priority Very High

Integration The data which you created in the configuration phase in the Problem Messages tab is analyzed.

Features

Selection criteria Selection criteria Meaning

Project structure Selection of substructures or structure elements to be analyzed


Object attributes

Message

Description

Status

Priority

Subject

Creator

Processor

Created at

Changed at

Message number

Message short text

Message priority fron Low to High

Component – Message category

Output Project structure with existing selection criteria values

� You can go directly to the problem message processing by double-clicking on a

row in the results list (not a structure element).

� You can go directly to the Problem Message tab of a structure element in the configuration phase project structure, by double-clicking on the structure element.



Test Organization: Analysis with the Status Info System

Use This function monitors the progress of one or more test plans.

Prerequisites You must already have created test plans.

Features Use the Status Info System to:

• display complete results of test plans graphically or in a table

• display status analyses of individual test plans, export into Office applications or print

• display and analyze test plan problem messages

Activities You can call the status info system:

• From the transcation Solution Manager: Analyses: ...

a. Call the transaction Solution Manager: Analyses.

b. Choose the report variant Test → Analyze Test Plan Status in the structure tree

c. Choose the project to be analyzed, and Execute.

• from the Configuration

Choose the menu function Environment → Project Analysis → Test in the Configuration [page 150].

• from the Test Plan Administration

Choose the Status Info System pushbutton in the Test Plan Management [page 248].

See also:

• Analyze Test Status [external link]

• Test Plan Problem Overview [page 256]

• Test Organization: Analysis of Tests by Process [page 190]

Test Organization: Analysis of Tests by Process

Use You can monitor the progress of tests in your project by process and across test plans, with Project Status Analysis. You see in which test plan and test package a test case is used, if any.

Integration The Status Info System Analysis [page 190] (test plan status analysis) analyzes the status of test cases by test plans or test packages in which a test case is used. The analysis of tests by process (project status analysis) shows the status of test cases across test plans.



Prerequisites • You have assigned test cases to your project structure.

• You have put the test cases in a test plan, and generated the test plan.

• You have put the test cases in a test package.

Features

Selection

Selection criteria



Logical component Analysis of the logical components which are assigned to the structure elements



Status Test case status


Activities Call the analysis of tests by process in the transaction Solution Manager: Analysis (SOLAR_EVAL) → Test → Project Status Analysis.

System Landscape

Use The System Landscape function in the transaction Solution Manager: Analysis (SOLAR_EVAL) determines which components are assigned to which process steps.

Features Selection criteria



Logical components A logical component usually corresponds to a product, e.g. SAP CRM

Output Project structure with logical components and logical systems



Analyze Project

Prerequisites To be able to analyze projects, you must have recorded information about the project phases in Execute Project.

Test organization details are not considered here. For further information see Analyze test status [page 254].

Prerequisites You are in the initial screen of the program to be run.

Procedure ...

1. Enter the number of the project that you want to analyze.

You can also specify a range of project numbers to make a cross-project analysis.

2. Restrict project analysis by specified criteria. If you do not specify any selection criteria, all selection criteria are analyzed by default.

You can select by initial value with Edit → Selection Options.

You want to select all elements that have been started but not yet completed. Enter a project start date (actual start) and set the project end (actual end) to its initial value by double-clicking the selection field. The system displays the Select by Initial Value dialog box. Choose = (Single value) and Continue. Leave the selection field empty.

3. Choose Execute to start project analysis.

You can save your selection data as a variant in the initial screen of the associated program type, to reuse it as your standard analysis later.

� Choose Goto → Variants → Save as Variant…

� Assign a meaningful name and a meaning (short description) for the variant, and save it. The variant is assigned as a variant of the program type, in the Analyze Project dialog box.

� The variant icon in the program type initial screen indicates that a program type has a program variant. You can get a program-specific selection of your standard variants under Goto → Variants → Display… You can also call the variant directly by double-click in the Analyze Project dialog box.

For more information on how to use the selection screen, choose Goto → Selection Screen Help.



Result The analysis results are displayed as a hierarchy. You can switch to a tabular results display with the Table pushbutton.

This display format has a Node Type column, which tells you the structure element type (scenario, business process, process step, master data, organizational unit), as well as the Hierarchy display.

General

You can navigate by double-clicking on an element in the hierarchy or table, depending on the program type:

• Program type Cross-System IMG Analysis: Navigation into the project IMG in which you can work as usual. The selected structure title in the Project IMG is highlighted.

• Business Blueprint or Configuration phase programs: Navigation to the structure element in the project structure, for which you can edit the status information or other business content (exception in the behaviour of: Problem Messages [page 189]).

If you change status information or business content assignments after you have performed a project analysis, you must perform this analysis again to update the results list.

Process Project Analyses Results

Use You can process the results of the project analysis in various ways, including:

• sort project results (only in table display)

• filter results selection display (only in table display)

• sum numeric columns and show subtotals (only in table display)

• define and display display variants (only in table display)

• download analysis results (only in table display)

• export analysis results to MS Excel (only in table display)

Sort Proceed as follows: ...

1. Choose Edit → Sort in Ascending Order or Sort in Descending Order, or the Sort in Ascending Order or Sort in Descending Order symbols, in the analysis list.

The system lists all fields available.

2. Put fields from the field list in the sort fields list. The field sequence is significant.

The top sort field in the Sort Fields list is the first sort criterion.

3. Choose Copy.

The analysis list is sorted as defined.



Filter Proceed as follows: ...

1. Select the headers of all columns that you want to filter, in the analysis list.

2. Choose Edit → Set Filter, or the Set Filter symbol.

You select filter criteria from among the columns that you have selected.

3. Enter a value or a term as your filter criterion.

You can specify a restriction interval with the Multiple Selection symbol. You can use relational operators.

4. Choose Continue.

The list is filtered according to your criteria.

To remove your filter, choose Edit → Delete Filter or the Delete Filter pushbutton.

Totals Proceed as follows: ...

1. Select the headers of all columns that you want to sum, in the analysis list.

2. Choose Edit → Sum Values, or the Sum Values symbol.

A new row is appended to the list, with the totals of the selected columns.

You can calculate subtotals for sorted columns.

Proceed as follows: ...

1. Select the header of a column in the analysis list that contains values that cannot be summed, such as the Project team members column.

2. Choose Edit → Subtotal, or the Subtotal symbol.

The system displays a new row after each change in the column selected, that shows the subtotals of the values added up previously.

Define and display display variants You can save the changed results list display format as a display variant, for reuse at a later date.

Proceed as follows:

3. Choose: Settings → Display Variants → Save Display Variants… for template and implementation projects Settings → Display Variant → Save… or the Save Display Variant pushbutton for customizing projects.

...

1. Enter a name and a description for your display variant.

2. Set the User-Specific checkbox if the display variant is not to be available to other users.

3. Specify whether you also want to save the sort and subtotals criteria in your display variant.

4. Choose Save.

Your settings are saved as a display variant. To display it later, choose: Settings → Display Variants → Select Display Variant… for template and implementation projects



For information about ALV Grid Control functions, see the ABAP List Viewer (ALV) documentation under Toolbar and context menu functions [external link].

Project View You can create a project view for each project in the results list. Proceed as follows: ...

1. Position the cursor on a row of the project for which you want to create a project view, in the results list.

2. Enter the name of the project view.

3. Display project view immediately goes to the project view.

You can use the project view as usual and change it as required.

4. Choose Back to return to the analysis list.

5. If you change the project view, you must perform your analysis again.

Download analysis results Proceed as follows: ...

1. Choose the Local File icon.

2. Select the list/table save format.

3. Specify the file name and directory in which you want to save the analysis results.

Specify the file name extension explicitly.


Export analysis results to MS Excel You can export the analysis results directly to MS Excel for editing. Proceed as folows: ...

1. Choose Spreadsheet.

2. Choose Table and Microsoft Excel in the following dialog box.

3. You can save the exported table.

Customizing Synchronization

PurposeYou use several SAP components in your system landscape, e.g. SAP R/3 and SAP MDM. The SAP MDM system is based on data which is already in SAP R/3, and the systems cooperate in many business scenarios. Customizing settings which define business processes across systems must be and remain synchronized, to ensure smooth and correct exchange of data. Areas in which the customizing must be synchronized include customer and product groups, sales areas, payment conditions, delivery conditions, commission groups, currencies, countries, regions and measurement units.

SAP provides two tools to support customizing synchronization:

Customizing Distribution and the Customizing Scout. ...



1. Customizing Distribution transfers customizing from one system to another ("Initial distribution"), or updates customizing in different systems at the same time, whenever customizing is changed in a reference system ("Delta distribution"). Customizing Distribution can:

� configure training, demo and test systems quickly with the initial customizing distribution

� synchronize SAP R/3, SAP MDM and SAP APO systems with the delta distribution, to ensure that cross-component processes run smoothly

� synchronize customizing in different SAP R/3 systems, to prepare an ALE distribution of master data

Customizing Distribution helps system administrators to monitor customizing activities in several systems, with checks, automatic logging of all customizing distributions, and error handling.

2. The Customizing Scout, a tool which compares the customizing between different systems, complements Customizing Distribution.

Integration The Customizing Synchronization is part of the SAP Solution Manager.

Customizing Distribution transfers the customizing from one development system (SAP R/3) into another (e.g. SAP R/3 or SAP MDM). You can then transport the data into the quality assurance and production systems in a controlled manner. This customizing data thus takes the same path through the development and test systems as other customizing data. The Customizing Distribution also has other additional functions, above all comparison, distribution of customizing changes, and logging.

FeaturesYou können use the following tools:

• The Customizing Scout [page 230] compares customizing in two systems.

• The Customizing Distribution [page 200] synchronizes customizing in a source and various target systems.

• You can specify customizing objects which must be synchronized in your system landscape, with the Synchronization Object Specification Tool [external link].

Restrictions You can use predefined Synchronization objects [page 206], customizing objects which are to be synchronized in different components, in the Customizing Distribution and the Customizing Scout. You can also select any transportable customizing object of type Space (table), V (view), S (table with text table), C (view cluster), T (individual transaction ) and L (logical transport object), for the Customizing Synchronization. This customizing objects must satisfy the prerequisites described in suitable objects for the Customizing Synchronization [page 246].

You can only distribute customizing in harmonized systems. Distributing customizing in system landscapes which are not harmonized causes data inconsistencies.

Do not combine Customizing Distribution and the Customizing ID Mapping Framework [page 87] for a customizing object and its system. This can also cause data inconsistencies. Customizing Distribution and the Customizing ID Mapping Framework are both components of the SAP Solution Manager, but they are not integrated with each other. You can either distribute a customizing object between two systems with the Customizing Distribution, or set-up ID mapping.



Prerequisites for Customizing Distribution and Customizing Scout

Purpose Before you use the Customizing Distribution [page 200] or compare customizing with the Customizing Scout [page 230], you must fulfill their technical prerequisites in the systems involved. This process describes how to make the necessary system settings.

Process Flow

Install and set-up system landscape You have installed the SAP Solution Manager, as described in the Installation Guide.

The installation guide is in the SAP Service Marketplace service.sap.com/instguides -> SAP Components -> SAP Solution Manager.

Assign authorizations

System administrator

The system administrator or project leader must have the following authorizations in the component systems, to be able to make Customizing Distribution settings:

Authorizations in the component systems

Authorization Meaning Note

S_USER_AUT

S_USER_GRP

S_USER_PRO

Create user

S_PROJECT

S_PROJECTS


S_CTS_ADMI Transportadministration Customizing Distribution only

S_TRANSPORT Create transport requests Customizing Distribution only

S_RFCACL Trusted System connections Customizing Distribution only

SAP Solution Manager system authorizations:

SAP Solution Manager system authorizations


S_CD_SYSAC System access for comparisons

Customizing Scout only

S_CD_SYST Set-up system landscape

S_PROJECT

S_PROJECTS


S_RFCACL Trusted System connections Customizing Distribution only



Customizer

All customizers in the component systems have the following authorizations:

Authorizations in the component systems


S_TABU_CLI

S_TABU_DIS

View maintenance

S_TABU_LIN Row authorization

S_TABU_RFC Data transfer by RFC

S_BCSETS Create and activate BC Sets Customizing Distribution only

All customizers in the SAP Solution Manager system have the following authorizations:

SAP Solution Manager system authorizations


S_CD_SYNC Comparison or Distribution authorization check

S_TABU_RFC Data transfer by RFC Customizing Scout only

S_TABU_DIS

S_TABU_CLI

View maintenance

You can also use the authorization profile S_CUS_CMP in the component systems. You must edit it if it was not already edited during the installation of the SAP Solution Manager. See SAP note 492908.

The role Application Consultant has all authorizations which are needed to set-up the Customizing Distribution in the SAP Solution Manager system.

Client settings The Customizing Distribution requires that all customizing changes are automatically put in a transport request. Set the clients in the component systems to Record Changes Automatically, in the transaction SCC4. Set all clients in the component systems to changeble in the transaction SE06, and make settings in the transaction SCC4 to allow changes to cross-client customizing.

Check Support Package status For the minimum Support Package status in the source and target systems, see the SAP Solution Manager configuration guide, or the following notes:

• SAP note 552457: Prerequisites for Customizing Distribution target systems

• SAP note 552494: Prerequisites for Customizing Distribution source systems

The configuration guide is in the SAP Service Marketplace service.sap.com/instguides -> SAP Components -> SAP Solution Manager. The



relevant chapter is: Implementation and Distribution - Support Package Levels for Customizing Distribution

Setup RFC connections with the System Landscape transaction ...

Create the RFC connections for Customizing Scout or Customizing Distribution, in the transaction, Set-Up System Landscape (SMSY_SETUP).

Follow the detailed instructions in the System landscape [page 60] help.

Customizing Scout Customizing Distribution

RFC connections required

SM_<system ID>CLNT<client>_READ to read data

SM_<system ID>CLNT<client>_TRUSTED for interactive access for the Customizing Distribution

SM_<System ID>CLNT<client>_BACK to check/display customizing objects which are in an active distribution, and are to be locked

If you have created RFC connections for SAP R/3 3.1I or 4.0, enter them in the table scdtsysrfc with the transaction SE16, because the system does not do so.

RFC read connection (only for Customizing Scout) ...

1. Go to the target system to which you want read access with the Customizing Scout for a customizing comparison.

2. Create a user with which you want read access to the target system, in the user maintenance transaction (SU01).

3. Assign the authorization profile S_CUS_CMP to the user. Read SAP note 492908 to check the authorization profile for completeness, and enhance it if necessary.

4. If no RFC connection has yet been created, create an RFC connection to the SAP Solution Manager system, with the RFC connection maintenance transaction (SM59).

5. Save the created user and password in this RFC connection, for future read access to the system with the user.

Create Customizing Distribution project (only for Customizing Distribution) Follow the detailed description in the Project Administration [page 25] help (transaction solar_project_admin), to perform the following steps: ...

1. Create a project in the Project Administration.

2. Define a system landscape for this project. Ensure that development systems are defined for all components.

3. Generate a project IMG for all development systems.

You go to the Project Administration in the system. Transports [page 35], which are also used during customizing, must be created for this project, in the component systems.

4. Create customizing and workbench transports for this project.



5. If sie want to distribute customizing changes after transport change or transport release, create tasks for all customizers in the systems involved, in the transport requests.

6. If you want to distribute customizing with the Initial Distribution [page 216] or timed, as system administrator, create tasks for yourself in the transport requests in the systems involved. If you want to Redistribute Customizing after Errors [page 223], you must also have a task in the transport requests in the systems involved.

7. Go Back and save your entries in the SAP Solution Manager system.

Load synchronization objects for SAP components If you use another component than those of the SAP R/3 product, e.g. to compare SAP R/3 and SAP MDM, you must load the synchronization objects for these components, to adjust structure differences between SAP R/3 and SAP MDM.

Go to the Synchronization group editor [page 210] and load the synchronization objects with Goto → Load Object Lists [page 231].

Result You can now compare customizing in different systems with the Customizing Scout. You can also now use the Customizing Distribution [page 204].

Customizing Distribution

Use You often have to make selected customizing settings match in various systems within a system landscape. You can use the Customizing Distribution to synchronize selected customizing settings in a source system (e.g. SAP R/3) with the customizing settings in the target systems (e.g. an SAP MDM system).

The system which is the reference for the Customizing Distribution is also referred to below as the source system. All other systems in your system landscape are referred to as target systems and are synchronized with the source system.

Integration The Customizing Distribution synchronizes the customizing settings when implementing or updating while operating the system. Before you synchronize customizing settings, you can compare them with another tool, the Customizing Scout [page 230],.

Prerequisites You have satisfied all the Customizing Distribution prerequisites [page 197]. You have ensured that the Customizing ID Mapping Framework [page 87] is not used in more than one customizing object and system at the same time.

Features

Automatic distribution of customizing You can perform the following functions on customizing settings in a development landscape with the Customizing Distribution:

• initial download from a source system into a target system (initial distribution)



• timed distribution

• distribute automatically after each transport release or customizing change (from SAP R/3 4.6C)

• distribute manually.

The Customizing Distribution starts a process which transfers the customizing into the target systems. The Customizing Distribution writes all distributed customizing changes in transport requests, so that you can transport the customizing changes from the development systems into the quality assurance and production systems.

You can only select one distribution type per Solution Manager project and source client, i.e. you must decide whether you use timed Customizing Distribution, or distribute after transport release or after customizing changes. Only one distribution type per source client is also allowed for non-project-specific Customizing Distribution.

Predefined objects for Customizing Distribution Certain customizing objects which must be synchronized in a development landscape are predefined in the system (Synchronization Objects [page 206]). You can select synchronization objects and other customizing objects for the distribution with the Synchronization Group Editor [page 210].

For further information about which customizing objects can be distributed, see Suitable Objects for Customizing Synchronization [page 246].

Display Customizing Distribution in the Implementation Guide An icon in the component system Implementation Guide (IMG) indicates whether the customizing of an IMG activity was changed by the distribution. To display this icon in the IMG, the component systems must contain the software component SAP_BASIS with the following Basis Support Packages:

Basis support packages required to display the icons in the IMG

SAP_BASIS Basis support package

6.10 24

6.20 7

6.30 and higher -

Lock distribution-relevant customizing objects in the target systems You can automatically lock the customizing objects or key areas which are to be changed by the Customizing Distribution. The entire customizing object is locked. You can filter the locks to specified key entries, which lets you add other, for example target system-specific entries, in the target system.

You can only lock standard customizing objects, i.e. objects of type View (V), View Cluster (C) and Table with Text Table (S). You can only lock other customizing objects organizationally.

Logging You can Display the Customizing Distribution Logs [page 223] after Customizing Distribution.



Quick Guide: Setting-Up Customizing Distribution

Purpose The Quick Guide lists the minimum activities which you must perform to make the basic Customizing Distribution settings. You can use it for reference, as a quick reference or as a checklist.

The detailed information refers to other sources of information, in which the listed activities are described in more detail.

Prerequisites Depending on your role, you have:

• Authorization to set-up Customizing Distribution as system administrator

• Authorization to customize the source and target systems as a customizer

The system settings allow customizing to be recorded in transport requests in the source client (transaction SCC4).

For detailed information about authorizations and client-specific system settings, see: Prerequisites for Customizing Distribution and Scout [page 197]

Process Flow The following activities apply for the initial distribution, automatic distribution and manual distribution of customizing with Customizing Distribution, except where stated otherwise.

Required Activities Details

Check minimum technical requirements Configuration Guide: Solution Manager <release> in SAP Service Marketplace /instguides → SAP Solution Manager: Relevant chapter for use case “Implementation and Distribution”, keyword: Customizing Distribution

System landscape (transaction SMSY)

Landscape component Systems: record systems involved in distribution, centrally

Clients tab : Generate client-specific RFC connections per main instance:

If no client information has yet been read in: Generate RFC connections and read users, to update system data

Set-up trusted system RFC connection für customizing synchronization

Return RFC to check locks: Selection of RFC connections from <SYS_ZIEL> to <SYS_SOLMAN>, client XYZ

Prerequisites for Customizing Distribution and Customizing Scout [page 197]



SAP Solution Manager: Project Administration (transaction: SOLAR_PROJECT_ADMIN)

Create Solution Manager Project (Type: Implementation Project)

Tab: System Landscape/Systems:

Define logical components with products/product versions

Assign logical systems for system role to development system (corresponds to distribution source and target systems)

Tab: System Landscape/IMG Projects:

Namensgleiche IMG-Projekte für logische Systeme (Entwicklungssysteme) generieren

Generate transport requests for IMG projects, and tasks for customizers in source and target requests, at the same time

Initial distribution only needs a transport request in the target system.

Create/Change Project [page 25]; especially System Landschaft Tab [page 30]

Set-Up Customizing Distribution: Overview (transaction SCDT_SETUP)

If some synchronization objects have been defined, e.g. to map customer-specific objects (transaction SCDT_MAPPING in the target system)

Synchronization Object Specification Tool [page 238]

For cross-component distribution (e.g. from SAP R/3 to SAP MDM) or for defined user objects: Load synchronization objects from target system (Goto → Load Object Lists menu in the Set-Up Customizing Distribution: Overview initial screen)

Create and Load Synchronization Objects [page 236]

sapurl_link_0014_0007_0014

If synchronization groups which are not pre-defined by SAP are used: Define synchronization groups in the editor (choose Goto → Synchronization Group Editor in the Set-Up Customizing Distribution: Overview initial screen)

Create Synchronization Group [page 213]

Recommendation: If there are several transport requests in the target client : Assign source and target transports by IMG project (Edit → Assign Transport Request in Set-up Customizing Distribution: Details detail screen )

Assign Transport Requests to Source and Target Systems [page 208]



Set-Up Customizing Distribution: Details: Automatic or manual distribution:

Select synchronization group from possible entries help

Select source IMG project for distribution-relevant transports

Specify distribution type and source system

Specify distribution target system(s)

If you have problems with automatic (transport-controlled) distribution, set -up distribution in the Customizing Distribution: Details screen:

Trigger manual distribution of transports (Goto → Customizing Distribution: Individual Transport) or

Trigger redistribution of failed distributions of a project (Edit → Automatic Redistribution after Errors)

Set-Up Automatic Customizing Distribution [page 217],

Start Initial Distribution [page 216],

Distribute Individual Transport Manually [page 219],

Automatic Redistribution after Errors [page 223]

Analyze Customizing Distribution Logs (Goto → Customizing Distribution: Logs menu in the Set-Up Customizing Distribution : Overview initial screen)

Log Customizing Distribution [page 220]

Customizing Distribution

Purpose The Customizing Distribution transfers customizing settings or customizing changes made in one development system into other development systems in your system landscape. You can for example use the Customizing Distribution to:

• download selected customizing from an SAP R/3 into a newly-installed SAP MDM system

• synchronize customizing in an HR and a non-HR system, and then use ALE distribution in a stand-alone HR [page 212]

• synchronize customizing in an SAP R/3 System and an SAP MDM system, because you have business processes which run in both SAP R/3 and SAP MDM.

Prerequisites You have satisfied all the Customizing Distribution prerequisites [page 197].

Process Flow

Preparing Customizing Distribution ...

1. Choose customizing objects or IMG activities which are Customizing Distribution-relevant. Create a synchronization group in the Synchronization group editor [page 210]. The synchronization group comprises all customizing objects which you want to distribute from a source component to a target component.

2. Start the Initial distribution [page 216] to initiallysynchronize selected customizing in a source system with customizing in target systems. You specify:

− which synchronization group is to be activated for the customizing distribution

− the source development system



− the target development system

3. Set-up the automatic Customizing Distribution [page 217], to transfer selected customizing changes from a source system into target systems. Specify whether the customizing is to be distributed during customizing, after transport release, or periodically at specified times

Automatic Customizing Distribution by transport

SAPSolutionManager

SAPR/3DEV

SAPMDMDEV

SAPR/3QAS

SAPR/3PRD

SAPMDMQAS

SAPMDMPRD

Protokoll

...

1. You make customizing changes in the source system.

2. The source system reports the changes to the SAP Solution Manager system. The SAP Solution Manager system checks:

− whether the customizing changes are in a synchronization group for which the Customizing Distribution is active

− into which target system the changes are to be passed.

3. The SAP Solution Manager system converts customizing data which is to be distributed, into customizing data for the target system.

4. The SAP Solution Manager system passes the customizing changes to the target systems.

5. The Customizing Distribution writes changes in transport requests, with which you can transport the new customizing settings into subsequent systems in the transport path, in the target systems.

6. The target systems report any Customizing Distribution errors to the SAP Solution Manager system.

7. Examine the Customizing Distribution logs [page 223] in the SAP Solution Manager system, to check the Customizing Distribution results.

8. Compare the customizing in the various systems with the Customizing Scout [page 230], to check whether the Customizing Distribution has really synchronized the customizing.



Result Customizing Distribution is performed in development systems. To transport to a quality assurance and production system later, release the associated transport requests. This ensures that the customizing settings are synchronized in all subsequent systems, not just the development system.

You can change or copy Customizing Distributions at any time via the menu. After copying, you can for example change the distribution option or the distribution project.

Synchronization Object

Definition A customizing object in an SAP component, to which a customizing object with the same contents in another component is assigned. The contents of the customizing objects have to be synchronized in different systems in a system landscape.

You create synchronization objects if customizing objects in different systems have the same contents, but different structures, for example different table and field names.

Use The synchronization objects are the basis for comparisons in the Customizing Scout [page 230], and the adjustment of customizing in the Customizing Distribution [page 200]. You can also select individual synchronization objects for which you want to make a comparison in the Customizing Scout, or an adjustment in the Customizing Distribution, with the Synchronization Group Editor [page 210].

Predefined synchronization objects are currently available for the following SAP components:

Components for which synchronization objects are available

Target component

Software component Source component

Software component

SAP HR (stand-alone HR) [page 211]

SAP_HR 6.10 SAP R/3 SAP_APPL 6.10

SAP R/3 (stand-alone HR)

SAP_APPL 6.10 SAP HR SAP_HR 6.10

SAP MDM MDM 2.0, 3.0 SAP R/3, also object pairs for SAP MDM

SAP_APPL 3.1 and later

The Customizing Scout and the Customizing Distribution first get system landscape component information, including the release (e.g. SAP MDM 3.0, SAP R/3 4.0B). This information is important because the mapping of customizing objects in the source component to a customizing object in the target component is release-dependent.

Structure In the simplest case, a synchronization object comprises one customizing object in a source component, which corresponds to exactly one customizing object with the same name in the target component. If the objects are not identical, the system contains descriptions of how they are mapped onto each other. The description specifies which customizing object in the target component corresponds to a customizing object in a source component, i.e. a



customizing object in the target component is mapped onto a customizing object in a source component. The starting point of the assignment is always the object in the target component, i.e. tables and field names of the object in the target component are first determined, and are then assigned to field names of the corresponding object in the source component.

The following forms of mapping are currently supported:

• No Mapping Required (same data): Both the table names and the field names are identical in the target and source components. Not all fields must be in both tables.

• Different Table Names: The field names are identical in the target and source components, but the table names are different. Not all fields must be in both tables.

• Different Table and Field Names: Both the table names and the field names are different in the target and source components. Not all fields must be in both tables.

• Programmed Mapping: The customizing is assigned in the source and target components by a function module.

Integration The synchronization objects are customizing objects of the following types:

• Table (space)

• View (V)

• Table with text table (S)

• View cluster (C)

• Transactions (T)

• Logical Transport Objects (L)

View clusters are resolved into individual views, and transactions into their tables.

Display Synchronization Object Definition

Use You display the definition of a synchronization object to check whether you want to use it in the Customizing Distribution.

Prerequisites You have called the transaction scdt_show_mapping and are in the synchronization object display initial screen. If you want to see synchronization objects for other components (e.g. SAP MDM), you have downloaded them with Goto → Load Object Lists.

Procedure ...

1. Choose a target component and release.

The system displays a list of synchronization objects.

2. Choose a synchronization object.

3. Choose Display.

You go to the Display Synchronization Objects screen.



Result The system displays the following information:

• The source component is usually the SAP R/3 system (software component: SAP_APPL); the target system runs on the software component, for example MDM.

• An IMG activity is usually assigned to each synchronization object.

• The original system for the synchronization object is the system from which it was downloaded into the SAP Solution Manager system.

• For each synchronization object is defined:

� whether it can only be used for comparison with the Customizing Scout [page 230] (only relevant for comparison)

� whether it can be used for comparison with the Customizing Scout and the Customizing Distribution [page 200] (relevant for comparison and distribution)

� whether it can only be used for manual Customizing Distribution by transport [page 219] (only relevant for distribution by transport)

� whether it can only be used for the Initial Distribution [page 216] (only relevant for initial distribution)

� whether it can only be used for the initial distribution and the comparison with the Customizing Scout

• The mapping type is specified under Structure Differences:

− No Mapping Required: The tables have the same table and field names.

− Different Table Names

− Different Table/Field Names

− Programmed Mapping: A function module converts source system customizing data into target system customizing data.

• If the table or field names differ, the Assignment table contains the names of the tables or fields which correspond.

• The system shows whether the synchronization object has been further restricted for distribution or comparison, by filter conditions for the source system or the target system, under Filter Conditions [page 215].

• The Fixed Field Value/Variable column can also contain fixed field values or variables.

Fixed field values are required for a source component table, for example, if one or more tables in the target component contain additional fields which have no corresponding fields in the source component. The following variables are currently available: $LOGSYS; $SYLANGU; $MANDT; $UNAME; $SYDATUM; $SYUZEIT.

Assign Transport Requests to Source and Target Systems

Use Transport-controlled distribution using several transport requests in the target system requires the controlled assignment of target requests to source requests. This allows you to synchronize the customizing data of a transport request in the source system, with transport requests in the target systems and client.



The assignment only applies to open requests in the source and target systems; released requests are no longer offered for assignment.

There can only be one active assignment pair per system-client combination, i.e. one source and one target request with the status „open“.

The assignment must be transport request type-specific, i.e. you can only assign customizing requests to customizing requests and workbench requests to workbench requests. You need workbench requests to distribute cross-client customizing.

If necessary, you can assign several source requests to a target request; but not vice versa.

Procedure

Automatic distribution with minimal administrator/user intervention By default, i.e. without previous assignment of source and target transport requests, Customizing Distribution uses the first open target request in which the user has an open task. If no such request is found, the user is prompted to create and assign a request or task. The correct project is proposed automatically.

Assign requests centrally before Customizing Distribution This option is appropriate if the transport requests are to be assigned centrally by an administrator.

Prerequisites:

For project-specific distribution, the requests to be assigned have been assigned to the customizing projects in the source and target system.

To make assignments, the user must have at least one task in the source and target transport requests. ...

1. Choose an active distribution by double-click in the customizing distribution setup.

� Choose Edit → Assign Transport Requests. The source and target systems and clients of the selected project open requests in the source and target systems, and existing assignments of open transport requests for the system-client combination are displayed.

2. Choose the target request to assign, in the Requests in Target System box, and Drag and Drop it from the folder icon to a request in Requests in Source System.

User request assignment during Customizing Distribution 3. If your use scenario does not allow complete central assignment of transports, for

organizational reasons, the user can make the assignment during Customizing Distribution, or it can be made automatically. If you have selected the option Always Confirm Target Request with Edit → Expert Settings, in the Customizing Distribution detail screen, you can help the customizers to select the correct target request. The request is assigned as follows:

4. Option is active

5. If the user has a free request with an appropriate free task in the target system, it is assigned automatically in the background. Otherwise he can select or create a request in a dialog.

6. Option is not active

7. If the user has a free request with an appropriate free task in the target system, it is assigned automatically in the background. If the user has no task in the free request, he can select a transport request in a dialog. If there is no target request, a check is made whether the user in the target system is assigned to another open request, and if so it is assigned in the background. If the check does not find another open target request, you can select another target request in a dialog.



Put the developments in several source requests into one target request Proceed as described under Assignment Request Centrally before Customizing Distribution or Assign Request during Customizing Distribution, to make multiple assignments.

Result The assigned request appears in the transport request assignment under the selected option. Transport assignments which are made during Customizing Distribution appear in the transport request assignment overview.

Once you have saved, you cannot cancel or delete the assignment. If a request has been incorrectly assigned, you can overwrite the assignment with a new request.

Synchronization Group Editor

Use With this editor, you can define groups of customizing objects (synchronization groups), which you want to adjust with the Customizing Distribution [page 200], or compare with the Customizing Scout [page 230].

Prerequisites You have authorization for the authorization object s_cd_sync for the synchronization group editor, you need activity 3 for calling, activity 2 for changes (for the system roles 'Development/Customizing', i.e. scdtsysrol = 'c').

Features With the editor, you can

• create

• edit

• copy

• delete and

• transport synchronization groups.

A synchronization group can comprise the following objects:

• Customizing objects which are predefined in the system as synchronization-relevant for a software component (Synchronization Objects [page 206])

The system contains information about which customizing objects in SAP R/3 correspond to these synchronization objects (mapping).

• Customizing objects which you select by IMG activity

• Customizing objects whose object name and type you enter manually

• other synchronization groups

You can select customizing objects of type V (view), S (table with text table) T (transaction), L (logical transport object) or C (view cluster) for a synchronization



group. The system resolves view clusters into individual views, and objects of type T and L into their underlying tables.

If you select customizing objects, the system checks whether these objects exist in the Implementation Guide (IMGs) of the source and target systems, and gives an overview of any objects which could not be put in a synchronization group. You can also check in advance, which customizing objects or IMG activities are suitable for Customizing Distribution. See the notes in the Restrictions section in Customizing Synchronization [page 195].

You can also specify filter conditions for your synchronization group. You specify whether table rows are only to be taken into account by the Customizing Scout or Customizing Distribution, if specified fields satisfy conditions which you define. You can also put customer tables in a synchronization group. You must either put these tables in the table SOBJ (transaction sobj), or create the customer tables as Synchronization objects [page 206] with appropriate mapping.

Synchronization Group for Stand-Alone HR

Definition A set of customizing objects predefined by SAP, which must be synchronized in a system landscape comprising an SAP HR system and an SAP non-HR system.

Use The synchronization groups for SAP HR can be used in a "stand-alone HR" (i.e. in the standard situation that you want to use one SAP R/3 as your HR system, and one other SAP R/3 as non-HR system). The "stand-alone HR", with one HR system and one non-HR system is divided into scenarios, of which a customer uses some. There are one or two synchronization groups predefined by SAP for each scenario.

Structure A synchronization group comprises predefined synchronization objects [page 206] for the software components SAP_HR and SAP_APPL. Each synchronization object corresponds to a customizing table in SAP R/3, which must be synchronized for one or more scenarios in an HR and a non-HR system, so that data replicated by ALE is interpreted correctly in the system.

There are various types of synchronization group:

The synchronization groups HRCA-Kapseln and HR-ALE-Grundtabellen contain the basic settings per synchronization direction. The ALE distribution is based on the basic tables, and they should be synchronized, independently of the scenarios used. These two synchronization groups are in the template COPY_FOR_USE (for distribution from non-HR to HR systems) and COPY_FOR_USE_A (for distribution from HR to non-HR). You can copy the groups into your namespace (and edit them there), and then also copy the groups for your scenarios there, with Drag&Drop.

Some stand-alone HR scenarios require certain info types. Synchronization group info types, which begin with IT, exist for this purpose. The synchronization group IT <nnnn> belongs to info type <nnnn>. These synchronization groups are subgroups in the scenario synchronization groups.

There are also three synchronization groups for message types:

• COAMAS (Customizing for the replication of activity types)

• COELEM (Customizing for the replication of cost elements)

• COELEM (Customizing for the replication of cost centers)



These synchronization groups are already in the ALE scenario synchronization groups which require master data replication.

See also:

Overview of ALE Integration Scenarios [external link]

IMG documentation for ALE-IMG: Transaction SALE, IMG path: Model and Implement Business Processes → Configure Predefined ALE Business Processes → Personnel → HR <-> LO or HR <-> AC and Model and implement Business Processes → Configure Predefined ALE Business Processes → Auto-Customizing.

Using Synchronization Groups for Stand-Alone HR

Purpose This process uses synchronisation groups predefined by SAP to compare and synchronize customizing in "stand-alone HR" (one HR and one non-HR system). The stand-alone HR is divided among various ALE scenarios. You can use one or more synchronization groups for each of these scenarios. If you use these synchronization groups, you do not have to find out yourself, and manually specify, which customizing objects you need for the various ALE scenarios.

The process describes a standard situation, in which you have one HR and one non-HR system. If you use a different system landscape, you must create your own appropriate synchronization groups with the synchronization group editor.

Prerequisites You have checked which scenarios you are using for the stand-alone HR. You can do this with a test program in the ALE implementation guide (ALE IMG), under Model and Implement Business Processes → Configure Predefined ALE Business Processes → Auto-Customizing, which checks which settings are active in the IMG, and shows which interfaces are being used.

Process Flow ...

1. Start the synchronization group editor.

The editor displays all the SAP predefined synchronization groups.

2. Choose the synchronization groups COPY_FOR_USE and COPY_FOR_USE_A, and copy them.

The system copies the synchronization groups into the customer namespace. You can now edit the copies. Both synchronization groups already contain synchronization objects for general settings.

3. You choose the predefined synchronization groups which match the interfaces which you have implemented.

The synchronization groups have the same name as the corresponding interfaces which were named in the IMG for ALE.

4. Drag & Drop the selected synchronization groups into the synchronization groups created in step 2, taking account of the synchronization direction.



Result You can use the synchronization group to compare the customizing between an HR system and a non-HR system with the Customizing Scout [page 230], or distribute it with the Customizing Distribution [page 200].

Create Synchronization Group

Use A synchronization group contains a set of customizing objects which you want to compare later in two systems with the Customizing Scout, or synchronize in a system landscape with the Customizing Distribution.

Prerequisites You have satisfied all the Customizing Distribution prerequisites [page 197]. You are in the Customizing Distribution setup [page 217].

Procedure

Create Synchronization Group ...

1. Call the synchronization group editor with Goto → Synchronization Group Editor.

You can also call the editor with Tools → Customizing → Distribution → Synchronization Groups in the SAP menu.

2. Choose Create.

3. Enter a technical name in your namespace, a source and target component, and a descriptive short text, in the dialog box.

When you create a synchronization group, assign it to the correct source and target components. The source system from which you want to distribute customizing must contain the software components which you specify under source component. The target systems into which you want to distribute customizing must also contain the software components which you specify under target component.

The source and target component possible entries help displays all existing software components in the system landscape.

4. Specify a source and target system in the dialog box.

The synchronization group editor accesses the Implementation Guides (IMGs) of these systems.

5. If no existing synchronization objects flag is set in the dialog box, load these objects with the Load Object Lists pushbutton.

6. If you want to restrict the object selection from the SAP Reference IMG to one project IMG, set the Project Selection from Project IMG flag and choose the customizing project with the same name from the list of SAP Solution Manager projects, if there is one, or specify the customizing project manually if there is no list.

7. Choose Continue.

8. Specify a package in the following dialog box, and choose Save.



The system displays the new synchronization group in the right-hand frame. You can now put objects in the synchronization group.

Insert customizing objects based on IMG activities ...

1. Choose the synchronization group by double-click in the list in the left-hand frame.

2. Go to edit mode for the synchronization group.

3. Click on the synchronization group with the right-hand mouse key.

4. Choose Insert Objects from the Target IMG or Insert Objects from the Source IMG, in the context menu. If you selected the Project Selection from the Project IMG flag when you created the synchronization group, the selection of IMG activities is restricted to the project IMG.

5. If a logon screen appears, enter your user name and password for the source or target system.

The system displays the source or target system IMG in a dialog box.

6. Mark one or more IMG activities and choose Continue.

The system checks whether the IMG activities have synchronization objects, and if so replaces simple customizing objects with synchronization objects.

7. Confirm the system message that customizing objects have been replaced by synchronization objects.

The system checks whether the customizing objects are in the Implementation Guides of the source and target systems, and sends a message if not

Customizing objects which do not satisfy the check are displayed in a dialog box, and not put in the synchronization group.

8. Choose Continue.


Search for and insert customizing objects by technical name ...

1. Choose the synchronization group by double-click in the list in the left-hand frame.



4. Choose Insert Customizing Object from Target, in the context menu.

5. The system displays the first 500 alphabetically sorted customizing objects in the target system.

6. To search for more customizing objects, click on Restrictions with the right-hand mouse key, and search. You can also search for customer objects, if they are in the table SOBJ

7. Choose Continue.

The system checks whether the customizing objects are in the Implementation Guides of the source and target systems, and sends a message if not

Customizing objects which do not satisfy the check are displayed in a dialog box, and not put in the synchronization group.

8. Choose Continue.


Put synchronization objects in a synchronization group ...

1. Choose the synchronization group by double-click in the list in the right-hand frame.





4. Choose Insert Synch. Objects <target component release> in the context menu.

The system displays all synchronization objects predefined by SAP for the target component and the release, in a dialog box. The descriptions of the IMG activities in the synchronization objects are also displayed.

Choose Goto → Display Synchronization Objects for further details about displaying synchronization objects [page 207].

5. Mark a synchronization object and choose Copy.


Result The system lists all objects which you have put in the synchronization group, in the right-hand frame. The Type column indicates whether it is a synchronization object predefined by SAP, with table and field name mapping information, or a simple customizing object. The views belonging to view clusters, and the tables belonging to customizing objects of type T or L, are displayed in the list. The IMG activity short text is displayed in the Description column.

You can now:

• Insert existing synchronization groups as subgroups in your synchronization group with Drag & Drop

• change the structure of your synchronization group by moving objects with Drag & Drop.

Changes to a synchronization group affect all uses of it.

• Document the synchronization group with Synchronization Group → Change Documentation

• Specify Filter conditions [page 215] for the synchronization group

You can also later identify and delete customizing objects which are not in the source and target system, from the synchronization group, with Edit → Check. You can also delete all customizing objects which are not for Customizing Distribution, from a synchronization group, with Edit → Delete Non BC Set-Compatible Objects.

Specify Filter Conditions

Use you specify filter conditions for a synchronization group or a customizing object if you only want to take individual table rows into account for the comparison or distribution of customizing. The fields in these table rows must satisfy these filter conditions.



Prerequisites You have selected a synchronization group for processing.

Procedure ...

1. Mark either the root node of the synchronization group or a customizing object, with the right-hand mouse key.

2. Choose Filter Conditions in the context menu.

The system displays a dialog box.

3. If you have selected the entire group, enter the customizing object for which you want to define filter conditions, in the Customizing Object column in the dialog box.

4. Enter the fields for which you want to define filter conditions, in the Field Name column.

5. Choose an operator. Notes:

� Pattern: All characters in the field must match the template. The meta-characters '_' (one character) and '%' (any number of characters) are allowed.

� equals, not equal, less than, greater than, between, below lower limit, above upper limit, using the ASCII table character sequence. Only specify values of type char and int as constants.

6. Specify one or two constants per operator, as required.


Types of Customizing Distribution There are the following types of customizing distribution:

• Initial distribution For the initial delivery of customizing data for selected customizing objects in an active customizing distribution, to a system. Transport recording in the source system is not necessary.

• Automatic customizing distribution To distribute changed customizing objects. In contrast to initial distribution, only the changed (and in the transport request) entries of a customizing object are distributed, not all.

• Manual distribution of a transport This is useful after a distribution error, if the customizing data of a particular transport request needs to be distributed again.

Initial Distribution

Use Initial distribution performs a one-off transfer of customizing from a source system into target systems.



The customizing is written into the target system tables without a foreign key check.

Prerequisites You have satisfied the prerequisites described in Set-Up Automatische Customizing Distribution [page 217].

Procedure 8. Choose Tools → Customizing → Distribution → Setup Customizing Distribution in the

SAP menu, or call the transaction scdt_setup.

The system displays all synchronization groups which are flagged for Customizing Distribution, and their projects and source systems.

9. Choose Create.

You go to a dialog screen, in which you can enter the Customizing Distribution data.

10. If you want to restrict the distribution to certain objects, specify a synchronization group.

If you do not specify a synchronization group, all objects which are predefined as synchronization objects [page 206] by SAP, are distributed.

11. Choose the Distribution Type No Automatic Distribution.

12. Specify a logiscal system, from which the customizing is to be distributed into the other systems, under Source System.

13. Enter the target logical systems in the Target Systems table.

The system displays the logical systems which have been created for this project in the SAP Solution Manager Project Administration [page 22], in the possible entries help.

14. Choose the Initial Distribution pushbutton.

Result The data is transferred from the source system into the target systems. You can now release the associated transport requests, to transport the data, for example, into a quality assurance.

The initial distribution does not save the data you enter, but you can setup an automatic Customizing Distribution [page 217] directly after the initial distribution and save, to distribute all changes to customizing objects in the source system into the target systems.

Setup Automatic Customizing Distribution

Use You want to flag a synchronization group in the SAP Solution Manager for Customizing Distribution. This ensures that all changes that you make in the customizing of a source system are distributed into target systems.

If you want to reconcile the customizing in a source system with the customizing in target systems initially, before distributing customizing changes, perform an Initial Distribution [page 216].



Prerequisite You have made all necessary System Settings for the Customizing Distribution [page 197]. If you want to distribute customizing in a project with the SAP Solution Manager, you have setup a project with a system landscape in the Project Administration [page 22]. The system supports Customizing Distribution for implementation projects in the SAP Solution Manager.

If you want to restrict the customizing distribution to certain customizing objects, you have created a synchronization group in the Synchronization Group Editor [page 210]. A synchronization group is a group of customizing objects which must be synchronized. If you do not specify a synchronization group, Customizing Distribution is setup for a set of customizing objects, pre-defined by SAP, which are to be synchronized for the components in your project system landscape (synchronization objects).

If you create a new distribution, you can to the synchronization group editor or the system landscape maintenance by double-clicking on the synchronization group or the systems.

Procedure ...

� Choose Tools → Customizing → Distribution → Setup Customizing Distribution in the SAP menu, or call the transaction scdt_setup.

The system displays all synchronization groups which for which Customizing Distribution has been setup, and their projects.

1. Choose Create.

You go to a dialog screen, in which you can enter the Customizing Distribution data.

2. If you want to restrict the distribution to certain objects, specify a synchronization group.

If you do not specify a synchronization group, all objects which are predefined as synchronization objects [page 206] by SAP, are distributed.

3. Specify:

� whether customizing is to be distributed for all transport requests which have been created for SAP Solution Manager projects in the source system

� whether customizing is to be distributed only for the transport requests for a particular SAP Solution Manager project, and specify a project name.

4. Choose a distribution type:

� Timed Distribution: The Customizing Distribution is scheduled as the job CUSTOMIZING DIST. for <project name>, in the background, at the times which you specify.

� Synchronization by Transport Release: Each time a transport request belonging to the project is released, the relevant customizing is distributed.

� Synchronization by Transport Changes: Each time a transport request belonging to the project is released or changed, the relevant customizing is distributed.

5. Specify a logiscal system, from which the customizing is to be distributed into the other systems, under Source System.

The SAP Solution Manager displays the system, client, RFC destination, Basis release and Support Package automatically, after you specify the logical system. It checks whether the release and Support Package status is sufficient for the distribution type which you selected, and switches to timed distribution if this is not the case.

6. Enter the target logical systems in the Target Systems table.

The system displays the logical systems which have been created for this project in the SAP Solution Manager Project Administration [page 22], in the possible entries help.



You can test the RFC destinations in your system landscape in Customizing Distribution via Goto → Test RFC Destinations.

7. If you want the customizing in the target system to be locked for changes after the customizing distribution, set the Lock Editor in Target System flag.

For further information about the lock mechanisms in the Customizing Distribution,see under: Customizing Distribution Lock Logic [page 228].


Result The system checks whether:

• all selected systems exist and are reachable

• the objects in the synchronization group are appropriate Customizing Distribution

• the required RFC connections exist

• customizing is already distributed for this project and source system via another central system.

If the checks are passed, the customizing distribution distributes all changes to customizing objects in the synchronization group, from the source system into the target systems (development systems only). You can now transport these customizing changes into quality assurance and production systems, by releasing the associated transport requests.

Distribute Individual Transport Manually

Use You want to make the customizing which was changed in your source system by an individual transport, once, automatically in your target systems as well.

Prerequisite You have made the necessary System Settings for the Customizing Distribution [page 197]. You have a task in the transport requests of the systems involved.

You are in the Customizing Distribution setup.

Procedure ...

1. Choose Goto → Distribute Transport Manually, or the transaction scdt_fetch.

You can also distribute customizing manually from the Customizing Distribution Log display.

2. Enter the transport request task containing the customizing changes which you want to distribute.

3. Enter a project for this transport request.

The project tells the system the system landscape in which customizing is to be distributed, and the associated transport requests in the target systems.



4. Enter an RFC destination for the source system, from which you want to distribute the customizing into the target systems.

5. Choose Distribute Transport Request into the Target Systems.

Result The customizing changes from the source system, which are in the transport request, are also made in the target systems.

Logging Customizing Distribution

Use The Customizing Distribution logging gives an overview of successful and failed customizing distributions. It reveals sources of error in failed customizing distributions and can restart Customizing Distribution manually.

Features You can examine all Customizing Distribution logs and traces. You can display:

• Logs of a customizing distribution, with its system messages

• Business Configuration Sets which were activated for a customizing distribution

• Business Configuration Set activation logs

• Logs of distribution-relevant procedures in the SAP Solution Manager system (Trace Display [page 221]).

You can search for logs by the following selection criteria:

• Project

• Target system

• Target transport requests used (in the logging initial screen under Goto → Target Transport Requests Used)

• Transport request or initial distribution

• Time periods

• User.

You can also:

• Restart failed customizing distributions

• Check RFC destinations

• Go to the following data in the detail display: Synchronization group, Transport request, Project, System landscape

• Perform Customizing Distribution analyses [page 222]: Search for customizing objects, transport requests, and their logs.



Display Trace of Incoming Distribution Requests

Use The trace display displays all logged procedures in the system which were called by Customizing Distribution. It supports troubleshooting if a customizing distribution failed.

Sie haben Various Customizing Distribution analyses [page 222] also help you to identify errors.

Integration All procedures which are called by the Customizing Distribution in the SAP Solution Manager system are logged by trace.

Features With the trace display you can:

• see all distribution requests received in the SAP Solution Manager system

Distribution requests arise when customizing has been changed in the source system and written into a transport request. The SAP Solution Manager system checks whether these customizing changes are also relevant for target systems in a project.

• display Customizing Distribution logs which have been created for a transport request in a source system

• display source transport requests to a Customizing Distribution

The trace display includes the following data:

• Transport request

• Customizing Distribution source system

• Time of distribution request

• User who made distribution request

• Number of customizing objects changed

• Number of target systems into which customizing objects have been, or are to be, distributed

• Last Customizing Distribution action or error message

Activities ... ...

1. Start the trace display with Goto → Trace Display in the Customizing Distribution log menu.

2. Find the transport request whose customizing distribution you want to check, in the display.

3. Check whether the Customizing Distribution is flagged as successful.

4. If there is a log for the transport request, double-click on it.

5. If there is no log, display the last action in the system, or the error message in the overview, and check possible causes of error.

If no log has been created, no customizing was distributed. This can be because:



Customizing was changed in the source system, but the change is not distribution-relevant, because, for examplw, the customizing objects are not in any synchronization group.

The Customizing Distribution found no target system.

Analysing Customizing Distribution

Use You can use these functions to search in the Customizing Distribution setup or logging for individual customizing objects or transport requestss, and display their logs. This is useful if errors occur in the Customizing Distribution. You can use the analyses to trace the course of individual distributions and find the causes of errors.

Prerequisites You have setup Customizing Distribution. You are in the Customizing Distribution log selection initial screen.

Features

Display all active objects You can display a list of all objects for which Customizing Distribution is active with Goto → Display alle Active Objects.

You can display:

• the definition of the associated Synchronization objects [page 207]

• the associated synchronization group in the Synchronization Group Editor [page 210]

• the associated project in the Project Administration [page 22]

You can also call this list from the Customizing Distribution setup.

Display transport requests used You can display a list of all transport requests which were used in a Customizing Distribution, with Goto → Transport Requests Used. Using the filter and sort options, you can, for example, determine:

• which source system transport request supplied a target system transport request?

• into which target system transport request have the contents of a source system transport request been passed?

You can display:

• all logs for a target request

• the target or source transport request in the transport system

• Project Administration [page 22] project data for the associated SAP Solution Manager project.

Display distributed objects You can display a list of all objects which were distributed in a system landscape by the Customizing Distribution, with Goto → Distributed Objects. The display is initially filtered by the period which was specified in the Customizing Distribution logging initial screen. You can:



• sort the display and filter by other time periods

• display the technical details of a Synchronization object [page 207]

• go directly to the IMG activity for the object (source or target system)

• display the associated source transport request

• display all logs for a selected object in the selected time period.

The system shows all logs of the object and all logs which were distributed with this object in a comparison, so the display can include logs in which the selected object is not mentioned.

Automatic Redistribution after Errors

Use Tthis function restarts customizing distributions which failed, automatically in the background.

Prerequisites You have a task in the transport requests of the systems involved.

Features From the time that redistribution is scheduled, all customizing distributions for a project are collected, which:

• contain errors

• were cancelled.

Customizing distribution which have been successfully redistributed are excluded. This distributions are redistributed at times which you specify. You can schedule redistribution periodically in the background.

Activities ...

1. Call the Setup Customizing Verteilung transaction.

2. Choose an active synchronization group and ist project, and choose Display or Edit.

3. Choose the Edit → Automatic Redistribution after Errors menu.

4. Enter the background job scheduling data.

The system schedules the background job DISTR. CORRECTION <project name>.

5. The system redistributes the project according to your specification.

Display Customizing Distribution Logs

Use You have distributed customizing in your system landscape and want to check in the logs whether the distribution was successful.



Prerequisites You are in the Customizing Distribution setup [page 217].

Procedure

Select logs ... ...

1. Choose Goto → Distribution Logs or call the transaction scdt_log.

The system displays the Customizing Distribution Log Selection dialog screen.

2. You can restrict the log selection with one or more selection conditions.

3. You can set the flag that only logs since the last complete distribution are displayed.

You should set the flag. A successful, complete distribution of a transport request usually makes older logs obsolete. The overall status of a distribution in the log overview structure reflects the worst individual result of all displayed logs. If you display the obsolete logs, they affect the overall status of the distribution in the log overview. So the overall status can be 'error', although all objects have been distributed successfully by a more recent distribution in the meantime.

4. Choose Display Logs by Selection or Only Display Logs with Errors.

The system lists all logs in your selection.

You can skip the Customizing Distribution Log Selection dialog screen next time you call the logs, if you set the corresponding flag. You can change the settings again later with Edit → Options.

Display log ...

1. To find individual logs for a date, navigate through the structure in the left-hand frame.

2. Double-click on the date in the left-hand frame.

The system displays all messages in the log, in the right-hand frame.

3. Proceed as follows:

� To display the message long text, click on the question mark after a message.

You can find Customizing Distribution logs which are not assigned to a project with *.

� To display the logs for all target systems into which the customizing in a transport request or an initial distribution has been distributed, choose Display Associated Logs.

� To display the activation logs of a Business Configuration Set which was activated for a Customizing Distribution, choose Display BC Set Activation Log.

Reload log • To reload one log, select it and choose Reload Log.

• To display logs which have been generated in the meantime, choose Load New Logs.



When you load new logs, logs which are already displayed are not refreshed, even if they have been changed.

• To reload all logs and load any additional logs, choose Refresh All.

Result You have displayed the logs. You can now:

• Redistribute customizing for a transport request manually [page 219]

• delete several logs with Goto → Delete Logs.

Delete Customizing Distribution Logs

Use You delete obsolete logs to get a better overview of the current logs in the log display. Obsolete logs include all logs for which more recent logs of the following type exist:

• a more recent log shows that the associated synchronization group has been successfully distributed in an initial distribution.

• a more recent log shows that customizing has been distributed completely and successfully in a transport request (either completely by a transport release, or by the complete manual distribution of the transport request [page 219]).

You can delete non-obsolete logs individually in the log display.

Prerequisites You have authorization for the authorization object S_APPL_LOG, with the following field values: Object = cust_sync, Subobject = distrib, Activity = 6 (Delete).

You are in the Customizing Distribution logging initial screen.

Procedure ... ...

1. Choose Goto → Delete Logs in the menu, or call the transaction SCDT_LOG_DELETE.

2. You can restrict the log selection with one or more selection conditions:

3. Choose Delete Logs Immediately or Create Selection List.

Delete Logs Immediately deletes all obsolete logs which satisfy your selection.

Create Selection List lists all obsolete logs which satisfy your selection.

4. If you have selected Create Selection List, mark the logs which you want to delete, and choose Delete Selected Logs.

5. Confirm the prompt.

Expert Customizing Distribution See the following topics for further information:



• Distributing Languages [page 226]

• Expert Settings [page 227], e.g. administration of transport requests

• Lock Mechanism Overview [page 228]

• Detailed Local Lock Information [page 228]

Distributing Languages

Use You can distribute the translations of, for example, a customizing view, as well as the entries in the logon language. The distribution logic depends on the distribution types. You can distributie translations of standard customizing objects (view, view cluster, tables with text tables) and non-standard objects (individual transactions, logical transport objects).

Integration To transport distributed texts with their translations through the development landscape, i.e. from the development to the quality assurance to the production system, the transport system option which transports customizing entries independently of the original language, must be active. This option is active by default when an SAP systems is delivered.

Features Initial distribution

• The initial distribution distributes all languages for which the texts are not identical in the logon language in the source and target, or do not yet exist for the key in the target.

• If the data is the same in the logon language in the source and target systems, it is not distributed again. So translations which exist before initial distribution are not distributed.

You can still distribute these texts by selecting another language for the initial distribution. If the translations are not yet in the target system, they are distributed.

You can also change the texts in the logon language and then distribute them with their translations. Then change the text back to its original status.

• Deletions of entire data records (texts and their keys) or only texts can only be distributed for the logon language. If you delete the entire data record, you no longer have access to the other languages into which the texts have been translated, because the access key no longer exists.

Delta distribution

The delta distribution (distribution at transport release, transport recording, timed distribution), texts are distributes in all languages if they are put in a transport request as new or changed.

You can distribute the missing translations by changing them and putting them in a transport request explicitly. You may have to discard the changes later. Here too, only entries changed in the logon language or explicitly changed translations are distributed. Unchanged, and therefore not recorded, translations are not distributed.

Deletions are here also only distributed for entire data records or texts in the logon language. Deleted translation texts must be put in the transport request explicitly to be distributed. When



entire data records are deleted, you can no longer access their translations because there is no access key any more.

If you want to delete a data record and its translations, delete the translated texts first, and then the entire data record.

Expert Settings

Use You can control the interaction between Customizing Distribution and the user, in the expert settings.

Features You can make the following expert settings:

• Always Confirm Target Request: You are always prompted to confirm the target system request – regardless of whether one has already been assigned. You can then:

� confirm the target request

� assign a different target request

� create a new target request

The last two options affect the transport assignment: a new, project-specific transport assignment is made. See also: Assign Transport Requests to Source and Target Systems [page 208]

• User Debugging: Activate debugging for one or more users. The debugger is called automatically whenever the SAP Solution Manager is called from an external system, e.g. source system.

• Distribution in the background: (default) If a user saves several entries in a customizing object, several processes process them in parallel in the background. This ensures that the user can proceed without delay in synchronization by transport release in the source system, without waiting for the distribution to end. The same applies if several users save in the same source transport request.

• Send message to user in source system in case of error (default) The customizer in the source system is informed directly of Customizing Distribution errors, if he is still logged on. If the customizer is no longer logged on, distribution errors are logged in the Customizing Distribution log.

Activities To change the expert settings, choose Edit → Expert Settings in the Customizing Distribution initial screen for an active distribution szenario.



Customizing Distribution Lock Logic The Customizing Distribution uses various mechanisms to lock customizing in the target client. For all locks:

• You can only lock standard customizing objects (views, view clusters, tables with text tables).

• The locks are target client-dependent.

Customizing locks (SCDT_LOCK)

Local locks

• Use: Lock customizing objects against changes in the target system, locally, without distributing customizing. For further information, see: Insert Local Locks for Customizing Objects [page 228]

• For the prerequisite SAP Basis or SAP WAS Support Packages in the component systems: See SAP note 753005

Customizing Distribution (SCDT_SETUP)

BC Set lock

• Lock distributed entries field-wise, if the editor lock for the target system is set at distribution

• Use: Transport-controlled distribution (automatic customizing verteilung, delta distribution, distribution of individual transports), not initial distribution

Lock Customizing Distribution (remote lock) with flag „Lock Editor in Target System“

• The customizing objects are locked in the target client, possibly filtered.

When local locks have been set-up in the same target client by customizing locks, they replace the remote lock for performance reasons.

Example: You have four synchronization groups, A, B, C and D, which are used actively in customizing distributions, in the same target client Z. Synchronization group A also has a local lock in target client Z. The local lock replaces the lock logic for B, C and D, as well as the explicitly selected synchronization group A, for performance reasons.

• Use: All distribution types, whether transport-controlled or not

• For the prerequisite SAP Basis or SAP WAS Support Packages in the component systems: See SAP note 628690

Local Locks for Customizing Objects

Use Local locks lock standard customizing objects (views, view clusters, tables with text tables) in the component systems against further maintenance. You specify the customizing objects to be locked in a synchronization group, and distribute the information to the systems to be locked. Local locks are independent of the availability of the SAP Solution Manager.



Possible use scenarios:

• You use the Customizing Distribution and the lock functions together. You can use the same synchronization group for the Customizing Distribution and to lock the customizing objects in the synchronization group locally. In this case, customizing only gets to the component system centrally, in the Customizing Distribution.

• You only use local locks, without using Customizing Distribution.

In all scenarios, you can also filter local, non-maintainable customizing for key fields. For further information about the interaction of the various lock mechanisms in Customizing Distribution, see: Lock logic in Customizing Distribution [page 228]

Prerequisites You are authorized to set-up local locks as system administrator and customizer in the SAP Solution Manager system, and in the component systems

Notes:

Note no. Authorization in system Authorizations

566922 Satellite system For Customizing Scout and system landscape

625773 SAP Solution Manager System

Role SAP_SOL_AC_COMP or at least subrole SAP_SCDT_ALL

The authorizations have company-specific values.

Procedure ...

1. Define the synchronization group with the objects which are to be locked or explicitly released, in the synchronization group editor. If you only use the synchronization group for locks, you can specify the same logical system for the target to be locked, in the source and target reference systems.

You can only lock standard customizing objects.

2. Choose Goto → Set-Up Customizing Locks, in the Customizing Distribution initial screen.

3. Choose the synchronization group.

4. Choose the targets for the locks. The standard customizing objects in the synchronization group are locked against changes, in the target system. If you filter the customizing objects, only the filtered entries are locked (analogously to Customizing Distribution).


If you change a synchronization group after activating a lock (e.g. by adding a new object or a filter), the lock is automatically refreshed.



Result You can see actively locked objects by selecting the lock entry and choosing Goto → Display Active Locks in the Target System. If you lock by filter, you can see the filter by double-clicking on the field. You can go to the IMG activity in the target system containing the customizing object, by double-click on the IMG activity.

You can see not, or only partially, lockable objects in a synchronization group, with Goto -> Display Synchronization Group.

Customizing Scout

Use This tool compares customizing objects in a system in a SAP system landscape with customizing objects in SAP R/3.

Certain customizing objects which must be synchronized in a development landscape, are predefined in the system for selected components (Synchronization Objects [page 206]). You can select synchronization objects and other customizing objects for the comparison with the Synchronization Group Editor [page 210].

The system which is the reference for a comparison is also referred to below as the source system in the SAP system landscape. This is an SAP R/3 System. All other systems in your SAP system landscape are referred to as target systems and are only compared with the source system.

Integration The comparison helps you to synchronize the customizing settings when implementing or updating a system landscape. You can use the comparison to eliminate differences in the customizing settings of the systems, for example by using the IMG implementation guide or the Customizing Distribution [page 200].after the comparison.

Prerequisites

System landscape, authorizations and RFC connections You fulfilled the Prerequisites [page 197].

Security The protection levels must be set to one of the following values for the comparison source and target systems:

• 0 (unrestricted)

• 1 (no overwriting)

You can set this in the client maintenance. For further information, see Maintain Clients and Logical Systems [external link] and the F1 help in Client Maintenance.

Features

Select system landscape Before you make a comparison, you can choose the system landscape in which it is to be made:

• a system landscape defined in a project in the SAP Solution Manager



• the entire transport domain.

If you select the entire transport domain, all comparisons are displayed, regardless of which project they are assigned to.

Comparisons You can display or make comparisons as follows:

• display, edit and delete existing comparisons

• compare a target system with a source system in dialog or in the background

• compare several target systems with a source system in the background

• compare one or more target systems periodically in the background

You can also create comparisons only for systems whose customizing is compared with the Customizing Distribution [page 200].

Display comparison result You can choose between several views of the comparison result:

• Comparisons in the system landscape: You get an overview of all systems which you have selected for comparison. You can also examine all existing comparisons for each system in a list.

• Object Overview: You can list all compared objects and their comparison and processing status for a system.

• Object comparison: You can select a customizing object in the object overview and make and analyze a detailed comparison of the field entries.

Utilities and other functions in the object overview:

• display a comparison log for missing comparisons which were cancelled

• change the processing status of specified objects

• filter the object display by processing status, comparison status and object type

• select objects and go to the corresponding IMG activity in the source or target system to make changes.

Load Object Lists

Use Before you can make a comparison between an application component (e.g. SAP MDM) and an SAP R/3, you must give the Customizing Scout the list of customizing objects to be synchronized in your system landscape. These object lists are delivered with some application components. If you download the object lists from the application component into the SAP Solution Manager system in which the Customizing Scout is running, it can access the object lists.

For further information about components for which piece lists are delivered, see Synchronization Object [page 206].



Prerequisites You have satisfied the prerequisites under Customizing Scout [page 230], in particular, you have created a system landscape. You also need the following authorizations to load object lists:

• activity (ACTVT) 02 for authorization object s_cd_sync

• the authorization fields sysdlvunit, project_id and scdtsysrol are not checked, so you only need authorization for a project, a system category (e.g. development system, production system) and an application component.

The authorizations are also in the predefined roles in the SAP Solution Manager. You can also use the above authorizations.

Procedure ...

1. To start the Customizing Scout, choose Tools → Customizing → Distribution → Customizing Scout in the SAP menu, or enter the transaction scout.

2. Choose Extras → Object Lists.

3. Enter the logical system from which you want to download the object lists, in the following dialog box.

If you have already downloaded an object list, you can set the Only New Objects flag and only new objects, which are not yet in your object lists, are downloaded.

4. Choose Continue.

Result The system downloads the object list and displays an overview showing:

• for which logical system object lists have been downloaded

• how many objects were changed at the last download

• how many objects were changed at the last download.

Compare Customizing

Use You have an SAP system landscape with an SAP R/3 System and at least one other system, for example SAP MDM. You want to compare the customizing in one or more target systems with the customizing in a source system.

Prerequisites You have created a system landscape and possibly a synchronization group, as described under Customizing Scout [page 230] Prerequisites.

You must download the list of customizing objects to be synchronized from the application system [page 231] before the first comparison. You can only then use the Customizing Scout.

Use the authorizations in the SAP Solution Manager roles for the comparison.

Procedure ...

1. To start the Customizing Scout:



� Choose Tools → Customizing → Distribution → Customizing Scout in the SAP menu.

� Enter the transaction SCOUT.

The system displays the Customizing Scout initial screen.

2. Choose a system landscape and one or more system roles.

You can choose a project in the SAP Solution Manager from the possible entries help. The system then uses the project system landscape for the comparison.

3. Choose Display Selection.

The system shows you a list of all systems which belong to your selected system landscape or to your transport domain. You can see all existing comparisons, including comparisons with systems which are not in the selected project, by double-clicking on a system.

4. To compare the customizing objects in one or more target systems with customizing objects in a source system, mark one or more target systems in the displayed list, and choose Compare.

All selected logical systems are displayed in the following dialog box. The existence of an RFC destination is checked in the background. If not, a log is displayed.

5. Specify a synchronization group [page 210] or choose all synchronization objects [page 206] for the component.

6. Enter a source system and a source client.

7. If you are only comparing one logical system with an SAP R/3 comparison system, choose comparison in dialog or in the background. If you are comparing several logical systems with one R/3 comparison system, the comparison is made in the background.

8. When you perform a comparison in the background: ...

a. Specify a server for the background job in the following dialog screen, if required.

b. Specify and save your background processing start time.

The system checks whether you have the authorizations for such a comparison and whether an RFC destination exists. If not, a log is displayed.

Result

Individual comparison in dialog A list of compared objects is displayed. Both the processing status and the comparison result for each object are listed.

Complete comparison in background When the complete comparison has been made, you can select a system and choose Refresh. You can then display this last comparison [page 234].

The system gives you an overview of all customizing objects in the target system. If you need an overview of which customizing objects in the source system correspond to the customizing objects in the target system, choose the menu Goto → Display Structure Comparison in the Customizing Scout: Object Comparison dialog screen.



Object overview The object overview shows you the technical name, and the description in the target system, of each customizing object. If the customizing object has a synchronization object [page 206], its technical name is also displayed.

Each customizing object has two status values:

• Comparison status

Type of any differences found. Assigned automatically.

• Processing status

Distinguishes between objects which have been processed and those which have not.

Processing status can be assigned manually. The next comparison changes the processing status of objects with no differences from Open ( ) to Finished ( ).

The possible status values are:

Status values

Status Symbol Meaning

Processing status Open

being processed

Finished

Comparison status Views/tables not yet compared

View/table contents are identical

View/table contents are identical and there are structure differences

View/table contents are not identical

View/table contents are not identical and there are structure differences

Cannot be compared (see below)

You can list these values in the worklist legend.

Comparison may not be possible for the following reasons:

• Process cancelled

• The user has no display authorization in the source or target system

• Communication error (RFC)

• source or target system crash

Display Last Comparison

Prerequisites The Customizing Scout has already compared customizing in the SAP R/3 with another system. You want to display the last comparison for this system. You can now either use the Customizing Scout with the authorizations as they are delivered in the SAP Solution Manager roles, or you have the authorizations described as prerequisites under Customizing Scout [page 230].



Procedure ...

1. To start the Customizing Scout:

� Enter the transaction SCOUT.

� Choose Tools → Customizing → Distribution → Customizing Scout in the SAP menu.

The system displays the Customizing Scout initial screen.

2. Choose a system landscape and one or more system roles.

You can choose a project in the SAP Solution Manager from the possible entries help. The system then uses the project system landscape for the comparison.

3. Choose Display Selection.

The system checks your authorization for the selected systems. The system shows you a list of all logical systems which belong to your selected system landscape or to your transport domain.

4. Double-click on a logical system.

The system displays the last comparisons with the source systems (if available) in the table below.

5. Choose Display Comparison Result.

You can also start processing the last comparison result by double-click on the target system.

Result A list of compared objects is displayed.

Both the processing status and the comparison status, and the comparison result for each object are displayed in this list. You can now compare one or more objects in the list or change the processing status of the objects.

See also:

Change Processing Status of a Comparison Object [page 235]

Change Processing Status of a Comparison Object

Use You have compared one or more systems with a source system (e.g. an SAP R/3 System) and changed customizing objects on the basis of this comparison. You therefore want to change the processing status of some customizing objects.

Prerequisites You have compared the customizing for a system [page 232] or you have displayed an existing comparison [page 234].

Procedure Click on the processing status of an object in the list. Repeated clicking changes the processing status again.



The possible processing status values are:

Processing status values

Symbol Meaning

Open

being processed

Finished

The processing status is recalculated after every comparison. In particular all processing statuses for objects with differences are set to Open again, even if you changed the processing status in the last comparison. If you have objects in your list which still have differences which are not relevant for your customizing, you can restrict your selection to the relevant objects with the Synchronization Group Editor [page 210].

Result You have changed the processing status of one or more objects.

Create and Load Synchronization Objects

Purpose This process creates Synchronization objects [page 206] in the system, which you want to use later for comparison with the Customizing Scout, or for Customizing Distribution. You create synchronization objects if customizing objects in different systems have the same contents, but different structures, for example different table and field names.

Prerequisites You have decided which customizing objects you want to assign to each other in a source and target component. You have checked that the objects are in the transaction SOBJ. You have checked whether the Objects are Customizing-Synchronization-Compatible [page 246].

You have set-up RFC Connections [page 240] for the synchronization object specification tool.

Process Flow

Create synchronization objects ...

1. You logon to the Customizing Distribution target system. If you want create for example synchronization objects for the software component MDM, logon to a system which contains this component.

2. Start the Synchronization object specification tool [page 238].

3. Create a synchronization object [page 240] following the following rules:

� If a table is used in several customizing objects, create a synchronization object for each customizing object.



You want to create a synchronization object for the table TSAD5. In the transaction SOBJ you find the table as underlying table in the piece list of two objects: in the view V_TSAD5 and in the object TSDAD5 (a table with text table). You create two synchronization objects – one for the view V_TSAD5 and another for the object TSDAD5.

� You put tables and views which must be transported together, in a synchronization object. For example, you combine all tables in the target system which are subobjects of a view or view cluster in the source system.

4. You can assign tables and field names to each other when you create the synchronization object. Note:

� The data types of the fields must be assignment-compatible, not necessarily identical.

� Fields are truncated if they are longer in one component than in the other.

� Data fields which are not in a component are ignored.

� All key fields of the tables and views of a customizing object must be defined for the target system. You can use any fields in the tables and views involved, for the source system.

� If several tables or views are used for the source system, the system links the records of the tables/views according to the following algorithm:

� One table is flagged as the primary table.

� The key fields of secondary tables are linked to the fields of the primary table with the same namen by an InnerJoin.

� The secondary table can have other key fields which corrspond to fields in the target structure.

� If you use a table with text table, the text field is also automatically flagged as such by the system.

� If you assign a table with text table in a source system to a view in the target system, you must Specify Source Object Filter Conditions [page 245]: You create a filter for the language field with the value $SPRAS or $SLANGU.

� If you assign a table/view to another table/view, without all fields in the source object being mapped to target object fields, you must Specify Source Object Filter Conditions [page 245]: You create a filter for the unused key fields which have a constant or generic value.

5. Check [page 245] all created and existing synchronization objects which you want to use.

Load synchronization objects ...

1. Logon to the SAP-Solution Manager system.

2. Start the transaction Synchronization Group Editor [page 210] and load the synchronization objects from the system in which you created them, into the SAP Solution Manager system.

Result The synchronization objects are now available für the Customizing Distribution and the Customizing Scout. You can now use the Customizing Distributionn [page 204] or compare cross-component customizing [page 230].



Synchronization Object Specification Tool

UseThe synchronization object specification tool (transaction scdt_mapping) is an additional customizing synchronisation tool (Customizing Scout [page 230], Customizing-Distribution [page 200]) in the SAP Solution Manager.

Customizing Scout und Customizing Distribution use a list of customizing objects which need to be synchronized in the components. These customizing objects are referred to as synchronization objects here. SAP delivers a selection of synchronization objects for various application components, e.g. SAP MDM.

Create a list of synchronization objects and their attributes with the specification tool, in the application component systems. These lists specify which customizing objects in the target component (e.g. MDM) correspond to which customizing objects in the source component (e.g. SAP_APPL) for which releases (mapping).

Use the SAP Solution Manager transaction Display Synchronization Objects [page 207] to display existing synchronization objects which you have loaded into the SAP Solution Manager system.

PrerequisitesTo use the specification tool, you need:

• RFC destinations in all systems involved: You usually use the specification tool in your application component development system, e.g. SAP MDM. You need RFC destinations for all source systems, i.e. for all R/3 Systems for which you create customizing objects.

An ideal system landscape would be as follows:



Anwendungs-komponentez.B. SAP MDM

SAPR/3 3.1

DEV

SAPR/3 4.6C

DEV

SAPR/3 Ent 4.7

DEV

Erfassen des Mappingsscdt_mapping

RFC-Verbindung

RFC-Verbindung

RFC-Verbindung

You must have set-up an RFC destination to an R/3 System; preferably to all possible R/3 releases.

• Authorization profile: You need the authorization profile s_cus_cmp for the user with which you logon to the above SAP R/3 systems. You must add some authorizations to this authorization profile; see note 383704. You also need the authorization s_tabu_all for the authorization object s_tabu_dis in your development system, e.g. in an SAP MDM system in which you use the specification tool.

FeaturesYou can create a list of all customizing objects in a system landscape which must be synchronized, i.e. have the same field entries, with the specification tool. The result is a list of synchronization objects, i.e. customizing objects which must be synchronized. Synchronization objects in a component such as SAP R/3 and in an application component such as SAP MDM, often have different table or even field names. In these cases, you can assign corresponding tables or fields with different names to each other in the specification tool. If values are to be mapped onto each other, you can specify a function module which converts source system customizing data into target system customizing data.

You can also:

• copy

• edit

• display

• restrict release validity

• sort and filter

• check the consistency

• or delete global ID types.



You can also

• document objects

• specify whether an object is only to be compared with the Customizing Scout, or can also be distributed in a system landscape with the Customizing Distribution

• specify whether an object is only to be distributed from SAP R/3 into another SAP component or in the reverse direction as well (backwards distribution)

• assign IMG activities to the objects

The assignment of an object to an IMG activity enables the Customizing Distribution users to select objects for distribution by selecting IMG activities. The assignment also permits the IMG to be linked to the Customizing Scout.

Specify RFC Destinations

UseYou must specify RFC destinations for the systems with the source and target component releases of the planned synchronization objects. This allows you to specify synchronization objects in the specification tool and perform checks.

PrerequisitesYou have created RFC destinations for your components with the transaction SM59. You are in the specification tool initial screen.

Procedure...

1. Choose Goto → Change RFC Destinations.

You go to the Change Supported Components, Releases and RFC Destinations dialog screen.

2. Choose the New Entries pushbutton or the Edit → New Entries menu.


The system checks which software components are in the local system, and gives them the RFC destination NONE. You can use these components.


Edit Synchronization Object

UseYou want to compare or adjust customizing in the tables/views of a source and target system.

• Create synchronization object You create Synchronization objects [page 206] if customizing objects in different systems have the same contents but different structures, for example different table and field names. The information in the synchronization objects is used by the



Customizing Scout and the Customizing Distribution to compare and adjust customizing.

• Change synchronization object You change a synchronization object if you want to specify additional details, or make corrections.

You must adjust synchronization objects if you have made the following changes to view and table definitions:

• You have put a new table in the piece list of a customizing object, for example you have put a new table in a view.

• You have changed a key in a table in the piece list, for example you have added, deleted, or changed the length of a key field.

PrerequisitesYou are logged on to a Customizing Distribution target system.

You must create synchronization objects in a system which contains the Customizing Distribution target component. This is usually not the SAP Solution Manager system.

You have created the required RFC destinations in the RFC destination maintenance transaction SM59, and have the authorization described in the Synchronization object specification tool [page 238] prerequisites. You have specified RFC destinations [page 240] in the specification tool.

You have checked whether the Customizing Objects are Customizing Synchronization-compatible [page 246] and the customizing object types. You know the notes under Create and Load Synchronization Objects [page 236]. Note:

• view clusters (type C) must be resolved into individual views which are then entered in the specification tool.

• customizing objects of type T (individual transaction) or L (logical transport object) must be resolved into their tables (space, V, S); which are then entered in the specification tool.

Procedure

Create Synchronization Object...

1. Choose Tools → Customizing → Distribution → Change Synchronization Objects in the SAP menu, or call the transaction scdt_mapping.

You go to the synchronization object specification tool initial screen.

2. Choose a software component as target component, and a target release.

A list of existing synchronization objects is displayed.

* in the Release field means „all releases“.

3. Choose Create.

4. You go to the Create Synchronization Objects dialog screen.

5. Assign a name to your synchronization object and change the source component, or the releases for source and target components, if necessary.



The names in TADIR must be unique, so follow a naming convention for your synchronization objects.

6. Choose an option under Relevant for:

� Relevant for Comparison and Distribution: The object is used by the Customizing Scout and Customizing Distribution.

� Only Relevant for Comparison: The synchronization object is used by the Customizing Scout, but not in the Customizing Distribution.

� Only Relevant for Transport-Based Distribution: The synchronization object can only be used for Customizing Distribution by transport change, transport release, and timed distribution, not for initial distribution.

� Only Relevant for Initial Distribution

� Only Relevant for Comparison and Initial Distribution: The synchronization object can only be used for the initial distribution and the comparison with the Customizing Scout.

7. Redistribution Active: If you set this flag, you can swap the Customizing Distribution source and target systems, i.e. the Customizing Distribution user can distribute customizing from an application component such as SAP CRM to SAP R/3, as well as from SAP R/3 to other application components.

This flag is automatically set for No Mapping Required.

8. Specify the mapping type under Structure Differences:

� No Mapping Required: The tables have the same table and field names.

� Different Table Names

Tables may also differ in their structure, for example, one table can have more fields than the other, or fields with the same name can be of different types. If you still choose No Mapping Required or Different Table Names, the Customizing Scout and the Customizing Distribution will only process the fields with the same field name, which are in both components, and whose types are compatible.

� Different Table/Field Name : The tables/views have different table and field names. Customizing Synchronization only processes the fields for which you specify assignments.

� Programmed Mapping: Source system customizing data is converted into target system customizing data by a function module.

9. If the table or field names differ, enter the names of the corresponding tables or fields in the appropriate fields under Assignment.

The system tells you in Key Field Target and Text Field Target, whether the synchronization object contains key fields or fields in a text table.

10. If necessary, enter a fixed field value or a variable in the Fixed Field Value/Variable column.

Fixed field values are required for a source component table, for example, if one or more tables in the target component contain additional fields which have no corresponding fields in the source component. The following variables are



currently available: $LOGSYS; $SYLANGU; $MANDT; $UNAME; $SYDATUM; $SYUZEIT.

11. Specify Source and Target Object Filter Conditions [page 245] with the Change pushbutton in the Display/Change Filter Condition column, if necessary.

12. If you have specified the mapping type Programmed Mapping, specify the source system function module which converts the source system customizing data into target system customizing data. If you have also set the Redistribution Active flag, specify a target system function module as well.

13. Assign a source and target IMG activity to your synchronization object. You can use the possible entries help.

14. You can document the synchronization object with the Documentation pushbutton.

The documentation is created in the SAPscript editor. It has the type General Text.

15. Save your data.

The system checks the data entered. See check synchronization objects [page 245].

16. Specify a package and a transport request.

Change Synchronization Object ...

1. Choose Tools → Customizing → Distribution → Change Synchronization Objects in the SAP menu, or call the transaction scdt_mapping.

You go to the synchronization object specification tool initial screen.

2. Choose a target component and release.


3. Choose Change.

You go to the Change Synchronization Object dialog screen.

4. Make your changes.

5. Save your data.

ResultYou can now:

• Restrict the synchronization object release validity [page 243]

• Copy or delete the synchronization object.

You can load the synchronization object [page 231] in the SAP Solution Manager system to use it for the Customizing Distribution or the Customizing Scout.

Restrict Synchronization Object Release

UseThe table and field assignments of a synchronization object can differ between releases. You want to restrict the validity of a synchronization object definition with its table and field assignments, to a release interval. You can restrict the definition for both the source and target components.

You can:

• create several synchronization objects with the same name but different mappings, for different releases.



• change the release interval for a synchronization object.

If the target table changes between source releases, you must create two synchronization objects, to avoid data inconsistencies in the Customizing Distribution.

PrerequisiteYou are in the synchronization object specification tool initial screen.

Procedure...

1. Choose a target component and a source release.


2. Select an object and choose Edit Release Interval.

You go to the Synchronization Objects: Manage Intervals dialog screen.

3. Split Interval: To create different mappings for different releases for a synchronization object:

Choose Split Interval and then choose an upper release limit up to which your synchronization object is to apply, for the source or target component.

Choose Check.

If the check is successful, a new synchronization object is created automatically for releases above your upper limit, and displayed in the table at the top of the dialog box.

You can repeat this procedure any number of times, to define a synchronization object with different mappings for different releases.

4. Move Interval Limits: To move the release limits for a synchronization object:

a. Choose an object in the table in the dialog box.

b. Choose the limit which you want to change.

c. Choose a release.

d. Choose Check.

The system adjusts the release interval limits of the other synchronization objects with this name, so that the intervals are contiguous.

5. Save your data.

ResultThe system now contains two synchronization objects with the same names and the same mapping definition, but for different releases, or the system has changed the definitions of synchronization objects. You can now edit the synchronization objects, if necessary, for example, change the mapping type for some releases, or assign tables and fields.

You should check the synchronization objects [page 245].



Check Synchronization Object

UseWhen you save a synchronization object, its consistency is checked. If you change the system landscape after creating a synchronization object, or the release limits of the object change, you should check the synchronization object.

PrerequisiteYou are in the synchronization object initial screen.

Procedure...

1. Select the object in the object list in the initial screen.

2. Choose the Object → Check menu.

The system checks the consistency of the synchronization object, and shows any system messages:

� Are the specified tables and fields in the source and target systems?

� Do the data types of the source and target fields match, or can they be converted into each other? Are the fields the same length?

� Is the object BC Set compatible?

3. If the system sends messages, edit the object again and check whether the mapping type and the table and field assignments are correct for the specified releases, and change them if not.

Specify Filter Conditions for Source and Target Objects

UseYou can use filter conditions to specify key areas in the table which contain the data for one customizing-object. For example, you can specify that a field must have a specified constant value. You can restrict the Customizing Distribution to specified contents, with filter conditions (select rows from a customizing object). You can specify filter conditions for a source object, if they apply to a source field which does not exist in the target. This is relevant above all when the source object has more fields than the target object.

PrerequisitesYou are in the synchronization object editing screen.

Specify Filter Conditions for a Target Object ...

1. Choose the Change pushbutton in the Display/Change Filter Conditions column.

2. Enter the required data: field name, operator and a constant.

If you specify several conditions for one field name in different rows, they are automatically linked by the OR operator. If you specify several conditions in different field names, they are automatically linked by the AND operator.

3. Choose Continue.



Specify Source Object Filter Conditions ...

1. Choose the Change pushbutton in the Display/Change Filter Conditions column under Source Object.

2. Specify a field name and a field value or a system variable.

The following variables are currently available: $LOGSYS; $SYLANGU; $MANDT; $UNAME; $SYDATUM; $SYUZEIT.

3. Choose Continue.

Suitable Objects for the Customizing Synchronization SAP has predefined customizing objects which you can use in the Customizing Distribution and Customizing Scout comparisons (Synchronization objects [page 206]). You can also select other customizing objects for the Customizing Distribution or comparison, if you satisfy the following prerequisites.

Suitable customizing objects for Customizing Scout comparisons Table and field names must be the same in the source and target systems. If this is not the case, create a synchronization object [page 240].

Suitable customizing objects for Customizing Distribution

General prerequisites Table and field names must be the same in the source and target systems. If this is not the case, create a synchronization object [page 240]. The Customizing Objects must not contain Before-Export methods, and must be at least manually transportable.

Prerequisites for the automatic distribution of customizing changes Customizing objects which you want to use in the automatic distribution of customizing changes [page 217], must have an automatic transport connection, and be BC Set-compatible in the target system. When you set-up the Customizing Distribution, the system checks whether the objects which you selected are BC Set-compatible in the target system.

You can also check the BC Set-compatibility of objects in the IMG yourself before using the Customizing Distribution:

• In the synchronization group editor (transaction scdt_groups) under Edit → Delete BC Set-Incompatible Objects. BC Set-incompatible objects are flagged, and you can remove them.

• You can check objects in all systems based on software component SAP_BASIS 4.6C and higher, with the Check IMG for BC Set-Compatibility program. Specifically, you can perform this check in SAP R/3 systems with Release 4.6C. For further information about the IMG check program, see SAP note 398178.

• In all systems based on the software component SAP_BASIS 6.20 (e.g. SAP R/3 Enterprise) and higher, you can call a function to check the BC Set-compatibility, in the transaction SOBJ and in the Implementation Guide (IMG).

Objects for which you get a green icon for unchecked activation are suitable for the Customizing Distribution.



Test Organization

Purpose • A test organizer can create one or more test plans for the projects which are assigned

to him. He can also edit test plans and assign test packages to testers.

• The test organizer can get test plan status information.

The Test [external link] is performed with the Test Workbench [external link]. The Test Workbench is the SAP test environment and is in all SAP systems. A tester calls the Test Workbench and gets an overview of the test cases assigned to him in his worklist. He can perform tests, set processing status and note open items.

Prerequisites You must have created a Business Blueprint [page 134] and configured [page 150] your systems.

Flow diagram: Testing in the Realization phase

SalesSales BlueprintBlueprint

BC Set activationBC Set activation

TestingTesting

SandboxEvaluation

SandboxEvaluation

Fine-tuningFine-tuning

IMG customizingIMG customizing

Non-SAPNon-SAP

Realization

Process Flow Test Organization comprises the following steps: ...

1. You create test plans in the test plan management. When you Create Test Plans for a Project [page 249], , all test cases and transactions which were assigned to the project



in the Configuration are selected by default. You can deselect test cases and transactions from this default selection and then generate a test plan.

2. You can also display, change, copy or delete test plans, if necessary.

3. You combine a selection of test cases into a test package [page 252] and assign it to a tester.

4. Use the status info system to display, print and process test plan status analyses [page 254].

The Solution Manager reuses Test Workbench functionality in Test Organization. For further information about the Test Workbench, see The Test Workbench in the R/3 System [external link].

Test Plan Management

Use With this function you can:

• create

• change, copy or delete test plans

Integration You organize tests after you have created a project structure while creating the Business Blueprint [page 132]. You have performed Configuration [page 150] and want to test this configuration by process. When you create a test plan for a project, the default test plan structure is based on the structure of the Business Blueprint which you have previously created for your project.

Prerequisites To use this function, you must have defined a project in the Project administration [page 22], and created a project structure in the Business Blueprint [page 132] and assigned test cases or transactions to it in the Configuration [page 150], or you have created a test catalog with the Test Workbench. You must also set up a test system landscape with the transaction Solution Manager System landscape [page 60] before you start the Test Organization.

Features With the test plan management, you can:

• create, change, copy or delete test plans

• transport test plans

• divide test plans into test packages and assign them to testers

• monitor test progress with the status info system, and export test results.

With the test plan management, you can create test plans which are based on:

• the project structure which you created in the Business Blueprint

• one or more test catalogs.

The test plans are the set of all test cases which you need for a specific test phase, and can comprise the following objects:



• manual test cases

• external applications, e.g. third-party test tools an MS Word document

• CATTs

• eCATT test configurations

• function module tests

In the Utilities menu you can also:

• examine the worklists of testers

• upload and download notes

• display project data for a project to which a test plan is assigned

• Check the System Landscape of a Project [page 34] to which a test plan is assigned

You can create and print a test report which contains, e.g. the test case descriptions, messages and status, in the Goto menu.

Create Test Plan for a Project

Use You create a test plan for a project in the SAP Solution Manager if you want to reuse the project structure created in the Business Blueprint for a process-oriented test. You can select all the test cases and transactions which you have assigned to the project structure, for the test plan. These test cases are performed by testers; they can call assigned transactions and run test cases in them.

Prerequisites If you want to create a test plan based on the structure of an SAP Solution Manager project, you have created a project [page 25]. You have created a system landscape for the project. You have also defined a Business Blueprint with the Configuration [page 132] transaction, created test cases in the Test cases [page 180] tab, and assigned them to the structure.

You can also base test plans on test catalogs [external link] which are assigned to the application component hierarchy.

Procedure ...

1. Start the Test Plan Management.

2. Choose Test Plan → Create.

3. Enter the following data in the following dialog box:

� Choose a Solution Manager project and a system role from the possible entries help.

� You can specify a system data container if you want to put eCATT configurations in the test plan. You can also specify a target system, in which the eCATT configuration is to run.

The values which you specify are displayed as default values in the eCATT configuration initial screen. You can change them.

� Enter a title for the test plan.



� You can specify a test sequence.Test sequences are attributes of test plans, with which you can group test plans, and by which you can filter in the status info system

Create test sequences in Solution Manager customizing, under Scenario-Specific Settings → Implementation → Test → Central Test Settings.

4. Choose Continue.

5. Specify a package in the dialog box for the object directory entry, and choose Continue.

If a transportable package exists for the selected project, it is used to generate the test plan. Otherwise, the system shows you a dialog box for the object directory entry.

The system automatically puts the transactions which you have assigned to the project structure in the Transactions and Test Cases tabs, in the test plan.

The structure of your project is displayed. You see the attributes of a test case, in the General Data tab.

6. Choose elements from the project structure for your test plan.

You can filter the project structure, e.g. by assigned keywords or status. You can also filter test cases by attributes and base a test plan on the selection.

7. Choose Generate Test Plan.

The system generates a test plan based on your selection, and returns to the initial screen.

Result The system has generated a test plan based on your selection. You can now:

• change, copy or delete the test plan

• combine test cases and transactions into test packages, and assign them to testers

You can change your test plan [page 250] later. You can, for example, select additional test cases or transactions, and regenerate your test plan, without losing the status information for test cases which you have already run.

Change Test Plan for a Project You can put test cases or transactions which you have put in your project structure since the last generation of the test plans, into the test plan. ...


2. Select a test plan.

3. Choose Change.

4. The project structure underlying this test plan is displayed. Expand the project structure until you reach the relevant area.

The test cases or transactions in the test plan are selected.

5. Select the subareas that are relevant for the test plan.



6. If you want to select further by test case attribute or test case status, choose Filter Test Case Attribute or Filter Test Case Status.

Fill in the following selection screen and Execute. Only those test cases are now selected which were selected in step 5, and also satisfy the specified selection conditions.

7. You can select or discard test cases or transactions manually.

8. Change the structure element sequence under a higher-level structure element, by Drag&Drop.

The sequence change deletes the link to the project structure.

9. Generate the selected test plan with the Generate pushbutton.

The sequence of the test cases is retained.

Status information for test cases or transactions which have already been put in the test plan, is not lost when you regenerate the test plan.

After generation, you go to the Test Plan Management initial screen.

Change Project Test Plan Attributes

Use You change test plan attributes if you notice, when planning the test, that organizational or technical details have changed. For example, the person responsible for the test planning can change, or you want to enter a system data container for additional eCATT configurations in the test plan.

You can also change the system role of the test plan. This can cause inconsistencies in the test result of test plans which have already been processed, because they now access test cases in other systems. You should only change the system role in carefully selected exceptional cases.

Procedure ...

1. Start the Test Organization.

2. Select a test plan.

3. Choose .

You go to the test plan attribute display.

4. To change attributes, go to change mode with .

5. Change attributes, e.g. title, test series and person responsible for the test plan or the release.

6. If the test plan uses ‘Referring’ test cases, you must specify a remote link to the target system in which the referred test cases are defined, in the Logical Destination field.




Transport Test Plan

Prerequisites The test plan must be in a transportable package.

Procedure ...


2. Choose the test plan to be transported.

3. Choose Test Plan → Transport.

You get a list of the objects in the test catalog in the chosen test cases.

4. Select objects.

5. Choose Transport.

The transport requests assigned to you are listed.

6. Choose the request in which the selected objects are to be put, and Continue.

Result All objects are put in the specified transport request.

Objects in not-transportable packages can be put in transportable packages. These objects can then also be transported.

Create Test Package for Projects in Solution Manager

Use Test cases are collected for the tester in test packages. A test package is based on a test plan. Test cases are chosen from the test plan for the test package. If you have created a test plan for a project in the SAP Solution Manager, you can also select transactions, which a test should test, for a test package, from the test plan.

Procedure ...


2. Choose a test plan and the Manage Test Package pushbutton.

3. Choose Create.

The project structure underlying your test plan is displayed.

4. Select the subareas which are relevant for the test package.

5. To select by test case attributes or test case status, choose Test Case Attributes or Test Case Status, respectively.

Enter your selection criteria in the following screen. Only those test cases are now selected which were previously selected, and also satisfy the specified selection conditions.

6. You can select or discard test cases or transactions manually.



7. Choose Generate.

8. Enter a short description for the test package in the following dialog box and choose Continue.

Result The new test package is displayed when it has been generated. You can now assign a tester to the test package.

Assign Test Package to a Tester

Use A test package is usually assigned to one tester. The tester finds this test package as a work list in the test transaction. You can also lock or delete a test package for a tester.

The test package assignment is client-specific.

Prerequisites You have started the Test Plan Administration.

Procedure

Assign test package to tester To assign a test package to a tester: ...

1. Select a test plan and choose Manage Test Packages.

2. Select the test package.

3. Choose .

4. Enter the tester’s user name in the Assign Test Package dialog box, and choose Continue.

The tester assignment is put in the hierarchy.

To reset a tester assignment, position the cursor on the name of the tester and choose .

If you assign a test case to several testers, the test case result is displayed as follows:

• If several testers have tested the same automatic test case in the same test package, the status entry of the last tester applies.

• If several testers have tested the same manual test case in the same test package, the worst result applies.

• If several testers are to test the same manual test case in the same test package, and there are the test statuses ‚OK‘ and ‚open‘, the result is ‚OK‘.

If you want to test a test case twice, independently, you must copy the test package and assign each package to a different tester. For automatic test cases



which run in the background, the four eyes principle (testing twice) is superfluous, because the test is so defined that any tester would get the same result.

Delete test package from tester’s worklist If you want to remove test packages from the tester’s worklist, without losing the tester assignment, you can lock the assignments. This is useful above all when a test is finished and the tester should not change the status any more. ...


2. Mark the tester in the test packages.

3. Lock the test packages with the pushbutton or Goto → Lock Assignment.

The assignment status symbol changes from (Assignment Released) to (Assignment Locked).

To unlock an assignment, mark the tester and choose the pushbutton or the menu Goto → Release Assignment.

Delete test package assignment ...


2. Mark the tester in the test packages.

3. Choose Goto → Delete Assignment.

You should not delete the assignment of a test package to a tester if it has already been processed, because you would lose information.

Analyze Status You can analyze the status for one test plan or across test plans. The status of one test plan is usually the result of a particular test. Test plan-independent status analyses combine the results of several test plans, and can be considered as the overall result of a complex test, which comprises several test plans.

Status analysis of one test plan

Procedure ...

1. Go to the test plan management via Tools → ABAP Workbench → Test → Test Workbench → Test Organizer → Manage Test plans in the SAP menu.

2. Choose a test plan. Use the F4 help or choose a test plan from your Favorites.

3. Choose Status Analysis.

4. You can specify a period in which the statuses are analyzed with .

5. Select an object, depending on whether the status of one test package or the entire test plan is to be analyzed.

6. Choose Create detail view.



An overview of the test progress appears. The left-hand column contains information about the test case, and the right-hand column contains the test status.

If a test case was assigned to several test packages, each test package has a separate test case status. You can see all statuses of a test case by clicking on the Overview symbol after the test case.

To display all test statuses assigned to all test cases, choose View → Additional information. Other status analysis display types are under the menu item View.

Test plan-independent status analysis

Procedure ...

1. Go to the status info system initial screen Tools → ABAP Workbench → Test → Test Workbench → Test Organizer → Status Info System in the SAP menu.

2. Restrict the status analysis with selection conditions and choose Execute.

The Test Session field is a useful way of restricting selections. Test Session combines several test plans for the status analysis. To do this, enter a Test Session name in Test Plan Attributes [external link].

3. A list of selected test plans and condensed status information is displayed.

This analysis uses status information from previous status analyses for individual test plans. These statuses could be obsolete (e.g. a tester has changed a test case status in the meantime). This is indicated by a flag in the Obsolete result column and an entry in the list header. You can update this information by selecting the test plans and choosing Goto → Refresh Status Analysis.

4. To see detailed status information for a test, select it and choose Status information detail view.

Result You get an up-to-date status analysis of all test packages in the selected test plan.

• To send the status analysis, choose . You can send it with a comment via the Office mail system.

• You can use the general list functions to further analyze the list. You can for example:

� pass the data to a spreadsheet program

� export the data to a text processing program

� display the results graphically.

You can also display a problem message overview [external link] for your test plans in the Status Info System.



Test Plan Problem Overview

Use An overview of all problem messages in a test plan. Problem messages are created by testers when a test cannot be performed.

Prerequisites You have created test plans in the SAP Solution Manager and testers have started to test.

You have a problem message system, in which your testers can create problem messages. The problem message system is connected when the Solution Manager is installed. You need a user in the problem message system.

Features The problem overview contains the following information:

• problem message status

• problem message priority

• reporter

• current processor

• Message short text

• associated test case and test plan.

You can process the list of all problem messages for a test plan, in the problem overview, as follows:

• display

• print

• filter

• export to Office applications

• save in a local file

• send by E-Mail.

You can open any problem message by double-click, and display and edit it in your problem message system.

• If the problem message system for your Solution Manager is a basis system, process messages for which you are the processor, with the transaction DNOTIFWL.

• If as the message system for your Solution Manager is a CRM system, process messages with the Support Desk [page 340].

Activities ...

1. Start Test Plan Management in the Solution Manager.

2. Start a status analysis with the Status Info System.

3. The system shows an overview of all test plans which you have selected, and their overall results.



4. Choose a test plan and Problem Messages.

5. The system shows an overview of all the test plan’s problem messages. You can now open any problem message by double-click and see further details.

Solution Monitoring

Use Solution Monitoring helps you to manage heterogeneous system landscapes efficiently.

You can:

• your systems and

• your business processes

in one tool.

This uniform overview guarantees high performance and availibility of all your business processes across various systems and system components. The SAP Solution Manager provides predefined views and values for the functions in the sessions.

Integration You can:

• Configure your solution individually and specify which components are to be monitored (Solution Manager System Landscape [page 60]).

• Use external management tools and services provided by SAP, e.g. the SAP EarlyWatch service, the optimization services and self service (Service Plan [external link]).

• Handle problem messages (Service Desk [page 337]).

Features Solution Monitoring comprises:

• Service Level Reporting [page 282] (based on SAP EarlyWatch Alert [page 276])

Service level reporting guarantees continuous monitoring and reporting, based on weekly SAP EarlyWatch alerts.

• System monitoring [page 293] (including System administration [page 304]).

The system monitoring guarantees the real time monitoring of all systems in a solution, based on the Computer Center Management System [external link] (CCMS).

• Business process monitoring [page 316]

Business prozess monitoring guarantees the real time monitoring of all your business processes, based on a graphical overview. Like the system monitoring, it is based on the Computer Center Management System (CCMS).

Result Solution Monitoring monitors your solutions so that:

• core business processes run in accordance with the priorities of your company

• system unavailability and performance bottlenecks are avoided

• the operating costs of a solution are controlled



Solution Directory

Use Manage your solutions, systems and business processes in the Solution Directory.

Integration The Solution Directory is an interface between the configuration of your solutions and production processing.


• ActiveX controls are active in your browser

• Solution Directory roles [page 128] are assigned to users

Features The Solution Directory can: ...

1. Specify central solution attributes:

• assign logical components and logical systems

• specify contact persons

• specify other attributes

•

2. Copy business scenario or define your own:

• Copy structure elements from:

� Projects

� Business Process Repository (BPR)

� Operations templates

into the Solution Directory.

• Copy structure elements from the Solution Directory into a project.

• Define user views of hardware and process graphics, which are automatically copied into Solution Monitoring [page 257].

• The following tabs still exist:

� Documentation [external link]

� Structure [external link]

� Transactions [external link]

� Configuration [external link]

� Test Cases [external link]

� Graphic [external link]

�

Activities ...



1. Specify Solution Scope [external link].

2. Migrate Solutions to SAP Solution Manager 3.20. [page 258]

Create Solution

Use You want to create a new Solution.

Prerequisites Wenn when you create a new solution in the SAP Solution Manager, you are prompted for a name and a customer number.

Procedure ...

1. Choose the overview of active solutions.

Choose Back, to display the overview from a solution.

2. Choose New.

You go to a screen for creating new solutions.


Field input

Field Name Meaning

Name of the solution landscape Choose a name for your solution, e.g. your main business processes or branch offices.

Customer number The system creates the solution landscape, according to the customer and installation numbers of the „central administration system“ of the system landscape, if there is one. If you do not use a central administration system, you can also enter the data of the current system. This is proposed by the system.

Original language Language in which the solution is maintained.

4. Choose New.

The system creates your new solution and goes to the Operations Setup area in the Solution Landscape tab. From here you can go to the following transactions:

� System Landscape Maintenance (transaction SMSY)

� Maintain system landscape

� Define RFC connections

� Solution Directory

� Specify solution scope

� Make solution settings

� Project Scoping



Result You can now assign the systems and business processes which you want to monitor and manage, to your solution in the Solution Directory.

Create and Delete Logical Components

Use You create logical components, to assign them to logical systems later.

Prerequisite You have created a solution.

Procedure Create logical component ...

1. Choose the transaction SOLMAN_DIRECTORY.

Alternatively, you can also select a solution from the Overview of active solutions [page 270] and go to the Solution Directory.

2. Select your solution.

3. Choose the possible entries help for the Logical Components column.

4. Choose Create in the dialog box.

The Create Logical Component dialog box appears.

5. Enter the required data from the possible entries help.

� Name your logical components following the convention <Z> <component

name>, so they are not in the SAP namespace.

� You can also specify non-SAP products for the logical component:

i. Choose Create Product.

ii. Enter the required data.

iii. Save.

Name your logical components following the convention <Z> <component name>, so they are not in the SAP namespace.

6. Save.

The system goes to the system landscape maintenance (transaction SMSY).

7. Enter the product data. [page 66]

8. Save.



Delete logical component ...




3. Select a logical component.

4. Choose Remove Logical Component.

5. Save.

You can only delete an assigned logical component if it is not used in any other solution.

Result You have created logical components and products for your solution, and deleted logical components.

Assign Solution Attributes

Use You want to assign attributes to your solution:

Prerequisites You have:

• created a solution

• assigned Solution Directory roles [page 128] to users

Procedure ...




3. Choose the system role from the possible entries help for the System Group tab.

When you have saved, you can no longer change the system role.

4. Add logical components from the possible entries help for your solution.

5. Complete the following data:



• You can specify central systems for test cases, in the System Group tab.

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.

• You can also enter contact person data in the Contact Person tab.

� Proceed as follows:

i. Choose Add Contact Person.

ii. Enter the required data.

iii. Save your entries.

� The contact data appears in the Solution Monitoring sessions, e.g. in Set-Up Business Process Monitoring [page 325].

• You can enter the following data in the Attributes tab:

� Day of SAP EarlyWatch Alert [page 277] data download

� Monitoring graphic refresh period

� Administration information, such as:

� Customer number

� Installation number

� Database ID

� Knowledge Warehouse Information

You can only display the Knowledge Warehouse information.


Copy Business Scenarios

Use You copy data from:

• a project

• the Business Process Repository (BPR)

The Business Process Repository is a structured set of all preconfigured structure elements that you can reuse.

• Operations Template

• the Solution Directory.




• created a project to copy from a project in the Project Administration [page 22] (transaction: SOLAR_PROJECT_ADMIN).

• created a solution.

• assigned Solution Directory roles [page 128] to users.

Procedure ...



3. Specify whether you want to copy business processes from the Business Process Repository or from a Project, in the possible entries help for the field Selection Help.

4. Proceed as follows, depending on your selection:

• Business Process Repository ...

a. Choose the Business Scenarios link in the left-hand screen.

b. Choose the Structure tab.

c. Choose a business scenario in the possible entries help for the Scenario Name column.

d. Confirm the following dialog box.

The system copies the business scenario and its business processes/process steps.

• Project ...

a. Choose the Business Scenarios link in the left-hand screen.

b. Choose the Structure tab.

c. Specify that you want to copy business processes from a project, in the possible entries help for the field Selection Help.

d. Choose a business scenario in the possible entries help for the Scenario Name column.

e. Choose Copy Options.

f. Specify in the dialog box whether want to copy project documentation.

g. Confirm.

h. Specify in the dialog box, how you want to handle the assigned documents.

i. Confirm.

The Logical Component Assignment dialog box appears.

j. Check the assignment of the logical components to the systems.

k. If the status is green, confirm. Otherwise, assign the logical components first [page 261].

The system copies the business scenario and its business processes/steps.

2. Choose the business scenario status.

To be able to monitor your business scenario and business processes in the Business Process Monitoring Sitzung [page 316], you must set the Status to Production.




The background information for Solution Directory Copy Scenarios tells you which other data is copied from the tabs.

Result You have copied business scenarios from the Business Process Repository or a project.

You can change and add information in the following tabs:

• Documentation [external link]

• Structure [external link]

• Transactions [external link]

• Configuration [external link]

• Test cases [external link]

• Graphic

Solution Directory Copy Scenarios

Solution Directory copy scenarios.

Copy into the Solution Directory

supported

tabs

of Business Blueprint [page 132] (SOLAR01) and

Configuration [page 150] (SOLAR02)

from a project from the Business

Process

Repository

from Operations template

Structure all structure elements except:

Configuration

Master data

Organizational

units

all structure elements except:

Configuration

Master data

Organizational

units

Business processes and business process steps

General

Documentation

not supported does not exist does not exist

Project

Documentation

all Business Blueprint-relevant documents

does not exist does not exist

Transactions all object types all object types does not exist



In Scope and Default flags are copied, but not shown

Test cases all test case types, with documentation and test objects

all test case types, with documentation and test objects

does not exist

Configuration all object types with documentation

Person responsible for configuration

and status are not passed

all object types with documentation

does not exist

Roles all roles

Data is copied, but not shown


End user

documentation

all documents

Data is copied, but not shown


Graphic Graphic attributes of process folders and processes

Graphic attributes of process folders and processes

Template graphics

Copy from the Solution Directory

Supported tabs

of Business Blueprint [page 132] (SOLAR01) and

Configuration [page 150] (SOLAR02)

in a Project

Structure all structure elements except:

Configuration

Master data

Organizational

units

General Documentation all Solution Directory Documentation documents.

Project Documentation all Solution Directory Documentation documents, except in template projects.

Transactions all object types

In Scope and Default flags are copied, although not shown in the Solution Directory

Test cases all test case types, with documentation and test objects

Configuration all object types with documentation

Roles all roles

Data is copied rnommen, although not shown in the Solution Directory



System graphic

Use You want to:

• To get an overview of your server architecture for a solution.

• adjust the graphic of the systems in a solution to your requirements in your view, for Solution Monitoring [page 257].


• Defined systems for your solution, in the System Landscape Maintenance [page 60] (transaction SMSY).

• assigned Solution Directory roles [page 128] to users.

Procedure 4. Choose the transaction SOLMAN_DIRECTORY.

5. Open the structure element Solutions.

You see all solutions for the SAP Solution Manager system.

6. Choose the solution for which you want to display the system architecture.

7. Choose the structure element Systems.

8. Choose the Graphic tab.

You see the system components and interfaces per system.

To see details (system components) of the systems, choose the link to the system in the graphic, or the structure element directly.

9. You can perform the following system activities in the graphic:

• General graphic display

� Define view

i. Choose the Complete View link in the system graphic, to define your view.

ii. Specify a view name.

iii. Create your view.

iv. Save your entries.

� Adjust the graphic size with a symbol or percentage

� Adjust the font size with Attributes

� Change the size and position of the graphic manually ...

i. The cursor is in the graphic to be able to move it.

ii. You can change the size by left-clicking on the points which appear on the edges of the graphic.



� Print graphic

� With the symbol in the Register tab

� With the Graphic In Place �> In Separate Window symbol in the menu bar.

� Export graphic as Power Point or Word document

• Define Interfaces [external link]

• Show and hide system components ...

i. The cursor is in the graphic of a system component.

ii. Click the right-hand mouse key.

A dialog box appears.

iii. Flag elements and confirm.

You can hide an element in the same way. You can only hide elements which you have previously shown.

Result The system copies your new view in the Solution Monitoring graphic. You can now use it.

Server Graphic

Use To get an overview of your server architecture for a solution.

Prerequisites You have created a solution and assigned logical components [page 261].

Procedure ...


2. Open the structure element Solutions.

You see all solutions for the SAP Solution Manager system.

3. Choose the solution for which you want to display the server architecture.

4. Choose the structure element Server.

5. Choose the Graphic tab.

6. You can perform the following activities in the graphic:

� Adjust the graphic size with a symbol or percentage

� Adjust the font size with Attributes

� Change the size and position of the graphic manually

� ...

i. The cursor is in the graphic to be able to move it.



ii. You can change the size by left-clicking on the points which appear on the edges of the graphic.

� Print graphic

iii. With the symbol in the Register tab

iv. With the Graphic In Place �> In Separate Window symbol in the menu bar.

� Export graphic as Power Point or Word document


Manage Solution

Purpose The SAP Solution Manager Operations allows you to set-up, manage and monitor systems and business processes for a solution [external link]. You can use both complete solutions and individual systems, business processes and software components. You can also set-up and run your own solution support.

Integration The SAP Solution Manager for operational processing provides an infrastructure for the integration of the SAP Support Services and their system administration activities.

Features You can:

• display a solution overview [page 270]

• create and delete solutions

• activate and deactivate solutions

You can also perform a self-diagnosis of one or all solutions.

Activities ...

1. Create a new solution. [page 259]

2. Copy a solution [page 272]

3. Activate and deactivate a solution [page 274].

4. Delete a solution [page 275].

5. Perform an SAP Solution Manager self-diagnosis [page 275].

Navigation in Operational Processing



Structure

Operations Setup The Operations Setup area gives you access to the contents and functions which you need to set-up the systems and business processes of your solution.

The Operations Setup area provides objects in the various service categories (e.g. SAP Technology, Global Strategy) which are assigned to your solution (e.g. services, documents and graphics).

Each service category (e.g. SAP Technology) contains several subcategories (e.g. Monitoring, Administration). The subcategories can contain tabs, e.g.:

• Work Area

The work area is an overview of all relevant objects for this area, e.g.:

� Best Practice documents for the topic, e.g. for:

� simplified technical implementation

� solution landscape management

� recommendations for the use of the SAP Solution Manager functions

� links to services

� links to the creation of sessions, e.g.:

� Administration

� Service Level Reporting

� Business Process Monitoring

• Solution Graphic

The Solution Graphic performs tasks in a graphical display of the systems and system components of your solution, e.g.:

� System monitoring: graphical display of critical alerts

� Central system administration: Display of open tasks

Operations The Operations area gives you access to the contents and functions which you need to perform management and monitoring tasks in your solution.

The Operations area provides objects in the various service categories (e.g. SAP Technology, Global Strategy), which are assigned to your solution (e.g. services, documents and graphics).

Each service category (e.g. SAP Technology) contains several subcategories (e.g. Monitoring, Administration). The subcategories can contain tabs, e.g.:

• Work Area

The work area is an overview of all relevant objects for this area, e.g.:

� links to sessions

� SAP EarlyWatch Alert

� System Monitoring

� Service Level Reporting




• Solution Graphic

The Solution Graphic performs tasks in a graphical display of the systems and system components of your solution, e.g.:

� System monitoring: graphical display of critical alerts

� Central system administration: Display of open tasks

You can switch between the areas in two ways:

� Shortcuts in the left-hand screen area

� Goto in the top right-hand screen area

You can also

� Go to the overview of active solutions

� Open other active solutions

� Make solution settings.

You must be in the Operations Setup area.

Overview of Active Solutions

Definition This overview displays all active solutions in your SAP Solution Manager solution landscape. If you have not yet defined any solutions, the overview is empty.

Use From the overview, you can:

• Create a new Solution [page 259].

• open an existing solution

• copy [page 272] solutions

• deactivate [page 274] solutions.

• Activate inactive solutions

• Call solution monitoring functions

• set-up automatic refresh

When you first call the transaction SOLUTION_MANAGER, you go to the Active Solutions overview. If you have already been in a solution, you go to the one which you were most recently in. Choose Back or the shortcut Solution Overview, to go to the Active Solutions overview.

Structure Functions in the solution status overview



Solution Choose the name of a solution, to access the area in it in which you were last.

Last Update The date and time show when the status data was last refreshed.

Manual update:

Choose Update Alert for the solution.

Automatic update:

Automatic refresh: You can set an interval for the automatic refresh of all active solutions (in minutes). It should be between 5 and 10 minutes.

You can activate automatic refresh for individual solutions or for all solutions:

Individual solution

To activate automatic refresh for a solution, choose das Symbol Automatic Refresh Inactive .

To deactivate automatic refresh for a solution, choose Automatic Refresh Active .

All Solutions

To activate or deactivate automatic refresh for all solutions, choose Activate All or Deactivate All, respectively.

Status of:

EWA

System Monitoring


Red flags indicate that the data of the systems in the session are overdue. Continuing system operation is not currently under threat.

Red symbols indicate serious errors or alerts. Continuing system operation is under threat.

Yellow symbols warn of problems to which you must attend, but which are not currently critical. Continuing system operation is not currently under threat.

Green symbols indicate that a monitored value is within allowed limits

Gray symbols mean that the system has no status information.

You can go directly into the dialog view, by clicking on the symbol.

Solution Directory You can go to the Solution Directory [page 258] in the Activities column.

You can:

copy a not yet migrated solution (from SAP Solution Manager 2.20 or 3.10), with Sie das Symbol Put in Solution Directory .

Solutions to be migrated are on a gray background.

Assign new business scenarios and user graphical views of the systems, to your solution with Goto Solution Directory .



Copy Solutions

Use Copy one or more of your existing solutions.

Prerequisites You have created solutions.

Procedure ...

1. Choose the Solution Manager transaction SOLUTION_MANAGER.

2. Go to the Solution Overview [page 270].

3. Flag the solution to be copied.

You can copy several solutions at the same time.

4. Choose Copy.

5. You can give new names to the solutions to be copied.

6. Choose Copy Solutions.

The system:

� copies all the settings of your solution, except Knowledge Warehouse documents. The system refers to the same documents as in the source solution.

� deactivates the Business Process Monitoring [page 334] sessions. Activate the sessions after the copy.

Result Your solution appears in the Solution Overview. You can use the solution.

Edit Solutions

Use You want to edit attributes in your solution landscape.

Integration The solution landscape management integrates project implementation and management functions, system landscape set-up, and the running of your solutions.

Prerequisites You have created a solution.

You are in the Solution Landscape menu in the Operations Setup area of the SOLUTION_MANAGER transaction.



Activities You can:

• Maintain the system components, business processes and graphic views of your solution

...

a. Choose the Solution Maintenance link.

You go to the Solution Directory [page 258] (transaction SOLMAN_DIRECTORY).

• You get an overview of projects which you have assigned to your solution. ...

a. Choose the Project Scoping [page 273] link.

• Edit your solution settings. ...

a. Choose the Solution Settings link.

You go to the Attributes tab in the Solution Directory [page 261] (transaction SOLMAN_DIRECTORY).

• Maintain the systems of your solution ...

a. Choose the Solution Landscape Maintenance link.

The system goes to the System landscape [page 60] maintenance (transaction SMSY).

Project Overview

Use In the project overview, you can see which projects you have assigned to the solution. You can assign new projects to the solution, and edit existing projects.

Prerequisites You have created a solution and may have assigned projects to it (transaction SOLAR_PROJECT_ADMIN).

Procedure

Assign new project to a solution ...

1. Choose the transaction SOLUTION_MANAGER.

2. Choose Solution Landscape → Project Scoping in Operations Setup.

3. Choose the Create Project link in the project overview.



5. Create a new project for your solution [page 25]

Edit existing project ...


2. Choose Solution Landscape → Project Scoping in Operations Setup.

3. Choose your existing project in the project overview.

4. You can:



Possibilities Activities

Display Roadmap You can go to the Roadmap

Display project details

You see planned data, actual data and milestones of your project.

Link to the project administration transactions

System Landscape [page 60]

Project Administration [page 22]

Business Blueprint [page 134]

Configuration [external link]

Reporting [external link]

Activate and Deactivate Solutions

Use You can deactivate a solution, e.g. when it is not being used.

Inactive solutions are removed from the overview of active solutions, and displayed in a separate screen. To display the inactive solutions, choose Display Inctive Solutions .

You can reactivate inactive solutions at any time.

Procedure

deactivate solutions ...

1. Flag the solution.

2. Choose the Deactivate pushbutton.

When you deactivate a solution, its data is retained. You cannot display services for, or change, this solution. Background jobs ignore inactive solutions. Deactivation thus reduces the the use of system resources by solutions.

Your solution appears in the overview of deactivated solutions.

Activate solutions ...

1. Choose a solution in the overview of inactive solutions.

2. Choose the Activate pushbutton.

Your solution appears in the overview of active solutions.



Delete Solution

Use You want to delete solutions which you no longer need, to get a better overview of your active solutions.

Procedure 3. Start the transaction ABAP Editor (SA38).

4. Run the program RDSMOPDELETESOLUTIONS.

5. Choose a solution from the possible entries help.


You get a list of the deleted data.

When you have confirmed the dialog box, the system deletes the data from the database.

Result The system has deleted the solution from the database.

SAP Solution Manager Self Diagnosis

Use This function identifies SAP Solution Manager and solution landscape problems and takes appropriate action.

Prerequisites You have created at least one solution.

Features You can perform self diagnosis at various levels:

• For the SAP Solution Manager

• For the SAP Solution Manager and a solution

Activities ...


You go to the SAP Solution Manager: Active Solutions screen.

2. 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.

3. Choose Goto → Self Diagnosis.

You get an overview of all self diagnosis logs in the system.



4. Choose Message Long Text for the row to see the long text with further information for a diagnosis.

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.

Using SAP EarlyWatch Alert

Purpose This process identifies potential problems early, avoids bottlenecks and monitors the performance of your systems. SAP EarlyWatch Alert monitors your most important business processes and systems.

The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.


• set up RFC connections between your satellite systems and the SAP Solution Manager system, and an RFC connection between the SAP Solution Manager and the SAP Service Marketplace.

• checked the availability of the required tools for the SAP service session (ST-A/PI add-on), with the reports RTCCTOOL.

• activated Alert Monitoring for all SAP satellite systems, and the central SAP Solution Manager of your solution, and set up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCC) of your satellite systems (SAP note 91488).

• set up your systems in a solution landscape in the SAP Solution Manager.

See: Configuration Guide: SAP Solution Manager 3.2

Process Flow ...

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 [page 261]

The default value is Mondays. 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 [external link] 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 SAP Solution Data Manager (SDCCN).

5. The job SM:EXEC SERVICES triggers the processing of the data in a system session.

6. Further processing is in accordance with the following rules, which SAP has specified in the system:

� Red status: Critical/Error

i. Analyze the report. The SAP Solution Manager system sends the data to SAP.

ii. SAP Support analyzes the problems and contacts you if necessary, to discuss further action.

iii. If you consider the alert to be critical, discuss further action with SAP.

iv. Take the agreed action.

� Yellow status: Critical/Warning ...

i. Analyze the report.

� Gray status: Status unknown ...

i. Check why the system status could not be determined.

� Green status: No error

The system sends initial and monthly sessions to SAP via the SAP Service Marketplace, regardless of the analysis of the weekly SAP EarlyWatch Alert reports.

SAP EarlyWatch Alert

Use The SAP EarlyWatch Alert is a diagnosis service, for the solution monitoring of SAP and non-SAP systems in the SAP Solution Manager.

Integration SAP EarlyWatch Alert is the prerequisite for Service Level Reporting [page 284].


• set up RFC connections between your satellite systems and the SAP Solution Manager system, and an RFC connection between the SAP Solution Manager and the SAP Service Marketplace.

• checked the availability of the required tools for the SAP service session (ST-A, ST-PI add-on), with the report RTCCTOOL.

• assigned the Solution Monitoring roles [page 129] to the users.

• set up the Automatic Session Manager (ASM) in the Service Data Control Center [external link] (transaction: SDCCN) for all SAP satellite systems and the central SAP Solution Manager of your solution (SAP note 91488).




See: Configuration Guide: SAP Solution Manager 3.2

Features The following satellite system data is captured in a week and passed to the SAP Solution Manager:

• General component status

• System configuration

• Hardware

• Performance development

• Average response times

• Current system load

• Critical error messages and process interruptions

• Database administration

The system processes the downloaded data. You can display the report as an HTML document. You can also create the report as an MS Word document. You can use the documents as status reports. These reports can help you analyze and avoid problems.

Activities ...

1. Perform an SAP EarlyWatch Alert Download Manually [page 278]

2. Create an SAP EarlyWatch Alert Report and See the Session Details in the SAP Solution Manager [page 280]

3. Save, Retrieve and Archive an SAP EarlyWatch Alert in the SAP Solution Manager [page 281]

Perform SAP EarlyWatch Alert Download Manually

Use 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.

Procedure I...

1. Start the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring → EarlyWatch Alert in the Operations screen.

You go to the overview of all SAP EarlyWatch Alert services.

3. Choose Create Services.

4. Choose the SAP EarlyWatch Alert Service Create Service for a system.

5. Choose the planned date.

6. Confirm your entries.



The system creates an initial SAP EarlyWatch Alert Service.

The newly-created SAP EarlyWatch Alert appears with the symbol Wait for ’Download Data’.

7. Choose the SAP EarlyWatch alert for a system.

You go to a screen in which the further procedure is explained.

8. Call the Service Data Control Center [external link] (transaction: SDCCN), in the relevant system, with the Call Service Data Control Center pushbutton.

You go to the Service Data Control Center of the selected satellite system.

9. Choose the Create New pushbutton in the Service Data Control Center.

10. Choose the Refresh Sessions task.


11. To refresh the task immediately, choose Now.

12. To schedule the task once, choose the Run Task Once pushbutton.

13. Choose your Service Data Control Centre Target RFC Destination from the possible entries help.

14. Confirm.

You get a task number

15. Confirm.

Your task number appears in a row in the To Do tab.

16. Select this row.

17. Choose Edit → Start Now.

18. Confirm.

19. You can monitor the job in the Task Log tab.

20. Go back to the SAP Solution Manager system.

21. Refresh your data in the SAP Solution Manager.

Successful download is indicated by a symbol in the SAP Solution Manager overview. The alert data is then available in the SAP Solution Manager.

22. Choose the link to the SAP EarlyWatch Alert, to process your session data in the SAP Solution Manager.

23. Proceed as described.

You can start the background job yourself with Start Service Processing.

Result 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.



Create SAP EarlyWatch Alert Report, Display Details, Send E-mail

Use The SAP EarlyWatch Report gives you detailed information about system status, performance, configuration, system operation, database administration and trends.


• processed the session

• installed the Internet Graphics Server (IGS) to create an HTML report with graphics.

• setup automatic E-Mail sending [external link], if necessary.

Procedure

Create SAP EarlyWatch report ählen Sie die...




You can generate an SAP EarlyWatch Alert report as: ...

• HTML document

a. Choose a link to a service.

b. Choose a report type.

You can send the HTML report as an E-mail, to yourself and any number of other recipients (Add Recipient… pushbutton).

You can only enter one recipient per row.

• MS Word document

� ...

c. Choose the Create Word Report symbol.

d. Choose a report type.

When you have generated the report, it appears as an attachment.

You can send the document as an E-mail from MS Word.

• Choose the Central Session Management program [external link] under Goto → Session Overview.

�

Display session details ... ...






3. Choose Display Session.

4. Confirm the information dialog box.

You go to Display Mode: EarlyWatch Alert.

You can display all data, hierarchically, without analysis, in the EWA Viewer.

5. You can create the reports with HTML or MS Word Document.

To save an HTML document locally, choose Goto → HTML Document → Save.

Result You can now see the report created, and respond to its recommendations.

Save, Activate and Archive SAP EarlyWatch Alert

Use You want to perform the following actions with SAP EarlyWatch Alert services/documents:

• deactivate, to give a better overview of your SAP EarlyWatch Alert Services.

• activate, to check alert data.

Procedure

Deactivate service ...




3. Choose Inactive Services.

4. Select a service to save.

5. Choose Save Services.

You go back to the SAP EarlyWatch Alert overview screen. You go to the overview of saved Services with the pushbutton Repository.

Retrieve service ...

1. Choose Repository.

2. Choose Retrieve Service to retrieve the SAP EarlyWatch Alert.

You go back to the overview screen. The retrieved SAP EarlyWatch Alert Service is in the overview: Archive Session.



Archive service

Prerequisite

You must save sessions before you can archive them.

Your archiving system is not part of the SAP environment. You must set-up an external archiving system (note 546685).

Archive sessions manually ...

1. Choose Archive Services in the repository.

2. Specify a date and confirm your entries.

The system archives the sessions which are older than the specified date, with their attachments. The daily job RDARCH_CLEAN_DATABASE, deletes archived sessions and documents physically from the database. You can no longer open archived sessions. You can only display them.

Archive sessions automatically

You can schedule sessions for automatic archiving from the repository. ...

1. Schedule the job RDARCH_ARCHIVE_DATA_SOLMAN with transaction SM37.

You can schedule the job periodically, e.g. daily, to archive all sessions which are older than ten days.

2. The job archives sessions in the repositors which are older than the specified age, with their attachments.

Accessing archived sessions and documents

You can access any session in the archive.

You can display, but not change saved sessions. When you archive sessions, the system saves them in an external repository and deletes them physically from the database. This reduces the size of the database.

Result You can save SAP EarlyWatch Alert services/documents and retrieve them from the repository. You can archive services.

Using Service Level Reporting

Purpose Service Level Reporting:

• is the interface between your IT department and the person responsible for a business process.

• provides analyses across the systems and business processes in your solution landscape.



You can thus react quickly to risks, and continually improve your IT service.


• set-up SAP EarlyWatch Alert in the SAP Solution Manager.

• assigned the Solution Monitoring roles [page 129] to the users:

Setup Service Level Reporting. You also want to see the SAP EarlyWatch Alert analyses and display the business processes in the business process monitoring, which you want to put in the Service Level report, in the Business Process MONITORING session. You need the following functional roles:

� SAP_SETUP_DSWP_SLR

� SAP_OP_DSWP_SLR

� SAP_SV_SOLUTION_MANAGER_DISP

Adjust the authorization object D_SOLMANBU with the Bundle IDs for the sessions.

•

Process Flow Der Kunde de...

1. A Service Level Agreement [external link] is defined between you and an IT organization. It covers:

� Your IT service quality requirements, for example performance and security

� unambiguous and measurable service targets

� communication structures

2. You schedule Service Level Reports based on the Service Level Agreement. You create Service Level Report types. Service Level Report types are templates for Service Level Reports. The Service Level Report types specify the contents and scope of the Service Level Report.

3. You specify the scope of the Service Level Reporting, e.g.:

� which business processes and which systems in your solution are analyzed

� which checks and alert thresholds you require

� how the information is presented in the reports

� report types

4. The system creates the relevant Service Level Report sessions, which you can process, to change details or add further information.

5. You send the Service Level Report to the persons responsible.




Use You use the Service Level Reporting to optimize and simplify long-term system monitoring. You can use Service Level Reporting to fulfill your internal and external Service Level Agreements (SLA).

Integration Service Level Reporting:

• based on SAP EarlyWatch Alert.

• allows you to display aggregated alert information from the Business Process Monitoring.

If you have created business processes in a project, you can put them in Service Level Reporting with their assigned systems and transactions.


• set up a solution landscape in the SAP Solution Manager.

• set up the RFC connections between the SAP Solution Manager and the satellite systems:

• set up SAP EarlyWatch Alert for all systems, in the SAP Solution Manager.

Features Service Level Reporting functions:

• Service Level Reporting regularly checks the specified technical Key Performance Indicators (KPI) such as system availability and performance thresholds.

• You can set-up various Service Level Report types for reporting, schedule Service Level Reports for automatic generation, and process them in sessions, according to your requirements.

• You can display the Service Level Reports as detailed HTML reports, or send them as created MS Word reports.

Activities ...

1. Set-up a Service Level Report [page 284].

2. Process a Service Level Report Session [page 292].

3. Set-up a Service Level Report [page 290].

4. Save, Retrieve and Archive Service Level Reports [page 291].

Set-Up Service Level Reporting

Use Set-up a new Service Level Report.



Prerequisites You have set-up SAP EarlyWatch Alert [page 276] in all systems in your solution landscape.

If you want to put Business Process Monitoring [page 333] data in the Service Level Report, you have configured the Business Process Monitoring in the SAP Solution Manager.

Activities 5. Start the transaction SOLUTION_MANAGER.

6. Choose Solution Monitoring → Service Level Reporting, in the Operations Set-Up area.

7. Choose SL – Set-Up Reporting.

You go to Change Mode: Set-Up SLR.

8. Perform the following checks in change mode:

a. Specify Service Level Report Type [external link]

b. Maintain General Settings [page 286]

c. Specify and Maintain System for Service Level Report Type [page 287]

d. Specify and Maintain Business Processes [page 288]

e. Specify Business Processes Based on Business Process Monitoring [page 289]

f. Process Service Level Report Data Manually [page 289]

Service Level Reporting Change Mode

Definition You specify the scope of the Service Level Reporting in the change mode of the set-up session.

Structure The screen is divided into three areas:

• Left-hand column:

Displays all the checks which you should perform to set-up the Service Level report type.

� Specify SL Report

� General Setting for SL Report

� Select Systems for SL Report

� Select Business Processes for SL Report

� SL Reporting Based on BP Monitoring

Any subitems of checks only appear when you have performed and saved the check. These subchecks can be partially preconfigured, if the system has the necessary data.

• Top right screen area:

Explains the use, background and procedure of the check.



To hide the documentation, move the frame.

• Bottom right screen area:

The tables to be maintained by the check.

You can call the online documentation in the logon language, for the checks, with HELP.

Maintain General Settings

Use You maintain general report type attributes.

Procedure 9. Select the General Settings for SL Report check.

10. Enter your customer data in the Customer Data tab.

This data appears in the Service Level Report cover page.

Select a field and enter the data.

11. Specify when, and how often, the report is to be automatically created, in the Scheduling of SL Report tab.

You want, for example, to schedule the report every 2 months on a Tuesday. Choose the day of the week Tuesday, the period 2 and period type Monthly.

Scheduling

Scheduling Period Period Type

Weekly 1 Weekly

Quarterly 3 Monthly

Yearly 12 Monthly

The period type Monthly is a sum of weekly SAP EarlyWatch Alerts. To get correct results for monthly Service Level Reports, you must perform weekly SAP EarlyWatch Alerts.

12. Save your entries with Save + next w/o Check.

You go to the next unprocessed check.



Specify Systems for Service Level Report

Use You specify the systems which you want to analyze.

Procedure 13. Select the Select Systems for SL Report check.

14. Choose the systems whose data is to be analyzed in the report.


16. Expand the Select Systems for SL Report check.

17. Select the Report Content for System check.

The system proposes the scope of analysis of the Service Level Report.

18. Expand the Report Content for System check.

You can adjust system availability or threshold values to your requirements in the checks System Availability and System Performance Thresholds.

� System availability values

i. Enter alert threshold values in the Availability tab.

You should retain the default threshold values.

ii. Choose dates and times for which you want to display statistics in your Service Level Report.

iii. Save your entries.

� System threshold values ...

i. Specify response times.

The average response time in dialog must not be less than the the average response time of the database.

If you do not specify alert threshold values, no alert data is read for the Service Level Report.

You must make these settings before you transfer the SAP EarlyWatch Alert sessions from the satellite systems, because the system uses this data for the next SAP EarlyWatch Alert sessions to be scheduled.



Select Business Processes for the Service Level Report

Use You specify the business processes which you want to analyze.

Procedure 19. Select the Select Business Processes for SL Report check.

20. To display business processes which you created in other sessions, for selection, choose Load Gglobal Business Processes.

The system copies all existing business processes into the Service Level Report table.

21. Choose the business processes which you need for your Service Level Report.

If you have already specified a business process in Business Process Monitoring [page 333], it is the default value. Otherwise you can specify any business process.

You can also create new business processes for this specific Service Level Report, for example to test the report functionality, or to monitor background jobs which comprise an ABAP report or a chain of ABAP reports.

Business Process: my Background Job

Analyses: X

22.


You go to a subnode of the business process step Analyses of Business Process <nn> checks. You activate the history for average response times and flag posting errors or query analyses for the business process step transactions, reports or queries, for analysis.

a. Specify the transaction, report or query for the business process step.

The transaction name of a business process step is in the System → Status menu of the transaction.

b. Set the Response Time and Update Error analyses for the transaction, report or query.

Business process steps which are based on a non-SAP software component, are not displayed.

For check: Analyses of Business Process my Background Job

Step Name:

� my Job 1

� my Job 2



� …


25. Specify the alert threshold for the business process, if necessary.


If you have specified business processes in Business Process Monitoring, you go to the associated check.

Select Business Processes from the Business Process Monitoring

Use You specify the business processes which you want to analyze, from the Business Process Monitoring.

Prerequisite You have created business processes in your solution landscape, copied them from a project, and monitor them in Business Process Monitoring.

If you have configured the Business Process Monitoring, the system sets a flag in the BP Mon Configured column.

If you have activated the Business Process Monitoring for the business process, the system sets a flag in the BP Mon Activated column.

Procedure 27. Select the SL Reporting Based on BP Monitoring check.

28. Choose production business processes from your solution landscape which you want to put in the Service Level Report.

29. Set the analysis manually to Done.


You go to subnodes of the processes. Select the check for the process.

You can specify which monitoring functions and which summation steps of your business processes you want to put in the Service Level Report.


Process Service Level Report Data Manually

Use You want to process the existing data.



Procedure 32. Start the transaction SOLUTION_MANAGER.

33. Choose Solution Monitoring → Service Level Report, in the Operations area.

If you have created a new report type, the system initially gived you the service data, independently of the next scheduled date. Changes in the report type only become active at the next scheduled date.

34. Choose a link to a Service Level Report.

You go to a screen in which the further procedure is explained.

35. Choose the link Start Service Processing.

36. Confirm the start of the background job.

37. Refresh the Work Area tab overview.

Create Service Level Report

Use You create the Service Level Report to send it to the person responsible.


• processed the session data

• setup automatic E-Mail sending [external link], if necessary

Procedure You can create and display a Service Level Report in various ways.

• From the Service Level Reporting overview

� HTML report

Choose a link to a Service Level Report.

You can send the report as an E-mail, to yourself and any number of other recipients (Add Recipient… pushbutton). You can only enter one recipient per row.

� MS Word document ...

i. Choose the Create Word Report symbol.

ii. Choose a report.

When you create the report, it appears as an attachment.

You can send the report as an E-mail from MS Word.

• From the Service Level Reporting session data Über die ...



You can display the HTML report and create the MS Word report with the HTML Document and MS Word Document pushbuttons respectively.

To save an HTML document locally, choose Goto → HTML Document → Save.

• Choose the Central Session Management program [external link] under Goto → Session Overview.

Result You can now display the created Service Level Report and send it to the person responsible.

Save, Retrieve and Archive Service Level Report

Use You save Service Level Reports which you no longer need in the overview.

You can retrieve saved Service Level Reports.

You can archive Service Level Reports.

Procedure

Save service ...


2. Choose Global Strategy → Service Level Management, in the Operations screen.

You go to the Work Area for all Service Level Reports.


4. Select the Service Level Report which you want to save.


You go back to the overview screen. You go to the overview of saved Service Level Reports with the pushbutton Saved.

Retrieve service ...

1. Choose the Save pushbutton.

You go to the overview of saved Service Level Reports.

2. To retrieve a Service Level Report, choose Retrieve Service for it.

You go back to the overview screen. The retrieved Service Level Report is in the overview.

Archive service

Prerequisite

You must save reports before you can archive them.

You have the role SAP_SV_SOLUTION_MANAGER or SAP_SV_SOLUTION_MANAGER_EDIT.



Your archiving system is not part of the SAP environment. You must set-up an external archiving system (note 546685).

Archive sessions manually ...

1. Choose Archive Services in the repository.

2. Specify a date and confirm your entries.

The system archives the reports which are older than the specified date, with their attachments. The daily job RDARCH_CLEAN_DATABASE, deletes archived reports and documents physically from the database. You can no longer open archived reports. You can only display them.

Archive sessions automatically

You can schedule reports for automatic archiving from the repository. ...

1. Schedule the job RDARCH_ARCHIVE_DATA_SOLMAN with transaction SM37.

You can schedule the job periodically, e.g. daily, to archive all reports which are older than ten days.

2. The job archives reports in the repositors which are older than the specified age, with their attachments.

Accessing archived sessions and documents

You can access any report in the archive.

You can display, but not change saved sessions. When you archive reports, the system saves them in an external repository and deletes them physically from the database. This reduces the size of the database.

Result You can save Service Level Reports and retrieve them from the repository. You can archive Service Level Reports.

Process Service Level Report Session

Use You want the detailed session data for a Service Level Report. You process the session to add further information for the person responsible for the business process.

Procedure 3. Start the transaction SOLUTION_MANAGER.

4. Choose Solution Monitoring → Service Level Report, in the Operation area.

5. Choose Process Session.

You go to the Change Mode: SL Reporting.

You can specify the processors of the alert.



a. Choose the Post Processing of EW Alerts check.

� When you have processed the alert, set the Processed flag.

� If you want to postpone processing of the alert, enter a date in the Postponed until column.

b. Save your entries.

When you save, the system fills the remaining fields.

System Monitoring

Use The system monitoring monitors the systems in your solution landscape, in real time.

Integration The system monitoring is based on the Monitoring Architecture [external link] concept.

Prerequisites You have created a solution landscape.

You have set up the RFC sonnections between the SAP Solution Manager and the satellite systems:

• You have set the Assign RFC Dest. for System Monitoring flag in the System Landscape [page 71] (transaction SMSY) to generate the RFC connection.

Proceed as folows:

...

i. Choose the SAP Solution Manager system of your landscape components.

ii. Select a row.

iii. Generate your RFC connection in the Clients tab.

iv. Set the Assign RFC Dest. for System Monitoring flag.

• You have entered all required data about Load Balancing in the Solution Manager System Landscape (transaction: SMSY).

Proceed as folows:

...

i. Choose the SAP Solution Manager System of your landscape components.

ii. Generate your RFC connection in the Clients tab.

iii. Specify the RFC Destination Attributes.

• You have assigned the Solution Monitoring roles [page 129] to the users.

Activities ...

1. Set-up system monitoring [page 297].



2. Set-up user alerts [page 303].

3. Display the alerts in the alert graphic [page 301].

4. Reset alerts [page 302].

System Monitoring Change Mode

Definition You define the systems and alert monitoring thresholds in change mode in the system monitoring set-up session. The system generates system-specific checks for the following components:

• R/3-based SAP systems

• ITS

• IMS

• IPC

• LiveCache


• Left-hand column:

Displays all the checks which you should perform to set-up the system monitoring of your solution.

� Cross-system checks ...

i. Activate Monitoring

ii. Check CCMS Connectivity

iii. Copy Customizing

� System-specific subchecks ...

i. Setup Monitoring for SAP System

ii. User-Defined Alerts

� Additional hardware components (optional)

� Additional software components (optional)

System-specific checks are classified acording to the configuration of your solution landscape.

Any subitems of checks only appear when you have performed and saved the check. The subitems are partially preconfigured if the system has the necessary information.









CCMS and SAP Solution Manager

System and Business Process Monitoring in the SAP Solution Manager

The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) [external link] (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions [external link]. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.

You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system.

CCMS and system monitoring in the SAP Solution Manager

The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.

You want to monitor alerts of a J2EE Basis 6.40 (z.B. EP6.0). The J2EE 6.40 can be connected to a central CCMS (CEN) 6.40. You can thus also monitor alerts of these components in SAP Solution Manager 3.20 with Basis 6.20.



SolManST-SER 3.20

ABAP Stack 6.20EP5.0Java Stack 6.20

EP6.0J2EE Stack 6.40

DEVST-PI

ABAP Stack 6.20

QASST-PI

ABAP Stack 6.20

CENST-PI

ABAP Stack 6.40

DEVST-PI

ABAP Stack 6.40

Setting-up this alert in the system monitoring session is equivalent to Setting-up user-defined alerts [page 303].

The graphical display [page 301] in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.

The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session [page 297]. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwritin the values in the local CCMS.

CCMS and business process/interface monitoring

You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, „BPM“ of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.

The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:

• The system collects performance (dialog transactions), posting cancellations (V1 and V2) and „Other CCMS“ and interface data, in the local CCMS of the satellite systems.

• The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.

The SAP Solution Manager system copies the data from the local CCMS.

The graphical display [page 335] in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.



The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.

Set-Up System Monitoring

Use You want to specify which CCMS alerts are displayed in the SAP Solution Manager alert graphic.


� Choose Solution Monitoring → System Monitoring, in the Operations Set-Up area.

You go to an overview screen, from which you can go to the the system monitoring set-up in change mode, and call Best Practice documents.

6. Choose Set-Up System Monitoring.

You go to Change Mode: Solution Monitoring.


a. Select active systems [page 297]

b. Check CCMS Connectivity [external link]

c. Copy Default Values [page 299]

d. Handle system-dependent and system component-dependent checks [page 298]

e. Insert additionally hardware components (optional) [page 300]

f. Insert additionally software components (optional) [page 301]

Select Active Systems

Use You select the systems which you want to monitor.

Procedure ...

1. Select the Activate Monitoring check.

All systems are activated by default.

2. To deactivate the systems which you do not want to monitor, reset the Active? flag.

The system only lists ABAP-based systems.

3. To save your entries, choose the pushbutton Save + next w/o Check.




Check RFC Connection for System Monitoring

Use You check the availability of the selected systems. If you have not defined an RFC connection between the systems before setting-up the system monitoring, this check has the status red.

Procedure

Critical status (red) ...

1. Call the Solution Manager System Landscape (transaction SMSY).

2. Generate your RFC connection in the Clients tab.

3. Set the Assign RFC Dest. for System Monitoring flag.


The system classifies the check as uncritical in the session.

Uncritical status (green) ...

1. Select the Set-Up RFC Connections for Monitoring check in the SAP Solution Manager system monitoring set-up session.

2. Check the table entries.

3. To save the check, choose the pushbutton Save + next w/o Check.


Set-Up System-Specific Checks

Use You set-up alerts for your systems.

Procedure 4. To set-up alerts for a system, select the SAP System check for it.

The SAP System check is structured according to the configuration of your solution landscape.

5. Go to the CCMS Context tab to make the possible entries help for CCMS alerts available to the SAP Solution Manager for user alerts.

6. Choose a CCMS context from the possible entries help.

7. You can activate or deactivate alerts in the subchecks.

a. Select a check.

b. Set or reset the Active? flag for all alerts which you want to put in or remove from the alert graphic, respectively.



You can load the default configuration for all alerts which match the local CCMS values, which is predefined by SAP. Choose Load Defaults for R/3 System in the SAP System check.

The symbol in front of each check indicates the reachability of the alerts in the CCMS monitoring tree. The meaning of the symbols is explained in the Legend.

Reachability of the alerts

Symbol Meaning

Alert is reachable: The system has found the alert name iin the monitoring tree element (MTE) of the local CCMS.

Alert was reachable but is no longer: The system had previously found the alert name in the MTE of the local CCMS, but finds it now no longer.

Alert is not reachable: The system has not found the alert name in the MTE of the local CCMS.

Alert is not reachable: The system has not found the alert name in the MTE of the local CCMS. The alert is deactivated.

c. To see or change the attributes of the active alert, choose Properties.

You go to the transaction Monitoring: Properties and Methods (RZ20) of the system. You can switch between the attributes of the active alerts with Next Selection Object and Previous Selection Object.

d. Set the flag in the TID-Specific column, if you only want to set the settings for a specified alert, and not for the CCMS customizing group assigned to the alert.

If you have flagged the alert as TID-Specific, the system ignores your specific alert settings if it copies customizing to other systems later.

e. To save your entries, choose the pushbutton Save + next w/o Check.


Copy Customizing

Use You copy the alert customizing from one system or system component to another.

Procedure ...

1. Select the Copy Customizing check.

2. Choose the component whose alert settings you want to copy, in the Context column.

3. Choose the system/system component that you want to copy, as Source.

4. Choose the system/system component into which you want to copy, as Destination.



5. Choose Expand Systems to copy systems with components. The system fills the relevant fields automatically.

You can only copy customizing when the Source und Destination system/system components have the same database type.

6. To copy threshold values, set the flag in the Thresholds column.

7. To set the threshold values for each alert in the target system, set the flag in the TID-Specific column.

In the local CCMS in satellite systems, alerts are collected into attribute groups, e.g. alerts with the same threshold values. If you change, for example the threshold value of an alert in an attribute group, the system changes the threshold values of all alerts in the group. If you only want to change the threshold value of one alert in this attribute group, set the TID-Specific flag.

8. Choose Copy.

If inconsistencies occur, the system sends an error message. You can resolve the errors manually, or choose Correct Inconsistencies for an automatic correction.



Insert Additional Hardware Components

Use You assign CCMS alerts of a non-SAP ABAP system to a hardware server in your solution landscape, which is in the alert graphic.

Procedure 10. Select the Additional Hardware Components check.

11. Choose the hardware server for which you want to set-up alerts.

12. Choose the central monitoring system in the Central Monitoring System column.

13. Set the to monitor flag to activate the monitoring.



15. Select the Hardware Component check.

16. Choose the CCMS Context for user alerts.

17. Select the Set-Up Monitoring check.

18. Activate or deactivate alerts.

19. Maintain the thresholds.




Insert Software Components

Use You assign CCMS alerts to a software component, so that they appear in the alert graphic.

Procedure 21. Select the Additional Software Components check.

22. Choose the type and name of the software component for which you want set-up alerts.

23. Select the Specify Central Monitoring System check.

24. Choose the system with the assigned monitoring context, in the Central Monitoring System column.

25. Choose the CCMS Context to activate the possible entries help for user alerts.


Display Alert

Use You want to see the current status of your systems. You want display all open, i.e. not yet handled alerts.

Prerequisites You have set up system monitoring for your solution landscape.

Procedure Choose Create.


2. Choose Solution Monitoring → System Monitoring/Administration in the Operations screen.

You go to the overview of the system monitoring and system administration alert services. This view shows you the current status of your systems and components.

Description Meaning

SW Status Software alert status

HW Status Hardware alert status

BP Status Business process alert status

3. You can go to alert handling.

• System monitoring

The symbols show you the status of the system monitoring alerts. You can:

� go directly to the satellite system



i. Click on the right-hand mouse key in the box.

ii. Choose Logon to System <nn>.

You go to the satellite system.

� Display Alerts ...

i. Choose Display Alerts.

You are in the view of the selected current alert. This view shows you the current status of your systems and components.

ii. You can see the alerts in your systems and system components, in two ways:

� You can see all alerts in the system by choosing the associated symbol in front of one of its components. You can go from here to the alerts of the system components.

� If you choose the link of a component directly, you go to the graphical view of the system details of the component, and can navigate further from here.

The alert display in the SAP Solution Manager is the same as the CCMS alert monitoring in your satellite systems. The most critical alert for all elements of a node is displayed. If, for example, one or more components of a system have red alerts, the system has a red icon.

iii. Choose Open Alerts.

This view shows all not yet handled alerts and when they occurred.

The color is that of the most critical alert that has not yet been handled. This display does not necessarily reflect the current status of the system.

If you can go to the alert to be handled, you go to the maintained analysis method of the alerts in the system.

• System administration

The symbols show you the status of any open system administration tasks [page 314].

Result You can see and monitor the current status of your systems. You can analyze the not yet handled alerts, and handle or reset them.

Reset Alert

Use You reset an alert for a specified period while you analyze and handle it.

Procedure � Choose Solution Monitoring → System Monitoring/Administration in the

Operations screen.



You go to the overview of all alert services.

4. Go to the display of all not yet handled alerts, Open Alerts.

5. Select an alert to reset.

6. Choose Reset Alerts.

7. Specify the period for which you want to reset the display of the selected alert.

8. Confirm your entries.

Result The alert is not displayed for the period which you have specified.

Define User Alerts

Use You define an alert for a system in your solution, which is not in the SAP Solution Manager system monitoring.

Prerequisites The alert is: ...

1. not proposed for activation in the SAP Solution Manager system monitoring.

2. in the local or central (CEN) CCMS of the satellite system.

3. readable by the system via an RFC connection to the central (CEN) CCMS of the satellite system.

� If the satellite system < Web AS 6.40, you must assign this connection to the local des SAP Solution Manager CCMS.

The SAP Solution Manager CCMS determines the alert.

� If the satellite system => Web AS 6.40 you can specify the RFC connection in the system landscape maintenance (transaction SMSY).

You have selected a CCMS context in the system’s check.

Procedure ...

1. Call the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring → System Monitoring, in the Operations Set-Up area.

3. Choose Set-Up System Monitoring.

You go to Change Mode: Solution Monitoring.

4. Choose the User Defined Alerts check for the system, instance or server.

5. Choose an alert from the possible entries help for the Alert Long Name column.

The Alert Long Name is the MTE name in the local or central CCMS.

The system offers you all the alerts in the CCMS context specified in the check at system level <SAP system> <SID>.



If the possible entries help is empty, check whether the selected CCMS context exists and is accessible. If the system exists, you get the possible entries help. Otherwise, check the RFC connection.

6. Enter the alert name in the Alert Name column.

You can overwrite the alert name in the table.

7. Activate monitoring for the alert by setting the Active? flag.

You can see and change the alert attributes in the local system CCMS, e.g. analysis methods for the alert. Choose Properties.

� ...


Result You can display the user-defined alerts of your satellite systems, in the SAP Solution Manager alert graphic and alert overview.

Central System Administration

Use The central system administration manages tasks for the systems in your solution, centrally. The preconfigured view of your tasks, and the logical collection of the administration tasks help you to handle open tasks.

The system generates component-specific administration tasks, depending on the SAP system type.



• set up the RFC connections between the SAP Solution Manager and the satellite systems in your solution landscape.


�

Features You can:

• Set-up tasks for the systems in your solution

• Perform tasks

• Create task logs

• Monitor task plans

• Monitor task status

The system generates component-specific administration tasks, divided into logical areas, depending on the SAP system types.



Activities 9. Set-up central system administration initially [page 305].

10. Monitor and process tasks in the Central System Administration Session [page 314].

11. Set-up user-specific tasks [page 312].

12. Use the graphical display [external link].

Set-Up Central System Administration

Use SAP delivers all tasks for the session with inactive Task Frequencies. You must perform initial customizing.


• created a solution landscape.

• set up the RFC connections between the SAP Solution Manager and the satellite systems in your solution landscape.


The functional role to setup initial customizing of the central system administration contains the authorization object S_SAA_ADMI.


14. Choose Solution Monitoring → Administration in the Operations Setup area.

15. Choose Central System Administration.

You go to the Change Mode: Central System Administration session.

16. Perform the following tasks in the session, as required: ...

a. Choose Administration and Monitoring Work Area [page 307]

b. Task View Master [page 308]

c. Report Content [page 308]

d. User-Defined Task Master [page 312]

e. Copy Customizing [page 309]

f. Check RFC Destination [page 310]

g. Customizing Task Log Book and Task Log History [page 311]

h. Specify system data and initially setup tasks [page 311]

i. Cover Page [page 312]

Central System Administration: Seesion Change



Mode

Definition A session is an environment which is specially-developed to help you set-up and process the functions for a topic, e.g.:

• Solution Monitoring (e.g. System Monitoring) Session: Set-up and process Solution Monitoring

• Services (e.g. Health Check) Session: Service procedure; the system reads and analyzes data.

•

The Central System Administration session is a hierarchical tree structure which classifies important system and component tasks into logical areas.

Use In change mode in the session:

• Define the scope of Central System Administration for your solution

• Monitor and perform the tasks set-up


• Left-hand column – General tasks and the list of task groups:

� Initially shows all tasks which you need to set-up the Central System Administration for your solution:

� Specify Administration and Monitoring Environment

This group contains all the general administration tasks which you must set-up.

Choose Administration and Monitoring Work Area

Task View Master

Report Content

� General Session Customizing

This group contains all administration set-up tasks. You need authorization for the administration function ADM (authorization object: S_SAA_ADMI), to be able to edit the group. Otherwise, the following checks are not visible:

User-Defined Tasks Master

Copy Customizing

Check RFC Destinations

Customizing Task Log Book and Task Log History

� Cover Page



�

� When you have processed the Choose Administration and Monitoring Work Area tasks, the system generates the following tasks with task group lists, dynamically:

� General Basis Administration Task Group

� Database Administration Task Group

� Performance Monitoring Task Group

� Component-Specific Administration, e.g. mySAP CRM Administration Task Group

� User-Defined Task Group


Explains the use, background and procedure of the task.



Maintain the tables for each task.


Choose Administration and Monitoring Work Area

Use You choose a default view of the task group list.

Procedure ...

1. Select the Choose Administration and Monitoring Workarea check.

2. Set the flag to choose a default view.

Your choice of view determines how the system displays the list of task groups and their tasks.

Default views of the task list

View Meaning

ENTIRE The system displays all open and completed tasks.

TASK WORKLIST The system displays all open tasks, regardless of their frequency

DAILY OPEN The system displays all open daily tasks.

WEEKLY OPEN The system displays all open weekly tasks.

MONTHLY OPEN The system displays all open monthly tasks.



YEARLY OPEN The system displays all open annual tasks.

PERFORMED TASKS The system displays all completed tasks, regardless of their planned frequency.

SCHEDULED OPEN TASKS

The system displays all open scheduled tasks.

SCHEDULED PERFORMED TASKS

The system displays all completed scheduled tasks.


Task View Master

Use The system provides various default views. You can also define your own views of the task group list. The system provides 9 ways of specifying user views. You can adjust these views to your requirements.

Procedure ...

1. Select the View Master Task task.

2. The Standard Views tab shows the settings for the predefined views.

You cannot change these views.

3. You can specify which task type in the Task Type column you want to put in your view, in the User Views tab.

View 1:

� Daily open

� Daily performed

4. You can name your own view in the Logical User View Names tab.


Your view appears in the Choose Administration and Monitoring Workarea check.

Report Content

Use You specify the contents of customer-specific reports.



Prerequisite You have flagged tasks as completed. The system has written the completed tasks into the Task Log Book of the task.

Procedure 6. Select the Report Content check.

7. Choose the Define Content for Task Log History tab.

8. Flag whether you only want to put tasks with comments in the report.

9. You can specify a time period for the task report output, in the Task Logs from Date and Task Logs until Date columns.

You restrict the output of entries without comments additionally, by setting-up the Customizing Task Log Book and Task Log History [page 311] task.

10. Save your entries, to update the Task Log History table.

11. Go to the Tasks Log History tab.

You see all entries which appear in the report, in the same sequence.

Choose Tasks Log History to see the Tasks Log History as an HTML document.

12. Save your entries

Result You can now print the document as an MS Word report, with the MS Word Document pushbutton.

Copy Default Settings

Use You want to copy session and task customizing from from one system into another, or into all systems with one or more solutions. You can copy the following settings:

• User views

• Task frequencies

• Customer-specific task descriptions

• User-defined tasks

• Customizing Task Log Book and Task Log History

Prerequisite You have selected the view ENTIRE in the Choose Administration and Monitoring Work Area check.

Procedure 13. Select the Copy Customizing check.



14. Choose the source system to be copied, from the possible entries help in the Solution System column in the Copy Customizing from System tab.

The system fills other fields automatically.

15. You can copy customizing for some or all systems of a solution.

� Selected systems of a solution

� ...

Choose one or more target systems, from the possible entries help in the Target Solution column in the Copy Customizing to System tab.

� All systems of a solution

Choose one or more target solutions from the possible entries help in the Copy Customizing to Solutions tab.

You can perform several copies in parallel.

The system copies the source system customizing into each system in the target solution.

16. Indicate the amount of data to be copied, in the Copy Session tab:

� General customizing of the session, and/or

� User-specific tasks [page 312]

If you do not set a flag, the system copies the general customizing and the user-defined tasks.

17. Save your entries

18. Confirm the dialog box.

The system copies the customizing as soon as you call the central system administration session for the tsrget system.

Check RFC Connection ...

Prerequisite You have set up RFC connections between the satellite systems and the SAP Solution Manager of your solution, in the System Landscape (transaction: SMSY) .

Procedure 1. Select the Check RFC Destinations check.

2. Choose an RFC connection for the target system, from the possible entries help for the RFC Destination column.




Customizing Task Log Book and Task Log History

Use You specify the scope of the Task Log Books per task, and the Task Log History.

Procedure ...

1. Choose the Define Size of Task Log Book tab.

2. Specify the number of entries to be retained by the system in the Task Log Book per task.

If the Task Log Book contains more than this number of entries, the system deletes the oldest entries.

You should not set the number of entries too high, for performance reasons. The system proposes default values.

3. Choose the Define Size of Task Log History tab.

4. Enter the number of days for which the system task log is to show entries with comments.

The system deletes the Task Log History entries when you save the check. The system reorganizes the Task Log History automatically.

To create and analyze the Task Log History, go to the task Report Content [page 308].


Specify System Data and Initially Set-Up Tasks

Use Complete the system task effort.

Prerequisites You have set-up the view ENTIRE in the Choose Administration and Monitoring Work Area check.

� ...

Procedure

Specify system data ...

1. Select the check of the system check of the session <SID; installation number; nn>, which you want to administer.

2. You specify the type of your system in the System Type tab.

This field is for documentatory purposes only, and is displayed in the session, after the system names. You can also specify your own system texts.



3. You specify the components with which your system communicates, in the Involved Components tab.

The system generates a task structure for the selected component, dynamically.

Only process this table if the system is an R/3 backend system.

4. Choose Load Default Frequencies to activate default values for the frequency of tasks.

The default values are based on SAP experience.

You can activate the default values at session, system, or task level.


Specify frequency ...

1. Expand the higher-level check for the task groups.

You get a list of task groups.

2. Select the check of the task group.

3. Specify the frequency in the possible entries help for the task.

The system sets the task frequency initially to not active in the task list, when the central system administration is set-up.


Set-up Report Cover Page

Use You create an MS Word report.

Procedure 5. Select the Cover Page check.

6. Enter the name of the report, city and country.


Create User-Specific Tasks

Use You define your own tasks which are not in the SAP task list provided.

Procedure

Check: User Defined Task Master 8. Select the User Defined Task Master check.



9. Choose the Append Rows symbol in the Groups of Tasks tab.

10. Enter a group name.

11. Choose the group action type from the possible entries help for the Action Type column.

Action types

Action type Action

Function Function module name

Program Program name

Transaction Transaction code

URL URL

Others Do not specify an activity

You can use the activity type Others, if you do not want to assign a direct action, such as a transaction or URL, to the task. In this case, the system does not generate an Execute pushbutton in the header of the generated task.

12. Define the action in the Action column.

Group Description: RFC Destinations

Action Type: Transaction

Action: SM59


14. Go to the User Task tab.

15. Choose your group from the possible entries help for the Group column.

16. Assign one or more tasks to this group in the Task column.

Group: RFC Destinations

Task: Check the RFC Connection


Check: System level <SID> <installation number> <system type> ...

1. Select the system check to which you want to assign the task.

2. Go to the User-Defined Tasks tab.

3. Choose the Task and Group from the possible entries help.


The system generates a subcheck of the User-Defined Tasks in the systems with this group.

Check: User-Defined Task Group ... ...

1. Select the User-Defined Task Group subcheck with your group name.



RFC Destinations

2. Set-up the frequency of the user-specific task.


Check: User Defined Alert Handle user-defined alerts [page 314].

Result You can copy user-specific tasks to other systems in your solution, in the Copy Customizing check.

Process Open Tasks

Use You complete open tasks for the system, regularly in the session.

Prerequisites You have initially setup the session for the central system administration.

Procedure ...


2. Choose Operations.

3. Choose Solution Monitoring → System Monitoring/Administration.

4. Choose the CSA session symbol:

� No Open Tasks

You go to the CSA session.

� Display Open Tasks ...

You go to the list of open tasks.

5. Choose a task for processing.

The system goes to change mode.

6. Process the open tasks.

7. When the task is completed, flag it in the Done column.

You can set the status for one or more tasks of a check at the same time.

� For one task:

You set the status to completed by setting the flag in the Done column for the task.



� For several tasks:

You set the status with the pushbuttons in the status bar.

Status in the status bar

Status Meaning

Automatic rating The system determines the status of the task group from the status of its tasks.

All tasks performed You set all task in the table to Done.

The system sets all tasks in the task group to Done.

Critical issue You set the task group manually to the status Critical.

The system passes the status on down to system level.

When you set this status, the automatic rating is deactivated for this task group. You must reset this status manually to Automatic Rating, after performing the task.

The Critical Issue symbol indicates tasks with problems, or which you have not yet performed completely.

8. Enter a comment in the Comment for Log Book column.

The comments appear in the session report if you have created the Log History Task in the Report Content [page 308] check.

9. haben You can also make notes about the tasks, in the Task Notepad tab.

The notes in the Task Notepad are not output in the report.

Comments in the action list are in their own section at the end of the report. To maintain commentars in the action list:

i. Choose Action List in the top menu bar.

ii. choose New Session Action in the following dialog box.

iii. Enter the required data.


v.

10. You can enter customer-specific task descriptions in the Company-Specific Task Description tab.

This description appears for user-defined alerts in the Watcher action.


The check is given the status Task Performed.




Using Business Process Monitoring

Purpose Business process monitoring monitors your most important business processes, which can be distributed across complex system landscapes. You can also monitor the interfaces between your business process steps.

This enables you to identify critical problems proactively.



• implemented the ST-PI and ST-A/PI plug-ins in your satellite systems.

• set up RFC connections between the SAP Solution Manager and the satellite systems:

• a certification key. Cf.: Note 521820

If you use the Service Level Reporting [page 284] function, you have set up SAP EarlyWatch Alert [page 277] in the SAP Solution Manager.

You should have SAP perform the SAP Solution Management Assessment Service (SMA) or a Technical Integration Check (TIC).

Process Flow 13. You become aware of the SAP Solution Manager business process monitoring:

� order the service according to your requirements:

� in the SAP Marketplace

� from the SAP Solution Manager Service Catalog [external link]

� You receive an SAP quotation for performing the service.

� You or SAP analyze your most important business processes, for example to identify the systems and interfaces involved.

If you have performed an SMA service in the SAP Solution Manager, the data is available in the SAP Solution Manager.

14. SAP experts can develop a strategy to monitoring your business processes, containing:

� Solution Support Organization

� Business Process Documentation


� Integration and Interface Management

� Program Scheduling Management

� Master Data Maintenance

� Data Management and Archiving

� Change Management



� Key Performance Indicators (KPIs)

15. SAP experts configure your strategy in your SAP Solution Manager. Proceed as folows:

a. Set-up business process monitoring in the SAP Solution Manager Business Process Monitoring Session SETUP [page 324].

If you have not performed an SMA service, you must put your business processes and business process steps in the Solution Directory [page 258].

You activate the business monitoring in a Business Process MONITORING session [page 333].

b. You monitor the business processes in an SAP Solution Manager Business Process MONITORING session

There is always a SETUP Business Process Monitoring session, and corresponding Business Process MONITORING sessions for each business process which you have configured and generated in the SETUP Business Process Monitoring session.

If you took advantage of the SMA service, the system fills the SETUP Business Process Monitoring session with default values, which you can change.

16. SAP experts develop a service report containing the following data:

� business process analysis documentation

� monitoring checklist

� Action plan for subsequent activities

17. The customer sets-up more business processes for business process monitoring.


Use The business process monitoring monitors all business-specific processes. You can identify and solve problems at an early stage.

Integration The business process monitoring passes statistical data records to das Service Level Reporting [page 282].

You can create Service Desk [page 337] messages yourself from the business process monitoring, or have them created automatically by the system. The system writes the Service Desk message status in the Business Process MONITORING session of the business step.



• implemented the ST-PI and ST-A/PI plug-ins in your satellite systems.

• installed OCX.

• implemented die ST-SER and ST-A/PI plug-ins in your SAP Solution Manager Systems.



• created the user CSMREG in the SAP Solution Manager transaction SU01. (note 455356)


• set up RFC connections between the SAP Solution Manager and the satellite systems:

• a certification key. Cf. Note 521820

If you use the Service Level Reporting [page 284] function, you have set up SAP EarlyWatch Alert [page 277] in the SAP Solution Manager.

You should have previously performed the SAP Solution Management Assessment Service (SMA) or a Technical Integration Check (TIC).

Features You can monitor the following functions:

• the performance of business processes according to specified key performance indicators (KPI)

• background jobs via das Program Scheduling Management

• Business application logs, e.g. error logs, general application logs, due list logs

• data consistency and data transfer at system component interfaces

Activities ...

1. Create Business Processes [page 258]

2. Edit business processes for documentary purposes, in the Business Process MAINTENANCE session [page 322]

3. Set-up business process monitoring, in the Business Process Monitoring SETUP session [page 324]

4. Set-up interface monitoring, in the Business Process Monitoring SETUP session [external link]

5. Monitor the business processes in the Business Process MONITORING session [page 333]

6. Use the Process Graphic [page 335].

Session Change Modes

Definition In the change mode:

• of the business process monitoring maintenance session, you specify the business processes and business process steps which you have created.

• of the business process monitoring Setup session, you specify the business processes and their alerts which you want to monitor.

• of the business process monitoring Monitoring session, you monitor the business processes and process the alert messages.




Left-hand column

Displays all the checks which you must perform to set-up the business process monitoring of your solution.

Business Process Maintenance session

• Business Processes - Overview

• Interface Overview

• Contact Data

Business Process SETUP session

• Solution Support Organization

• Business Processes

� BPMon: <nn> ...

� Notifications

� Steps (according to process steps set up)

Monitoring Types (according to the number of monitoring types selected)

Monitoring Transactions

Monitoring Activities

Notifications

� Generate Monitoring Customizing

� Interface Monitoring

� Analyses and Monitoring tools

� Monitoring activities

� Notifications ...

• Data Collector Frequencies

• Local RFC Destination for Data Collection

• Monitoring Check Lists

• Cover Page

Business Processes MONITORING session

• Basic Settings

• Activation

• Business process

�



Any subitems of checks only appear when you have performed and saved the check. The subitems are partially preconfigured if the system has the necessary information.

�

Top right screen area:



Bottom right screen area:


You can call the online documentation in the logon language, for the checks, with HELP (see SAP note: 789703).

CCMS and SAP Solution Manager

System and Business Process Monitoring in the SAP Solution Manager

The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) [external link] (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions [external link]. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.

You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system.

CCMS and system monitoring in the SAP Solution Manager

The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.



You want to monitor alerts of a J2EE Basis 6.40 (z.B. EP6.0). The J2EE 6.40 can be connected to a central CCMS (CEN) 6.40. You can thus also monitor alerts of these components in SAP Solution Manager 3.20 with Basis 6.20.

SolManST-SER 3.20

ABAP Stack 6.20EP5.0Java Stack 6.20

EP6.0J2EE Stack 6.40

DEVST-PI

ABAP Stack 6.20

QASST-PI

ABAP Stack 6.20

CENST-PI

ABAP Stack 6.40

DEVST-PI

ABAP Stack 6.40

Setting-up this alert in the system monitoring session is equivalent to Setting-up user-defined alerts [page 303].

The graphical display [page 301] in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.

The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session [page 297]. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwritin the values in the local CCMS.

CCMS and business process/interface monitoring

You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, „BPM“ of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.

The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:

• The system collects performance (dialog transactions), posting cancellations (V1 and V2) and „Other CCMS“ and interface data, in the local CCMS of the satellite systems.

• The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.

The SAP Solution Manager system copies the data from the local CCMS.



The graphical display [page 335] in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.

The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.

Specify New Business Process

Use You want to document newly-created business processes and business process steps in detail.

Activities ...

1. Start the transaction SOLMAN_DIRECTORY.

2. Choose Business Process Details.

You go to Change Mode: SMO: Business Process Maintenance.


a. BP Maintenance

i. Business Processes - Overview [page 322]

ii. Interface Overview

iii. Maintain Contacts [page 324]

The system generates subchecks for the business processes and interface checks, automatically.

Select Business Processes

Use Choose the business processes for which you want to specify further details for monitoring.

Prerequisites You have created business processes in the Solution Directory [page 258].

Procedure ...

1. Select the check Business Process – Overview.

2. Flag the business processes which you want to set-up, in the Details column in the Core Business Processes tab.

3. Specify the priority of the step from the possible entries help for each process, in the Priority column.



4. Enter further details if required. You can:

� You can see a business process description template in the Template for Core Business tab.

� Describe your business processes in as much detail as possible in the Core Business tab.

5. Save.

� The system generates subchecks for each flagged business process.

� You can go to the Solution Directory with the Solution Directory pushbutton.

Specify Business Process Specify the business processes.

Procedure 6. Select the check Business Process <nn>.

7. Flag the business process steps which you want to set-up, in the Details column in the Core Business Processes tab.

8. Enter the system client (if R/3) in the Client column.

9. The Step Type (SAP Engl. terminology) column in the Process Steps tab shows which business process steps you want to monitor.

10. You can adjust the SAP terminology to your requirements, in the Step Name (Customer Terminology) column.

11. You can enter the person who is responsible for the business process, in the Business Process Champion tab.


13. You can flag the months in which the greatest load for this step occurs, in the Seasons/Peak Month tab.


15. Specify the times at which the business process is to be available, from the possible entries help in the Process Availability tab.

You can also specify your own availability times.


You can flag individual or all steps as performed:

� one step

i. Choose Done.

� all steps

� ...



� ...

ii. Choose Set „Done“ (w/o saving).

iii. Save.

Specify Business Process

Use Analyze the business process step.

Procedure ...

1. Select the check Step <nn>.

2. Flag a Processing Type, e.g. dialog or background, in the Yes column.

3. Enter data as required:

� You can see the previous business process steps, in the Preceding Step(s) tab.

� You can specify the person responsible for the business process, in the Power User tab.

� You can describe the step in detail in the Step Description tab.


You can flag the step as done. Choose Done.

Set-Up Contact Data

Use Record staff contact data.

Procedure ...

1. Choose the Maintain Contacts check.



Set-Up Business Process Monitoring

Use You want determine which processes and functions, e.g. background processing, important transactions or logs, are to be monitored.

To ensure quick processing of errors, you can specify detailed procedures for:

• Business Process Monitoring



• Error handling

• Contact persons

• Escalation paths

Prerequisite You have:


• set up RFC connections between your SAP Solution Manager and your satellite system.

• defined business processes and business process steps, in the Business Process MAINTENANCE session [page 322].

Activities ...


2. Choose Solution Monitoring → Business Process Monitoring, in the Operations Set-Up area.

3. Choose Set-Up Business Process Monitoring.

You go to Change Mode: SMO: Business Process Management.


a. Solution Support Organization [page 325]

b. Business Processes [page 326]

c. Data Collector Frequencies [page 329]

d. Local RFC Destination for Data Collection [page 330]

e.

Define Solution Support Organization

Use Specify the groups and group members of your support organization who are responsible for operational processing. You can assign monitoring roles to groups.

Prerequisite You are in the Business Process SETUP session.

Procedure ...

1. Select the Solution Support Organization check.

2. Specify the group name of your support organization.

To insert rows, choose Append Row or Insert Row.


The system generates subchecks for the groups, according to your entries.

4. Select a subcheck for your group.



5. Select the names and contact information of your group members from the possible entries help in the Team Members tab.

If you have setup contacts in the Contacts [page 261] tab in the Solution Directory, you can call them from the possible entries help.

6. Flag the monitoring role which you assign to the group, in the Monitoring Roles tab.

You can add a user role:

i. Flag the role Other Monitoring.

ii. Save.

The system generates a subcheck, Other Monitoring.

iii. Select the subcheck.

iv. Enter your role description.

v. Save.

The role is now available.


Select Business Processes

Use You select the business processes which you want to monitor.

Prerequisites You are in the Business Process SETUP session.

You have created a business process.

Procedure ...

1. Select the Business Processes check.

2. Flag the processes which you want to monitor, in the Core Business Processes tab.

3. Check whether the system has automatically set the Planned? column for your business process.

You can set business processes in your solution productive in the Solution Directory [page 258].


The system generates further subchecks.



Business Process Monitoring <Business Process>

Use Set-up monitoring for this business process.

Prerequisites You have flagged the business process for monitoring in the Business Processes [page 326] check.

Procedure ...

1. Select the BPMon <nn> check for the business process.

2. Flag which business process steps you want to monitor, in the Business Process Steps tab.

3. The 2. Process Description (Display) tab shows a process description template.

4. You can describe how to restart the process, e.g. in the case of a system crash, in the 3. Restart Process tab.

Describe such procedures in as much detail as possible.

5. Flag which interfaces you want to monitor, in the Business Process Interfaces tab.


7. Perform the following subchecks:

� Subcheck: Message Control Templates [page 327]

� Subcheck: Set-Up Process Step Monitoring [page 328]

� Subcheck: Generate Customizing [page 329]

Subcheck: Message Control Templates

Prerequisite You have asigned the role SAP_SOL_SERVTRANS_CREATE to the user.

Procedure ...

1. Select the subcheck BPMon: Notifications.

2. Enter the required data in the Workflow Notification tab:

Table fields

Field Meaning

Sender Sender of the message

Recipient Address Recipient of the message



Recipient Type Message type. Existing types:

R Name of the user in the connected SAP system, e.g. SMITHB. Specify also the system ID and the client in the fields TARGET SID and TARGET CLIENT.

C Distribution list, e.g. Business Process Monitoring

U E-mail address, e.g. [email protected]

B SAP User name, e.g. SMITHB

Target SID Target system (see Message Type R)

Target Client Client in target system (see Message Type R)

Detailed Flag whether the Workflow should contain notification long texts.

Enter the required data in the Support Notification tab:

Table fields

Field Meaning

Business Process/ Monitoring Type Business process and monitoring types

Priority Message priority

Processor Message processor

Automatic Messages sent automatically

Reporter Reporter

No. of Yellow Alerts Number of yellow alerts

Number of Red Alerts Number of red alerts


Subcheck: Set-Up Process Step Monitoring

Procedure 4. Select the subcheck Step <nn>.

5. Flag which montoring types you want to monitor for this process step, in the Relevant column, in the 1. Monitoring Types tab.

Set the Background Job flag.


7. Perform the monitoring type check(s).

i. Select the check Background Job.

ii. Flag the ABAP programs or transactions to be monitored.



If you maintain the ABAP program/transaction in the Solution Landscape Maintenance [page 262] (Transactions tab), it appears in the ABAP program/transaction selection possible entries help).


9.

Subcheck: Generate Monitoring Customizing

Prerequisite Before you generate the customizing, you must perform the subchecks Data Collector Frequencies and Local RFC Destination for Data Collection.

Procedure ...

1. Select the subcheck Generate Monitoring Customizing.

2. Choose Generate Customizing.

3. You can see the generation log in the Log tab.

Activate [page 334] the customizing in the Business Process MONITORING business monitoring session. If you have performed customizing, the system creates a new node for the satellite system, in the CCMS Monitoring Collection (transaction: RZ20).


Frequency of Data Collection

Use You want to specify how frequently data is to be collected.

Procedure ...

1. Select the Data Collection Frequency check.

2. Specify the frequency in minutes for each data collector per system.

You should retain the default value. The data collection period for the following monitoring types is 5 minutes.

� Dialog

� Update error

� Document volumes




Set-Up Local RFC Connections

Use Check and complete the local RFC connections.

Procedure ...

1. Select the Local RFC Destination for Data Collection check.

2. If the system has already set the check automatically to Done, you can go to the next check. Otherwise continue from step 3.

3. Specify a user with the authorization profile S_CSMREG.

4. Specify the password for the connection to the client BPM_LOCAL_<client>.

The RFC connection refers to the client which you also use in Business Process MONITORING.

5. Choose Generate Local RFC Destination.

If you do not maintain this information, you cannot monitor in the Business Process MONITORING session.


Set-Up Interface Monitor Objects

Use Define interface monitor objects. You can setup monitor objects for the following interfaces:

• ALE/EDI

• qRFC


• created a solution [page 259]

• created monitoring business processes in the Solution Directory [external link]

• created interfaces between your business processes in the Solution Directory [external link]

• setup the required interfaces in the Business Process Monitoring SETUP session [page 327]

• created a transport request

Procedure Create interfaces in the satellite systems

• ALE/EDI interface



You create monitor objects for outgoing (from sender system) and incoming (to recipient system) interfaces in the same way:

...

a. Create the monitor object in the satellite system: ...

i. Go to your satellite system in the view ALE/CCMS Monitoring Objects (transaction: BDMO).

ii. Choose the Create/Activate Monitoring Objects pushbutton.

You go to the table maintenance for the transaction.

iii. Choose New Entries, and enter the required data.

The monitor object name is valid for both the incoming and outgoing interfaces, if both sides are to be monitored.

iv. Save.

b. Detail the monitor object in the satellite system:

i. Go to your satellite system in the view ALE/CCMS Monitoring Objects (transaction: BDMO).

ii. Choose the monitor object from the possible entries help.

iii. Choose Change Monitoring Object.

You go to the Selection Conditions view.

iv. Define the message type for the interface.

If you:

� create in the sender system, you define the outgoing interface.

� create in the recipient system, you define the incoming interface.

v. Save your entries.

c. Start monitor objects in the view ALE/CCMS Monitoring Objects (transaction: BDMO) manually, if necessary:

i. Choose Monitoring Object-> Start All.

The system starts the job SAP_CCMS_MONI_BATCH_DP automatically every 15 minutes.

You can check whether the system has create the monitor object, in the view CCMS Monitoring Sets (transaction: RZ20).

ii.

• qRFC interface

� ...

d. Create the monitor object in the satellite system: ...

i. Go to Monitoring: Attributes and Methods (transaction: RZ21) in your satellite system.

ii. Choose Menü Techn. Infrastructure -> Configure QRFC Monitoring.

You go to the table maintenance for the transaction.



iii. Choose New Entries, and enter the required data:

Field Meaning

Owner Object name

Activity X

The name of the monitor object is valid for both the incoming and outgoing interfaces, if both sides are to be monitored


Create a transport request if necessary.

v. Select the relevant rows in the table.

vi. Double-click on the row Queue Group.

vii. Choose New Entries

viii. Select the owner from the possible entries help.

ix. Enter the queue group name from the transaction SMQ1 or SMQ2:

� SMQ1: Outgoing interface

� SMQ2: Incoming interface

x. Enter an MTE class name.

xi. Select the queue type from the possible entries help.

xii. Save.

xiii. Double-click on the row Queue Assignments.

xiv. Choose New Entries

xv. Select the owner from the possible entries help.

xvi. Save.

xvii. Run the QRFC monitor. Choose the following transaction:

� SMQ1: Outgoing interface

� SMQ2: Incoming interface

xviii. If the newly-created object has not appeared in the view CCMS Monitoring Sets after 15 minuten, start the monitor objects manually, with Monitoring Object -> Start All, in the view ALE/CCMS Monitoring Objects (transaction BDMO).

You can check whether the system has created the monitor object, in the view CCMS Monitoring Sets (transaction: RZ20).

CCMS Reload in the Solution Manager System ...

a. Choose the Business Process Monitoring SETUP session [page 324] in your SAP Solution Monitoring system



b. Go to the check for the interface Interface <nn>.

c. Choose CCMS Reload <nn>

The monitor object appears in the table.

d. Save your entries.

Business Process Monitoring Session

Use You want to:

• activate the Business Process SETUP session settings for a business process.

• monitor the activated business process.

Prerequisites You have set up business process monitoring in the Business Process SETUP Session [page 324].

Activities ...


2. Choose Solution Monitoring → Business Process Monitoring, in the Operations area.

3. Choose the Business Process Monitoring link to the desired business process.

You go to Change Mode: Business Process Monitoring.


a. Basic Settings [page 333]

b. Activation [page 334]

c. Business Process <nn> [page 335]

� Step <nn>

The system generates the check with its process step subchecks when you have activated the monitoring for the business process. Check the activation log.

General Settings

Use You want to specify important data for the business monitoring of the selected process.

Procedure ...

1. Select the Basic Settings check.

2. Enter the following data on the 1. Monitoring Data Retention Time tab:

a. Number of days for which you want to keep the monitoring data.

b. Number of days, after which the monitoring data is to be aggregated.



This number of days must not be greater than a).

c. The number of days for which the aggregate data is to be held.

This is relevant for confirming alerts and for Service Level Reporting [page 282].

3. Specify in which language you want to see the alert messages in the SAP Solution Manager, in the 2. Language for Alert Msg’s tab.


Activate/Deactivate Business Process Monitoring

Procedure ...

1. Select the Activation check.

2. Choose Activate Monitoring.

� Activation

When you activate the business process monitoring, the system created the required CCMS nodes in your satellite system, in the CCMS Monitoring Collection (transaction RZ20).

� Deactivation

When you deactivate the business monitoring, the system deletes the CCMS node in your satellite system, in the CCMS Monitoring Collection (transaction RZ20), so that no more data can be collected.

� Deactivation and Activation

If you change the customizing for the business process monitoring, in the Business Process SETUP session, you must generate the new customizing. You must first deactivate the old monitoring and then activate the new monitoring with the new customizing, in the Business Process MONITORING session.

The system deletes all current and aggregated alert data and the business monitoring process graphic shows no more alert information. The system only starts to collect data again when the data collector is active again.

No business process monitoring data is passed to the Service Level Reporting [page 289]. You should wait for the last Service Level report before you deactivate the business process monitoring and activate new customizing.

3. Check the log for warnings and errors.

The tab MTE Info shows detailed information about the monitoring objects which you have defined.




Call the session again after activation, to get current alert information.

Display Alert Information

Procedure ...

1. Select the Business Process <nn> check.

You can check the following aspects of the business process in the tabs:

Tab Meaning

Business process steps You see all business process steps which you have selected for monitoring

Workflow messages You can change or add to the workflow messages here, without having to regenerate the customizing in the Business Process SETUP session.

Support messages

You can change or add to the workflow messages here, without having to regenerate the customizing in the Business Process SETUP session.

Process description You see the process description which you maintained when setting up the business process monitoring.

Restart the process You see the description which you maintained when setting up the business process monitoring.

Subcheck: Step <nn> You can check various aspects of the business process step, in the tabs, analogously to the business process. You can confirm alerts and create Service Desk messagef for alerts [page 336] in another subcheck, Alert Messages.

Subcheck: Alert Type You can check various aspects of the alert type, in the tabs, analogously to the business process.

2. If you have made changes, save your entries.

Display Alert

Use You want to see the current status of your business processes/interfaces. You want display all open, i.e. not yet confirmed, alerts, for handling.

Procedure Choose Create.


2. Choose Solution Monitoring → Business Process Monitoring, in the Operations screen.

The business process overview of your solution landscape is displayed graphically, organized by business process, business process step, and interfaces.



The system flags only active business processes.

3. You can see the alerts in your systems and system components, in two ways:

� You can see a critical business process by choosing the Symbol in front of the business process name. You can go to the business process alerts. If you choose the alert link, you go to die Business Process MONITORING session.

� If you choose a business process Link, you go to the graphical view of the business processes, with their business process steps. You can navigate further from here.

The alert display in the SAP Solution Manager is the same as the CCMS alert monitoring in your satellite systems. The most critical alert for all elements of a node, is displayed. If, for example, a monitoring object of a process has a red alert, the system has a red icon.

4. Choose the alert links, to see and handle the alerts at your interfaces.

You go to the maintained analysis method of the alert, in its system.

Result You can confirm [page 336] and further process the not yet handled alerts, when you have analyzed them, e.g. in the Service Desk, to SAP or by E-mail.

Confirm Alerts

Use Confirm handled alerts.

Prerequisite You have resolved the alert in your satellite system.

You are in the check of the alerts which you want to confirm, in the Business Process MONITORING session.

Procedure ...

• Individual alert

a. Set the alert handled flag in the Confirm column.

b. Choose Confirm.

c. Save.

• Selected by alert rating

� ...

� all yellow alerts

i. Choose Confirm All Yellow.

ii. Save.

� all red alerts

� ...



iii. Choose Confirm All Red.

iv. Save.

�

Service Desk

Purpose You use this component to process internal support messages, and forward them to SAP Support, if necessary.

Integration Your project team members can create messages, which you can manage centrally in the Service Desk, in all project phases, e.g. in the Blueprint and during the test phase. Your internal customers, i.e. end or key users, can also create support messages from any SAP system. You process these support messages centrally in the Solution Manager Service Desk.

Features

Central management of support messages • Direct creation of support messages from any transaction

• Automatic capture of important data about the system in which the support message was created, e.g. installation number, installed software components, operating system, transaction, screen number.

• Automatic assignment of the support message to a support level

• Central message processing in the SAP Solution Manager:

� Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)

� Assign processor

� Send messages to the creator and other processors

� Forward message to other processors or support units

� Create documents and URLs

� Attach documents

� Status assignment and monitoring

� Create a worklist with selection conditions

Search for and import SAP notes • Search for SAP notes in the SAP Service Marketplace

• Import SAP notes with the SAP Notes Assistant

� Automatic corrections in ABAP source code

� Adjust changes to already imported Support Packages

� Display all SAP notes which were imported into a system with the SAP Notes Assistant



Internal solution database You can search for problem solutions in your internal solution database. The solution database is delivered without symptoms and solutions. You construct the internal solution database with the functions Edit Symptoms and Solutions (IS01) and Update Solution Database Index (IS02). For further information about creating your own solution database, see under http://help.sap.com/ → SAP Customer Relationship Mgmt. → SAP CRM 3.1 → Search for „Customer Service (CS), Solution Database“ → Solution Database in the Search menu.

Interface to SAP Support The Support Desk is your interface to the SAP Service & Support. You can forward messages to SAP and receive problem solutions, in the Service Desk.

See also:

• Process description, under Service Desk [page 338].

• Service Procedures [external link]

Using the Service Desk

Purpose This process allows your internal customers or end or key users to create problem messages directly from a transaction. This enables them to contact your Service Desk easily. Your internal Service Desk can comprise several support units.

The Service Desk processor responsible for the problem can enter symptoms in an internal solution database, and search for solutions. He can also search for SAP notes in the SAP Service Marketplace. If no problem solution is found, the processor can forward the problem message to subsequent support units or to the SAP Support, and monitor the progress of the message in the Service Desk.

Prerequisites • You have configured the Service Desk according to the Solution Manager configuration

guide.

• You have set-up the criteria by which an incoming support message is assigned to a support unit, e.g. priority, category, region of creator, in the Service Desk customizing. The system assigns the support message to the support unit for its SAP component, by default. See SAP note 616946.

• You have the Service Desk authorizations [page 132] required for your tasks.

Process Flow ...

1. The customer or end or key user creates a support message:

� under Help → Create Support Message in a transaction menu in an SAP system

� independently of the SAP system, in a web browser.

For further information about setting-up this function, see Set-Up Message Creation in Web Browser [page 339].

� directly in the SAP Solution Manager in the Messages tab, or the Service Desk -> Create Message tab for Service Desk staff

2. The system captures the system data for the support message, automatically.

3. The support message arrives in your Service Desk.



a. The system assigns the support message to the appropriate support level automatically, e.g. by SAP component, priority or support message category.

b. The system determines the associated business partners, e.g. customer, key user or support team, automatically.

c. The system creates a service process in the SAP Solution Manager.

d. If the customizing is set appropriately, the system checks whether there are existing contracts for this installation and customer. Such a contract can, for example, contain a Service Level Agreement (SLA), in which the customer has been guaranteed certain services, for example maximum response times.

If a contract is found, choose the relevant contract item, e.g. Support, Consulting or Development.

4. A member of the support unit responsible declares himself to be the processor in the support message.

5. You search for a solution for the problem described by the customer, in the customer’s own solution database [page 340].

6. If you find no solution in your customer solution database, search for SAP notes in the SAP Service Marketplace [page 341].

If you find a relevent SAP note, assign it to your support message. You can import and test appropriate SAP notes with code corrections directly into your development or test system, with the SAP Note Assistant. After testing, transport the changes into your quality assurance or production system. You can easily discard any unwanted changes with the SAP Note Assistant.

7. If you find no solution in the SAP Service Marketplace, put an internal note in the customer message, detailing the measures which you have so far taken to find a solution, and forward the problem message to the appropriate next support units.

8. If the next support unit can also not solve the problem, put an Information for SAP in the problem message, with any appropriate attachments, and send the problem message to the SAP Support [page 342] (SAPNet R/3 Frontend).

9. The SAP Support processes the message and sends it back to you with a proposed solution or further question, and an updated status.

You can monitor the status of the support message at any time in your Service Desk.

10. The appropriate members of your internal support organization, e.g. the Customer Competence Centers, test and evaluate the proposed solution.

11. The member of your internal support organization delivers the solution to the person who reported the problem, in one of the existing communication channels.

12. The person who reported the problem tests and confirms the solution.

13. The Service Desk processor closes the message and formulates the solution found, for the internal solution database, if it could be of use to other Service Desk staff.

Set-Up Message Creation via Web Browser

Use Users who have no access to an SAP system, can create a message for your service desk in a web browser, with the BSP application dswp_create_message. The message system data is captured automatically in the background and sent to the service desk in the Solution Manager system.



Prerequisites You have installed the BSP application according to the SAP notes 699087 and 742691.

Procedure

The Internet Communication Framework [external link] (ICF) path to the BSP application dswp_create_msg input screen is:

/sap/bc/bsp/sap/dswp_create_msg/msg_new.do ...

1. Enter the name of your SAP Solution Manager web application server, the port number, and the client, in the URL:

http://<host>:<port>/sap/bc/bsp/sap/dswp_create_msg?sap-client=<client>

2. You can create an alias/quick link to the BSP application, to simplify the message creation BSP application call. For further information, see Internal Aliases [external link].

Process Messages in the Service Desk

Use You process the messages which staff or customers have created, in the Solution Manager Service Desk.

Prerequisites You have the role SAP_SOL_SERVTRANS.

Procedure ...

1. Choose Tools → SAP Solution Manager → Solution Operation (SOLUTION_MANAGER) in the SAP Easy Access menu.

2. Choose a solution landscape.

3. Choose Service Desk.

4. Display the message:

� To display a list of open support messages, choose All Open Messages → Execute pushbutton, in the possible entries help.

� To search for a message:

i. Choose the Start Transaction Monitor pushbutton and specify your selection criteria.

You go to the Transaction Monitor Service Procedures (CRM_DNO_SERVICE_MONITOR)

ii. Select a message and choose Detail.

You go to the detail screen of the message

5. You can choose the arrow key Display Minimal, to display all details for the message.

To set-up the message display with all details for your user, choose Extras → Settings → General tab, and set the Narrow flag for the display type in the Locator screen area.



6. Choose the Change pushbutton, to process the message.

7. Choose a message processor in the screen area Reference in the possible entries help.

8. Choose the Transaction Data pushbutton.

9. Process the message. You can:

� Upload documents

� Create URLs and documents

� Search for solutions in the internal solution database

� Search for Solutions in the SAP Service Marketplace [page 341]

� Import SAP notes with correction instructions, automatically:

i. If you have found a suitable SAP note with automatically importable correction instructions, in the SAP Service Marketplace, assign it to your support message.

ii. Go back to the Service Desk.

iii. Select the SAP note.

iv. Choose the Note Assistant pushbutton in change mode.

v. Specify the RFC connection to your development or test system, into which you want to import the SAP note.

vi. Import the note. For further information, see the SAP Note Assistant help.

vii. Test the changes.

viii. Transport the changes into your quality assurance or production system.

You can discard any unwanted changes with the SAP Note Assistant.

� Send messages to the creator and other processors

� Forward the support message to other processors and SAP [page 342]

10. Choose the Fast Entry pushbutton and assign a status to the message.


Find Solution for Support Message

Use You process the messages which staff or customers have created, in the Solution Manager Service Desk.

PrerequisitesYou are in the detail screen of a support message in the Transaction Monitor Service Procedures.

Procedure...

Search for solution in SAP Service Marketplace ...


2. Choose the Search for Notes pushbutton in the SAP Notes tab, to search for SAP notes in the SAP Service Marketplace.



You go to the SAP Service Marketplace.

3. Logon to the SAP Service Marketplace.

4. Search for SAP notes in the search template.

5. To assign an SAP note which you have found, to the support message, copy the note number and the short text of the SAP note to the SAP Notes tab.

To display an assigned SAP note, select it and choose Display Note.

You can import SAP notes with correction instructions into your systems automatically. For further information, see Processing Messages in the Service Desk [page 340].

6. Leave the SAP Service Marketplace by closing the browser window.

Search for solution in the solution database If you have found no suitable SAP note for your problem, search for a problem solution which has already been documented in your solution database. ...


2. Choose the Search SDB pushbutton in the Solution Database tab.

The system automatically uses the support message short text as search criterion.

3. Specify your search criteria and choose Continue.

The system displays the existing symptoms and solutions for your support message. You can copy these solutions into your support message.

Forward Support Message to SAP

Use You forward a support message to the SAP Support if you can neither process it yourself nor find a solution for it in SAP notes or your solution database.

Prerequisites You are in the detail screen of a support message in the Transaction Monitor Service Procedures.

Procedure ...

1. Write information for SAP in the Overview tab.

2. Attach any documents for the support message in the Documents tab.

3. Choose the Action pushbutton.

4. Choose Send Message to SAP from the drop-down list.


The system sends the support message when you save.

Result You can monitor the procedure in the SAP Attributes tab:

• You see the SAPNet R/3 Frontend message number of the procedure.

• You can monitor the changed status.



Change Request Management

Purpose Change Request Management enables you to manage your maintenance and implementation projects from top to bottom: Starting with change management and project planning, through resource management and cost control, to physical transports of changes from the development environment into the productive environment.

Ongoing software and configuration changes as well as large implementations are ongoing challenges for managing data consistency and secure project control. Change Request Management as part of SAP Solution Manager integrates Service Desk functionality for managing change requests, and extends project control by integrating project planning with the cProjects application into a transport workflow control.

The processes supported by Change Request Management include urgent corrections for implementing fast and direct changes in the productive environment, and maintenance cycle activities such as regular releases, and implementation, upgrade, or template projects. Cross-system and cross-component changes are supported.

Change Request Management offers you the following benefits:

• Increased maintenance and project efficiency

• Minimized costs for project management and IT

• Reduced risk of correction and project failure

• Shorter correction, implementation, and going-live phase

• Efficient maintenance of customer developments and implementations

Integration Change Request Management is a scenario of SAP Solution Manager and contains interfaces to the following SAP solutions:

• SAP Solution Manager for managing Customizing projects

• Service Desk for creating and managing change requests (optional)

• cProjects for managing project planning (optional)

Features • Management of maintenance and implementations spanning multiple components

• Powerful service request management plus project management for controlling, planning, design, development, testing, and going live

• Comprehensive, workflow-driven management of distributed activities comprising planning, development, maintenance, and production

• Powerful project change tracking

We recommend that you initially use Change Request Management to manage your urgent corrections and maintenance cycles; you can then install the Service Desk to benefit from additional functionality for managing large implementations, and upgrade and template projects.



Roles in Change Request Management

Before users can start working with Change Request Management, the system administrator (or equivalent user) has to create user roles that contain the relevant authorizations, and then assign these roles to the corresponding users. The roles have to be created (by using transaction SU01) for users in the three main system groups of Change Request Management:

• Service Desk system [page 344]

• Change Request Management system [page 344] (Change Request Management and the Schedule Manager run in this system)

• Satellite systems [page 345] that are managed by Change Request Management

Service Desk Roles

The following roles are delivered with SAP Solution Manager 3.20 and have to be assigned to the corresponding users in the Service Desk system:

SAP_SOCM_CHANGE_MANAGER

The change manager is responsible for approving or rejecting change requests.

SAP_SOCM_DEVELOPER

The developer makes corrections in the development system and releases the necessary transport requests.

SAP_SOCM_TESTER

The tester is responsible for testing corrections in the test system to check whether they work.

SAP_SOCM_IT_OPERATOR

The IT operator imports corrections into the production system.

SAP_SOCM_PRODUCTION_MANAGER

The production manager decides whether corrections can be imported into the production system. (In certain critical situations such as during a payroll run, the production manager can decide not to import corrections into the production system; otherwise, the system could be rendered inconsistent.)

SAP_SOCM_REQUESTER

The requester is the person who creates change requests.

SAP_SOCM_ADMINISTRATOR

The administrator customizes and checks all Change Request Management functions in the Solution Manager system.

Schedule Manager Roles

The following roles are delivered with SAP Solution Manager 3.20 and have to be assigned to the corresponding users in the Change Request Management system:



SAP_CM_SMAN_ADMINISTRATOR

The task list administrator in Change Request Management deals with the administrative and technical side of maintenance cycles and urgent corrections; in particular, the Schedule Manager task lists.

SAP_CM_SMAN_DEVELOPER

The developer is the user who is responsible for making corrections in the maintenance and development systems.

SAP_CM_SMAN_OPERATOR

The operator deals with the operational side of task lists.

SAP_CM_SMAN_PRODUCTIONMANAGER

The production manager approves imports into the production systems.

SAP_CM_SMAN_TESTER

The tester is the user who is responsible for testing and validating corrections in test systems.

Satellite System Roles

• Real Users

From a transport point of view, the remote architecture of Change Request Management consists of one central system (Change Request Management server) where all transports are controlled, and satellite systems where transport requests are created, released, and imported. In all these satellite systems, the local users need to have special authorizations within the Change and Transport System (CTS) according to their particular tasks.

For users in the satellite systems that have the system role types Development, Test or even Production, assign the following roles:

� SAP_CHANGEMAN_DEVELOPER

Contains the authorization profile S_TMW_DEVELO. CTS authorizations for developers: No authorization to create transport requests , and no authorization to release transport requests but to create and release tasks.

� SAP_CHANGEMAN_OPERATOR

Contains the authorization profile S_TMW_OPERA. CTS authorizations for operators: All transport authorizations; no configuration authorizations

� SAP_CHANGEMAN_ADMIN

Contains the authorization profile S_TMW_ADMIN. CTS authorizations for administrators: All authorizations in the CTS (including configuration)



Note that the roles SAP_CHANGEMAN_PROJECTASSISTANT and SAP_CHANGEMAN_PROJECTLEAD are obsolete; do NOT assign them to users.

For SAP R/3 Releases lower than SAP Web Application Server 6.10, the profiles listed above are available, but not the roles. Therefore, you have to explicitly assign the authorization profiles to the relevant users.

• Trusted System Users

For all client system actions in Change Request Management, users are required to log on by using trusted systems. For this purpose, you must also assign trusted system authorizations to the relevant users. In particular, you have to assign the authorization object S_RFCACL. For more information, see Technical Requirements -> Automatic Generation of Trusted System RFC Destinations (in SAP Solution Manager: Configuration Guide).

• Background User

A connection has to be created from the SAP Solution Manager system landscape (transaction SMSY) to all system that have the role type source system. For more information, see the online documentation: help.sap.com -> Documentation -> SAP NetWeaver -> Solution Manager -> Solution Manager 3.x -> Solution Manager System Landscape -> Create Systems -> Generate RFC Connections. In these logical systems, a communication (background) user is generated for executing tasks in the background (user SOLTMW<cm-sid><cm-client>). This background user automatically has the following profiles from the CTS area:

� S_TMW_CREATE for creating and releasing transport requests in development systems as well as for setting the project status switch for creating transport requests

� S_TMW_IMPORT for importing transport requests into test systems (empty)

The most important task of the background user is to create and release transport requests and tasks remotely from Change Request Management. Requests that are created in this way are known to Change Request Management, which means that Change Request Management can control the distribution of these requests within the landscape.

Requests that are created, released, or imported locally cannot be identified by Change Request Management in conjunction with a change request and are therefore not part of the Change Request Management transport control and distribution process. For this reason, we recommend that no users (apart from administrators) have authorization to create transport requests or tasks in Change Request Management-controlled clients.

• Import Authorization Checks

Change Request Management uses the import functions of the Transport Management System (TMS). The TMS remote infrastructure is based on RFC connections that point solely to the 000 client of a target system. For this reason, you must make sure that Operators and Administrators have users both in the client into which changes are imported, and in the 000 client of these systems.



• Automatic Imports

In test systems, it is sometimes necessary that imports are performed automatically. If you want developers within the Change Request Management scenario to start imports into a test system automatically, you must add the profile S_TMW_IMPORT to the user TMSADM in client 000 of the test system. Since S_TMW_IMPORT is delivered empty, you have to assign it the authorizations S_CTS_IMPALL and S_CTS_IMPSGL, which are also contained in the authorization object S_CTS_ADMI.

It is now possible to start an import into this system from every remote system within your domain by using the CPIC user TMSADM; therefore, do not use this method in production systems or in any other security-critical systems.

The system where you want to start the import automatically must share the same transport directory as its preceding system. If the transport directories were different, the user who starts the import would need “addtobuffer” authorizations for the buffer adjustment, which would present a security risk not only for the system concerned, but also for the whole landscape (including the production system).

Authorizations

• Schedule Manager roles

The following table shows which task list authorizations are assigned to the Schedule Manager roles:

Developer Tester Prod. Manager

Operator Administrator

Display X X X X X

Create X --- --- --- X

Change --- --- --- --- X

Delete --- --- --- --- X

Run X X X X X

Change status

X X X X X

• Satellite system roles

The following table shows which transport request/task authorizations are assigned to the satellite system roles:



SAP_CHANGEMAN_OPERATOR SAP_CHANGEMAN_ADMINISTRATOR

------------“trusted” user

---(possible with additional authorizations)

------------TMSADM (background user)

User in client 000

---SAP_CHANGEMAN_OPERATOR SAP_CHANGEMAN_ADMINISTRATOR

SAP_CHANGEMAN_DEVELOPERSAP_CHANGEMAN_OPERATOR SAP_CHANGEMAN_ADMINISTRATOR

SAP_CHANGEMAN_OPERATOR SAP_CHANGEMAN_ADMINISTRATOR

SAP_CHANGEMAN_OPERATORSAP_CHANGEMAN_ADMINISTRATOR

“trusted” user

---XXXXSOLTMW<SID><CLI> (background user)

User in target client

IMPORT REQUESTRELEASE REQUEST

RELEASE TASKCREATE TASKCREATE REQUEST

Transport Methods

Central Configuration Tool of Change Request Management

Purpose The Central Configuration tool of Change Request Management allows you to configure system-specific and project-specific settings. The tool takes into account all systems defined in SAP Solution Manager, as well as all projects that are created in SAP Solution Manager.

Prerequisites • You have configured Change Request Management.

• You have configured all your systems in SAP Solution Manager (transaction SMSY).

Features On the Change Management - Central Configuration screen there are four tab pages:

General Settings

Here you configure the data collector of Change Request Management. See Scheduling the Data Collector [page 349].

Distribution Routes

Here you configure transport routes and make project-specific settings. See Displaying and Configuring Transport Routes [page 349].

System Change Option

Here you define system change parameters for components, namespaces, and clients. See System Change Option [page 353].

Project Structure



Here you can view the relationship between systems, clients, and projects, as well as between projects, IMG projects, and CTS projects. See Project Interdependencies [page 355].

Scheduling the Data Collector

Use Before you can start to use Change Request Management, you have to schedule the data collector.

Procedure 6. Call transaction /TMWFLOW/CMSCONF.

7. Select the General Settings tab page.

8. In the Data Collector group box, make an entry in the Schedule every and Timeout after fields.

9. Choose Schedule Collector.

The system schedules the data collector and the transport of status information into the system where Change Request Management runs.

You can choose to reset the collected data for a particular system. To do so, enter a system ID in the System field and choose Reset Data. We recommend that you reset the data every time you make a system copy so that the memory of the transport history can be regenerated.

When you schedule the data collector, a background job (BTC_CMS_COLLECTOR) is started. If you want to deactivate this job, use transaction SM37. If you change the time for starting the job, the previous job is deactivated.

Result A green circular icon appears on the General Settings tab page to indicate that the data collector has been scheduled correctly.

If a yellow triangular icon appears, this indicates that the data collector has not been scheduled correctly. Repeat the procedure if necessary.

Displaying and Configuring Distribution Routes

Use You want to display or configure distribution routes in your system landscape or in your project landscape.

A green circular icon on the Distribution Routes tab page indicates that the projects have one of the following statuses: Created, Released, or Completed. A yellow triangular icon indicates that the status of at least one project is Locked.



Procedure

To display the transport routes in the Change Request Management system landscape, proceed as follows:

1. Call transaction /TMWFLOW/CMSCONF.

2. Select the Distribution Routes tab page.

3. In the System Landscape group box, choose System Landscape.

You can also make changes to the configuration of the server, databases, systems, and system components in SAP Solution Manager [page 60].

To check that the set-up of the TMS configuration is Change Request Management-compliant, proceed as follows:



3. In the System Landscape group box, select a transport domain.

4. Choose TMS Configuration.

An overview of all systems that belong to the transport domain you selected is displayed.

5. Double-click any system to display the current configuration.

6. If you need to make any changes, switch to change mode.

The recommended TMS settings are described in Customizing for SAP Solution Manager (SV-SMG): SAP Solution Manager → Scenario-Specific Settings → Change Request Management → Standard Configuration → Transport Management System (TMS).

To display the transport routes that have been configured for the whole system landscape proceed as follows:



3. In the System Landscape group box, select a transport domain.

4. Choose System-Specific Transport Routes.

You can make changes to the transport routes by switching to change mode.

To display the systems that are part of a particular project landscape, proceed as follows:



3. In the Project Landscape group box, select a Solution Manager project.

4. Choose Project Landscape.

The system switches to the project administration tool of SAP Solution Manager.



If you need to make changes to the project landscape, you can do so by switching to change mode. In particular, you can change the assignment of logical components to Solution Manager projects (System Landscape tab).

To display the transport routes that have been configured for a particular project, proceed as follows:




4. Choose Synchronize Configuration.

You only need to perform this step once. This ensures that all Solution Manager project landscapes are checked against the transport routes in the Transport Management System, and against the IMG projects in the satellite systems. Subsequently, these checks are performed synchronously when a project is saved.

5. Choose Project-Specific Transport Routes.

The system displays all the transport routes for the project that you selected.

If the system displays an empty screen, this is an indication that the transport routes for this project have not been configured correctly. You cannot make any changes to the configuration on this screen; instead, you have to go back to the previous screen and choose Project Landscape again to configure the routes in the project administration tool of SAP Solution Manager.

To display the project status switches for a particular Solution Manager project, proceed as follows:



3. In the Project Landscape group box, select a Solution Manager project whose status is Active or Released.

4. Choose CTS Status Switches.

The system displays the Display Project Status Switches screen. The top node of the display contains the CTS projects and the nodes below contain the systems that are part of the project landscape. The sequence in which the systems are displayed depends on whether a transport track [external link] exists. If a transport track exists, the systems are displayed in the sequence of the systems in the transport track; the exporting systems are displayed first, followed by the systems that receive transports from the exporting systems. If no track exists, the development system is displayed as the top node, and the production system is displayed as the last node; the remaining systems are displayed in a random sequence.

If you change the sequence of the systems that belong to the distribution route in SAP Solution Manager, you have to refresh the display on the Display Project Status Switches screen

If you need to change any of the project status switches, proceed as follows:

1. Under the node of the system whose project status switch you want to change, double-click the relevant project status switch (Requests cannot be created, for example).

The system displays the Change Project Status Switches dialog box.



2. Choose No.

The Display Project Status Switches screen now displays the setting of the selected system as Requests can be created.

If you want to manually generate a task list for a maintenance cycle, proceed as follows:




4. If you have defined a customer-specific variant in Customizing for SAP Solution Manager, choose Project Task List Variant.

If you use a customer-specific variant to create task lists, make sure that the mandatory tasks contained in the SAP0 variant are also included in your variant.

5. Select the variant that you want to use for generating the task list.

If you have not defined a customer-specific variant, task lists are generated by using the standard SAP0 variant.

If you want to create a project cycle, proceed as follows:



3. In the Project Landscape group box, select the project for which you want to create a project cycle.

The status of the project must be Released.

4. Choose Create Project Cycle.

5. Enter the name of the task list of the maintenance cycle.

6. If a dialog box appears, in which you are asked whether you want to go to the task list, proceed as follows:

a. Choose Yes.

b. In the task list, choose Status.

c. In the Set Status for Maintenance Cycle dialog box, select Activate and then choose Continue.

The system sets the status of the project cycle to Development wo Release.

d. Set the status of the general tasks, the track, and the general final tasks to Active.

The system has now created a service transaction for the maintenance cycle. The status of the service transaction for the project cycle is set to Development wo Release. For maintenance projects, you can now execute urgent corrections completely, and regular corrections up to the phase where transport requests are created. For development projects, you can execute project requests up to the phase where transport requests are created.



Activating Project Status Switches

Use Project status switches are automatically deactivated when a task list is generated. This means that transport requests for the corresponding CTS projects cannot be created, exported, or imported. The transport methods of the task list activate certain project status switches as required and then deactivate them again. However, you may need to manually activate project status switches for a particular project.

Procedure


2. In the Project Landscape group box, select the project whose project status switches you want to activate.

3. Choose CTS Status Switches.

4. Activate the corresponding switches by double-clicking them and then choosing Yes.

System Change Option System change options are interpreted according to system roles. A logical system that has the role of development system in one project, for example, cannot simultaneously have the role of test system in another project. In a system in which a client has the role of test client for project 1 and in a different client has the role of development client for project 2, cross-client changes are not permitted. The system change options interpret the change options of systems, components, namespaces, and clients and relate them to the roles of Solution Manager projects.

On the Change Management – Central Configuration screen, you can display and change certain system change options by selecting the System Change Option tab page.

First you see an overview of the systems and clients in your project landscape that you defined in SAP Solution Manager.

Icon Legend

The status of each client in a system is determined according to two criteria:

• Role of the client

• Values of different parameters that might affect how the client functions in a particular role

• Production System (role type = P)

The status is RED in the following cases:

� Client settings allow repository changes

� Client settings allow changes to client data

� CATTS can be started

� Transport requests can be exported from the system

� System is modifiable



In all other cases, the status is GREEN.

• Test System (role type = O)

The status is RED in the following cases:

� Client settings allow repository changes

� Client settings allow changes to client data

� System is modifiable

The status is YELLOW if client settings allow the export of transport requests. In all other cases the status is GREEN.

• Development System (role type = D)

The status is YELLOW if project assignment is optional for the client. In all other cases the status is GREEN.

• Single Systems or Standalone Systems (role type = S)

Every type of configuration is permitted; no system status is displayed.

The overall system status that is displayed is the most negative status of all the clients (red = most negative).

Proj. Assignment column

You can check for each system whether it is mandatory to assign transport requests to a project. If all clients that are defined as logical systems of a transport route are mandatory, the whole system project assignment state is set to mandatory. If one client that is defined as a logical system of a transport route is set to optional, the whole system project assignment state is set to optional. Other clients can be displayed here, but they do not belong to your project landscape

.

We recommend that you set the assignment of transport requests to a project as mandatory. To change this setting, double-click the relevant entry. The system navigates to the relevant system where you can change the setting.

Sys. Change Option column

You can check whether modifications are permitted for each system.

We recommend that you set your test and production systems as non-modifiable. To change this setting, double-click the relevant entry. The system navigates to the relevant system where you can change this setting.

Software Components and Namespaces/Name Ranges

You can display the change options of your remote systems by double-clicking a system name in the System/Client column. If you want to change any component or namespace change options, you can double-click the relevant entry on the right-hand side of the screen (Software Components or Namespace/Name Range table).

Client Settings and Project Status Switches

You can display client settings of your remote systems by expanding the first node in the overview (System/Client column), and then double-clicking the corresponding client. The system displays two tables in the right-hand screen area: Client <number> and Project Status Switch.



If you want to change any client settings, you can double-click the relevant entry in the Client <number> table.

You cannot change the project status switches on this screen (see Displaying and Configuring Transport Routes [page 349]).

Since the system change option data has to be buffered in SAP Solution Manager, you either have to schedule the batch job for synchronizing the system landscape, or you schedule the batch job /TMWFLOW/CONFIG_BATCH_GET exclusively.

Project Interdependencies On the Project Structure tab page of the Change Management – Central Configuration screen, you can display various system and project interdependencies. You can switch between the project view and the system view. The default layout of these views is a tree display, but you can switch to a grid display by choosing Grid Display. (To switch back, you choose Tree Display).

• Project View

Here you can display the relationship between cProjects (projects created in the cProjects application), Solution Manager projects, IMG projects, CTS projects, and task lists. You can also see the status of each Solution Manager project (Released, Active, Locked, or Finished). The entries in the Date and Time columns indicate when the Project View table was last updated.

• System View

Here you can display the relationship between systems, clients (logical systems), Solution Manager projects, CTS projects, and (logical) system roles.

By double-clicking the entry in the Identifier, IMG Project, CTS Project, Transport Request, Change Transaction, and Task List columns, you can navigate directly to the corresponding maintenance view.

Scheduling Tool of Change Request Management

Purpose To execute the operational activities for distributing software in your system landscape, Change Request Management provides a scheduling tool. This tool is based on the Schedule Manager.

Prerequisites You have configured Change Request Management.

Features You can use the scheduling tool to perform the following activities:



• Create maintenance cycles [page 356] for executing your development and maintenance tasks (for regular maintenance and for urgent corrections)

• Create urgent corrections [page 359]

• Display and change the status [page 361] of maintenance cycles and urgent corrections

• Analyze [page 363] maintenance cycles and urgent corrections

Creating a Maintenance Cycle

Use You want to make changes in systems as part of your planned maintenance period, and import all these changes simultaneously into production systems at the end of the maintenance period. For this purpose, you want to create a maintenance cycle.

A maintenance cycle is the period of time in which you:

• Make changes in maintenance systems

• Include these changes in new transport requests

• Import these requests into follow-on systems for testing

At the end of a maintenance cycle, all transport requests are imported into the production system at the same time. Subsequently, the maintenance cycle can be closed manually and a new one can be created, if necessary (but only in compliance with the rules of the change requests that belong to the maintenance cycle).

A maintenance cycle and the tasks that have to be executed as part of the cycle are contained in a task list of the Schedule Manager. This task list is generated automatically when you create a maintenance cycle. The Service Desk transaction for managing cycle phases is also generated.

If you want to create an urgent correction [page 359] in Change Request Management, first you have to create a maintenance cycle. New urgent corrections always have to be assigned to an existing maintenance cycle.

If the system landscape of a maintenance cycle is changed incompatibly (if a system is added to a route, for example), you can ignore the checking rules of the cycle and close the current maintenance cycle. Subsequently, you can create a new task list. At the same time, a new Service Desk cycle is created automatically. To close an incompatible maintenance cycle, start the report /TMWFLOW/TL_COMPLETE_FORCE. However, only do so if absolutely necessary. Alternatively, you can use the TMS to provide the new systems with data during a project.

Prerequisites • You have created at least one maintenance project [page 25] in SAP Solution Manager,

and specified which systems you want to use for this project.

• You have created transport routes between the systems that you specified in SAP Solution Manager (in Customizing for SAP Solution Manager → Scenario-Specific Settings → Change Request Management → Standard Configuration → Transport Management System → Define Transport Routes for System Landscape).



• You have provided Change Request Management with your configuration data (transaction /TMWFLOW/CMSCONF → Distribution Routes → Synchronize Configuration).

Procedure


2. Choose Scheduling.

3. On the Mainten. Cycles tab page, select Create New Maintenance Cycles.

The system displays a list of the maintenance projects that you created in SAP Solution Manager, including the corresponding maintenance and production systems.

One maintenance project can have multiple maintenance systems assigned to it, including the corresponding transport routes (one logical system for Workbench requests and one logical system for Customizing requests, for example). A maintenance cycle belongs to exactly one maintenance project.

4. Select the maintenance project for which you want to generate a maintenance cycle.

5. Choose Create Maintenance Cycle.

6. In the dialog box that appears, enter a short description for the new maintenance cycle (maintenance cycle for project ABC, week 12, for example). This text helps you to find the maintenance cycle later.

The system generates a task list in the Schedule Manager and a service transaction for managing the maintenance cycle.

7. In the dialog box that appears, choose Yes to navigate to the task list.

8. On the task list screen, choose Status.

9. Select Activate.

The system changes the status of the maintenance cycle from Created to Development Without Export. Alternatively, you can choose Phase to set the status of the task list as Active. In the dialog box that appears, choose Next Phase.

10. Choose Phase.

The system displays the current phase, and allows you to switch from this phase to the previous one or to the next one. In the same way, you can switch between the phases of the service transaction.

11. Click the General Tasks node with the secondary mouse button.

12. Choose Lock/Unlock Group/Subsequent Groups.

The system unlocks the tasks in the task list.

13. Repeat steps 11 and 12 for the Track of Project <n> and General Final Tasks nodes.

Result The system displays your new, activated maintenance cycle as a task list in the Schedule Manager.

Note that you cannot create the ID of the maintenance cycle yourself; the system generates the ID automatically. The name consists of the prefix M (for maintenance) and a consecutive number, which is taken from the number range object /TMWFLOW/M. You defined a number range for this object when you installed Change Request Management.

All systems that are part of your maintenance project landscape including the tasks that have to be executed are displayed in the task list. The sequence in which the systems and tasks (task groups) are displayed depends on the transport track [external link] and the types of



system roles. In addition, the header contains general tasks and the footer contains general final tasks that automatically appear in every task list that is generated.

The task groups of the task list are displayed in the Schedule Manager as follows:

• At the highest hierarchy level of the task groups you see the transport routes that originate from exactly one maintenance system. If you defined <n> maintenance systems in the Solution Manager project, you see <n> task groups at the highest hierarchy level.

• Above the task groups, you see a task group for the general header tasks.

• Below the task groups, you see a task group that contains systems without a transport connection (if there are any). These systems are either postprocessing systems or single systems. However, if you have included systems of other types in your maintenance project, but have not defined transport routes in TMS for them, they also appear here.

• At the bottom of the task list, you see a task group with the general final footer tasks.

• Each task group for a transport route contains three additional groups, which correspond to the types of system roles. Three groups are always displayed (Source Systems, Target Systems, and Production Systems), even if there is no system for a role type in your Solution Manager project whose role is assigned to this type. The additional group for the systems without a transport connection (Postprocessing Systems and Single Systems, for example) appears if systems have been defined for these groups.

• The next hierarchy level contains the system roles that are assigned to the role type (but only if there are systems in the roles).

• The lowest hierarchy level of the task groups contains the logical system (system name and client) of the role.

• For each system you see the tasks that are planned for a system of this type.

You can now proceed to execute tasks for your maintenance cycle and create urgent corrections [page 359].

See also:

Changing the Status of Maintenance Cycles/Urgent Corrections [page 361]

Status Administration of Task Lists for Maintenance Cycles [page 358]

Status Administration of Task Lists for Maintenance Cycles When you navigate from a maintenance cycle to the corresponding task list, the system displays the task list in a version of the Schedule Manager that has been adapted to the requirements of Change Request Management. In addition to all Schedule Manager functions, there is a status administration function available to you.

The status administration of the task list is almost the same as the status administration of the Schedule Manager and is documented in the Schedule Manager (Help → Application Help). Additionally, the status of the tasks in the daily overview or in the monitor is transferred to the task list. In the task list, the status of the tasks is initially Locked or Unlocked, depending on the status of the task group. As soon as a task has been executed, its status is changed to the status of the (last) execution. If, for example, you start a task that returns the status Contains Errors, you then see this status in the daily overview, in the monitor, and in the task list. If, subsequently, you start the task again, but the task returns the status Warning, you see



this status for the newly scheduled items in the daily overview, in the monitor, and in the task list. The former Contains Errors status in the task list has now changed to Warning, while the status of the previous execution remains unchanged in the daily overview and in the monitor.

The status in the task list refers to the last execution of the corresponding task. You can still manually set the status (by using the secondary mouse button), and display the status history. The status history in the task list refers to the last execution of the corresponding task. If you want to see additional information apart from the status history of all previous executions, you have to look in the daily overview or in the monitor.

Apart from the tasks, also the task groups and the task list have a status. Task groups are either locked or unlocked. The tasks initially have the same status as the task group to which they belong. Tasks can only be executed if the status of all task groups higher in the hierarchy is Unlocked. The status of the entire task list, which is the highest node in the task list display, can be Initial, Locked, Active, or Completed. Tasks that belong to a task list can only be executed if the task list is active. If the status of the task list is Completed, it can no longer be changed or activated, an tasks in this task list can no longer be executed. All tasks that have never been executed now receive the status Skipped.

Urgent Corrections If you want to import corrections into a production system immediately; that is, before the end of a maintenance period, you have to create an urgent correction. An urgent correction can consist of one or more transport requests.

Whereas a maintenance cycle groups transport requests that belong to one maintenance period, and imports them all simultaneously into the production systems at the end of the period, an urgent correction imports only one (or just a few) transport requests immediately (before the end of a maintenance period). If you need to create an urgent correction, you have to assign it to a specific maintenance cycle. An urgent correction is similar to a maintenance cycle, except that different tasks can be planned.

If you want to define new tasks or change the definition of predefined tasks, you can do so in Customizing for SAP Solution Manager (SV-SMG) by choosing SAP Solution Manager → Scenario-Specific Settings → Change Request Management → Extended Configuration → Schedule Manager.

While the task list of a maintenance cycle contains all the systems that you defined in the maintenance project, the task list of an urgent correction contains exactly one production system (where the problem occurred) and only the systems that are on the shortest transport route from a development system to the production system. The reason for this is that you want to implement your urgent correction as quickly as possible.

To import a number of urgent corrections simultaneously into production systems, you can use the report CRM_SOCM_SERVICE_REPORT. You can also import urgent corrections that have been completed into parallel production systems by using the report /TMWFLOW/SCMA_BTCH_SYNC_UC.

If you want to create urgent corrections for maintenance cycles for which a service transaction has been generated, you can only do so by using a service transaction. The standard service transaction provided by SAP for urgent corrections is called SDHF.

Note that you cannot create the ID for the urgent correction yourself; the system generates the ID automatically. The ID consists of the prefix H and a consecutive number, which is taken from the number range object /TMWFLOW/M, for which you defined a number range when you installed Change Request Management. The task groups are displayed in the same way as for a maintenance instance.



If a task list for an urgent correction is generated by the service transaction SDHF, the status of the task list is set by the service transaction, too. In the task list of the Schedule Manager, no tasks can be started if the task list was generated by a service transaction. In the Schedule Manager, you can, however, manually set the status of a task that has been completed (by setting a checkmark), provided that you have the corresponding authorization.

Scheduling the Automatic Import of Urgent Corrections

Use You want to schedule the import of urgent corrections into your test and production systems by using periodic background processes. In doing so, you ensure that the state of each system is consistent.

Prerequisites • A maintenance cycle exists whose status is Active. Only those urgent corrections that

are assigned to this maintenance cycle are included in the automatic import.

• For one development system you have defined and activated multiple, parallel follow-on systems (test systems).

• For one development system you have defined and activated multiple, parallel production systems.

• The urgent correction has been imported into the production system where the change request originated.

Urgent corrections that are imported into the production system where the change request originated are not imported into other parallel production systems.

• The corresponding change transaction has been completed.

• The tracking process of the central system knows that the urgent correction has been imported into the first production system.

Procedure Execute the report /TMWFLOW/SCMA_BTCH_SYNC_UC as follows:

1. As mandatory import parameters, specify the following:

a. System ID and the client of the system into which you want to import the urgent corrections

b. Name of the Solution Manager project that is assigned to the active maintenance project

2. Using the Job Wizard (transaction SM36), schedule the report /TMWFLOW/SCMA_BTCH_SYNC_UC as a background job.

If the report ends in an error, check the batch log file (transaction SM37).



Result After every run of the batch job, a message is written to the application log. You can view this log in transaction SLG1. In the Object field, enter /TMWFLOW/CMSCV and in the Subobject field, enter SCHEDMAN.

Resetting Unsuccessful Corrections

If you notice in a test system that a correction you made contains errors, or if you decide that you do not want to make a particular correction (for a maintenance cycle or as part of an urgent correction), you want to prevent the corresponding transport request from being imported into your production systems. However, it is not sufficient simply to cancel this particular import, since all transport requests that are created within a maintenance period are imported simultaneously into the production systems at the end of the period (applies to maintenance cycles and urgent corrections). This means that you cannot isolate the transport request that contains the unsuccessful correction.

The solution is that you have to create an additional transport request where you withdraw the unsuccessful correction. This new transport request is also imported into your production systems, and invalidates the unsuccessful correction.

If the objects involved in the correction have not been changed in the meantime, and if the correction did not affect other objects (no processes or data were changed), you can simply reset the objects to the previous version (if versioning exists for the objects) and activate them.

If the objects have been changed in the meantime by another correction, you have to remove the unsuccessful correction without changing the new correction. It does not matter if the unsuccessful correction has already affected processes and data, since it has not been imported into the production systems yet. However, if you want to correct the data in your test systems, you have to make local corrections.

Changing the Status of Maintenance Cycles

Use You want to see an overview of the maintenance cycles that you have already created, view detailed information about them, or change their status.

Procedure

The steps in this procedure refer explicitly to maintenance cycles; however, you can also use this procedure for urgent corrections. If you want to do so, select the Urgent Corrections tab page instead of the Mainten. Cycles tab page.

To display an overview of maintenance cycles, proceed as follows:


2. Choose Scheduling.

3. On the Mainten. Cycles tab page, select Display Existing Maintenance Cycles.



The system displays a list of the maintenance cycles whose status is Active (default setting).

4. To display cycles that have other statuses, choose Status Selection.

5. Select the relevant status(es), and choose Enter.

6. Select the cycle whose status you want to change.

7. Depending on which status you want, choose with the quick info text Lock Maintenance Cycle, with the quick info text Activate Maintenance Cycle, or with the quick info text Complete Maintenance Cycle.

8. You can display additional information about a maintenance cycle by selecting it and choosing Production System or Maintenance System, or by clicking the entry in the Maintenance System/Development System, or Production System columns. If there is more than one production or maintenance system/development system assigned to the maintenance project/development project, a list of the corresponding systems is displayed.

9. Click the entry in the Maintenance Cycle column or choose with the quick info text Display Maintenance Cycle.

The system displays the task list in the Schedule Manager where you can execute tasks.

New maintenance cycles or project cycles have the status Initial. Before you can execute tasks for a new maintenance cycle, or change the task list, you have to set its status to Active, and then unlock the task groups and tasks in the Schedule Manager.

You can also change the status of the task list:

1. Choose Status.

The system displays the Set Status for Project dialog box.

2. Select Active.

3. To release the task groups and tasks, select the first entry of the task group hierarchy in the task list that has the status Locked.

4. Click this entry with the secondary mouse button and choose either Lock/Unlock Group (to release only this task group and its tasks), or Lock/Unlock Group/Subsequent Groups (to release all task groups and their tasks).

5. If you decide during a maintenance cycle that no tasks are to be executed for a certain period of time, you can lock the cycle. To do so, in the overview table, select the cycle, and choose with the quick info text Lock Maintenance Cycle. You can only continue to execute tasks for this cycle once you have activated the cycle again.

6. Instead of locking the whole task list, you can also decide to lock a particular task group, including all embedded task groups and tasks. To do so, click the task group with the secondary mouse button and choose Lock/Unlock Group/Subsequent Groups.

7. If the end of a particular cycle has been reached, you set the status of the cycle to Completed by choosing with the quick info text Complete Maintenance Cycle.

This ensures that no more tasks can be executed and no more changes can be made to this cycle. However, once a cycle has been completed, it can no longer be locked or activated.

8. If you need to delete a task list, select the corresponding row in the Schedule Manager and then choose Task List → Delete.



9. If the status of the task list has changed since you displayed the task list, you can refresh the display by choosing Edit → Refresh.

You can also see the following:

� Description of the task list

� User who set the last status

� When the task list was generated

� When the task list was last activated

� When the task list was completed

� Which tool created the task list (Change Request Management or the Service Desk)

Analyzing Maintenance Cycles and Urgent Corrections

Use At any time, you can display the task lists that belong to your maintenance cycles and urgent corrections (including additional information). In addition, there are various options available for analyzing maintenance cycles or urgent corrections.

Procedure

The steps in this procedure refer explicitly to maintenance cycles; however, you can also use this procedure for urgent corrections. If you want to do so, select Analyze Urgent Corrections instead of Analyze Maintenance Cycles.


2. Choose Tracking or Scheduling.

3. Select the Scheduling Analysis tab page.

4. In the Selection group box, select Analyze Maintenance Cycles.

Result The system displays a list of the maintenance cycles that have been activated. (To display maintenance cycles that have other statuses, choose Status Selection and select the corresponding status(es).)

This list contains the status of the various tasks as follows:

Highest Status of Executed Tasks column

The sequence is as follows (the highest status is displayed):

Statuses of Executed Tasks

Status Explanation

Not Defined Status of the executed task is unknown

Aborted Execution of the task was canceled

Error Task was executed with errors



Warning A warning was triggered when the task was executed

OK Task was executed without errors

Checked Execution of the task was checked

Highest Status of Non-Executed Tasks column


Statuses of Non-Executed Tasks

Status Explanation

Skipped Task was skipped; this status is set by the system when you complete the task list (when you set the status of the task list to completed)

Active Task is currently being executed

Released Task is scheduled in the future and has been released; execution of the task has not started yet

Not Active Task is scheduled in the future but has not been released yet

Unlocked Task has been released, but has not been started or scheduled

Locked Task has not been released yet

Highest Status of Mandatory Tasks column


Statuses of Mandatory Tasks

Status Explanation

Skipped Task was skipped; this status is set by the system when you complete the task list (when you set the status of the task list to completed)

Active Task is currently being executed

Released Task is scheduled in the future and has been released; execution of the task has not started yet

Not Active Task is scheduled in the future but has not been released yet

Unlocked Task has been released, but has not been started or scheduled

Locked Task has not been released yet

Not Defined Status of the executed task is unknown

Aborted Execution of the task was canceled

Error Task was executed with errors



Warning A warning was triggered when the task was executed

OK Task was executed without errors

Checked Execution of the task was checked

The other columns in this list contain the following information:

� Description of the task list

� User who set the last status

� When the task list was generated

� When the task list was last activated

� When the task list was completed

� Which tool generated the task list (Change Request Management or Service Desk)

You can perform additional analyses in the Schedule Manager monitor. Proceed as follows:

1. Select a maintenance cycle.

2. Choose Maintenance Cycle (or click the entry in the Maintenance Cycle column).

To display transport requests, proceed as follows:

1. Select a maintenance cycle.

2. Choose Transport Requests/Tracking.

The system displays all transport requests that belong to the maintenance cycle. The following information is displayed:

� Task list name of the urgent correction (if the transport request belongs to an urgent correction)

� Transport request number

� Status of the transport request in the source system:

� Modifiable

� Release started

� Released

� Transport request type

� System in which the request was created

� Project ID in the Change and Transport System (CTS project), which is the same for all transport requests of a maintenance cycle

� Who created and released the request

� When the request was released

� Which tool created the task list, and its ID

If you select a row in the list and choose Display Maintenance Cycle or Display Urgent Correction, you can navigate to the task list.

If you select a row in the list and choose Tracking for Transport Request or Tracking for Maintenance Cycle, you can navigate to the transport log of the selected transport request or to the transport logs of all transport requests of the maintenance cycle.



Using Project Logistics

Use Whereas the Central Configuration, Tracking, and Scheduling tools of Change Request Management provide a cross-project view for system administrators, Project Logistics provides a project-specific view for IT operators.

System administrators set up the system environment for projects; IT operators, on the other hand, monitor system states for one or more projects, and perform operative actions.

Prerequisites • You have generated a project cycle for a Solution Manager project.

• You have scheduled the data collector in the Central Configuration tool of Change Request Management.

• You have IT operator authorizations.

Procedure


2. Choose Project Logistics.

3. In the Project Type drop-down list, select a project type and then choose Save.

4. Expand the Projects node.

5. Select a project that you want to monitor.

6. Click the project with the secondary mouse button and choose Add to Favorites.

7. Click the project with the secondary mouse button again and choose Set as Default.

You can add any number of projects to your favorites, but you can only set one project as the default.

Result The project has been added to your favorites. If you want to remove the project from your favorites, you click it with the secondary mouse button and choose Delete from Favorites. Since you also set the project as the default, next time you access Project Logistics, the system will automatically display this project.

You can decide which tab pages are displayed on the Project Logistics screen by choosing Settings → User-Specific Settings.

You can proceed to display various aspects of the project (and perform operative actions) by selecting the corresponding tab page:

• Scheduling

• Tracking

• Planning



• Project Monitor

• Project Structure

• CTS Status Switches

• System Change Options

Using the Scheduling Function

Use IT operators use the scheduling function to execute operative actions for a project (either as a background process or online). This function provides a project-specific daily view of scheduling in Change Request Management.

Prerequisites You have selected a project that has a cycle assigned to it.

Procedure

1. On the Project Logistics screen, select the Scheduling tab page.

The system displays the daily overview of the task list for the selected project.

2. In your role as IT operator, perform your daily tasks here.

3. To display the task list with the calendar overview, choose Full Screen.

4. Schedule your future tasks, and analyze previous tasks on this screen.

See also:

Scheduling Tool of Change Request Management [page 355]

Using the Tracking Function

Use IT operators use the Tracking function to analyze the current status of transport requests and maintenance levels for a particular project in the project landscape.

Prerequisites • You have scheduled the data collector in the Central Configuration tool of Change

Request Management.

• You have updated the relevant data on the Tracking screen.

Procedure

1. On the Project Logistics screen, select the Tracking tab page.

The system displays three views:



� Project landscape according to the project routes that have been defined

� Project change status according to the project-specific transport requests

� System maintenance status, including the status of Support Packages and SAP Notes

2. Perform your analyses for the project on this screen.

See also:

Tracking Changes for One Project [page 371]

Using the Planning Function

Use IT operators can view the planning phases and tasks, including their attributes, status, and description.

Prerequisites • You use cProjects as your project planning tool.

• You have assigned a cProjects plan to your task list.

Procedure

1. On the Project Logistics screen, select the Planning tab page.

2. Choose Save in cProjects.

3. Make changes to the attributes or status of tasks as required.

4. To go to the current project plan, select a task and then choose Save in cProjects.

Using the Project Monitor

Use IT operators use the Project Monitor to display the status of project cycles, messages, change requests, and change transactions.

Prerequisites You have created a project cycle (and change requests/transactions, if necessary).

Procedure

1. On the Project Logistics screen, select the Project Monitor tab page.

2. Select a variant that displays the project cycles, messages, change requests, or change transactions that you want to view. (You can save the variant as the default variant.)

Depending on the variant that you chose, the Project Monitor displays the transactions, including their status, transaction number, priority, and current processor, for example.

3. To go to the selected service transaction, double-click the relevant row in the Project Monitor.



See also:

Change Transactions in Change Request Management [page 375]

Using the Project Structure Function

Use IT operators use the Project Structure function to display the structure of a particular project, including the relevant transport requests.

Prerequisites • You have scheduled the data collector in the Central Configuration tool of Change

Request Management.

• You have created a project cycle for the selected project.

Procedure

On the Project Logistics screen, select the Project Structure tab page.

The system displays a hierarchy with the following elements:

• Solution Manager project

• IMG project

• CTS project

• Transport requests

If a cProjects plan has been assigned to the project, this is displayed as a project attribute. The change transaction for the active cycle of the project and the task list are displayed as additional project attributes.

See also:

Project Interdependencies [page 355]

Activating CTS Status Switches

Use The CTS status switches are deactivated by default when a project cycle is generated. This means that the tools of the Change and Transport System cannot be used to create, release, or import transport requests. For troubleshooting purposes, however, system administrators are allowed to activate these switches.

Prerequisites • You have Administrator authorizations.

• You have generated a project cycle for a project.

• A task list exists for the project.

Procedure



1. On the Project Logistics screen, select the CTS Status Switches tab page.

2. Double-click the switch that you want to activate (Requests cannot be created, for example).

The system activates the switch, and you are now allowed to create transport requests for a particular project without using Change Request Management.

Displaying/Changing System Change Options

Use You want to display an overview of the system change options of the systems that are in a particular project landscape. You can view or change details such as the assignment of a transport request to a project, system change options in general, as well as component, namespace, and client change options.

Prerequisites • You have Administrator authorizations.

• You have synchronized the system landscape setup data or have scheduled /TMWFLOW/CONFIG_BATCH_GET as a background job.

Procedure

1. On the Project Logistics screen, select the System Change Options tab page.

The system displays a tree containing the systems (and logical systems) that are in a particular project landscape. You can see whether project assignment is mandatory and the status of the system change option.

2. To make changes to these attributes, double-click the relevant attribute.

In the right-hand screen area, you can see the system change options of the software components and the namespaces of the components.

3. To make changes to the components, double-click the relevant component.

4. To view client change options, select the relevant client by double-clicking it.

The system displays the project status switches underneath the client change options.

5. To make changes to the client change options or the switches, double-click the relevant option.

See also:

System Change Option [page 353]

Change Tracking in Change Request Management

Purpose The Change Tracking function of Change Request Management allows you to track everything that relates to changes within the context of a Solution Manager project, or an IMG



project. You can track all transport requests from the system where they are created to the systems into which they are imported. Within the project context, all transport requests that belong to a particular project can be tracked across all the systems in the project landscape. You can navigate into the transport logs, and into the import queue, as well as into the corresponding service transaction or task list. You can also navigate into the Solution Manager project, the satellite IMG project, or the CTS project.

Prerequisites • You have created a Solution Manager project.

• The data collector has been configured in Change Request Management (see Scheduling the Data Collector [page 349]).

Features • Project analysis

Here you can track all changes for one project that was defined in the Solution Manager for Implementation (see Tracking Changes for One Project [page 371]).

• System analysis

Here you can compare change requests within systems, differences in the number of change requests, and differences in the sequence in which requests are exported and imported (see Displaying Information About Transport Requests in One System [page 373]).

• Request analysis

Here you can track change requests, starting with the system where the request was created, to all systems into which the transport is imported (see Tracking Transport Requests Across a Transport Route [page 375])

• Scheduling analysis

Here you can analyze one transport track in a maintenance instance for all instances, or analyze one maintenance instance (including all transport requests) (see Analyzing Maintenance Cycles and Urgent Corrections [page 363]).

Tracking Changes for One Project

Use You want to track all changes for one Solution Manager project or for one IMG project.

Procedure


2. Choose Tracking.

3. Select the Search tab page.

4. In the Project Analysis group box, use the F4 Help to select a Solution Manager project or an IMG project.

5. Choose Search.

The system displays the project on a new screen. On this screen you can see an overview of all systems that are dedicated to system roles (development, consolidation, testing, production, and so on) of the project that you selected. The sequence in which the system roles are displayed on this screen depends on their sequence in the



transport track that you previously defined in the Transport Management System (TMS).

6. To display all systems that are assigned to a particular system role, click the corresponding column header (Development System, for example).

Result In the lower screen area, the system displays information about the selected system role in a table with the following columns:

Date

Date of the last data collection

Source System

Source system where transport requests are created (development system, for example)

Dest Sys

Target system into which transport requests are imported (production system, for example)

Exported

Number of transport requests exported from this system (applies to target system).

Imported

Number of transport requests imported into this system (applies to target system).

Open

Number of transport requests that were created but have not been released yet (applies to source system).

Waiting

Number of transport requests that are waiting to be imported into the system (applies to target system).

Imp. Errors

Number of transport requests that were imported with errors (applies to target system).

Seq. Violation

Indicates whether or not change requests were imported in the correct sequence into the target system (OK/green background or <number of sequence violations>/yellow background). The sequence within maintenance projects, however, always differs due to the import sequence of the individual urgent corrections.

Delta Errors

Indicates whether or not there are inconsistencies in the content of the source and target systems concerning the export and import of change requests (OK/green background or <number of delta project requests>/red background). Delta errors may, however, exist due to transports being copied, or due to cross-system transports into the development system.



RFC

A red, yellow, or green icon indicates the status of the RFC connection to the data collector (yellow means that there is no information available about the status of the last data collection).

To see more detailed information about the transport requests, you can double-click the entry in the Exported, Imported, Open, Waiting, and Imp. Errors columns. The system then displays the corresponding System Analysis screen from where you can view the change transaction and task list by double-clicking the relevant column.

Displaying Information About Transport Requests in One System

Procedure

1. On the Change Management - Change Tracking screen, select the Search tab page.

2. In the System Analysis group box, use the F4 Help to select the following:

a. System (mandatory)

b. Client (optional)

c. Project (Solution Manager or IMG) (optional)

d. Date (default setting is exactly one month previous to the current date but entry is optional); refers to data collected since this date.

e. Time (optional)

3. In the Status of Transport Request field, select which status of transport requests you want to view. The following statuses exist:

a. Blank

(Only select this option if you want to view only Support Packages and Note corrections.)

b. Exported

c. Imported

d. In Import Queue or Imported

e. Open

f. Open or Exported

4. If you want to see which Support Packages and Note corrections have been imported into the system, select incl. Support Packages & Note Corrections.

5. Choose Search.

Result The system displays a new screen where you can view information about the system that you selected, according to the criteria that you selected. On this screen you can trigger the data collector (choose Refresh Data). The system then updates the information displayed on this



screen. You can double-click an entry in the Object column (transport request) to navigate to the transport log of the system you selected (display mode only).

Comparing Transport Requests in Two Systems

Use You want to compare two systems with each other (a development system with a consolidation system, for example) to check which transport requests have been imported or exported.

Procedure

1. On the Change Management – Change Tracking screen, select the Search tab page.

2. In the System Analysis group box, use the F4 Help to select the two systems (and, optionally, clients) that you want to compare.

If you make entries in the Project, Date, and Time fields, these entries apply to both systems.

3. In the Change Request Status field, use the F4 Help to select the statuses that you want to compare.

The default selection is Exported for the first system and Imported for the system with which you want to compare the first system. However, other combinations are possible.

4. If you want to display which Support Packages and SAP Notes were imported into both systems, select incl. Support Packages & Note Corrections.

5. Choose Search.

Result The system displays all information about the two systems on a new screen according to the criteria that you selected. On this comparison screen, you can choose Refresh Data to view the data from the latest data collector run.

Functions on the comparison screen:

• Show All Records

This is the default setting when two systems are compared.

• Show Delta

You can use this function only if you selected Exported and Imported as the corresponding change request statuses on the previous screen. This function enables you to see which changes were exported from the first system but that were not imported into the second system. Also, you can view which changes were imported into the second system but that were not exported from the first system.

• Analyze Import Sequence

You can use this function if you want to see whether differences exist in the sequence in which changes were exported from the first system and imported into the second system. The system displays the number of sequence violations at the top of the right-hand screen area. If violations exist, you can display each one by choosing Next Sequence Violation (icon next to Refresh Data). The violations are displayed in red. You can then click Type in the relevant row to display the corresponding violation on the left-hand side of the screen.



If you want to display a particular transport request that was exported and check whether this request was imported into the second system, you can click Type in the relevant row of the export system. If the system cannot find this request, an error message is displayed at the bottom of the screen, and the system finds the next transport request that was exported from the first system and imported into the second system.

Tracking Transport Requests Across a Transport Route

Use You can use this function to display all actions that have been performed for particular transport requests.

Procedure

1. On the Change Management - Change Tracking screen, select the Search tab page.

2. In the Request Analysis group box, enter one or more transport requests.

3. Choose Search.

Result The system displays all actions (export or import, for example) that have been performed for the selected transport request(s), and indicates in which systems the actions were performed.

Change Transactions in Change Request Management The Change Request Management scenario consists of a workflow for implementing urgent corrections and regular corrections within a maintenance cycle. The workflow for a correction starts with the occurrence of an error or missing functions. This is reported to the Service Desk where the system creates a change request. If the error is serious enough to warrant the implementation of a correction, the change request is then approved. Subsequently, depending on the subject in the change request, a change transaction is then created of the type Urgent Correction, Regular Correction, or a type that you defined in Customizing for SAP Solution Manager. The change transaction then passes through certain phases:

• Developing a correction

• Testing the correction

• Importing the correction into the production system

All users involved in the correction process navigate from the change transaction into the relevant target systems in the maintenance landscape. In these systems, the users execute various tasks, provided that they have the required authorizations [page 344]. If the corresponding Business Partners have been configured, the change transaction is passed on to the next processor (a tester, for example). Each time that the change transaction receives a new status (Tested Successfully, for example), certain change management actions such as releasing a transport request have to be performed. These actions are performed either



automatically when the change document is saved, or are performed explicitly by a particular user.

Actions can only be performed under certain conditions. Which actions are performed depends on the status of the change transaction and on the status of the corresponding maintenance cycle. The statuses of a maintenance cycle represent phases of a maintenance process. For each task list of the type maintenance cycle in the Schedule Manager, there is exactly one change transaction of the type maintenance cycle. The task list and the change transaction are both representative of a maintenance cycle instance, which controls the change process of a maintenance landscape in accordance with a phase model that is relevant for all parties involved. Additional business objects are assigned to this maintenance cycle (Solution Manager maintenance project and, optionally, a cProjects project, for example).

The phases of a maintenance cycle are as follows:

• Created

• In Development wo Release

• In Development w Release

• Test

• Emergency Correction

• Go-Live

• To be closed

• Completed

Only in the going live phase is it possible to import the contents of the import buffer into the production system. In this phase, all transport requests in the buffer that have been released as part of a maintenance cycle are imported in the same sequence as they were exported. Subsequently, the cycle can be closed, or reset to a previous phase (In Development w Release, for example).

A prerequisite for using phase control is that corrections are assigned to a maintenance cycle.

Workflow for Maintenance Cycles

Purpose You use this process to create a maintenance cycle for your regular and urgent corrections.

Process Flow

1. A user creates a maintenance cycle. When the cycle is created, its status is Created. Urgent corrections and regular corrections can only be created as change transactions. Their status also has to remain as Created until the corresponding task list has been activated by the administrator.

2. The change manager sets the status of the maintenance cycle to Development wo Release. When this status is set, corrections can be developed, and transport requests and transport tasks can be created. Exports, however, are not permitted (except in the case of urgent corrections). Urgent corrections are permitted in every phase except for the Go Live phase.

3. If the change manager switches the status of the maintenance cycle from Development wo Release to Development w Release, transport requests can be released from within



a regular correction. The administrator uses the task list to import all released corrections into test systems.

4. If any regular corrections exist whose status has not yet been set to Tested Successfully when the maintenance cycle phase is changed from Development w Release to Test, the system issues a warning. These corrections are then excluded from the integration test and cannot be released.

5. If changes still have to be made after the test phase has been completed, transport requests and tasks can be created and released as part of the Emergency Correction phase, but only by using the task list of the Schedule Manager.

6. The Go Live phase is reserved for importing the entire project buffer into the production system. Neither transport requests nor urgent corrections can be released during this phase.

7. If there are still any open transport requests, you have to return to the Development w Release phase and repeat the process including the test phase to ensure that any open requests can be released and transported.

8. If there are no open transport requests, you can close the maintenance cycle by setting the status to To be closed. You can subsequently create a new maintenance cycle.

Regular corrections can still be created in the test phase of a maintenance cycle, but the corresponding transport requests cannot be exported.

Workflow for Regular Corrections

Purpose You use this process to make regular corrections in your maintenance landscape.

Process Flow

1. A user detects missing functions in a system.

2. The user (requester) creates a Support Message and documents the request in this message.

3. A change request is generated in the Service Desk.

4. The change request is forwarded to a change manager for approval or rejection.

5. Depending on the priority, the change manager approves or rejects the change request.

6. If the change request is approved and the subject is set accordingly, a change transaction of the type Regular Correction is generated.

7. The change transaction is forwarded to a developer who sets the status to In Development.

8. The developer creates a transport request. (By means of actions, the developer can log on to the development system directly.)

9. When the correction has been developed, the developer releases the transport request from within the change transaction.

10. If the purpose of the change request has been fulfilled and all the corresponding transport requests have been released, the developer sets the status to Correction Completed.



11. A tester or another developer sets the status of the change transaction to Tested Successfully to indicate that the new function has been tested and can be imported into the production system.

12. The new function is imported into a test system during one of the regular imports of the project buffer.

13. The new function is imported into the production system when the corresponding maintenance cycle is in the Going Live phase.

14. The status can only be set to Productive when the regular correction has been imported into the production system along with all the other regular corrections that belong to the maintenance cycle. You can choose to set this status for all imported regular corrections at the end of a maintenance instance by scheduling the batch job CRM_SOCM_SERVICE_REPORT.

Regular corrections whose status is still In Development trigger a warning in the transaction of the corresponding maintenance cycle if the status is set during the test phase; regular corrections can be created during the test phase of a maintenance cycle, but the corresponding transport requests can no longer be exported.

Workflow for Urgent Corrections

Purpose You use this process to make an urgent correction in your production system.

Process Flow

1. A problem is detected by an end user in a system.

2. The user (requester) creates a Support Message and documents the problem in this message.

3. A change request is generated in the Service Desk as a result of the Support Message.

4. The change request is forwarded to a change manager for approval or rejection.

5. Depending on the severity of the problem, the change manager approves or rejects the change request.

6. If the change request is approved and the subject is set accordingly, a change transaction of the type Urgent Correction is generated.

7. The change transaction is forwarded to a developer so that the urgent correction can be developed. Simultaneously, a specific urgent correction task list containing the necessary tasks to execute the urgent correction is generated in the background in the Schedule Manager.

8. The developer makes the urgent correction in a development system and forwards the change transaction to a tester.

9. The tester logs on to a test system to check whether the urgent correction works.

10. If the correction contains no errors, the tester forwards the change transaction to the production manager. (If errors occurred during testing, the tester returns the change transaction to the developer so that the urgent correction can be changed. This correction then has to be tested again.)

11. The production manager approves the urgent correction for import into the production system and forwards the change transaction to an IT operator.



12. The operator imports the urgent correction into the production system and sets the status of the urgent correction to Productive.

13. The requester confirms that the correction has been made by setting the status of the change request to Confirmed.

If you want to set multiple change transactions to the next status (from “Approved for Import” to “Productive”, for example), execute the batch job CRM_SOCM_SERVICE_REPORT.

If no Support Message has been created, but an urgent correction needs to be made, you can also manually create a change request [page 380].

Making User Settings for Change Request Management

Use Before you start to use the Service Desk for the Change Request Management scenario, you may want to make some personal settings.

Procedure

1. Call transaction CRMD_ORDER.

2. Choose with the quick info text Settings.

3. Select the Specific tab page.

4. Make the following entries:

� In the Pushbutton 1 field, enter SDCR.

� In the Pushbutton 2 field, enter SDHF (optional)

� In the Pushbutton 3 field, enter SLFN.

5. Select the ObjctServices tab page.

6. Select everything except for Actions.


Result The initial screen of transaction CRMD_ORDER now contains the following personalized pushbuttons:

Change Request

Urgent Correction (optional)

Service Desk Message



You can now also see with the quick info text Actions.

These pushbuttons are required for the procedures described in the Change Request Management documentation.

Transaction Codes for Worklists in Change Request Management

All change requests and change documents are displayed as worklists. Depending on user authorizations, these worklists can be accessed by using the following transactions:

Transaction Code Menu Path on SAP Easy Access Screen

S_SMC_47000018 Requests for Change → Change Requests Created by Me

S_SMC_47000019 Requests for Change → My Non-Completed Change Requests

S_SMC_47000020 Requests for Change → Non-Completed Change Requests

S_SMC_47000021 Documents for Change → Change Documents Created by Me

S_SMC_47000022 Documents for Change → Change Documents to be Processed by Me

S_SMC_47000023 Documents for Change → Change Documents to be Processed

S_SMC_47000024 Documents for Change → Change Docs. To Be Proc. w/o Prcssr

You can open any change request or change document by double-clicking it in the relevant worklist. The system then opens the request or document in the Service Desk (transaction CRMD_ORDER).

Creating a Change Request

Use A problem has been detected in a system. No support message has been created, but you want to create a change request anyway.

Prerequisites Your user profile contains Requester authorizations.

Procedure



1. Call transaction CRMD_ORDER.

2. Choose Change Request.

If this pushbutton is not visible, see Making User Settings for Change Request Management [page 379].

3. Make an entry in the following fields:

a. Description

b. Sold-to Party

c. Requester

d. IBase component (which you defined in Customizing for SAP Solution Manager → Basic Settings → SAP Solution Manager System → Service Desk → iBase)

4. In the Subject field, select Urgent Correction.

5. In the lower right-hand screen area, select Change Description in the dropdown list box.

6. Enter a description of the change that you want to be implemented.

7. In the Change Manager field, enter the Business Partner (user) of the change manager who is responsible for approving or rejecting the change request.

8. Choose Save.

Result A change request has been created and assigned to a change manager for approval. The status of the change request is To Be Approved.

Approving a Change Request

Use As a result of a serious problem, an urgent correction needs to be implemented immediately in a production system. For this purpose, a change request has been created. This change request has to be approved by a change manager.

Prerequisites • A change request has been created that documents the problem.

• In Customizing for SAP Solution Manager (SV-SMG), you have defined the production system where the urgent correction has to be implemented (Customizing for SAP Solution Manager → Basic Settings → SAP Solution Manager System → Service Desk → iBase).

• Your user profile contains Change Manager authorizations.

Procedure

1. On the SAP Easy Access screen, choose Requests for Change → My Non-Completed Change Requests.

2. Select the change request that you want to approve by double-clicking the entry in the Number column.

The system opens the change request.



3. In the Subject field, select Urgent Correction.

4. Choose with the quick info text Actions.

5. In the dropdown list, choose Approve Change Request.

6. Choose Save.

Result The system sets the status of the change request to Approved. A change document of the type Urgent Correction has been created in the background. You can navigate to this document by choosing Document Flow.

Rejecting a Change Request

Use A change request has been created. In your position as change manager, you have decided that the problem is not serious enough to warrant an urgent correction. You now have to reject the change request in the Service Desk.

Prerequisites • A change request has been created and contains information about the problem.

• Your user profile contains Change Manager authorizations.

Procedure

1. In the worklist [page 380], select the change request by double-clicking it.

The system opens the change request.

2. Choose with the quick info text Actions.

3. In the dropdown list, choose Reject Change Request.

4. Choose Save.

Result The status of the change request is now Rejected. The process is now closed. If the change request was generated as a result of a Support Message, you can navigate back to the Support Message by choosing with the quick info text Document Flow.

Making a Regular Correction in a Development System

Use As a result of an approved change request, you want to make a regular correction in a development system.



Prerequisites • Your user profile contains Developer authorizations.

• In the Service Desk, you have selected the corresponding regular correction with the status Created (SAP Easy Access screen → Change Docs. to be Processed by Me) by double-clicking it.

• You are in change mode.

Procedure

1. Make sure that your user appears in the Current Processor field.

2. Choose Actions.

3. Choose Set To "In Development".

4. Choose Save.

5. If the maintenance cycle is not unique, specify your maintenance cycle in the dialog box.

The entry in the Status field changes to In Development.

6. Choose Actions.

7. Choose Create Transport Request.

8. Choose Save.

9. Choose Actions.

10. Choose Log On to System.

11. Make the required correction in the development system.

12. Release the task in the corresponding transport request.

13. Navigate back to the Service Desk by choosing Back.

14. Choose Actions.

15. Choose Release Transport Requests.

16. Choose Save.

17. In the lower right-hand screen area, select Test instructions in the dropdown list box.

18. Enter test instructions for the tester.

19. In the Current Processor field, enter the user name of the tester.

20. Choose Actions.

21. Choose Complete Correction.

22. Choose Save.

Result • The Developer partner function contains the business partner of the developer.

• The Current Processor partner function contains the business partner of the tester.

• The correction has been made in the development system, and the corresponding transport requests have been released.

Making an Urgent Correction in a Development



System

Use As a result of an approved change request, you want to make an urgent correction in a development system.

Prerequisites • Your user profile contains Developer authorizations.

• In the Service Desk, you have selected the corresponding urgent correction with the status Created (SAP Easy Access screen → Change Docs. to be Processed by Me) by double-clicking it.


Procedure


2. Choose Actions.

3. Choose Set To "In Development".

4. If the maintenance cycle is not unique, specify your maintenance cycle in the dialog box

5. Choose Save.

The entry in the Status field changes to In Development.

6. Choose Actions.

7. Choose Log On to System.

8. If you cannot find a modifiable transport request, choose Actions → Create Additional Transport Request.

9. Make the required correction in the development system.

10. Release the task in the corresponding transport request.

11. Choose Back.

12. In the lower right-hand screen area, select Test instructions in the dropdown list box.

13. Enter test instructions for the tester.

14. In the Current Processor field, enter the user name of the tester.

15. Choose Actions.

16. Choose Correction passed to test.

17. Choose Save.

Result • The system creates a task list in the Scheduling tool of Change Request Management.

• A transport request is created in the development system for the current processor.

• The system releases the transport request that contains the changes and the transport request is imported into the test system.

• The task list is now included in the document flow.

• The Developer partner function contains the business partner of the developer.

• The Current Processor partner function contains the business partner of the tester.



• The status of the urgent correction is To Be Tested.

Testing an Urgent Correction

Use An urgent correction has been made in a development system. You now need to check this urgent correction in a test system.

Prerequisites • Your user profile contains Tester authorizations.

• In the Service Desk, you have selected the corresponding urgent correction with the status To Be Tested (SAP Easy Access screen → Change Docs. to be Processed by Me) by double-clicking it.


Procedure

1. Make sure that your user name (Business Partner) appears in the Current Processor field.

2. Choose Actions.

3. Choose Log On To System.

4. Test the correction in the test system.

5. Choose Back.

• If the test was successful, proceed as follows:

a. In the lower right-hand screen area, select Test report in the dropdown list box.

b. Enter a test report.

c. If you know the user name of the production manager, enter it in the Current Processor field.

d. Choose Actions.

e. Choose Confirm Test Success.

f. Choose Save.

• If the test failed, proceed as follows:

a. In the lower right-hand screen area, select Test report in the dropdown list box.

b. Enter the errors in the test report.

c. In the Current Processor field, enter the user name of the developer who developed the correction.

d. Choose Actions.

e. Choose Reset to "In Development".

f. Choose Save.



Result • If the test was successful, the status of the urgent correction is Tested Successfully.

The production manager now has to approve the import into the production system.

• If the test failed, the status of the urgent correction is In Development. The developer who developed the correction has to make some changes and then the correction can be retested.

Importing an Urgent Correction into a Production System

Use An urgent correction has been tested in a test system. The test was successful and the urgent correction has been approved for import by the production manager. In your position as IT operator, you now want to import the correction into a production system.

Prerequisites • Your user profile contains IT Operator authorizations.

• In the Service Desk, you have selected the corresponding urgent correction with the status Approved for Import (SAP Easy Access screen → Documents for Change → Change Docs. to be Processed by Me) by double-clicking it.


Procedure


2. Choose Actions.

3. Choose Import Correction Into Production System.

4. Choose Save.

5. Make sure that no errors are displayed (see Urgent Corrections: Troubleshooting [page 387]).

6. Choose Actions.

7. Choose Go To Task List.

Check the processing status of the task list.

8. Navigate back to the Service Desk by choosing Back.

9. Choose Actions.

10. Choose Log On To System.

11. In the production system, check whether the import was successful by checking the transport logs.

12. Choose Back.

13. If the import caused errors or did not solve the original problem, reset the status of the urgent correction to In Development by choosing Actions → Reset to “In Development”.



Result • If the import caused errors, the status of the urgent correction is now In Development.

Corrections have to be made and then the urgent correction can be tested again.

• If the import was successful, the status of the urgent correction is now Productive. The status of the change request is Realized. The requester now has to confirm the urgent correction.

Completing an Urgent Correction

Use An urgent correction has been imported into a production system, the status has been set to Confirmed, and now you want to complete the process.

After you have completed an urgent correction, you can no longer make any changes to it.

Prerequisites • Your user profile contains Administrator or Operator authorizations.

• You have selected the corresponding urgent correction in the Service Desk with the status Confirmed (SAP Easy Access screen → Documents for Change → Change Docs. to be Processed by Me) by double-clicking it.

• The task list of the type Urgent Correction has been completed [page 358] in Change Request Management.


Procedure

1. Choose Actions.

2. Choose Complete Correction.

3. Choose Save.

Result The status of the urgent correction is now Completed. The urgent correction can no longer be processed.

Urgent Corrections: Troubleshooting



If a change transaction has a red or yellow icon on the Service Desk interface, the transaction contains errors and cannot be processed until you remove the cause of the errors.

If you click the red or yellow icon with the quick info text Display/Close Messages, the system displays the corresponding error messages.

There are four error types:

• A status is incorrect (inconsistent), which means that the subsequent action cannot be performed.

• The system rejects a status change.

• An action cannot be performed in the current phase of the maintenance cycle

• An unexpected technical exception was triggered.

The first three types of error can be resolved by system users; the fourth type has to be analyzed by a system administrator.

Type 1: There is at least one error message (red icon). The subsequent action cannot be selected. You may have to perform a specific action in the maintenance landscape (release a task, for example). If this action can be performed directly, you see an entry in the Action exists column (next to the message text). You can perform the action by double-clicking the message. After you have performed the action, save the change transaction. The system checks the status again and the change transaction no longer contains any errors. If there is no entry in the Action exists column, choose Actions → Recheck Correction in the toolbar.

Type 2: Only warning messages exist. One message indicates that the current status was set by the system due to a possible error. The other warnings explain the error itself. Since no actual error exists as far as the status set by the system is concerned, the subsequent action can be performed.

Type 3: There is at least one error message (red icon) indicating that an action cannot be processed in the current phase of the maintenance cycle. The subsequent action cannot be selected. No action can be performed by double-clicking the message. Choose Actions → Recheck Correction in the toolbar. The system checks the current status of the change transaction and deletes the error message if the system determines that the current status is consistent. Subsequently, the change transaction can be processed as soon as the phase of the maintenance cycle has changed accordingly.

In many cases, the long text of the message provides additional information about the cause of the problem and how to solve it. The application log in the task list provides additional information if the error was caused by a task not being executed completely or correctly.

Sometimes the system displays an error because certain asynchronous processes have not been completed yet. If you want to check whether an action was completed successfully, check the task list. You can do this by choosing Actions → Go To Task List. If all processes have been completed in the task list, navigate back to the change transaction and save it again. The system checks the status again and the change transaction no longer contains any errors.

The function Actions → Recheck Correction is always available; even if an error has been corrected, the error message does not always disappear (especially if you used the task list to correct the error).

SAP Solution Manager - Freenagattaque.free.fr/CLEMENCE/Doc aide SAP/Solution_Manager_32_SP… ·...

Documents

Transcript of SAP Solution Manager - Freenagattaque.free.fr/CLEMENCE/Doc aide SAP/Solution_Manager_32_SP… ·...