Show TOC

Procedure documentationUpgrade with an Enhancement Package


When you upgrade a product version for a system, Maintenance Optimizer can find and implement its enhancement packages as well. Maintenance Optimizer calculates all the files that you have to download in addition to the files delivered on the upgrade DVD provided by SAP Service Marketplace. Maintenance Optimizer leads you through the implementation of these files.


  • You have a product version for which SAP offers an upgrade, and you want to install an enhancement package at the same time.

  • You want Maintenance Optimizer to determine the download files.

  • For information about prerequisites, see Prerequisites.


Step 1: Plan Maintenance
  1. Enter the required transaction information. The following fields require input:

    • Priority

      Specify the priority of the transaction.

    • Description

      The text New Maintenance Optimizer Transaction is the default. You can put a short description in the field.

    • Product Version

      Select the product version for which you want to determine and install the enhancement package release for the upgrade. Maintenance Optimizer displays all the product systems assigned to the product version.

    • Product System

      Select the product systems for which you want to install the enhancement package.

    Entries are optional in the following fields:

    • Solution

      If you use solutions, you can specify a solution at the start of the transaction.

    • More Fields...

      You can specify the processor and the requester. You can also display the documents assigned to the transaction, or upload documents yourself.

  2. Choose Continue. The system checks the product instances installed in your product system, and determines the update options. This check is based on the settings that you made in the Landscape Management Database (LMDB) for the selected product system.

Step 2: Select Files
  1. Choose Calculate Files Automatically and then Continue.

  2. Select the enhancement package for the product version you want to upgrade. This option is only available when you have selected a product version in step 1, for which an upgrade with the installation of an enhancement package is possible.

  3. Choose Continue

Maintenance Optimizer shows the following additional steps, in which you can select the files to download.

Step 2.1: Choose stack

Maintenance Optimizer lists all enhancement package releases that can be installed for the product version specified in step 1, in a drop-down list.

  1. Choose an enhancement package release.

  2. As well as specifying the enhancement package release, Maintenance Optimizer proposes a target stack, in a drop-down list. A compatible support package stack is usually installed when you install an enhancement package.

    Choose the version of the target stack.

    You can display a summary of the contents of the selected target stack, with Stack Details.

  3. If you want to install an enhancement package with technical usages, Maintenance Optimizer lists the technical usages.

    Select technical usages. Technical usages already installed in the system are automatically selected.

    Note Note

    Maintenance Optimizer evaluates the software component versions of the product instances of the already-installed technical usages. This result is sometimes ambiguous. Other technical usages which contain the same software component versions, are flagged as installed.

    Check that the product instance for a technical usage is installed in the technical system.

    End of the note.

    All technical usages in the product instance are listed under a product instance. You can display detailed information about technical usages via the links. This is the product instances of the selected enhancement package release, required product instances, product versions, and product systems.

    You can only install technical usages whose required product instances are assigned in the product system. For technical usages that are not available, the product instances are colored red.

  4. (optional) If you have already scheduled the scope of business functions in a project, you can display the required technical usages. You must have activated project selection in Customizing for SAP Solution Manager. For further in information, see Customizing for Start of the navigation path SAP Solution Manager Next navigation step Capabilities Next navigation step Maintenance Management End of the navigation path.

    Proceed as follows:

    1. Choose Get Technical Usages from Project.

    2. Select the project from the value help.

      The system lists all matching logical components and product instances for the product version selected in the maintenance transaction. The system determines the technical usages required, from these product instances. You can accept these selections by default.

      You can also go to the Business Function Scope transaction, and get information about the business functions planning and activation status in the project.

      You can deselect logical components, if you are still in the planning phase, and have not yet assigned systems to them, in the Project Management, in the System Landscape tab.

    3. Confirm.

  5. If you have assigned Java technical systems to your maintenance transaction, Maintenance Optimizer also shows all installable Java instances. Java instances which are relevant for the selected version of the target stack, are pre-selected.

    Select other Java instances to be installed during your maintenance transaction.

  6. Choose Continue.

Step 2.2: Confirm target

Maintenance Optimizer lists the target constellation for the selected product systems and other technical systems, which are affected by the upgrade.

Confirm the target constellation with Continue.

Step 2.3: Select Add-On Products

This step is only available when the following conditions are met:

  • You have a license for add-ons that are available in the selected target product version.

  • The selected target product version is based on at least SAP NetWeaver 7.02.

Proceed as follows:

  1. Select the add-on product versions that you want to install in the selected product system, in the Product Version column. Their product instances are selected automatically.

    The link in the Product Version column gives you information about the instances. If you have not yet selected the product version, you can select any product instance.

    You assign the selected product instances to a technical system by choosing Assign System. You can assign several technical systems to a product instance, according to the list.

    For already-installed add-on product versions:

    • If an add-on product version is installed in the selected target product version, Maintenance Optimizer selects it automatically, and you cannot deselect it.

    • If the installed add-on product version is not suitable for the selected constellation, an upgrade must be performed for this add-on product version. Maintenance Optimizer selects the highest available product version. If there is only one add-on target product version, you cannot deselect it. If there is no add-on target product version, you are warned on the Log tab.

    Maintenance Optimizer lists add-on product versions in the target product version that you can also install.

  2. Select the stack level for the selected add-on product versions, in the Stack column.

  3. You access the Product Availability Matrix (PAM) in the SAP Support Portal by choosing the link in the Documentation column. This information is shown in a separate window.

  4. Choose Continue.

Step 2.4: Select OS/DB-dependent files

Maintenance Optimizer shows a list of files. It is sorted by operating system and database.

  1. Choose files for your operating system/database combination.

    Note Note

    Maintenance Optimizer selects the database-independent files for the files for a database and operating system that you have selected.

    End of the note.
  2. Choose Continue.

Step 2.5: Select stack-independent files

If your selection contains files that are not assigned to a stack, Maintenance Optimizer shows these stack-independent files. Stack-independent files are, for example, database, kernel or operating system files.

Maintenance Optimizer proposes the highest currently available support package for download, for system components with no support package stack.

Note Note

Support packages for which there is no delivery package in the SAP Service Marketplace, are flagged with a red star.

End of the note.
  1. Check the selection. Deselect files which you do not need.

  2. If the selection you made in the previous step contains add-ons, Maintenance Optimizer shows them.

    Check the selection. Deselect files which you do not need.

  3. You can also select files from the download basket that are also to be downloaded for this maintenance transaction, manually.

    Choose Include/Exclude Files in Download Basket.

    Note Note

    Maintenance Optimizer downloads these files, but does not automatically import them. You must import them yourself, later.

    End of the note.
  4. Choose Continue.

Step 2.6: Select stack-dependent files
  1. Check the automatic Maintenance Optimizer selection. All displayed files are in one or more selected stacks.

    Note Note

    Maintenance Optimizer downloads these files, but does not automatically import them. You must import them yourself, later.

    End of the note.
    • If you want to put current patches for Java support packages, in your maintenance transaction, choose Add Java Patches. A dialog box appears.

      Select files and choose OK.

    • To add HR Support Packages or Country Legal Change Packages (CLC Packages) for an HR system selected as a product system, to your maintenance transaction, choose Add HR Packages. A dialog box appears.

      Select files and choose OK.

  2. Choose Continue.

Note Note

In Maintenance Optimizer, you can restrict the data selected to the software packages required to run your business applications. For ABAP, select the required industry-specific packages, and for non-ABAP the required business packages.

End of the note.
Step 2.7: Confirm selection
  1. Specify how the selected files are to be downloaded:

    • You can download with the download basket.

      The files are first put in the download basket, and then downloaded to your local computer. For more information, see Approve and Download Files into Download Basket.

    • You can download with the Software Lifecycle Manager.

      It loads the files into a central directory, from which they can be installed quickly. Continue by downloading the files with the download manager or the software lifecycle manager. For more information, see Downloading Files.

  2. To download from the download basket, continue as described in Approve and Download Files in Download Basket in Step 3: Download Files, as described under Download.

    To download with the Software Lifecycle Manager, choose Continue.

Note Note

A package configuration file containing your selections, based on your entries, is generated. Once you confirm the selection, this file is stored in the database in the SAP Solution Manager, and, at operating system level, in the Electronic Parcel Service inbox of the transport directory.

For more information, see the SAP Solution Manager security guide in the SAP Service Marketplace, under Start of the navigation path published on SAP site Next navigation step SAP Components Next navigation step SAP Solution Manager End of the navigation path. The SAP software logistics tools read this package configuration file and create the instances.

End of the note.

Caution Caution

Do not change the configuration file manually. The SAP software logistics tools do not support changes.

End of the caution.

The following steps are only relevant for download with the Software Lifecycle Manager.

Steps 3-5 Download Files, Implement, and End Maintenance

Information about steps 3, 4 and 5 start at Step 3: Download Files under Maintenance Transaction with Installation of a Support Package Stack.