Road map for Documentation and
Implementation in SAP Solution Manager
Robin Schönwald, SAP Consulting
September 2014
Public
Agenda
Application Lifecycle Management (ALM)
Why do you need this ALM Service
§  Pain points on the following 3 flavors:
•
Documentation, Implementation, Template Management and Re-Documentation
What will be delivered during this ALM Service
§  Brief introduction on how SAP Solution Manager can meet the challenge on each of the 3
flavors:
•
Documentation, Implementation, Template Management and Re-Documentation
Who should attend this ALM Service
§  Project Managers and project team members
§  Support/BAU
How can you use the information you received during the ALM Service
§  Effort of Service delivery
§  Deliverables in any One of the flavors
•
Documentation, Implementation, Template Management and Re-Documentation
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
2
Application Lifecycle Management
An Approach in Six Phases of ITIL Application Management
Upgrade Management
Ÿ  Comprehensive project support for release transitions
Custom Code Management
Ÿ  Lifecycle management for custom code
Landscape Transformation
Ÿ  Management of business- and IT-driven
changes in SAP solution landscapes
Maintenance Management
Ÿ  Management of corrective software
packages, reduction of waste in
custom code
Business Process Operations
Ÿ  Help ensure business continuity
Ÿ  Provide business KPIs
Ÿ  Business process benchmarking
Technical Operations
Ÿ  Central monitoring and alerting
infrastructure
Ÿ  Unique end-user experience monitoring
Ÿ  Central administration tools
Solution Documentation
Ÿ  Central documentation of processes, system landscape,
custom code, partner applications, and more
Solution Implementation
Ÿ  Discover and realize enhanced business
functionality
Ÿ  Avoid disruption of business
Template Management
Ÿ  Standardize configuration across
multiple projects
Test Management
Ÿ  Change impact analysis
Ÿ  Complete test management
Change Control Management
Ÿ  Integrated quality management
Ÿ  Synchronized transports of various
components
Ÿ  Controlled and documented
Application Incident Management
adjustment of business processes
Ÿ  Integrated service desk
incl. approval process
Ÿ  Involvement of partners in problem resolution
Ÿ  Root-cause analysis for complex landscapes
with diverse technology stacks
SOLUTION TODAY
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
3
Scope of Service “Documentation and Implementation”
within the Application Lifecycle Management (ALM)
Upgrade
Solution Implementation
Ÿ  Re-documentation RBPD/
SoDocA
Ÿ  Implementation & Upgrade
Ÿ  Discover and realize business
Functionality
Ÿ  Project Administration
Ÿ  Blueprint Documentation and
Modeling (ARIS)
Ÿ  Reporting and Monitoring
Solution Management
Template Management
Ÿ  Handover Project
à Solution
Ÿ  Maintenance Projects
Ÿ  Retrofit
Ÿ  Upgrade Management
Ÿ  Template/Rollout Projects
Ÿ  Global / Local Processes
Ÿ  Rollout Generation Template
based Synchronization
Governance
Ÿ  Release & Version Management
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
4
Big Picture: Service “Documentation and Implementation”
Flavor: Documentation & Implementation and Template Management, Re-Documentation
Excel
Upload
SAP Business
Process
Blueprinting
ARIS
IBIS/ BPR
Solution
Documentation
Assistant
Upgrade/
Long Term
Project
Solution
Implementation
Project
Template
Project
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Maintenance
Project
5
Agenda
Why do you need this Service
Pain points on the following 3 flavors:
–  Documentation & Implementation, Template Management and Re-Documentation
Configuration
ReDocumentation
Blueprint
Testing
Upgrade
Implementation
Project
Maintenance
End User
Training
Template
Solution
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
6
Documentation
Typical Customer Use Cases
My Document is:
Ÿ  Hard to understand for non-experts
Initially my business processes have been modeled very detailed.
After go-live, the documentation is too complex to be reused.
Ÿ  Outdated and not reliable
Because of costs or organizational aspects my business process
documentation has not been updated or verified since it’s initial
creation.
Ÿ  Not related to supporting software
No sufficient transparency which SAP and non-SAP software
supports my business processes.
Ÿ  Not centrally accessible
No centralized access to my business process and system
landscape information
Ÿ  Very costly to maintain
No automated and controlled maintenance of my documentation.
So I do this effort sporadically, partially or before major software
updates.
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
7
Implementation
Typical Customer Use Cases
Ÿ  Who is involved in the project?
(For example: Does business reengineering
require that the business process experts are
involved with requirements and design?)
Ÿ  When have the deliverables to be generated?
(For example: Deliverables across heterogeneous
teams require templates to provide a common
understanding on tasks and activities.)
Ÿ  What has to be done by whom?
(For example: Complex business teams require
clear work lists and strong and transparent
planning.)
Ÿ  How to control and report the progress of
each phase?
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
8
Template Management
Typical Customer Use Cases
Ÿ  Unstandardized business processes
across scattered business landscapes
Ÿ  Different implementation approaches
and strategies
Ÿ  Missing link between business process
documentation and technical
realization
Ÿ  No flexibility for business process
adjustments leads to a long time to
benefit
Ÿ  No harmonized Release- and Version
Management across the application
landscape
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
9
Re-Documentation
Typical Customer Use Cases
How Do I
…get full transparency about real usage of SAP
Applications with the most important business processes
…obtain a comprehensive representation of current
implemented and used processes and solutions
…do risk-based testing rather than testing everything
…ensure a quick and easy way to get business
processes documented in the SAP Solution manager
…obtain a central entry point to manage and monitor
all SAP solutions and processes
…enable a quick re-use of processes for planned
projects (e.g. upgrade, rollouts etc.)
…leverage on a central basis to set up the basis further
ALM processes
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
10
Agenda
What will be delivered during this Service
Brief introduction on how SAP Solution Manager can meet the challenge on each of
the 3 flavors:
–  Documentation & Implementation, Template Management and Re-Documentation
Configuration
ReDocumentation
Blueprint
Testing
Upgrade
Implementation
Project
Maintanance
End User
Training
Template
Solution
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
11
Documentation
Approach
Documentation means having documented the following key elements:
Ÿ  core business processes
Ÿ  related technical objects, such as transactions, programs, custom code, background jobs,
interfaces
Ÿ  related (non-SAP) system and software components
The activities required to implement the documentation standard is to validate
existing documentation policies and practices and agree upon how to
progress to the next step. This includes:
Ÿ  types of documents (technical and business processes)
Ÿ  Naming convention
Ÿ  Templates
Ÿ  Ownership responsibility of the document maintenance
Ÿ  Documents of project and maintenance
Document storage area (central vs. individual)
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
12
Documentation – Goal
ALM Phase and Related Documentation
Documentation can be continuously
enriched along the application life-cycle
Ÿ  Design: Create global business process
templates and specifications, e.g. for later
implementation projects
Ÿ  Design/Build: Newly create or locally adjust
business process structure during your
implementation project
Ÿ  Build/Test: Extend business process
documentation during configuration, e.g. with
custom code documentation, configuration
information, test cases
Ÿ  Operate: Re-document or adjust your business
process documentation during operations, e.g.
with system information
Ÿ  Optimize: Verify your business process
documentation before upgrades, e.g. delete
obsolete information, e.g. not used custom
code
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Solution Documentation life-cycle
Template Management
à create global
documentation
Upgrades
à verify
documentation
Application
Management
Implementation
à create or
locally adjust
documentation
Operations
à re-document
Configuration
à extend
Documentation
13
Documentation
Types
Documentation contains 2 types of documentation
Technical Landscape Documentation
Ÿ  System, server, database and software component documentation
Ÿ  Maintenance done by:
–  System administrators
–  Technical SAP Solution Manager experts
Business Process Documentation
Ÿ  Documentation of Core Business Processes, related interfaces and custom code
Ÿ  Maintenance done by:
–
–
–
–
solution architects, e.g. for custom development and interface specifications;
business process experts, e.g. to document (core) process flow
project members, e.g. to document test cases and project specific customizing
functional SAP Solution Manager experts, e.g. for simple transfer if good process documentation is
available
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
14
Documentation- Use Cases
Reuse of Business Structure and Related Information in SAP Solution
Manager Capabilities
Blueprint
Structure
Tabs /
Tab content
Business
Blueprint
Configuration
Testing
System
Monitoring
Business ProSolution
cess Monitoring Maintenance
Solution
Upgrade
Scenarios
Processes
Process
Steps
Project
Documents
Transactions
Configuration/
Development
Test Cases
E-Learning
Interfaces
Systems/
Servers
*
*
Logical
Component
* Limited reuse of information
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
15
Solution Implementation – Approach
Fast, Easy with Integrated Functionalities
Ÿ  Use optimized implementation, updates
tools and methods
Ÿ  Usage of Methodology concept and
accelerators speed project organization
Ÿ  Usage of integrated test scenarios
reduce test and training effort
Ÿ  Use integrated comprehensive (project)
documentation
Ÿ  Implement a solution based on SAP
best practices and according to SAP
implementation methods
Ÿ  Ensure smooth and secure go-live
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
16
Implementation – Goal
Speed Implementation and Reduce Costs
Ÿ  Provide proven and comprehensive
implementation, update and upgrade
support
Ÿ  Enable global standardization
Ÿ  Consolidate and preserve project
documentation
Ÿ  Optimize customizing and configuration
Ÿ  Optimized and accelerated test
management and execution
Ÿ  Enable knowledge transfer from experts
to end users
Ÿ  Manage phases with Quality Gates
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
17
Implementation
Implementation Project Administration
Project Administration is used to create
the project and define some global
settings such as:
Ÿ  Project system landscape: all systems relevant
for business processes which has to be defined,
documented and implemented by this project.
The systems are represented by Logical
Components.
Ÿ  Assignment of a Roadmap: SAP is providing
standard SAP Methodology in form of
roadmaps.
Ÿ  Roadmaps are providing information how to run
the project and which tasks have to be done in
which phase
Ÿ  Definition of project standards: definition of
keywords, and document types (templates).
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Configuration
Blueprint
Testing
Implementation
Project
End User
Training
Solution
18
Implementation
Blueprint
Business Blueprint is used to define
your ‘To-be’ processes and the project
scope:
Ÿ  In the blueprint you can define the business
scenarios which are consisting of business
processes. The business process is build out of
business process steps (transactional steps).
Ÿ  Assignment of documents: you can use the
predefined document templates (from Project
Administration) to describe business processes
and specify then technically.
Ÿ  Assignment of transactions: transaction
representing the business process step can be
assigned on the appropriate tab.
Ÿ  Assignment of structure attributes
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Configuration
Blueprint
Testing
Project
Administration
End User
Training
Solution
19
Implementation
Configuration
Configuration is used to define your
customer specific developments, execute
and implement the configuration as well
as document the test cases and training
material.
The Configuration reuses the same
structure to document business
processes with additional assignments.
Ÿ  Assignment of configuration objects: it is
recommended to assign the configuration objects
at lowest possible level (business process step).
You can assign IMG objects, reports, transactions
or documents describing the configuration
content.
Ÿ  Assignment of development objects: it is
recommended to assign the development objects
at lowest possible level (business process step).
You can assign reports, function modules,
classes, includes (and much more) or documents
describing the development content.
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Configuration
Blueprint
Testing
Project
Administration
End User
Training
Solution
20
Implementation
Use Cases
The following processes and capabilities are integrated with Solution
Implementation activities
Ÿ  Business Process Modelling
Ÿ  Document Management Basics
Ÿ  Interaction Document Management
Ÿ  Roadmap
Ÿ  Testing
Ÿ  Business Process Change Analyzer
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Ÿ  Service Desk Integration
Ÿ  ChaRM Integration
Ÿ  Solution Documentation Assistant
Ÿ  Business Process Monitoring
Ÿ  Compare & Adjust
21
Add on: SAP Business Process Blueprinting
SAP Solution Manager 7.1
as THE Single Source of Truth
SAP business
process expert
SAP users
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP business
process expert
Non-SAP users
22
SAP Business Process Blueprinting and SAP Solution
Manager
Ÿ  Document Your Business
Process Requirements and
Processes
SAP ES Workplace
Ÿ  Adapt SAP best-practice
processes to meet Your
business best
Ÿ  Facilitate discussions on
process implementation and
optimization
Third
Party
SAP Solution
Manager
Homegrown
Business Process
Blueprinting
Business Process Library
Solution Composer Server
Enterprise Services
Repository
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP ERP
SAP NetWeaver
BPM
Ÿ  Visualize Your Scenarios and
Processes for better
communication and proper
scoping
Ÿ  Client: Eclipse RCP
Ÿ  Solution will be available with
SAP Solution Manager 7.1 as
a pilot release
23
Add-on: SAP Solution Manager and ARIS
Integration
SAP SOLUTION MANAGER
ARIS
Blueprint Structure
Business Process Structure
Business Scenario
Business Process 1
5-level Model
Business Process Step 1
Business Process Step 2
Business Process Step 3
…
Business Process 2
Business Process Step 1
Business Process Step 2
Business Process Step 3
•
•
•
•
ARIS Script
Mapping
3-level Model
(IT View)
Exchange of business process structures
Transfer of transactions assigned to business process structures
Representation of business process documents by links in ARIS
Exchange of End-User roles information assigned to the business process structure
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
24
Template Management
Approach
Ÿ  Define scenarios and processes as templates as well as a global rollout roadmap
as implementation methodology
Ÿ  Specify to what extent rollout projects can effect changes in delivered templates
that are already being implemented
Ÿ  Assign process documentation, transactions, configuration settings and
documents as well as developments such as test cases and roll-out training
materials.
Ÿ  Easy implementation of rollout projects generated by template selection. Reuse of
standard processes, configuration and documentation for global Processes
Ÿ  Optimize, compare and adjust your newly created templates with already
implemented ones
Ÿ  Roll in changest from Operation to Template Project development landscape
supported by synchronized maintenance projects (Retrofit).
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
25
Template Management
Goal
Template
Managed System
Reference System
Ÿ  Is a container that bundles business processes which are standardized to a certain extent
Ÿ  Links to process-specific developments, configuration, and test data
Ÿ  Can be used for roll out to other company locations
SAP Solution Manager
CRM System
BC Sets
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
ERP System
Transactions
SCM System
Test Cases
26
Template Management Project Functions
•  Setting the Global
Attribute influences
the changeability in
the roll-out project
Roll-out Project
Template Project
Global Attributes – Functions for Structures
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
27
Re-Documentation
Approach
How could I get my existing documentation into
SAP Solution Manager?
n  Solution Re-documentation means having documented core business processes
including the related:
n
Documentation, e.g. process design, specifications, configuration or business test requirements
n
Technical objects, e.g. transactions, TBOMs, custom code, background jobs, system configuration,
interfaces
System and software components (SAP and non-SAP)
n
n  Redocument - current documentation available
n
n
Manually transfer business process structure and related objects in business blueprint
Maintain business process structure and related objects in XLS, Lotus Notes and transfer it via
XML upload (as this procedure requires expertise this is currently an consultant solution, only)
n  Transfer - current and compatible tool based documentation available
n
Automatically transfer business process structure and related objects in business blueprint
n
XML upload: select content, structure it, and transfer via XML (see above)
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
28
Re-Documentation
Goal
Enhanced solution and process usage transparency
Comprehensive representation of current implemented
and used processes and solutions
Ready for standardization through comparison of
business processes at different locations
Accelerates initial Solution Documentation, ready for reuse for future projects or templates
Basis for optimized testing
Implementation of central entry point to manage and
monitor all solutions and processes
Enables simple and fast system consolidation
Facilitates business improvements
Cost-efficient through automated verification of Solution
Documentation
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
29
Re-Documentation
Use Cases– Based on Usage Data
Risk-Based Testing Strategy
Upgrade Preparation / System Consolidation
Standardization / Template Management
Accelerated Innovation
Centralized Documentation Repository
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
30
Add On: Reverse Business Process Documentation
(RBPD)
Reverse Business Process Documentation (RBPD) allows the customer to easily
re-document his business processes directly from his SAP systems. The redocumentation is done by analyzing the actual usage of the system and is
supported by comprehensive analysis content pre-delivered from SAP.
Usage analysis
Pre-defined
Content
Solution Documentation
Assistant
Re-documentation
SAP Solution Manager
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP system
31
RBPD
Detailed Data Flow
SAP Solution Manager
Projects (all types)
Solution
Content Interface
4
ERP upload BP
structures
3
Solution Documentation Assistant
1
1 = Upload business process
structure/rules
2 = add custom transactions manually
3 = Analyze managed systems
4 = Create and complete project
(custom objects)
5 = Hand over to solution
SAP
Solution
Landscape
Usually 3 -6 months period (performance reasons)
2
SAP ERP
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP CRM
SAP SCM
Other
32
Agenda
Who should attend this Service
Ÿ  Project Managers and project team members
Ÿ  Support/BAU
Configuration
ReDocumentation
Blueprint
Testing
Upgrade
Implementation
Project
Maintenance
End User
Training
Template
Solution
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
33
Attendees for this Service
Principal Technology Consultant
•
•
•
•
Project definition and administration
Provide a clear project methodology to manage project
efficiently on- time and within budget
Maintaining Business blueprint information
Define, maintain and assign the process structure and items
under that
Technology Consultant
•
•
•
Maintaining Configuration objects
Keep track of developments
Assign test cases to ensure transparency for testing
•
•
•
Usage analysis using Solution Documentation Assistant
Business Process Modeling
Template Roll-out
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
34
Agenda
How can you use the information you received during the Service
Ÿ  Effort of Service delivery
Ÿ  Deliverables in any One of the flavors
–  Documentation & Implementation, Template Management and Re-Documentation
Configuration
ReDocumentation
Blueprint
Testing
Upgrade
Implementation
Project
Maintenance
End User
Training
Template
Solution
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
35
Delivery – Building Blocks
Road map for
documentation and implementation
in SAP Solution Manager
Service Flavor
Service Flavor
Service Flavor
Add-on 1
Add-on 2
Documentation &
Implementation*
Template
Management*
Re-Documentation*
SAP BB or ARIS
RBPD
Effort 20 PD
Effort 22 PD
Effort 24 PD
Effort 5 PD
Effort 5 PD
by
2 Consultants
by
2 Consultants
by
2 Consultants
by
2 Consultants
by
2 Consultants
SAP BB = SAP Business Blueprinting
RBPD = Reverse Business Process Documentation
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
* includes 4 business processes with
10 process steps each
36
Delivery – Additional Business Processes
Services covers 4 business processes
with max 10 process steps each
Service Flavor
Service Flavor
Service Flavor
Documentation &
Implementation*
Template
Management*
Re-Documentation*
per additional
business process
with 10 steps
Effort 20 PD
Effort 22 PD
Effort 24 PD
Effort 1 PD
by
2 Consultants
by
2 Consultants
by
2 Consultants
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
37
Approach
Customer
presentation
?
?
?
?
Questionnaire
Kick Off
Scoping WS
Service Delivery
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Service scope plus delivery range
20 day to 34 days
Pre selection of service flavor + add-on
Presentation of service flavor specific
Kick Off documents
Definition of service flavor + add-on
Delivery of the service and knowledge transfer
38
Flavor
Documentation & Implementation
Upgrade/
Long Term
Project
Solution
Implementation
Project
Maintenance
Project
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
39
Documentation
SAP Solution Manager:
Typical Customer pain points
Commence the prerequisites of Solution
Documentation
Ÿ  Types of documents to the loaded
Ÿ  Present storage of documents (third party tool, etc.)
Ÿ  Upload methodology
Create a project
Get the approval on 1 scenario with up to 4
business processes
Ÿ  Create the structure
Ÿ  Check the transaction codes
Ÿ  Upload the appropriate documents
Hand over to Support
Ÿ  Additional Information:
Ÿ  Provide a how to manual on what was set up in SAP Solution
Manager
Ÿ  Discuss the authorizations required for the designated roles
Ÿ  Deliver a knowledge transfer session to the nominated client
staff on how to maintain the Solution and the document flow
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
40
Implementation
Create a pilot project
Ÿ
Ÿ
Ÿ
Ÿ
Select the roadmap
Enter the project team
Choose the system landscape
Establish the project standards (status values, keyword searches, templates)
Create the business blueprint structure
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Implementation
Project
Use the BPR to create 1 scenario with up to 4 business processes
Load documents
Enter transaction codes
Create service messages
Create end users
Create a Solution
Additional Information:
Ÿ  Provide a how to manual on what was set up in SAP Solution Manager
Ÿ  Discuss the authorizations required for the designated roles
Ÿ  Deliver a knowledge transfer session to the nominated client staff on Solution Implementation to Hand
over to Support
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
41
Flavor
Template Documentation
Upgrade/
Long Term
Project
Solution
Implementation
Project
Template
Project
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Maintenance
Project
42
Template Management
SAP Solution Manager
Create a pilot template project
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Select the roadmap
Activate global rollout functionality
Define template scope
Enter the project team
Choose the system landscape
Establish the project standards (status values, keyword searches, templates)
Template
Project
Create the business blueprint structure
Ÿ  Define global processes and requirements
–  Use the BPR to create Use the BPR to create 1 scenario with up to 4 business processes
Ÿ
Ÿ
Ÿ
Ÿ
Load documents
Enter transaction codes
Create service messages
Create end users
Additional Information
Ÿ  Provide a how to manual on what was set up in SAP Solution Manager
Ÿ  Discuss the authorizations required for the designated roles
Ÿ  Deliver a knowledge transfer session to the nominated client staff on Template Management to Hand over
to Support
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
43
Solution Documentation Assistant
Template Management / Standardization
i
Create a Global Template
Choose the system expected to be closest to
your company standard, create a Solution
Manager project and do the Solution
Documentation
Solution Manager
Project
Create an Analysis Project and run an
analysis
Start analysis for a second system/client and
compare the usage of the processes and
steps . If there are differences, evaluate if one
can be chosen as standard
Update the Solution Manager project structure
with the new process or step and roll-out the
new processes
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
PRD
EMEA
Solution
Documentation
Assistant
PRD
China
44
Flavor
Re-Documentation
Upgrade/
Long Term
Project
Solution
Implementation
Project
Excel
Upload
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
Maintenance
Project
45
Re-Documentation
SAP Solution Manager
Commence the prerequisites of Solution
Documentation
Ÿ  Types of documents to be loaded
Ÿ  Present storage of documents (third party tools, etc.)
Ÿ  Upload methodology
Create a project
Get the approval on Use the BPR to create 1
scenario with up to 4 business processes
Ÿ  Create the structure
Ÿ  Check the transaction codes
Ÿ  Upload the appropriate documents
Hand over to Support
Ÿ  Additional Information:
Ÿ  Provide a how to manual on what was set up in SAP
Solution Manager
Ÿ  Discuss the authorizations required for the designated
roles
Ÿ  Deliver a knowledge transfer session to the nominated
client staff on how to maintain the Solution and the
document flow
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
46
Business Blueprint Upload Interface: Process Flow
System
Administrator
Business Process
Expert
Program
Management
Create a project
Create structure
Upload file
Create content
upload file
Maintain file
Upload file
Edit and Finalize
business blueprint
New functionalities in Release 7.1
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
47
Upload Interface for Initial Upload of Blueprint Structure
and Documents
Initial documentation is automatically being build up
by using implementation projects in SAP Solution
Manager. To speed up this process, a new upload
interface has been built into the Business Blueprint.
The following information can be uploaded from external
sources:
Ÿ  Business Blueprint Structure
Ÿ  Business Blueprint Structure Attributes
Ÿ  Project Documentation tab
Ÿ  Transactions tab
Ÿ  Business Functions tab
Ÿ  Configuration tab
Ÿ  Development tab
Ÿ  Test Cases tab
Ÿ  Training Material tab
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
How to work with the upload
interface:
Export the structure, attributes
and other tabs to template .txt
files which contain content
examples for your reference
and can easily be edited, e.g.
with Microsoft Excel.
Create a Business Blueprint
Structure first before you
continue uploading additional
content.
Detailed information can be
found in the SAP Solution
Manager online help.
48
Detailed approach for all flavors
1 business scenario with up to 4 business processes and no more than 10
process steps
Up to 3 fully documented steps including customer documents
Up to 8 documents types
Up to 6 status schemas
2 structure attributes
2 document attributes
One interface
One template
One reference folder (KW)
One reporting variant
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
49
Difference Between Documentation, Re-Documentation
and Reverse Business Process Documentation
DOCUMENTATION
RE-DOCUMENTATION
Position
Position
Ÿ  When the client has no
documentation available
Initial steps
Ÿ  Ascertain the types of
documents the client will use
Ÿ  In conjunction with the client
design a document strategy
Ÿ  Create a project in SAP
Solution Manager using the
BPR for the blueprint structure
Add On
Ÿ  Consider Reverse Business
Process documentation
Ÿ  The client has documents,
however these are not stored
in a central repository
Initial steps
Ÿ  Create a project in SAP
Solution Manager
Ÿ  Use the XLS interface to
accelerate the process of
uploading documentation
Workshop
Ÿ  Simple example of IBIS
content used to detect
productively running business
processes (by using SoDocA)
Add On
Ÿ  Reverse Business Process
Documentation
REVERSE BUSINESS
PROCESS
DOCUMENTATION
Position
Ÿ  Business processes are used
in a customer’s productive
environment and answers the
question of how business
processes can be
documented, reflecting real
usage from day to day
execution
Initial steps
Ÿ  Load the latest RBPD content
into SoDocA
Ÿ  Assign roles and
authorizations
Ÿ  Complete the technical
prerequisites
Ÿ  Run the analysis
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
50
Thank you
Contact information:
Robin Schönwald
Business Development Manager, SAP Consulting
E robin.schoenwald@sap.com
© 2014 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. 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.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP SE in Germany and
other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin
are trademarks or registered trademarks of Citrix Systems Inc.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®,
World Wide Web Consortium, Massachusetts Institute of Technology.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of
Crossgate AG in Germany and other countries. Crossgate is an SAP company.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.
©  2014 SAP SE or an SAP affiliate company. All rights reserved.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP SE.
52