Professional Documents
Culture Documents
Signavio Process Insights
Signavio Process Insights
How-To-Guide
Instructions to extract all necessary information and request SAP Signavio Process Insights, discovery edition
PUBLIC
Context
This step by step guide describes what needs to be done to request the SAP Signavio Process Insights, discovery
edition.
The SAP Signavio Process Insights, discovery edition will provide tailor-made recommendations based on data
extracted from your SAP ERP system. It will help business decision makers in your company understand the value of
moving the current SAP ERP to SAP S/4HANA and transform your processes.
SAP Signavio Process Insights, discovery edition can be used for a live SAP S/4HANA system.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Check Pre-requisites
Before you start, ensure that you fulfil the following prerequisites:
• The analysis is run only for productive SAP ERP 6.0 or SAP S/4HANA systems (incl. all EHP versions).
A system copy of the productive system shall not be used, as not all logs files are available there.
• ST-A/PI version 01V – SP0 or higher shall be installed on your ERP system. Version 01V SP3 is
recommended.
• Add authorization object SM_BPM_DET (with the Characteristic of 'OBJECT_MS’) and S_DEVELOP to
the user who is executing the report
• Human Resources line of business and related processes are not part of the analysis.
1
• Select scenario:
‘SAP Signavio Process Insights - Discovery’
2
• This field is inactive and default is set to 3 months. 4
3
• Keep the default selection of KPIs
1
•
4 Press the button Schedule Analysis and a pop-up will 2
3
appear
5
• You can chose to execute data collection immediately
or schedule it as background job.
We recommend to schedule the job at your best
5
convenience.
*If the screen you see on your system looks different and you do not find the field “Transaction
Usage Data Collection Period”, you might need to implement a later version of note 2758146.
If you have problems during the extraction process or any of the files mentioned below is empty, please follow the
instructions from the troubleshooting guide. If the error persists create an incident under component SV-SCS-S4R.
Ana_sys_add_info.xml
Additional technical information related to the
system related to database, level of different
solutions and software components installed.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Extract data
STEP 6: Final Checks
1. Check that the right zip file is shared, the file name 2. Check that JSON files contain data, by opening
should start with BPIAnalysisData followed by your one or two.
system ID and extraction date.
à If one of the files is empty, ensure that the latest
à This zip file should contain at least 10 JSON files versions of the SAP Notes are applied to your SAP
(depending of the usage of your system). If the zip file ERP system and data was collected in your productive
does not contain any JSON file, it is likely that it was system (see step 1).
incorrectly created with another program.
Incorrect Incorrect
Correct
If you have questions please reach out to us via:
Signavio-Discovery@sap.com
• Fill out the form and upload the original ZIP file
you have extracted in previous steps (please do
not change the content of any file)
• Questions?
Please contact us at: Signavio-Discovery@sap.com
www.sap.com/contactsap
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/copyright for additional trademark information and notices.