Professional Documents
Culture Documents
Below are the Source and Target Details during the ECC 6.0 EhP7 Upgrade for
our System upgrade
Source: ECC 6.0 EhP5
Target: ECC 6.0 EhP7
OS: Linux RHEL 6
DB: ORACLE 11.2.0.3
Prerequisites
Checking the Hardware Requirements
Checking the Software Requirements
Checking the Source Release of the SAP System
Meeting the Operating System-Specific Requirements
Upgrade of the Operating System and Database System if required
Checking the Software Update Manager Version, Please try and ensure that we have latest Tool
SUM 1.0 SP10
Checking the Software Delivery Manager Version
Checking the Structural Requirements for ABAP
Setting the Operation Mode for the Update
Checking the Number of Background Processes
Making Preparations in the Monitoring Area
Checking the Requirements for the Modification Adjustment
OS level user: SIDADM and ORASID, SAP level user DDIC password in all the clients should
be known prior to start and in 000 ,System user password is required for DB .
1639578,1547947 and 1622837 notes should be referred to setup the new DB connection
before the issue arises( - Secure connection of AS ABAP to Oracle via SSFS for removal of OPS$
mechanism)
Cleanup profile directory and only active and relevant profiles should be there , all the
backup profiles etc. should not be present and removed from the location, See SAP note 1649026 .
In case you are upgrading the second system in the landscape Import TR for SAP notes
001680583,0001678047,1609895,1861585 and can be imported before the upgrade and hence
you can skip this step during the SUM checks, else you need to implement the above mentioned
notes in DEV system and then generate a TR for the same. \
Get the number of Dialog and Background WP's increased and hence you can use the
NZDM option
SAP note 1387739 for ACT_UPG phase please refer options used during the upgrade.
You need to ensure that your present SAP kernel level should meet the criteria to use ssf
authentication.
1.
2.
3.
Determining the Host for the Preparations(If separate host for shadow etc.. )
Create New Table space with brtools named PSAPSR3740 of size 140 GB in advance
Use of NZDM (Configuration)
PSAPTEMP table space increased upto 20% of total DB size so as to avoid out of space in
TEMP.
If your installation is of type HA then please make sure that XML file generated from
solution manager contains the hostname of ASCS instance, else you will get an error while SUM is
trying to recognize the instance .
If Installation of SAP system is heterogeneous then please make sure that ASCS and CI
kernels are upgraded independently, SUM tool even will ask you for DB host OS incase of
HA/Distributed installation.
Challenges/Learnings
Setup of SSF authentication mechanism for WPs, before upgrade. As you need to complete
the preprocessing with ssf mechanism in place and system needs to be restarted and environment
parameters need to be implemented manually
Change in SAP Kernel path and hence you need to update /usr/sap/<SID>/SYS/exe/dbg link
to reflect to new path.Ensure that new kernel path is updated in <sid>adm and ora<sid> users for
all the systems , including App servers. If App servers are there then prefer to reinstall app servers
with latest SWPM.
Increase the shared memory parameters on Linux Kernel as below in the file
/etc/sysctl.conf and activate :
1.
kernel.shmmax=68719476736
2.
kernel.shmall=41943040
Posted by Satish Karemore in Satish Karemore's Blog on Jan 29, 2015 8:51:24 AM
inShare47
level. All features of SAP HANA can be utilized to speed up complex MRP
runs and capacity planning.
Data aging The use of data in-memory platform of SAP HANA can
be used for implement a data aging strategy efficiently. This can provide
near real-time data to end user for day-to-day operations such as the
financial results for the last two years.
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.
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. Once development upgrade is done in the landscape, a
detail check of modifies authorization object must be done by SAP security
consultant/team. 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 replanning 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.
Challenges
Enhancement pack 7 is the latest pack provided by SAP. Even SAP
doesnt have complete knowledge bank on the issues occurred. In our
case customer specific SAP notes had developed by SAP to resolve issues
in SAP standard code during technical upgrade.
Coordination with vendors for SAP security, Basis, EAI, Portals and
SAP for respective activities in different time zones.
Stringent timelines due to other projects based on business
priorities.
Governance of emergency changes and fixes.
Risks
Issues encountered during upgrade and testing in (DEV/QUA) which
might need structural fix
Delayed response from SAP in providing required solution since
issues are not in knowlege bank of SAP
Upgrading CTP to EHP7 brings additional risk due to older versions
of other systems in the landscape.
Existing projects, new projects and project aftercare issues can be
impacted during upgrade activities of productive system
UAT issues/fixes of the ongoing projects can be impacted during
upgrade activities.
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.
Governance Board:
1.
2.
1.
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.