SAP Upgrade

Technical Upgrade & Enhancement Package Upgrade

SAP System

Current Version

For PCI Compliance

Comments

SAP ECC

SAP EHP3 for SAP ERP 6.0 SP2 on SAP NetWeaver 7.0 SP15

SAP EHP4 for SAP ERP 6.0 SPS14 on SAP NetWeaver 7.0 EHP2 SPS14

No Version upgrade. Only Technical (SPS)and Enhancement package upgrade

SAP PI

SAP NetWeaver 7.1 SPS8

SAP NetWeaver 7.1 SPS17

No Version upgrade. Only Technical (SPS) upgrade

SAP BW

SAP EHP 1 for SAP NetWeaver 7.0 SPS4

SAP EHP 1 for SAP NetWeaver 7.0 SPS14

No Version upgrade. Only Technical (SPS) upgrade

SAP SOLMAN SAP EHP 1 for SAP Solution Manager 7.0 SPS28

SAP EHP 1 for SAP Solution Manager 7.0 SPS31

No Version upgrade. Only Technical (SPS) upgrade

SAP System

Recommneded SAP EHP6 for SAP ERP 6.0 SPS9 on SAP NetWeaver 7.0 EHP2 SAP ECC SPS14 SAP PI SAP NetWeaver 7.4 SPS4 (Version Upgrade) SAP BW SAP NetWeaver 7.4 SPS4 (Version Upgrade) SAP SOLMAN SAP Solution Manager 7.1 (Version Upgrade)

Upgrade
Why does it take long duration for upgrades ?

 The actual implementation of support packages (and even support package stacks) is usually not a labor-intensive task. In fact, the technical aspects of implementing a support package stack should not take more than a day.

 A single support package contains, on average, about 400 notes and a support package stack contains around 8,000 notes. Some implementations span across several support package stacks and therefore translate to the implementation of tens of thousands of code corrections at once.

 When applying such a massive change to your code, the main challenge consists of assessing the impact of that change on the behavior of the system. By definition, notes are supposed to only correct bugs, but in reality they potentially create new problems by changing standard functionality, introducing new bugs, or, most commonly, causing custom code to fail.

 Consequently, support package implementation projects include extensive testing that is aimed at verifying the correct operation of the pre-implementation functionality and identifying any new problems introduced into the system. Not surprisingly, efficient testing was also selected as one of the key challenges in a support package implementation project by nearly 39% of survey respondents. In regard to implementation timelines, the survey shows that support package implementations require an average of 73 person days, with the majority of the effort (42 days) associated with testing.