Implementation Procedure

[Former Member]

Hi Gurus,

Plz. Tell me which all problems and testing will do in relization stage. I am having an idea on ASAP. Kindly note give some of u r problems and tests which will be done during this stage.One or examples please....................

Regards

Ravi

[Former Member · Accepted solution]

Hi,

In case of Rollouts/implementation projects following are the types of testing being done. (THough I am mentioning it from my company's perspective the testing may differ from company to company)

1. Unit testing: Done in the Development client. The behaviour of the transactions/ programs (RICEF ) etc. Basically it is done by the development / implementation team.

2. String testing/

It is done in the higher clients than Development. Usually the user departments are asked to create there own set of test data and test for each transactions functionality.

3. Regression Testing:

Before moving it to Production client it is done in Quality / Simulation cleint or server. Basically it is done to monitor the impact of peice of code or config changes on the existing functionality of the exixitng sites gone live.

Hope this summarises explaination to your query.

Regards,

Arshad.

[Former Member]

Hi Ravi,

In realization stage u did all configuration part like define sales orgnization and necessary configuration part. Once u complete configuration part then testing part will come to the picture in testing u will check ur trasactional data. U have different types testing like integrationa and unit testing.

Thanks & Regards

Sasikanth.Ch

[Former Member]

Hi Sasi

Thakyou for your reply. Will u please tell me in detail about tests and any examples if possible and is there any trouble shouting to be done.

Regards,

Ravi.

[Former Member]

Type of Testings:

• Configuration testing - The configuration testing ensures that all the requirements supported by standard SAP are properly configured and verified.

The main objective of the testing is to test the functioning of the individual SAP transactions after baseline configuration is completed and to identify any configuration related defects.

• Development Unit Testing - Development Unit Testing is performed for all the identified GAPs in requirements.

The objective of the Development Unit Testing is to ensure that the development objects are performing as per the requirement and design specifications.

• Interface Testing - The Interface testing includes the testing of the SAP interface programs, external interface programs and all related middleware settings.

The objective of interface testing is that the interface meets the technical and functional requirements and the data transfer requirements between the applications.

• Batch Testing - Batch testing tests that all the batch processes required are performing as per expectation and the scheduler is working as expected.

• Conversion Testing - Conversion testing includes the testing of the SAP data migration programs and all related middleware settings which will load the data from the existing system to the SAP system.

The objective of this testing is to check that all the developed conversion programs are performing as expected.

• Security Testing - Security testing ensures the SAP security roles and authorization based on the defined requirements.

• Regression Testing - Each time any new patch comes in or any fix has been applied in any of the system components, regression testing needs to be done to ensure that any changes applied to the system does not impact any of the existing functionalities or cause any undesirable results from the system. During multiple releases, regression testing needs to be done whenever a new release is installed to ensure that the new functionality does not impact any of the existing functionalities.

• Integration Testing - Functional Integration testing is performed to verify proper execution of the entire application including interfaces to external applications. This ensures that the integrated components of the configured transactions and the development objects for the GAPs are functioning properly according to the requirements and specifications.

The objective is to perform the end to end process integration between all the SAP components and all external application systems are functioning properly. Functional Integration Testing ensures that all the business scenarios have been tested prior to the User Acceptance Testing.

• User Acceptance Testing - User Acceptance testing is conducted in by a group of business end users in order to validate that the system meets requirements relevant to their functional areas. This testing will ensure that the system is acceptable from the user’s perspective and is performing as per the requirement as well as the expectation from the users.

• Performance and Load Testing - The performance testing is performed to verify whether the performance of each operation is as per expectation. The objective is to verify the response time of the transactions under different conditions.

• Backup and Recovery testing - This is to test the system backup processes. Also the restoration process is verified here.

• Cutover Testing - This testing is performed to ensure that all the required activities (Data Migration, quality check, manual update and data synchronization) can be completed prior to go live within identified cut over window. The objective of this testing is to ensure that the data conversion, dependencies of cutover activities and timing match with the cutover plan.

• Pre Production Testing - Pre-production testing is to verify that the application and its interfaces can operate in the production environment. Its focus is on the operational aspects of the system but not a thorough functional test but a subset of it.

This testing is generally the final part of a testing exercise prior to go live.

Regards,

Rajesh Banka

Reward points if helpful.