This content is available to Premium Members. Upcoming Events. Your request has been successfully sent. This website uses cookies. If you continue to use the site you consent to our use of cookies in accordance with our Cookie Policy. He applied EHP 3 to all possible modules in the system whether we are using it or not. Is there any negative impact to the modules we are actually using? Is it not a requirement for EHP4 to install all of the modules?
Should I have him tied to a tree and flogged for doing the wrong thing, is there no major impact? Regards Julius Like 0 Share Right click and copy the link to share this comment Dominic Thompson July 30, at am We only update once a year and we are at erp 6. This year we want to go to erp enhp 4 stack 4 when it comes out. My basis team is asking are we suppose to put the enhancement pack on all of the components or do we pick and choose which ones to enhance when installing. Or my understanding we would install in on the entire erp and turn on what we decide to turn on.
We wouldn't want all the components at different levels, would we. Even your blog states to install only what we need. What does that mean exactly.
You can always install more later on but once you have installed components you cannot uninstall them any more. The presentation explains the two strategy "Selective installation" and "Broad installation".
None of it suggests you to completely install all of the components. When you do the Selective Installation, you select the technical usages based on the business functions that you want to activate later on in the system. On the other hand, when you do the Broad Installation, you select the technical usages that fit best for the company and for the use of the system HCM for an HR system for example. You choose the Broad installation if you do not know which business functions you are going to activate later on.
But still with the Broad installation strategy you select only a limited number of technical usages. Best regards, Joachim Like 0 Share Right click and copy the link to share this comment Eduardo Gironas September 4, at pm hello: I need to upgrade 4. Before receiving the services of a consultant I need to write some terms of reference. Between other documents I read the yours, but I have terrible confusions in new upgrade terminologies and technologies, for example: 1 upgrade using SAP NetWeaver 7.
If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy. See our Privacy Policy and User Agreement for details. The SlideShare family just got bigger. Home Explore Login Signup. Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. Sap enhancement package concept. Upcoming SlideShare. Like this presentation? Why not share! Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Next SlideShares. I nstallation 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.
SAP charges separately for doing such studies. For this purpose, it collects technical information in your current production system and evaluates it based on general experience obtained. The table below shows the most critical risk and outlay drivers for any software change project grouped by key focus areas. An explanation of the key focus areas can be found in the upgrade white paper of the SAP standards for solution operations.
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. Security Authorization Check. Enhancement package impact on the security and authorization objects of the end users.
This activity will mitigate further risk of authorization issues after production upgrade. The transports of the security adjustment must be transported just after upgrading quality or production system.
Test Factory for SIT:. Test factory must be involved for SIT in project planning to avoid re-planning or any impact the go-live date. Test factory do not always have all the domain knowledge to be able to execute a full SIT. If test scripts are not ready or up-to-date, it could cause adverse impact on the project timelines. Its is highly recommended to execute knowledge transfer to test factory for the areas where they are currently lacking the knowledge of the upgrading system.
There involvement during start-up of the project will help in the efficient project planning. Test Factory can execute Regression Testing on the upgrading system as a part of regular monthly release. SAP Quality manager must be involved right from kick-off of the upgrade.
This is a paid service of SAP and must be arrange in advance to avoid unexpected delays in project timelines due to software issues during upgrade.
Challenges and Risk:. Communication Protocol:. Communication plan must be prepared and approved before actual execution of the projects from IT and business. Daily call — There must be daily call on every working day with the project team along with client IT team. Use Run book to review the status on a daily basis. Governance Board call — It must be a bi-weekly call. All stakeholders must be invited to join this meeting. It should always starts with a brief status update on upgrade project.
A tracker would help to track these changes along with transport list. Lessons learned call — At the end of each major project stage, a lessons learned call must be scheduled to capture the lessons learned in the lessons learned log. Ad-hoc call — Calls when important decisions need to take place e. All stakeholders of the project were invited to join the meeting. Governance Board:.
0コメント