Show TOC

Procedure documentationMaintenance Transaction with Installation of a Support Package Stack Locate this document in the navigation structure

 

In a maintenance transaction, you can import a support package stack for a product version, or install a support package stack for an existing enhancement package. Support package stacks are a combination of support packages for ABAP and patches for Java instances (not kernel patches), which were tested together by SAP, and whose implementation SAP recommends, or possibly even requires.

Note Note

When upgrading an AS ABAP on an SAP HANA database to the next support package, including the installation of an ABAP add-on:

To implement the downloaded files, use Software Update Manager (SUM) SP05 or higher. For more information about installation with SUM, see the SAP Support Portal at   https://service.sap.com/support   Release & Upgrade Info   Installation & Upgrade Guides   SAP Components   SL Toolset   Software Logistics Toolset 1.0   SUM  .

End of the note.

Prerequisites

  • You have one of the following product versions:

    • A product version for which SAP offers a support package stack.

    • A product version with an enhancement package, for which SAP offers a support package stack

  • You want Maintenance Optimizer to determine the download files.

  • For the technical prerequisites, see Prerequisites.

Procedure

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 install a support package stack. Maintenance Optimizer displays all the product systems assigned to the product version.

    • Product System

      Set the checkboxes for the product systems for which you want to call and install a support package stack.

    Entries are optional in the following fields:

    • Solution

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

    • Other 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. Choose Maintenance, and then Continue. The maintenance option is only available if there are support package stacks for the product version specified in step 1.

Maintenance Optimizer shows the following additional steps to determine the download files automatically.

Step 2.1: Choose stack

  • To install a support package stack for your product version:

    Maintenance Optimizer shows all target stacks that are currently available in the SAP Service Marketplace, for the specified product version, in a drop-down list. The current target stack is the default.

    1. Select the target stack.

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

    2. Choose Continue.

  • To install a support package stack for an installed enhancement package:

    Maintenance Optimizer lists all enhancement package releases for which support package stacks 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 installed, if technically required, when you install an enhancement package.

    3. Choose the version of the target stack.

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

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

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

    5. Choose Continue.

Step 2.2: Confirm target

Maintenance Optimizer lists the target constellation for the selected product systems and other technical systems that are affected by the installation of the support package stack.

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. Set the checkboxes of 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 can 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 in this list 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.

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 in the lists with a red star.

End of the note.

  1. Check the selection. Deselect files that 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 that 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.

    Caution Caution

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

    End of the caution.

  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.

    Caution Caution

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

    End of the caution.

    • 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   http://service.sap.com/instguides   SAP Components   SAP Solution Manager  . The SAP software logistics tools read this 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.

Step 3: Download files

  1. Choose Download.

  2. Choose Continue.

Step 4: Implementation

The security notes for the download files are displayed.

If you selected product systems in step 1, they are shown here. When the data has been downloaded, you must import it into the selected product systems.

Note Note

Depending on the maintenance plan, you can use different SAP software logistics tools to import the maintenance files provided, see Maintenance Optimizer. For more information about the Software Update Manager, see SAP Service Marketplace at   http://service.sap.com/sltoolset   Your SL Toolset Version   Documentation   Software Update Manager (SUM)  .

End of the note.

  1. Use Maintenance Optimizer to document the implementation. You can specify a start and end date, and the implementation status. You can only continue when you have selected the status Completed for all listed product systems.

    The copied and confirmed download files are listed. You can display detailed information about each file, or call a side-effect report, before implementing.

  2. When you have checked all files, and documented the implementation transaction, choose Continue.

Step 5: End maintenance

When you have implemented the files in the desired product systems, you can complete the maintenance transaction. Choose Complete Transaction.

You can then make no more changes.