Professional Documents
Culture Documents
Document - Knowlege Sharing On Solution Manager PDF
Document - Knowlege Sharing On Solution Manager PDF
SAP landscape
• ECC Retail, ECC Industry, ECC slag, SCM, CRM, BW (HANA/ABAP), CAR
(HANA/ABAP), SLT, Enterprise Portal, NWDI
• Solution Manager 7.2 SP4
• Three tier system landscape + sandbox
• >4000 users
Statement: Process modelling is the foundation for control and measure of our solution, and
a common visual language between IT and Business
Solution Documentation
Coop Experience and learning points
General recommendations
- Recommend to upgrade to SP05 with possibility to define business process variants
- Identify the processes responsible to ensure ownership and continues maintenance
- Recommend numbering the defined processes as part of naming standard, for easier
reporting and search
- Define needed customer attributes from start to simplify the search and reporting (via
SOLMAN_SETUP)
- Use collaboration diagram in order to allow modelling of interfaces to third parties
- Define how the process can be measured and controlled (input to BPMon)
General experience
- Very good search and filtering functionality
- Experience that IE browser is slow to work with, Chrome is better but does not have the
edit online function for document handling
- Not possible to mass update (example attributes). Mass update comes in SP5 but not
stated what its used for
Solution Documentation
Coop Experience and learning points
• Scope: Upgrade all SAP systems (3xECC, BW, CRM, SCM, Portal, TREX, Java Hub, NDWI)
• Timeline: 6 months (April – October 2017)
• Facts: 38 systems upgraded, 130 involved people, 1766 manual test cases executed, 159
errors detected and corrected
TEST FASE PACKAGES TEST CASES NO IN PROGRESS ERRORS OK DEFECTS COMPLETION (%)
RESULT
SANDBOX (ST) 124 503 16 4 16 467 36 93
DEVELOPMENT (DT) 9 89 21 5 2 61 2 69
One of the key success factors was the preparation work, identify and secure test
coverage of critical business processes and related interfaces
Test Suite
High level Test flow
• Run BPCA to scope test • Test Execution via Tester • Test defect handling in ITSM
• Creation of Test Plan, Test Worklist
• Using Defect Correction in
Package and Test Case and • Test Note creation ChaRM (close link to test defect)
Tester assignment • Test Defect creation
• Creation of Test Reports
Test Suite - Test Planning
Test Experience and Learning points
Manager
Experience
• Nice integration with Solution Documentation, structure is maintained and well known
• Note that changes in test case (SolDoc) will not be visible in existing test packages, new test
package needs to be created and assigned to tester
• Missing mass update function of tester in test packages for Test Manager. Coming in SP05
• Good reporting possibilities (drill down in all levels)
• No experience with BPCA in 7.2 (not working for Maintenance Planner during project period)
• No experience in Test Case sequence, possible but not used
Learning points
• Decide on which level in structure the test plan and test packages should be created for easy
reporting and follow up
Example of report:
Test Suite - Test Execution
Experience and Learning points
Tester
Experience
• Tester recognize the structure in tester worklist from the process structure, which is good
• Too many pop ups/different windows when working with manual execution. Solved with Focus Build
• Test Cases opens in a separate window, not embedded as in 7.1. Solved with Focus Build
• Many refresh buttons under Tester Worklist. Needs to be refreshed manually
• Start Test Execution button makes sense if you have test case on process step level (Coops
decision to have test case on process level). Solved with Focus Build
• No experience in TBOM recording, decided not to use refer to statement above
Learning points
• Decide the use of Test Note and Test Result, and method (check in check out or upload new
version)
• Evaluate the available Focused Build solutions offered by SAP related to Test Suite (Simplified test
execution etc)
NEWS: Focused Build for 7.2 - New manual test solution with grid approach fully
embedded in Test Suite etc – link (slide 27-45)
Test Suite - Defect Handling
Experience and Learning points
Developer
Experience
• Nice follow up document integration between Test Defect (Incident) and Defect Correction
(ChaRM), text and field entries can be copied over
• No interlink when processing Test Defect and Defect Correction (Note: Coming). Developer
needs to work on both Test Defect and Defect Correction document when updating status etc
• No direct link to test notes from Test Defect, only link to test case (where actual result is blank)
• Note that Testers must go into ITSM in order to reply and confirm reported Test Defects (direct
link from tester worklist or mail notification)
Learning points
• Analyse the standard Defect Handling workflow and evaluate if customizing is needed
COMING: Status profiles for Test Defect and Defect Correction interlinked – link (slide 24)
Demo
SolMan 7.2 SP4