SNP SYSTEM SCAN PRODUCT DESCRIPTION

Transcription

1 SNP 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) Creation of a standardized S/4 Assessment and providing the results as slide show and HTML report. Further information can be found in the chapter S/4 HANA Assessment 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. Customer tables: Exact fill level analysis of all tables in customer name spaces. 02 SNP SYSTEM SCAN

3 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. 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: 03 SNP SYSTEM SCAN

4 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 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. SNP System Scan 04 SNP SYSTEM SCAN

5 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. S/4 HANA Assessment Evaluation of a scan by used organizational units The SNP S/4 Assessment helps you to better plan a migration project and provides the following features: Standardization degree of the SAP system The standardization degree of the SAP system is used to determine whether the system complies with the SAP standard or is highly customized. A high standardization degree generally means less effort in the migration to S/4HANA. Where are most of the data stored? SAP standard, custom developments or third party developments? Do SAP standard developments, custom developments or third party developments move most of the data? Are the employees mainly using SAP standard programs or custom developments and third party software? 05 SNP SYSTEM SCAN

6 Usage of the SAP system This area shows the usage of the SAP system. In particular, it is examined whether certain modules are active or inactive and how they are actually used. This allows to derive different strategies, e.g., should the entire SAP system be migrated to SAP S/4HANA or only a specific, frequently used module? Which modules are active or inactive? Which modules are most frequently used? How many different transactions are frequently used per module? Potentials of the SAP system The potentials of the SAP system can be exploited by taking a closer look at active but unused areas of the system and turning them off. These include, first and foremost, unused organizational units and custom developments, which cause unnecessary costs in the context of restructuring measures and maintenance operations. Above all, however, it is custom developments that result in significant effort in the context of the SAP Custom Code check to examine the operability in an SAP S/4HANA system. A restriction to actually used custom developments simplifies the check enormously. Which organizational units are actually used in the active system? Which custom developments are used or not used? Which third party developments are used or not used? Fiori Apps Fiori is the new user interface of SAP and brings with it a brand-new user experience. The old transactions are gradually transported from the SAP GUI to the browser or mobile devices using Fiori apps. This makes SAP applications simpler and more user-friendly. The SNP System Scan can be used to determine the relevant Fiori apps based on the usage of the SAP system. Which Fiori apps are interesting based on the usage of the system? Which conditions must be satisfied in order to execute the Fiori apps? Which user groups would benefit most from Fiori apps? Which Fiori apps will probably not be used based on the usage of the SAP system? 06 SNP SYSTEM SCAN

7 Impact of SAP S/4HANA Simplifications Simplifications describe the difference in the data model and transactions with regard to the available modules and functions in an SAP S/4HANA system. The SNP System Scan lists the simplifications that are relevant based on the usage of the system or active Business functions. Which simplifications are relevant based on the usage of the system? Which simplifications are relevant based on the active Business functions? Which simplifications hold the highest risk? The S/4 Assessment is continuously expanded and improved. In future SNP System Scan versions, further evaluations will be available. Risk in transitioning to SAP S/4HANA When transitioning to S/4HANA, there is the possibility that functions you are currently using are no longer contained in the function scope. Based on the SAP Simplification Database and the SAP Blacklist, the SNP System Scan analyzes which used functions change or disappear when transitioning to S/4HANA. The following objects are taken into account: Transactions that change or disappear when transitioning to S/4HANA Reports that change or disappear when transitioning to S/4HANA SAP tables that change or disappear when transitioning to S/4HANA Integration of SAP Pre-Transition Checks Before migrating to S/4HANA, SAP recommends performing different analyses. The SAP Pre-Transition Check classified as an important part of the analysis package and strongly advised to be carried out delivers a list of items that need to be considered prior to a conversion. For the execution of the SAP Pre-Transition Checks, numerous SAP Notes must be imported into the relevant SAP system. The SNP System Scan uses the functionality of the SAP Pre-Transition Checks, i.e. when executing the SNP System Scan, the Pre-Transition checks are executed as well. After completing the SNP System Scan, the results are available in the Scan results. This enables you to use the full range of functions of the SAP Pre- Transition checks without the need of importing additional S-Notes. 07 SNP SYSTEM SCAN

8 Limitation 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. Copyright Copyright SNP AG, All rights reserved. All other products mentioned in this document are registered or unregistered trademarks of their respective companies. 08 SNP SYSTEM SCAN