Skip to Content
Author's profile photo Former Member

SAP Upgrade Project: Why All Interfaces Should Be Tested?

Organizations world over who have a SAP System as a business solution have either upgraded to latest version SAP ERP 6 or are in the process of doing so. The overall testing scope is determined based on combination of factors e.g. Prioritization based on identified critical transactions, GxP practices, Regulatory compliances etcetera.  The blog explores why it is important to test all the interfaces in an SAP Upgrade Project.

SAP Upgrade Project would involve creation of parallel landscape of Sandbox, Development, Quality and Production System. The present landscape of Sandbox-Development-Quality-Production system would continue to function till the time the new landscape is fully upgraded and project has gone live. The Upgrade would be applied first on the Sandbox or Development System of the new landscape. The screening and fixing of upgrade related issues would happen in upgraded Development System. Thereafter, the Quality System would be prepared and upgraded and upgrade related testing would be performed in upgraded Quality System. The new upgraded systems (Sandbox-Development-Quality-Production) are prepared for new landscape. On upgrade project go-live, the old landscape would cease to function and new landscape will go live. The System ID (SID) in new landscape would be same as was for the non-upgraded landscape. It is important to understand than upgraded landscape is built on new hardware (servers). Each of the Sandbox-Development-Quality-Production System is based on new server which would have new IP address. All the interfaces that were part of SAP Business solution would need of adjusted for this change. The various Interfaces types e.g. SAP-SAP, SAP-Non SAP System, Non-SAP System – SAP System, Direct DBCON etc. should be identified and adjusted for the IP addresses changes. The connectivity testing should be performed for upgraded Development, Quality system and should precede the formal quality testing. The Non-SAP Quality system should also be adjusted for new IP address, user id and password of target SAP Quality system. The change/adjustment are to be checked and performed in Development, Quality, Production system of upgraded SAP side and target or source SAP/Non-SAP Systems. Such an exercise is essential to give the confidence that because of new hardware migration the Interfaces are adjusted as relevant and would work as expected.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.