Ehp7-Enhancement Pack 7 What Is Enhancement Pack
Ehp7-Enhancement Pack 7 What Is Enhancement Pack
data to end user for day-to-day operations such as the financial results for the
last two years.
SAP Upgrade from ECC 6.0 EHP4 to ECC 6.0 EHP7:
Pre-upgrade Activities must be done on the existing level of software to
understand impact on the basic software level. Another installation check should be
done to identify any critical issues that could lead to additional risks or work on
total number of custom objects /customizing to identify the impact of EHP7
enhancements on the existing custom transactions/reports
Study of Software components versions:
The component versions can be generated by Solution Manager System which
gives the overall components needs to be upgraded from EHP4 to EHP7 SPS3.
This can be done by SAP basis consultant using SAP Solution Manager. A list of
all the new versions of software components can be seen and selected before
upgrading to EHP7. Find below sample screenshots which show the components
selected that will be upgraded with new version.
Installation Check:
Installation check is the activity to must be done to understand if there are any
critical issues that could lead to additional risks or work when compared with the
average SAP EHP installation project.
This check can be done by development team or SAP support can be taken to study
and report the impact on the existing set of processes in the ERP SAP system. SAP
charges separately for doing such studies.
The objective of the SAP EHP Installation Check is to identify the most significant
risk and effort drivers for your planned project. For this purpose, it collects
technical information in your current production system and evaluates it based on
general experience obtained.
An action plan for the activities can be prepared based on the priorities on
identified risk and precautions before upgrade initiation.
Installation check will be baseline for estimations of the efforts required for
adjustment during upgrade of enhancement package.
Governance Board:
Governance Model Execution:
During the freeze period of upgrading SAP systems, there are two kind of
situations which can occur:
1. Aftercare issues ongoing projects
2. Production issues in operations
Governance board will work for smooth execution of these issues:
1. Aftercare issues:
Project Manager of the respective project must approach business,
Tech Lead/BA of that project an
operations lead in case of Change required and get the approval ready.
Then formal approval in Governance board meeting.
Project Manager of the respective project to connect with Release
Manager and QA officer for transporting changes/fix approved.
2. Production Issues:
Raise an incident in the ticket handling tool.
Corrective change/fix must be checked and Incident Manager/Service
Lead must approach Business and operational lead for approval.
Then formal approval in Governance board.
Service Lead/IM to connect with Release Manager for transporting
changes/fix if approved.
Lesson Learned and Recommendations:
Project Plan and Run book preparation:
All the stakeholders and involved parties must be involved while preparing project
plan. Most important activity is to gather run book from all vendors supporting
upgrade activity and merge into master run book and project plan. Get POC from
each of the vendors for interchanging information and involve in meetings.
Following contributors must involve for their respective responsibilities:
1. Basis will be doing technical upgrade of the system. Involve POC right from
project kick-off and planning project activities.
2. Security and Authorization team must take care of arranging user access for
Basis and other dialog and non-dialog users (system users, batch users, etc.).
3. Business must be involve to make sure availability of users for UAT.
4. Test Factory must be involve for regression testing
5. SAP Functional team must be involve for unit testing and functional testing