Skip to Content

SAP Solution Manager is a centralized management system that provide technical support for distributed connected systems (systems which are located far from each other) — with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. It is a gateway providing tools, content, and direct access to SAP to increase the reliability of solutions providing more flexibility and also lowering the total cost involved.

Testing — SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests. Thus, a test plan management is designed for the project. The main purpose of Test Plan Management is to defined Test Plans, organize them and perform testing within an SAP Solution Manager Project .In the Test Plan Management, Test Cases are recognized from the Business Scenario, Compiled into a Package and allocated to a Tester for Testing.

A Test plan is a set of test cases which are to be tested in a particular period for a particular purpose. A test plan is based on one or more test catalogs. A test plan comprises the test plan structure and the test plan attributes. Test plan attributes are for Test Plan Management. When you create a test plan for a project, the default test plan structure is based on the structure of the Business Blueprint which you have previously created for your project.

Here SMDEMO project is created to serve the purpose.

 First Step: Assignment of Test Cases to the Project Use The Test Cases are defined here and later used in the Test Plan Generation as per requirement.

  • Start the SAP Solution Manager Configuration transaction (SOLAR02).
  • Make sure that the correct project SMDemo is selected, otherwise change it using the Test plan option available in the menu bar.
  • Navigate to Business Scenarios –> Responsive Replenishment –> Business Processes –>Sales Order Processing for Responsive Replenishment–>Process Sales Order.
  • On the right side window, select the Test Cases Tab

image

Save data and go back.

 Note: Here only CATT test cases are shown depending upon the requirement, ECATT, Manual test etc can be selected as shown in the figure. The Project SMDemo comprises of business scenarios as shown on the left side. Remember either SAP provided or user defined both test cases can be provided here depending upon your requirement.

 Generation of Test plan

Open the transaction STWB_2 or go to Test Plan Management The Test Plan Creation or changing the existing Test plan or Deletion is to be done from this screen. Provide a name say Z_TPL_INT_DEMOTESTPLAN,

image

Click the create button or Select the create option from test plan from the menu.

image

Select copy transaction check box.

image

By default all the Business scenarios are selected and provided here.Also,notice the change on left side under process order with general transactions like create sales order, change sales order and display sales order there is also extra line coming above them Testing for creating, changing & Display sales order.

4. Click the generate Test Plan button and save it in development class. For demo it is saved as local object. Creation of Test Packages Use Test Cases are combined a package for simplicity for the tester in a Test package; which is also a period-oriented view of a test plan. It contains all tests which a tester is to perform in a specified period. Move to Tcode “STWB_2”, select the name of test plan as created. Now click Test packages tab.

image

image

 

 During creation provide a name for the test package also select the scenarios as per requirement. Extensive tests are usually performed by several testers; Basically, divide the test cases in our test plan into test packages which are work lists for a tester. We can assign a test case to several test packages.

Finally, the test package is assigned to a tester. NOTE: Experience personal can show his intelligence here as he can make CRM package comprising of CRM test cases and later allocate them to CRM Tester similarly for R/3 ABAP related test cases to the concerned tester etc. Assignment of Test Packages To a Tester Use From the same screen of Test Plan Management or tcode STWB_2 just click test packages and select any test packages .Here Z_Process_sales_order is selected and then click Assign tester.

image

Even if F4 is used it will show the name of all ID List .Select the ID of desired tester. After selecting the same just check that node or expand it the name or ID selected will come under that. Status Analysis of Test Plan Use From the same screen of Test Plan Management or tcode STWB_2 just click Status analysis and select any test packages if you have created more than one .

The beauty of this product lies in the fact that you can run all the transactions or test cases from solution manager this screen only (only,RFC must be properly maintained). Even the ECATT test cases are run and you can select all also to provide flexibility of running all the test cases once. From this screen, Information of thousand words can be seen, What are the test cases? What are the test packages? Which test case is assigned to which tester? How much he has completed? What is the current status of any test case? Logs are created for automated test cases like ECATT and CATT. Also for Manual user can update its status as well as send message notification.

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

      1. Anonymous
        Hello James,

        Following are some common Tcodes available,
        Solar_project_admin->>>>>For Project Administration
        Solar01—>>>>>>>>>>>Business Blueprint change
        solar02———>>>>>Config change
        Stwb_2———>>>>>>Test plan management
        Solution_manager->>>>Service desk

        These are widely used common Tcodes for creating and administrating project.

        (0) 
      2. Anonymous
        Hello James,

        Following are some common Tcodes available,
        Solar_project_admin->>>>>For Project Administration
        Solar01—>>>>>>>>>>>Business Blueprint change
        solar02———>>>>>Config change
        Stwb_2———>>>>>>Test plan management
        Solution_manager->>>>Service desk

        These are widely used common Tcodes for creating and administrating project.

        (0) 
  1. Ravindra babu Immadisetty
    Hi Prakar,

    This blog helped me lot,in doing the Testing I am facing one issue. I build multiple test cases in a package and executed in Automated test. It is creating all the test cases, log is created online. After that I went and saw through testplan, only the first test cases is showing the log ( ex.Sales Order No). But for other test caeses it is mentioning the log no, but it is not displaying the document no (ex.Material no created through MM01).

    Thanks in advance.
    Regards
    Ravindra Babu

    (0) 
    1. Anonymous
      Hi Fr,

      The solution for this is to create a parameter for material no…secondly it is better to have one more script for mm03 after mm01 script.

      When you add these two script adv is
      the first script create a material and transfer the no to other one using param
      and secondly …second uses the same and you can check the values are properly filled in.

      Regards
      Prakhar

      (0) 
  2. chaitanya nagalla
    the blog was really very nice. we have successfully created teh project but the lower level nodes are not getting displayed for proceeding further.

    Please share the document to create the SMDEMO project.

    (0) 

Leave a Reply