SYSTEM SCAN PRODUCT DESCRIPTION

Transcription

1 SYSTEM SCAN PRODUCT DESCRIPTION

2 Objectives The SNP System Scan is designed to determine basic statistical and structural information from SAP ERP systems. You can create an evaluation from a scan that provides an overview of the system. This applies in particular to the way the system is used (e.g. the scope of the organization structure or the utilization of the system or the modules). It is possible to compare multiple scans of different systems or clients. The SNP System Scan can be used prior to transformation projects to determine the complexity of the project. An essential question is how much the transformation rule set has to be expanded to transform all relevant tables and data objects. Scope of Function Contents and Determined Data For the determination of data, the Standard Scan and the Extended Scan are available. The modes differ in the quantity of the extracted data. The standard mode has a short runtime. It is optimized for sales purposes and contains all information required to create an offer. The extended mode extracts additional data that are relevant for consultancy and migration projects, and therefore has a longer runtime. It is used to perform more detailed evaluations. The determined data derived from the following areas. Technical Analyses SAP S/4 HANA-specific evaluation (available transactions under S/4, Fiori potential, determination of customer-relevant simplifications) Basic information: Determination of technical basic information, SAP Release, operating system, database system, SAP Kernel. Add-ons and extension-sets: Determination of installed add-ons, extension-sets and SAP HANA delivery units. Profile parameter: Determining of the current SAP instance profile parameter. SAP tables: Exact fill level analysis of tables from SAP name spaces. 02 SYSTEM SCAN

3 Customer tables: Exact fill level analysis of all tables in customer name spaces. Field content: Determination of the usage of settings in transaction data (e.g. used document types, material types). Selected number ranges: Determination of the use of number ranges of selected document types (e.g. purchasing documents, financial accounting documents). User: Determination of the detail information of users. No extraction of personal data. Exact fill level for master data Repository: Analysis of namespaces, customer developments and usage frequencies (usage statistics and UPL). Analysis of the DDIC information of customer tables System Usage: Analyses the actual usage of the system long term and on a weekly basis Transportation: Determination of the itinerary and its usage. Workflow: Determination of active workflows. Compliance: User and roles are checked rudimentary against compliance rules. No extraction of personal data. Provision of all information to carry out the SAP Fiori Relevance and Readiness Analysis. Determination of the usage of organizational units in customer tables. Business Analyses Determining active SAP modules and components. Business Object Repository: determining how many object instances exist for the corresponding BOR object types. Determining relevant SAP LT Business Objects. Transformation objects: Which data structures are covered by the transformation rule set (as part of SNP Transformation Backbone) and which areas have still to be expanded. 03 SYSTEM SCAN

4 Determining organizational structures that are used as part of the master- and transaction data. Determining relevant SNP Automated Testing objects for the test scope after the data migration Determining configured organizational structures and their connections. Archive objects: Collecting information about which optical archives, document archives, printer lists, and archived workflow documents exist. Evaluating the logical archives in which they are stored and how these archives are configured. Determining the new General Ledger and its usage as well as its definition. Determining used functions in the SAP Solution Manager (e.g. Service Desk or ChaRM). Determining active Business Functions and their dependencies Calculation of the relative size of organizational units 04 SYSTEM SCAN

5 Description Upon consultation with your SNP Consultant you will receive an that contains a transport. Import this transport to your SAP ERP system. Start the SNP System Scan via the interface in SAP GUI and monitor it during the run time. After completing the analysis, you download the data via this interface. Only edit settings of special analyses. The analysis takes several hours and will be planned as batch job. During the execution the scan will only read from the analyzed system. There won't be changes to the analyzed system. The scan has no individual data storage and saves the result in the directory of the application server. It is also possible to save the analysis result in the SAP spool. System Scan 05 SYSTEM SCAN

6 The system scan saves the results in a text file that you can transfer to SNP via or upload. You can then receive reports based on that data. Limitation Evaluation of a scan by used organizational units The SNP System Scan does not deliberately collect personal data or detailed business information. Given your organizational structures are based on individuals (e.g. sales or purchase organizations) personal data like names can be contained in the analysis result. The collection of this data can be disabled by starting the analysis with a specific parameter set. System requirements SAP R/3 systems from 4.6c. Minimum 1 GB free memory in the directory of the application server where the System Scan file is stored. SNP

7 Copyright Copyright SNP AG, All rights reserved. All other products mentioned in this document are registered or unregistered trademarks of their respective companies. Find out more Visit nttdatasolutions.com.au/snp-partnership 07 SYSTEM SCAN