Manual Data Source Maintenance

Use

You cannot edit all data manually in hosts, 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.

4. Confirm the confirmation prompt.

Automatic Data Capture

Editing automatically captured data

You cannot edit all data manually in hosts, 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 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.

Set-Up Automatic System Landscape Data Capture

Use

You set-up the automatic data transfer from the Landscape Infrastructure Server (LIS) and the System Landscape Directory (SLD), to get system data for the Solution Manager System Landscape.

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

Prerequisites

You have assigned the Solution Manager to a transport domain or defined the Solution Manager system as the new domain controller, in the Transport Management System (STMS), to be able to use the Landscape Infrastructure Server (LIS).

Procedure

...

...

Choose the transaction Setup System Landscape (SMSY_SETUP).

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 Infrastructure Server (LIS) only gets data about system names, clients and software components in the systems, for systems in the transport domain. SLD gets host and database data independently of the transport domain.

To access the System Landscape Directory (SLD):

a. Choose Edit ® Expert Settings.

b. Specify the host 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.

Choose Schedule Automatic Data Transfer.

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

For further information, see Automatic Data Capture.

Save your entries.

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 haveset-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 hosts in the Solution Manager System Landscape are visible.

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

· Display the scenarios of a project

· Display the component views of scenarios and processes

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.

· 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).

Edit Products, Product Assignment and Product Version in Solution Manager System Landscape

Prerequisites

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

Procedure

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

¡ To hide the general product definitionsn in the landscape components entirely, reset the Display General Product Definitions in Tree flag.

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

Change assignment of a system to a product and 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. If you want to assign only certain products to a system, flag these products as leading. (5).

...

1. Choose Landscape Components ® 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.

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 servers have already been maintained for another product, you can copy the servers for the new system:

a. Select the product to the left of the landscape components, and go to the Server tab.

b. Choose Copy Server.

c. Choose a server.

d. Save your selection.

Solution Manager System Landscape

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, Services, Support Desk).

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)

· Maintainc 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

Define 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 are in the Project Administration transaction in change mode.

You have setup automatic data capture for the system landscape. This enables you to use the possible entries help when you select your logical systems.

You are in the Project Administration and have selected the System Landscape tab.

Procedure

Systemstab

Define logical components

A logical component in an implementation project refers to a product in an SAP environment, without specifying systems or versions of the product. A logical component can also be a non-ABAP product.

· Choose the Scenario Selection pushbutton to copy the logical components, on which the scenarios which you selected in the Template Selection tab are based, into the Systems tab.

· To copy more logical components, choose them, and their products/main instances, in the possible entries help for the Logical Components column.

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

· To create a new logical component, choose the possible entries help ® Create New Entry.

You can create a non-SAP product in the next dialog box. The Define Non-SAP Products section in Setup Editing Products contains further information about creating a non-SAP product.

· You can assign another product version to the product/main instance in the possible entries help.

· Choose Replace Log. Component to replace a logical component by another throughout the project structure.

· To go to the component systems in the project phases, assign logical systems to the logical components for the system roles, from the possible entries help for the Evaluation System, etc. columns.

The systems which you specify 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

You can change the system roles and their assignment to the project phases, with Role Assignment in the Project Administration. You can also change the test system selected, at any time, in the Test Organization

Edit system roles

You can change the sequence of the system roles, select additional system roles, define up to ten user system roles and delete system roles from your project, with Role Assignment in the Systems tab.

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

Solution Landscape tab

You can assign a production solution landscape to your project on the Solution Landscape tab. 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. The system shows the project in the Solution Manager Operations in the solution whose production solution landscape you assign here. You can copy processes from your project into your solution landscape, in the Solution Manager Operations.

IMG Projects tab

If you have defined logical components in the System Landscape tab, the system displays their IMG projects in this tab, i.e. all subprojects in the component systems which belong to your Solution Manager project.

Generate the IMG projects in the component systems, and 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

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

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

· Red (square): Project does not yet exist

· Green (dot): Project exists in the specified logical components and the assigned logical systems.

Generate IMG projects in the component systems

To generate and distribute a project:

...

...

1. Choose the system role for IMG Projects.

2. Select the IMG project.

The generation and distribution is started in the component systems.

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.

You go to the header data of the project.

You can also go to the project header data by selecting Display Project in the context menu (right mouse click on the IMG project).

Assign another IMG project in the component systems

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

...

1. Position the cursor on the IMG project.

2. Choose Assign Other Project in the context menu.

3. Enter the name of the project to be assigned.

4. Log on to the component system.

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.

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.

Displaying and Managing Existing CPI-C Connections

By choosing Goto ® Active connections ® Details, you can display details on the active CPI-C connections on which the cursor is positioned in the initial screen. This is important for specialists, particularly for troubleshooting purposes.

Use the menu path Goto ® Active Connections to:

· Interrupt or delete the connection (see Deleting a CPI-C Connection)

· Reset the error counter for this connection or all error counters (see Resetting Error Counters)

· Activate or deactivate the trace function for the selected connection(s). Unlike the procedure described in Activating Traces, trace level 2 for the selected connections.

Deleting a CPI-C Connection

There are two ways of clearing down a connection.

By choosing Goto ® Active connections ® Interrupt connection, you can clear down the connection; a corresponding return value, however, remains in the connection table so that the CPI-C programs affected can be informed.

When you choose Goto --> Active connections --> Delete connection, the connection is cleared down and the corresponding entry is deleted from the connection table.

To use this function the system authorization profile S_ADMI_FCD is needed (Tools ® Administration, Maintain users ® Profiles).

Display Gateway Work Processes

This function is only relevant for monitoring an SNA gateway (Goto ® Gateway ® SNA Gateway).

You can display a list of work processes via Goto ® Work processes. The following values are displayed for each gateway work process started:

· Number in the process table

· Number of CPI-C connections assigned to this process

· Number of times this process has been started so far

· Status of the process:

READY: Process awaits request

BUSY: Process working on a request

· Number of the CPI-C connection currently served

(Number in connection table)

· Number of the request block which holds the CPI-C function you have just executed

Starting and Stopping the SAP System (Microsoft Windows)

Use

You are starting the SAP system with the Microsoft Management Console (MMC). With a newly installed MMC, you only start installed SAP instances locally on the host that you are logged on to. If the MMC is configured for central system administration, you can start the entire SAP system from a single host.

Starting the SAP System

1. Start the MMC on the central system host by choosing Start ® Programs ® SAP System Management Console.

2. In the tree of nodes, choose the central instance. If you have configured the MMC for central administration, choose the node of the SAP system.

3. Click the right mouse button to display the context menu.

4. Choose Start. The following is started, depending on whether you have selected an individual instance or the SAP system:

¡ The central SAP instance and database

¡ The SAP system, all dialog instances, and the database

5. If the MMC is not configured in such as way that it permits central system administration, repeat the above steps on the hosts of all dialog instances.

Stopping the SAP System

...

1. Start the MMC on the central system host by choosing Start ® Programs ® SAP System Management Console.

2. In the tree of nodes, choose the central instance. If you have configured the MMC for central administration, choose the node of the SAP system.

3. Click the right mouse button to display the context menu.

4. Choose Stop. The following is stopped, depending on whether you have selected an individual instance or the SAP system:

¡ SAP central instance

¡ SAP system and all dialog instances

The database is not stopped. You must stop it separately.

5. If the MMC is not configured in such as way that it permits central system administration, repeat the above steps on the hosts of all dialog instances.

Starting and Stopping the SAP System (Unix)

Use

You can use the following commands under UNIX to start and to stop the SAP central instance and the database system.

Starting the SAP System

1. Log on in UNIX as a user with SAP administrator authorization (adm).

1. Enter the command startsap [DB|R3|ALL] from your home directory. The following applies to this command:

¡ DB starts the database system

¡ R3 starts the instances and associated processes of the SAP System (using the sapstartprogram)

¡ ALL starts both the database system and the SAP System. ALL is the default value and can be left out.

2. After you have started the database and the central instance, you can perform other actions within the CCMS.

To check whether all application servers of an SAP System were started correctly, start the Alert Monitor (transaction RZ20) or the Overview of SAP Application Servers (transaction SM51)

Stopping the SAP System

1. Log on in UNIX as a user with SAP administrator authorization ( adm).

2. Enter the command stopsap [DB|R3|ALL] from your home directory. The following applies to this command:

¡ DB stops the database system

¡ R3 stops the instances and associated processes of the SAP System

¡ ALL stops both the database system and the SAP System. ALL is the default value and can be left out.

Starting and Stopping Instances

Use

To start and stop instances of an SAP System, you can use the Control Panel.

Procedure

To start or stop instances in the Control Panel, follow the procedure below:

1. To start the Control Panel, choose CCMS ® Control/Monitoring ® Control Panel, or call transaction RZ03.

2. Select the instances that you want to start or stop.

3. Choose Control ® Start SAP instance or Stop SAP instance. The selected instances are then started or stopped in the current operation mode.

4. Ensure that all instances are started or stopped correctly. You can identify the status of the instances from their color in the system monitor:

○ green successful start

○ red start error

○ gray an instance has been stopped (or is inactive)

5. Check whether the start and stop commands were correctly executed. To do this, choose Refresh from the Control Panel. Active instances are identified by a cross in the Active column.

To restart stopped instances of an operation mode in the Control Panel, follow the procedure below:

1. Choose Select ® All stopped.

2. To start the instances, choose Control ® Start SAP Instance.

To stop instances of an operation mode in the Control Panel, follow the procedure below:

1. Choose Select ® All configured.

2. To stop the instances, choose Control ® Stop SAP Instances.