Resetting the Patch Status

Use

If you have to reapply a patch because errors occurred or a SPAM update is necessary, then reset its status.

Resetting the status does not mean that the system has the old status.

Procedure

To reset a patch or a patch queue, choose Extras ® Reset status.

Result

The corresponding entries are deleted in the cofile and in the log file after the status has been updated. You have to completely apply the patch again. Transaction SPAM starts the application with the step CHECK_REQUIREMENTS.

Displaying the Patch Status

Use

You can display the status of the patch application and the patch status of your system.

Procedure

Displaying the Application Status

To display the patch application status, choose Goto ® Status. A dialog pox appears telling you if the patch was applied successfully.

Displaying the Patch Status of the System

To display the patch status of your system, under Directory select one of the following checkboxes:

• New patches (have not been applied yet)
• Aborted patches (have not been successfully applied)
• Applied patches (have been successfully applied)
• All patches

A list is displayed with information about the selected patches. For more information on the patches displayed, choose View ® Change view.

Applying Patches to Other Systems

Requirements

1. The patches were applied successfully in a system (test or development system).
2. You have performed a modification adjustment (Transaction SPAU).

Procedure

1. Load the patches in the next system (quality or production system). You must differentiate between the following scenarios:

- Your systems have a common transport directory:

Release 3.x:

Run RSEPSDOL in the source system and RSEPSUPL in the target system.

Release 4.x:

In the target system, choose SPAM ® Patch ® Upload.

- Your systems do not have a common transport directory:

Release 3.x:

Run RSEPSDOL in the source system.

With the command ftp , transfer all the files with the extension *.PAT in binary mode and all the files with the extension *.ATT in ASCII mode from the source system directory /usr/sap/trans/EPS/in (UNIX) to the target system transport directory.

Run RSEPSUPL in the target system.

Release 4.x:

With the command ftp , transfer all the files with the extension *.PAT in binary mode from the source system directory /usr/sap/trans/EPS/in (UNIX) to the target system transport directory.

In the target system, choose SPAM ® Patch ® Upload.

2. Apply the patches as usual.
3. Import the modification adjustment transport.

Confirming a Patch Queue

Use

Confirm the successful application of the patch queue in your system. This ensures that other patches can be applied in the future. Another patch cannot be applied without a confirmation.

If you have not yet confirmed patches that were applied successfully, you will be asked to confirm these patches when the system is upgraded.

Requirements

You have successfully applied one or several patches.

Procedure

Confirm the successful application of the patch in your system by choosing Patch ® Confirm.

Applying a Patch Queue

Use

The SAP Patch Manager offers you 2 scenarios for applying patches and/or patch queues:

• Test scenario

Use the Test scenario before actually applying the patch or patch queue to determine if any conflicts or problems arise (for example, repairs that have not been released), or if a modification adjustment is necessary.

The scenario enables you to estimate and perhaps minimize the time and energy needed to apply patches. In this scenario, no data is imported into the system and if an error occurs, you can also continue the process without correcting the error.

You must choose the Test scenario explicitly.

Note that after the Test scenario has run, the patch queue is empty and must defined once again. Furthermore, you must explicitly choose the Standard scenario afterward.

• Standard scenario

In this scenario, the patches in the queue are completely applied. If an error occurs, you can only continue and end the application successfully if the error is corrected.

Requirements

The patch queue is defined.

Procedure

1. To choose the desired scenario, choose Extras ® Settings.
2. Choose the scenario.
3. Choose Patch ® Apply patch queue.

Standard scenario:

This function is also used to resume an aborted patch application.

The status line informs you of the progress of the application and the current steps of the SAP Patch Manager. During the application, you may have to perform a modification adjustment because SPAM deems it necessary (SPDD, SPAU). You must adjust the Dictionary objects (SPDD) immediately, whereas with the Repository objects (SPAU), you have the choice of adjusting them later on ( Modification Adjustment).

The session is blocked while a patch is being applied. To avoid logging on again, open a second session before you apply the patch.

Examples of Consistent Patch Queues

In the following section, you will find examples of consistent patch queues for SAP R/3 4.0B and SAP BW 1.2A:

• You have an R/3 standard system and are applying Hot Packages:

SAPKH40B01 (Hot Package 01)

SAPKH40B02 (Hot Package 02)

SAPKH40B03 (Hot Package 03)

SAPKH40B04 (Hot Package 04)

• Your system has FCS status and you are applying Hot Packages:

SAPKD40BXX (FFDP)

SAPKH40B01 (Hot Package 01)

SAPKH40B02 (Hot Package 02)

SAPKH40B03 (Hot Package 03)

SAPKH40B04 (Hot Package 04)

• You are using the Human Resources (SAP HR) application component and are applying LCPs:

SAPKE40B01 (LCP 01)

SAPKE40B02 (LCP 02)

SAPKE40B03 (LCP 03)

• You are using an add-on (without HR) and are applying Hot Packages:

SAPKH40B01 (Hot Package 01)

SAPKIPFB01 (CRT for Hot Package 01)

SAPKH40B02 (Hot Package 02)

SAPKH40B03 (Hot Package 03)

SAPKIPFB03 (CRT for Hot Package 03)

• The system is FCS and you are using an HR add-on and applying LCPs:

SAPKD40BXX (FFDP)

SAPKE40B01 (LCP 01)

SAPKE40B02 (LCP 02)

SAPKIDZB02 (CRT for LCP 02)

SAPKE40B03 (LCP 03)

• You are using the SAP BW application component ("12A" denotes the SAP BW Release 1.2A):

SAPKW12A01

SAPKW12A02

SAPKW12A03

SAPKW12A04