Show TOC

Background documentationSupport Package Manager Settings Locate this document in the navigation structure

 

Choose   Extras   Settings   to make general settings for Support Package Manager. These settings influence the behavior of the system when loading and importing various types of Support Packages. SPAM/SAINT updates are an exception, as certain default settings cannot be changed.

You only have to define the settings once. They are saved and can be used each time you call Support Package Manager. Note that these settings also apply to Add-On Installation Tool.

One exception is the setting for import mode: Downtime-minimized. This does not automatically apply to Add-On Installation Tool.

You can set or check the following attributes.

Tab page: Loading Packages

  • Directory on Application Server

    You can check which application server directory the Support Packages are located in.

  • Load CAR/SAR Archives from Front End

    • Display Content Before Decompressing

      You can decide whether to display a dialog box with the contents of the CAR/SAR archive before decompressing it. This is the default setting.

    • Delete Archive After Decompressing

      You can choose whether to delete the CAR/SAR archive transferred to the application server after decompressing it. This is the default setting.

    • Save Last Upload Directory

      You can decide whether to save the most recently used upload directory from your front-end host. This directory then appears automatically as the start directory in the archive selection dialog box next time round. This is the default setting.

      You can enter an upload directory of your choosing in the Upload directory field. This upload directory then appears as the start directory in the archive selection dialog box.

Tab page: Defining a Queue

  • Queue Calculation Initial Screen

    You can specify the queue calculation method that you want to be provided with by default upon entering the queue definition screen.

    • Queue calculation for a vector of software components

      The Support Package queue calculation takes place for multiple software components based on the target Support Package level that has been defined for each software component (see Defining a Queue Based on Multiple Software Components).

    • Queue calculation for one software component

      The Support Package queue calculation takes place by selecting one software component and the highest Support Package for this software component (see Defining a Queue Based on a Software Component).

  • Including the Modification Adjustment

    You can specify whether you want the system to always check the queue definition for modification adjustment transports that are to be included.

    • Include adjustment transports

      For the queue definition, the dialog box for including adjustment transports is always displayed.

    • Do not include adjustment transports

      No adjustment transports are included in the Support Package queue. The corresponding dialog box is not displayed automatically.

    • Always ask

      When defining the queue, the system asks you whether to include adjustment transports or not. You can then decide whether the dialog box for including adjustment transports is to be displayed or not.

  • Filtering the Component List

    You can filter the software components using different criteria. This improves the overview of the software component list for the queue definition. You can adapt the standard settings and your requirements.

    • Displaying Inactive Software Components

      As of SAP NetWeaver 7.0, SAP also delivers the Switch Framework with which you can activate individual software components by activating the related Business Function Set in the Switch Framework as required. This means that not all the software components installed in, for example, an ERP 6.0 system are active. Industry-specific enhancements, such as ECC-DMP and IS-OIL, are inactive as standard. Since support packages do not necessarily have to be imported for inactive software components, you can hide these components in the component list of the queue definition as standard.

      If you deselect this checkbox, the system does not display the inactive components.

    • Displaying Unused Subcomponents

      Some software components were divided into subcomponents that form the entire scope of the master component (originally software component). An example for this is the division of software component SAP_HR into country-specific subcomponents. Support Packages only have to be imported for those subcomponents that are actually used. You can hide the unused subcomponents from the component list of the queue definition.

      If you deselect this checkbox, the system does not display the subcomponents that you have selected as Unused using the Subcomponents pushbutton.

      • “Subcomponents” pushbutton

        You can specify which of the subcomponents are not used.

        Note Note

        When creating the subcomponents automatically, the system takes which country-specific functions are used for the SAP_HR software component from the previous use of the function and shows these as Used. You can change this setting.

        End of the note.
Tab page: Importing a Queue

  • Scenario

    When choosing the scenario, you determine which activities you want to be performed when the Support Package is imported.

    • Standard

      You use the standard scenario to import Support Packages completely. All steps are performed.

      • Import Mode Downtime-Minimized

        If you choose the standard scenario, you can also choose import mode downtime-minimized to reduce the downtime. In the default setting, this option is deactivated. The packages are imported using the conventional import method.

        Note Note

        To find the best import mode for your system, check the prerequisites under Import Mode: Downtime-Minimized.

        End of the note.

    • Test

      Use the test scenario to determine if a modification adjustment is required before the Support Package is actually imported, or if any conflicts need to be resolved before the import. The test scenario does not import data into your SAP system.

      There is no test scenario for SPAM/SAINT updates. A SPAM/SAINT import ignores the scenario you select.

  • Number of parallel processes for each R3trans

    You specify the number of parallel processes that are started by R3trans to import transport request data into the database. We recommend you set this to a maximum of 5.

    For more information about this R3trans function, see 1127194. To avoid known problems with this function, use the version of R3trans from at least 19.12.08.

    Note Note

    This option affects the import of all Support Packages imported with the Support Package Manager.

    End of the note.

  • Create New Data File

    You can determine whether the data files are to be unpacked from the EPS parcels during each subsequent import process. This is the default setting.

    If you use a multiple system landscape with a common transport directory, it is best to only activate this option in the first system into which you import Support Packages, and to deactivate it in the following systems. This saves time because the data files do not need to be created again in these systems.

    Note Note

    This option does not apply for importing SPAM/SAINT updates, the data file is always unpacked from the EPS package for this.

    End of the note.

  • Delete Data File After Import

    You can determine whether to delete the data files after the Support Packages have been imported. This saves hard disk space and is the default setting.

    If you use a multiple system landscape with a common transport directory, it is best to deactivate this option, since then you do not need to create new data files in the other systems (see Create new data file).

  • Create Object Versions During Import

    This option does not apply to SPAM/SAINT updates.

    You can choose to create versions of the objects in the Support Packages in the queue when they are imported. This option is deactivated by default, since it only makes sense to do this if version creation is active for all imports. This can take a long time and uses up a lot of space in the database.

    Note Note

    If version creation is activated in the configuration of the transport tools in the Transport Management System (transaction STMS), parameter VERS_AT_IMP must be set as ALWAYS.

    End of the note.

  • ABAP/Screen Generation

    Select this option if you want the programs and screens delivered in the Support Packages to be generated when they are imported.

    You cannot change the generation settings for SPAM/SAINT updates.

    • Never Execute

      If you set this option, the programs and screens are generated only when called for the first time.

    • Always Execute

      If you set this option, the programs and screens are always generated. Note that generation can take a long time and may cause errors.

    • According to SAP Instructions

      If you choose this option, the programs and screens are generated if the option for generating them while importing these Support Packages has been activated by SAP.

Default Settings in Support Package Manager

Option

Global Setting

Display Content Before Decompressing

On

Delete Archive After Decompressing

On

Save Last Upload Directory

On

Queue Calculation Initial Screen

Calculation for a component vector

Including Modification Adjustment Transports

Always ask

Displaying Inactive Software Components

On

Displaying Unused Subcomponents

Off

Scenario

Standard

Import Mode Downtime-Minimized

Off

Number of parallel processes for each R3trans

1

Create New Data File

On

Delete Data File After Import

On

Create Object Versions During Import

Off

ABAP/Screen Generation

Never Execute