Ask The CRM Expert: Questions & Answers

What's the testing process for an SAP CRM implementation?

What's the testing process for an SAP CRM implementation?

By  Srinivasa Katta, President and CEO, iServiceGlobe, Inc.

SearchCRM.com

Can you explain the testing process in an SAP CRM implementation?
Like any other project, implementing SAP CRM happens in phases. The general phases are:

1) Project planning
2) Blueprinting
3) Realization
4) Final preparation (Business validation, quality assurance (Q/A))
5) Go live and support

So the typical system landscape for SAP CRM, at the minimum, are:

1) Development system
2) Q/A system
3) Production system

Large and complex projects may have a sandbox system before the development system and a training system also:

1) Sandbox system
2) Development system
3a) Q/A system
3b) Training system
3c) Production system

The implementation team completes the construction of the application as per business requirements evolved in the blueprinting phase. Unit testing of application is done within the development system. Applications and programs that are successful after the unit testing will be transported to Q/A system. The busi

To continue reading for free, register below or login

Requires Membership to View

To gain access to this and all member only content, please provide the following information:

By joining SearchCRM.com you agree to receive email updates from the TechTarget network of sites, including updates on new content, magazine or event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile or unsubscribing via email.

TechTarget cares about your privacy. Read our Privacy Policy

ness super users and key users will do the end-to-end integration testing of the applications. The results of such testing will then be documented in an issue tracking system with the issue number, issue, issue description, application, issue priority (critical, high, medium and low) created by, created date, responsible owner, resolved date. The responsible owner will be notified via email whenever an issue is recorded in the issue tracking system. The owner of the issue will look into the issue and update the issue with the solution, resolved date. The responsible owner transports the changes from development to the QA system and notifies the person who created the issue. The tester will test the application and either closes the issue or report if any further issues noticed.

This continues until the application is robust and "bug free" from both functional and technical aspects. The successful application will be transported from development to training system for end user training and finally to the production system.