Implementation Scenarios for EHP2 and SP Stacks (Examples)
Starting on SAP ERP 6.0
Key Messages: Always: Combine installations of EHPs with updating your SP Stack SPS 10 SPS 10
Starting from ERp 6.0 SPS 08 or lower: Ideal starting position for EHP2 and EHP3! Starting from SPS 09 or higher: The lower the SP level is when installing an EHP, the more efficient this is for your maintenance activities. This means: Corrections already included in the system (e.g. installed with SPS9) are reinstalled. Possibly repeated SPAU effort. This refers to: all software component versions that are brought into a higher version through installing a technical usage.
SPS 10
EHP 2
SPS 09 SPS 08 SPS 09
SPS 12 SPS 11 SPS 10 09
SPS SPS12 2 SPS SPS11 1 SPS 10
SAP SAP ERPERP 6.0 (SPS 6.0 09) SPS 09 SPS 08 SAP ERP 6.0 (SPS 12) SPS 09
Implementation Scenarios for EHP3 and SP Stacks (Examples)
Starting on SAP ERP 6.0
Key Messages: SPS 11 SPS 10
EHP 3 EHP 2
SPS 11 SPS 10
EHP 3 xEHP 2
Always: Combine installations of EHPs with updating your SP Stack Starting from ERp 6.0 SPS 08 or lower: Ideal starting position for EHP2 and EHP3! Starting from SPS 09 or higher: The lower the SP level is when installing an EHP, the more efficient this is for your maintenance activities. This means: Corrections already included in the system (e.g. installed with SPS9) are reinstalled. Possibly repeated SPAU effort. This refers to: all software component versions that are brought into a higher version through installing a technical usage.
How are corrections of existing functionality included?
Whenever a customer patches his SAP ERP 6.0 system (with or without EHPs installed), he is always recommended to use the SAP Solution Manager Maintenance Optimizer. This tool automatically identifies the relevant installation files (support packages) according to the current system status and thereby ensures a consistent SP Stack level. Below some rules how the relevant files are identified: Installing an EHP means bringing a subset of software component versions (SWCs) to a higher version, e.g. from 600 to 603. With the installation of an EHP you reach a certain correction level. This corresponds (‘is equivalent’) to an SP Stack level of the underlying SAP ERP 6.0. Example: It is not possible to have EHP2 installed while remaining on SPS 09 or lower. The only efficient way to install the eventually missing SP stacks is to install these together and in one step with the Enhancement Package. Support Package for higher software component versions (e.g. for SAP_APPL 603) are independent from the Support Packages of lower SWC versions. It contains*: A) Corrections of functionality which came new with this SWC version B) Corrections of functionality which was already available with former SWC versions It is not possible to install only corrections of either A or B.
Comparison of Correction Levels with / without EHP – Detailed View (without HR components)
How are corrections of former versions included in the SP Stacks? Scenario: Customer patches his SAP ERP system
Starting position: no EHP installed, SPS12 Starting position: EHP3 installed, SPS1
EA_APPL 600
…
EA_APPL 603
…
SAP_APPL 600
SAP_ABA SAP_BASIS
SAP_APPL 603
SAP_ABA
Compare both installation stacks (Identified by the MOPZ) :
EHP3 SPS02 SAP_APPL 6.03 – SAPKH60302 EA_APPL 6.03 – SAPK-60302INEAAPPL … installation files include the same corrections as the files These on the left hand side plus corrections for the new functionality