Required Configuration Parameters (Phase INITSUBST)

In this dialogue, you are informed about the current scenario strategy, and you are asked to provide further parameters to configure the procedure:

• Database Archiving Parameter

  Decide on the archiving mode of your database. For more information, see Database Archiving Parameter.

• Parallel Processes Configuration

  Maintain parameter values for uptime and downtime processes. For more information, see Process and Tool Parameters.

• Batch Host Configuration

  Enter the host name of the background server and select the instance of your system that shall be used as background server. For more information, see Process and Tool Parameters.

• APO liveCache Execution Mode

  The APO liveCache must be saved before and restored after the downtime according to sections B and C of report /SAPAPO/OM_LC_UPGRADE_70. Select if you want an automatic or manual start of the report.

• SGEN Execution Mode

  Configure the execution strategy for the ABAP load generation (transaction SGEN). For more information, see SGEN Execution Modes.

• Update of Additional Application Server Instances

  If you are running additional application server instances, decide if they shall be updated. For more information, see Upgrading Additional Application Server Instances.

Inclusion of Customer Transport Buffer File (Phase SUMASK_CUSTOMER_BUFFER)

This phase is executed if the scenario category Customer Transport Integration only has been selected.

The Software Update Manager prompts you enter the name and the path of the customer buffer file that you want to include in the update.

You also get some information about the values for the transport file. For the transport profile, preselected values are taken over from the transport profile file. Moreover, you can decide if you want to override the preset value of the VERS_AT_IMP parameter. Your entries are validated later on in phase ADJUSTPRP. If the validation is successful, no further action is required. Otherwise, the corresponding dialogs are displayed.

Request for Automatic Modification Adjustment (Phase SUMASK_SPDD_SPAU)

If you have exported an ABAP Dictionary modification adjustment transport on a development system that belongs to the same system track as the current system, you can choose the appropriate request in this phase. In addition, you can decide whether you want to double-check the ABAP Dictionary modifications from that transport manually at the beginning of the ACT_UPG phase.

Your entries are validated later on in phase ADJUSTPRP. If the validation is then successful, no further action is required. Otherwise, the corresponding dialogs are displayed.

Request for Single Transport Request (Phase SUMASK_SINGLE_TRANSPORT_REQUEST)

In certain situations, you can use a single transport request to avoid data loss. The Software Update Manager prompts you enter the single change transport requests that you want to include in the update. Your entries are validated later on in phase BIND_PATCH. If the validation is then successful, no further action is required. Otherwise, the corresponding dialogs are displayed.

The modification adjustment function ignores this request. In addition, the version history for the objects in such a transport request may not be correct after the update.

Saving Variants (Phases JOB_RASUVAR1 and JOB_RASUVAR2)

After the upgrade, many of your variants can no longer be used because the relevant selection screens have changed. To save the variants, the SAP system offers two reports:

• RASUVAR1 saves your variants on the source system.

• RASUVAR2 restores the variants in the target system.

During phase SAVE_VAR_CHK, you can decide whether you want the upgrade tool to run report RASUVAR1. The report is started in phase JOB_RASUVAR1. If you have decided to run report RASUVAR1, phase JOB_RASUVAR2 automatically starts report RASUVAR2 towards the end of the upgrade.

For more information about the reports, see SAP Note 712297 .

Tool Versions (Phase TOOLCHECKXML_INI)

The Software Update Manager checks the tool versions in your system (SAP kernel patch level, the tp version, and the date of R3trans).

Add-On Strategy Check (Phase ADDON_INFO)

For most of the add-ons produced by SAP, there are special SAP Notes containing information about the upgrade strategy. In the ADDON_INFO phase, the Software Update Manager writes the SAP Note numbers for your upgrade into the CHECKS.LOG file. The Software Update Manager lists the general add-on Note as well as, if possible, specific add-on upgrade Notes to the add-ons installed.

Before the upgrade, check all SAP Notes listed in the CHECKS.LOG file. If there are add-ons installed in your SAP system for which there is no information in one of the listed SAP Notes, refer to the add-on producer for information.

Mount Directories for Languages (Phase LANG_SELECT)

If not all necessary language archives are available in the download directory, the Software Update Manager prompts you now to mount the necessary directories of the language archives. You must do this even if only the standard languages English and German are installed in your system.

Provided that you have chosen the Expert Mode, you also have the option to exclude those languages from the upgrade of which the language archives are missing and that are not yet registered in the ABAP system. You cannot deselect already installed languages. They must be manually removed from the ABAP system beforehand.

In principle, it is possible to install additional languages during the upgrade. For more information, see Importing Additional Languages.

SPAM Version Check (Phase SPAMCHK_INI)

The Software Update Manager calls functions of the SAP Support Package Manager (transaction SPAM). For this, it checks if the level of the SPAM version on your source release is sufficient for the update. If your SPAM version is not high enough, the Software Update Manager searches for a higher version and installs it. If no higher SPAM version is found, the update stops with an error message prompting you to provide a higher SPAM update archive in the download directory.

For more information about importing a SPAM update, see the online help in transaction SPAM, or the SAP Help Portal for the corresponding source release at http://help.sap.com/spmanager,Support Package Manager    SAP Library    Importing Support Packages with Support Package Manager .

Decision About Add-Ons (Phase IS_SELECT)

The Software Update Manager determines all the add-ons that are contained in the SAP system and checks, which add-ons can be handled in the IS_SELECT phase. Moreover, it checks for which add-ons a decision has already been included in the stack configuration file of the Maintenance Planner, which you have entered in the SELSTACKXML phase. The add-ons that can be handled in this IS_SELECT phase and that have not been decided using the stack configuration file are displayed. These are, for example, all optional add-ons that are not part of the stack configuration file.

• Release upgrade only: Add-ons with default status INST/UPG WITH STD CD

  All add-ons that are included in the Upgrade Export archives and that you can update to a new release appear on the selection screen with default status INST/UPG WITH STD CD. For these add-ons, there is no need to make a new decision, unless you want to include a newer version of the add-on in the upgrade.

  Depending on whether the software components required by the add-on have to be kept the same or have to be updated, the add-on can also remain unchanged or may have to be updated. For this you have the following alternatives:

  • Source release SAP NetWeaver 7.0 only: Upgrade with SAINT packages (Upgrade the add-on with SAINT package).

    The packages have to be in the EPS inbox of the transport directory /usr/sap/trans/EPS/in.

  • Upgrade with an add-on-specific archive (Upgrade the add-on with CD/DVD)

    When you choose this alternative, you are asked to insert the corresponding CD or DVD. The data is copied to the SUM directory.

  • Upgrade to the version in the Upgrade Export archives (Upgrade the add-on to version delivered with upgrade DVDs)

    This alternative is only valid if there is an add-on in the Upgrade Export archive. Once you have chosen this alternative, you do not need any additional archives or packages for the add-on.

• Add-ons with default status KEEP YOURS

  All add-ons that you can take over unchanged appear on the selection screen with default status Keep yours. For these add-ons, there is no need to make a new decision, unless you want to include a newer version of the add-on in the update procedure.

  You can decide whether you want to keep this add-on unchanged, or whether you want to update it. If you want to update it, choose Upgrade the add-on using SAINT package.

  The packages have to be in the EPS inbox of the transport directory /usr/sap/trans/EPS/in.

• Add-ons with default status UNDECIDED

  These are optional add-ons that were installed on the source system. Decide how to proceed.

  For an add-on with status UNDECIDED, you have the following options in addition to the ones described above:

  • Keep the current add-on version (Use this option only if it is supported by the add-on vendor! A vendor key is required.).

    The add-on is transferred unchanged to the target release. If you choose this alternative, you have to enter a vendor key. Ask the add-on vendor beforehand whether you can use the key.

  • Keep the add-on as it is (Keep the add-on with your version).

    The add-on is transferred without any changes to the target release. You do not have to enter a vendor key. This option is only possible if the requirements of the installation of the add-on have been met.

• Deletion of Add-ons

  You can delete an add-on actively with SAINT package. This option includes a deletion package for the deletion of repository objects as well as for the deletion of table data of the add-on.

• Reset all decisions

  If you select option Reset all decisions and choose Continue, the system resets all the decisions that you have made. The system reinitializes the values and opens the selection screen for decisions about the add-ons again.

  If you want to continue with the decisions that you have made, choose Continue without selecting Reset all decisions.

Passwords for Add-Ons (Phase ADDONKEY_CHK)

If you use SAP add-on components in your SAP system (such as IS components), you are prompted for passwords. SAP systems that have other software components (add-ons) installed on top of them have to wait until the upgrade has been released by the relevant add-on software vendor.

Support Package Confirmation Check (Phase PATCH_CHK3)

This phase tests whether all support packages have been confirmed.

Unconfirmed support packages are displayed on the screen and in the PATCHOUT.LOG file that is located in the subdirectory log of the SUM directory. Confirm these support packages with transaction SPAM.

Release upgrade only: If the source release contains support packages that are more recent than those in the delivered target release, a warning appears that informs you which support packages these are. All software components appear whose support package level is more up-to-date than the status of the software components in the Upgrade Export archives.

If you use an add-on component, you can find information about including the corresponding add-on support packages or Conflict Resolution Transports in the SAP Note for the add-on supplement archive.

If the Software Update Manager displays a warning that your support package level of the source release is too up-to-date and you want to include the corresponding support packages of the target release, you have to do this in the next phase BIND_PATCH. You can include the support packages for multiple software components in this phase.

Including Support Packages (Phase BIND_PATCH)

In this phase, you are asked in a dialog for support packages. The dialog is normally available only when you have switched on the expert mode at the beginning of the update.

In rare cases, you might have to include support packages of certain software components, such as HR packages, because these packages have a shorter release cycle than the complete support package stack. For these cases, in the phase BIND_PATCH, you have the option to add the additional support packages to those that have already been included in the SELSTACKXML phase.

If you answer Yes to the prompt about including support packages, SUM displays a list of support packages in which you can select those that you want to include into the update.

You have to provide information about the support package level you want for your various software components. You can also include a SPAM update and single transport requests.

For this phase, we recommend that you also check the correctness of the support package levels of included software components. Note that only those software components are shown that are activated in the system.

For a complete list of imported software components, see the Using the SUM Analysis Feature utility.

It may take a few minutes to unpack the support package data.

If the release of a component does not change during the upgrade, the support packages previously installed for this component are automatically kept and do not have to be included again. Even another adjustment of the modifications contained within using transaction SPDD or SPAU is not required. You can also include additional support packages for this component.

To include support packages, proceed as follows:

1. If you want to include support packages for your various software components, answer Yes to the prompt about including support packages in the BIND_PATCH phase.

2. In the Selection column, enter the support package level you want for your various software components.

   Release upgrade only: Column Export Level contains the support package level delivered with the upgrade export.

   SPS update: Column Export Level includes the support package level that is already installed in the system.

   Column Minimum Level contains the minimum support package level required for a component to meet the import prerequisites of the included add-on packages.

   Column Equivalent Level contains the equivalent support package level. This is the support package level of the target release, which corresponds to the support package level of the source release. To avoid data loss, the support package level of the target release should not be lower than the equivalent support package level.

   Column Maximum Level contains the maximum support package level that can be included. The maximum level is set for some central components only (such as SAP_BASIS and SAP_ABA), for which support packages can only be included in the stack configuration file (stack.xml). For these components is no further support package inclusion in phase BIND_PATCH possible.

   Column Calculated Level contains the default support package queue, provided that it could be found or calculated. You can take over the queue by selecting field Take over calculated level in the dialogue.

   Column Target Level contains the highest support package level that is currently included. To find out the current state of the SAP system, the Software Update Manager checks the following support package level information:

   • Support package level that has already been installed in the source system. This only applies when the release of the SAP component does not change during the upgrade (component upgrade procedure).

   • Support package level that is delivered with the upgrade archives (for example, a support release level)

   • Support package level that has been included in the stack configuration file

   • Support package level that has already been selected and confirmed by the customer

3. Apart from including support packages, you can also include the latest SPAM update for the target release. This prevents any error messages caused by the SPAM update in the source release being newer than the SPAM version in the upgrade archive. It can also save you from having to import the latest SPAM update immediately after the upgrade. The Software Update Manager automatically looks in the EPS inbox for a current SPAM update and includes it automatically.

4. When you confirm the confirmation prompt, you integrate all support packages up to the specified level into the upgrade for this component.

It may take a few minutes to unpack the support package data.

You can include any necessary Conflict Resolution Transports (CRTs) in the upgrade. Any support packages that you cannot include in the upgrade have to be imported into the system after the upgrade.

Validation of the Specifications in the SUMASK*-Phases (Phase ADJUSTPRP)

That is, your specifications regarding automatic modification adjustments, single transport requests, and customer buffers are validated. If the validation has no errors, no further action is required and SUM continues the procedure. Otherwise, the corresponding dialogs are displayed again in which you can correct your specifications.