Overview of the solution offering “Profiling for SAP®” for the analysis, re-engineering and re-documentation of SAP® ERP systems TransWare Software Solutions AG

Scenarios and Use-Cases Page  2

Some typical questions of an SAP® person in charge Page  3 Who is actively using SAP®, and in which way? Is the current number of existing, customer-specific “Z” transactions and reports actually needed? Which areas should I focus my training efforts on? Do we have to update our customer-specific transactions and reports to the latest SAP® release? Do I have a problem with authorizations concerning Segregation of Duties (SoD)? Where shall I concentrate my validation efforts? Where I can increase efficiency of corporate SAP® usage? In the context of a system consolidation, which processes from individual SAP® systems are to be used in the future as Best Practice processes in the new SAP® system? ? ? ?

The aspects of SAP® analysis, re-engineering and re-documentation with Profiling for SAP® Page  4 1) Technical analysis Customer transactions and reports, user exits, development object modifications Authorizations management (roles, profiles, authorization objects, customizing,…); analysis of arbitrary SAP® configuration data 2) Functional and organizational analysis Functional usage of the SAP® system (transactions, reports, RFC calls (from portals, external applications), document types) Configuration of the technical organization levels, HR info types 3) Business process analysis Capture of the customer-side SAP®-supported business processes Creation of SAP® Solution Manager Blueprint descriptions (projects) Technical analysis Process analysis TransWare AG has developed a comprehensive software solution for process and configuration analysis based on business intelligence, SAP® NetWeaver, SAP® Solution Manager and SAP® methodologies: Functional & org. analysis

Analytic reports as work results of Profiling for SAP® Page  5 Output formats of the analyses: Web-based reports, Excel reports, business charts Blueprint projects in SAP® Solution Manager BPM modeling format Content-related examples of analyses: Which transactions and reports are used within the organizations most frequently? Usage of customer-specific Z, Y transactions and reports Organizational and authorization analyses Comparison of the system usage and configuration across several SAP® clients, system roles and systems Activity of the SAP® users, in view of license usage monitoring and optimization Profiling für SAP® Vergleiche Technical analysis Functional & org. analysis Process analysis

Use and benefits through Profiling for SAP® Page  6 Lower costs through automated procedure, as compared to manual documentation Cost reduction in the creation of an SAP® development object inventory, analysis of transaction usage, customer-specific transactions and reports, user authorizations, document type usage, … Cost reduction for As-Is process documentation including the semi-automatic creation of SAP® Business Blueprints for process modeling, analysis and optimization Reduced expenditure of time for data capture; quicker results Automated inventory list creation instead of conventional approach with audits and workshops Creation of process models from existing SAP® reference models out of the SAP® BPR, scoping of the models by means of the inventory list data Via precise snapshots of the inventory, profiling of the temporal development are possible Higher quality; reproducible results Accurate usage data for transactions, reports and RFC-enabled function modules; comprises Y, Z, and customer namespace objects, customer extensions and exits Accurate information on the customizing status of transactions, reports, rights configuration Inclusion of authorization roles, profiles, user accounts permits Governance-Risk-Compliance (GRC) analyses like access control or 4/6-eye-principle checking (SoD) Easily repeatable steps with maximum reproducibility of the results Technical analysis Process analysis Functional & org. analysis

Technical Analysis Improving the software support and maintenance of SAP® Page  7 Technical analysis Functional & org. analysis Process analysis

Overview: Technical analysis Page  8 Technical analysis Functional & org. analysis Process analysis Technical analysis delivers basic statements in the profiling of SAP® systems. SAP® development objects like programs, function modules, classes, transactions etc. are read out from SAP®. In addition, the entire authorizations management including roles, profiles, authorization objects and user accounts is read from SAP® into the profiling SQL database. The data baseline from the technical analysis permits a comparison of different SAP® systems in the context of system consolidations, or to check the configuration of individual SAP® system roles like production, test and development. Further analyses permit the optimization of authorizations for the streamlining of the authorizations management, access checking as well as SoD analyses.

Overview of the SAP® modifications of an SAP® system as a 3D chart Page  9 Modification types SAP® module Anzahl Modification types Analysis of the miscellaneous adoptions of the SAP® system’s development objects: Z, Y, /customer-namespace/ for SAP® transactions and reports SAP® modifications User exits Example of an SAP® ECC 6.0 with SAP ® modifications: Technical analysis Functional & org. analysis Process analysis

Modification types for a given SAP® module Page  10 Technical analysis Functional & org. analysis Process analysis Distribution of the SAP® modification types for a given module like e.g. SAP® MM Critical code modifications without modification assistant Drill-down into object types like e.g. “programs modified” Critical, modified program objects

SAP® modules for a given SAP® modification type Page  11 Technical analysis Functional & org. analysis Process analysis Distribution of e.g. critical SAP® code modifications “Program changes without modification assistant” SAP® SD Drill-down into object types like e.g. “programs modified” SAP® modules Critical, modified program objects

Analysis of authorizations management including the use of SAP® transactions Page  12 Technical analysis Functional & org. analysis Process analysis Authorization objects (roles and profiles, hierarchy) SAP® objects like transactions including descriptions Call count Analyses on different levels: Anonymous analyses (without user account reference) Analyses with SAP user account reference

Functional & org. analysis Improving the efficiency and utility of SAP® Page  13 Technical analysis Functional & org. analysis Process analysis

Overview: Functional and organizational analysis Page  14 Technical analysis Functional & org. analysis Process analysis Functional and organizational analysis utilizes the data from the technical analysis, and combines them with data on the usage of transactions, reports, RFC function modules, document history and document flow, organizational levels (of technical org units) as well as (optionally) HR info types. SAP® usage can be correlated with accounts, authorizations or organizational units. Further, modifications of the standard can be identified with reference to SAP® usage. Hence detailed statements arise as to the system usage characteristics of the organization, as well as to license optimization. A comparison of the usage with the customizing of SAP® across the time frame investigated provides detailed assertions concerning the real use of adapted objects. This way, the deconstruction of customized objects is facilitated, as well as the upgrade of systems.

Page  15 Functional and organizational analysis: “What is used within SAP®, and by whom?” Technical analysis Functional & org. analysis Process analysis Usage frequency of SAP® objects like e.g. transactions and reports per SAP® module Detailed usage analysis of SAP® transactions on an organizational level like e.g. business areas

Savings potential with functional SAP® upgrades Page  16 Estimation for the “functional upgrade” scenario: Reduce by up to 50% of unused transactions and reports 0.5 days needed for upgrade & validation per transaction; 0.25 days per report; EUR 800.- per day Typical cost reduction: 50% (312 / 2 + 2376 / 4) * 800 = EUR 300,000.- 355 customer-specific transactions, 312 thereof unused (about 88% unused) 2.783 customer-specific reports, 2376 thereof unused (about 85% unused) Technical analysis Functional & org. analysis Process analysis Reduce

License optimization Page  17 168 users have been inactive within the analysis timeframe Detailed analysis of SAP® usage in different contexts like org. units, roles, user accounts e.g. usage with reference to module and user account Minor (or no) usage Technical analysis Functional & org. analysis Process analysis

Pre-configured reports for the analysis of all aspects of transactions, organizational levels, document types, etc. Page  18 Statistics, analytical reports Technical analysis Functional & org. analysis Process analysis Master data and organizational data Document types, doc. flow and history

Process analysis Optimizing SAP® business processes Page  19 Technical analysis Functional & org. analysis Process analysis

Overview: Process analysis of SAP® Page  20 Technical analysis Functional & org. analysis Process analysis Process analysis is based on the data from the functional and organizational analysis, in combination with business process reference models. Those reference models may be customer-specific, or originate from the SAP® reference model or from Blueprint projects in SAP® Solution Manager. By means of a specified methodology, the quality of the generated process models – according to the SAP® systematic – is improved via workshops with process owners. Through an interface, the process models and their associated SAP® transactions can be loaded into the SAP® Solution Manager process repository which is structured into projects. These process models, as a so-called SAP® Business Blueprint, form the basis of a detailed documentation of the customizing of an SAP® solution.

SAP® Solution Manager Blueprint Project including the used SAP® Transactions Page  21 Technical analysis Functional & org. analysis Process analysis 1) Analysis & Reengineering 2) As-Is / to-be Process Models 3) To-be Blueprint The Process Analysis has 3 sub-phases: SAP® analysis and re-engineering to upload SAP® Transactions to SAP Solution Manager As-Is Process Documentation, the business process analysis for the optimization of to-be business processes Mapping the to-be processes to SAP Objects for the SAP® Blueprint The Profiling for SAP® solution is a part of the initial analysis phase and delivers the input for the following process documentation and optimization phases Transactions are loaded into the SAP® Solution Manager project with a structure based on existing Blueprints or Reference Models Profiling for SAP® comes with a methodology to improve generated process maps SAP® Solution Manager Blueprint Project with Business Scenarios, Processes and Process-Steps including assigned Transactions

Profiling for SAP® for the process documentation and blueprinting with SAP® Solution Manager (SSM) Page  22 Re-engineering and analysis As-Is and To-Be processes models To-Be SAP® Blueprint Profiling for SAP® SSM As-Is project SSM Blueprint project Optimized SSM Blueprint project SAP landscape Optimized To-Be process models As-Is business process models SAP® As-Is process maps To-Be models with SAP® objects Technical analysis Functional & org. analysis Process analysis Development template:

SAP® business process capability maps Page  23 Corporate business processes on the basis of the SAP® system specifications (excerpt) Business scenario level Process level Technical analysis Functional & org. analysis Process analysis Unused process with respect to SAP® standard Active process in the company

Process level with process steps (activities) and assigned SAP® transactions (capability map) Page  24 Technical analysis Functional & org. analysis Process analysis SAP® module Process steps (activity not executed) Roles or profiles Process steps (activity executed) Transaction (active) Transaction (inactive)

Modeling methodologies, Best Practice and governance for BPM in SAP® projects Page  25 Technical analysis Functional & org. analysis Process analysis Modeling methods are compliant with SAP® standards and conventions are aligned to the SAP® process meta-model safeguard the compliance of the SAP® Solution Manager repository business logic “BPM Best Practice” for BPM employs SAP® reference models from the SAP® Business Process Repository (BPR) describes the connection between SAP® processes and end-to-end business processes specifies the application of business process architectures within SAP® projects BPM governance assures BPM project progress as well as the workflows among the actors defines the end-to-end process of modeling using SAP® Solution Manager matches the BPM procedure to the course of action within the SAP® project

Technical configuration Profiling for SAP® for a comprehensive configuration, usage and process analysis of complex SAP® landscapes Page  26

Solution components and information flow Page  27 Profiling for SAP® SQL Business intelligence, web-based reporting BPM tool SAP® Solution Manager Reporting templates Process models SAP® projects and process repository SAP® Solution Manager SAP® system landscape SAP® Business Process Repository, reference models Results

Three alternatives for the execution of Profiling for SAP® for system landscape analysis Page  28 Variant 1: Execution of a job on the SAP® systems Variant 2: Execution of Profiling on SAP® Solution Manager Variant 3: Profiling as a SaaS offering External service provider Customer – SAP® Solution Manager Customer – SAP® landscape R/3 4.6, 4.7, ECC, CRM, SCM, ... ABAP 700 application server is used. Profiling installed on a central server, analysis of the satellite systems via RFC. No SAP® Solution Manager is used. Installation of an ABAP report and execution as a job on the SAP® system Within this variant, the Profiling solution is used as Software as a Service (SaaS). The analysis takes place across a SAP® Router connection.

Summary Page  29 Safety, simple use Central installation of the analysis software needed on an SAP® application server >700 No software installation needed on the productive SAP® ERP systems Variety of supported target systems: R/3, ECC5, ECC6 as well as new SAP® modules (CRM, SCM, PLM, SRM, ...) Access to the full potential of the SAP® system Support for a migration towards SAP® standards, employing the latest SAP® reference models Employment of automatically created process models where they are actually needed (SAP® Business Blueprints in the Solution Manager, SOLAR01), in implementation/upgrade projects Easy processing and publishing of inventory data and process models BI analysis tools for the inventory data catalogs; publishing as MS Excel, HTML, etc. Creation of process models in the BPM format, for subsequent processing in BPM tools and viewing by users from a business process perspective Access to SAP® usage, process, and configuration data without the need for technical SAP® knowledge

Solutions by TransWare Page  30 TransWare Software Solutions AG Fritz-Wunderlich-Str. 49 66869 Kusel Germany Phone: +49-(0)6381-916-0 Email: info@transware.de Web: www.transware.de All product, service and company names mentioned herein are for identification purposes only and may be trademarks or registered trademarks of their respective owners