AddOn Installation & import support packages

AddOn Installation

Protect4S is delivered as a SAP Addon and must be applied through the usual AddOn installation process using transaction SAINT in client 000 of the relevant SAP Solution Manager system.

New Protect4S Installations require the Protect4S40 base package plus the latest Protect4S Support package. These can be installed in a single SAINT queue.

Support packages are non-incremental (they contain all predecessors) and can be merged into the installation queue.

(See SAPHelp : Installing and Upgrading Add-Ons)

Afterwards, the installation Post-processing must be executed via transaction /n/ESEC/SA_PI.

Importing Support packages

When Protect4S is already installed and you want to update to the newest Support Pack you can use the regular SAP transaction SPAM in client 000 to import the most recent Support Package. The software can be obtained via https://protect4s.com/downloads with your personal user-ID. If you don't have one please reach out to support@protect4s.com for assistance.

Keep in mind that the Protect4S Support Packages are non-cumulative, so you just need the latest SP as it contains all previous functionality as well. Support packages for Protect4S 4.0 can only be installed after the initial Protect4S 4.0 package is installed.

Important: After having imported the latest support Package make sure to run the Post-Installation wizard via transaction /n/ESEC/SA_PI.

Upgrade from Protect4S 3.x to 4.0

Protect4S 4.0 is a new major version that can be installed newly or over the existing 3.x installation using transaction SAINT in client 000. Support packages for Protect4S 4.0 can only be installed after the initial Protect4S 4.0 package is installed.

Please Note that for Protect4S version 4.0, first OSS Note 2752858 needs to be applied in the Solution Manager System when applicable.

For the prerequisites for Protect4S 4.0 see the Chapter Software version requirements.

Afterwards, the installation Post-processing must be executed via transaction /n/ESEC/SA_PI in the productive client.