SAP Support Packages

Objectives

After completing this lesson, you will be able to:
  • Describe the prerequisites for requesting an SAP Support Package Stack
  • Import an SAP Support Package that requires a modification adjustment
  • Explain the difference between SAP Support Package Stacks and Feature Package Stacks

Introduction to SAP Support Packages and SAP Support Package Stacks

An AS ABAP based SAP system consists of different software components (see the following figure). All of these software components are regularly updated using SAP Support Packages. With the help of SAP Support Packages, issues are solved, legal changes are shipped, security issues are solved, and new functions are provided.

The SAP system should always be kept at an up-to-date level so that errors in the standard release are proactively removed.

What is an SAP Support Package?

An SAP Support Package is a group of corrected or new SAP objects. SAP Support Packages are required to correct issues in various components. This is done by replacing erroneous objects with corrected versions of these objects.

Each software component (such as SAP_BASIS) has a separate sequence of SAP Support Packages.

An SAP Support Package Stack is a set of SAP Support Packages for a product version that are best implemented together. SAP Support Package Stacks allow you to keep productive applications up to date on a regular basis with a minimal cost of ownership.

Hint

In contrast to SAP Support Packages, Feature Packages (FPs) might include innovations, product features, functions, or functionality in addition to corrections. With regards to technology, upgrade, and administration, Feature Packages and SAP Support Packages are handled in the same manner, however. For details, see the end of this lesson.

Requesting SAP Support Packages

Before you can apply SAP Support Packages, you must download them from the SAP Support Portal. You should apply whole SAP Support Package stacks rather than other combinations of SAP Support Packages.

For requesting SAP Support Packages, you need your SAP system registered in your SAP Solution Manager system. This SAP system information is brought to SAP Support Portal. Here, you start the Maintenance Planner to calculate the SAP Support Packages.

  1. Register your SAP system to be patched in a central System Landscape Directory (SLD). In this SLD technical information about your SAP system is stored.
  2. Transfer the information from SLD via batch job to your central SAP Solution Manager system, into the Landscape Management Database (LMDB).

    Note

    You can also decide to send the system data directly to the LMDB and not through the SLD.

  3. Manually check or define a Technical system in LMDB.
  4. Transfer the information from LMDB using batch job to SAP Support Portal.
  5. In SAP Support Portal, start the Maintenance Planner. Define SAP System dependencies and perform some verification.
  6. Use the Maintenance Planner to calculate the list of SAP Support Packages to be applied.
  7. From Maintenance Planner, download an XML file containing the description of the calculated SAP Support Packages to be applied. Use Maintenance Planner to push the calculated SAP Support Packages to your download basket. Use the Download Manager to download the calculated SAP Support Packages from your download basket.
  8. Start the tool to apply the SAP Support Packages, either SPAM or SUM. When using transaction SPAM, this transaction needs to be executed in client 000 of the system in question.

Note

You can also use Data Supplier Processing, where the managed systems send data directly to the LMDB and not through the SLD. For details, see SAP Note 2183995 – Data Supplier Processing in SAP Solution Manager 7.2 in LMDB.

You can also send the data from the Data Supplier directly to SAP Support Portal (without involving SAP Solution Manager). For more information, see SAP Note 2855951 – How to Configure SLD Data Supplier to Directly Send Data to SAP's Support Backbone.

You also need a valid maintenance certificate in order to apply SAP Support Packages.

SAP recommends that you create the maintenance certificates automatically with SAP Solution Manager. This takes much less effort than creating them manually, especially if maintenance certificates for several SAP systems are needed. A maintenance certificate can also be created manually using the SAP Support Portal (using the License Key application).

Hint

A maintenance certificate is valid for three months only. For more information, see the SAP Support Portal, area Maintenance → Maintenance Information → Maintenance Certificate.

Importing SAP Support Packages

Prerequisite: SPAM/SAINT Update

To import SAP Support Packages, you can use SAP Support Package Manager (transaction SPAM). Here SAP Support Package refers to kind of transport request, for problem fixing, legal changes, solving security issues and new functionality for a software component of an SAP system and Support Package Manager (SPAM) refers to Tool in the SAP system for applying SAP Support Packages.

Before using the SAP Support Package Manager, you should patch the tool itself with a SPAM/SAINT update. This is a patch to enhance the functions of transactions SPAM and SAINT, for example, when dealing with new attributes from new SAP Support Packages.

Note

Transaction SAINT (Software Add-On Installation Tool) allows you to install and upgrade add-ons.

Note

SPAM/SAINT updates are in German and English only. See SAP Note 170543 – Transaction SPAM only useable in language D and E. If you work in another language, new or updated user interface elements and texts might not be properly displayed. SAP recommends that you log on in German or English if you want to use the Support Package Manager.

After you have updated transactions SPAM and SAINT to the latest patch level, from a technical perspective, you're ready to import an SAP Support Package stack.

Process Flow

SAP Support Package Manager ensures that only SAP Support Packages that match your SAP system are displayed in the queue. SAP Support Packages that are intended for a different release or an add-on that is not installed don't appear in the queue.

You can compile a shared queue for all software components in the SAP system, by choosing All Components.

The queue contains the SAP Support Packages available for the selected component(s) in your SAP system and any required Conflict Resolution Transports (CRTs) and associated Add-on SAP Support Packages.

The following rules apply when you create a queue:

  • SAP Support Packages for a selected software component are placed in the queue according to their sequence.
  • If SAP Support Packages in the queue are related to SAP Support Packages for another software component (predecessor relationship, CRT required), the extra SAP Support Packages will be added to the queue until all predecessor relationships are included.

If the SAP system has calculated a consistent queue, you can display it and check it by choosing the Calculated Queue tab.

Import Process

Transaction SPAM offers different scenarios to import the Support Packages. To set the desired scenario, choose Extras → Settings.

  • Use the test scenario to check whether a modification adjustment is necessary, or whether there are any conflicts or problems (such as unreleased repairs), before you actually import the SAP Support Package. Use this scenario to estimate and possibly minimize the effort needed to import the SAP Support Packages. This scenario imports no data or objects into your SAP system. If errors occur, you can continue the import without the need to remove the errors.

    Note

    You need to select the test scenario explicitly. Note that the queue is empty after you run the test scenario and you need to define it again. You then need to select the standard scenario explicitly.

  • The standard scenario imports all SAP Support Packages in the queue completely. If errors occur, you can only continue and complete the import after you have removed the errors. If you selected the standard scenario, you could choose between the standard import mode and the downtime-minimized import mode to reduce downtime.

Note

During the time needed for importing SAP Support Packages, no imports can take place, and no manual changes can be made to repository objects (ABAP programs, dictionary objects). The transport requests for modification adjustment are handled in a special way, so the time for importing SAP Support Packages should be kept as short as possible.

Hint

When importing SAP Support Packages, the SAP Support Package Manager will check if there are still any transport requests in the import queue for the old SAP Support Package level. In this case, the SAP Support Package Manager returns a warning. You have the option to ignore the warning and still import the SAP Support Packages.

Due to the size and scope of current SAP Support Packages, importing SAP Support Packages requires longer SAP system downtime. The SAP system is not stopped and restarted during the import process, but it cannot be used productively during this time. This restriction is a disadvantage for many production systems.

To reduce the downtime during the import of SAP Support Packages, an import procedure has been developed that allows you to import a large portion of the objects to be imported during production operation. These objects are mainly programs. The downtime can be significantly reduced if an SAP Support Package contains a high portion of programs (the portion might be up to 80%). With the downtime-minimized import mode (not shown in the figure above), the objects are imported into the database in an inactive state and are, therefore, "invisible" to the SAP system and you can continue to use the SAP system productively for a longer time.

Hint

It is also possible to import SAP Support Packages with the Software Update Manager (SUM). Importing SAP Support Packages with SUM is more difficult for the SAP system administrator, but can lead to a shorter downtime if configured correctly.

Modification Adjustment

The modification adjustment works as follows:

  1. The SAP Support Package Manager stops in order to allow the modification adjustment.
  2. Create one transport request in the Transport Organizer and tasks inside the transport request for the developers so that your developers can perform the modification adjustment.
  3. Ask the developers to perform the modification adjustment for their objects. After the adjustment is complete, the developers must release their tasks and inform you. The adjustment should be performed in the development client, not client 000, of course.
  4. If you left the transaction, call the Support Package Manager (transaction SPAM) again, and choose Support Package → Import Queue from the menu. Then the SAP system prompts you again to perform the modification adjustment. As it has already been completed, ignore the message and choose Continue. The Support Package Manager then completes the processing and displays the status.

The import logs of the queue function displays logs for steps of the Support Package Manager that use the transport control program tp. After the queue has been successfully imported, you should always check these logs. To jump to the log display, choose the menu path Goto → Import Logs → Queue in the initial screen of the Support Package Manager.

Finally, you need to confirm the successful import of the queue into your SAP system. This ensures that you can import other SAP Support Packages in future.

If you have not yet confirmed successfully imported SAP Support Packages, you will be prompted to confirm these packages during the next update of the SAP system.

Note

Without this confirmation, you can't import additional SAP Support Packages or complete even other maintenance-related tasks, such as the implementation of SAP Notes in transaction SNOTE.

If you have a multi-system landscape, you only need to perform the modification adjustment once. The system stores the data for the modification adjustment in transport requests that you can include in the import process when importing the Support Package queue into the follow-on systems.

Hint

When a modification adjustment transport is imported as part of a Support Package queue, it is deleted from the normal transport flow for workbench transport requests. Modification adjustment requests are not forwarded to follow-on systems automatically.

If you are working with the classic three-system landscape comprising a development system (DEV), quality assurance system (QAS) and production system (PRD), the modification adjustment transport is put into the QAS import queue after being exported from the DEV system. Including the adjustment transport in a Support Package queue in system QAS deletes it from the QAS import queue. Because no transport forwarding takes place when importing a Support Package queue, the adjustment transport is not forwarded into the import queue of the PRD system. This means that the modification adjustment will not be imported to your PRD system with the Transport Management System.

As a consequence, you need to import the adjustment transport into the PRD system as part of a Support Package queue using the same procedure as in the QAS system.

SAP Support Packages and TMS

Note

In the remaining part of this lesson, for the sake of simplicity, the term SAP Support Package is used for both SAP Support Packages and SAP Support Package stacks.

A transport request that has been released from an SAP system with a certain release should only be imported into an SAP system with the same release. This is obvious when transporting objects from the SAP standard, for example modifications and customizing. But this restriction should also be considered, when transporting customer developments, because these can be related to SAP standard objects.

You must consider not just the release, for example SAP S/4HANA Server 2020 versus SAP S/4HANA Server 2021, but also the level of the corresponding software components and the SAP Support Package level. For example, a transport request that has been exported from an SAP S/4HANA 2021 Server with S4CORE Support Package 2 should not be imported into an SAP S/4HANA 2021 Server with S4CORE Support Package 1.

Hint

The export release should be equal to the import release. Transport requests usually rely on a certain release of the corresponding software components and their SAP Support Package level. They should not be imported to an SAP system with a different level than the one from which they were exported.

As a result of this, the applying of SAP Support Packages and the importing of transport requests must be coordinated (see the following figure).

The Transport Management System (TMS) checks if a transport request fits the software component version and SAP Support Package level of the target SAP system. The result of this check can be seen in the import queue, in the CV column (to see this column, choose Display More in the application toolbar). This is done by comparing the software component vector of the transport request with the software components of the target system. If the check is negative, the Status column shows the icon for Request does not match component version. For details, see the following figure.

Hint

A transport request that does not fit the target system can still be imported choosing the import option Ignore Invalid Component Version.

Hint

The version check will be performed only if the tp parameter SP_TRANS_SYNC is set to ON for the SAP system to be imported in. For more information, see SAP Notes 1742547 – Information about component version check in TMS and 1688610 – TMS import queue warning message : 'Does not match component version' or 'Checking components of the requests'.

A corresponding check is also performed when importing SAP Support Packages. If there are still any transport requests in the import queue for the old SAP Support Package level, SAP Support Package Manager will return a warning (see the figure above). However, you have the option to ignore the warning and still import the SAP Support Packages.

Perform a Modification Adjustment

Business Example

To correct errors in the SAP standard, apply legal changes, apply security features, and to apply new functions, the SAP system administrator has to implement SAP Support Package Stacks on a regular basis.

Note

## represents the group number the instructor has assigned to you.

Task 1: Adjust Dictionary Elements (SPDD)

Adjust dictionary repository objects using transaction SPDD in the development system S4D, development client 100.

Steps

  1. When applying an SAP Support Package, the SAP system checks if a modification adjustment for dictionary repository objects is necessary. If this is the case, the SAP system requires you to use transaction SPDD to adjust the modification or to return to the SAP standard. With the SAP Support Package for this exercise, this is the case for your table ADM325X## (here and in the following, ## denotes the group number the instructor has assigned to you). The instructor will call transaction SPDD to display the objects to be adjusted and ask you to adjust your own object.

    1. Log on to the development system, client 100 with the credentials provided by your instructor and start transaction SPDD. The SPDD Selection and Start screen is displayed.

    2. In the Selection area, enter your user ID in the Last Changed By field and choose Execute. The Modification Adjustment — Data Dictionary screen appears. Select the Without Assistant tab to see the table you have modified.

    3. Select the line containing the dictionary object that you have modified.

      Note

      Check the version history of the affected objects using transaction SE11 (ABAP Dictionary) or from inside SPDD by selecting Compare versions (new orig. v. last mod.) in area Available Actions and then choosing Execute.

    4. On the Modification Adjustment – Data Dictionary screen, choose Adjust with Proposal from the Available Actions area. Then choose Execute.

    5. Assign the retained modification to the transport request that the instructor has created for SPDD adjustment. Confirm a dialog box about repairs. An adjustment proposal is displayed. You can either edit or accept the proposal. In this case, choose Accept Proposal.

    6. Transaction SPDD suggests keeping all SAP standard fields and to move your customer field into an append structure. Accept the name of the append (ZAADM325X##) with Continue (Enter), choose the package ZPACKAGE_## (that you have created before in this class) for the append structure and save the assignment to the package.

    7. Again, assign the retained modification to the transport request that the instructor has created for SPDD adjustment. If required, confirm a dialog box that a new task for the transport request will be created.

    8. On the Log display screen, choose Back, because there are no errors displayed.

    9. On the Adjustment for Table ADM325X##: Phase 2 screen, choose Back to return to the previous screen.

    10. Once the object has been adjusted, the SAP system automatically assigns the status Processing completed or Reset, depending on your choice.

      Note

      The object ADM325X## now contains your old modification (the field ZZBIRTHPLACE) in an append structure and the new field TELNO that came with the SAP Support Package from SAP. If you don't adjust your modification, you will lose the field ZZBIRTHPLACE and its data from your table.

      Note

      Depending on the release and SAP Support Package level of software component SAP_BASIS, SPDD displays the status symbol green mark or yellow traffic light. In case of the green mark, the modification adjustment for this object is completed. In case of the yellow traffic light, you still have to select the object, choose option Reset and perform Execute. A Reset resets the table itself, not the append you created. The field ZZBIRTHPLACE is located in the append and is save in both cases.

      Note

      Depending on the release and SAP Support Package level of software component SAP_BASIS, the naming of the possible actions that can be executed in SPDD vary slightly. This is subject to change in future releases and SAP Support Package levels, also.

      Caution

      It is important to perform the modification adjustment now. If not, the field would be deleted from the table as soon as transaction SPAM continues. Later, you can add the field ZZBIRTHPLACE again. But you would have lost the data that was stored in this field.

      Note

      After your decision in transaction SPDD, you should check the result using the version history of the affected objects. You can do this for example via transaction SE11 (ABAP Dictionary) . If you're not satisfied with the inactive version, change it using SE11. Don't activate the inactive version manually. This will be done by transaction SPAM later.

    11. Release your task(s) of the transport request you have chosen in previous steps using transaction SE09. Do not release the transport request itself.

  2. After all participants have completed the adjustment, the instructor now flags the SPDD transport request by choosing Modification Adjustment → Assign Transport in transaction SPDD. The instructor returns to the Support Package Manager (transaction SPAM) and continues the application of the SAP Support Package(s).

    1. The instructor continues the application of the SAP Support Package(s).

Task 2: Adjust Other Repository Objects (SPAU)

Adjust the non-dictionary repository objects using transaction SPAU in the development system S4D, development client 100.

Steps

  1. When applying an SAP Support Package, the SAP system also checks if a modification adjustment is necessary for other repository objects as those from transaction SPDD. If this is the case, the SAP system requires you to use transaction SPAU to adjust the modification or to return to the SAP standard. With the SAP Support Package for this exercise, this is the case for program ADM325X##. This is because this program has been modified in a previous exercise. The instructor will call transaction SPAU to display the objects to be adjusted and ask the participants to adjust their own objects.

    1. If you're not already logged on, log on to the development system, client 100, with the credentials provided by your instructor and start transaction SPAU.

      The SPAU Selection and Start screen displays.

    2. In the Selection area, enter your user ID in the Last Changed By field and choose Execute. The Modification Adjustment screen appears. Change to the With Assistant tab (if necessary) to see the program that you have modified in a previous exercise of this class.

    3. Discard the changes and return to the SAP standard. To do this, position your cursor on the line for the program ADM325X## and choose Reset from the Available Actions area. Choose Execute.

    4. Use the value help to assign the reset of your modification to the transport request for SPAU adjustment, which is provided by the instructor and confirm the Information dialog box with Continue (Enter).

      Note

      If you want to retain the modification, choose Adjust from the area Available Actions and then Execute (and specify a transport request). Depending on your modification, you now may enter the adjustment process using the Modification Assistant. The split screen editor may appear displaying the original object on the left and the modification on the right. Look over the code to see if you want to save your modifications or return to the original. Return to the main screen of SPAU when you're finished. The report's traffic light is replaced by a green check mark to indicate that the adjustment process is complete.

      Hint

      Remember to activate your program if you have adjusted it, otherwise the transport request containing the SPAU objects can't be released by the instructor.

      Note

      Depending on the release and SAP Support Package level of software component SAP_BASIS, the naming of the possible actions that can be executed in SPAU vary slightly. This is subject to change in future releases and SAP Support Package levels, also.

    5. Release your task of the transport request in which you have recorded your changes using transaction SE09. Do not release the transport request itself.

  2. After all participants have completed the adjustment, the instructor now flags the SPAU transport request by choosing the menu path Modification Adjustment → Assign Transport in transaction SPAU. Then, the instructor returns to the Support Package Manager (transaction SPAM) and continues the application of the SAP Support Package(s).

    1. The instructor continues the application of the SAP Support Package(s).

Result

After adjusting all modifications that are necessary, and after successfully applying the SAP Support Package queue, the instructor will check the logs in transaction SPAM. Afterward, the instructor will confirm the SAP Support Packages using transaction SPAM.

The instructor finally will release the transport requests for SPDD adjustment and SPAU adjustment.

Importing SAP Support Packages with SUM

It is also possible to import SAP Support Packages with Software Update Manager (SUM). SUM is the tool used for an SAP system upgrade, but it can also be used to import SAP Support Packages. SUM is more complicated to use than the SAP Support Package Manager, transaction SPAM, but it can generate a much shorter downtime than SPAM when configured appropriate.

Hint

If downtime is an issue, consider using SUM instead of SPAM.

The SUMStandard mode uses a shadow system in which several activities take place during the preparation phase thus reducing the downtime.

Both, SPAM and SUM can be used now and in the future. Both tools have scenarios in which they are the preferred choice.

Note

Both tools, SPAM and SUM, can be used to import SAP Support Packages. In many cases you would choose the SPAM, but you should choose SUM for importing a large number of SAP Support Packages in system landscapes with downtime critical SAP systems. For more information, see SAP Note 1803986 – Rules to use SUM or SPAM/SAINT to apply SPs for ABAP stacks.

The following figure provides advantages of both methods:

Feature Package Stacks and SAP Support Package Stacks

SAP continuously improves SAP software through the SAP Notes service and Feature Packages and Support Packages.

For SAP systems based on AS ABAP, an SAP Support Package is a bundle of software corrections available as a Support Package for the ABAP programming language.

Feature Packages are packages that deliver non-disruptive innovation for generally available product versions, also bundling software corrections and legal changes. A Feature Package delivery comes as a Feature Package stack. Like an SAP Support Package stack, it must be used in the given combination. Feature Package stacks should be seen as an entity in themselves. Customers must obey the minimum requirements and dependencies between individual components and apply the Feature Packages and patches specified in the Feature Package stack together.

Note

Feature Packages are not provided for all product versions. SAP decides case by case whether a Feature Package phase is offered after general availability of a product version for a defined period.

For on-premise software products, SAP S/4HANA provides innovations on a regular basis through releases and Feature Packages.

The last Feature Package stack for a given release before a new release is shipped is usually the starting point of the maintenance-only phase. This Feature Package stack is also called Go-to Feature Package. During a maintenance-only phase, SAP provides corrections but no new innovations for the release.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn