Documente Academic
Documente Profesional
Documente Cultură
This post will help you to prepare plan for upgrading your system.
Installation Check:
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.
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.
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.
Challenges
Risks
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. Meeting was chaired by the onsite/offshore PM.
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.g.
Go/No Go and Changes to the project plan / freeze periods. All
stakeholders of the project were invited to join the meeting
Governance Board:
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
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.
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:
Basis will be doing technical upgrade of the system. Involve POC right
from project kick-off and planning project activities.
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.).
Business must be involve to make sure availability of users for UAT.
Test Factory must be involve for regression testing
SAP Functional team must be involve for unit testing and functional
testing
SAP technical team must be involve to implement SAP notes, SPAU/SPDD
activities, bug fixing in functional testing/UAT/aftercare
Release Manager is an important participant to adjust system upgrade of
each system in continuation with regular/monthly activities
Prerequisites of EHP7:
SAP system must be well equipped before go-live. EHP7 brings loads of
additional functionalities to the existing SAP system. It creates considerable
reduction in the system response and generally contribute to system
performance. Make sure SAP system will be at latest software component
level. Go through the note mentioned below for further details.
There are several SAP notes available providing information about EHP7
package. Find below one of the note which is providing related information
about support packs.
1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note
Test script and Test users:
Make sure test scripts must be updated with the latest approved testing
process and test users must be having similar role as that of the business
users executing certain business processes . Make sure Test factory testing
script are updated.
Security and Authorizations:
EHP7 modifies authorization objects at some extent. Involve security and
authorizations team in planning study of changes in authorizations and roles
of users. There is a separate exercise must be done after implementing EHP7
in DEV system to find change s in the authorizations. A separate run book
must be prepared for S&A activity and merge in master run book and project
plan
SAP involvement:
OSS messages raised due to various issues during upgrade of DEV or QUA
takes time since SAP do not allow to keep priority High/Very High for nonproduction system. Involvement of POC from SAP helps is arranging
appropriate in-time support during non-production system upgrades.
Other third party interfaces or applications POCs must be involve during
testing of interfaces/portals etc. Project managers of the
other ongoing projects will help in prioritize activities.