Hands-On Lab: Leveraging SAP Solution Manager To Automate Testing and Streamline Your Next Enhancement Package Project or Upgrade
Hands-On Lab: Leveraging SAP Solution Manager To Automate Testing and Streamline Your Next Enhancement Package Project or Upgrade
Hands-On Lab: Leveraging SAP Solution Manager To Automate Testing and Streamline Your Next Enhancement Package Project or Upgrade
Page 2 of 57
Lab Overview
This lab is meant to give attendees an introduction to Solution Manager 7.1 and how customers can leverage the tool
during their next upgrade or Enhancement Package project. During this lab we will focus on the required steps to access
Work Centers, define a project to begin documenting business processes, execute an analysis within Solution
Documentation Assistant, create a Technical Bill of Materials, and access the Business Process Change Analyzer. With
this experience in a controlled lab environment attendees will begin to understand the effort required and the value
Solution Manager brings. This lab assumes the Solution Manager system has been minimally configured using
SOLMAN_SETUP transactions. And that attendees have a basic knowledge of SAP navigation.
Process Flow
Page 3 of 57
Information Sheet
Item
User Name
Password
SID
Client
Project Name
Value
<User>
<Password>
SM6
001
<User >
Page 4 of 57
9. Click the Scope tab and then select the Roadmap Select tab
Page 5 of 57
12. Click the Country tab to describe the country that your project includes
Page 6 of 57
Page 7 of 57
18. Navigate to SAP ERP > SAP ECC SERVER and select Z_NW702_ERP6
19. Click the Green Check
Page 8 of 57
Page 9 of 57
26. Type /n in the command field and press Enter to return to main menu
button
Page 10 of 57
Page 11 of 57
8. Next, enter Scenario Name for your business process under the Structure tab
a. Example: LABUSER01 FI Processes
9. Press Enter and click Save button
10. We must save after every change within the Structure tab
11. Expand the Business Scenario you just created down to the Business Processes level
12. Click on Business Processes and then click the visual assist button under Process Name
13. Verify the Source is set to Business Process Repository
14. The Business Process Repository can take up to five minutes to load. Be Patient.
15. Navigate to a functional area that you would like to add from the Business Process Repository
a. In this example I have select Financials > Accounts Payable > SAP ECC 6.0
16. Click the Green Check to continue
Page 12 of 57
Page 13 of 57
19. Return to the Business Processes node and select the Structure tab
20. Now we will add our own business process by entering a value in the Process Name column
a. Example: LABUSER01 AP Processes
21. Press Enter and click the Save button
22. View your business process on the left
23. Next, we will copy from the Business Process Repository to our custom business process
24. Highlight a Business Process Step from the Business Process Repository content you added and click the Copy
button
25. Then, highlight your custom business process on the left and click the Paste button
Page 14 of 57
27. When prompted to Specify how the following data will be handled select the following options
28. Expand the custom business process you created and verify you see the copy
Page 15 of 57
29. Use the Structure tab to rename the copied business process. Press Enter and click Save.
Page 16 of 57
Page 17 of 57
4. Ensure your project is displayed by verifying the title at the top of the screen.
5. Navigate to Business Scenarios > LABUSERXX - Process > Business Processes > LABUSERXX Business Process >
LABUSERXX Business Process Step
a. The lowest level of you project should be a business process step
7. When prompted to edit the document, enter some example text. Click the Save
9. Verify your document was created by highlighting the row and clicking Display
Page 18 of 57
Page 19 of 57
10. Next, check the document out to your Desktop by select the Check In / Out button
11. Keep in mind in order to check the document in it must be checked in from the same location the document
was checked out
12. After you have checked the document in, click the Save button on the project
13. Type /n in the command field and press Enter
14. Return to SOLMAN_WORKCENTER
Page 20 of 57
5. Click Next
6. Leave the default values in the Define Profile screen
7.
8.
9.
10.
Select the business processes you would like to search for on the target system
In this demo you can leave the default all should be selected
Click the Create button
Verify the results in the Summary screen and close the browser
Page 21 of 57
11. Return to the Work Center and click the link on the lower right to refresh
12. Highlight your Analysis Project and then click the Create button under Analyses
Page 22 of 57
Page 23 of 57
15. Select the logical component Z_NW702_ERP6. Deselect any other logical component that may be displayed.
Click Next.
16. Verify the system ECD client 100 is displayed. Click Next.
17. Select the previous month for the workload period. Click Next.
Page 24 of 57
20. Click Create and view the summary. Close the IE browser.
Page 25 of 57
Page 26 of 57
23. Click the Analysis you executed and this will open an IE browser
24. When you open the Analysis Results, you will see either a red or green light next to the active business
processes
a. Red = transaction or report was not run during the analysis period
b. Green = transaction or report was run at least once during the analysis period
25. You can further explore the analysis by selecting the Object Usage tab
a. The Analysis tab displays what transactions we searched for
b. The Not in Analysis tab displays the transactions that were executed on the system
c. The Graphics tab visually displays how often specific transactions we executed
Page 27 of 57
Page 28 of 57
3. Navigate thru your project to a Business Process. Here we will add our own Business Process Step
a. Remember A Business Process Step is the transaction, report, background job, or interface that is
executed
4. From the Structure tab, enter a description for your Business Process Step and select the Logical Component
Z_NW702_ERP6
5. Click Save
6. Return to the Implementation / Upgrade Work Center
7. Highlight your project and select Goto > Configuration
Page 29 of 57
10. In the grid row, select the drop down under Type and choose Transaction
11. In the object field, enter a transaction code for something we can execute as read only in ERP
12.
13.
14.
15.
Page 30 of 57
16. Next, highlight the grid row for your transaction and click the Attributes
18. Verify the TBOM Reference Client and accept the default description
button
Page 31 of 57
19. Press Enter and this will launch the transaction in that target system (in this example an ERP system named
ECD)
20. Now run thru the transaction as you would if you were a user
Page 32 of 57
Page 33 of 57
2. Select the radio button for Support Packages / Support Package Stacks
3. Input the system and client where a change has already occurred
a. System ECD
b. Client 100
4. Enter your Project ID
5. Enter in an Analysis Description LABUSERXX BPCA 001
6.
7.
8.
9.
Page 34 of 57
10. Now that we have the list of transports to compare against our project we can click Run
12. Scroll down in the BP Change Analyzer Work Center to view the analysis status
Page 35 of 57
Page 36 of 57
13. Click Refresh on the lower right to refresh the results grid. The job will take 5-20 minutes to execute
depending on the number of support packages included in the comparison
14. When the job completes, it will display the results below. If the transaction you added would be affected by the
Support Packages selected it will be highlighted below.
Page 37 of 57
9. From the list of results, highlight the desired project by clicking on the appropriate row
10. Choose the Configuration button to access the Configuration transaction
11. In the Configuration Structure on the left side of the screen, drill down to the level where you want to assign the
test case.
Example:
12. To assign a test case to the Post Down Payment Required process step of our sample project, choose:
Business Scenarios Financial Processes in ERP Business Processes Accounts Payable Post Down
Payment Required
Page 38 of 57
15. In the Add Document dialog box, specify you want to create a new document. It is also possible to upload an
existing test case document by selecting the appropriate radio button
16. Enter the Title of the document to be created
17. In the Documentation Type field, select the option Test Scripts
18. Confirm your entries by choosing OK)
Page 39 of 57
21. Fill in the template with the appropriate instructions and information
22.
23.
24.
25.
Page 40 of 57
Page 41 of 57
5. In the content area, click on Test Plan and choose Create Test Plan from the context menu
icon to proceed
Page 42 of 57
Page 43 of 57
11. On the test plan creation screen, choose the Expand All pushbutton
to expand the Test Plan Structure on
the left of the screen
12. In the Test Plan Structure, select the test cases that shall be in scope of the test plan
13. Once you have defined the scope, choose the pushbutton
14. In the Create Object Directory Entry dialog box, choose Local Object. You will automatically be returned to
the Test Plan Management area within the Test Management work center
15. Choose the My Test Plans query
16. Click on Refresh to refresh the active query. The test plan you have just created is displayed in the table.
Page 44 of 57
17. In the Test Plan column, click on your test plan. The Test Plan Attributes screen opens.
18. Choose the Change pushbutton
19. In the System Role field, make sure the correct entry is selected. The system role defines which system is used
as the system under test.
20. Select the Workflow Active checkbox to enable the workflow function for your test plan
21. The workflow functionality can specify and start actions at specified events in the test management process or
during testing. Sending an email is the default value. When the Workflow Active checkbox is selected, automatic
e-mail notifications are sent to the relevant testers when packages are assigned to them or the status of the test
plan changes.
22. Change the Status to NEW.
Page 45 of 57
Page 46 of 57
Page 47 of 57
9. Select the nodes that are relevant for your test package
10.
11.
12.
13.
pushbutton ( ).
14. In the Create Object Directory Entry dialog box, select custom package ZSOLMAN
15. You will receive confirmation of the test package being generated
Page 48 of 57
Page 49 of 57
8. In the User field, enter the user name of the tester to whom you want to assign the test package.
9. Choose Continue
Page 50 of 57
11. Once a test plan is released, the test packages that are included in the test plan can be executed by the assigned
testers
12. Back at the Test Management Work Center, Highlight the desired test plan.
13. Choose Goto Attributes. The Test Plan Attributes screen opens.
14.
15.
16.
17.
Page 51 of 57
18. The test plan is released and thus no longer locked for test execution
19. If the Workflow Active checkbox has been selected, email notifications are automatically sent to assigned testers
to inform them that their test packages are available and ready for testing.
Page 52 of 57
Page 53 of 57
9. In the Test Case Description column, click on the Test Document icon
for the desired test case to open the
associated test case description
10. In the Test Object column, click on the transaction name to call up the transaction in the system under test
11. To execute test, click on the Run pushbutton in the Assigned Test Cases section. This will bring up the Manual
Test Case screen.
Page 54 of 57
12. Click on Start Execution to launch session in the managed system under test
13. Enter Login credentials and then execute the transaction
14. After you have performed the test, choose the Exit pushbutton
to quit the transaction in the system
under test
15. Change status for test case to OK if the test was successfully complete
16. In the Test Effort field, enter the amount of time required to complete the test
Page 55 of 57
Page 56 of 57
18. If problems occur during test execution and the test cannot be completed successfully, you can create a test
message, which is automatically linked to the relevant test case.
19. If the test fails, assign the Status Errors. Retest Required and click on the Messages tab, and then click Create
Page 57 of 57