openSAP Solman2-1 Week 2 All Slides

Week 2: Explore Phase (Process Expert/Analyst)
Unit 1: Introducing Solution Documentation

Introducing Solution Documentation
Process flow Focused Build – Requirements-to-deploy
Create project ▪ Manage waves and sprints Manage Q-Gate Hand over ▪ Project plan
PMO ▪ Track project readiness, issues, and risks deliverables, release to
plan ▪ Manage scope change sign-off customer ▪ Release, waves, and sprints
Fit / Gap ▪ Process model

Business WS for ▪ Application landscape
Process Owner requirements ▪ Requirements and gaps
Assign work ▪ Functional specification

Solution Create work items & build Manage
package show & tell ▪ Config. guide, test cases
Architect teams ▪ System landscape
Build Team Develop, Document Release work Defect ▪ Tech. design paper
(Developer, configure, unit work item &
test progress item correction ▪ Dev. objects in transports
Consultant)
Test Plan & Manage ▪ Test request

execute SFT,
Manager FIT, UAT, RT defects ▪ Test plan
Release Build, test and Manage

deploy release hypercare ▪ Release
Manager
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Responsibilities and outputs by role
Process Expert /
▪ Project roles: process expert, business analyst, test case designer, subject matter expert Business Analyst
▪ Responsibilities:
– Accurately represent their business units’ needs to the project team, validate the deliverables
that describe the product or service that the project will produce
– Work with users to ensure the project meets business needs – training staff as needed
– Functional expert documenting business processes
– Participate in Fit/Gap workshops
– Documentation and analysis of current and future
processes/systems
– Document requirements
– Design and execute user acceptance tests
▪ Outputs:
– Process description
– Definition of business processes BPML
– Application landscape
– Documented requirements and gaps

What is a solution in SAP Solution Manager?
Solution
Branches
Production
PRD
Operations
PRD Development
Standards Scopes
DEV & QAS
Maintenance
DEV & QAS
Design
Sandbox
Import
Sandbox
Solution
Documentation
Change Control Sites

Landscape
System Landscape

One process landscape for business and IT
Libraries help to re-use documentation elements to avoid redundancies
Process
Processes
Process Step Library
Executable Library
Configuration
Interface Library Development Library
Library

Documentation templates in Focused Build
Minimum documentation
Process
standards and their typical usage: Processes
Business process description

Functional specification type WRICEF
Process Step Library
Functional specification type Interface
Configuration guide
Executable Library
Technical design
Functional integration test case description Interface Configuration

Library Development Library Library
Single functional test case description
SAP Solution Manager allows to define document standards by central definition of document types,
their templates, allowed usages, and completeness rules.
Branches
Production
▪ Production branch PRD
− Production branch represents the productive
solution (incl. systems and processes)
As-is solution As-is solution

▪ Innovation branches
To-be solution To-be solution
− Import branch to import best-practice
processes Development
− Design branch to design customer target DEV & QAS & PRE
operating model and processes Design

− Development branch to build the defined Sandbox or DEV
operating model, processes, and systems Import
Sandbox or DEV
Innovate & Enhance & Fix

= Locked = Change controlled

Solution documentation UI in SAP Solution Manager
Global Functions
Column Browser
(Structure)
Attribute Pane
(Attributes)
Elements List
(Object assignments)

Demo

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2021 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.
The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP 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 platforms, 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, and they
should not be relied upon in making purchasing decisions.
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. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Unit 2: Using Best Practice Content from SAP Activate
Using Best Practice Content from SAP Activate
SAP Activate for SAP S/4HANA

SAP Model Company
Accelerators Engineered Service

Configuration and how-to guides, test Handover and enablement workshops
and demo scripts, implementation tools to jumpstart discovery, exploration,
and realization
Business Content Preconfigured Solution

Business process hierarchy, end-to-end Available as a ready-to-run appliance,
scenarios, process diagrams by roles incl. incl. all applications, configuration,
process steps sample data
Foundation
Activate + Industry Reference Architecture + Digital Business Framework

SAP Model Company
LoB or Industry-
Specific End-to-End
Business Scenarios
Configuration
LoB or Industry- Guides
Specific Process
Hierarchy
Configuration Test Cases
Best Practice Configuration Configuration Test Cases

Processes Guides

Example: scenario diagram/processes of SAP Model Company for SAP Oil & Gas
Navigate to SAP Model Company system

Review best practice content in the Import branch
Analyze best practices business processes including documentation, test cases, executables,
and configuration
One process
Go to Business Process steps
per scope item
Processes
All available documentation Default import

can be found in the elements folder One scenario per
of the process including: imported package
▪ Diagram
▪ Links to other diagrams
▪ Link to process
documentation including
BPD (business process
description), test cases,
and configuration guide
▪ Assigned building blocks
for activation

Release scoped processes from Import to Design branch
Production Scoped processes are

PRD released to the Design
branch
As-is solution As-is solution

To-be solution
Development
✓
✓
Design ✓
✓
Import
Processes are moved to
Innovate the correct folder and
should be renamed

Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Business Process Modeling
Business Process Modeling
Principle
Process Hierarchy
Process hierarchy and process diagrams

are two sides of the same coin.
They are managed as a whole.
Process Diagrams

Definitions
A process is a set of logically related activities performed to achieve a defined business outcome
Modular processes
▪ Flow of activities restricted to one functional domain
▪ Do not exceed the functional domain of an organization
▪ One process owner for the full process
End to End processes

▪ Comprehensive flow of activities needed to solve large business matters across organizations
▪ Do not stop at the boundaries of an organization and involve multiple functional domains or
systems
▪ Share process responsibility
▪ Are built from re-useable process steps and interfaces

Example: Modular processes with SAP Model Company content

Example: End-to-end processes with SAP Model Company content

Process definition vs process diagram
Process diagrams are tailored to specific needs One process

▪ End-user perspective versus definition
▪ Implementation perspective versus

▪ Business process monitoring perspective
One process definition, multiple

tailored diagrams
Multiple
diagrams

BPMN 2.0 in SAP Solution Manager
Some guidelines following the BPMN 2.0 notation
▪ A BPMN process model…

− concentrates on the process logic
− reveals only the order of activities in
which they are executed
− shows when activities happen
− depicts under what conditions activities
happen
▪ A BPMN process does not…
− express what happens inside an activity
− describe how an activity is performed
− show where (location) an activity is
performed
− explain why an activity is performed

Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Recording Requirements
Recording Requirements
Product backlog in Focused Build
Product Backlog
Process Expert / WI Architect /
Requirement
Business Analyst WI
Developer
Work
Requirement Package WI
Requirement WI
Work
Fit/Gap Requirement Work Item
Package
Communication
▪ Bridge between Business and IT
▪ To efficiently document requirements, an IT expert, the architect, should take part in the FIT to Standard workshops

Where to add requirements?
The best practice is to add requirements to process steps and processes, but they can also be
linked to other elements if required.
Process
Requirements
Processes
Requirements can be maintained

for the following SolDoc elements:
▪ Structure Elements
Process Step Library − Process
− Process Step (Reference)
▪ Library Elements
Executable Library − Configuration Item
− Process Step (Original)
Development Library
Configuration − Executable
Interface Library Library
− Development
− Interface
Create Requirements in Solution Documentation
Requirements can be assigned within the diagram editor or in the Solution Documentation
browser by selecting the process step or other structure elements.

Display requirements in Solution Documentation
The relationship between requirements and processes in Solution Documentation features the following:
▪ Indicate in the process if requirements are available
▪ Direct access to all existing requirements

Solution Documentation – Reporting capabilities
In the Solution Documentation UI it is possible to get a list of all requirements created in the Focused Build
context. This list has all standard filter and sorting options – e.g. to find requirements related to a specific
business process or process step.

My Requirements app
Use Case
If you want to review all your requirements use the Requirements app available in the SAP Solution Manager launchpad.

Do’s and Don’ts
▪ Define and follow clear naming conventions for

Requirements
▪ Define and discuss within project team how to use
priority, category and other attributes across project
teams
▪ Decide on Requirement Categories before starting
Requirement gathering in order to simplify searching
and filtering
▪ Add meaningful names and description to
Requirements – especially when working on bigger
teams
▪ Sign-off process including Requirements by
customer

Demo: creating a requirement in SAP Solution Manager

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Managing Requirements Backlog
Managing Requirements Backlog
Release planning – Roles and responsibilities
Create requirement
based on business
1. Define product process
Business Analyst
Responsibility
backlog
Business
Use value points High-Level

and priority to rank Release Plan
2. Prioritize product Approve/
backlog postpone Based on Project
5. What would you like requirements
in the release?
3. Analysis of
dependencies
Responsibility
Use effort to
Architect
Detailed
estimate
IT
4. Estimate product Create work Release Plan

backlog packages Based on Wave
6. Scope release:
Build logical and technical
packages

Requirements Management process flow
Requirements
Send for Approval To Be Approve

Draft Approved In Realization Realized Completed
Approved
Revise
Reject Create Create

WP WP
Create Set Set Set
WP by by by
Recover Set WP WP WP
Rejected
by
WP
Withdraw
Postpone Postpone
Canceled
Withdraw
Withdraw
Recover
= manual status setting
Postponed Set = automated status setting
by
WP

Find requirements
Use the Requirements app to filter, sort, and

maybe export the list of all requirements.
You can maintain further attributes like Value

Points or Effort Points to prioritize your backlog.

Prioritize the backlog
How to establish clear priorities

▪ In Agile projects the process owner must prioritize and
force-rank list of all requirements in project backlog
▪ No two items should end up being ‘equal’ on the list
(for example, have the same priority and ranking)
▪ Main reason for this is to prevent everything being
rated as a “very high”.
▪ The MSCW prioritization (Must-Have, Should-Have,
Could-Have, Would-Have) is mapped with priorities
very high, high, medium, and low in SAP Solution
Manager
▪ Secondary step is to rank items within the same
priority group with value points
Use columns “Priority” and “Value Points” in the

requirement in SSM to prioritize and sequence the
product backlog.
Approve requirements via Mass Change Operations app
You can use the Mass Change Operations app from SAP Solution Manager launchpad to approve
requirements in batch.

Monitor all requirements using the Solution Readiness Dashboard
Tile: Requirements
Gives an overview of all requirements assigned to your project.
Each bar of the tile is clickable and offers a filtered list of requirements.
Unassigned Requirements
The Unassigned Requirements bar displays all requirements
that still need work packages creating for them.

Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Working with Scope
Working with Scope
What is a solution documentation scope? (1)
Definition of content Allows focussing Represents the Build test plan scope Considers certain
visibility for specific on certain area during documentation scope of a based on the solution structure areas for
group of interests or based reporting tasks. project. documentation scope. export or information
on area. exchange with other
tools.
The scope selection Can be extended by Scopes can be assigned The scope provides
can be further adjusted by additional filtering directly to the project on all selected processes
use of filtering capabilities criteria like customer the Solution and library elements,
in list and column browser. attributes. Documentation tab. including test-relevant
objects like manual
or automated test
cases and test steps
Documentation Reporting Project Test suite Export/API
Scope
Specifies areas in business process structures and includes automatically (default setting) all library elements
Working with Scope
What is a solution documentation scope? (2)
Scope can be further

The diversity of …can be simplified Test plan can be
used to specify
documentation in by a public scope created based on
documentation focus
a branch… definition a scope
for a particular project
Solution Documentation Scope

HR
Project scope Test plan
Logistics
Finance

Working with Scope
Scope in Focused Build: procedure (1)
Define Assign scopes to

Upload best practice Run discovery
documentation Define projects the appropriate
content workshops
scopes project
Upload of applicable Using standard Define all relevant Assign the solution Start transaction
best practice content into transaction for solution projects. documentation scope(s) SOLDOC and select a
Import branch. documentation to create to the appropriate project scope corresponding
public scopes. to the workshop focus,
The relation can be: make changes to the
Relevant content can be These scopes can solution documentation
released into the Design represent documentation ▪ One scope to one content and document
branch and thus initially scope for a project or build project. This later requirements.
prepared for discovery group of scenarios and allows the direct
workshops. processes from one area relation of
(e.g. Finance, Logistics). requirements to a build
project.
▪ Several scopes to one
build project.

Working with Scope
Detect and create Extend the Create Create

Upload Best Practice Define documentation documentation
requirements Define projects work Assign
packagesscopes to work Run
itemsdiscovery
Run discovery
content scopes the appropriate workshops
scope (optional)
workshops project
Scope selected If the requirement also When creating the work Once a structure is
previously in solution relates to other package, the scope selected from the work
documentation is processes from the information together with package to create a
transferred to the same scope, you can corresponding process work item, the scope
requirement together easily extend it. structures will be passed information will be
with the relevant from the requirement to inherited.
process structure. the work package.
The selected process If another scope is Based on assigned Further additions of

structure and the scope affected, you can scopes, the selection of relevant structures can
from which it was change the scope and relevant projects will be be just made from
selected forms an select structures from restricted to all projects already available scope
inseparable connection. there. The additional with assigned scope.
scope will be saved
together with the Solution documentation
corresponding selected can only be extended
structure in the within the scopes that
requirement. have been assigned to
the requirement.
Working with Scope
Detect and create Extend the Create Create

Define build projects Upload Best
requirements Define documentationwork Assign
documentation scopes to work Run
packages itemsdiscovery
Run discovery Practice content scopes the appropriate workshops
scope (optional)
workshops build project
Assigned Scope
Solution Documentation Scope Requirements structure attribute
HR HR
n:m
Project scope: HR
Automated project
Assigned Scope
Logistics detection based
on available
Work Package structure attribute
scope attribute HR
1:n
Project scope: FI
Finance
Assigned Scope
Work Item structure attribute
HR

Working with Scope
Scope in Focused Build: result
Upload best practice Define documentation Define projects Assign scopes to Run discovery
content scopes the appropriate workshops
project
Advantages
➔ Possibility to assign process management content (scope) to a project (1 : 1 or many :1)

➔ Possibility to assign scope to requirement (1 : 1 or many : 1)
➔ Simplification in project search for work packages by already assigned scopes
➔ Reduction of solution documentation content to project-relevant scope when extending work
package documentation scope (Assign Structure(s) popup)

Working with Scope
Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 7: Process Reporting
Process Reporting
Reporting capabilities for project q-gates (1)
▪ Standard reporting
Using the list viewer or the standard reports
provided within the solution documentation, you can
report on various elements or documentation status.
▪ Focused Build reporting
In addition to the standard capabilities a new
dashboard has been delivered which helps to detect
the current implementation state in a certain
business process area (scope).
Depending on the selected branch you focus on:
- Design branch: Requirements and work
packages which are not yet in development
- Development branch: Requirements, work
packages, and work items which are currently in
development
- Productive branch: All Requirements, work
packages and work items for already productively
used processes

Process Reporting
Backlog Definition Handover to Development Handover to Release

Use Case Example
Selection of all open Before this Q-Gate you can ensure Before this Q-Gate you can ensure
requirements available in the with a selection of work packages with a selection of work items
Design branch for a specific (Design branch) in a specific status (Development branch) in a specific
process area (scope) in status and assigned to a certain status and assigned to a certain
“Draft” and “To Be Approved”. project/wave that all documentation sprint, that all documenation KPIs
This result gives an overview KPIs for functional specification for technical design as well as the
of the incomming backlog for and test cases are rated green. appropriate work package-related
the next project wave. With that, you can ensure a smooth functional specification and test
handover of activities to cases are rated green. With that,
development in your process area. you can ensure a smooth handover
to release for your process area.
Process Reporting
By the selection of solution, branch, and

documentation scope, the report will provide
information about the number of requirements, work
packages, and work items in a certain status.
These statuses can be used for specific filtering of
displayed details in the table.
The table also provides information about the status
of documentation KPIs available for a work package
and work items.
From the result table, further investigation can be
performed by jumping into specific work packages
and work items to control the correctness of the
documentation.
The result table can be downloaded into a local file
(together with additional information about referred
process structures and structure attributes) to
document a certain project status.

Process Reporting
Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 8: New Features Since SP03
What’s New with Focused Build SP4?
Process Management
Process Management – new with Focused Build SP04
Composite interface and Test scripts
Application
dropDocs integration to Work Package and
Work Item
Feature details
• Possibility to address composite interfaces in
Requirement, Work Package and Item
• Visibility of test scripts (CBTA) and recognition
for KPI rating (CBTA + Test Steps)
Use Case
Completing of coverage solution documentation
objects, which can be handled by Focus Build.

Scope and structure scope popup
Application
Solution Documentation “Scope” integration into
Requirement to deploy and process scope popup
harmonization.
Feature details
• Possibility to select solution documentation
“Scope” on the process scope popup. This is
impacting the displayed content.
• Storage of the “Scope” information to all
selected structures on the scoping popup
and in the process assignment area.
Use Case
Simplification of structure assignments and
project selection for projects with assigned
Solution Documentation “Scope”.
Availability of dropDocs
Application
Availability of documentation tab for additional
CRM transaction types:
- Request for Change
- Standard/urgent change
- Defect correction
Feature details
• Possibility to access and change
documentation.
• No impact on KPI rating
Use Case
Unification of UI design for additional CRM
transaction types.

Process Management
Language recognition and performance improvements
Application
dropDocs integration to Work Package and
Work Item
Feature details
• Improvements on structure assignment popup
• Language recognition on documentation tab
• Performance improvements for document handling and KPI
Use Case
Visibility of already scoped structures on structure assignment
popup and visibility of maintained languages and translations.

What’s New with Focused Build SP6
Process Management
Status change for Test Step and structure related activities
Application
dropDocs integration to Work Package and Work Item
Feature details
▪ Un-assign of structures in Work Package and Work
Item
▪ Move of structures in Work Items
▪ Status display and direct status change for Test
Steps
Use Case
Quick changes on Test Step status trough Work
Package and Item as well as harmonized un-
assignment of structures and documents.
Simplification of move structures between Work Items.

Process Management
Reporting dashboard and handling improvements
Application
dropDocs integration to Work Package and Work Item.
Feature details
• Availability of Documentation Reporting
Dashboard
• Release check of structures in Work Items to detect
release conflicts
• FB specific related documents display per branch
• Customer status schema recognition for KPI and
Solution Readiness Dashboard as well as unlocking
of documents
Use Case
Simplification of activities around documentation
handling and reporting.
Documentation Reporting Dashboard
Application
Documentation Reporting Dashboard
Feature details
Using the Business Process Readiness report as part of
Documentation Reporting Dashboard you can detect the
current status of implementation from business process
perspective.
Running the report for design branch, it provides all
Requirements and Work Packages which are planed for the
selected scope. Executing the same selection for
development branch gives an overview about current active
implementation. Once the process arrived in production
branch, the report gives an absolute number of
Requirements, Work Packages and Items for certain scope.
Benefits
Simplified method to report on the current state of
implementation for a specific business process scope.

Release check
Application
dropDocs integration to Work Item.
Feature details
• Detection of all objects changed or created by
current Work Item
• Detection of all potential obstacles for Work Item
release before hand over to release.
Use Case
This functionality can be used as final documentation
check before handing over the Work Item to Release.

Focused Build specific related documents
Application
Solution Documentation
Feature details
• Visibility of new Focused Build specific related
documents:
• (FB) Request for Change
• (FB) Change Document
• Changes on visibility and counting method for

• Requirements
• Work Package
• Work Item
Benefits
Better visibility of associated related documents to
selected structure.
Customer status schema and unlocking of documents
Application
dropDocs integration to Work Package and Work
Item.
Feature details
• Enablement to use customer specific status
schemas for document types
• Reflection of customer status values by KPI
calculation and Solution Readiness Dashboard
• Possibility to unlock locked documents directly from
Work Package or Work Item.
Benefits
Handling simplification to unlock documents and
extended flexibility in use of customer status values
for documents.
Process Management
Improvements in BP-Readiness Dashboard
Application
Business Process Readiness Dashboard is
improved by additional filtering capabilities.
Feature details
- Additional selection of business processes as
filtering criteria
- Display of project ID in the result table
Benefits / Use Case

Better results due to the extended filter possibility
and more information in the result table for
additional result processing.

Display of deleted objects from Work Package/Item
Application
dropDocs integration for to Requirements, Work
Package and Work Items
Feature details
In case relevant structures for a certain Work
Package/Item has been deleted in one of following
waves:
- the deleted structure will be still displayed in the
according Requirement, Work Package/Item
- Click on relevant document from WP/WI opens
the document in the version which was valid as
the WP/WI has been completed.
Benefits / Use Case

- Visibility of related but deleted structures.
- Access to the correct document version once the
WP/WI is completed

Navigation from Related Documents area
Application
Related documents for Focused Build related
objects has been changed.
Feature details
Depending on the branch from which the related
document type is called, different overview
possibilities are displayed:
- Design => Requirements Management
- Development => Mass change app
- Production => Mass change app
Benefits / Use Case

Clear visibility of related Requirements, Work
Packages and Items for selected solution
documentation structure and synchronicity with
Business Process Readiness Dashboard.

Requirement Management
My Requirements, My Work Packages, My Work Items - New with SP04
Value, Effort, Story Points default values
Applications
My Requirements, My Work Packages, My Work Items,
Features
• Requirements, Work Packages, Work Items:
Customizing table for Value, Effort, Story Points default
values
• Take-over of values in case of 1:1 relation
of Requirement : Work Package
• Example customizing available via BC-Set
Use Case
The default values allow a standardized maintenance of
values across the project team.

Requirements Managememt, My Requirements - New with SP04
Create and report on Requirements based on Scope
Applications
Requirements Management, My Requirements
Features
• Create Requirements out of Scope
• Inherited filter settings in Requirements Management
application
• Filtering for Elements part of a Scope
Use Case
Requirement creation: Before you start Fit-Gap Workshops
define appropriate (public) Scopes. When you later create new
Requirements for this business area, you can filter on this
Scope. So it’s easier to find the correct process elements and
the Requirement get’s this Scope assigned as an Attribute.
Filtering: Allows to display Requirements which have been
created in a specific Scope context, e.g. for reporting, to rework
the Requirements or to set a status like ‘To Be Approved’
Requirements Management - New with SP04
Create Work Packages based on Scope
Applications
Requirements Management
Features
• Create Work Packages part of a Scope
• By default only show projects assigned to the
selected Scope
Use Case
To ensure, that only projects can be selected which
are assigned to the selected Solution Documentation
Scope, the project application help is prefiltered
accordingly.

Requirement Management
Requirements Management – new with Focused Build SP05
Requirement Upload Report
Applications
Requirements Management, Upload report
/SALM/Requirement_Import
Features
• Additional options how to handle the
Requirement Owner field
• Overwrite existing with current logon user
• Keep original Business Partner
• Check and take-over in case Business Partner
exists in source and target system
• Complete Requirements with current logon user in
case the Business Partner is not maintained
• Extended consistency checks
• Completeness of obligatory fields
• Duplicate Requirements
• Success of Process Structure mapping
(creation of standalone Requirement)
Use Case
The extended checks ensure better data quality
and less clean-up effort after the upload
My Requirements, My Work Packages, My Work Items – new with SP05
Extended Change History
Applications
My Requirements, My Work Packages, My Work Items
and the related CRM Web UI
Features
The change history has been extended by the following
values
• Requirement
• Value Points, Effort Points, Local Flag
• Work Package
• Value Points, Effort Points, PPM Project, Wave, Dates
• Work Item
• Value Points, Story Points, Dates
Use Case
E.g. in My Requirements app several fields are open for
changes after approval. As it is compliance relevant, a
Change History is needed to see, if and who changed
the values at a later point in time.

Requirement Management, My Work Packages – new with SP05
Create Work Package - Solution Filter for Project Display
Applications
Requirement Management, My Work Packages
Features
Creating new Work Packages, you need to choose a project.
Now the Project selection is limited to Projects part of the
selected Solution
Use Cases
• Use Case 1:
In case in Requirements Management there is a filter set for one
Solution and you select one or more Requirements from the result list
-> in Project selection pop-up, only projects assigned to this one
Solution are displayed
• Use Case 2:
In case of standalone WP
-> in Project selection pop-up, all projects of all Solutions are shown
• Use Case 3:
In case there is no Solution filter selected and there are Requirements
of more than 1 Solution selected
-> pop-up informing, that it is not allowed to create Work Packages of
different Solutions

Performance Improvements
Applications
Features
Reduced time to display the Requirements
result list
Use Case
In some cases it is helpful to display several
hundreds or thousands of Requirements,
e.g. to:
• use the app for an ad hoc reporting
purposes
• do an xls export to create a customer
specific reporting
• do an xls export to upload to another
Solution Manager system

New value 'No Solution'
Applications
Features
• New value 'No Solution' is available in the
dropdown menu ‘Solution’
• It lists all Requirements without Solution
assignment in Requirements Management.
Use Case
This feature allows to efficiently clean-up the Solution,
e.g. identify Requirements, which have been created
once, but not further processed.

‘Status’ Filter with Multi Selection
Applications
Features
• Multi selection checkboxes for the ‘Status’ filter
drop-down
• Allows an extended search pattern in the
Requirements Management app
Use Case
The potential combination of Requirement status
improves the reporting capabilities of the
Requirements Management app., e.g. it allows to
display the all Requirements:
• in a the final status ‘Completed’ or ‘Canceled’
• which are approved, ‘In Realization’ or ‘Realized’
but not completed

Navigation Improvement on Requirement Detailed View
Applications
Features
• Improved navigation for Requirements Management
details pop-up
• Additional button ‘Save and New’
Use Case
In order to easily set the status ‘To be Approved’ directly
after creating a new Requirement the remains open, after
saving.
In case you want to create a new Requirement without
setting the status ‘To be Approved’, there’s a new button
‘Save and New’
If you work with a Requirement in status ‘To Be Approved’
and save, the pop-up remains open, because the user might
just want to save the current state of work.
When choosing the Action ‘Send for Approval’, the pop-up
closes, because the Approval is done by another responsible

Direct Navigation to Requirements Management Detailed View
Applications
Features
Direct Navigation to Requirements Management
Detailed View via link
Use Case
In case you copy the Requirements Management
Detailed View link (e.g. into a document), you are
now directly directed to the detailed screen of the
Requirement you copied it from.
Before SP06 only the link to the Requirements
Overview is possible.

In-App Help – new with Focused Build SP6
More applications covered by Web Assistant
Application
Content for web-based help system to provide you with

context-sensitive user assistance
Feature details
Can be activated with Help control
With SP6 the following applications are covered:

▪ Requirements Management
▪ Project Management
▪ My Test Execution
▪ Test Steps Designer
▪ Test Steps Parameters
Benefits
Intuitive access to help information
See Configuring SAP Web Dispatcher for In-App Help on the SAP Help Portal at https://help.sap.com/viewer/product/SM_FIORI/
> Configuration Guide > Setting Up the System Landscape > Setup of In-App Help.

New field Requirements Team
Applications
(CRM Web UI), Mass Change
Feature details
• Maintaining a new Requirement, there’s a new
field ‘Team’
Use Case
So far it was only possible to assign a specific
Business Partner to a Requirement as Owner.
With the new field it’s now possible to assign the
Requirement to a team, e.g. responsible for a
Business Process. So if one responsible is on
vacation or sick another member of the team can
process the Requirement.

New field Planned Project
Applications
(CRM Web UI), Mass Change
Feature details
• Maintaining a new Requirement, there’s a new
field ‘Planned Project’
• The F4-help displays all Build Projects of the
same Solution in case they are in status
Created or Released
Use Case
With the new field it’s now possible to do an early
product backlog planning, e.g. to estimate and
hire the required resources for a planned Build
Project or Work Stream.

UI5 Text Templates
Applications
Requirements Management, My Requirements, My Work
Packages, My Defects, My Defect Corrections, My Request for
Changes
Feature details
Up to now, there was the need to switch to CRM Web UI to
maintain Text Type templates
• In the Requirements Management Details Screen, there is
now the possibility to define Templates for the ‘Description’ tab
• In My Requirements and all other Document Types there is
the possibility to maintain private templates for all Text Types
Use Case
Text templates allow to standardize the creation of
Requirements. This helps to ensure, that they are maintained in
the right granularity and contain all the information the Architect
needs to create the Work Packages.
Customizing for Requirement Description Text
Applications
Requirements Management, SOLMAN_SETUP
Feature details
In transaction SOLMAN_SETUP
> Step Perform Basic Configuration
> Sub-step Requirements Management
> There is a new Activity ‘Set text type to obligatory’
Use Case
In Requirements Management Details app and
My Requirements text tab, there are several text fields.
They are not mandatory by default.
There is now an Activity in the Basic Configuration of
transaction SOLMAN_SETUP, which allows to control, if
the Requirement ‘Description’ text field shall be mandatory
or optional.

Create Work Package
Applications
Feature details
• When a new standalone Work Package is created,
there is a success message, with a direct link
leading to the newly created WP
• In Requirements Managements Detailed view, it is
now possible to create a new Work Packages out
of an Requirement detailed screen if it is in status
‘Approved’ or ‘In Realization’
Use Case
These features optimize the navigation and
accelerate the creation of new Work Packages

Improve WP Checks for Project & Wave Selection
Applications
Requirements Management > Assign Existing Work
Package Pop-Up
Feature details
New filter displaying the Solution context of selected
Requirements
Improved checks and value helps when selecting Work
Packages, e.g.
• only allow Work Packages in status Created, Scoping,
Scope finalized
• only display Projects of the same Solution
• filter on projects with assigned Solution
Documentation Scope
Use Case
The new checks have the following advantages:
• Reduce the risk of maintaining wrong data
• Better usability and time saving because of precise
value helps
Multilanguage Support for Requirements Import
Applications
Feature details
Report /SALM/Requirement_Import now allows
• Separate selection or source and target language
• Logon language as default language
Use Case
Beforehand it was only possible to export and import your
Requirements in English.
This function allows to display the original source system text in a

different language context of the target system e.g. Spanish, French
or Russian text in the English language context.
With that, there is at least the text in the original language visible.
This can be used as a ‘fallback language’ and manually replaced or
extended, later.
In case no language is selected, the current logon language will be

taken as default value.
Requirement Export
Applications
Feature details
The current excel export from Requirements Management
smart table provides only the element name
• After column ‘Element ID’ there is an addition column
‘Element Path’
• If there are several Solution Documentation Elements
assigned to one Requirement. There is a concatenation of
these Solution Documentation Elements links listed
Use Case
With the complete path, it is now clear, to which other Solution
Documentation Process Structure Elements the exported
Element is assigned to.

Solution column in requirements result list
Application
Requirements Management, Mass Change
Operations
Feature details
There is a new column ‘Solution’ with enabled
sort functionality. The column is not displayed
by default but it can be displayed via the
Settings.
Benefits / Use Case

If you search cross Solutions (the Solution filter
is empty), e.g. for unassigned Requirements,
it’s now visible which Requirements are of the
same Solution. With that, you can do e.g.
some Mass Change operations.

WRICEF Sub-Classification filter
Application
Requirements Management, Mass
Change Operations
Feature details
There is a new filter and column
‘WRICEF Sub-Classification’ inclusive
sort functionality. Via the filter settings
this column can be hidden.
Benefits / Use Case

In case the Requirement
Classification filter has the entry
‘WRICEF’, you now have a more
detailed search for specific WRICEF
elements. So, it’s now transparent,
how many and which Requirements
have a specific WRICEF element
assigned.
Mass Change Operations
Mass Change, Requirements Management - New with SP04
Value, Effort, Story Points default value ranges
Applications
Requirements Management, Mass Change Operations
Features
• Customizing table for Value, Effort, Story Points
ranges
• Mass Change: Extended Filter and Display Options for
Value, Effort and Story Points ranges
• Example customizing available via BC-Set
Use Case
The range selection in the Mass Change offers an
efficient filtering based on the predefined values, e.g.:
• to define Initial Backlog in Requirements Management
based on Requirements, Value and Effort Points
• to define Product Backlog in Mass Change Operations
based on Work Packages, Value and Effort Points
• to do Sprint planning in Mass Change Operations
based on Work Items, Story Points
My Work Items - New with SP04
Display Role for Mass Change
Applications
My Requirements, My Work Packages, My Work Items,
Features
• Add Mass Change Operations tile has been added to the
following persona: Project Manager, Developer, Test
Manager, Tool Lead
• Sharpened authorization concept dependent on
Document Type, e.g. Defect or Work Package
Use Case
Allows other project members either to display of Mass
Change Operations data, e.g. the developer to check Work
Items in status Postponed.
Other persona got change authorization, e.g. the Test
Manager to mass change the support team for some
Defects
Mass Change – new with Focused Build SP6
Improved Display of Column ‘Release’
Applications
Mass Change
Features
Improved display of Release information in columns:
• Actual Release
• Requested Release
Harmonization of Release display, e.g. in the value help,
the Release is now displayed as a three-digit number to
the right of the description
Use Case
In Mass Change - Actual and Requested Release:
In the result lists, the Release is displayed as a three-digit
number.
The full Release description is displayed via tooltip.
This reduces the table widths and allows to display more
results, especially on smaller screens
New filter for Sub-Elements and Sub-Categories
Applications
Mass Change
Features
New filter possibility ‘Sub-Elements’
introduced for:
• Requirements
New filter possibility ‘Sub-Categories’
introduced for:
• Requirements
• Work Packages
• Work Items
• Defects
• Defect Corrections
• Change Requests
• Changes
• Risk
Use Case
Allows more granular filtering like in Requirements
Management application.
Filter & View variants for Mass Change
Applications
Mass Change
Feature details
For all Mass Change Document Types it is now
possible to save private and global:
• Filter settings
• View Settings
Use Case
Like in Requirements Management, the Filter Variant
allows an end user to save typical filter settings, e.g.
for a Project Manager to regularly check, if there are
Requirements in Status ‘To Be Approved’ for the
Business Process in his responsibility.
As well the view of the displayed columns can be
saved. This is important as the space to display the
content is limited.
Both features extremely accelerate the search and
display of the required content.
Allow filtering for multiple IDs and fragments
Applications
Mass Change
Feature details
Using filter ‘ID’ it is now possible to search with:
• Multiple IDs, e.g. 8000004711, 8000004712
• Fragments of an ID, e.g. 4711
• Multiple ID fragments, e.g. 4711, 4712
Use Case
In Mass Change Operations it is now possible
to filter for ID fragments or multiple IDs like in
Requirements Management.

Solution Readiness Dashboard
Solution Readiness Dashboard – new with Focused Build SP5
Usability and performance improvements of extraction report
Default variant of extraction report /SALM/DATA_EXTRACTION_PPMITSM to be scheduled via Job Scheduler (SM36):
Focused Build data to be selected for Solution Readiness and

Release Dashboard
This option extracts only data that has been changed since last
extraction to save runtime. Only deactivate this option when
necessary due to issues.
All Focused Build projects with status ‘Created’ or ‘Released’

are considered by the default variant ‘FOCUSED_BUILD1’
Variant can be changed to allow extraction for dedicated
projects based on project id or status.
E.g. if you like to keep data also for completed projects you can
adapt the variant accordingly.
Depending on the amount of projects, requirements, work

packages etc. you might face longer runtime of the batch job.
With the default variant, the extraction is processed in parallel
and uses 50 % of available work processes.

Usability and performance improvements of extraction data housekeeping report
Report /SALM/DATA_EXTRACTION_DELETE can be used on demand to cleanup extraction data for un-used
projects or compress transactional historic data on a weekly base
Time frame for aggregation of transactional historic data
If selected, project data with below criteria are deleted from extraction data.
If selected, transactional data from time frame above are compressed, so
only one entry of a weeks state of an entity will be kept.
Selection criteria for projects to be deleted from extractor data
Project ID - Here you choose the Project IDs for the projects, which will be
deleted. When the field is empty, all project with the chosen project status
are deleted.
Project Status - Here you choose the Project Status Values for the projects,
which will be deleted. Default: Completed, Canceled, To be Archived
Data are only deleted, when both conditions are fulfilled.

Realtime update of Dashboard data
Applications
Realtime update and refresh of Dashboard data for Focused Build
entities
Feature Details
The data displayed in the Solution Readiness is provided by extractor
and caching tables which have been updated by batch jobs in the past.
This has been enhanced by a event triggered update and refresh
feature in order to get real-time data shown in the dashboard for
following Focused Build entities:
• Requirements , Work Packages and Work Items
• Defect Corrections
• Projects and Risks
Data refresh can be controlled for the currently selected project by a

timer via new button in the dashboard and typically has a delay of 10 –
40 seconds depending on size of project.
Benefit
Improved monitoring and transparency about implementation progress
and KPI fulfillment with real-time data
Requirements Tile – Improved Usability
Applications
Feature details
For all Requirements in Requirements tile, there is
display of all Requirements, without predefined filters.
To reach the complete list of Requirements, click on
the Requirements tile.
Use Case
In SRD Requirements tile, by clicking on one of the
bars, there was only a standardized list of pre-filtered
Requirements displayed.
Now the user ha more flexibility, as there is:
• A list of all Requirements displayed
• The list display then allows a user specific, cross
status, filtering, e.g. based on Priority

Improved Export to spreadsheet feature
Applications
Solution Readiness Dashboard - Export to Spreadsheet
Feature details
Export CSV has been replaced by Export to spreadsheet
for all list views in the dashboard
Benefit
After export the spreadsheet can be directly opened without
conversion. Filter is active by default using the header row
(1). No problems with special characters.

Thank you.
open@sap.com
Follow all of SAP

warranty.
See www.sap.com/copyright for additional trademark information and notices.

openSAP Solman2-1 Week 2 All Slides

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

openSAP Solman2-1 Week 2 All Slides

Uploaded by

Copyright:

Available Formats

Week 2: Explore Phase (Process Expert/Analyst)

Unit 1: Introducing Solution Documentation

Fit / Gap ▪ Process model

Assign work ▪ Functional specification

Test Plan & Manage ▪ Test request

Release Build, test and Manage

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Change Control Sites

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Libraries help to re-use documentation elements to avoid redundancies

Process Step Library

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Business process description

Functional integration test case description Interface Configuration

As-is solution As-is solution

operating model and processes Design

Innovate & Enhance & Fix

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Accelerators Engineered Service

Business Content Preconfigured Solution

Activate + Industry Reference Architecture + Digital Business Framework

Configuration Test Cases

Best Practice Configuration Configuration Test Cases

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Navigate to SAP Model Company system

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

All available documentation Default import

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Production Scoped processes are

As-is solution As-is solution

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

Process hierarchy and process diagrams

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

End to End processes

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Process diagrams are tailored to specific needs One process

▪ Implementation perspective versus

One process definition, multiple

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Some guidelines following the BPMN 2.0 notation

▪ A BPMN process model…

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Requirements can be maintained

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

▪ Define and follow clear naming conventions for

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2021 SAP SE or an SAP affiliate company. All rights reserved.