SAP Solution Manager

Purpose
The SAP Solution Manager is a platform which provides integrated support of the life-cycle of a
business solution, from the Business Blueprint via configuration to production operation. The SAP
Solution Manager provides central access to tools, methods and preconfigured contents, which
you can use during the evaluation and implementation, as well as in operation processing of your
systems.

Features
Implementing the my SAP Business Suite
 all phases of the implementation project (Business Blueprint, Configuration) are performed
centrally, in the Solution Manager system
 Central project documentation repository in the Solution Manager
 Integrated Project Administration, with which you can manage planning schedules, human
resources and other project data
Customizing Synchronization
 The Customizing Scout, which compares the customizing in different SAP components,
e.g. an ERP system with an SAP CRM system
 Customizing Distribution, which synchronizes the customizing in different SAP components
Test
 Test Workbench, with which you can organize and perform tests at the end of a project
phase
 Reuse of the project structure for a process test
Global rollout
Integrated authoring environment, with which customers and partners can create their own
templates, which you can, for example, reuse in a global rollout to subsidiaries
E-Learning management
Create training materials and Learning Maps (computer-supported self-tuition courses), to train
end users after the implementation of new functions
Solution Monitoring
 Central system administration
 Evaluation and analysis of your system landscape, with Service Level Reporting
 System monitoring in real-time
 Business process monitoring
Services
Access to programs and services, which monitor and optimize the performance and availability of
your system landscapes, and minimize the operational risks of your systems
Service Desk
Solutions support with workflow to create and handle problem messages
Change Request Management
Management of change requests, with workflow for tracing and auditing changes and transports
in your system landscape.
Using the SAP Solution Manager in 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 for more information on creating preconfigured content and
templates.

Process Flow
...

1. The Roadmaps contain information and procedures for all phases of your
implementation project.
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. You enter administrative
data in the Project Administration transaction, for example, details of project dates and
resources.
3. You set the project scope during the project preparation phase.
4. In the project preparation phase, you define the system landscape you require for the
implementation of your e-business solution.
5. You define a Business Blueprint by documenting the organizational units, master data,
business scenarios and business processes you require for the implementation of your e-
business 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.
6. You configure your business scenarios in the development systems.
7. You check the test cases delivered with your solution and assign further test cases to
individual processes and process steps.
8. You check the consistency of the customizing of your business processes, i.e. you
check whether the customizing is the same in the various application components. You
synchronize customizing with theCustomizing Distribution.
9. You organize tests. You can reuse the test cases selected during configuration.
10. You create training material and learning maps (computer-supported self-learning
courses) to train the end users.

You can analyze a project at any time, to determine its status and the progress
made in testing or configuration.
Solution Manager System Landscape
Use

You create and manage the system landscape centrally in the Solution Manager, to use it
in your implementation and template projects, in the Customizing Synchronization
(Customizing Scout, Customizing Distribution) and in operational processing (Solution
Monitoring).

Integration

The 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)
 Maintain the solution landscapes for the operational processing of your solutions

Features
 Create landscape components (hosts, databases, systems)
 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

Create Business Blueprint

Purpose

You create a Business Blueprint during the implementation of your mySAP.com solution,
to document the business processes in your company, and decide which processes to
implement in your SAP system.

You use the Business Blueprint in the Solution Manager during the realization
(configuration and testing) phase. You reuse the project structure you created in the
Business Blueprint phase, to configure and to create test plans. You can also display,
change and enhance project documentation created during the Business Blueprint phase,
during configuration.
Prerequisites

You want to implement a my SAP solution. You have completed the Project Preparation.
You have defined an implementation project and a system landscape in the Project
Administration of the SAP Solution Manager.

Process Flow
...

1. Create a Blueprint structure, using predefined substructures.

2. Check the Business Blueprint structure, and its business scenarios, business
processes and process steps.
3. Decide which business scenarios, business processes and process steps to include in
the Business Blueprint. You can enhance the processes and process steps, or adjust the
names of individual processes to your company requirements.
4. Create the project documentation and save it in the Business Blueprint.
5. Assign transactions to process steps. This specifies which transactions in the system
correspond to the process steps in your company.
6. Print the Business Blueprint document.
7. When the Business Blueprint is complete, you set-up the development system
landscape.

Result

You have created a Business Blueprint and set-up a development system landscape. You
can reuse the Business Blueprint and the project structure to configure and test your
business processes.

Using Templates
Purpose

This process describes the use of a template. You can use templates:

 A customer:
  creates a template and uses it in one or more implementation projects as the
basis of the Business Blueprint.
  creates a template in a system and transports it into other systems as the basis
for the Business Blueprint of a project, e.g. in a global rollout.
 A partner:
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.
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 /…/.
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. 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.Assign these
objects to transportable packages with transport recording, when you create them.
Assign names in the namespace /.../, if it exists. Record these objects, per template
and logical system, in a user request, which you can later transport import into other
systems.
5. Create one or more templates in this template project, in the Templates tab in the
Project Administration.
6. Assign templates to the scenarios with the possible entries help in the Structure tab in
the Business Blueprint transaction, to put the scenario structures in your template. You can
assign several templates per scenario.
7. Set the visibility of the template to Public in the Templates tab in the Project
Administration, to make it visible system-wide.
8. 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.
9. 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 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 section Performing an Implementation
Project with the Template in the Target System.

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:
1. 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.
2. b. Create a piece list per component used.
3. c. Copy the result of the project analysis into the piece lists.
4. d. Put these piece lists in a transport request and release it.
5. e. Send this transport request into 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.

Configuration
Use

This project step configures the process requirements specified in the Business Blueprint
phase, in the system.

You assign objects, which help you and the project team to perform the configuration,
e.g. BC Sets, IMG objects and test cases, to the process structure. The configuration is
performed in the component systems, based on the process structure created in the
Solution Manager, and the objects assigned to it.

Prerequisites

You have created a process structure in the Business Blueprint phase.

Features

This project task comprises the following steps:

  Assign transactions/programs
You can call assigned transactions, add new ones or remove superfluous ones from the
project scope, in the Transactions tab.
 Assign/edit BC Sets
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, for
example, 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
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 Implementation Guide.
 Edit test cases
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 tab or in the IMG.
1.  Create/change problem messages

Project Analyses
Use

You can save information about a project per phase or project activity, e.g. status,
deadlines or team members. Project analysis analyzes this information. The more detailed
information you have recorded, the more project 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 project analyses comprise the following programs:

 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)

The project 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 project 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.
Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
  synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
  The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.
Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.

Customizing Synchronization
Use
Your system landscape contains several SAP components, e.g. an ERP system and SAP
CRM. The SAP CRM system is based on data which is already in the ERP system, 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 of the ERP system and SAP
CRM 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 which help you to synchronize customizing: Customizing
Distribution and the Customizing Scout. 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 CRM and SAP APO systems with the delta distribution, to ensure that
cross-component processes run smoothly
 synchronize customizing in different ERP 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. The Customizing Scout, a tool which compares the customizing between
different systems, complements Customizing Distribution.
Features
You can use the following tools:
 The Customizing Scout compares customizing in two systems.
 The Customizing Distribution 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.
 Trace and Log Files
Trace and log information are written in standard log format into the Solution Manager
Diagnostics’ log directory, location: <J2EE home>/cluster/server<n>/log:
 applications.<n>.log:
Consists of error and startup information of Solution Manager Diagnostics applications.
 defaultTrace.<n>.trc:
Contains detailed information of Solution Manager Diagnostics applications.

Architecture
The graphic below shows how Business Content is accessed via the various participating
components:

In the case of ‘Authoring’ (SAP and customer-side content assignment and customer-side
configuration) SAP Solution Manager must connect to the NW 2004s AS ABAP on
which Business Content Environment is situated. SAP Solution Manager can then call up
the relevant interface. This authoring and configuration environment on the ABAP server
can also forward queries to the reference systems and access the required content objects.
For authoring and configuration purposes, it is therefore possible to use a single interface
to carry out searches in various repositories that have differing structures. In the Java-
based portal, access is made via HTTP, while BI access is via RFC.

Since Solution Manager and Business Content Environment do not run on the same
system in Releases lower than Solution Manager 4.0, you need to access two
different systems if you are using SAP Solution Manager 3.20. These are the
 business content system (ABAP server) and the relevant content provider system.
You can avoid having to do this by setting up a trusted connection between the SAP
Solution Manager system and the Business Content server. The users of this trusted
system connection need to be assigned to authorization object S_RFACL.

Using the SAP Solution Manager in 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 for more information on creating preconfigured content and
templates.

Process Flow
...

1. The Roadmaps contain information and procedures for all phases of your
implementation project.
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. You enter administrative
data in the Project Administration transaction, for example, details of project dates and
resources.
3. You set the project scope during the project preparation phase.
4. In the project preparation phase, you define the system landscape you require for the
implementation of your e-business solution.
5. You define a Business Blueprint by documenting the organizational units, master data,
business scenarios and business processes you require for the implementation of your e-
business 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.
6. You configure your business scenarios in the development systems.
7. You check the test cases delivered with your solution and assign further test cases to
individual processes and process steps.
8. You check the consistency of the customizing of your business processes, i.e. you
check whether the customizing is the same in the various application components. You
synchronize customizing with theCustomizing Distribution.
9. You organize tests. You can reuse the test cases selected during configuration.
10. You create training material and learning maps (computer-supported self-learning
courses) to train the end users.
You can analyze a project at any time, to determine its status and the progress
made in testing or configuration.