SAP Solution Manager: Special Cases in Installation and

PUBLIC

For SAP Solution Manager 7.1 SP05 and higher2015-01-19

SAP Solution Manager: Special Cases in Installation and Upgrade

Content

1 More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Standard Product System Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Modeling of Exceptional Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.1 Add Installation of SAP Business Suite Usage Types in Existing NW System. . . . . . . . . . . . . . . . . . . . . . 84.2 Add Installation of SAP CRM or SRM Portal Content on Top of Existing NW Portal. . . . . . . . . . . . . . . . . . 94.3 Add Installation of SAP ERP Portal Content on Top of Existing NW Portal. . . . . . . . . . . . . . . . . . . . . . . 124.4 Modeling of SAP SEM-BW, SAP ERECRUIT, LSOFE, and FINBASIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Handling Add-Ons as Part of the SAP ERP Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Handling SEM-BW as Part of the NW Add-On SAP SEM Product. . . . . . . . . . . . . . . . . . . . . . . . . . . 16Correction of Installed Software Information (CISI) for SEM-BW. . . . . . . . . . . . . . . . . . . . . . . . . . . 17CISI for SAP SEM as Part of ERP: Change from NW703 to NW731. . . . . . . . . . . . . . . . . . . . . . . . . . 17CISI for SAP SEM as Part of ERP: Change to NW Add-On Product Version. . . . . . . . . . . . . . . . . . . . 20

4.5 Updating to SAP NetWeaver 7.3 Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.6 Products Not Relevant for Maintenance Optimizer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.7 Products that Are Only Partially Relevant for Maintenance Optimizer. . . . . . . . . . . . . . . . . . . . . . . . . . 24

2P U B L I C© 2015 SAP SE or an SAP affiliate company. All rights reserved.

SAP Solution Manager: Special Cases in Installation and UpgradeContent

1 More Information

● Always check for the latest version of this document at Maintenance Optimizer Special Cases in Installation and Upgrade .

● Documentation for System Landscape Management - LMDB● For installation of support package stacks, enhancement packages, and additional Java instances (technical

units): Upgrade Information , Upgrade Tools and Application-Specific Information.

SAP Solution Manager: Special Cases in Installation and UpgradeMore Information

P U B L I C© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/disclaimer?site=http://support.sap.com/mopz

http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-29495

http://help.sap.com/disclaimer?site=https://support.sap.com/release-upgrade-maintenance/upgrade-info.html

2 Introduction

This guide comprises recommendations on how to manage particular SAP products to which certain exceptions apply. The focus is on new installation, product system modeling in the Landscape Management Database (LMDB) of SAP Solution Manager, and on updates or upgrades with Maintenance Optimizer and Software Update Manager (SUM).

Why do you need product systems? Because they define the scope of your maintenance projects for all involved technical systems.

Things would be simple if you could install any product version (SAP ERP or SAP CRM, for example) on a single technical system. But this is not possible because …

● …it would be inflexible installed software could not be reused. For example, you could not use one Enterprise Portal System for several business systems. Product system definitions describe dependencies and reuse between technical systems. This is required to be able to update the technical systems consistently and keep the solution running.

● …it would require the installation of dual-stack systems, because even in product versions like SAP ERP 6.0, core parts based on AS ABAP are combined with AS Java-based parts, such as – most prominently – the Enterprise Portal used for Employee Self-Services in an HR scenario.

To enable reuse, often only certain parts of one product version are installed, and the installation is distributed over several technical systems.

For more information, see the White Paper: SAP Solution Landscape .

Most technical systems can automatically supply information about their installed software to an SLD, with an SLD data supplier (e.g. transaction RZ70 for AS ABAP). From an SLD, this technical system data is synchronized with the LMDB. Based on this mere technical system information, you create logical landscape data in the LMDB, by defining product systems and technical scenarios, which semantically describe interdependencies between technical systems.

A product system describes how a product version’s product instances are installed on different technical systems, or on technical systems that constitute a dual-stack. All parts of a product system are maintained as one unit. So you must define the product system consistently with the product version information from the SAP Support Portal. The verification function in the LMDB editor for product systems helps you do so.

Product system descriptions define the software to be deployed in an update or upgrade of the product system. They enable Maintenance Optimizer to create a correct stack XML for that software download.


SAP Solution Manager: Special Cases in Installation and UpgradeIntroduction

http://help.sap.com/disclaimer?site=https://scn.sap.com/docs/DOC-31897

3 Standard Product System Models

One technical system can be assigned to one product system, several technical systems can be assigned to one product system, or one technical system can have product instances that are assigned to several product systems.

In the simplest case, one technical system with all its product instances is used in the product system. The following example shows two simple product systems for different technologies, with one technical system each:

SAP Solution Manager: Special Cases in Installation and UpgradeStandard Product System Models


In a slightly more complex scenario, two technical systems with different technologies comprise one product system. For example, an SAP ERP 6.0 system that uses an SAP NetWeaver portal. The portal is a ‘sidecar’ technical system and is updated together with the ERP system:

If the steps of the business processes are tightly integrated, there are dependencies between connected technical systems that must be considered in an upgrade. An example is an HR application of SAP ERP that runs on an AS ABAP-based backend system, and a separate SAP NetWeaver portal system that provides Employee Self-Services. The Portal system can also be reused, by an SAP CRM system for example. This reuse makes the technical system with the portal a ‘hub system’; in updates, it is updated to the minimum version required by the applications involved.



The graphic shows three product systems (HRP, CRP, and HRP), reusing a central hub technical system (EPP) with the Java Portal content. The hub is also modeled as a product system, to enable an independent update of the portal that is installed on it:

For more information, see the Maintenance Planning Guide .



http://help.sap.com/disclaimer?site=https://scn.sap.com/docs/DOC-35437

4 Modeling of Exceptional Products

The following sections describe examples of SAP products to which special installation and upgrade conditions apply.

4.1 Add Installation of SAP Business Suite Usage Types in Existing NW System

Context

To install additional SAP Business Suite usage types on top of an existing SAP NetWeaver Java system, proceed as follows:

Procedure

1. Assign the planned product instances to the product system, in SAP Solution Manager.2. Run a maintenance transaction in Maintenance Optimizer to calculate a stack XML file to install the planned

usage type.3. Install the new usage type with Software Update Manager (SUM).

4. Activate the new usage type. For more information, see SAP Note 1793486 .5. After the installation, the newly installed software information is automatically forwarded to the SLD and

LMDB, and the previously assigned product instances are now marked as installed.

Next Steps

See also the following examples with screenshots:

● Add Installation of SAP CRM or SRM Portal Content on Top of Existing NW Portal [page 9]● Add Installation of SAP ERP Portal Content on Top of Existing NW Portal [page 12]


SAP Solution Manager: Special Cases in Installation and UpgradeModeling of Exceptional Products

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1793486

4.2 Add Installation of SAP CRM or SRM Portal Content on Top of Existing NW Portal

Context

NoteIf you model a product system for an SAP CRM 7.0 or SRM 7.0 with an SAP NetWeaver Java component (for example, SAP Enterprise Portal), create a separate product system for the SAP NetWeaver product. All installed SAP NetWeaver product instances have to be assigned to this product system. This is relevant for the following product versions and their related EHPs:

● SAP CRM 7.0● SAP CRM 7.0 / NW7.01● SAP SRM 7.0● SAP SRM 7.0 / NW7.01

Initial situation:

● Installed: SAP CRM Application Server ABAP or SAP SRM Application Server ABAP● Installed: SAP NetWeaver Enterprise Portal Core (or Enterprise Portal)● SLD data suppliers on technical systems forward system information to the SLD and to SAP Solution

Manager.

To install portal content, you have to assign it to the product system in SAP Solution Manager in advance. This enables Maintenance Optimizer to calculate the required stack XML file for installation. Proceed as follows:

Procedure

1. In transaction LMDB of SAP Solution Manager, edit the CRM/SRM product system.

To add the product instance for SAP CRM/SRM portal content, which you are planning to install, choose Add in the product system editor. In the new window for product instance assignment, select the AS Java



technical system on which the NW Enterprise Portal is installed. Now search for the product version 'SAP CRM' or 'SAP SRM', and assign the portal content product instance:

Do not verify the product system; if you do verify it, ignore any verification error that reports missing product instances.

You can now see the following assignments in the LMDB product system editor:

The portal content instance is assigned, but not yet installed.2. Start a maintenance transaction (type 'maintenance'). It offers additional, preselected installable Java

instances, as shown in this example:



Create the new stack XML file for the update, including the portal content instance.3. Install the update with Software Update Manager (SUM), which will install the additional selected instance.

Note: This will also install new, equivalent service pack stacks.

4. Activate the new usage type. For more information, see SAP Note 1793486 .5. The system information is automatically updated by the update, and forwarded by SLD data suppliers.

Results

The following graphic shows which product instances were initially installed and which were assigned and installed in the maintenance process:




4.3 Add Installation of SAP ERP Portal Content on Top of Existing NW Portal

Context

Initial situation:

● Installed: SAP ERP ECC Server (ABAP)● Installed: SAP NetWeaver Enterprise Portal Core● SLD data suppliers on technical systems forward system information to the SLD and to SAP Solution

Manager.

To install portal content, you have to assign it to the product system in SAP Solution Manager in advance. This enables Maintenance Optimizer to calculate the required stack XML file for installation. Proceed as follows:

Procedure

1. In transaction LMDB of SAP Solution Manager, edit the ERP product system and add the product instance for portal content, which you are planning to install.For more information, see the previous chapter, Add Installation of SAP CRM or SRM Portal Content on Top of Existing NW Portal [page 9].

You can now see the following assignments in the LMDB product system editor:

2. Start a maintenance transaction with Maintenance Optimizer:

Select a support package stack for SAP ERP and, if required, additional Java instances (technical usages).

Select the technical usages that are required to add the portal content of the corresponding application.

NoteFor ERP Portal Content, you can also install a selective subset of business packages, which is supported with SUM as of SL Toolset SP06. To do so, in Maintenance Optimizer step 2.5 (Select Stack-Dependent Files), you can deselect business packages. The following minimum target SP ERP stack levels are required:



○ EHP4 FOR SAP ERP 6.0 SP12○ EHP5 FOR SAP ERP 6.0 SP09○ EHP6 FOR SAP ERP 6.0 SP05○ EHP7 FOR SAP ERP 6.0 SP00

3. Install the updates from the stack XML, with Software Update Manager (SUM).4. The system information is automatically updated in the SLD and LMDB by SLD data suppliers.

Results

The following graphic shows which product instances were initially installed and which were assigned and installed in the maintenance process:

4.4 Modeling of SAP SEM-BW, SAP ERECRUIT, LSOFE, and FINBASIS

Context

SEM-BW, ERECRUIT, LSOFE, and FINBASIS are add-ons that can be installed as part of the SAP ERP ECC server or stand-alone on SAP NetWeaver systems. They are modeled in the SAP ERP product in the SAP software catalog (SAP-internal: PPMS system), so the technical system with the add-on must be configured as an SAP ERP system. For more information, see the next section and SAP Note 1326576 .

For SEM-BW, additional product versions were created in the SAP software catalog, to make maintenance with SAP Solution Manager easier. For new stand-alone installations of SEM-BW on SAP NetWeaver systems, select the new SAP SEM add-on product. The new product versions contain the same ABAP components as the SAP




SEM product instance in SAP ERP. For more information, see Handling SEM-BW as Part of the NW Add-On SAP SEM Product [page 16].

For SEM-BW, you can also change the installed product information from SAP ERP to SAP SEM. For more information see CISI for SAP SEM as Part of ERP: Change to NW Add-On Product Version [page 20]. This process is especially recommended if you want to upgrade to SEM-BW 736 on HANA.

For supported upgrade and update paths, see Upgrade and Update Paths for BW 7.0x to 7.3x under http://help.sap.com/sem.

4.4.1 Handling Add-Ons as Part of the SAP ERP Product

Context

Procedure

1. In the LMDB of SAP Solution Manager, an AS ABAP is automatically registered as technical system, including the product instances that are installed on it.

2. Create the product system, manually, and assign the following product instances to the SAP NetWeaver product system:

○ For SAP-SEM:

○ SAP SEM (for SAP ERP 6.0)○ SAP SEM (for EHP<xy> FOR SAP ERP 6.0) = Add-On○ Application Server ABAP (for SAP EHP<xy> FOR SAP NETWEAVER 7.0)

○ For FINBASIS:

○ SAP FSCM - FSCM Server (for SAP ERP 6.0)○ Finbasis (for EHP<xy> FOR SAP ERP 6.0) = Add-On○ Application Server ABAP (for SAP EHP<xy> FOR SAP NETWEAVER 7.0)

○ For ERECRUIT:

○ SAP E-Recruiting (for SAP ERP 6.0)○ SAP E-Recruiting (for EHP<xy> FOR SAP ERP 6.0) = Add-On○ Application Server ABAP (for SAP EHP<xy> FOR SAP NETWEAVER 7.0)

○ For LSOFE:

○ SAP Learning Sol-Frontend ABAP (for SAP ERP 6.0)○ Learning Solution – ABAP only (for EHP<xy> FOR SAP ERP 6.0) = Add-On○ Application Server ABAP (for SAP EHP<xy> FOR SAP NETWEAVER 7.0)



http://help.sap.com/disclaimer?site=http://service.sap.com/%7Esapidb/011000358700000890142012E

http://help.sap.com/sem

http://help.sap.com/sem

In the editor for product systems of the LMDB, the assignment of product instances can look like this, for example:

3. Start a new Maintenance Optimizer transaction for the SAP ERP 6.0 product version:

(For the EHP, you cannot create a maintenance transaction, because it is not a standalone add-on product version.)

4. In Maintenance Optimizer, assign the required technical usage:

○ for SEMBW: Strat Enterpr Mgmt Standalone○ for FINBASIS: Finbasis Standalone○ for LSOFE: SAP Learning Sol Standalone○ for ERECRUIT: ERecruiting Standalone



4.4.2 Handling SEM-BW as Part of the NW Add-On SAP SEM Product

Context

For the product system modeling in SAP Solution Manager, assign the following product instances to the SAP NetWeaver product system:

Procedure

1. In the LMDB of SAP Solution Manager, the technical system is automatically registered, including its installed product instances. You manually create the product system, for further maintenance.

2. Create the product system, manually, and assign the following product instances to the SAP NetWeaver product system:

For SAP-SEM:

○ SAP SEM (for EHPxx FOR SAP SEM 6.0)○ Application Server ABAP (for SAP EHPxx FOR SAP NETWEAVER xx)

3. Start a new Maintenance Optimizer transaction for the SAP NetWeaver product system.

The supported target version of the SEM-BW add-on will be preselected in the add-on screen.

Next Steps

If you have installed SAP SEM as ERP product, how to change the installed product information into the SAP SEM add-on product information is explained under CISI for SAP SEM as Part of ERP: Change to NW Add-On Product Version [page 20].



4.4.3 Correction of Installed Software Information (CISI) for SEM-BW

Context

There are situations where it is required to change the labels of installed software information directly in the tables of a technical system, without actually changing the installed software itself. To do so you can perform a 'correction of installed software information' (CISI). For more information, see SAP Note 1816146 .

The following two sections describe how you can change the installed software information for SAP SEM-BW for the following two major use cases:

● CISI for SAP SEM as Part of ERP: Change from NW703 to NW731 [page 17]● CISI for SAP SEM as Part of ERP: Change to NW Add-On Product Version [page 20]

4.4.4 CISI for SAP SEM as Part of ERP: Change from NW703 to NW731

Context

After an update to EHP6 FOR SAP ERP 6.0, the underlying SAP NetWeaver product version is technically set to EHP3 FOR SAP NETWEAVER 7.0, in the system tables. This is the default release of the product version EHP6 FOR SAP ERP 6.0.

SAP EHP1 FOR SAP NETWEAVER 7.3 contains the same set of ABAP software component versions as EHP3 FOR SAP NETWEAVER 7.0 but the label of the product versions is different. The start profiles are consolidated.

However, in the SAP SEM scenario there are situations which require that you rename the product information for the SAP NetWeaver version in the system tables to EHP1 FOR SAP NETWEAVER 7.3, for example if you want to migrate your database to SAP HANA. For the rename, you can use the CISI procedure.

This is the old information that is stored in the tables PRDVERS and SWFEATURE on the technical system and that is forwarded by data supplier to the System Landscape Directory (SLD) and to the LMDB in SAP Solution Manager:

● SAP EHPxx for SAP NetWeaver 7.0: Application Server ABAP (= obsolete)● SAP ERP 6.0: SAP SEM● EHPxx for SAP ERP 6.0: SAP SEM




The same product instances are assigned to the product system description:

With this obsolete product information, Maintenance Optimizer cannot calculate the appropriate stack xml file for future updates. You need to adjust the product system information manually, according to the updated product version.

NoteAdjust the data only for the product system. Do not manually change the information for the technical system in the LMDB, which must always be provided automatically by SLD data supplier.



Procedure

1. Start transaction LMDB, select the related product system and choose Edit.

2. In the navigation tree, choose Technical Systems.

Choose the row with the product instance SAP EHPxx FOR SAP NETWEAVER 7.0: Application Server ABAP. Choose Edit Selected.

3. In the popup, select Select By: Product Version and enter SAP EHP1 FOR SAP NETWEAVER 7.3. Choose Search.

In the search results, set the Assigned indicator for the new product instance:

Choose Close.4. Choose the row with the product instance SAP EHP3 FOR SAP NETWEAVER 7.0 and choose Delete:

Confirm with OK.5. Save your changes in the editor for product systems.6. You can now create the CISI.XML file from the updated product system description:

Start transaction SA38 and run the report RLMDB_DOWNLOAD_INST_SOFT_INFO.

Select the affected product system and choose Execute.

Save the CISI.XML.

For more information about the CISI process, see SAP Note 1816146 .7. Update the installed software information with SUM:

Start SUM on the technical system on which the application server ABAP of SAP EHP1 for SAP NetWeaver 7.3 is installed. In the Select Target step, select the CISI XML file.

8. Check the PRDVERS table of the technical system, which should now look like this:




Check the SWFEATURE table of the technical system, which should now look like this:

9. When the RZ70 data supplier has automatically forwarded the updated information to the SLD, the following data is visible in the SLD:

10. The SLD data is automatically synchronized with SAP Solution Manager. In transaction LMDB, the new product version and product instance are now marked as Installed on the technical system.

11. View the product system in the LMDB and select the Verification step and run a verification. There should not be any errors.

Next Steps

For more information on the start profile consolidation, see SAP Note 1326576 .

4.4.5 CISI for SAP SEM as Part of ERP: Change to NW Add-On Product Version

Context

You can install the SAP SEM product only as add-on on an SAP NetWeaver system. For example, you can upgrade directly to SAP EHP1 FOR SAP NETWEAVER 7.3. You do not need to update to SAP EHP3 FOR SAP NETWEAVER 7.0 in advance, and overwrite the CISI information afterwards. However, you can use the CISI procedure to change from SAP ERP or SAP ERP EHP to SAP SEM to become more independent of SAP ERP for future maintenance processes. This is only possible if you have SAP SEM as an add-on on top of SAP NetWeaver, and not if you have a complete ECC server.




This is the old information, which is stored in the tables PRDVERS and SWFEATURE on the technical system:

● SAP EHP3 for SAP NetWeaver 7.0: Application Server ABAP (= outdated)● SAP ERP 6.0: SAP SEM● EHP6 for SAP ERP 6.0: SAP SEM

The same product instances are assigned to the product system description:

To be able to use the new SAP SEM Add-On product version you need to adjust the product system information manually.

NoteAdjust the data for the product system. Do not change the information for the technical system in the LMDB. This information must always be provided automatically by SLD data supplier.



Procedure

1. Start transaction LMDB, select the related product system and choose Edit.

2. In the navigation tree, choose Technical Systems.

Choose the row with the product instance SAP EHP3 FOR SAP NETWEAVER 7.0: Application Server ABAP. Choose Edit Selected.

3. In the popup, select Select By: Product Version and enter EHP6 FOR SAP SEM 6.0. Choose Search.

In the search results, set the Assigned indicator for the new product instance:

Choose Close.4. Choose the rows with the old product instances SAP EHP6 FOR SAP ERP 6.0 and SAP ERP 6.0 and choose

Delete:

Confirm with OK.5. Save your changes in the editor for product systems.6. You can now create the CISI.XML file from the updated product system description:

Start transaction SA38 and run the report RLMDB_DOWNLOAD_INST_SOFT_INFO.

Select the affected product system and choose Execute.

Save the CISI.XML.

For more information about the CISI process, see SAP Note 1816146 .7. Update the installed software information with SUM:

Start SUM on the technical system on which the application server ABAP of EHP3 FOR SAP NETWEAVER 7.0 or SAP EHP1 FOR SAP NETWEAVER 7.3 is installed. In the Select Target step, select the CISI XML file.

8. Check the PRDVERS table of the technical system, which should now look like this:




Check the SWFEATURE table of the technical system, which should now look like this:

9. When the RZ70 data supplier has automatically forwarded the updated information to the SLD, the following data is visible in the SLD:

10. The SLD data is automatically synchronized with SAP Solution Manager. In transaction LMDB, the new product version and product instance are now marked as Installed on the technical system:

11. View the product system in the LMDB and select the Verification step and run a verification. There should not be any errors.



4.5 Updating to SAP NetWeaver 7.3 Hub

Context

For more information, see the SAP Community Network at SAP NetWeaver 7.3x hub systems upgrade .

Procedure

4.6 Products Not Relevant for Maintenance Optimizer

Context

SAP MDM 7.1 (SAP NetWeaver Master Data Management 7.1)

Maintenance transactions with Maintenance Optimizer are not relevant for any product instances of SAP NetWeaver Master Data Management 7.1, .

4.7 Products that Are Only Partially Relevant for Maintenance Optimizer

There are SAP product versions for which Maintenance Optimizer can calculate update or upgrade information only some product instances.

Context

SAP IdM (SAP NetWeaver Identity Management)

The SAP IDM Web UI is an SAP NetWeaver add-on product instance. No other parts of SAP IDM product version are deployed on the SAP NetWeaver stack of the AS Java technical systems, so information about these parts is



http://help.sap.com/disclaimer?site=http://wiki.sdn.sap.com/wiki/x/0QEiEg

not forwarded to SAP Solution Manager by the SLD, and must be created in the LMDB manually. It is not checked by the verification function for product systems, but Maintenance Optimizer does consider it for the stack XML file in maintenance transactions. All IDM software components for AS ABAP and AS Java technical systems can be updated by SUM. Updates for any other system types are also calculated correctly, but remain in the download basket; you can install them manuallywith the dedicated installation tools.

In addition to the IDM Web UI instance, IDM consists of other AS Java stand-alone product instances of the Identity Center Runtime and the database for the Identity Center Designtime.

In the LMDB, a technical system with an IDM deployment can look like this:

For the IDM product system that you have to create in the LMDB, only the technical system on which the IDM Web UI is installed is relevant. The product system can be modeled like this:

In the editor for product systems of the LMDB, you can create a maintenance transaction for the SAP NetWeaver product version, because it is stand-alone:



Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


SAP Solution Manager: Special Cases in Installation and UpgradeImportant Disclaimers and Legal Information

http://help.sap.com/disclaimer/

SAP Solution Manager: Special Cases in Installation and UpgradeImportant Disclaimers and Legal Information


www.sap.com/contactsap

© 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Documents

SAP Solution Manager: Special Cases in Installation and