Test Preparation 20160727

Customer
SAP Solution Manager – Test Suite

Solution Documentation & Test Preparation
Digital Business Services, SAP SE
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP’s
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, included but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally of grossly negligent.
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 2
Test Preparation
Test Case assignment to Solution Documentation
Solution Documentation
• Documentation of Business Processes, Process Steps and
Executables (Transactions, Reports, Fiori, …)
• Assignment of Test Cases (manual, automated) to Executables,
Process Steps or Business Processes
Changes with SAP Solution Manager 7.2

• Executable Library generated from assigned managed systems
• Test Case (manual, automated) assignment at any level in
Executable Library, Process Step Library, Business Processes
• New attribute „Assignment Type“ with values „additive“ or
„exclusive“ to enable use of already assigned test cases assigned
to library nodes for Business Processes
Solution documentation
SAP Solution Manager solution documentation

SAP Solution Manager 7.2 comes with a  Web-based documentation experience
dramatically improved solution  Integrated BPMN process editor
documentation capability.
 Multi-level hierarchies (more than three)
 Processes assembled from re-use libraries
 Processes are validated and optimized continuously based
on real usage
Integrated process experience

 Requirements Management
 Project and Portfolio Management integration
 Change and Request Management integration
 Test Management integration
 Business Process Monitoring integration
Solution
Basics
The solution is the sum of a company’s systems,

applications and processes. It acts as a container System Landscape Processes
for versions of solution documentation, one of (and Applications) (and Libraries)
which is the production version.
Roles
 System
Solution
– Logical component groups are groups of logical components.
Sites
Logical components point to actual technical systems. Developments
 Process
– A process executes functions in systems to achieve a business Interfaces
goal.
 Version
– Each solution documentation version is a branch.
Branches
(Versions)
New Architecture in SAP Solution Manager 7.2
Concentrate on core
competencies.
The New Solution

The Solution is the sum of a company’s systems,
applications and processes. It acts as a container for
versions of solution documentation, one of which is the
production version.
Real Project Management

Replace “underdone” Project Management with full
Project Management Suite SAP PPM – integrated into
SAP Solution Manager processes.
Change Control Management

Establish central landscape definition with Logical
Component Groups and Change Control Landscapes
which allow easy, instant and multiple re-use capabilities.
Lifecycle based on Branches
Basics
A Branch represents a version of the The Production Branch represents the

productive version of the entire solution
solution documentation containing processes, documentation.
Production
libraries, and systems.
Maintenance Development
The Maintenance Branch represents the

editable version of the productive solution
documentation. It provides an safe
environment for performing changes.
Further Branches e.g. to
deliver the future solution
documentation.
SAP Solution Manager Integration Model
Best-Practice Approach for Branch Setup
Production branch
• Production branch represents the productive solution
Operations branch
• Operations branch to apply monitoring instrumentation
Maintenance branch
• Maintenance branch to change the productive solution
Innovation branches
• Import branch to import new best-practice processes
• Design branch to design customer target operating model
• Development branch to build the actual operating model
= Locked = Change controlled
Integrated Change Management & Solution Documentation
Requirements Management and ChaRM (Physical-) System Landscape
Request Transactions Tasklist

(Requirements Management) Triggers and
controls SAP CTS
Business
Requirement DEV QAS PRD
Transport
Request for
IT Requirement
Change
Change Documents Cycle Transactions Solution

(Change Request Management)
Production
Process
General Continual Cycle
Normal Change
Change Triggers and Process Step
controls the
solution
Admin Change Urgent Change Phase Cycle documentation Release
lifecycle.
Maintenance
Process ‘
… Release Cycle
Process Step ‘
Solution Documentation Model, Re-use and Referencing
Re-use and referencing

whenever possible is key
Process
to avoid redundant
documentation.
Processes
Process Step Originals
Executable Originals
Interface Configuration
Originals Development Originals Units
= Relevant for Test Management

Executable Library
Executable Library
Logical
Component • SAP_ERP
Group
ACH Folder • SD
ACH Folder • SD-SLS
This library contains executables

as well as the basic elements Executable VA01
 Test Case
relevant for Test Management like  TBOM
a generic functional test case and
generic TBOM assigned to the
executable (e.g. transaction
VA01)
ACH = Application Component Hierarchy
Processes Step Library
Process Step Library Executable Library

Logical
Folder Logistics Component • SAP_ERP
Group
Process Step Library contains Folder Sales and Delivery ACH Folder • SD
Steps to reflect a specific use

case or variant of an executable. Process
Step Create Sales Order ACH Folder • SD-SLS
The executable is referenced <Orig.>
together with the assigned VA01 VA01

Executable Executable
generic elements, but can be  Test
Case  Test
Case
enriched with use case specific  TBOM  TBOM
Test Case and TBOM •TBOM

Executable in Process Step Library
is a reference to the original
Executable in Executable Library
If TBOM (dynamic) is created on •Test Case including underlying elements
step level, referenced TBOM from
executable (semi-dynamic) is not = Referenced Assignment = Local Assignment (Original) ACH = Application Component Hierarchy
relevant.
New Solution Documentation - Business Processes and Libraries
Business Processes Process Step Library Executable Library

Logical
Scenario Logistics Folder Logistics Component • SAP_ERP
Group
Process Order-To-Cash Folder Sales and Delivery ACH Folder • SD
Process
Process Create Sales Order • SD-SLS
Create Sales Order Step ACH Folder
Step <Ref.>
<Orig.>
Executable VA01 Executable VA01 Executable VA01

 Test Case  Test Case  Test Case
Process Step in Business Processes
 TBOM  TBOM  TBOM
is a reference to the original Process
Step in Process Step Library
•TBOM including underlying elements Executable in Process Step Library
•TBOM
•Test Case is a reference to the original
Executable in Executable Library
VA01 •Test Case including underlying elements
Executable
Which Test Cases
•TBOM
are relevant now ?
= Referenced Assignment = Local Assignment (Original) ACH = Application Component Hierarchy
•Test Case
Local vs. referenced
New Solution Documentation - Business Processes and Libraries
New Attribute: Assignment Type
Business Processes Flexibility

• With the new concept of executable library, process
step library and business process it is possible to
Scenario Logistics assign test cases in various areas that allows re-using
test cases while avoiding redundancy.
• In the business process area test case can be
Process Order-To-Cash
assigned at process step, process and scenario level
Process Billing
Step <Ref.>
Control availability of test cases for test
Executable VF01 planning
 Test Case • With the new structure attribute Assignment Type it is
possible to control on each level if referenced or
underlying test cases should be available for test
•Test Case
planning or not
•Test Case
Use of local and referenced Test Cases on step level
Business Processes New attribute: Assignment Type
Scenario Logistics
Process Order-To-Cash
Use Attribute Setting Assignment Type for Process Step to control if referenced
Test Cases should be available for Test Management or not
Process Billing
Step <Ref.>
‘Additive’ ‘Exclusive’
Executable VF01 Test Case from referenced
 Test Case available not available
Executable
Test Case from referenced

•Test Case available not available
Step
•Test Case Locally assigned Test Case available available
Use of Test Cases assigned to Process and Process Step
Business Processes Use Attribute Setting Assignment Type

for Process to control if underlying Test
Scenario Cases should be available for Test
Management or not
Process Test Case
Process If Test Case Assignment Type has been set to ‘Additive’ on

Step 1 Test Case process level all test cases available from step level as well as
from process level are considered for Test Plan generation and
BPCA.
Process
Step 2
Test Case
Process
Step 3 Test Case
Use of Test Cases assigned to Process and Process Step
Business Processes Use Attribute Setting Assignment Type

for Process to control if underlying Test
Scenario Cases should be available for Test
Management or not
Process Test Case
Process If Test Case Assignment Type has been set to ‘Exclusive’ on

Step 1 Test Case process level only test cases assigned to process level but no test
cases from step level are considered for Test Plan generation and
BPCA.
Process
Step 2
Test Case
Process
Step 3 Test Case
Test Management
Assignment of Test Cases to Solution Documentation
Process Steps defined in Process Step Library with reference to executables from Executable Library and assigned Test Cases
Attributes allow systematic Test Planning

and Reporting
• Priority
• Status
• Responsible Person
• Test Classification to be able to distinguish

between different test types
• Duration (Expected Test Effort)
• Customer defined attributes

e.g. relevance for legal requirements,
organizational aspects
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Test Preparation 20160727

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Preparation 20160727

Uploaded by

Copyright:

Available Formats

Customer

SAP Solution Manager – Test Suite

Changes with SAP Solution Manager 7.2

SAP Solution Manager solution documentation

Integrated process experience

The solution is the sum of a company’s systems,

which is the production version.

The New Solution

Real Project Management

Change Control Management

A Branch represents a version of the The Production Branch represents the

The Maintenance Branch represents the

= Locked = Change controlled

Requirements Management and ChaRM (Physical-) System Landscape

Request Transactions Tasklist

Change Documents Cycle Transactions Solution

Re-use and referencing

Process Step Originals

= Relevant for Test Management

ACH Folder • SD-SLS

This library contains executables

Process Step Library Executable Library

Steps to reflect a specific use

together with the assigned VA01 VA01

Test Case and TBOM •TBOM

Business Processes Process Step Library Executable Library

Process Order-To-Cash Folder Sales and Delivery ACH Folder • SD

Executable VA01 Executable VA01 Executable VA01

Business Processes Flexibility

Business Processes New attribute: Assignment Type

Test Case from referenced

•Test Case Locally assigned Test Case available available

Business Processes Use Attribute Setting Assignment Type

Process Test Case

Process If Test Case Assignment Type has been set to ‘Additive’ on

Business Processes Use Attribute Setting Assignment Type

Process Test Case

Process If Test Case Assignment Type has been set to ‘Exclusive’ on

Attributes allow systematic Test Planning

• Test Classification to be able to distinguish

• Duration (Expected Test Effort)

• Customer defined attributes

National product specifications may vary.

You might also like