Important Note : we have less than 200No of users’ load on the SAP servers and thus we are going to use the HP tools in SMALL configuration and Very Minimum Nos of note more than 200 Nodes / Users. We all have a myth that all the custom implementations are lost during an upgrade project. The dates and time commitments of all EHP activities are. Please confirmīased on the above mentioned information, we are looking forward your support for recommending the best way to get proceed for moving the above servers into production environment only for the purpose of measuring the SLA as mentioned in the below table. SPAUENH : This tcode is a boon which has been introduced by SAP in recent EHP 7 version. EHP7 will consist of 3 plenaries, 5 touchpoints, 1 training bootcamp, 1 workshop, and 1 launch session.

I trust, this much information is helping you to understand the environment setup at our end. In case you are unsure about your environment, here are the steps to confirm the version from your SAP system: Use SAP GUI to connect to the SAP System. For example, SAP ECC 6.0 EHP 7 in general has NetWeaver version >7.4. Similarly, we have SAP ERP 6.0 EHP7 / NetWeaver 7.4 and its modules installed in various virtual boxes using VMWare ESXi 5.5, each of the SAP module is also having its own IP in the way we have mentioned above for HP module.Īlso Physically, all of the above mentioned virtual boxes are spread across 15 Physical Blade Servers on a single HP 7000 series Chassis. The version 7.01 or later refers to SAP NetWeaver version instead of SAP ECC version. We have separate virtual and separate boxes for each of the mentioned HP tool along with respective RDBMS installed.Ĭould anyone advise on how to proceed by moving the following setup into the production environment.

Ehp 7